-
Regulatory language cannot be the same for all software
In reviewing the language and concepts being used in the various draft bills and directives circulating in Brussels at present, it is clear that the experts crafting the language are using their understanding of proprietary software to build the protections they clearly intend for Open Source.
by
Simon Phipps
Recent Posts
-
Predictions in Open Source: Security, Mature Strategies, COSO, AI/ML
I joined Javier Perez and Rod Cope of Perforce in a webinar entitled Open Source Trends to Watch in 2023 where…
-
What’s next for OSI’s website
OSI’s website moved to a managed platform, laying the foundations for future improvements.
-
Open Source Initiative joins the Digital Public Goods Alliance
OSI to contribute to Digital Public Goods Alliance’s mission to address world’s most pressing economic challenges by furthering adoption of Open Source software.
-
2023, governments scrutinize Open Source
In 2022, we’ve seen a visible acceleration of interest in open source from governments around the world. Partially, this is…
-
The ultimate list of reactions to the Cyber Resilience Act
The European Commission’s proposed Cyber Resilience Act (CRA) as drafted may harm Open Source, and perhaps all other non-industrial software. A list of most relevant responses.
-
The License Review working group asks for community input on its recommendations
The License Review Working Group concluded its review of the license review process and is making recommendations for modification to the process. The next step is community review and input.
MOST VIEWED STORIES
-
Regulatory language cannot be the same for all software
-
Why open video is vital for Open Source
-
Webinar: ClearlyDefined proceeding towards a clear governance structure
-
Another issue with the Cyber Resilience Act: European standards bodies are inaccessible to Open Source projects
-
The Cyber Resilience Act introduces uncertainty and risk leaving Open Source projects confused
RECENT COMMENTS
CATEGORIES