Issues labeling

[ivanlanin]

I like the way we label issues with color. It's easier to read. I would like to propose a shorter labels/tags. We try to make the label in only one word with the shortest option, e.g. ODT, Pull, Bug, Doc, etc.

I would also request one label, i.e. "Answered", to label issues that we have answered and waiting for response. Alternative: "Hold".

What do you think, guys?

cc: @Progi1984 @gabrielbull @RomanSyroeshko @bskrtich

[ghost]

I don't have any permissions which allow me label issues. :)

[ivanlanin]

I mean, do you think the label helps us to identify issues?

[ghost]

Label appears after preliminary assessment of the certain issue. Labels are usually used in reporting and planning. For example, you have a guy who deals with performance issues. Then, if you label some issues with "Performance", that guy will know that this is his task. There are a lot of applications for labels. I mean, we should have good understanding of what we using labels for, otherwise it's a waste of time.

I don't see why I need label on some issue now. Perhaps, this is useful for project owner, @Progi1984. Who knows? :)

[ivanlanin]

phpDocumentor2 might be a good example for my idea.

[ghost]

Perhaps, I could share some thoughts if I knew the problem you want to resolve with labeling and the results you want to achieve. Could you please clarify what are you worried with, why do you want to do this?

[ivanlanin]

I'm worried we missed critical issues (like bugs) while, on the other hand, we have some issues that we have either answered or decided to put later. I want to be able to use our list of issues more effectively.

Anyway, I guess we should worry about it too much now since our list hasn't contains too much items. Thanks for discussing this. I'll close it for now and (perhaps) bring it out later once we have more items on our list of issues :)