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
领域
analytics, documentation, tooling

调研方向

从 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 摘要。