On Fri, Nov 24, 2023 at 07:55:01AM -0600, Gunnar Wolf wrote:
> Hello Bart,
Hi Gunnar!
>
> Bart Martens dijo [Wed, Nov 22, 2023 at 07:16:48PM +0100]:
> > Hello, I hereby welcome seconds for adding this text to 2023/vote_002
> > as a separate proposal.
>
> Thanks for your contribution to this discussion!
And thank you for your feedback.
That is praphrasing my proposal rather roughly, but let's focus on the point
you want to make.
> That is
> true, but a fair answer from them (if we warrant it!) could be "We
> represent more people and wider interests than yours. Your SC is over
> a quarter of a century old. Update your SC to comply with the changing
> times". Which could even make sense! (although it would make Debian
> stop being Debian!)
>
> This reading is the main reason I'm not endorsing it, and still prefer
> our original proposal instead.
How would such hypothetical answer from the EU matter for preferring one
proposal over the other? I'm trying to understand your motive.
Allow me to point out some weak points in proposal A, motivating me to write my
separate proposal.
- 1.a. The phrase "with no legal restrictions" is incorrect in the sense that
FOSS uses legal restrictions for keeping it FOSS.
- 1.b. I read "Knowing whether software is commercial or not". It is, in my
understanding, about commercial use or non-commercial use.
- 1.b. Arguing that knowing what's commercial or not isn't feasible implies
accepting such distinction when the EU can give a practical legal definition.
- 1.c. Stopping development would not exempt the author from CRA. Stopping the
commercial use would.
- 1.d. This somewhat implies accepting CRA requirements for big companies.
- 2.a. Explaining that the 24h window would disrupt FOSS' well working system
of responsible disclosures of security issues, implies accepting that the
FOSS community would be legally required to provide security support.
- 2.b. Mentioning the efforts Debian is doing on security support in this
context implies accepting that Debian is required to do so.
- 2.d. I don't feel comfortable with mentioning that Debian supports activists
living under oppressive regimes.
- 2.e. Commercial companies can currently hide security issues in proprietary
software. One could argue that this is worse than downplaying when reporting.
- 3. Software development in the open is in fact making unfinished software
available on the market.
- 3. Asking to exempt unfinished software being developed in the open, implies
accepting that it becomes no longer exempt when it's ready for use.
- 4. This implies, almost states explicitly, accepting CRA requirements for big
companies.
I invite you to compare the two proposals on the points listed above. In short,
my proposal defends commercial use of FOSS and the usual liability disclaimers
in FOSS licenses.
To be clear, for avoiding misunderstandings, the EU regulation can be a good
thing, when it requires manufacturers of closed products to provide security
support for the pieces of FOSS they use in their products. Then we're talking
about compulsory liability for those close products as a whole. My focus aims
at protecting the liberty of not providing support whenever the users can help
themselves with the available source code.
Has my proposal sufficient seconds by now? If not... you know what to do.
Cheers,
Bart
>
> Greetings,
>
> - Gunnar.