COMMUNITY: Review Community Categories/Labels (#143)

[ChristopherA]

• [ ] Choose Different Ones for Community?
• [ ] Add to Community
• [ ] Are people actually using labels?
• [ ] Since we have have so many repositories, we should come up with a reasonable set of standard labels that are suitable for our needs. The trick will be not to have TOO many labels. We don't tend to host giant projects with lots of contributors and complex automated CI scripts, instead for most it is typically a lead and some contributors. However, some repos like this one and the Airgapped Community also need some labels suitable to our community as whole and the cross-repo project management work we do.

First do some research: look at some other cryptocurrency repos, in particular Bitcoin-Core. I also found some good links:

• https://robinpowered.com/blog/best-practice-system-for-organizing-and-tagging-github-issues
• https://docs.saltproject.io/en/latest/topics/development/labels.html
• https://seantrane.com/posts/logical-colorful-github-labels-18230/
• https://medium.com/@dave_lunny/sane-github-labels-c5d2e6004b63

We should make some decisions on if we want to use emoji in Labels and how non-Label tags might be used (in particular, Milestones and Projects)

I'd suggest starting with the Secure Template as it is what is used to create new repos as the base set, and then add some additional labels to this Community repo. Then seek feedback. Once a set it finalized, it needs to be brought into our other repos, which can either be done by hand, or automated or use gitlabelmaker.

See below (from #143) for categories for community discussion, that might then be dovetailed into labels.

We need some help with better discussion categories for our Community Discussions.

https://github.com/blockchaincommons/community/discussions

Resolving this has a few steps. We need the first three or maybe four right now:

• [ ] Identify most active GitHub Discussions community.
  • Not sure how to do this. Maybe Github has publicized some of the better github sponsor repos?
  • Maybe IPFS?
• [ ] Research Categories used by top communities.
• [ ] Produce a list of categories.
• [ ] Suggest changes to standard labels used in the Community Repo
• [ ] Get Feedback
• [ ] Implement

[ChristopherA]

Related to automating projects, a labeling scheme: https://medium.com/the-andela-way/how-to-build-a-power-up-for-your-github-project-board-for-project-management-344d5b380a68

[HarshCasper]

Hi @ChristopherA

Can I take up the project? I expressed interest in working on CI and this would be something that would concern my area of work.

[ChristopherA]

👍

[shannona]

I've reviewed the suggested sources and added a few (security, in process, idea). I've also tightened up color-coding a tiny bit.

We could add a set of labels for difficulty and a set of labels for importance. I feel like we cover important with the "next release" tag, while it'd be a question of whether developers such as @wolfmcnally would find difficulty labels worthwhile as an interaction medium. I've tabled that for the moment, but if we want to add them in, let me know.

I'm going to add new ones and update colors on GST on Gordian Server.

I'd then suggest closing this.

[shannona]

GST and Gordian Server now match this. GST has a few extra labels for specific content/platform (Ethereum, MacOS), which is probably fine. I laid them out in a standardized purple.

[shannona]

Closing per @ChristopherA