[GH Request] Onboard Javier Ontiveros

[arbrandes]

Firm Name

Axim

User List (case sensitive!) - Please also include in ticket title

• Javier Ontiveros, @holaontiveros

Core Contributor nomination thread

https://discuss.openedx.org/t/core-contributor-nomination-javier-ontiveros/17773

Email address

No response

Special Requests

As per the nomination thread, in addition to regular write access to frontend-base and frontend-app-instruct, Javier should have limited write access to any frontend-app-* repositories that have a frontend-base branch, in which case he should only be able to write to that particular branch. Currently, these are:

• frontend-app-authn@frontend-base
• frontend-app-account@frontend-base
• frontend-app-profile@frontend-base
• frontend-app-learner-dashboard@frontend-base
• frontend-app-gradebook@frontend-base
• frontend-app-discussions@frontend-base

However, in conversation with @sarina we agreed that trying to implement this limit with GH branch protection rules might become too complicated (if not impossible). Instead, given the wording of the nomination and the fact CCs are by definition trusted, we suggest that Javier simply be given write access to all frontend-app-* repositories via the https://github.com/orgs/openedx/teams/committers-frontend-apps team (in addition to https://github.com/orgs/openedx/teams/committers-frontend-base). He will then be informed (and trusted) to restrict himself as per the nomination.

[github-actions]

Thank you for your report! @openedx/axim-oncall will triage within a business day. Simple requests usually take 2-3 business days to resolve; more complex requests could take longer.

[ormsbee]

CC Onboarding Checklist for Axim On-Call

Initial steps:

• If the CC didn't include their email address in the on-call request, then DM them on Slack to ask them for it.
• Invite them by email address to the Core Contributor Onboarding course (link requires login).
• Ask the CC to complete the course and to ping you when they're done. Let them know that completion of the course is required in order to be a full CC.

Now, mark the ticket Blocked until the following are done:

• An Axim CC Program Administrator has commented on the ticket affirming that the Core Contributor Agreement has been signed. (This will only happen after the CC has signed both the Individual CLA and the Agreement). If it has been a little while, you can check in with cc-program-admins@axim.org or Axim Legal.
• The CC has completed the relevant sections in the onboarding course. You can check this by going to "Student Admin" tab of the onboarding course's instructor dashboard and entering their email into “View a specific learner's grades and progress”.

Once those are done, complete the onboarding:

• Look up the CC's record in Salesforce. Do they have two records? If so: merge them, making sure to maintain all of the important information such as the Individual CLA checkbox, address, phone, personal email, etc. Ask in #axim-engineering if you're having trouble with this.
• Add "Core Contributor" to the Roles section in the CC's Salesforce record.
• Ensure the CC has introduced themselves in the Open edX #core-contributors Slack channel.
• Ensure the CC has added themselves correctly to the Core Contributors list.
• Add them to the overall CC mailing list.
• Let CC know about possible working groups that they can join if not already mentioned by the proposer.
• Ensure they are in the openedx GitHub organization and a member of openedx-triage.
• Ask a Forum Moderator to award the “Core Contributor” badge to the person’s forums profile. (forum moderation rights are listed on the Core Contributors page).
• Share the Core Contributor badge assets using the Google Drive share functionality. Please use the following message: "Dear [CC name], Enclosed find the Core Contributor badge assets. Please refer to your Core Contributor Program Agreement for usage guidelines for these assets."

Final steps, for Coding roles only:

• Add them to the Google group. This is very low traffic, meant primarily for announcements we want to be sure get to all developers.
• Add the CC to the @core-contributor-committers Slack user group
• Ask them to review the Merge Guidelines for Coding Core Contributors and join the two Slack channels mentioned at the top of the guidelines.
• Also add them to the GitHub group committers teams.
• Grant write access to the repositories described in the vote. Do not grant it directly to the user; instead, use existing committers- teams, making new ones as you need to. See this page for details.
• If the new CC is onboarding as a maintainer, direct them to review the Maintainers's Documentation