Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Insights into the growth and maintenance of our Patterns collection

未關閉
#565 12 則留言 1 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
28/100
Issue 類型
功能
描述清晰度
需要釐清
活躍度
停滯
技術堆疊
github-actions

研究方向

從 meta/boardreports/2023-05.md 和連結的 Issue Metrics GitHub Action 文件開始。確認哪些季度指標可以可靠地產生,以及它們應如何納入董事會報告。完成的標準是 Patterns WG 已經有一套經過共識、可重複的方式來產生所選指標。

由索引模型根據 Issue 內容生成。

描述

:gear: Type - Meta

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.

主要語言
HTML
星號
853
分支
206
平均合併
1 天 23 小時
30 天內合併 PR
2

貢獻指南

開啟貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

InnerSourceCommons/InnerSourcePatterns 的其他 Issue

查看 InnerSourceCommons/InnerSourcePatterns 的全部 Issue

相似的 Issue

更多 Data Visualization Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。