...
Create projects on GitHub as a Kanban board at the openedx organization level, with which we can track all the necessary repositories of the organization. We could group related repositories; like the Slack channels: cc-edx-platform, cc-fronrendfrontend-apps, cc-core-appliocationsapplications, cc-openedx-utils, cc-xblocks. The different filters show all Core Contributor's tasks and the assigned repository.
Issues to which a Core Contributor is assigned and Pull Requests to which a Core Contributor is assigned as a reviewer will be added to the boards. From now on they will be called tickets
The boards will have the following columns:
Backlog: This column will contain all the tickets created and assigned. The automation will place the tickets first in this column.
Next sprint/iteration: Here are the tentative tickets to be done in the next sprint.
For the current sprint/iteration: Here are the tickets that are going to be done or are being done in the current sprint. It is everyone's responsibility to move their tickets to this column. It will serve to give us a general idea of what is being worked on in the current sprint.
In review: Here are the tickets that are currently under review. It is everyone's responsibility to move their tickets to this column.
Blocked: Tickets that are blocked for some reason are listed here. It is everyone's responsibility to move their tickets to this column. It will serve to give us a general idea of the tasks that are blocked and need help.
Done: Here are the tickets that have been completed.
Create a bot that can perform the different automation of the boards:
When an issue is assigned to a Core Contributor, add it to the respective board, in the Backlog column.
When a Core Contributor is assigned as a reviewer on a PR, add it to the respective board, in the Backlog column.
Use labels to differentiate the work done by a person as a Core Contributor from any other work done by the same person outside the program.
...