Improving OSPR Management

[cassiezamparini]

• See proposal
• Tasks from this epic

[antoviaque]

@xitij2000 @itsjeyd During the last meeting of the coordination working group, we set as a goal to have a plan for each of the approved proposals from the summit. It's likely going to be tricky to get things done with Christmas, but what would be your plan & timeline beyond that?

[itsjeyd]

@antoviaque This sprint I spent some time reviewing the scope of the proposal and scheduling tickets for implementing it. There are three different buckets of work, if you will:

1. Documentation updates
   • Tickets ready to be worked on
   • Tentative completion date: Feb 28 2025
2. Implementation of features and processes that are unique to this proposal
   • Tickets ready to be worked on
   • Tentative completion date: Apr 30 2025
3. Implementation of features and processes that overlap with Single Responsible Person Principle (for bugs & PRs) #135 and Improve review process by using CODEOWNERS #140 fully or partially.
   • No tickets yet
   • Next step will be to have a conversation with @bradenmacdonald and @navinkarkera to see how we can combine the suggested approaches from the three proposals.

CC @xitij2000 @cassiezamparini

[itsjeyd]

FYI @mphilbrick211 @antoviaque

Status update

Here is a comprehensive list of tickets we have scheduled for the new year:

Documentation updates

• Update documentation about PRs needing product review (details)
• Improve documentation on how to find OSPRs to review (details)
• Simplify the OSPR welcome message (details)

Implementation of features and processes that are unique to this proposal

• Create prototype app to list all core contributors for a repo (details)
• Discovery: How to get a global list of CCs to use for automation purposes (details)
• Automatically remove obsolete labels from OSPRs upon merge/close (details)
• Automatically populate metadata on Contributions board (details)

Implementation of features and processes that overlap with other proposals

• Define workflow for interactive PR bot that enacts Single Responsible Person Principle (details)

---

@cassiezamparini I would love to turn those into actual GitHub tickets but wasn't sure where to put them?

---

CC @xitij2000 @bradenmacdonald @navinkarkera

[cassiezamparini]

I would love to turn those into actual GitHub tickets but wasn't sure where to put them?

@itsjeyd Hmmm, a good question. I'm going to defer this to @antoviaque and @jalondonot. What is best practice here? I don't want the issues to get confused with our WG issues, so perhaps this needs to be a separate project?

[antoviaque]

@cassiezamparini What would be the issue with having the tickets as part of the working group? They are effectively subtasks or split tasks from one already on the board, no?

[cassiezamparini]

@antoviaque I just thought the board could get very cluttered: https://github.com/orgs/openedx/projects/62/views/1. But I guess it would be a good way to keep tabs on the projects as we could sift through the tickets in our meetings...

[antoviaque]

@cassiezamparini True, that could happen if we overdid it - in which case we might be able to address it with different views of the board, depending on the granularity we want during the meeting?

[cassiezamparini]

@antoviaque Makes sense.

FYI. @itsjeyd You can create issues on the Contributors Coordination Topics board.

[itsjeyd]

@cassiezamparini Sounds good, I'll do that. Thanks to you and @antoviaque for clarifying 👍

[itsjeyd]

Tickets are up on the board now:

• Update documentation about PRs needing product review #145
• Improve documentation on how to find OSPRs to review #146
• Simplify the OSPR welcome message #147
• Create prototype app to list all core contributors for a repo #148
• Discovery: How to get a global list of CCs to use for automation purposes #149
• Automatically remove obsolete labels from OSPRs upon merge/close #150
• Automatically populate metadata on Contributions board #151
• Define workflow for interactive PR bot that enacts Single Responsible Person Principle #152

[antoviaque]

@cassiezamparini @itsjeyd

I just thought the board could get very cluttered: https://github.com/orgs/openedx/projects/62/views/1

Btw, to add explicit sub-tasks without cluttering, maybe github officially supporting those will help?

https://github.blog/changelog/2025-01-13-evolving-github-issues-public-preview/#break-down-and-nest-issues-with-sub-issues

[itsjeyd]

@antoviaque Oh, awesome! Such a timely move from GitHub to be adding this functionality now 😎

I'll try it out.

CC @cassiezamparini

[itsjeyd]

@antoviaque @cassiezamparini It looks like the sub-issues still show up as standalone tickets on the board. But either way, having a list of all the issues that belong to this proposal attached to the first post is probably still going to be helpful.

[antoviaque]

@itsjeyd It's probably a good thing they can show up on the board - maybe they can be filtered out from specific board though? I haven't looked in detail, so I am just speculating.

[antoviaque]

-snip- -- I was wrong.

[itsjeyd]

@antoviaque Your hunch was right, there is a way to enable filtering, by setting the Type field of each sub-issue to Task. Then you can say -type:Task on the board and it will hide the sub-issues.

CC @cassiezamparini

[itsjeyd]

@cassiezamparini Can I ask you to please add this filter to the ticket description:

Tasks from this epic

[cassiezamparini]

Done @itsjeyd 😄

[itsjeyd]

Great, thanks @cassiezamparini 🚀