OSS Strategy
Open Source Software (OSS) is today the primary site of technological innovation. A professional OSS strategy uses this ecosystem not merely as a consumer, but participates actively in shaping it. This secures influence over roadmaps, increases security, and strengthens the employer brand.
Innovation through openness means solving commodity problems together with the global community, freeing up your own resources for the actual business value.
Anti-Patterns: The Passive Consumer Role
- The Fork Trap: You modify an open-source project locally for your own purposes without contributing the changes back (Upstream). The result: you can never apply updates from the original project again without laboriously migrating your own changes.
- Strategic Blindness: You rely on an important library but realise too late that its development has been discontinued or is moving in an unfavorable direction.
- Fear of Reputation: Companies are afraid to publish code out of concern that it might not be good enough.
The Strategic Contribution
- Upstream First: Every improvement to an OSS component you use is offered primarily to the original project. This minimises your own maintenance costs.
- OSS Readiness: Establishing processes that allow developers to contribute to open source projects in a legally sound and straightforward way (see OSPO).
- Sponsorship: Targeted financial support for critical open-source projects on which your own infrastructure depends.
- Own Projects as Standard: Publishing internal tools as open source to make them the industry standard and receive external feedback.
- Community Management: Active dialogue with the developers and users of the projects that matter to your organisation.
The Advantage: Innovation Speed
By using and contributing to OSS, the organisation benefits from the innovations of thousands of developers worldwide — a pace no internal IT department can match on its own.
FAQ
Don't we lose our competitive advantage by sharing our code?
Only if you share your core algorithm. Most innovations happen in infrastructure, frameworks, or tools. Sharing these lowers your costs and increases your reputation as a technology leader.
How do we find time for Open Source contributions alongside project work?
We treat contributions to the projects we use as part of regular maintenance work. A Bugfix in the original project is more sustainable than a local Workaround.
Reference Guide
- Open Source Strategy (Linux Foundation): Comprehensive resources for organisations. linuxfoundation.org
- The OSPO Mind Map: Tasks and goals of an Open Source Program Office. todogroup.org
- Working in Public: Nadia Eghbal on the economics of open source. Stripe Press