github / github/github-ospo

InnerSource Contributions labeler

Aperta
#96 2 commenti 2 reazioni 0 assegnatari Vedi su GitHub
enhancement new-action
Lingua principale
Nessun dato sulla lingua
Stelle
749
Fork
72
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

### New Action request

## Description

It would be helpful to be able to [label contributions to a project](https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/managing-labels) that come from outside the owning team. This is beneficial for being able to recognize InnerSource practices and measure statistics related to that. This action could be combined with the issue-metrics action to get those statistics for issues/and PRs labeled as InnerSource. InnerSource in this case would be defined as contributions from a non-owner team within an organization. ie. When a feature team contributes to the observability tools on which they depend but do not own as an area of responsibility.

Additionally it may be helpful to "label" the repository with a [Repository Topic](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics) so that it can be identified as a repository that practices InnerSource.

One complication that would need to be overcome here is the method by which a contribution is determined to be from a "non-owner" team. The tool could rely on several places to get ownership information:
- Interface with [Backstage API](https://backstage.io/docs/features/software-catalog/software-catalog-api/) assuming that there is a Backstage instance that has a complete catalog of repos with ownership information
- Codeowners file (If someone or a group they belong to is in the codeowners file then they could be considered an owner)
- An org chart interface (API) (such as workday, etc.)
- Other ideas? Open to thoughts here...

Guida per i contributori

Apri la guida per i contributori

Direzione di ricerca

Inizia esaminando la documentazione relativa alle etichette GitHub e agli argomenti dei repository, quindi confronta le fonti di ownership proposte: la Backstage API, CODEOWNERS e un’API dell’organigramma come Workday. Un contributo completato dovrebbe definire come vengono identificate le contribuzioni di persone che non sono owner, quali elementi ricevono un’etichetta InnerSource e se vengono inclusi gli argomenti dei repository.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
github
Ambito
tooling
Tipo di issue
Funzionalità
Difficoltà
5/5
Tempo stimato
Più di una settimana
Stato di attività
Ferma
Chiarezza
Da chiarire
Idoneità per principianti
25/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.