...
Core Contributors (Applies to all roles, unless indicated otherwise) | 2U & Direct Contractors | Other Contributors | ||
---|---|---|---|---|
ORGANIZATION | 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. | |
REPOSITORY | 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 core-contributor-program-committers group 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: Granting write access to repos in the openedx org | 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:
The sum of a CC’s write access grants should match this page: Core Contributors to the Open edX Project . 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 | Only Axim Engineering employees may have administrative rights | AdminThis 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. | |||
PROJECT (aka BOARDS) | 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. |
...