Proposal: regular Triage/Planning meetings and dedicated github project boards
Hey folks, I’d like to propose a few ideas to improve the maintainability and efficiency of this project.
Regular Triage / Planning Meetings
Frequency: Once or twice a month
The concept of these meetings would be similar to what @derberg used to run for the generator and spec repo, and what @thulieblack does for the conference repo.
The broader agenda will be:
-
Discuss any issues and talk about what things we are currently working on on the website, and what areas need attention. Maybe if we need to discuss/implement anything, we can talk about it there and create the relevant issue there itself if needed. It will be easier and quicker since we’ll have
more hands (from maintainers side)there on the call. -
The second part would be
triaging. We have so many issues open at the moment, so with more hands in the meeting, it will be really quick totriage, as sometimes we need another opinion and conversations over chat take longer compared to having the same discussion in a meeting. We can quickly triage the bugs/issues and maybe plan things for the website better.
Two Separate GitHub Project Boards
I’d like to propose maintaining two GitHub project boards:
-
Maintainers’ BoardInspired by the generator repo’sMaintainer’s Workboard. This board would track issues that maintainers are responsible for. -
Contributors’ BoardThe idea is that whatever tickets/issues we have triaged or discussed in the above mentioned meeting will be marked astriagedby adding atriagedlabel and moved to that board. We are adding the label to segregate the issues and to easily identify which ones have not been discussed. We will then use the contributors’ board to track the issues ourselves.
For this Contributors’ Board part, yes, it is a rough plan and will be more of an experiment. Let’s see if it turns out to be effective. Please feel free to share your thoughts and input.
Todo:
Can you guys please share feasible dates and times when you are available for the triage/planning meeting? I am thinking of having one this month, but I guess we might have limited availability due to year-end vacations. However, if we do have availability, we can try to have one this month; otherwise, we will start from next year
Please let me know your views: @derberg @akshatnema @anshgoyalevil @sambhavgupta0705 @Mayaleeeee @thulieblack @TRohit20 @bandantonio @devilkiller-ag @vishvamsinh28 @CBID2
Hey @princerajpoot20,
This sounds great! I really like the idea of having regular triage meetings—async discussions can definitely drag on sometimes, so real-time conversations would help a lot. The separate project boards make sense too. Having a clear "triaged" label and a Contributors' board will make it much easier to pick up issues that are ready to work on.
Yes, why not do this month itself — an online meeting works well .
go go please treat me as a backup maintainer though - so not actively working and participating I can join and help when asked in advance though
The separate project boards make sense too. Having a clear "triaged" label and a Contributors' board will make it much easier to pick up issues that are ready to work on.
My thoughts exactly. I'm already overwhelmed with the number of GitHub notifications, so I would vote for a more clear overview of issues and their status without having to check each of them individually.
Hey @princerajpoot20 I 100% support having triage meetings and organizing the work on boards as well!
We can keep it biweekly On Wednesday 21:00 IST