4 ms·
I think some of these reactions are rather overstated. I can't find language that states that you're on the hook for software support and fines just because you
by jeroenhd 4y ago
I think some of these reactions are rather overstated. I can't find language that states that you're on the hook for software support and fines just because you pushed a patch to Github that one time. The text mostly objected to is:
> In order not to hamper innovation or research, free and open-source software
developed or supplied outside the course of a commercial activity should not be
covered by this Regulation. This is in particular the case for software, including its source code and modified versions, that is openly shared and freely accessible, usable, modifiable and redistributable. In the context of software, a commercial activity might be characterized not only by charging a price for a product, but also by charging a price for technical support services, by providing a software platform through which the manufacturer monetises other services, or by the use of personal data for reasons other than exclusively for improving the security, compatibility or interoperability of the software.
From context it reads like open source is excluded unless the company developing software is selling services in the EU, in which case I don't see why open source software would need to be treated any differently from closed source software.
I think it's very valid to object to the lack of a definition of what "free and open source" means (free as in speech or free as in mattress, for one). However, that doesn't seem to be the part that most of these companies object to.
"If we post the source, we don't have to follow the CRA" would probably just lead to source dumps of crapware so that the law can be ignored. The cynic in me says that many of these objections are from people who don't want to be forced to patch the software they sell.
Luckily, this is just a proposal for now. I see a lot of things I like in this proposal. Putting pressure on manufacturers to patch their shitty hardware might finally do something about the botnets of media players and security cameras that plague the modern internet.
- BlueTemplar 4y agoIt might cause issues at (today's) margins ?? You know, how with FLOSS software (IIRC) you MUST provide the source on request, but CAN demand to be paid for the inconvenience (hosting, bandwidth, shipping physical storage...) Seems like this wouldn't be an issue, but it would still be nice that this situation had been covered by the law. P.S.: GPL : https://www.gnu.org/philosophy/selling.html https://www.gnu.org/philosophy/selling.html "Distributing free software is an opportunity to raise funds for development. Don't waste it!" OS : https://opensource.org/osd/ https://opensource.org/osd/ "The license shall not restrict any party from selling or giving away the software [...]" (Emphasis mine, literally the first non-fluff phrase !)
- jeroenhd 4y agoThose terms are quite GPL specific. The payment you can demand under GPL explicitly isn't allowed to be a money maker. It's to cover the costs only. I wouldn't classify that as commercial and I'm not aware of any laws that would.
- denton-scratch 4y agoThat's not FLOSS; that's GPL.
- RHSeeger 4y ago> free and open-source software developed or supplied outside the course of a commercial activity That seems extremely ambiguous to me. What does "software developed or supplied outside the course of a commercial activity" mean. Is it all of the piece of software? What if you pay me to develop and submit some patches to a gnu project? That means that, at least in part, the project was not developed wholly "outside the course of a commercial activity". What about if I have a free and open source project, then you come along and pay me to make some changes you need. Is the whole project now covered by such a law?