Knowledge Tree
governance
Facts (77)
Sources
Patterns in the Transition From Founder-Leadership to Community ... arxiv.org Feb 5, 2026 26 facts
claimPrior research on open source software policy texts has focused on superficial features such as length, headers, and topics, and has been cross-sectional rather than tracking persistent governance inscriptions over time.
claimOpen source projects expand the scope of their governance texts as they mature, formalizing a more diverse set of actors and activities.
referenceThe article 'For a more transparent governance of open source' published in Communications of the ACM (vol 66) advocates for more transparent governance in open source projects.
claimGovernance files in open source projects articulate roles, permissions, obligations, and protected resources, which makes project governance transparent and traceable.
claimOpen source software projects transitioning governance from founders to communities exhibit increases in the number of defined roles and actions, as well as increases in the entropies of the distribution of institutional statements over those constructs.
claimGovernance in open-source software is a social process that structures participation, trust, and accountability in geographically dispersed collaboration networks, with group awareness, norms, and transparent decision-making playing central roles in sustaining coordination.
claimInstitutional statements decompose governance into basic elements including the types of resources and agents that must be managed, as well as the conditions and nuances under which that management is applied.
claimGovernance mechanisms in open-source software projects, such as conflict management, contribution guidelines, and social practices that facilitate knowledge sharing, are essential to long-term project resilience rather than being merely auxiliary to code development.
referenceThe study of governance artifacts parses text into three core components: Roles (who is responsible), Actions (what activities are authorized or required), and Deontics (the normative force behind directives), reflecting established practices for articulating governance rules in open-source ecosystems.
referenceThe paper 'The governance of open source software communities: an exploratory analysis' was published in the Journal of Business Systems Governance & Ethics.
claimThere is a lack of established longitudinal research on how governance transitions to community management are documented in formal textual artifacts and how those representations evolve over time.
claimAnalyzing governance-related content in artifacts like guidelines, policies, and files stored in version control provides direct insight into the institutional structure and accountability of open source software projects.
referenceThe article 'Transition of governance in a mature open software source community: evidence from the debian case' was published in Information Economics and Policy, volume 20, pages 323–332.
measurementThe study defines 'Count' as a measure of the diversity of governance elements present at a given version, specifically the number of distinct roles, actions, and deontics formalized in the governance documentation.
referenceEmpirical studies of open source software governance have historically inferred governance structures from behavioral traces such as commits, issues, and mailing lists, supplemented by qualitative case studies of contribution guidelines and social practices that support coordination in distributed communities.
claimOpen-source software governance is a socio-technical concern that requires research approaches capable of directly capturing how governance is articulated and evolves within projects.
claimOpen-source software (OSS) governance diversifies and rebalances as projects evolve, which signals the maturation of governance structures beyond their initial configurations.
claimAs open source communities mature, governance increasingly functions as a coordinating mechanism to define, distribute, and orchestrate roles and responsibilities across the project, rather than solely acting as a control mechanism.
claimOpen-source software projects require infrastructure for collaboration, coordination, community visibility, and code storage, which necessitates addressing governance concerns such as authority allocation, contributor rights, and conflict resolution.
referenceThe article 'Control and collaboration: paradoxes of governance' was published in the Academy of Management Review, volume 28, issue 3, pages 397–415.
claimPrior research on open source software governance has primarily relied on indirect signals and descriptive accounts rather than systematic, longitudinal documentation of governance as expressed in textual artifacts.
claimGhag (2022) developed a theoretical framework that links community engagement models, governance structures, and Open Source Software security practices, identifying governance as a driver of participation and system-level resilience.
procedureThe study provides a scalable NLP pipeline designed to extract institutional components, specifically roles, actions, and deontics, from governance text to surface formal structures across repositories.
claimGovernance in open-source software is a fundamental determinant for sustaining critical digital infrastructure because the organization of authority, responsibility, and decision-making directly shapes participation, accountability, and conflict resolution across distributed communities.
claimDigital communities formalize and transform governance, and textual governance can be treated as a deployable, comparable artifact for collaboration and information-systems research.
referenceThe 'PolicyKit' framework is designed for building governance in online communities, as detailed in the proceedings of the 33rd Annual ACM Symposium on User Interface Software and Technology.
Governance of open source software: state of the art - Springer Nature link.springer.com Jun 9, 2007 17 facts
referenceThe article 'Governance of open source software: state of the art' cites the 2006 paper 'Selective revealing in open innovation processes: The case of embedded Linux' by J. Henkel, which analyzes selective revealing in open innovation.
referenceThe article 'Governance of open source software: state of the art' cites the 2006 book 'Open sources 2.0: The continuing evolution', edited by C. DiBona, D. Cooper, and M. Stone, which discusses the evolution of open source.
referenceThe article 'Governance of open source software: state of the art' cites the 2006 paper 'Reputation, trust and the dynamics of leadership in communities of practice' by P. Muller, which discusses leadership dynamics in communities of practice.
referenceThe article 'Governance of open source software: state of the art' cites the 2003 paper 'Guarding the commons: How community managed software projects protect their work' by S. O’Mahony, which examines how community-managed projects protect their work.
referenceThe article 'Governance of open source software: state of the art' cites the 2005 paper 'The co-evolution of systems and communities in free and open source software development' by Y. Ye, K. Nakakoji, Y. Yamamoto, and K. Kishida, which discusses the co-evolution of systems and communities.
referenceP.B. de Laat authored the article 'Governance of open source software: state of the art,' which was published in the Journal of Management and Governance, volume 11, pages 165–177, in 2007.
referenceThe article 'Governance of open source software: state of the art' cites the 2006 paper 'Motivation, governance, and the viability of hybrid forms in open source software development' by S. Shah, which analyzes governance and hybrid forms in open source.
referenceThe article 'Governance of open source software: state of the art' cites P. B. de Laat's 2006 work 'Internet-based commons of intellectual resources: An exploration of their variety', which explores the variety of internet-based commons.
referenceThe article 'Governance of open source software: state of the art' cites the 2005 paper 'Why hackers do what they do: Understanding motivation and effort in free/open source projects' by K. R. Lakhani and R. G. Wolf, which investigates motivations in open source projects.
referenceThe article 'Governance of open source software: state of the art' cites the 2005 paper 'Nonprofit foundations and their role in community-firm software collaboration' by S. O’Mahony, which discusses the role of foundations in software collaboration.
referenceThe article 'Governance of open source software: state of the art' cites the 2003/4 paper 'Continuous integration and quality assurance: A case study of two open source projects' by J. Holck and N. Jørgensen, which studies continuous integration and quality assurance in open source.
referenceThe article 'Governance of open source software: state of the art' cites the 2005 book 'Perspectives on free and open source software', edited by J. Feller, B. Fitzgerald, S. A. Hissam, and K. R. Lakhani, which provides perspectives on free and open source software.
referenceThe article 'Governance of open source software: state of the art' cites the 2005 paper 'Adopting open source software engineering (OSSE) practices by adopting OSSE Tools' by J. Robbins, which discusses the adoption of open source engineering practices.
referenceThe article 'Governance of open source software: state of the art' cites the 2003 paper 'How communities support innovative activities: An exploration of assistance and sharing among end-users' by N. Franke and S. Shah, which explores how communities support innovation.
referenceThe article 'Governance of open source software: state of the art' cites the 2003 paper 'Reconciling rent-seekers and donators - The governance structure of open source' by E. Franck and C. Jungwirth, which examines the governance structure of open source projects.
claimThe article 'Governance of open source software: state of the art' by P.B. de Laat is distributed under the Creative Commons Attribution Noncommercial License (version 2.0), which permits noncommercial use, distribution, and reproduction provided the original author and source are credited.
referenceThe article 'Governance of open source software: state of the art' cites the 2005 book 'Democratizing innovation' by E. von Hippel, which discusses the democratization of innovation.
Governance in Practice: How Open Source Projects Define ... - arXiv arxiv.org 5 days ago 9 facts
referenceThe paper 'Governance in open source software development projects: a comparative multi-level analysis' was published in the IFIP International Conference on Open Source Systems proceedings, pages 130–142.
referenceThe paper 'The emergence of governance in an open source community' was published in the Academy of Management Journal 50 (5), pages 1079–1106.
claimIndustry and institutional sources, including Red Hat (2022) and the OSPO Alliance (2023), emphasize that effective governance is central to sustaining healthy open source software communities.
claimOpen source software communities institutionalize governance by formalizing norms and practices into explicit structures, such as charters and artifacts, to manage coordination challenges and sustain development.
referenceThe paper 'Do we run how we say we run? formalization and practice of governance in oss communities' was published in the Proceedings of the 2024 CHI Conference on Human Factors in Computing Systems (CHI ’24).
referenceThe paper 'Governance matters: lessons from restructuring the data table OSS project' was published in the 2025 IEEE International Conference on Software Maintenance and Evolution (ICSME), pages 1–12.
procedureThe researchers restricted their search for governance documentation to files containing the term 'governance,' based on GitHub's official documentation identifying GOVERNANCE.md as a file describing project governance.
claimInformal governance arrangements in open source software projects often become insufficient for ensuring accountability, transparency, and continuity as projects increase in scale and complexity.
claimOpen source software projects vary widely in how they label and define roles, leading to inconsistencies where the same title carries distinct responsibilities across projects, and similar duties are referred to under different names.
Open-Source Governance And Open Source Communities - Meegle meegle.com 4 facts
claimGovernance prevents the splintering of open-source projects into competing forks by establishing clear guidelines and decision-making processes.
claimStructured governance reduces contributor burnout by distributing responsibilities among community members.
claimStructured governance ensures the long-term viability of open-source projects by addressing funding, resource allocation, and contributor retention.
claimGovernance helps prioritize tasks and allocate resources effectively to prevent stagnation in open-source projects.
Full article: Network governance and collaborative governance tandfonline.com Dec 4, 2021 3 facts
referenceRoiseland is cited in the article 'Network governance and collaborative governance' regarding the implementation of governance as collaboration.
claimPublic administrators often use collaboration as a strategy to improve governance, according to the article 'Network governance and collaborative governance'.
claimPublic administrators implement governance as collaboration, according to the article 'Network governance and collaborative governance'.
Open-Source Governance And Open Source Collaboration - Meegle meegle.com 2 facts
Business ecosystems as a way to activate lock-in in business models link.springer.com Mar 28, 2025 2 facts
referenceWilliamson published the article 'Transaction cost economics: The governance of contractual relations' in the Journal of Law and Economics in 1979.
claimA novelty-oriented business model offers a new way of doing business, which may stem from the involvement of a novel actor, activity, transaction mechanism, or pattern of the activity system, including governance.
7 features for successful programme management with OpenProject openproject.org Aug 21, 2025 1 fact
claimOpenProject provides an integrated 'cockpit' featuring phase gates, dashboards, risk management, and meetings to ensure governance, transparency, and collaboration.
Wild edible plants for food security, dietary diversity, and nutraceuticals frontiersin.org Nov 27, 2025 1 fact
referenceMount (2012) analyzes the scale and governance of local food systems in the article 'Growing local food: scale and local food systems governance' published in 'Agriculture and Human Values'.
A guide to open source project governance models - Red Hat redhat.com Jun 24, 2020 1 fact
claimSome open source projects utilize electoral processes for governance, which may include holding elections for specific roles or conducting votes to ratify or update project policies and procedures.
PM² Project Management Methodology - OpenProject openproject.org 1 fact
referenceThe House of PM² framework consists of four pillars: Governance, Lifecycle, Processes, and Artefacts, all supported by PM² Mindsets.
Building Leadership in an Open Source Community linuxfoundation.org 1 fact
referenceCollaborative open source development requires adapting culture, processes, and tools, including development models, collaboration, transparency, meritocracy, contribution processes, governance, approvals, operational models, compliance, IT infrastructure, development tools, knowledge sharing, code reuse, team formation, organizational structure, hiring practices, and metrics.
Ethnobotanical study of food plants used in traditional medicine in ... link.springer.com Nov 26, 2025 1 fact
referenceVierros M, Suttle CA, Harden-Davies H, and Burton G published 'Considering Indigenous peoples and local communities in governance of the global ocean commons' in Marine Policy in 2020.
What is Open Source Software (OSS)? - Harness harness.io Dec 17, 2025 1 fact
claimEffective governance and quality control mechanisms are necessary for open source software projects to maintain software integrity and mitigate challenges related to community contributions.
Unknown source 1 fact
claimOpen source projects typically function based on established rules, customs, and processes that define which contributors possess the authority to execute specific tasks.
Archetypes of open-source business models | Electronic Markets link.springer.com Jun 14, 2022 1 fact
claimSchreieck, Wiesche, and Krcmar (2016) identified key concepts and issues regarding the design and governance of platform ecosystems for future research.
Does the combination of sustainable business model patterns lead ... link.springer.com Feb 20, 2023 1 fact
referenceFraccascia, Giannoccaro, and Albino (2019) created a taxonomy for business models in industrial symbiosis, specifically focusing on the form of governance.
Cyber Insights 2025: Open Source and Software Supply Chain ... securityweek.com Jan 15, 2025 1 fact
claimOpen source software lacks a central authority, which prevents the imposition of formal oversight or governance.
Open source as an affordable key to Innovation in ... coforge.com 1 fact
procedureTo implement open-source processes, an enterprise should develop a training policy, create an internal website for governance, educate the organization on strategy and cost benefits, and establish a formal knowledge-sharing process for lessons learned.
Seven observations and research questions about Open Design ... cambridge.org Oct 19, 2021 1 fact
claimProcess openness is defined by the governance and coordination of the product development process.
What is Open Source? - Revenera revenera.com 1 fact
claimEffective governance, license compliance, and active community participation are essential for successful Open Source Software adoption in enterprises.