github / github/github-ospo

InnerSource Contributions labeler

Aberta
#96 2 comentários 2 reações 0 responsáveis Ver no GitHub
enhancement new-action
Linguagem predominante
Sem dados de linguagem
Estrelas
749
Forks
72
Métricas de merge de PRs
Nenhum PR com merge em 30d

Descrição

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

Guia de contribuição

Abrir o guia de contribuição

Direção de pesquisa

Comece revisando a documentação sobre labels do GitHub e tópicos de repositórios e, em seguida, compare as fontes de ownership propostas: a Backstage API, CODEOWNERS e uma API de organograma, como a Workday. Uma contribuição concluída deve definir como as contribuições de pessoas que não são owners são identificadas, quais itens recebem um label InnerSource e se os tópicos dos repositórios são incluídos.

Escrita pelo modelo de indexação a partir do texto da issue.

Avaliação

Stack de tecnologia
github
Domínio
tooling
Tipo de issue
Funcionalidade
Dificuldade
5/5
Tempo estimado
Mais de uma semana
Status de atividade
Estagnada
Clareza
Precisa de esclarecimento
Facilidade para iniciantes
25/100

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.