主题： collaboration
-
与长期开放的文档协助召集相比，预先安排的文档日能带来更多首次贡献者
假设：如果一个项目公布一个特定日期，配以精选的小型文档问题清单、维护者承诺当日评审，并为每项任务打上 good-first-issue 标签，那么它从从未贡献过的人那里获得的已合并文档改动数量，会多于把同一份清单全年保持开放所获得的数量；本文提出了一种基于单个项目自身历史数据的对比方法。
-
Describing a change so that reviewers can review it
A change description states the problem, the approach and its alternatives, how it was tested and what reviewers should look at; it links the ticket and lists risks and follow-ups, so review starts with understanding instead of archaeology.
-
Prefer change proposals for external ownership
Improve another contributor’s material through a revision-bound proposal when direct replacement is not authorized.
-
小项目的议题分流：固定标签集与定期巡查
分流意味着为每个新议题判断它是什么、是否可采取行动，以及下一步由谁推进。类型、状态、领域三个类别的小型标签词表，加上固定节奏的简短巡查，可让跟踪器如实反映情况。GitHub 的默认标签（包括 bug、enhancement、documentation、duplicate、question、wontfix、good first issue 和 help wanted）是可行的起始集合。
-
Recognising contributors: a contributors table by contribution type, without rankings
The All Contributors specification calls for a Contributors section in a prominent place, as a table of name, link and contribution category, inclusive of every kind of contribution at any level, with order immaterial; it recommends against excluding anyone for a perceived low level of contribution. Git's Co-authored-by trailer credits co-authors of a single commit. Together they let a small project credit documentation, triage, design and reports, not only merged code.
-
回答新人最初五个问题的 CONTRIBUTING 文件
准备贡献的人在写代码前会问：项目需要这个变更吗，如何提出，拉取请求必须包含什么，多久有人回复，合并后的变更如何到达用户。CONTRIBUTING 文件按顺序回答这五个问题，其余内容通过链接提供，旨在预先避免因超出范围或缺少测试而被拒绝的拉取请求。
-
拒绝功能请求，同时留住贡献者
及时给出拒绝，指向书面的项目范围，说明替代办法并关闭讨论，比沉默更体贴，也能让请求者继续贡献。Open Source Guides 指出，把事情写下来更容易说“不”，而回复通常不需要超过一两句话。
机器可读： JSON