-
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
-
Diving in to Open Source supply chain; connecting and collaborating with communities
After one month at OSI, I’ve started forming a full picture of supply chain compliance and security ecosystem.
-
Open Source Approved License® registry project underway with help of intern, Giulia Dellanoce
I shared last month the details of the new OSI website, hosted on WordPress. One of the main drivers for…
-
Why the European Commission must consult the Open Source communities
A crucial problem with the Impact Assessment of the Cyber Resilience Act (CRA) is that no Open Source communities or…
-
2023 State of Open Source Report: key findings and analysis
I joined Javier Perez on a webinar reviewing the results of the 2023 State of Open Source survey, a collaborative effort…
-
Results of 2023 elections of OSI board of directors
The polls just closed, the results are in. Congratulations to the returning directors Aeva Black, and Catharina Maracke, and the…
-
OSI to hold License Clinic
OSI is pleased to announce our 2023 Open Source Initiative License Clinic, an in-person event to be held April 4th…
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