Openscapes / Openscapes/openscapes.cloud
Sync descriptions bwn GitHub Teams & policies here
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Example discrepancy:
Which do we keep @jules32 ?
GitHub Team description WorkshopAccess-2i2c
This team provides access to the NASA Openscapes 2i2c JupyterHub. You are invited to this team because you had access via a workshop in the last six months. This is short term access and will be removed within six months. Nothing in the NASA Openscapes 2i2c space is permanent.
Workshops and Hack-a-thons: This provides short term access of up to 1-month to participants of NASA Earthdata workshops. Participants will be removed at any time and have no expectation of on-going storage in their home directories.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names the GitHub Team description and the 2i2c Access Policies page as the two sources; compare the linked sections first. Confirm which wording is authoritative with a maintainer, then update the relevant description or policy so the access duration is consistent and verify both links.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100