[GH Request] Onboard Ali-Salman29

[Ali-Salman29]

Firm Name

Arbisoft

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

Ali Salman, @Ali-Salman29

User Squad

No response

Core Contributor nomination thread

https://discuss.openedx.org/t/core-contributor-nomination-ali-salman/14339

Start Date

27 December 2024

Urgency

Low (2 weeks)

Special Requests

No response

[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.

[kdmccormick]

CC Onboarding Checklist for Axim On-Call

• Ensure their Salesforce (SF) contact is set up correctly. This step is usually a no-op, but it might require work if, e.g., the new CC recently changed firms and/or they only contributed code outside of the openedx org.
  • The SF contact should exist under their name and GitHub handle. Open edX Individual CLA should be checked. If any of this missing, then have them sign an individual CLA, and then confirm that it is reflected in SF. This may take a couple days.
  • Exactly one of the following scenarios should be true. If not, you will need to talk to both the new CC and a trusted point of contact from the Firm in question to make sure everybody's on the same page. If it's not obvious what to do, talk to the Axim eng team.
    • Employed CC scenario: The onboarding request specifies a Firm Name that matches the SF contact's Account Name, and Contributor Covered Under Entity CLA is checked.
    • Independent CC scenario: The onboarding request specifies "none" / "independent" for Firm Name. The SF contact's Account Name is ... Household, and Contributor Covered Under Entity CLA is unchecked.
  • The SF contact should specify an email address. You will need this for the remaining steps.
• Invite them by email address to the Core Contributor Onboarding course (link requires login) and let them know they need to complete the steps before they’re fully considered a core contributor.
• Confirm with them that they received the course invitation and have successfully accessed the training course.
• Let CC know that they may be required to take the privacy and a11y courses when they become available.
• Verify with Sarina or Axim Legal that the new Core Contributor successfully completed the required legal documents, including both the CLA and the CC Agreement. (Usually Legal will contact the CC Admins about this so you can check in with them if it’s been a little while). Keep the ticket open with status “Blocked” until this is done. Once complete, follow the remaining steps (some may be handled by the CC onboarding course now).
• Invite the CC to the Open edX #core-contributors Slack channel.
• Add them to the overall CC mailing list.
• Add them to the Core Contributors list.
• Back in their Salesforce contact record, go to their Role and add "Core Contributor".
• Ensure they are in the openedx GitHub organization and a member of the openedx-triage
• Send Fox a direct message on Slack with the full name and email address of the new CC. (Fox will contact the new CC explaining the bi-weekly check-ins at Listaflow.com, and provide the CC with a link to the latest sprint retro recap thread in the forums.
• 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).

Additional, 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
• Remind them to add themselves to the relevant shared Slack channel(s) corresponding to their merge accesses (some additional context if you’re curious). Here’s a DM you can copy and use: “For the repositories you have merge access to, please join the Slack room(s) that correspond to your repositories. These rooms are where to coordinate timing on merging breaking or major changes. Keep in mind that 2U runs CI/CD off the tip of master branches, so major changes will impact their site first. It's generally OK to announce in these rooms that you are merging a pr with 24 hour or more notice (eg, I'm merging this tomorrow at 1500 UTC), and engage in discussion with anyone who expresses concern. These rooms are also a good place to ask for a 2U review on critical/breaking change PRs before you get to the merging state.”
• 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.

[kdmccormick]

Congrats on your successful nomination @Ali-Salman29 ! Please complete the Open edX CC onboarding course--you will first need to create an account on the training site using your edly.io email. Let me know if you have any trouble accessing the course. In the future, you may also need to take followup courses an a11y and data privacy, but we don't have those available yet.

Please also complete an individual CLA using the same email address.

[Ali-Salman29]

We don't have edly.io emails. Can we do registration using `abisoft.com` emails?

…

On Fri, Dec 20, 2024 at 11:16 PM Kyle McCormick ***@***.***> wrote: Congrats on your successful nomination @Ali-Salman29 <https://github.com/Ali-Salman29> ! Please complete the Open edX CC onboarding course <https://training.openedx.io/courses/course-v1:OpenedX+NewCC+2024>--you will first need to create an account on the training site using your edly.io email. Let me know if you have any trouble accessing the course. In the future, you may also need to take followup courses an a11y and data privacy, but we don't have those available yet. Please also complete an individual CLA <https://openedx.org/cla> using the same email address. — Reply to this email directly, view it on GitHub <#1333 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVCEYX5PKOMXDGXZVC7WWXT2GSJLXAVCNFSM6AAAAABTUN5NWSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJXG44TENJXGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- The content of this email and attachment(s) are confidential and intended solely for the recipient(s) specified in the message. If you received this email by error, please alert the sender by replying to this email and follow with its deletion, so that we can ensure such an error does not occur in future. If you are not the intended recipient, you are strictly prohibited to use, copy, disseminate or store this email or its attachment(s).

[sarina]

@Ali-Salman29 - please let me know which email address to add you with.

[Ali-Salman29]

@sarina Please use this email.
[email protected]

[sarina]

@Ali-Salman29 you should be all set now.

[Ali-Salman29]

Thanks, it worked.

…

On Mon, Jan 6, 2025 at 1:42 PM Sarina Canelake ***@***.***> wrote: @Ali-Salman29 <https://github.com/Ali-Salman29> you should be all set now. — Reply to this email directly, view it on GitHub <#1333 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVCEYX6KVKXOVBGG3L5Y5S32JJ2ZXAVCNFSM6AAAAABTUN5NWSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZTGAZTINRYGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- The content of this email and attachment(s) are confidential and intended solely for the recipient(s) specified in the message. If you received this email by error, please alert the sender by replying to this email and follow with its deletion, so that we can ensure such an error does not occur in future. If you are not the intended recipient, you are strictly prohibited to use, copy, disseminate or store this email or its attachment(s).