Kelly Mears

Commons-Based Peer Production

Large-scale production coordinated by modular tasks and volunteer contribution rather than price or hierarchy.

Meaning & Society2 min read333 words11 out · 4 in
also calledPeer productionCBPP

Commons-based peer production is Yochai Benkler's term for a mode of production organised around neither market prices nor managerial hierarchy: large numbers of people, often volunteers, coordinate on a shared project by each contributing small, modular pieces of work.

Benkler names three structural conditions. Modularity means the whole divides into components that can be produced independently of one another. Granularity means those components are fine enough that a contributor can finish one cheaply — an evening's work, and no great loss if it is wasted. Low-cost integration lets the finished pieces be checked and merged cheaply, so a barely-adequate contribution is still worth accepting rather than screening out. A Wiki is the clearest instance of all three at once — anyone can fix one sentence without ever seeing the rest of the page.

Free software shows the same pattern applied to code rather than prose, and the argument about how to keep the commons open was never settled. Copyleft lets anyone use and modify the code but requires derivatives to stay open too; a Permissive License imposes no such obligation. The drift has been toward permissive terms, which overtook copyleft in share of projects somewhere between 2014 and 2017 and now cover roughly three-quarters of them. Both remain Collective Action problems at root — the good exists only if enough people keep contributing, and nothing forces anyone to.

Governance strains as a project grows. Early contributors often accumulate outsized influence over what gets accepted, reproducing the hierarchy peer production was meant to avoid; a small number of maintainers reviewing everyone else's work recreates Bus Factor risk even with thousands of contributors, since the real bottleneck is review capacity, not authorship. That bottleneck's shape tends to mirror the shape of the group producing it, an instance of Conway's Law applying to volunteer structures as readily as to companies. Version Control solved the mechanical half of coordination — tracking who changed what — without solving the social half of deciding who gets the final say.

See also4

Hand-picked in the note itself — the neighbours worth reading next.

Linked from4

Notes elsewhere in the wiki that reach for this one.