Document current usage of labels for somebody-should issues #487

Closed
amcewen opened this Issue May 3, 2017 · 15 comments

Comments

Projects
None yet
7 participants
@amcewen
Member

amcewen commented May 3, 2017

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)

@aubergine10

This comment has been minimized.

Show comment
Hide comment
@aubergine10

aubergine10 May 3, 2017

Contributor

In addition, it would be useful to indicate which labels affect external systems.

Contributor

aubergine10 commented May 3, 2017

In addition, it would be useful to indicate which labels affect external systems.

@aubergine10

This comment has been minimized.

Show comment
Hide comment
@aubergine10

aubergine10 May 3, 2017

Contributor

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

Contributor

aubergine10 commented 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

@aubergine10 aubergine10 self-assigned this May 3, 2017

@aubergine10

This comment has been minimized.

Show comment
Hide comment
@aubergine10

aubergine10 May 3, 2017

Contributor

So far so good:

region capture 12

I'll start chipping away at the labels stuff now.

Contributor

aubergine10 commented May 3, 2017

So far so good:

region capture 12

I'll start chipping away at the labels stuff now.

@aubergine10

This comment has been minimized.

Show comment
Hide comment
@aubergine10

aubergine10 May 3, 2017

Contributor

What are the following:

  • ESP Tech
  • Room29
  • Tosca
  • Violet
  • Rose
Contributor

aubergine10 commented May 3, 2017

What are the following:

  • ESP Tech
  • Room29
  • Tosca
  • Violet
  • Rose
@jackie1050

This comment has been minimized.

Show comment
Hide comment
@jackie1050

jackie1050 May 3, 2017

@johnmckerrell

This comment has been minimized.

Show comment
Hide comment
@johnmckerrell

johnmckerrell May 3, 2017

Member

Room 29 is the room off the main room that contains 4 of the permanent desks and is separately lockable (And was also the name of the room that I, @amcewen @osfameron and Ross Jones used to share before we started DoES Liverpool).

Member

johnmckerrell commented May 3, 2017

Room 29 is the room off the main room that contains 4 of the permanent desks and is separately lockable (And was also the name of the room that I, @amcewen @osfameron and Ross Jones used to share before we started DoES Liverpool).

@aubergine10

This comment has been minimized.

Show comment
Hide comment
@aubergine10

aubergine10 May 3, 2017

Contributor

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?

Contributor

aubergine10 commented 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?

@stevesparrow

This comment has been minimized.

Show comment
Hide comment
@stevesparrow

stevesparrow May 7, 2017

Hi,

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?
Could we rename them to be more obvious please. Something simple, as Guy suggested in the Milestones issue, or as simple as 'Priority: We Should'.

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?
S

Hi,

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?
Could we rename them to be more obvious please. Something simple, as Guy suggested in the Milestones issue, or as simple as 'Priority: We Should'.

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?
S

@aubergine10

This comment has been minimized.

Show comment
Hide comment
@aubergine10

aubergine10 May 7, 2017

Contributor

The label format needs to be <number> - <caption> to work with Huboard.

I can number Holding out for a hero as 6 - Holding out for a hero to make it appear in Huboard if desired?

The other priorities are based on this comment in previous ticket.

Contributor

aubergine10 commented May 7, 2017

The label format needs to be <number> - <caption> to work with Huboard.

I can number Holding out for a hero as 6 - Holding out for a hero to make it appear in Huboard if desired?

The other priorities are based on this comment in previous ticket.

@stevesparrow

This comment has been minimized.

Show comment
Hide comment
@stevesparrow

stevesparrow May 7, 2017

Thanks Guy,

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

Thanks
Steve


image

Thanks Guy,

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

Thanks
Steve


image

@aubergine10

This comment has been minimized.

Show comment
Hide comment
@aubergine10

aubergine10 May 7, 2017

Contributor

Changing the text on the priority labels should be relatively easy, but it must remain in the format required by Huboard: <number> - <string> so perhaps something like: 1 - Priority: Must Do?

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.

Contributor

aubergine10 commented May 7, 2017

Changing the text on the priority labels should be relatively easy, but it must remain in the format required by Huboard: <number> - <string> so perhaps something like: 1 - Priority: Must Do?

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.

@stevesparrow

This comment has been minimized.

Show comment
Hide comment
@stevesparrow

stevesparrow May 7, 2017

Fab, thanks. Anything like that sounds good to me, and absolutely Huboard (I really must take a look at that!)

Thanks
Steve

Fab, thanks. Anything like that sounds good to me, and absolutely Huboard (I really must take a look at that!)

Thanks
Steve

@ajlennon

This comment has been minimized.

Show comment
Hide comment
@ajlennon

ajlennon May 8, 2017

Contributor

Does DoES use Huboard? How do I use this?

Contributor

ajlennon commented May 8, 2017

Does DoES use Huboard? How do I use this?

@SayBeano

This comment has been minimized.

Show comment
Hide comment
Member

SayBeano commented May 8, 2017

@aubergine10

This comment has been minimized.

Show comment
Hide comment
@aubergine10

aubergine10 May 10, 2017

Contributor

As discussed above, I'm planning to change the priority labels to make them a bit better. Specifically:

  • 0 - Triage
  • 1 - Priority: Must Do
  • 2 - Priority: Should Do
  • 3 - Priority: Could Do
  • 4 - Won't Do
  • 5 - Stale
  • 6 - Waiting for a Hero

Note: Closed tickets don't appear in Huboard as far as I can tell.

Contributor

aubergine10 commented May 10, 2017

As discussed above, I'm planning to change the priority labels to make them a bit better. Specifically:

  • 0 - Triage
  • 1 - Priority: Must Do
  • 2 - Priority: Should Do
  • 3 - Priority: Could Do
  • 4 - Won't Do
  • 5 - Stale
  • 6 - Waiting for a Hero

Note: Closed tickets don't appear in Huboard as far as I can tell.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment