Magma's GitHub Teams #6301
hcgatewood
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Magma's GitHub Teams
The
magma
org currently has 27 teams, whereThis Discussion describes a path toward a common pattern for generating and naming teams in the
magma
org, assigning members and permissions according to the teams, and a resulting changelist.Conventions
Teams
We will make some use of GitHub's support for nested teams, where permissions and mentions are forwarded top-down.
We will use 4 categories of teams, where the team's prefix indicates its category
repo-
for repo-scoped permissions, e.g.repo-magma-admin
for Admin permissions to themagma/magma
repoteam-
for organizing contributors according to external teams, e.g.team-facebook
governance-
for organizing contributors according to their role in Magma governance, e.g.governance-tsc
misc-
for miscellaneous categories, e.g.misc-bots
The misc category should be used as sparingly as possible.
Permissions
Permissions should no longer be assigned on a per-user basis. Instead, users should be assigned to the set of teams that results in the necessary permissions. E.g. if a devops contributor needs admin access to the
magma/magma
repo, they should be added to therepo-magma-admin
team. cc @tmdzkChangelist
Repos
How much of a hassle would it be to rename
magma-website
towebsite
? There's no reason to include themagma-
prefix, and it will make some of the team names a little cleaner. cc @PARittergovernance
Governance
,community
community
(merged intogovernance
)foundation
(unused? cc @PARitter)magma-fb-only
(unused)Teams
Previous
ALTEN Calsoft Labs
BOTS
Deutsche Telekom
Domain Proxy Developers
Facebook
FreedomFi
Linux Foundation
Magma Admin
Magma Maintainers
OpenAirInterface
OpenInfraFoundation
Radisys
Rice University
Shoelacewireless
Unidentified members
Wavelabs
ci-approvers
ci-infra
community
cwf-approvers
domain-proxy-admin
entire-org
feg-approvers
magma-team
nms-approvers
orc8r-approvers
web
New (note that indented teams are nested under their higher-level team)
governance-tsc
misc-bots
repo-domain-proxy-admin
repo-domain-proxy-write
repo-governance-admin
repo-magma-admin
repo-magma-maintain
(from:Magma Maintainers
,entire-org
and its functionality)approvers-*
(see Proposed `approvers-*` teams for PR reviews #6218, @themarwhal will handle these)repo-magma-website-admin
repo-magma-write
team-all
team-unidentified
(from:Unidentified members
)team-calsoft
team-deutschetelekom
team-facebook
team-freedomfi
team-lf
team-oai
team-oif
team-radisys
team-riceuniversity
team-shoelacewireless
team-wavelabs
The one quirk here is @magma/entire-org has special functionality for the CODEOWNERS file, so we'll need to handle this before deleting the
entire-org
team.Beta Was this translation helpful? Give feedback.
All reactions