As the person who chose the colour scheme, I'll try to explain why I did it the way I did. :) If you look at https://github.com/python/cpython/labels you will notice all related labels that have the same prefix are the same colour *unless* there is a reason to make it stand out (e.g. type-security). The colours also try to use appropriate colours to represent whether the label requires attention (e.g. the "needs" labels are yellow as essentially that label represents why that PR has not been merged yet). Finally, I'm enough of a visual learner that I can look at an issue and notice by colour when a label is missing. So out of habit I make sure colours are distinct so I can visually notice when an issue is lacking a certain issue type. But I'm not attached to any of this, so if someone wants to come up with a colour scheme that people can generally agree to I'm fine with changing the colours (I would prefer to avoid changing the label names, though, as that potentially will break bots and scripts, plus I hate labels that are not self-describing as they suck for new people). On Tue, 24 Jul 2018 at 06:56 Emily Morehouse <emilyemorehouse@gmail.com> wrote:
+1 for consistent muted colors
I also think it may be helpful for labels that are manually managed stand out in some way - perhaps a prefix or different shades of a specific color. That way, a core dev could easily visually filter for any labels they may need to change or care more about for a PR.
On Jul 23, 2018 at 7:22 PM, Nick Coghlan <ncoghlan@gmail.com> wrote:
On Tue., 24 Jul. 2018, 5:17 am Carol Willing, <willingc@gmail.com> wrote:
A couple of years ago, I completely agreed that the labels were distracting when we were using them on Jupyter. Over time, I found that they were very helpful for triaging issues and viewing status/next actions when you have a large number of PRs.
One thing that I found helped quite a bit with the Christmas tree effect was to standardize the color scheme to either all black lettering on muted color or all white lettering on bright color.
I think this is going to be the key: choosing a deliberately muted display appearance for any informational labels that are intended primarily as search aids rather than as things to pick up on a quick visual scan of the full PR list.
Cheers, Nick.
_______________________________________________ core-workflow mailing list -- core-workflow@python.org To unsubscribe send an email to core-workflow-leave@python.org https://mail.python.org/mm3/mailman3/lists/core-workflow.python.org/ This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct
_______________________________________________ core-workflow mailing list -- core-workflow@python.org To unsubscribe send an email to core-workflow-leave@python.org https://mail.python.org/mm3/mailman3/lists/core-workflow.python.org/ This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct