Perturbatore: “What if an About page that does not name current decision-makers is not welcoming newcomers — but warning them away?”
The Assumption
The About page serves as the primary entry point for newcomers. If the page clearly states what peeragogy is and what it offers, the right people will find their way in. Information clarity produces engagement.
Operational Reality
Howard Rheingold convened the Peeragogy project in 2012. Years later, the About page still opens with his name. The handbook speaks of collaborative courses and collected know-how, but governance remains a footnote. Not a conspiracy. Not malice. Not even conscious choice — just the default drift toward founder mythology in projects that never establish explicit governance.
Founder mythology does not need malice. It needs inattention.
Open-core projects that document governance boundaries between corporate sponsors and communities reduce friction. The boundaries are visible. People know where they stand. Projects that claim pure peer governance while maintaining informal hierarchies create something more dangerous — the illusion of equality with the reality of invisible barriers.
GitLab documents exactly who decides what, and collaboration works because the boundaries are explicit before conflict arrives. Drupal shows that transitioning from BDFL to community governance requires years of structural work — an About page cannot solve a governance problem by renaming it. Apache shows that meritocracy-based governance creates invisible hierarchies through time-availability bias: the page that looks most open may trap newcomers most effectively.
Empirical Evidence
Resilience Cases (Confirming):
- GitLab Stewardship Handbook — Explicit documentation of governance boundaries between corporate sponsor and community reduces friction. Transparent documentation of who decides what makes collaboration sustainable.
Fracture Cases (Complicating):
- Drupal Governance — Governance transition from BDFL to community model required years of structural work. Governance transparency is not a communication problem but a structural one requiring explicit redesign.
- Apache Foundation How It Works — Meritocracy-based governance creates invisible hierarchies through time-availability bias. The page that looks most open may trap newcomers most effectively.
Operational Heuristics
Positive Boundary: Document both learning principles and governance boundaries explicitly on the About page — transparent decision-making boundaries reduce friction for newcomers.
Negative Boundary: Do not create About pages that explain learning principles without documenting power structures — meritocratic governance creates invisible class systems, and a page that hides them is a trap, not a welcome.
Epistemic Synthesis
The theory assumes that communication clarity produces engagement. The evidence shows governance structure matters more than page clarity. The About page problem is not being “too detailed” but presenting peeragogy as if it emerges naturally from good intentions instead of requiring explicit structures to function. GitLab, Drupal, and Apache each show that the meaningful information gap is not about the mission — it is about who decides what.
Evidence Status
| Status |
Count |
| Confirmed cases |
1 |
| Cases under study |
2 |
| Unverified cases |
0 |
| Ambiguous cases |
0 |
Traceability
Run: audit-v2 · Delta: 1.0 → 1.1217 · Diversity D: 2
References