The Meeting That Wrote Itself Down: Governance Artifacts for Projects Too Big for a Call
Photo: Peter Mercator, CC BY-SA 3.0, via Wikimedia Commons
Every maintainer of a project past a few hundred contributors eventually runs into the same wall: there is no hour of the week when the people who care can all be awake. Governance that depends on a calendar is governance that quietly excludes most of the community. The projects that scale past this wall do so by replacing the meeting with an artifact — a written object that carries the debate, the decision, and the deadline without requiring anyone to be present at the same moment.
Here are seven such artifacts, with an honest look at where each one works and where it quietly fails.
1. The RFC Document
The request-for-comments is the workhorse. A numbered proposal, a defined comment window, a recorded outcome. It works because it forces the reasoning into prose, which is reviewable long after the decision. Its failure mode is length: RFCs that run to thousands of words systematically filter out contributors reading in a second language. Template fix: require a three-paragraph summary — problem, proposal, alternatives — at the top of every document.
2. The Lazy-Consensus Timer
Announce a decision, state a window (often 72 hours), and proceed absent objection. It is the only mechanism that scales to high-volume, low-stakes calls. The failure mode is silence-as-consent favoring the attentive: contributors in distant time zones effectively get a shorter window. Template fix: anchor the timer to a full rotation of working hours across your core regions, not to the proposer's clock.
3. The Numbered Proposal (PEP-Style)
Sequential IDs give decisions a durable address — you can cite Proposal 441 in an issue three years later. The failure mode is process theater: heavyweight numbering applied to trivial changes breeds avoidance. Template fix: define explicitly what does not need a number.
4. The Annotated Commit Debate
Some decisions are best made in the diff itself, with review threads serving as the deliberative record. It works because the artifact and the decision are the same object. It fails when the rationale lives only in a review thread that gets buried; a decision with no retrievable reasoning is a decision that will be relitigated.
5. The Decision Log
A single append-only file listing every governance outcome, date, and link. Unglamorous, and disproportionately valuable to newcomers trying to understand why the project is shaped the way it is. Its failure mode is staleness — a log that lags six months becomes an anti-document. Assign ownership of it.
6. The Async Roll Call
For genuinely contested decisions, a structured vote conducted over a comment window, with each eligible contributor posting an explicit position. It surfaces objections that lazy consensus would steamroll. The failure mode is that it privileges those fluent enough to argue in writing — pair it with a channel for simplified, non-English summaries of the stakes.
7. The Post-Mortem Thread
After a decision is implemented, a scheduled written retrospective on how the process worked. It is the only mechanism on this list that improves the other six.
The Pattern Underneath
Notice what all seven share: the decision and its record are inseparable. That is the actual promise of asynchronous governance — not just convenience across time zones, but a project whose reasoning survives the departure of any single person, including you.
