-
Notifications
You must be signed in to change notification settings - Fork 16
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
add ipfs-tech org to key mf repos #109
Conversation
The following access changes will be introduced as a result of applying the plan: Access Changes
|
Looking at the changes here:
|
whoops, I didn't realize the teams were defined within this document, I assumed they were pointers to orgs registered in the greater github identity system. fixed in commit below.
whoops that was a typo, moved to
I defer to @mishmosh on how best to handle this, honestly-- I figured it was the Foundation's remit to make sure there are active maintainers for all the repos here listed, and thus being able to name them is probably good, but my personal remit and medium-term goals can all be met by just giving A.) me (or B.) the whole org) push rights. Should I open a separate PR for A or B and leave this one open for discussion? |
I think the preference is supposed to be for just enough access as required, then elevation on an as-needed basis. So prefer to not use |
Before merge, verify that all the following plans are correct. They will be applied as-is after the merge. Terraform plansmultiformats
|
Summary
Hey there-- as I've been leading the recent IETF efforts for multiformats and getting more involved in the general upkeep of docs and such, I never asked for privileges here, but Rod asked me to do so and the timing seems good since the IPFS Foundation now officially exists. I'm asking for privileges for the Foundation org rather than for me personally just to simplify delegation and maintenance down the road.
Why do you need this?
Just want to include multiformats/website in periodic documentation refreshes and have push-rights in multicodec if the IETF WG spins up in coming months.
What else do we need to know?
DRI: myself, @mishmosh, @darobin (current members of the ipfs-tech org)
Reviewer's Checklist