InnerSourceCommons / InnerSourceCommons/InnerSourcePatterns

Showcase the organizations and the patterns they use in our book

未關閉
#623 8 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

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

描述

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.

貢獻指南

開啟貢獻指南

從這裡開始

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

研究方向

先檢視書中現有的「Known Instances」章節,以及 issue 提議的單一頁面和按組織劃分的方法。完成條件是需要有一套已達成共識的呈現結構,用來展示各個組織及其採用的模式,但 issue 沒有指出檔案或測試。

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

評估

領域
documentation
Issue 類型
功能
難度
5/5
預估耗時
一週以上
活躍度
停滯
描述清晰度
需要釐清
新手友好度
20/100

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

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