Protocol for addressing admin changes
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- authorization, documentation
Research direction
Start with issue #65 and review the linked gesdisc-tutorials and python_cmr repositories, along with the referenced NAMS request and nasa-data email. No file or test is named; the issue is resolved when the requested maintainer and admin access are addressed and a transparent process for future admin changes is documented.
Written by the indexing model from the issue text.
Description
I have previously requested through NAMS following an NTR for the creation of the GitHub team: gesdisc as well as some subsequent repositories (https://github.com/nasa/gesdisc-tutorials). In addition, I have spoken with @frankinspace about becoming a maintainer of: https://github.com/nasa/python_cmr. Two things.
- I would like to request to be a maintainer of python_cmr
- I accidentally removed myself as admin of: https://github.com/nasa/gesdisc-tutorials and would like to be reinstated
I have been told to update my initial NAMS request to address both points. I did so for item (1) but there has been no action for months. Is there a more transparent process we can follow (i.e. through using GitHub's Issues)? I also sent an email back in January to the nasa-data email with no reply.
- Dominant language
- HTML
- Stars
- 393
- Forks
- 95
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from nasa/instructions
-
Difficulty 2/5 1-3 hours Newbie friendliness 57/100
nasa/instructions#101 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 42/100
nasa/instructions#95 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
nasa/instructions#77 · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
nasa/instructions#76 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 42/100
nasa/instructions#68 ·
All issues in nasa/instructions
Similar issues
-
bug platform-desktop platform-windows
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Termix-SSH/Termix#1951 · 2 comments ·
Maintainers usually reply within 1 day
-
ci good first issue priority:p1
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
mobeloper/better-oss#23 ·
-
Could Have good first issue security
Difficulty 1/5 Under an hour Newbie friendliness 88/100
hannahro15/Musical-Match-Saga#270 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
github-community-projects/private-mirrors#524 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
cloudflare/web-bot-auth#203 ·
Maintainers usually reply within 1 day