[GH Request] Onboard John Swope jswope00

[sarina]

Firm Name

Axim

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

John Swope @jswope00

• edx-documentation
• docs.openedx.org
• openedx-demo-course
• openedx-demo-course-new

Can add to https://github.com/orgs/openedx/teams/openedx-demo-course-maintainers and grant that group access to both the demo courses

If there's not already a documentors group, we should create one for the two docs repos

User Squad

No response

Start Date

9 Nov 2023

Urgency

Low (2 weeks)

Special Requests

Nomination thread: https://discuss.openedx.org/t/core-contributor-nomination-john-swope/11514/12

[openedx-workflow-automation]

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.

[sarina]

Coding CC Onboarding Checklist for Axim On-Call

• Invite them 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 (if you don’t know their email address, comment on the GH ticket and consider it blocked until you get that info).
• Confirm with them that they received the course invitation and have successfully accessed the training course.
• Set up access for CC in privacy & a11y courses (can skip for now, but let CC know that they may be upcoming).
• 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 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.”
• Add them to the Google group. This is very low traffic, meant primarily for announcements we want to be sure get to all developers. Also add them to the overall CC group.
• Add them to the Core Contributors list.
• Look up their record in Salesforce and grant them the Core Contributor role.
• Create a new GitHub team with the name: CCP Committer: {Contributor's GitHub user}. Add repositories to the team at the appropriate access levels, as specified by the CC vote.
• Is this user in the GitHub org?
  • If so: Add them to the teams CCP Committer: {Contributor's GitHub user}`` and openedx-triage`.
  • If not: invite them to the GitHub org, including those two teams in the invite. They will need to confirm their invite via email.
• Send Dean a direct message on Slack with the full name and email address of the new CC. (Dean will send the new CC an email explaining the bi-weekly check-ins at Listaflow.com, the report spreadsheet, and provide the CC with a link to the latest sprint retro recap thread in the forums. Dean will contact Fox Piacenti to add the new CC to the correct Listaflow list, and ensure the CC has successfully created an account.)
• 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).

[sarina]

@jswope00 can you confirm you've received an invite to the intro course?

[jswope00]

@sarina I don't think I have no :/

[sarina]

I just sent another invite to your `@c***.me` email address. If you don't see it, try logging in to training.openedx.org and it should be on your dashboard.

[jswope00]

@sarina I did find both invites in my spam. Will start.

[sarina]

Hi @jswope00 - I have finished your onboarding but there is one more step for you. Could you please visit https://app.listaflow.com/forgot-password to set up their password? Thank you!