Styleguide for tagging #39
Description
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:
#EE3F46Problems (high priority):bugsecurityproduction#5EBEFFImprovements (generally iteration on code):enhancementoptimizationrefactor#91CA55Additions (generally new code):feature#CC317CFeedback (some do not involve code):discussionquestioncommunity#FAD8C7Testing (needs to be done or only occurs in):teststaging#FFC274Experience (more artistic):designux#FEF2C0Mindless (can be done during a break):chorelegaldocumentationexamples#D2DAE1Inactive (gets immediately closed):invalidwontfixduplicatedeprecated
These can be attached to the ones above to give more context:
#BFD4F2Platform (can exceptionally be customized to group issues):serverbrowser#FBCA04Pending (stalled by difficulty or external):help wantedin progressepicon hold
We should use something like github-labels to do this automatically and integrate with #23.