1735182 - Request to be added to the Mozilla Services github organization

Status: RESOLVED FIXED

(mozilla.org :: Github: Administration, task)

Description

[Ted Han]

+++ This bug was initially created as a clone of Bug #1638095 +++

Hey data-ops team!

jepstein & I (in my new account capacity) were looking to gain access to the cloudops-infra repo for the work we're doing on Rally.

I'm still knowtheory on github (i think i lost access after my LDAP accounts turned over) and jepstein is conveniently also jepstein on github

Thank you!

Comment 1

[Wesley Dawson [:whd]]

:cknowles, I think these users should have access to the cloudops-infra repo for their rally work. I'm an admin of the cloudops-infra repo but per documentation manager approval is probably warranted. It's not clear to me if that manager would be Rebecca Weiss (:than/:jepstein's manager) or somebody in ITEO (as we own the cost center). Please NI any additional approvals.

As for structure, we sadly don't have a very coherent teams permissions structure for mozilla-services. To match best practices from the mana page, I recommend we do the following:

1. Create a new team "Rally" in the mozilla-services org
2. Add :than and :jepstein to the mozilla-services org
3. Add them to the new Rally team
4. Add read access for team Rally to cloudops-infra

Comment 2

[Chris Knowles [:cknowles]]

So, per org permissions - you have the ability to create teams, and add people to the new teams. and with your admin rights to that repo, you can assign teams to have access.

:than is already a member of the mozilla-services org. So you can assign them to the team.
:jepstein is NOT already a member - so that's where an org admin like me comes into play.

Asking here if :rweiss approves inviting :jepstein to the org. Let me know if there's a concern.

And if you create that team, I'd be happy to add :jepstein there when the time comes. (else, I can create it and add both to it.)

Comment 3

[[e-mail]]

Approved

Comment 4

[Wesley Dawson [:whd]]

So, per org permissions - you have the ability to create teams, and add people to the new teams. and with your admin rights to that repo, you can assign teams to have access.

I'd prefer not to use my org-level permissions to create teams, as I'm trying to follow newer procedures for GH administration. I believe I have teams creation access via two mechanisms:

1. https://github.com/orgs/mozilla-services/teams/people-formerly-known-as-owners, a legacy group which would probably no longer exist
2. via whd-mozilla-owner, a separate GH account that I have but expect to use only in exceptional circumstances

As an admin of cloudops-infra specifically, I would be ok with granting the newly created team r/o access.

Comment 5

[Chris Knowles [:cknowles]]

Ah. I did no checking on your access, simply your earlier comment that you had repo admin access.
I completely agree with not using your owner access to do much.

I've created the Rally team, and added :than to it, and invited :jepstein to the org, and that team.

I've made Rally have read access to the cloudops-infra repo.

Only question I have left - it's always a good idea to have a maintainer for the team - should either(both) be maintainers? or I can add you to the team as a maintainer. Let me know.

Otherwise, the work-work here is done, closing out.

Comment 6

[Wesley Dawson [:whd]]

Only question I have left - it's always a good idea to have a maintainer for the team - should either(both) be maintainers? or I can add you to the team as a maintainer. Let me know.

I think any of :than, :rweiss or :jepstein would be reasonable group maintainers. Thanks for setting this up.

Comment 7

[Chris Knowles [:cknowles]]

You have to be a member to be a maintainer, so made :than and :jepstein maintainers.

Let me know if there's questions.