Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LEAP-Pangeo user policy #1

Merged
merged 5 commits into from
May 9, 2022
Merged

LEAP-Pangeo user policy #1

merged 5 commits into from
May 9, 2022

Conversation

rabernat
Copy link
Contributor

@rabernat rabernat commented Apr 7, 2022

This is a proposed user policy for LEAP-Pangeo access. Please review and give your feedback.

Copy link

@galenmckinley galenmckinley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

there are some typos, but I am not finding where I could edit them

Copy link

@galenmckinley galenmckinley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We will not have an "open to anyone" tier. Need to define how people are added on the first tier.

@rabernat
Copy link
Contributor Author

Thanks for the feedback so far. The best way to make suggestions and inline comments is to go to the "Files Changed" tab. There you can click on specific lines and comment on them. Use the "Start a Review" option to group your comments together. Documentation here: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews. cc @tz33cu

@rabernat
Copy link
Contributor Author

Comment on lines +57 to +64
The proposal should provide the following information.
- Instructor's GitHub username
- Basic information about the course (institution, department/program, student population, class size, course dates)
- Basic information about the Instructor (name, affiliation, research interests)
- Confirmation of available administrative support for using the LEAP-Pangeo Hub for the class (setting up user account, monitoring use, etc)
- Anticipated usage level of LEAP-Pangeo Hub, including
- Number of user hours / week
- Types of virtual machines to be used (`Small`, `Medium`, or `Large`)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A form needs to be created to capture this information. @tz33cu, you previously volunteered to do this, but I'm also happy to do it myself. I don't want to step on your toes, but I also want to make sure the form is consistent with what the policy says here.

This process should include adding / removing them from this GitHub Team.
:::

## Education Tier
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
## Education Tier
## Education Group

maybe more inclusive

@rabernat
Copy link
Contributor Author

rabernat commented Apr 25, 2022

Notes from today's EC meeting

Ryan: end of the day tomorrow to provide comments and then I will merge comments so that we can move forward, so that people can use the Hub

  • Courtney: use more inclusive language than "tiers"
  • Tian: KT team can develop a short form for applying for access
  • Galen: add policy on being able to call out people who are overusing space
  • Tian: add LEAPangeo user policy to the Code of Conduct (Erin: yes, there is a placeholder to link to this)
  • Tian: add version, date, and policy for revisiting

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants