Discovery: How to get a global list of CCs to use for automation purposes

[itsjeyd]

Epic

#134: Improving OSPR Management

Story

"As a developer, I want to figure out a way to programmatically obtain a global, up-to-date list of core contributors to the Open edX project, so that I can implement support for automatically adding the core contributor label to relevant OSPRs in a future task."

Full description

This discovery is the first step towards automating the process of reliably labeling OSPRs coming from core contributors.

See Automating manual OSPR management tasks > Managing labels section of the proposal for Improving OSPR Management from this year's Summit to Enhance the Core Contributor Experience for details:

The OSPR management process involves a number of tasks that OSPR managers currently perform manually, and that could be automated to free up time for processing more PRs in the time that OSPR managers have available for triage. These tasks include:

<...>

• Setting the core contributor label upon PR creation.
  * This will require getting a global list of CCs* - even if someone is not a coding CC for one or more repos, they could still open a PR - e.g. from the Core Contributors to the Open edX Project wiki page, and checking whether the PR author is on that list.

Completion criteria

• Perform a technical discovery on how to programmatically obtain an up-to-date list of CCs.
  • As the ultimate goal is to automate the process of adding the core contributor label to relevant OSPRs, it must be possible to integrate the suggested approach with existing code/automations that operate on pull requests against repos belonging to the openedx organization on GitHub.
• Put your findings in a Google document.
• Get feedback from Axim on the approach and make adjustments as necessary.
• Create a follow-up ticket for implementing the automation described above.

Relevant repositories

• https://github.com/openedx/openedx-webhooks
• Maybe others (?)

[xitij2000]

I've composed a document with my recommended approach here: https://docs.google.com/document/d/1bJX8TgFeS32fs55DIf8wcIRjFFLcDPZUw_L5YY4Iapg/edit?tab=t.0
I would love to get feedback on the approach and its feasibility.

[itsjeyd]

@feanil @sarina @kdmccormick @mphilbrick211

⬆ Please have a look at @xitij2000's discovery document when you get a minute ⬆

[mphilbrick211]

@feanil @sarina @kdmccormick @mphilbrick211

⬆ Please have a look at @xitij2000's discovery document when you get a minute ⬆

Looks good to me, @itsjeyd!

[itsjeyd]

Great, thanks for checking @mphilbrick211!

[feanil]

I took a look and provided an alternate suggestion, thanks for leading/driving this.

[itsjeyd]

@feanil Thanks!

[antoviaque]

@itsjeyd @xitij2000 Did you get all the review comments and replies you needed to move forward with a plan, or are there still some blockers?

[itsjeyd]

@antoviaque I think we're good. We have #155 as a follow-up ticket, and concluded the conversations with Feanil and Sarina on the discovery document. At least that's my impression/understanding -- I checked in with @xitij2000 about it here. (He's off this week so it will be a few days until he'll be able to confirm.)