-
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
COMMUNITY: Review Community Categories/Labels (#143) #39
Comments
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 |
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. |
👍 |
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. |
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. |
Closing per @ChristopherA |
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:
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:
The text was updated successfully, but these errors were encountered: