Sharing the Load Effectively: Roles and Responsibilities in Open Source Projects

### Overview In this presentation from Open Source Summit Europe, Jeff Rowe, a program manager at the Linux Foundation, examines the organizational architecture of open-source projects. Drawing on decades of leadership experience across communities such as the Yocto Project, LF Energy, and RISC-V International, Rowe outlines how clear delineation of roles and responsibilities helps prevent contributor burnout, addresses structural gaps, and nurtures emerging leaders. He highlights the challenge of balancing high project volume with limited human resources—a dynamic he terms the "work-work balance"—and illustrates how different projects structure their governance.

### Key Topics - **Project Functional Silos:** Rowe classifies open-source leadership and operational functions into three tiers: Executive (decision-makers and financial managers), Administrative (implementers of executive strategy and operational drivers), and Managerial (tactical executors across technical, marketing, and community channels). - **Resourcing and Neutrality:** Roles are sourced from member organizations, hired directly by the project/foundation, or drawn from the wider community. Certain administrative and technical leadership roles require direct hiring or contracting to maintain operational neutrality rather than favoring any individual corporate sponsor. - **Separation of Concerns:** A foundational open-source best practice is maintaining a clear division between technical governance (e.g., technical steering committees and maintainers) and business/operational governance (e.g., governing boards and marketing).

### Technical Details - **Executive Roles:** - *TSC Chair / Chief Architect / Benevolent Dictator for Life (BDFL):* Serves as the ultimate arbiter of technical strategy and acts as the bridge to the governing board. A TSC chair is typically an elected, rotating community role, while chief architects may eventually transition into neutral hired positions. - *Governing Board and Board Chair:* Composed of member representatives who define budgets, vote on strategic matters, and govern per project charters. - *Treasurer:* Manages project budgeting and fiscal oversight on behalf of the board, frequently coordinating with executive directors on financial execution. - *Technical Director:* Vice president-level operational counterpart to the technical leader, establishing policies, managing incoming patches/bugs/feature requests, and tracking technical metrics. - *Executive Director (ED) / CEO:* Primary operational and "gap-filling" executive implementing board directives, often assuming general manager or chief of staff duties in smaller initiatives. - **Administrative Roles:** - *General Manager / Director of Operations:* Oversees high-level project resourcing when operational scale exceeds ED bandwidth. - *Director of Marketing / CMO:* Directs outward and inward communications, websites, press, branding, trademarks, affiliations, and events. - *Legal Counsel:* Contracted or internal counsel handling intellectual property, licensing, contributor agreements, trademarks, and escalated code of conduct disputes. - **Managerial & Tactical Roles:** - *Maintainers:* Domain-specific technical leads overseeing code repositories, triage, patch merges, and developer communications. - *Program Managers:* Tactical problem-solvers who coordinate execution across strategic initiatives, resource gap-filling, and cross-functional operations. - *Board Secretary:* Chartered role tasked with managing official meeting agendas, voting administration, list access, and maintaining official minutes. - *Community Managers:* Act as the "ears" of the project, advocating for the broader community up to leadership, providing emotional support, and handling initial code of conduct concerns (recommending training via organizations like Otter Tech). - **Case Studies in Governance Structure:** - *LF Energy:* Executive director and part-time program managers support a federated model where individual project TSC chairs convene under a Technical Advisory Council (TAC), with the TAC chair holding a voting seat on the Governing Board. - *RISC-V International:* A Swiss non-profit operating under an LF management services agreement, featuring an executive staff (CEO Calista Redmond, CTO, marketing director, part-time program/technical program managers) paired with dual member committees across ISA development. - *Hyperledger:* Enforces strict separation of business and community technical roles; working group chairs, special interest group (SIG) chairs, and the TSC chair are drawn directly from the general community rather than member-only seats.

### Takeaways Rowe concludes with three actionable recommendations for project communities: 1. **Map Roles and Responsibilities:** Understand the distinct functions required for project health and ensure roles are clearly delineated rather than overloaded onto single individuals. 2. **Audit Community Processes:** Objectively assess internal workflows to determine whether they foster collaboration or drive contributors away, monitoring workloads to prevent contributor burnout. 3. **Set Project Tone Intentionally:** Proactively discuss culture and soft-skill management among leaders, recognizing that deliberate cultivation of tone is fundamental to long-term community health and succession planning.