Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Document current usage of labels for somebody-should issues #487
As highlighted in issue #477, we have a lot of labels and it's not clear to newcomers (or lots of oldcomers too I expect...) what they're for.
We should rework/expand the explanation in https://github.com/DoESLiverpool/somebody-should/blob/master/README.md to explain what more of them are, provide links to some shortcut searches as examples of how to use them (e.g. a link to the closed laser-cutter issues as a quick starting point for searching through for last time we replaced the tube)
Some more hints/links to "what a good issue looks like" would also be good - using the SMART criteria mentioned in #477, etc.
It might also be that the README.md isn't the best location for that info. It's the most logical in github terms, as it keeps it in the same repo, but I'm open to suggestions for the best place for it to live (on the wiki or in the handbook being other obvious candidates)
referenced this issue
May 3, 2017
Git has some useful features that could help:
I'm going to try both of these things today and will report back.
Loads more stuff I didn't know about here: https://github.com/tiimgreen/github-cheat-sheet
Tosca is the name of our polargraph. ESPTech relates to ESP8266 stuff. From: Guy Fraser<mailto:firstname.lastname@example.org> Sent: 03 May 2017 13:57 To: DoESLiverpool/somebody-should<mailto:email@example.com> Cc: Subscribed<mailto:firstname.lastname@example.org> Subject: Re: [DoESLiverpool/somebody-should] Document current usage of labels for somebody-should issues (#487) What are the following: * ESP Tech * Room29 * Tosca — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#487 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AMNY0Av9aSIAUiZF5iHaTbb20bNUuPbwks5r2HlqgaJpZM4NPMWV>.
System: Issue Tracker
System: Status Page
May 3, 2017
That's most of them documented: https://github.com/DoESLiverpool/somebody-should/blob/master/CONTRIBUTING.md
Tomorrow I'll try and confirm the full list of machines and their names to ensure there are relevant labels for them, and will then start linking to wiki pages, online docs (eg. vendor sites), any applicable DoES code repositories, and so on - see #488
Unless there's anything major that I missed, this issue can probably be closed?
I've just seen to new labels, (Must DoES, Should DoES, Could DoES) and I'm not convinced they're any clearer than the ones they've replaced. Are they questions?
We've also dropped the 'Holding out for a hero', label out of the numbered system. I think it plays a valuable role, especially in moving along several of our long term projects. I'd like to restore it. Is there a reason not to?
I think that would be good on the Waiting for a hero. Happy for it to fit in language wise, it's the concept that's proved useful. Let's hold on a short while and see if anyone else chips in on it. Thanks.
Thanks as well for the link on the labels. I did read that re-thread before commenting here, and joined in that conversation. I was surprised that it was different than you'd shown in the image below.
As I said, I think it's less obvious, and I'm not sure it's any better. I'd like to make them more obvious, perhaps as you originally suggested in the image? It does though feel like things are running a little hot this evening, and it could quite easily be just me who reads them that way. Let's hold on a day or so, see any comments, and see where we are
Changing the text on the priority labels should be relatively easy, but it must remain in the format required by Huboard:
If we drop Huboard requirement, we'd have more freedom over the format of the labels. Depends how important Huboard is to the team. Personally I think it's useful to see swim lanes of priorities (what Huboard shows) from time to time, but a decision needs to be made as to whether that's more important than clarity of what the labels mean.
As discussed above, I'm planning to change the priority labels to make them a bit better. Specifically:
Note: Closed tickets don't appear in Huboard as far as I can tell.