Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Showcase the organizations and the patterns they use in our book

未关闭
#623 8 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
20/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
领域
documentation

调研方向

首先查看书中现有的“Known Instances”部分，以及 issue 提议的单页面和按组织划分的方法。完成标准是需要达成一种约定的展示结构，用于展示各个组织及其采用的模式，但 issue 没有指出文件或测试。

由索引模型根据 Issue 内容生成。

描述

(Self-) Hosting

Each pattern already has the "Known Instances" section, where organizations can list themselves when they are using a given pattern.

We could show this information a bit more prominently in our book.

Implementation ideas

Single Page

Maybe a single "Adopters" page at the top level, which would then list organizations, and they patterns they use e.g.

  • Airbus
    • InnerSource License
    • Standard Base Documentation
    • Maturity Model
    • ...
  • Europace
    • Standard Base Documentation
    • Communication Tooling
    • ...
  • Bosch
    • InnerSource License
    • Dedicated Community Leader
    • ...
  • Nike
    • Core Team
    • ...

Dedicated pages for each org

It could even be a dedicated page for each organization. Maybe that would be best?
so e.g. https://patterns.innersourcecommons.org/adopters/europace

On that pace we would only list the patterns used by Europace.

That would give the respective orgs a page that they can point to if they want to say "we use these InnerSource patterns".
And if adding themselves to the "Known Instances" of a pattern is the only way to do this, then that might motivate further contributions by other companies.

主要语言
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

更多 Documentation Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。