github / github/github-ospo

InnerSource Contributions labeler

Offen
#96 2 Kommentare 2 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
enhancement new-action
Vorherrschende Sprache
Keine Sprachdaten
Sterne
749
Forks
72
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

### 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...

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

Beginne mit der Durchsicht der Dokumentation zu GitHub-Labels und Repository-Themen und vergleiche anschließend die vorgeschlagenen Ownership-Quellen: die Backstage API, CODEOWNERS und eine Org-Chart-API wie Workday. Ein abgeschlossener Beitrag sollte festlegen, wie Beiträge von Nicht-Ownern identifiziert werden, welche Elemente ein InnerSource-Label erhalten und ob Repository-Themen einbezogen werden.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
github
Bereich
tooling
Issue-Typ
Feature
Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Aktivitätsstatus
Veraltet
Klarheit
Muss geklärt werden
Anfängerfreundlichkeit
25/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.