Working Group Folder
Slack channel #wg-oss-in-business
Follow-up happening during Thursday TODO Europe Touchpoint CallS
While the engineering-driven approach to open source is well-covered,a business-driven approach is less discussed but crucial for organizations to understand how open source can drive both innovation and financial value. This initiative was initiated as part of the TODO Group’s Touchpoint calls to create a guide to address the gap in knowledge and strategic guidance around open source adoption from a business-driven perspective.
Full proposal can be found here. Apporved proposal and rationale can be found here
- Provide businesses with tools to integrate open source into their core strategy.
- Help non-software-native companies (e.g., hardware or manufacturing) understand how open source can play a role in their business models.
- Educate business managers on the long-term investments required for successful open source strategies (e.g., building and nurturing open source communities).
| Glossary and Background - Existing frameworks and models | Engineering Driven vs. Business Driven Open Source | Misconceptions and Challenges | Communicating Engineering Benefits to Business Value | Case Studies and Success Stories | Future work and conclusion |
|---|---|---|---|---|---|
| Guide's purpose and audience | Definitions | Misconceptions managers have about open source | How to communicate open source benefits to business managers | Neutral collaboration: Stories from organizations like LF Energy’s OpenSTEF | Creating a living document that evolves with community input |
| Open source in modern business | Implementation strategies for business-driven | Addressing security concerns and support availability | Simplifying complex concepts for managerial understanding | Real-life examples to cluster open source suppliers to assess if they are open source first | Recap of the guide’s key points |
| Carl-Eric Mols' “Principles for Industrial Open Source” | Connecting the two perspectives for a holistic approach | Cyber Resilience Act (CRA) when publishing software | resources for managers to engage with open source effectively | Real-life examples that shares a system that enables organizations to asses “What do I want to reach by open-sourcing this?” | |
| Magnus presentation at FOSSNorth | How to properly budget or allocate resources for OSPOs? | ||||
| Mozilla archetypes and Heather Meeker’s frameworks |
To learn more about outline updates please visit the dedicated GH Discussions repo here
We are using TODO Touchpoints to allow people to share 5-minute presentations on potential content to include. If you’d like to participate, please consider joining the upcoming touchpoint call on the last Thursday of November 28th
- Define working repo Process / Roadmap / File issues by the community (Harmony)
- Open an Issue to include a new chapter title: "Transparent manageable risks in Open Source vs. Closed Source" (Ana)
- Review new PRs or Issues (All)
If you would like to catch up on motivation, interested participants involved, past discussions, and presentations shared, please read this GH Discussion thread. The Last comment is the most updated version to date
- Define workstreams/cluster of tasks and give them an order/priority. Make sure there are “owners” for each workstream
- Discuss if further follow-ups should be done in these meetings or need to allocate specific catch up calls/official working group under TODO