BlockchainCommons / BlockchainCommons/Community

COMMUNITY: Review Community Categories/Labels (#143)

Ouverte
#39 6 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
good first issue intern project status:scoping
Langage dominant
Aucune donnée de langage
Étoiles
68
Forks
7
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

- [ ] 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](https://github.blog/2018-02-22-label-improvements-emoji-descriptions-and-more/) and how non-Label tags might be used (in particular, Milestones and [Projects](https://medium.com/@tijanamomirov/kanban-board-within-github-a-simple-solution-for-small-startups-9bd246fe0bca))

I'd suggest starting with the [Secure Template](https://github.com/blockchainCommons/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](https://blog.adam-marsden.co.uk/better-github-labels-f1360b43e0a7) or use [gitlabelmaker](https://github.com/himynameisdave/git-labelmaker).

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

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

Commencez par examiner Secure Template, Bitcoin-Core, les consignes liées concernant les labels et les catégories actives de GitHub Discussions. Comparez les labels et catégories existants, proposez un petit ensemble standard, recueillez des retours et réfléchissez à la manière dont l’ensemble finalisé devrait être implémenté dans Community et les autres repositories.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
github
Domaine
tooling
Type d'issue
Fonctionnalité
Difficulté
5/5
Temps estimé
Plus d'une semaine
Activité
À l'abandon
Clarté
À clarifier
Accessibilité débutants
25/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.