[GH Request] Onboard PavloNetrebchuk

[cmltaWt0]

Firm Name

Raccoon Gang

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

• Pavlo Netrebchuk, @PavloNetrebchuk

User Squad

rg-mobile, openedx-triage

Core Contributor nomination thread

https://discuss.openedx.org/t/cc-nomination-pavlo-netrebchuk/15823

Start Date

1 June 2025

Urgency

Low (2 weeks)

Special Requests

Requesting CC access for Pavlo Netrebchuk with gh username PavloNetrebchuk to repo https://github.com/openedx/openedx-app-android.

Reason: https://discuss.openedx.org/t/cc-nomination-pavlo-netrebchuk/15823

Instructions: Please give access to https://github.com/openedx/openedx-app-android.

[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

• 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.
• Let CC know that they may be required to take the privacy and a11y courses when they become available.
• Confirm with them that they received the course invitation and have successfully accessed the training course and must complete it before continuing onboarding.
• Keep the ticket open with status “Blocked” until the following are done:
  • Verify in Salesforce or GitHub that the new CC signed an Individual CLA
  • Wait for a CC Admin to comment on the ticket affirming that the Core Contributor Agreement has been signed. If it has been a little while, you can check in with cc-program-admins@axim.org or Axim Legal.
    After legal documents are complete:
• 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.
• Let CC know about possible working groups that they can join if not already mentioned by the proposer.
• 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
• Ask them to review the Merge Guidelines for Coding Core Contributors and join the two Slack channels mentioned at the top of the guidelines.
• 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.
• If the new CC is onboarding as a maintainer, direct them to review the Maintainers's Documentation

[ormsbee]

@PavloNetrebchuk:

Please sign the Individual CLA and comment in this ticket once you have signed it.

Also, I've sent you an email invite to the CC onboarding course. Please let me know when you have completed it. You may be required to take additional courses on privacy and a11y when they become available. If you run into any issues, please let me know on this ticket.

[PavloNetrebchuk]

Hello @ormsbee. CLI is not opening.

[ormsbee]

@PavloNetrebchuk: Sorry, I have no idea how that link got mangled. Try this: https://tcril.tfaforms.net/f/individual-cla)