Engagement Goal: Engaging with the OSS Ecosystem
In this page:
Scope
This Goal develops the corporate perspective. Contributing back to open source projects and supporting open source communities. Developing project visibility: communicating and participating in open source industry and community events. At this level, the enterprise engages with the OSS ecosystem and contributes to its sustainability.
Resources
Feel free to contribute for the benefit of all. Check out how to contribute.
Title | Description | Link |
|---|---|---|
| How an OSPO Can Help Your Engineers Give Back to Open Source | The case for contributing back at corporate level. "And in a war for talent, companies that embrace open source are more attractive to developers." | Web page |
| Decision factors for open source software procurement | Not new but still a great useful read by our colleagues at OSS-watch in the UK. Check out the slide deck at http://oss-watch.ac.uk/files/procurement.odp | Web page |
| 5 Open Source Procurement Best Practices | A recent 5' read on open source procurement with useful hints. | Web page |
| Commercializing open source | An investor's view of the community to business evolution of open source projects. | Web page |
| What is commercial open source software | A quick read to understand commercial open source. | Web page |
| Participating in Open Source Communities | A useful page from the Linux Foundation explaining why and how to join communities and contribute to projects. | Web page |
| The Art Of Community | A book by Jono Bacon providing a complete review about building a strong community around open source projects. | |
| 6 motivations for consuming or publishing open source software, Ben Balter | Extensive analysis of the reasons behind using and publishing open source software by the well known GitHub attorney and open source evangelist Ben Balter. | Web page |
| Awesome OSS Funding | A curated list of awesome resources for funding open source projects and authors. | Web page |
| The Secrets of Successful Open Source Business Models | An interesting article to find the right model for an open-source company. | Web page |
| CII Best Practices Badge Program | The Linux Foundation (LF) Core Infrastructure Initiative (CII) Best Practices badge is a way for Free/Libre and Open Source Software (FLOSS) projects to show that they follow best practices. | Web page |
| How to Support Open Source Projects Now | A short page with ideas on funding open source projects | Web page |
You must be logged in to contribute
Suggested content
Ecosystem stakeholders
- Foundations (that pay people to do work): FSF, ASF, Eclipse, Mozilla
- Organization & communities -> OW2, ...
- Distributors: Redhat, CentOS Linux, Debian, Canonical UBUNTU, CoreOS, CentOS
- Editors (enterprise licenses vs. community editions)
- Integrators
- Model without Editor
- Model with Editor
- Cloud actors
- Equipment manufacturers (cost cutting vs. upstream innovation and influence ...)
- Communication Service Providers
Business models
- Dual licensing ex. community addition is AGPL, enterprise edition "removes" the "share" conditions.
- Dual product model ex. open core
- Open Source Professional services
- Additional functions (is this open core?), patches ahead of public, patches back-ported to prior versions (ex. Oracle Java)
Myths & Stories
- Quality
- Security
- OSS Licensing and Legal Issues
- Support
Funding open source projects
- Best practices
- Experience sharing