github / github/github-ospo

InnerSource Contributions labeler

Abierto
#96 2 comentarios 2 reacciones 0 asignados Ver en GitHub
enhancement new-action
Lenguaje dominante
Sin datos de lenguaje
Estrellas
749
Forks
72
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

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

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Comienza revisando la documentación sobre las etiquetas de GitHub y los temas de los repositorios; después, compara las fuentes de ownership propuestas: la Backstage API, CODEOWNERS y una API de organigrama como Workday. Una contribución completada debe definir cómo se identifican las contribuciones de personas que no son owners, qué elementos reciben una etiqueta InnerSource y si se incluyen los temas de los repositorios.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
github
Área
tooling
Tipo de issue
Nueva funcionalidad
Dificultad
5/5
Tiempo estimado
Más de una semana
Estado de actividad
Estancado
Claridad
Necesita aclaración
Aptitud para principiantes
25/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.