Governance in Practice: How Open Source Projects Define and Document Roles

A team of researchers from multiple institutions, including Igor Steinmacher and colleagues, conducted a systematic analysis of governance structures across 1,155 open source software (OSS) projects hosted on GitHub. Their paper, "Governance in Practice: How Open Source Projects Define and Document Roles," applies Institutional Grammar—a formal framework for analyzing rules—to extract and decompose role definitions from project documentation like CONTRIBUTING.md files. The study moves beyond anecdotal evidence to provide empirical data on how projects formally codify authority, decision rights, and responsibilities.

The analysis uncovered significant inconsistencies in how roles are defined, even when using common titles. The researchers identified 'role drift,' where identical titles (e.g., 'maintainer' or 'core contributor') carry vastly different sets of privileges, obligations, and life-cycle rules across different communities. Furthermore, the study found that a small number of individuals frequently accumulate a confluence of technical, managerial, and community duties, creating a 'Maintainer Paradox.' This centralization of diverse responsibilities can become a governance bottleneck, potentially hindering broader participation and threatening the long-term health and sustainability of OSS projects.

The findings provide crucial insights for both researchers and practitioners. For project leaders, the study highlights the importance of intentionally designing clearer, more transparent role definitions to distribute work effectively and reduce leadership overload. For the broader ecosystem, it underscores that sustainable OSS depends not just on code contributions but on robust, well-documented institutional infrastructure that guides how communities operate and make decisions.