Styleguide for tagging #39

For a more productive organisation, we should probably follow this simple styleguide for tagging issues and avoid creating new tags.

Here's what we should use

For clarity, use only one of these labels! if you feel that you need to use more, your issue might not be specific enough:

• #EE3F46 Problems (high priority): bug security production
• #5EBEFF Improvements (generally iteration on code): enhancement optimization refactor
• #91CA55 Additions (generally new code): feature
• #CC317C Feedback (some do not involve code): discussion question community
• #FAD8C7 Testing (needs to be done or only occurs in): test staging
• #FFC274 Experience (more artistic): design ux
• #FEF2C0 Mindless (can be done during a break): chore legal documentation examples
• #D2DAE1 Inactive (gets immediately closed): invalid wontfix duplicate deprecated

These can be attached to the ones above to give more context:

• #BFD4F2 Platform (can exceptionally be customized to group issues): server browser
• #FBCA04 Pending (stalled by difficulty or external): help wanted in progress epic on hold

We should use something like github-labels to do this automatically and integrate with #23.