You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 9, 2017. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 9, 2017. It is now read-only.
Adding @gibfahn to help repo / perhaps give collaborators group access #58
I'm making this issue to document manually adding @gibfahn to the help repo as a collaborator. There are two other individuals who have manually been given these permissions as well.
I would like to suggest that we give collaborator permission to @nodejs/collaborators, allowing people to opt out of notifications but maintain the ability to admin the repo.
EDIT: I do now have edit access to this repo, although I can't work out how. The giving nodejs/Collaborators permissions in nodejs/help is what is outstanding.
I am really +1 on adding nodejs/collaborators to the allowed teams. Currently, only nodejs/evangelism is there.
Do we need a formal approval from @nodejs/ctc ?
Since we don't have (AFAIK) a documented process for adding people to the help repo, I'd say no, it doesn't need formal approval. But some consensus-seeking seems in order.
I'd propose:
tag @nodejs/ctc for comments (oh look at that, already done)
mention it at the CTC meeting that's happening in about 14 hours
If no one objects in either place—that is, if we only have expressions of support along perhaps with some expressions of indifference—that seems to me a reasonable indicator that we have consensus on adding nodejs/collaborators team to the nodejs/help repo.
Reading through this thread it looks like we have consensus that this is a good idea, and I don’t think there’s much harm in giving the collaborator group write access. Done!
Reacted by Gibson Fahnestock, Sam Roberts and Vse Mozhe Buty
Activity
gibfahn commentedon Jan 7, 2017
More people looking at nodejs/help seems like a good idea to me.
jasnell commentedon Feb 25, 2017
has this been done yet?
gibfahn commentedon Feb 25, 2017
I don't think so, looking at https://github.com/orgs/nodejs/teams/collaborators/repositories
EDIT: I do now have edit access to this repo, although I can't work out how. The giving nodejs/Collaborators permissions in nodejs/help is what is outstanding.
targos commentedon Feb 28, 2017
The "Adding @gibfahn to help repo" part happened.
@gibfahn you have been given individual access from https://github.com/nodejs/help/settings/collaboration
I am really +1 on adding
nodejs/collaboratorsto the allowed teams. Currently, onlynodejs/evangelismis there.Do we need a formal approval from @nodejs/ctc ?
Trott commentedon Feb 28, 2017
Since we don't have (AFAIK) a documented process for adding people to the help repo, I'd say no, it doesn't need formal approval. But some consensus-seeking seems in order.
I'd propose:
If no one objects in either place—that is, if we only have expressions of support along perhaps with some expressions of indifference—that seems to me a reasonable indicator that we have consensus on adding nodejs/collaborators team to the nodejs/help repo.
gibfahn commentedon Feb 28, 2017
Ahh okay, I can't see that page (I assume you have to be a
nodejsorg owner to see it).addaleax commentedon Apr 17, 2017
Reading through this thread it looks like we have consensus that this is a good idea, and I don’t think there’s much harm in giving the collaborator group write access. Done!