The-turing-way: Build Project Board

[alexmorley]

Actions:

• [x] Decide on column labels (e.g. kanban style) - proposal below
• [x] Sort existing issues

[alexmorley]

• New Issues Incoming issues prior to sorting

• Icebox Issues that might be acted upon later. But not soon (e.g. not within a few weeks) and maybe not ever.

• Backlog or Commit Issues that we (as a project) commit to doing but haven't started yet. NB: These issues should concrete and actionable. Issues can be split up to fulfill this requirement if needed.

• In Progress Fairly self explanatory. Use issue comments or a separate branch to update progress.

• Needs Review This will usually be associated with a pull-request. After this the issue either goes to Done or back to In Progress

• Done :tada: There is nothing left to do under this issue. Any remaining points should be filed under a new issue if necessary.

(I think 5 is enough - I don't really count Done as it get's viewed much less often than the rest; but a final addition would be Waiting where an issue is blocked by something else. Otherwise I would put this kind of thing in Backlog.)

[LouiseABowler]

That list sounds good to me @alexmorley - I can see the icebox/backlog division being really useful for keeping the to-do list at a manageable length!

[KirstieJane]

This looks like a good plan to me!

[KirstieJane]

I've done this - ready to close unless anyone says otherwise!

[alexmorley]

Yep. I've put a few issues that we are definitely going to do soon into backlog. We can move more in there as they become more concrete (I made an edit to my column descriptions to reflect that backlogged issues should be concrete and actionable).