InnerSourceCommons / InnerSourceCommons/InnerSourcePatterns
Insights into the growth and maintenance of our Patterns collection
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- HTML
- Estrellas
- 853
- Forks
- 206
- Merge medio
- 1 d 23 h
- PR fusionados (30 d)
- 2
Descripción
Our InnerSource Patterns are maintained by a working group within the InnerSource Commons, often called Patterns WG for short. That Patterns WG is creating a report about anything that has happened related to our patterns once a quarter, to give the Board of the InnerSource Commons visibility into what is going on. These reports have also prove valuable for the Patterns WG itself as it motivates us to pause and look back over the last couple of months every once in a while :)
As an example, see the 2023-05 report.
In these reports we also include some measurable things like
- how many new patterns were proposed (or published in our book)
- how many patterns were improved? (like where did we discover further organizations that are using this pattern)
- etc
However as some of these measures were hard to collect, we did not do this consistently in our reports.
Now I read about the Issue Metrics GitHub Action, and was wondering if we could use that to generate some of the metrics from our reports automatically? See also this related blog post about data-driven insights by GitHub.
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
Comienza con meta/boardreports/2023-05.md y la documentación vinculada de Issue Metrics GitHub Action. Identifica qué métricas trimestrales se pueden generar de forma fiable y cómo deberían incorporarse a los informes de la junta. Se considerará terminado cuando el Patterns WG tenga una forma acordada y repetible de producir las métricas seleccionadas.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- github-actions
- Área
- analytics, documentation, tooling
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 28/100