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