InnerSourceCommons / InnerSourceCommons/InnerSourceLearningPath
Pulling contributors in as reviewers
還沒有人認領這個 Issue。
- 主要語言
- JavaScript
- 星號
- 77
- 分支
- 47
- 平均合併
- 11 小時 11 分鐘
- 30 天內合併 PR
- 5
描述
In the learning path for the Trusted Committer (part 2) we explain how it's the trusted committers that are reviewing code. In a first approximation this is correct and matches what I see in many open source projects.
When it comes to recruiting new committers and onboarding them I have seen a different approach:
https://blogs.apache.org/comdev/entry/an-approach-to-community-building (pretty much at the bottom) - contributors at Apache Beam are encouraged to do code reviews as well - in particular if the original patch comes from a committer, the idea is that such a review is enough for merging the code.
Maybe this is something for an InnerSource Pattern instead of the LearningPath though.
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
閱讀 Trusted Committer part 2 學習路徑部分和連結的 Apache Beam 社群建設文章,尤其關注其中關於貢獻者審查程式碼的討論。決定應在學習路徑中更新這些資料,還是將其記錄為 InnerSource Pattern;完成的標準是已就建議放置位置和範圍達成共識,並修訂了相關學習資料。
由索引模型根據 Issue 內容生成。
評估
- 領域
- documentation
- Issue 類型
- 文件
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 活躍度
- 停滯
- 描述清晰度
- 需要釐清
- 新手友好度
- 35/100