One approach that I'd like to try out is to use a 2x2 set of labels for priority and effort. For example - priority-high (red) - priority-low (gray) - effort-high (gray) - effort-low (red) The idea is that any issue would be assigned both a priority and effort. Items that are high priority and low effort should be tackled first (hence, two loud, red labels). Items that are low priority and high effort can probably be deferred (hence, two muted, gray labels). Other labels could be more ad-hoc, but it'd be nice to use colors to group labels. For example, a single color might be used to group all labels that point to a specific skimage package. That said, I've always been terrible at labeling issues. (It's right up there with forgetting to add to change-logs.) -Tony On Wed, Feb 4, 2015 at 9:32 PM, Stefan van der Walt <stefanv@berkeley.edu> wrote:

Hi all

Our current set of GitHub labels are not utilized, probably because they don't make much sense i.t.o. our workflow. If you've seen any good usage patterns for labels out there, i.e. ways we can use them to improve our development process, please let me know.

Thanks Stéfan

-- You received this message because you are subscribed to the Google Groups "scikit-image" group. To unsubscribe from this group and stop receiving emails from it, send an email to scikit-image+unsubscribe@googlegroups.com. For more options, visit https://groups.google.com/d/optout.