License

These materials are made available under the terms of Creative Commons 0 copyright waiver instead of a “traditional” copyleft license. We the undersigned agree to the following, wherein “this work” refers to “The Peeragogy Handbook” and all other content posted on peeragogy.org or the original collaboratory site, http://socialmediaclassroom.com/host/peeragogy.

I hereby waive all copyright and related or neighboring rights together with all associated claims and causes of action with respect to this work to the extent possible under the law.

Signed:

Bryan Alexander
Paul Allison
Elisa Armendáriz
Régis Barondeau
Doug Breitbart
George Brett
Suz Burroughs
Joseph Corneli
Jay Cross
Charles Jeffrey Danoff
Analua Dutka-Chirichetti
Julian Elve
María Fernanda Arenas
James Folkestad
John Graves
Kathy Gill
Matthew Herschler
Gigi Johnson
Anna Keune
John Laing
Kyle Larson
Roland Legrand
Amanda Lyons
Dorotea Mar
Christopher Tillman Neal
Ted Newcomb
Stephanie Parker
Miguel Ángel Pérez Álvarez
Charlotte Pierce
David Preston
Howard Rheingold
Paola Ricaurte
Laura Ritchie
Verena Roberts
Stephanie Schipper
Lisa Snow MacDonald
Fabrizio Terzi
Geoff Walker

Note that this waiver does not apply to other works by the above authors, including works linked to from peeragogy.org.

Future contributors: Note also that we will require a similar copyright waiver agreement. That said, the waiver also means that you are free to do essentially whatever you like with the content in your own work! Have fun!

How we came to this decision

These Creative Commons license options were proposed by various members of the community:

CC Zero - public domain; no restrictions for downstream users
CC By-SA - requires downstream users to include attribution and to license their work in the same way
CC By-SA-NC - requires downstream users to include attribution, to license their work in the same way and disallows any commercial use of the content

After a brief discussion, no one was in favor of restricting downstream users, so we decided to go with CC0. We agreed that we would get enough “credit” by having our names on peeragogy.org. In connection with this discussion, we agreed that we would work on ways to explicitly build “reusability” into the handbook content.

Perturbatore: “What if open licenses are like constitutions — they only work if someone is willing to enforce them, and enforcement is always political?”

The Assumption

The license is a means, not an end; sharing knowledge is the goal. Open licenses protect content but not the community’s sustainability.

Operational Reality

The Peeragogy Handbook carries no copyright. CC0 — complete surrender to the public domain. This is not generosity. It is recognition that collaborative work already belongs to everyone who touched it, and claiming ownership over collective intelligence is both impossible and dishonest.

Watch what happens when projects try to maintain control while inviting contribution. Redis changed its license in 2018, pushing commercial users toward paid versions. The community did not just complain — they forked. Valkey emerged with backing from AWS, Google, Oracle. Not because the code was better, but because the license respected what contributors had built together. The original project now competes with its own offspring.

Not ideology. Not principle. Not some abstract commitment to openness. The CC0 choice admits what most collaborative projects refuse to acknowledge — once you invite real participation, you have already lost control. The question is not whether to give up ownership, but whether to do it honestly or pretend you still have it while the work happens anyway.

GitLab shows that pairing license choice with documented governance stabilizes open communities. OpenStreetMap demonstrates that license enforcement requires institutional mechanisms. React’s patent clause controversy shows that license terms without community consent create fragility. Terraform’s license change shows that license unilateralism triggers structural resistance.

Empirical Evidence

Resilience Cases (Confirming):

GitLab Stewardship Handbook — Explicit documentation of governance boundaries between corporate sponsor and community reduces friction in open-core projects. Pairing license choice with documented governance stabilizes open communities.
OpenStreetMap Data Working Group — Formal dispute resolution bodies with binding authority and published reasoning resolve peer production conflicts that informal consensus cannot. License enforcement requires institutional mechanisms.

Fracture Cases (Complicating):

React License Controversy (Facebook) — Corporate-governed open-source can alienate the community through license terms, and community pressure can force governance reversals. License terms without community consent create fragility.
Terraform / OpenTofu Fork — License changes away from open-source can unite competitors into a fork, demonstrating that ecosystem dependency creates collective bargaining power. License unilateralism triggers structural resistance.

Operational Heuristics

Positive Boundary: The license works when paired with explicit governance documentation and formal dispute resolution mechanisms — transparent power boundaries and binding dispute resolution stabilize open communities.

Negative Boundary: Do not assume open license solves community sustainability when governance power remains concentrated and opaque — license control without transparent decision-making governance produces forks and alienation.

Epistemic Synthesis

Formal license becomes self-protection when it corresponds to the real power dynamics of collaborative work. The Redis fork demonstrates that communities hold more leverage than founders assume — but only when the legal framework allows them to exercise it. The useful tension: whether CC0 creates stronger collaborative relationships than protective licenses, or simply makes power struggles more honest.

Perturbatore: “What if open licenses are like constitutions — they only work if someone is willing to enforce them, and enforcement is always political?”

A fork is not a failure. It is the community exercising its only real power.

Evidence Status

Status	Count
Confirmed cases	2
Cases under study	0
Unverified cases	0
Ambiguous cases	0

Traceability

Run: audit-v2 · Delta: 1.0 → 1.0619 (±0.0619) · Diversity D: 2

References

💬 Field Report: License Is Self-Protection

Every pattern in the Handbook has been tested in the real world — and the real world usually has something to say about it. If you tried something similar, or saw it fail differently, share the story here.

Write in your native language — the browser will translate. Lowering the entry barrier is more important than choosing the "right" language. GitHub translates threads automatically so everyone can follow along.
Read how evidence is collected →

What happens after I share my story?

1. Your post appears in GitHub Discussions in the Field reports category.

2. Once a week, the project reads new threads and checks for patterns worth integrating.

3. If your story reveals a new Failure Vector, a revision to tension_index, or a sharper edge for the Perturbator — the entry gets updated.

4. The change is logged at /log and goes live on the next deploy.

Don't have a GitHub account? Here's how it works

GitHub Discussions is free. You need a GitHub account (30 seconds to create one).

Once you're signed in, click "Share your story" above. Write in your own language — the thread will be translated for everyone else automatically.

You don't need to know how to code. You don't need to know what "git" is. You just need an observation that the theory didn't match reality.

What are GitHub Discussions? →