Use labels and milestones to organise development issues

[seabbs]

As per the title it would be good to overall our issues list to use labels based on the type of work and organise these into milestones (ideally with an associated kanban board) for planning purposes. This should then lead to some docs or an issue template so that all new issues are also organised in this way.

[athowes]

I have added an "infrastructure" tag with the same hex as in epinowcast.

[athowes]

Perhaps we can talk about this next meeting @seabbs @kgostic @seabbs. That is generating milestones and possibly setting up a kanban board.

[kgostic]

I did create one milestone, but have not had the time to sort. Let's talk next week! This also reminds me I need to schedule a recurring meeting.

[athowes]

I think I'm blocked on making this kanban board by epinowcast community permissions.

I can create a "project" on my own account:

But for that, I can only add issues from repos that I am the owner of.

If I go to "Projects" direct from epinowcast/epidist then I have:

And I can't create a new project.

Let me know if you have a good way to fix this / any workarounds @seabbs.

[athowes]

I do now have this working. But I am not currently using it.

Perhaps next meeting we can move towards the workflow being more that we agree on issues for that week and organise them in the kanban board. Or we use the silly dinosaur names.

Perhaps part of me thinks this is overkill and it's going OK organising the work to do more informally. Might be different if the development was occuring across more different people.

[seabbs]

I don't like the sprint names or approach and am okay with it being fairly ad-hoc for now. I think post this week/next though we might want to start thinking about release numbers and hence milestones etc as we look to make Dev more formal. I'm flexible as to when we do that though (i.e could keep going for a month or more as is)

[athowes]

Closing this as covered by #233.