Dirk Riehle
See the following -
Inner-Sourcing: Adopting Open Source Development Processes In Corporate IT
Today, we are hearing from customers more and more frequently that they want to gain the benefits of open source community-style collaborative development inside their corporate development organizations – what Tim O’Reilly has called “inner-sourcing.” Read More »
- Login to post comments
The Cyber Resilience Act Introduces Uncertainty And Risk Leaving Open Source Projects
What might happen if the uncertainty persists around who is held responsible under the Cyber Resilience Act (CRA)? The global Open Source community is averse to legal risks and generally lacks access to counsel, so it’s very possible offers of source code will simply be withdrawn rather than seeking to resolve the uncertainty. The CRA rightly addresses the need for commercial suppliers to protect their customers from exploits and cyber attacks. But legislators have exposed the open development of software itself to the regulations rather than just the for-profit use of Open Source artifacts in the marketplace. They are incorrectly assuming that Dirk Riehle’s terminology calling single-company projects “commercial Open Source” means it’s possible to use the “commerciality” of an application to distinguish single-company activity from community projects, and by using the concepts of proprietary software to then define boundaries.
- Login to post comments
To Be Permissive Or Not To Be Permissive, That Is The Question For Open Source Licensors
A new study of open source project growth suggests that choosing a permissive license can help your community to grow faster...
- Login to post comments
Why You Should Fork Your Next Open-Source Project
Code forks, rarely used, turn out to be remarkably effective at driving innovation, so why don't we use them more? Matt Asay explains...
- Login to post comments