Insights into the growth and maintenance of our Patterns collection

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.

Comece com meta/boardreports/2023-05.md e a documentação vinculada do Issue Metrics GitHub Action. Identifique quais métricas trimestrais podem ser geradas de forma confiável e como elas devem alimentar os relatórios do conselho. Considera-se concluído quando o Patterns WG tiver uma maneira acordada e repetível de produzir as métricas selecionadas.