Content Comparison

...

1. Set the Account Name to the relevant Institution(2U/edx, OpenCraft, etc.)

2. The contributor's first and last name

3. The contributor's GitHub username (case sensitive - it should match what you see on their profile at https://github.com/<username>)

4. Ideally, their email address

5. Locate the field Contributor Covered Under Entity and select it

6. Locate the Role field and add the Entity Contributor role to the user.

...

• First, confirm the provenance of the request, as described in Handling requests from unknown users. If you can’t, then reject the request.

• Add the user to the openedx GitHub organization. Inform the user that their invite has been sent to their GitHub email.

• As part of the invitation, add the user to the groups:

  • @openedx/openedx-triage

  • @openedx/2u-$SQUAD, where $SQUAD is the specific squad they’re on at 2U. The onboarding request needs to specify this. If it doesn’t, ask, and mark the request as blocked.

    @openedx/2u-edx-legacy (was called @openedx/push-pull-all up until ~July 2023)

    We’re no longer adding users to the 2u-edx-legacy group, even if specifically requested

  • For some more context on this system and how it differs from what we did historically, you can see: Granting write access to repos in the openedx org (that’s a public memo, feel free to share).

• Do not grant the user write access to any repos as a part of this process. The CC process should be followed by the engineers once they’ve established a history with the project to get nominated (or self-nominate) for write access to repos.

• Add the user to the CLA database.

• Close the issue once the invitation is sent and the user has been added to the CLA database.

...