Organize labels into tasks and priorities

[sertansenturk]

Convert the Github labels into Agile tasks Reason Github labels by themselves are not really useful. By mapping them to the (subset of) Agile tasks & priorities, we can simplify the communication and understand the scope of the tickets across people.

Design Remove all labels. Create the labels below. Note that the labels/tasks can change, if we feel they are not adequate.

Type	Name	Color	Created	Created
Task	Bug	Pink	Defect in the code/process etc.	x
Task	Epic	Dark Green	Grouping for tasks with the same agenda	x
Task	Feature	Dark Beige	An enhancement, addition or improvement of the code/process etc.	x
Task	Task	Blue	An ad-hoc/one of process which is done without implementing a feature	x
Task	Spike	Purple	A issue to be researched. The ourcome would answer what are the potential solutions. The solution must not be implemented as part of this ticket but it should be handled as a separate one.	x
Priority	Blocker	Dark Red	An issue which hinders the development (e.g. a major bug or a mistake in evaluation), which requires everything to be dropped until the problem is solved.	x
Priority	Critical	Red	An issue which has to finish to reach the goal of the milestone.	x
Priority	Major	Orange	Something that should be prioritized above others. Typically, impacts the sprint goal directly.	x
Priority	Minor	Green	Something which is not (currently) urgent but could be a nice addition, provided there are resources to work on it.	x

Acceptance Criteria

• The labels should be created properly
• All current tickets must be labeled with the task. All tickets for this sprint must be also labeled with the priority.

[sertansenturk]

@hedonistrh I have created the relevant labels. Can you review the ticket?

[hedonistrh]

When I look for the color of epics. I encountered with this medium post

"the Bug label is deliberately not red (because when you have a large backlog, you need to prioritize aggressively, and this includes acknowledging that not all bugs are urgent/critical)."

However, we are using dark red for the Blocker, so that it is not a problem for us. I think, these labels and colors are appropriate for our project. Also, we have labeled all current tickets. So that, we can close this issue.

[sertansenturk]

@hedonistrh, I think this is a really good suggestion. I have changed the label colors to reflect type & urgency better (e.g. bug is now a non-threatening pink). I have also added another level called Critical between Blocker & Major.

We can later re-define the labels according to their practical usefulness but I think we have a good start for now. I will move the ticket to the "Integration" lane/pipeline. I will simply use that stage to re-label my tickets :)

I see that you have also labeled yours already, good job! I will write a few comments for discussion (not for dictation) in whichever ticket label I don't agree. Likewise, you can also comment on my ticket labels to either understand my reasoning or suggest an alternative. Once we come to a conclusion as a team (remember Sprint 0 is to align on the concepts), I will move this ticket from "integration" to "Closed."

[hedonistrh]

@sertansenturk Thanks for the change and comment. I agree with you, this is really good start. :)

I think, we should be careful about the distinction between major and critical at next steps.

[sertansenturk]

Let's see maybe we will need more, maybe less. Things will settle after a few iterations. :)