10.5. GOVERNANCE OPEN SOURCE STYLE
An interesting feature of the open source community is that the collective and individual behaviors are shaped by the community through a body of largely undocumented norms and expected behaviors. These "governance" rules are very stable, and consistently understood and enforced by the community. For example, the following are governing principles of the open source community:[]
[] Eric S. Raymond, The Cathedral and the Bazaar: Musings on Linux and Open Source by an Accidental Revolutionary, O'Reilly Media, 2001, p. 73.
No forking projects
Distributing changes without the moderator approval is not done
Removing a person's name from the project history, credits, or maintainer list is not done without that person's explicit permission
Open source governance customs and norms have evolved over time in a consistent direction that emphasizes the following:
Public accountability
More public notice
More preservation of credits and change histories in ways that establish the legitimacy of current project owners.
In fact, the rarity of governance violations of the open source governance model is astonishing! Raymond notes that over 20 years and hundreds of open source projects, he can count the number of significant violations using his fingers.[]
[] Ibid., p. 76.
Community governance and self-governance models are absolutely critical as supporting models to top-down, policy-driven governance models. A policy-driven approach is essential, but we feel that the ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access