Issue tagging about recastnavigation HOT 5 CLOSED

I think the real benefit of labels is just being able to see quickly what the status of everything is at a high level. At work, we have a pretty extensive issue labeling system that works well for us (labeling sprints, components, severity, etc..) but we also have an order of magnitude more issues than recast does. 😛 I'd say, let's stick with something lightweight for now until we find the need to get more fine-grained to stay organized. I like the Robin article's list, specifically how similar concerns are color-coordinated, though I think about 1/3 of those tags are relevant to us. Want to just go with the relevant labels from their list for now?

from recastnavigation.

I like the Programmers categorization better for it has type in each of its items - something that helps a lot to keep an eye on and wont require to explain to every newcomer what each color stands for. It's clear and can be colored just as well by category.

from recastnavigation.

I've added a few labels from the robin link that seem immediately relevant. I think we should follow that style (color coding categories of labels) in the future, but we probably don't need to get much more crazy with labeling right now. Here's my take on their definitions:

I'm going to close this issue for now. If we feel we need anything more than this in the future, we can re-open it.

from recastnavigation.

Thanks Graham; I just realised I opened this then went away for 5 days - sorry! I agree, that cut-down list looks good. I've just added 'documentation' too which the robin link doesn't mention, but I think is useful.

from recastnavigation.

Awesome. Documentation is another good one. 😄

from recastnavigation.