Suggestion: let's try to keep the labels short. I think that will make it easier to see what we have as the number of labels increases, and will make the labels a bit less visually overwhelming. (It looks like existing labels can be edited in the Manage Labels function, but I was afraid to try for fear I would mess something up.)
e.g.,
mac-osx -> OSX or Mac
ms-windows -> Win or MS
sourceforge-import -> SF
I have been marking feature requests from the old SF as "wishlist"; I hope that is consistent with the intentions of whoever made the label.
Eric
I am fine with shortening them. I have also interpreated wishlist to mean that.
I also want to bring in lessons I learned when participating in
Ubuntu's BugSquad. For the "triaging" process, the report needs to be
confirmed. Whenever we confirm a bug, we can tag it as such. If more
information is needed or if you don't have time to confirm, you can
tag it as "need_confirm". The tags are updated as progress is made.
There is also "ongoing" which I take to mean that the report has been
assigned and actively worked on.
Any others we want (or changes to the idea)?
Ben Root
ยทยทยท
On Tuesday, June 21, 2011, Eric Firing <efiring@...229...> wrote:
Suggestion: let's try to keep the labels short. I think that will make
it easier to see what we have as the number of labels increases, and
will make the labels a bit less visually overwhelming. (It looks like
existing labels can be edited in the Manage Labels function, but I was
afraid to try for fear I would mess something up.)
e.g.,
mac-osx -> OSX or Mac
ms-windows -> Win or MS
sourceforge-import -> SF
I have been marking feature requests from the old SF as "wishlist"; I
hope that is consistent with the intentions of whoever made the label.
Eric