InnerSourceCommons / InnerSourceCommons/InnerSourcePatterns
Call-out on website to collect Known Instances
還沒有人認領這個 Issue。
- 主要語言
- HTML
- 星號
- 853
- 分支
- 206
- 平均合併
- 1 天 23 小時
- 30 天內合併 PR
- 2
描述
How to motivate orgs to contribute their experiences with our patterns back to the community?
A small contribution would be to list themselves as a Known Instance on the pattern, possibly with a couple of sentences about how they have used the given pattern.
A great example of such a Known Instance description from the 30 Day Warranty pattern:
Microsoft recommends this pattern as a principle - teams set their own specific time target matching their needs and confidence.
Possible Solution
backstage.io has this need call-out at the side of their website, to motivate early adopters to share publicly that they are using backstage. See screenshot.
Could we do something similar on https://innersourcecommons.org?
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
先查看 innersourcecommons.org 和現有的 Known Instance 內容,然後將所要求的號召與 backstage.io 上的 Backstage 範例進行比較。當網站提供一種清楚的方式來邀請組織分享其模式實務經驗和 Known Instance 描述,並符合提議的目的時,即視為完成。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- html
- 領域
- content, design, web-dev
- Issue 類型
- 功能
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 活躍度
- 停滯
- 描述清晰度
- 需要釐清
- 新手友好度
- 25/100