Admin: Refine CDP Roadmap Project Board

[hawkticehurst]

As we're setting up this repo I'd love some help/discussion regarding how we structure the Project Board of this repo to best suit our needs.

The repo is loosely modeled off of the GitHub public roadmap and can be referenced as we figure out what we want to do.

In particular, how we organize the project board would be a nice first topic. GitHub organizes its roadmap by quarter, but since we operate more loosely I've temporarily included "To Do", "In Progress", and "Done" columns.

[evamaxfield]

I think having ours just be simpler buckets makes sense. I would like to make a request / comment, can we have the columns as:

"Ideas", "To Do", "In Progress", "Done"?

I think there is value in having a bucket that is in the "planning" phase basically.

[hawkticehurst]

Oh yeah, great idea. Consider it done.

[evamaxfield]

I changed Ideas to Planning as we now have an idea label I didn't want to get add confusion as to the stages of the process.

So far after transferring issues over to here I am already happy to see this general progress and planning.

It would be interesting if we had labels or some system added that @sarahjliu mentioned for RICE? Like for issues that move from Planning to To Do they specifically have to be checked / RICE information be added?

[evamaxfield]

Do things like CouncilDataProject/cdp-backend#167 belong here. I personally belive so but how should we tag them and such?

[hawkticehurst]

I think that makes sense this issue spans multiple repos and that was the line in the sand we drew for ourselves last night.

[hawkticehurst]

And of course, all the minor sub-issues that will live under the umbrella of this bigger goal can live within the respective repos that those sub-issues are related to.

[sarahjliu]

I thought about this a bit more and I do like being able to see the status of each overarching project in a single board but I also think it would be very helpful to have another board with a consolidated view to see all the smaller tasks for each issue instead of having to go into each respective repo to view each task.

After some brief searching, it doesn't seem like there is a way to have a item hierarchy (like epic -> user story -> task) with github boards so we would either need to use the Zenhub extension, use the existing issue checklist, or create the sub-tasks as issues + add the overarching project as a tag. Thoughts on going with the third option and having 2 project boards (our current public one with the high level overview/status of each project + a more detailed one to see the status of the sub-tasks)?

[evamaxfield]

Yea I was thinking basically: "when a project moves into todo, we convert all the tasks in the issue into github issues in the associated repos"

I do think we should stay with the tasking stuff. GitHub seems to be heading in that direction with the GitHub Issue beta (which hopefully we get soon)!

Since this is the "large public roadmap" I think it's fine to have this one as the main one and then a project for each issue here that shows the progress of the individual subtasks.