Hello everyone, do you have any thoughts on this? I'll go ahead and implement our proposal on Friday18th unless I hear otherwise. Best, Raff On Fri, Dec 4, 2015 at 7:49 PM, Raffaele Viglianti < raffaeleviglianti@gmail.com> wrote:
Dear all,
Elli and I spent some time this morning going through the labels on the TEI repository and discussed a new, simpler, system for organizing our tickets.
Here is a spreadsheet with current labels and their proposed new name: https://docs.google.com/spreadsheets/d/1VhBYft_85F6x8J0YpGvqn-ZfIHbXqk9j8QV_...
We propose to have 4 higher level label categories: *component* or *tool*, *type*, *priority*, and *status. *
When creating a new issue, one label from each category should be chosen.
For example a new ticket about a badly misguiding example for the the "div" element would probably get these labels:
"Component: Core schema" "Type: Bug" "Priority: High" "Status: Needs Discussion"
There are a couple of extra labels that don't fit this system: - "sf-automigrated": identifies tickets migrated from SF. We suggest to keep it. - "SIG": identifies tickets about SIG organization (maybe we need a category for less technical discussions, "meta"?).
Then we have a couple of specific questions for you: - Should we keep labels specific to each chapter in the guidelines? (e.g. MS, ND, PH, etc). We think they should go away. But if we keep them we can get group them under "Component: Guidelines", e.g. "Component: Guidelines: MS". - "sf_creator-*" tickets were introduced to facilitate finding migrated tickets by their original SF creator. Since that information is also recorded in the text of the ticket, we think they should go away. Thoughts?
Many thanks for your comments - after we make some decisions here, we will also check labels in the Spreadsheets repository and implement a similar system.
Best, Raff