What do you all think about a project board to organize work that we need to do?

[lwasser]

Friends, I'm getting a bit overwhelmed by all of the repos associated with this project. I want a few things:

1. A project board that we can look at for priority issues across the project
2. project boards for each repo that organize the issues for that specific repo

I'm not sure what is best for us here, but would love to hear what you all think? What I want is a way to jump into the project, remember the issues I started working on, and pick them back up. Right now, I have so many repos on GitHub that it's very hard to keep track of them. What do you all think would work for our team?

We could even have issues tagged as beginner friendly etc?

[JoshuaKGoldberg]

I like the idea of using project boards 🙂. Maybe a straightforward kanban style to start? We did something similar for a couple of other projects I'm on:

• Mocha: 📌 Project Status: Maintenance Reboot mochajs/mocha#5027 -> Mocha
• Yeoman: 📌 Project Status: Maintenance Reboot yeoman/yeoman#1779 -> Maintenance Reboot

Also +1 to tagging issues as good first issue where appropriate. I'd also suggest tagging some as team assigned when it's clear someone on the team should approach it (sparingly).

[lwasser]

I REALLY like that. especially the "what's next", which has no label/ status, and what's being worked on.

And then you are suggesting we reevaluate the labels in this org (I agree!!)
For the org I run (pyOpenSci), I also have a help-wanted board for the entire organization that helps direct folks to issues they could help with: pyOpenSci Help Wanted Project Board. I mostly use it when we run sprints to help people find things to work on.

Should we start by trying out a "maintenance reboot" style board for one of the repos? Maybe the cli repo? And then we can discuss labels here as well?

[JoshuaKGoldberg]

Sounds great to me!

[JimMadge]

I like a project board. I/my teams often use them to guide stand ups or when we sync. It helps to make sure everyone is on the same page about what the priorities are and who is doing what.

Also, the new-style projects on GitHub let you do some nice things like "a table of all tasks assigned to me".

We might want to start fresh with a new board?

[lwasser]

YES. @JimMadge i'm with you. i went to create a board the other day and there are SO MANY new features. I haven't had the energy to organize too much over in the CLI repo yet but i think they would be very helpful there as there is a huge chunk of work we need to do to simply update the dependencies and get a fresh build pushed to npm. (kinda like the docs here but much more complex web of dependencies and CI).

[JimMadge]

Agreed. At least for now we should focus on getting deps up to date and packages released.

We could use milestones or iterations but it might be easier to just exclude feature issues from our board for the moment.