# Coerced Contribution Kills the Commons Every governance model for open source sustainability eventually faces the same question: should contribution be mandatory? The answer is no, and the evidence converges from three unrelated fields. From commons research: Ostrom's work shows that mandating contributions crowds out intrinsic motivation. The German church taxation study found that framing donations as mandatory "taxes" rather than voluntary offerings reduced giving among the weakly motivated. People who contributed because they wanted to stopped contributing when told they had to. From community building: Jones and Vogl identify coercion as the failure mode of community leadership. "If any of these needs are contextualized outside a conversation of serving, enriching, emboldening, supporting, or protecting the inside, then it's likely to be coercion." Coercion produces compliance, not belonging. From free software philosophy: Toderash draws the line cleanly. "When contribution becomes a duty, the software is no longer free. It may still be open source, but it is not free -- neither libre nor gratis." The temptation to mandate is understandable. Maintainers are burned out. Companies extract billions from software they didn't build. The asymmetry feels unjust. But the proposed remedy -- contribution requirements, credit systems with marketplace consequences, social pressure campaigns -- replaces intrinsic motivation with external compliance. You get contributions that are minimal, strategic, and gamed. Buytaert acknowledges this about Drupal's credit system: "Some organizations have tried to game the system, while others question whether the cost-benefit is worthwhile." The alternative isn't passivity. It's designing systems where contributing is the obviously advantageous choice without being compulsory. Ostrom's successful commons aren't lawless -- they have clear boundaries, monitoring, and graduated sanctions. But the sanctions target rule-breaking, not non-participation. There's a difference between "you must contribute" and "if you contribute, here's what you get access to." The first is coercion. The second is a marketplace. Open source governance keeps conflating the two. <!-- atomicity: 1 idea ✓ --> ## Why This Matters If your open source sustainability strategy depends on shaming or mandating contributions, you're building a system that will produce minimal compliance from the companies you're targeting and resentment from the volunteers who were already contributing freely. Design for intrinsic motivation. Make contributing the better deal without making it the only legal option. ## Links - [[3. Resources/Permanent Notes/Ostrom-Theology Crossover - Commons Governance in Faith and Code]] — evidence-for: commons governance protects voluntary participation while setting enforceable rules for shared resources - [[3. Resources/Permanent Notes/The Maker-Taker Frame Confuses Two Different Scarcities]] — extends: contribution coercion follows when governance treats code abundance and maintainer attention as one undifferentiated scarcity - [[3. Resources/Permanent Notes/Belonging Requires Choice Connection and Progress]] — contrasts: coercion removes the choice without which participation cannot become belonging. - [[3. Resources/Permanent Notes/The Inverse Commons]] — contrasts: an inverse commons needs governance against harmful accumulation, but that does not make contribution itself a compulsory duty - [[3. Resources/Literature Notes/The Feasibility and Governance Concerns Behind 5% Contribution to WordPress Core]] — applies-in; the five-percent proposal shows how a uniform contribution duty creates unequal costs and governance pressure across firms. - [[3. Resources/Permanent Notes/Contribution-Based Education Produces Work-Ready Developers Faster Than Credentials]] — constrains: contribution-based teaching serves learners only while participation remains educational rather than compulsory project labor. - [[3. Resources/Permanent Notes/Curated Mastery Conferences Serve Practitioners That Volume Conferences Cannot]] — applies-in: unpaid expert speaking becomes a contribution tax when the event extracts practitioner knowledge without compensating the people who supply it. - [[3. Resources/Permanent Notes/Perm · WordCamp organizers should be paid, not voluntold]] — applies-in: unpaid event labor becomes coercive when community norms treat months of skilled organizing as an obligation rather than a voluntary gift - [[3. Resources/Permanent Notes/Matt Mullenweg WCUS 2024 Keynote - WP Engine]] — contrasts: public pressure to meet a contribution duty risks replacing voluntary commons participation with coerced compliance - [[3. Resources/Permanent Notes/Permissive Licenses Define a Floor But Don't Constitute a Community]] — applies-in: the social layer above a license must invite reciprocal stewardship without converting that norm into a compulsory license obligation - [[3. Resources/Permanent Notes/Public Credit Mechanisms Are the Visible Skeleton of Open Source Social Contracts]] — contrasts: public recognition can motivate and coordinate contribution without making participation a coerced duty - [[3. Resources/Permanent Notes/Zet · Enterprise open-source participation needs policy and training scaffolding]] — contrasts: policy, training, and organizational permission support voluntary participation instead of demanding contribution without agency. - [[3. Resources/Literature Notes/Lit · Pay WordCamp organizers and speakers]] — applies-in: compensating event labor removes the hidden tax created when a commons expects expert contribution without material support. - [[3. Resources/Permanent Notes/An Above-Market Offer Is Coercive When the Alternatives Are Already Gone]] — because applies-in: a commons erodes fastest through transactions every participant technically chose. - [[3. Resources/MOCs/Commons & Community Governance MOC]] — applies-in: the MOC lists this note under Created. - [[3. Resources/MOCs/Open Source Governance MOC]] — applies-in: the MOC lists this note under Community Architecture. ## Source - [[3. Resources/Literature Notes/Community Architecture - What Makes Communities Thrive vs Extract - Literature Note]] - [[3. Resources/Readwise/Full Document Contents/Articles/Reframing the Maker-Taker Problem]] - [[3. Resources/Readwise/Books/Building Brand Communities]] - [[3. Resources/Readwise/Articles/Solving the Maker-Taker Problem]] - [[3. Resources/Readwise/Books/Drive by Daniel H. Pink|Drive by Daniel H. Pink]] - [[3. Resources/Readwise/Books/Confronting Our Freedom|Confronting Our Freedom]] - [[3. Resources/Readwise/Books/The Art of Community|The Art of Community]]