| Info |
|---|
These are playbooks for on-call tasks. Feel free to add more! |
...
Set the Account Name to the relevant Institution(2U/edx, OpenCraft, etc.)
The contributor's first and last name
The contributor's GitHub username (case sensitive - it should match what you see on their profile at
https://github.com/<username>)Ideally, their email address
Locate the field Contributor Covered Under Entity and select it
Locate the Role field and add the
Entity Contributorrole to the user.
...
Look them up in Salesforce. Notice which roles they have. Notable roles include.
Core Contributor - a member of the CC program
Entity CLA Coverage Approver - someone who we trust to confirm new members of an entity. In the case of 2U, this means someone that we trust to provide names of new hires, such as a manager or trusted IT personnel.
Known managers and leaders - If the requestor is a known people manager or , staff engineer, or system administrator at 2U, we can accept the request from them. If they are not marked as an Entity CLA Coverage Approver, add this role to their account in Salesforce.
If you’re not sure if they are “known” ask the team or check with @georgebabeyJeremy Ristau.
If they don’t have an entry, ask about them.
Do they claim to be from 2U? Ping @georgebabey Jeremy Ristau and ask if they’re a 2U employee.
For anyone else, just ask in
#axim-engineering.
If their identity can be confirmed, add the requester to Salesforce, as described above. Give them the Entity CLA Coverage Approver role if appropriate.
If not, reject the request.
...
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.
...
For trivial PRs with unresponsive authors, as a rule of thumb if the change is:
less than 10 lines of code,
mostly deletions, or
the only way to do something, or it is just updated facts
it's okay to close it out and still make the change.
In this case, I can see that we tried a couple times to get the CLA, and that's good practice, too.