Automatically populate metadata on Contributions board

[itsjeyd]

Epic

#134: Improving OSPR Management

Story

"As an OSPR manager, I want certain types of OSPR metadata to be set automatically on the Contributions board, so that I don't have to do it manually."

Full description

See Automating manual OSPR management tasks > Managing metadata for the Contributions board 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:

<...>

• Retrieving the creation date of an OSPR from GitHub to populate the Date opened field. Ideally, this would also be done for platform roadmap tickets.
• Retrieving maintainer info from catalog-info.yaml, just like we are already doing for the OSPR welcome message, and using it to populate the Repo Owner / Owning Team field.
  • For repos maintained by specific individuals, we suggest to include both their full name (if available) and their GitHub handle, e.g. Brian Mesick (@bmtcril).
  • As a side note, "Repo Owner / Owning Team" terminology is outdated at this point. "Maintainer(s)" or "Maintaining Team(s)" would be more appropriate, as it would better reflect current practices. We should consider renaming the field.

Completion criteria

• Implement support for automatically populating the Date opened and Repo Owner / Owning Team fields with relevant data as described above.

  • See openedx-webhooks#233, the PR from BB-8799, for details on how to retrieve maintainer info from a repo's catalog-info.yaml.

• If the code for this feature will live in the https://github.com/openedx/openedx-webhooks repo (TBC as part of this ticket), ping Feanil for review on the PR(s) that you create. (Most likely, he will take care of testing and deploying the changes once they merge.)

• Create a follow-up ticket for the next step from the same section of the Improving OSPR Management proposal:

  ... introducing a Date merged/closed field and automatically it with data from GitHub as well.

  This might help us identify repositories whose time-to-merge is particularly high.

Relevant repositories

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

[itsjeyd]

PR: openedx/openedx-webhooks#327