Labels on issues

[stevenhwu]

• Here is what I got so far. We can try it a bit and update it later. Any other suggestions?
• There are two main groups of labels I would like to add, Priority-* and Type-*. I suggest we use them in the following way. Once we are happy with these, we should move some of these to wiki.
• The aim is not to labels 100% of the issues. if can can labels 75% of the issues, then I think we are doing pretty well. These unlabeled one can be fonud by no:labels
• Someone who is good with colours please double check them.

Priority-* labels

Priority-Blocker - Complete break DNG, fix it TODAY!
Priority-High - Pretty urgent, do it sooner than later
Priority-Normal - We should address these soon
Priority-Low - Maybe this one can wait

Type-* labels

Type-Interface - I/O, documentations,,...etc
Type-Research - algorithm, statistics,...etc
Type-RE - Release engineering, includes unittest, Jenkins...etc.
Type-Discussion - Maybe no code relate to this, just some idea to discuss.

Existing labels

I leave them un-touch now. Maybe some of them can turn into Type-*

Naming convention

Priority-High vs Priority_High vs Priority:High
This is open to debate. I pick Priority-High because

1. : is used is search label:
2. Cap_Cap looks funny

Others

The following labels might be useful. But I think they might make this more complicated than it has to be at this stage.

Status-in-progress - I am working on this, don't touch without discuss with each other first unless you love merge conflict.
Status-incomplete - Started working on it, but stopped for whatever reason, so not quite there yet
Status-complete - Ready to close, once other people approve.
Type-performance - This will improve the speed significantly, back up by profile
Type-Deprecated
Type-Waiting-for-response

[stevenhwu]

Since github introduce Project function, should we replace Type-** labels with functions? Any suggestions/recommendations?