Governance in Practice: How Open Source Projects Define and Document Roles
This paper empirically analyzes how open source projects codify governance roles in written artifacts using Institutional Grammar, revealing inconsistencies in role definitions ("role drift") and the concentration of diverse responsibilities in few individuals ("Maintainer Paradox") to advocate for clearer role design and distributed leadership for community sustainability.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine a massive, bustling city built entirely by volunteers. There are no mayors, no police chiefs, and no official job titles handed out by a government. Instead, thousands of people from all over the world show up every day to fix potholes, build new parks, write laws, and keep the lights on. This city is Open Source Software (OSS).
For a long time, we assumed this city ran on "good vibes" and mutual respect. But as the city grew, people started asking: Who actually makes the big decisions? Who gets to lock the gates? And why does one person seem to be doing the job of a whole department?
This paper is like a team of urban planners who decided to stop guessing and start reading the city's rulebooks (specifically, files named GOVERNANCE.md). They wanted to see how these volunteer cities actually organize themselves on paper.
Here is the breakdown of their findings, using some everyday analogies:
1. The "Name Tag" Problem (Role Drift)
The researchers found a funny but confusing problem: Names don't mean the same thing everywhere.
- The Analogy: Imagine you walk into a restaurant in New York and see a "Manager." You expect them to handle the staff and the menu. Then you walk into a restaurant in Tokyo with a "Manager," and they are actually the head chef and the busboy and the person who waters the plants.
- The Finding: In the world of open source, a "Maintainer" in one project might just be someone who merges code. In another project, a "Maintainer" is a super-hero who manages the budget, mentors new people, fixes bugs, and decides the project's future. The title is the same, but the job description is totally different. This is called "Role Drift."
2. The "Swiss Army Knife" Problem (The Maintainer Paradox)
The study discovered that the most important people in these projects—the Maintainers—are often carrying way too much weight.
- The Analogy: Think of a Maintainer as a Swiss Army Knife. They are expected to be the screwdriver (coding), the can opener (managing people), the scissors (fixing bugs), and the magnifying glass (planning strategy) all at once.
- The Finding: While this sounds efficient, it's actually dangerous. Because one person is doing the job of three different roles, they are at high risk of burning out (getting tired and quitting). The paper calls this the "Maintainer Paradox": The system relies on a few people to do everything, which makes the whole city fragile if those few people get sick or tired.
3. The Two Layers of the City
The researchers realized that these projects usually have two distinct layers, even if they mix them up in the rulebooks:
- The "City Council" (Organizational Layer): These are the people who decide the big picture. They write the constitution, decide where to build the next park, and talk to outside investors. They rarely fix the actual potholes.
- The "Construction Crew" (Operational Layer): These are the people actually laying bricks, fixing code, and answering user questions.
- The Mix-up: In many projects, the "City Council" members are also the ones holding the trowels. They try to do both the strategy and the manual labor, which leads to the burnout mentioned above.
4. The "Ghost" Roles (Symbolic Jobs)
The researchers also found some roles that don't seem to do "work" but are actually super important.
- The "Town Crier" (Advocates): These people don't write code. Their job is to shout about the project on social media, write blogs, and make sure people know the city exists.
- The "Hall of Fame" (Emeritus): These are former leaders who have retired. They don't have any power anymore, but the project keeps their title as a way to say, "Thank you for your service." It's like putting a plaque on a wall; it keeps the history alive and shows respect.
5. Why This Matters
The paper argues that we need to stop treating these rulebooks as boring legal documents. They are actually blueprints for the city's health.
- If the blueprint is messy: People get confused about who to ask for help, roles overlap, and the "Swiss Army Knife" leaders burn out.
- If the blueprint is clear: Everyone knows their job. The "City Council" focuses on strategy, the "Construction Crew" focuses on building, and the "Town Criers" keep the community happy.
The Bottom Line
This study is a wake-up call for open source communities. It says: "Stop assuming everyone knows the rules. Write them down clearly, split up the heavy lifting so no one person carries the whole city, and make sure you have people dedicated to just talking to people, not just fixing code."
By reading the rulebooks and understanding how roles are actually defined, we can build software communities that are less stressful, more sustainable, and better at keeping their lights on for the long haul.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.