-
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
-
It’s time to vote
It’s that time of year when the board confirms and renews its members. If you’re a full member of OSI…
-
Recap/Summary of the Digital Market Act workshop in Brussels
This Monday, I was in Brussels to attend a stakeholder workshop for the Digital Market Act (DMA) organized by the…
-
Meet the 2023 candidates for OSI’s board
The nominations for the Open Source Initiative board of elections just closed, March 6th. It’s time for voters to meet the candidates.
-
Why Open Source should be exempt from Standard-Essential Patents
With the European Commission soon to offer the Parliament a bill relating to Standard-Essential Patents (SEPs), it is worth taking time…
-
ClearlyDefined gets a new community manager with a vision toward the future
Nick Vidal has joined the project hosted by the Open Source Initiative (OSI) that helps Open Source projects thrive by putting essential licensing data at teams’ fingertips.
-
How OSI will renew its board of directors in 2023
The OSI board of directors will renew three of its seats with an open election process among its full individual members and affiliates.
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