3 ms·
> But it is stating the obvious: if you write free, open-source software, but you charge for support, then yes, you're engaging in a commercial activity! You ca
by AnthonyMouse 3y ago
> But it is stating the obvious: if you write free, open-source software, but you charge for support, then yes, you're engaging in a commercial activity! You cannot have your cake and eat it too.
It's the regulation which is trying to have its cake and eat it too.
There is a common model for open source development where you have a full-time project maintainer who is barely scraping by on donations and support contracts but these pay their salary, and then a large community that makes contributions. This works well because there is a lot of low-enjoyment and administrative work that needs to be done by someone but nobody wants to volunteer to do, but you can put this on a salaried employee and it makes the community possible.
Now if anyone does this they're put on the same footing as Samsung or Microsoft, which they don't have the resources for so they can't anymore. But they were the glue holding the rest of the community together, so the whole thing crumbles.
- em-bee 3y agoi think this is not relevant. if the maintainer is making money from support contracts he should be liable for those just as i am selling custom non-free software to my customers as a freelancer. do you think i have more resources than this maintainer? if anything we need a carve-out for freelancers or even small companies. i mean, how is this supposed to work? if sell support for a software i didn't write, should i be liable for the whole of it? on the other hand i see a potential positive effect too: commercial support is going to be more expensive. but i am not sure if it is possible make that work without some kind of price limit below which, the developer should not be liable.
- AnthonyMouse 3y agoThis isn't even a problem of carve outs, it's just a bad design. What you want here is something simple: Either the producer of the product provides security updates for as long as the product is in widespread use or they provide sufficient documentation and source code and such device access as is necessary for anyone to provide security updates. That works for everyone. If you're still actively supporting a product you're fine. You can stop supporting it whenever you want, but then you have to let anyone else do it. Producers of non-free software can stop supporting the product whenever they want by publishing the source code, or avoid publishing the source code for as long as they want by continuing to support the product. Open source developers will have satisfied the first option from the outset.