Owner

Grant these only to Axim Engineering employees following an affirmative CC vote for the Coding Contributor role plus org owner rights.

Only Axim Engineering employees may have administrative rights.

Member

CCs generally are already organization members. If they are not, they should be added during CC onboarding.

2U engineers should be added to the organization as part of their onboarding.

Grant to those who want to participate in issues/projects because they’re actively contributing to some part of Open edX. Be liberal with this access--we have unlimited seats in the organization. We do an annual audit to remove inactive contributors from the organization.

Triage

To unblock project & issue participation, the openedx-triage team grants triage access to every repository, to everyone in the organization.

Write to “issues-only” repos

Following a positive CC onboarding , all of these these should be granted to all Coding CCs via the committers team so that they can (a) edit issues other than their own and (b) manage repository milestones.

Non-Coding CCs can not be granted write access to any repository as coding CCs sign a different CC agreement that specifically covers contributions made in commits in git. Individuals seeking write access to non-code repos, such as docs repos and issue-only repos, still need to join the program as a Coding CC.

2U engineers have legacy write access to a variety of repositories, granted via 2u-* teams. To gain new write access, 2U engineers must follow the expansion of responsibilities process, borrowed from the CC program. The rationale and details for this are explained here: https://openedx.atlassian.net/wiki/spaces/COMM/pages/3771793429

These folks are not covered under any CLA, so they cannot commit to the project, code or otherwise.

Write to all other repos

Following a positive CC onboarding or CC rights expansion vote for the particular repo in question, these can be granted to Coding CCs only via:

• one or more committers-$TOPIC teams (PREFERRED) or

• the Coding CC’s own ccp-committer-$USERNAME team.

The sum of a CC’s write access grants should match this page: https://openedx.atlassian.net/wiki/spaces/COMM/pages/3156344833 . If this page doesn’t match reality, then the source of truth is to be found in the result of the votes on the forums--you might have to do some digging.

Non-Coding CCs can not be granted write access to any repository (see above).

Maintain

This grants the ability to modify branch protection rules, so only Axim Engineers who are Coding CCs may be granted it.

Admin

This grants the ability to modify branch protection rules and manage team/user access, so only Axim Engineers who are Coding CCs may be granted it.

Write

Not formally managed. Can be granted by project admins at their discretion.

Not formally managed. Can be granted by project admins at their discretion. Also requires being a member of the organization (see above).

Admin

Not formally managed. Can be granted at Axim’s discretion.

If someone is running a project, they should probably be a Core Contributor. Raise to Axim Engineering if this becomes an issue.

Teams related to managing the Open edX project itself.

Varies depending on need. Sometimes write, sometimes maintain, sometime admin. Follows the principle of least privilege.

The openedx-triage team is special team that grants triage on everything, so no other team should ever need to grant triage or read.

openedx-triage

openedx-release-managers (Grants maintain access to all community release repos.)

openedx-product

Bot accounts that need access to repositories. Generally one bot per team, although bots could be grouped together if it makes sense.

Ideally, the lowest level of access (write/maintain/admin) that the bot needs in order to function, granted on the smallest number of repositories possible.

bot-requirements

bot-semantic-release

cla-checker (needs renaming)

A subset of Coding Core Contributors, organized around an area of expertise or contribution topic.

Grants write access to a set of related repositories.

In some cases, the “set” may be a single repository.

committers (All Coding CCs. Grants write to open-edx-proposals + all issues-only repos.)

committers-analytics

committers-events

Frontend groups:

• committers-frontend

• committers-frontend-mfes

• committers-frontend-base

As opposed to a single frontend repo:

• committers-frontend-build

Temporary: A team containing a single Coding Core Contributor through which their access was granted.

We are moving away from these and towards committers- teams.

Grants write access to a set of repos.

ccp-committer-agrendalath

ccp-committer-regisb

Teams or sub-teams at 2U.

Just write on the specific repositories that the team works on.

2u-edx-legacy (Formerly push-pull-all. Grants write access to ~100 repos to all 2U/edX employees.)

2u-teaching-and-learning

2u-teaching-and-learning-oncall

2u-cosmonauts

2u-enterprise

2u-enterprise-quokkas

Firms/companies/orgs or teams within them.

None

axim-engineering

axim-engineering-oncall

opencraft

opencraft-bebop

Teams related to the working group <GROUPNAME>.

None

wg-build-test-release

wg-build-test-release-chair

Teams in the community that are centered around a shared project, interest, activity, background, etc.

None

interest-performance

This is a legacy team that will be deleted or renamed by Axim in the near future.

Varies