Requesting GitHub membership to the mozilla-sre-deploy org for MozillaSocial - Committers team
Categories
(mozilla.org :: Github: Administration, task)
Tracking
(Not tracked)
People
(Reporter: hluhano, Assigned: cknowles)
References
Details
I've read https://wiki.mozilla.org/GitHub#Team_Maintainers_.26_Project_Leads, and need help adding a contributor to the org:
Name: Herraj Luhano
Mozilla Email: hluhano@mozilla.com
Github Profile link: https://github.com/Herraj
Github Team(s) REQUIRED: https://github.com/orgs/mozilla-sre-deploy/teams/everyone
I would like to request read access to mozilla-sre-deploy
org for the MozillaSocial/Committers team.
I'm not sure if the team "everyone" is correct. Please let me know if anything else is required!
Comment 1•2 years ago
|
||
Chiming in here in support of read access -- we'd like for devs to be able to track deploy access. Write access not needed.
Comment 2•2 years ago
|
||
Upon reflection, I realize that the Committers
group in MozillaSocial is not going to be an entity in mozilla-sre-deploy
. I think the underlying request -- being able to see deploy status -- is sound, but I imagine we'll need a different way to go about it.
Reporter | ||
Updated•2 years ago
|
Comment 3•2 years ago
|
||
Sorry for the delay. Chris is out on PTO and I've fallen behind on tickets.
We can create the group and populate it initially, but we don't have any easy way of syncing them (so it's on you).
We'll brainstorm on other ideas.
Comment 4•2 years ago
|
||
That can work, Andrew! Thanks!
Assignee | ||
Comment 5•2 years ago
|
||
efixler: is there someone you're working with in the mozilla-sre-deploy org that led you to this approach? (adding 44 people to the org from the mozillasocial/committers team) - Not saying it's a bad approach, just asking so I can get confirmation that this influx won't surprise/worry them.
Comment 6•2 years ago
|
||
:hluhano is driving this ticket, I just dropped in to support, because we do want deploy visibility. Herraj is out today for Canadian Thanksgiving. I'm honestly not sure.
FWIW :cvalaas is likely the key SRE stakeholder.
Assignee | ||
Comment 7•2 years ago
|
||
Since the SRE's are the ones in control of that org - cc'ing in cvalaas for "What's the best approach to get the 44ish people in the mozilla social committers team visibility to the deploys they care about in the mozilla-sre-deploy org?"
Comment 8•2 years ago
|
||
It would be great to have a team of "all" (however they want that defined) the moso stakeholders to have viz into the mozilla-sre-deploy org!
Comment 9•2 years ago
•
|
||
(And once they're added, I presume I can assign further (beyond read) access on a per-repo basis ... ?)
Assignee | ||
Comment 10•2 years ago
|
||
Well, it's best to define a team(s) and add them to repos based on the teams.
So, :efixler, :hluhano - who all NEEDS this access to the mozilla-sre-deploy org from mozilla-social? (if the answer is "EVERYONE in committers", that's fine - I just want to make sure I ask.)
:cvalaas - Happy to add them to whatever team(s) you want - but as you note, once they're members of the org, team maintainers can add them to teams, and repo admins can add them to repos.
Comment 11•2 years ago
|
||
Great! Having all committers in one team works just fine for me. Or no teams and we can define that ourselves. No problem!
Assignee | ||
Comment 12•2 years ago
|
||
And a note for the mozillasocial folk - you'll probably want to adjust your onboarding documentation to include the access to the mozilla-sre-deploy org (and what I'm currently thinking would be "MozillaSocial-Committers" team - I'm open to suggestions) in that org, in addition to the mozillasocial access you currently do.
Once I hear from the MozillaSocial folk, we can start looking at invites.
Reporter | ||
Comment 13•2 years ago
|
||
Hi folks, I'm back today and have caught up with the thread. To answer to :cknowles question, everyone in the MozillaSocial/Committers team would need access.
And I agree with all of you here. Having a "MozillaSocial-Committers" team in the mozilla-sre-deploy org makes sense to me. Please let me know if anything else is required.
Assignee | ||
Comment 14•2 years ago
|
||
Alright, I think we've got enough to move on this. I'll get these out over the next day.
Note, I'll be sending out 44 invites to the phonebook group, and 44 invites to the github group - if people decide not to engage, they won't have membership. We'll make every effort to get them in - but this team is likely to be a subset of the full committers team.
And I do strongly recommend that going forward for github onboarding onto this project, that you modify any documentation to include the mozilla-sre-deploy and "MozillaSocial-Committers" team to the needed access.
I will update once things are sent.
Let me know if you have questions/concerns.
Assignee | ||
Comment 15•2 years ago
|
||
Alright, Directions are sent, as are the invites for all the folk that weren't already in the mozilla-sre-deploy org.
Please let me know if there are any questions or problems.
Assignee | ||
Updated•2 years ago
|
Description
•