Standardize org-wide labels

[hillaryj]

From PR #4, continuing discussion on labels.

We want to standardize on a set of labels org-wide for cisagov.

Individual repos can then add additional labels if needed.

From @jsf9k:

@cisagov/team-ois, I created example labels in this repository. Please have a look and let me know if you think those are good enough to make official here.

From @felddy:

I'd prefer more emojis in the labels... but these are fine.

https://github.blog/2018-02-22-label-improvements-emoji-descriptions-and-more/

entrylvl/platform#54

[hillaryj]

Another approach might be to separate out the different types of labels, e.g. status labels vs. type labels.

One librarian-esque approach that is still simple is described in this article on Sane GitHub Labels. This also links to a tool that makes label management easier.

Personally, I'd prefer to break out feature or improvement into its new vs updated parts - and also I have a strong preference for brevity and specificity in labels. So, something like the following (with or without the emoji).

• 🎉 feature for new features and functionality
• 🛠 improvement for improvements to existing functionality

[jsf9k]

I merged feature and improvement because I often have a difficult time deciding which is correct. Often my changes greatly expand the functionality of an existing feature.

I'm not greatly opposed to separating them again, if others find that useful.

[hillaryj]

I agree that Feature is sort of vague - I'll think about a better name for it. Or maybe it's just unnecessary.

Thinking about it more, adding status labels duplicates the purpose of the project boards, so since theoretically we use that for tracking statuses, unless we added automation it would require extra/duplicate effort.

So, for type labels, here's a proposed list with some alternate names. For repos like cool-system and cyhy-system we'd want to add a label for epics, since they have more project management than most - or, that could be a standard.

• blocked
• breaking change
• bug
• documentation
• duplicate
• epic
• improvement (alt: enhancement)
• invalid
• need info
• question
• upstream change (alt: maintenance or dependencies)
• version bump
• wontfix

[jsf9k]

Does ZenHub require an "eipc" label? Does it auto-add one for you?

I'd prefer to add the "epic" nowhere or add it everywhere. I get that there will be rare repos that need one or more custom labels, but "epics" seem to be generally useful unless that labeling is already being handled (perhaps by a means other than repo labels) in Zenhub.

I like the list @hillaryj created above. It's pretty similar to what I came up with, plus a few additions. I prefer the names @hillaryj listed over the alternatives she provided, which I think are more vague.

[hillaryj]

Roger that - I'd add epic everywhere, then. ZenHub doesn't require it, but it's a useful category for project management.

I definitely worked from that list - thanks for starting us off!

[jsf9k]

For the record, I'm fine with adding emojis if someone wants to take the lead on that.

[jsf9k]

I edited the labels for this repository to agree with Hillary's list, but I didn't delete "help wanted" or 'good first issue" yet. I feel we could go ahead and delete them since we never use them, although at one point we discussed using those labels to try and lure in external contributors.

Thoughts?

[dav3r]

I edited the labels for this repository to agree with Hillary's list, but I didn't delete "help wanted" or 'good first issue" yet. I feel we could go ahead and delete them since we never use them, although at one point we discussed using those labels to try and lure in external contributors.

Doesn't matter to me either way- it doesn't bother me having unused labels that we may or may not use in the future.

[hillaryj]

I'm fine with leaving them in - we're much more likely to use them if they exist already.

If we want to integrate with code.gov's "open tasks" to lure external contributors, we'll also need to add a code.gov label. The good first issue label will help there as it gets pulled in as a type in the open tasks list.

[jsf9k]

Added the "code.gov" label and left the "good first issue" label in place. I think we can remove "help wanted" with the addition of "code.gov". I believe that the set of labels is good now. Going once...