and risk management to technical collaboration β preparing modern enterprises to tackle pressing governance challenges.
π Read the Good Governance for Open Source handbook: dub.sh/OSPO-GGI-ZHTW
The Good Governance for Open Source handbook, translated with support from OCF, offers a framework for βopen source supply chain governance.β It helps organizations comprehensively approach open source adoption and strategy β from process design, legal compliance,
π« Using open source software is not enough β building systems, trust, and reciprocal participation is essential.
β
A true open source culture must take root through governance and institutional commitment.
πΉ Policy and Compliance: Does your organization clearly define licensing, contribution processes, and community participation principles?
πΉ Strategy and Impact: Is open source integrated into your companyβs innovation and business strategies?
πΉ Organizational Readiness: Do you have structured open source education and internal processes in place?
πΉ External Engagement: Are developers encouraged to contribute to external open source projects, with systems in place for contribution and feedback?
According to the Good Governance for Open Source handbook, organizations can assess themselves through the following four dimensions (summary below β refer to the handbook for full details):
Not Just Lip Service: 4 Deep Indicators of a True Open Source Culture
Is your organization truly embracing open source culture?
π Learn more: ocf.tw/p/pmpc/
π Bonus: Call for proposals now open for the 2025 COSCUP Open Source Policy track β submit yours today! www.facebook.com/share/p/17s1...
π― Public Money, Public Code refers to the practice of using open source software for digitizing public services and releasing software developed or procured with public funds under open source licenses.
3οΈβ£ Identify open source software with public value and proactively support community incubation and project development.
1οΈβ£ Audit existing digital services to clarify licensing and usage, and establish open government policies that can accommodate public code.
2οΈβ£ Manage and release public code using international standards to ensure cybersecurity and licensing stability.
OCF has long advocated for government adoption of open source software, believing it is key to achieving transparency, innovation, and digital autonomy. Our core proposals:
FSFE Policy Manager Johannes NΓ€der also stressed the need for the EU and national governments to ensure long-term, stable funding for open source software in order to safeguard digital sovereignty, promote interoperability, and support both the European economy and civil society.
ZenDiS Chair Jutta Horstmann called on public institutions to gradually increase their procurement of open source software to break away from reliance on U.S. based vendors.
The Do-FOSS initiative from DortmundβGermanyβs ninth-largest cityβhas successfully incorporated the "Public Money, Public Code" principle into municipal policy, setting a leading example for other cities.
Representatives from both the public sector and civil society unanimously agreed that governments should prioritize open source software to reduce dependence on proprietary technologies.
π¬ On April 8, the Free Software Foundation Europe (FSFE) hosted the "Public Money? Public Code!" conference in Germany, highlighting the importance of public sector procurement of Free and Open Source Software (FOSS) in achieving digital sovereignty and fostering innovation.
Thanks @ospoalliance.bsky.social made this awesome handbook and if you are willing to contribute on it please contact #OSPO Alliance.
offering a comprehensive strategy for using and managing open source software in the modern enterprise.
π Read the Open Source Good Governance Handbook: dub.sh/OSPO-GGI-ZHTW
The Open Source Good Governance Handbook, co-translated by OCF, introduces a framework based on open source supply chain governance. It helps organizations design processes, ensure legal compliance, manage risks, and foster technical collaborationβ
Governing open source is about building cross-functional, open collaboration within the organization. Itβs not just a technological transformation, but a governance transformation.
π§’ Executives and decision-makers β overarching open source strategy, mobilizing support for the OSPO, cross-department communication
π§’ Legal and compliance departments β license review and compliance, risk assessment
π§’ HR and management β incentives to give back to the community, developing open source talent
π§’ Procurement and admin teams β adjusting procurement strategies and workflows
The Open Source Good Governance Handbook notes that a mature OSPO (Open Source Program Office) should be able to coordinate across:
π§’ Engineering teams β tool selection, maintenance and contribution, security management
How an organization manages, uses, and contributes to open source isnβt just the responsibility of engineers. From choosing which open source tools to adopt, ensuring license compliance, encouraging team contributions, to setting internal policiesβall of these are part of open source governance.