Re: [TCLCORE] GPL Licence in TCLLib added

[Arjen M. <Arj...@de...>]

Hi everyone,

I found an alternative implementation. While I have not studied it in any detail yet, it offers a variety of filters (low, high, band, …). So, it is richer in that respect than the one I had before 😊.

Regards,

Arjen

From: Arjen Markus via Tcl-Core <tcl...@li...>
Sent: woensdag 6 november 2024 14:41
To: Kevin Walzer <kw...@co...>; tcl...@li...
Subject: Re: [TCLCORE] GPL Licence in TCLLib added

Caution: This message was sent from outside of Deltares. Please do not click links or open attachments unless you recognize the source of this email and know the content is safe. Please report all suspicious emails to "Ser...@de...<mailto:Ser...@de...>" as an attachment.

Hi everyone,

I indeed intend to revise the code, so that no GPL dependency is left. The algorithms are simple enough to rewrite them from scratch.

(The idea of a separate library that contains contributions with a different and incompatible license might be worth elaborating, but that is a very different matter and should be discussed in some detail.)

Regards,

Arjen

From: Kevin Walzer <kw...@co...<mailto:kw...@co...>>
Sent: woensdag 6 november 2024 13:01
To: tcl...@li...<mailto:tcl...@li...>
Subject: Re: [TCLCORE] GPL Licence in TCLLib added

Caution: This message was sent from outside of Deltares. Please do not click links or open attachments unless you recognize the source of this email and know the content is safe. Please report all suspicious emails to "Ser...@de...<mailto:Ser...@de...>" as an attachment.


On 11/6/24 6:08 AM, Poor Yorick wrote:

> "Contagious" is a mischaracterization.  A project chooses derive its
> work from
> a GPL-licensed work or not.  It doesn't involuntarily "get infected".
> filtergen.tcl is licensed under the GPL, and if it disappears from
> Tcllib,
> where will it be placed?  Some other GPL analogue of Tcllib?  The
> point of
> Tcllib is to make it easier for projects to get their hands on
> software they
> want to use.  Why not then just have branch in Tcllib for such
> things?  Or even
> better just make the license clear and let projects choose for
> themselves what
> works from Tcllib they will use?

The obvious answer to this question is that filtergen.tcl will be
updated with a clean implementation not derived from GPL code, or it
will be removed altogether. That's exactly the choice that the GPL
requires.

The point of tcllib is indeed "to make it easier to projects to get
their hands on projects they want to use." But tcllib has already has a
license, the BSD-style Tcl licnese, and the GPL is not compatible with
this license from the standpoint of developer freedom. That is, if a
developer wants to make code proprietary/closed-source, then any
copyleft-licensed code must be avoided.

--Kevin
DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail.
DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail.