tcl-core — Tcl Core Team discussions about Tcl development

Re: [TCLCORE] GPL Licence in TCLLib added

[Poor Y. <org...@po...>]

On 2024-11-06 23:08, Kevin Walzer wrote:
> But what organization would take that risk?

There's no risk.  The GPL goes to some length to articulate that point.

-- 
Yorick

Re: [TCLCORE] GPL Licence in TCLLib added

[Kevin W. <kw...@co...>]

<div><img width="1" height="1" src='https://fedbdhd.r.bh.d.sendibt3.com/tr/op/rdwe2XDx4Ud7y0e8TiwNWhjomL3yG8YDT8qsyqVIuFOxVKDZXM-7e_GlHZEK1Of5uOEewdeUhFVdlgvldAQ3QqLX7PAIrO74eD8L3JdItAVnW1aR6LoXgpZGAmMFrW38K1MOdvliVekMz4s4o_jLGVpOSLE7l8kCU3pbv4A03WnesZoho95jDdgN8K6neLCQaPqRB8_spzl2tvWojJotQtFyh3cqdqWG' /></div>But what organization would take that risk?<br/><br/>> On Nov 6, 2024, at 3:52 PM, Poor Yorick <org...@po...> wrote:<br/>> <br/>> A work that included Tcllib wholesale, but did not then itself use any GPL<br/>> licensed code from Tcllib, would not be de-facto in breach of the GPL.  The<br/>> only way the work would be considered derivative is if it depended functionally<br/>> on code licensed under the GPL<br/>

Re: [TCLCORE] GPL Licence in TCLLib added

[Poor Y. <org...@po...>]

On 2024-11-06 14:28, msc...@po... wrote:
> Am 06.11.2024 12:08 schrieb Poor Yorick:
>> 
>> "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?
> 
> It is indeed contagious in a certain way.
> 
> Tcllib gets distributed by various groups. Linux distros, commercial 
> programs etc.
> By including a (A)GPL licensed module, you suddenly make distribution 
> of the whole
> tcllib much much harder (or impossible) for lots of organisations, even 
> for unused modules,
> as GPL talks about distribution mostly.
> Thats contagious.
> 

A work that included Tcllib wholesale, but did not then itself use any 
GPL
licensed code from Tcllib, would not be de-facto in breach of the GPL.  
The
only way the work would be considered derivative is if it depended 
functionally
on code licensed under the GPL.

-- 
Yorick

Re: [TCLCORE] TIP 702 CFV Warning

[Jan N. <jan...@gm...>]

Op wo 6 nov 2024 om 14:05 schreef Harald Oehlmann:
> I would be in favour of the statical link and no requirement for
> "package require".

The current TIP #702 still requires "package require",
that's - IMHO - not what core commands should do.
They - at least - should do some auto-loading, like
"clock" does. That's one of my reasons for objecting
TIP #702.

Second: TIP #702 is sold as a solution to the creation
of temporary directories. It isn't: If someone zips
a "foo.dll" into the executable, loading this dll gives
exactly the same problem. Ticket [a8e4f76ce4] is
raised for that, it should be solved, whether
TIP #702 is accepted or not.

In my view, the dde and registry packages are
legacy, but used in many packages, simply
because there is no alternative. I started
with a new TIP #703, which can - eventually -
remedy this. The clock package need registry
to determine the timezone. msgcat needs the
registry for determining the locale. If there were
commands like "info timezone|locale" the
registry package would not be necessary
during startup any more for this purpose.

That's long enough for now.

Regards,
       Jan Nijtmans

Re: [TCLCORE] GPL Licence in TCLLib added

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

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...>
Sent: woensdag 6 november 2024 13:01
To: 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.

Re: [TCLCORE] TIP 702 CFV Warning

[Harald O. <har...@el...>]

Ashok,

I would be in favour of the statical link and no requirement for 
"package require".
In my daily life, that would make things easier.

Nevertheless, it would be great to get the temporary dll solved.

With starkits, I use the following startup-code which tries to delete 
all tcl temporary folders (with the dll's in).
If the current temp is taken, we get a "can not delete error" and it is 
not deleted. At least, the dll's of older runs are removed.

I have that somewhere on the wiki

   if {  $::tcl_platform(os) eq "Windows NT"
       && [info exists ::starkit::topdir]
   } {
     foreach name { TMP TEMP } {
       if { [info exists ::env($name)] } {
         foreach dir [glob -nocomplain -types d -directory $::env($name)\
"TCL\[0-9a-f\]\[0-9a-f\]\[0-9a-f\]\[0-9a-f\]\[0-9a-f\]\[0-9a-f\]\[0-9a-f\]\[0-9a-f\]"]\
         {
           catch { file delete -force -- $dir }
         }
       }
     }
   }


Thanks for all,
Harald

Am 06.11.2024 um 12:58 schrieb apnmbx-public--- via Tcl-Core:
> I plan to call for a vote on TIP 702 (statically linking regedit/dde) 
> couple of days from now. Please review and comment if not done yet.
> 
> The current mechanism (in the default build config with embedded zip) of 
> writing a DLL out to disk and loading it has issues on Windows as 
> described in the TIP. Static linking is proposed as a solution. If this 
> is not acceptable for whatever reason, at the very least, Jan’s proposal 
> of not including the DLL’s in the ZIP but instead shipping them 
> separately is an alternative that should be considered as the current 
> situation is the least desirable of the three options.
> 
> Personally, I prefer a single binary with all core functionality as that 
> was the whole purpose behind embedded ZIP’s but I could live with Jan’s 
> suggestion as well.
> 
> /Ashok

Re: [TCLCORE] GPL Licence in TCLLib added

[<msc...@po...>]

Am 06.11.2024 12:08 schrieb Poor Yorick:
> 
> "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?

It is indeed contagious in a certain way.

Tcllib gets distributed by various groups. Linux distros, commercial 
programs etc.
By including a (A)GPL licensed module, you suddenly make distribution of 
the whole
tcllib much much harder (or impossible) for lots of organisations, even 
for unused modules,
as GPL talks about distribution mostly.
Thats contagious.

Tcllib is not an package repository, where people pick modules for use, 
its usually distributed as a whole.

A second common pitfall is dependency management. If GPL licenses code 
is included in Tcllib,
any package require of another tcllib must be audited to ensure license 
compliance of the resulting combination.
Thats much easier with a common license for all involved packages.

Michael

P.S. But it might be a good idea to add explicit license identifiers 
like "# SPDX-License-Identifier: MIT" to the tcllib files to
ease automated license compliance reasoning. Then CI could check if the 
policy is kept.

Re: [TCLCORE] GPL Licence in TCLLib added

[Kevin W. <kw...@co...>]

<div><img width="1" height="1" src='https://fedbdhd.r.af.d.sendibt2.com/tr/op/TIJzNa2Aa0tln5NC8hptS0VD99fDxW6cnxez2TAYpYT_BNrf7evUp9nCtNnfLhVWbEczxFc7nlI9cXxFwBjonfKJ3nrqsPaE0RPTbAdzYg9xXMHrVvsgoR6fOKpqQSN2xiYLmGh7hRIqo5RokV8uL70WuGM8lTptN7G6OygLmErO0hwp-S-df0JS5ZjxfS3w77CG9KkeLJx_VCb46c245yqhv38fw-PT' /></div>On 11/6/24 6:08 AM, Poor Yorick wrote:<br/><br/>> "Contagious" is a mischaracterization.  A project chooses derive its <br/>> work from<br/>> a GPL-licensed work or not.  It doesn't involuntarily "get infected".<br/>> filtergen.tcl is licensed under the GPL, and if it disappears from <br/>> Tcllib,<br/>> where will it be placed?  Some other GPL analogue of Tcllib?  The <br/>> point of<br/>> Tcllib is to make it easier for projects to get their hands on <br/>> software they<br/>> want to use.  Why not then just have branch in Tcllib for such <br/>> things?  Or even<br/>> better just make the license clear and let projects choose for <br/>> themselves what<br/>> works from Tcllib they will use? <br/><br/>The obvious answer to this question is that filtergen.tcl will be <br/>updated with a clean implementation not derived from GPL code, or it <br/>will be removed altogether. That's exactly the choice that the GPL <br/>requires.<br/><br/>The point of tcllib is indeed "to make it easier to projects to get <br/>their hands on projects they want to use." But tcllib has already has a <br/>license, the BSD-style Tcl licnese, and the GPL is not compatible with <br/>this license from the standpoint of developer freedom. That is, if a <br/>developer wants to make code proprietary/closed-source, then any <br/>copyleft-licensed code must be avoided.<br/><br/>--Kevin<br/><br/>

[TCLCORE] TIP 702 CFV Warning

[<apn...@ya...>]

I plan to call for a vote on TIP 702 (statically linking regedit/dde) couple
of days from now. Please review and comment if not done yet.

 

The current mechanism (in the default build config with embedded zip) of
writing a DLL out to disk and loading it has issues on Windows as described
in the TIP. Static linking is proposed as a solution. If this is not
acceptable for whatever reason, at the very least, Jan's proposal of not
including the DLL's in the ZIP but instead shipping them separately is an
alternative that should be considered as the current situation is the least
desirable of the three options.

 

Personally, I prefer a single binary with all core functionality as that was
the whole purpose behind embedded ZIP's but I could live with Jan's
suggestion as well.

 

/Ashok

Re: [TCLCORE] GPL Licence in TCLLib added

[Poor Y. <org...@po...>]

On 2024-11-06 10:27, Arjen Markus via Tcl-Core wrote:
> Hi everyone,
> 
> I do not remember the actual conversion from the JavaScript original, 
> but as it is my code I will remove/replace this source file. GPL is 
> indeed contagious.
> 
> Regards,
> 
> Arjen
> 

"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?

-- 
Yorick

Re: [TCLCORE] GPL Licence in TCLLib added

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

Hi everyone,

I do not remember the actual conversion from the JavaScript original, but as it is my code I will remove/replace this source file. GPL is indeed contagious.

Regards,

Arjen

From: Brian Griffin <bri...@ea...>
Sent: dinsdag 5 november 2024 18:56
To: Kevin Walzer <kw...@co...>
Cc: Tcl Core List <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 Nov 5, 2024, at 08:39, Kevin Walzer <kw...@co...<mailto:kw...@co...>> wrote:


The strong tradition in Tcl is for non-copyleft code.

The more important reason for this is that GPL taints any code it touches. The consequence is that any commercial product built with Tcl embedded in it, is rendered effectively public domain. This is not a good revenue model for commercial software.

Considering that a lot of contributors and maintainers are also selling end products, It is critically important not to jeopardize those enterprises well being.

-Brian



> On Nov 5, 2024, at 11:15 AM, Poor Yorick wrote:
>
> On 2024-11-05 17:45, Jan Nijtmans wrote:
>> Op di 5 nov 2024 om 16:40 schreef Poor Yorick <
>> org...@po...<mailto:org...@po...>>:
>>> Since when is the GPL license not allowed?
>> See: Tcl Library Source Code: Documentation
>>
>> Section "Contributor":
>> As a contributor to Tcllib you are committing yourself to:
>> 1.
>> keep the guidelines written down in *Tcl Community - Kind Communication
>> *
>> in
>> your mind. The main point to take away from there is *to be kind to each
>> other*.
>> 2.
>> Your contributions getting distributed under a BSD/MIT license. For the
>> details see *Tcllib - License
>> *
>> Contributions are made by entering tickets into our tracker, providing
>> patches, bundles or branches of code for inclusion, or posting to the
>> Tcllib related mailing lists.
>> Regards,
>> Jan Nijtmans
>
> Aku added that documentation in 2019, so it's relatively new. Prohibiting the GPL means prohibiting the inclusion of works that are freely distributable, and probably useful to many users of Tcllib.
>
> --
> Yorick
>
>
> _______________________________________________
> Tcl-Core mailing list
> Tcl...@li...<mailto:Tcl...@li...>
> https://lists.sourceforge.net/lists/listinfo/tcl-core

_______________________________________________
Tcl-Core mailing list
Tcl...@li...<mailto:Tcl...@li...>
https://lists.sourceforge.net/lists/listinfo/tcl-core
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.

Re: [TCLCORE] GPL Licence in TCLLib added

[Brian G. <bri...@ea...>]

On Nov 5, 2024, at 08:39, Kevin Walzer <kw...@co...> wrote:



The strong tradition in Tcl is for non-copyleft code.

The more important reason for this is that GPL taints any code it touches. The consequence is that any commercial product built with Tcl embedded in it, is rendered effectively public domain. This is not a good revenue model for commercial software.

Considering that a lot of contributors and maintainers are also selling end products, It is critically important not to jeopardize those enterprises well being.

-Brian


> On Nov 5, 2024, at 11:15 AM, Poor Yorick wrote:
>
> On 2024-11-05 17:45, Jan Nijtmans wrote:
>> Op di 5 nov 2024 om 16:40 schreef Poor Yorick <
>> org...@po...>:
>>> Since when is the GPL license not allowed?
>> See: Tcl Library Source Code: Documentation
>>
>> Section "Contributor":
>> As a contributor to Tcllib you are committing yourself to:
>> 1.
>> keep the guidelines written down in *Tcl Community - Kind Communication
>> *
>> in
>> your mind. The main point to take away from there is *to be kind to each
>> other*.
>> 2.
>> Your contributions getting distributed under a BSD/MIT license. For the
>> details see *Tcllib - License
>> *
>> Contributions are made by entering tickets into our tracker, providing
>> patches, bundles or branches of code for inclusion, or posting to the
>> Tcllib related mailing lists.
>> Regards,
>> Jan Nijtmans
>
> Aku added that documentation in 2019, so it's relatively new. Prohibiting the GPL means prohibiting the inclusion of works that are freely distributable, and probably useful to many users of Tcllib.
>
> --
> Yorick
>
>
> _______________________________________________
> Tcl-Core mailing list
> Tcl...@li...
> https://lists.sourceforge.net/lists/listinfo/tcl-core

_______________________________________________
Tcl-Core mailing list
Tcl...@li...
https://lists.sourceforge.net/lists/listinfo/tcl-core

Re: [TCLCORE] [External] Re: GPL Licence in TCLLib added

[Poor Y. <org...@po...>]

On 2024-11-05 18:48, da Silva, Peter J                            
Collins wrote:
> If filtergen is derived from GPLed Javascript code, then it is GPLed.

The fact that filtergen.tcl is in Tcllib never bothered anyone, and I 
think
that's the right posture for Tcllib.  It's a convenient repository for
distributing free software.  Alternatively, one branch could be strictly 
for
works licensed under the MIT/Tcl license, and another branch could 
accomodate
other free software.

-- 
yorick

Re: [TCLCORE] GPL Licence in TCLLib added

[Kevin W. <kw...@co...>]

<div><img width="1" height="1" src='https://fedbdhd.r.af.d.sendibt2.com/tr/op/XjsMFyf9LUXxcleklQomEXWE_4Tw5vwiEbR29ctyokZNOwvG_M6kMORhdo6cXylb8tRIeEkO7ewNZRtNzr-qtuHMRqfNXfPaXwSE9D_VDM16BITnn4GtM3O0y9k4bHeXQU1Cd8pmQTPgI7GBzSPGA9bXDXBp-v7C39zjL8vAk7kYI6foCkSz7zY_-xipBSI60eIheRw2RC7uKIbzcFMCXuhM3GoyOESD' /></div>My vote would be no. <br/><br/>> On Nov 5, 2024, at 1:21 PM, Poor Yorick <org...@po...> wrote:<br/>> <br/>> There is no question here that official Tcl releases will be under the license<br/>> they always have been.  The question here is whether there is room in TCLLIB,<br/>> which is a collection of disparate software works, for a work licensed under<br/>> the GPL.<br/>

Re: [TCLCORE] GPL Licence in TCLLib added

[Poor Y. <org...@po...>]

On 2024-11-05 19:55, Brian Griffin wrote:
> On Nov 5, 2024, at 08:39, Kevin Walzer <kw...@co...> wrote:
> 
> 
> 
> The strong tradition in Tcl is for non-copyleft code.
> 
> The more important reason for this is that GPL taints any code it 
> touches. The consequence is that any commercial product built with Tcl 
> embedded in it, is rendered effectively public domain. This is not a 
> good revenue model for commercial software.
> 
> Considering that a lot of contributors and maintainers are also selling 
> end products, It is critically important not to jeopardize those 
> enterprises well being.
> 
> -Brian
> 
> 

There is no question here that official Tcl releases will be under the 
license
they always have been.  The question here is whether there is room in 
TCLLIB,
which is a collection of disparate software works, for a work licensed 
under
the GPL.

-- 
Yorick

Re: [TCLCORE] [External] Re: GPL Licence in TCLLib added

[da S. P. J C. <pet...@fl...>]

I would be EXTREMELY wary of allowing GPL code in the Tcl distribution. The TCL extension mechanism is quite good, after all that’s what it was designed for, and any code that isn’t able to be separately distributed as a separate extension is probably not safe to include because of the GPL interface-copyright (via their “derived works” language).

Re: [TCLCORE] [External] Re: GPL Licence in TCLLib added

[da S. P. J C. <pet...@fl...>]

If filtergen is derived from GPLed Javascript code, then it is GPLed.

Re: [TCLCORE] [External] Re: GPL Licence in TCLLib added

[da S. P. J C. <pet...@fl...>]

> modules/math/filtergen.tcl is GPL.

That needs to be replaced, then.

Re: [TCLCORE] GPL Licence in TCLLib added

[Kevin W. <kw...@co...>]

<div><img width="1" height="1" src='https://fedbdhd.r.bh.d.sendibt3.com/tr/op/a6URkgiuO-Y23YIGilJ_eF19Dbs5hCKLF6E0u4UMQ-ZDUO8oWizVe6uEEMZxAmfF1-30VjmFeXLOxacEKtlvcqDQlDbZfs4W-FBXSetwPogWtfPhwcjvyaV04Ns2kvzvboLy3ZLpdlg4cZFrHSA9cEECcDWl-B3jVjYm1jjFoBTRWL8-OF-GMqOQNtl7F8bJJjff_zM0c4oxnITyAQ08MaAe3UeDoGvy' /></div>The strong tradition in Tcl is for non-copyleft code. <br/><br/>> On Nov 5, 2024, at 11:15 AM, Poor Yorick <org...@po...> wrote:<br/>> <br/>> On 2024-11-05 17:45, Jan Nijtmans wrote:<br/>>> Op di 5 nov 2024 om 16:40 schreef Poor Yorick <<br/>>> org...@po...>:<br/>>>> Since when is the GPL license not allowed?<br/>>> See: Tcl Library Source Code: Documentation<br/>>> <https://core.tcl-lang.org/tcllib/doc/trunk/embedded/md/tcllib/files/devdoc/tcllib_devguide.md><br/>>> Section "Contributor":<br/>>> As a contributor to Tcllib you are committing yourself to:<br/>>>   1.<br/>>>   keep the guidelines written down in *Tcl Community - Kind Communication<br/>>>   <https://core.tcl-lang.org/tcllib/doc/trunk/embedded/md/tcllib/files/devdoc/tcl_community_communication.md>*<br/>>> in<br/>>>   your mind. The main point to take away from there is *to be kind to each<br/>>>   other*.<br/>>>   2.<br/>>>   Your contributions getting distributed under a BSD/MIT license. For the<br/>>>   details see *Tcllib - License<br/>>>   <https://core.tcl-lang.org/tcllib/doc/trunk/embedded/md/tcllib/files/devdoc/tcllib_license.md>*<br/>>> Contributions are made by entering tickets into our tracker, providing<br/>>> patches, bundles or branches of code for inclusion, or posting to the<br/>>> Tcllib related mailing lists.<br/>>> Regards,<br/>>>        Jan Nijtmans<br/>> <br/>> Aku added that documentation in 2019, so it's relatively new.  Prohibiting the GPL means prohibiting the inclusion of works that are freely distributable, and probably useful to many users of Tcllib.<br/>> <br/>> --<br/>> Yorick<br/>> <br/>> <br/>> _______________________________________________<br/>> Tcl-Core mailing list<br/>> Tcl...@li...<br/>> https://lists.sourceforge.net/lists/listinfo/tcl-core<br/>

Re: [TCLCORE] GPL Licence in TCLLib added

[Poor Y. <org...@po...>]

On 2024-11-05 17:45, Jan Nijtmans wrote:
> Op di 5 nov 2024 om 16:40 schreef Poor Yorick <
> org...@po...>:
> 
>> Since when is the GPL license not allowed?
>> 
> 
> See: Tcl Library Source Code: Documentation
> <https://core.tcl-lang.org/tcllib/doc/trunk/embedded/md/tcllib/files/devdoc/tcllib_devguide.md>
> Section "Contributor":
> 
> As a contributor to Tcllib you are committing yourself to:
> 
>    1.
> 
>    keep the guidelines written down in *Tcl Community - Kind 
> Communication
>    
> <https://core.tcl-lang.org/tcllib/doc/trunk/embedded/md/tcllib/files/devdoc/tcl_community_communication.md>*
> in
>    your mind. The main point to take away from there is *to be kind to 
> each
>    other*.
>    2.
> 
>    Your contributions getting distributed under a BSD/MIT license. For 
> the
>    details see *Tcllib - License
>    
> <https://core.tcl-lang.org/tcllib/doc/trunk/embedded/md/tcllib/files/devdoc/tcllib_license.md>*
> 
> Contributions are made by entering tickets into our tracker, providing
> patches, bundles or branches of code for inclusion, or posting to the
> Tcllib related mailing lists.
> 
> 
> Regards,
> 
>         Jan Nijtmans

Aku added that documentation in 2019, so it's relatively new.  
Prohibiting the GPL means prohibiting the inclusion of works that are 
freely distributable, and probably useful to many users of Tcllib.

-- 
Yorick

Re: [TCLCORE] GPL Licence in TCLLib added

[Jan N. <jan...@gm...>]

Op di 5 nov 2024 om 16:40 schreef Poor Yorick <
org...@po...>:

> Since when is the GPL license not allowed?
>

See: Tcl Library Source Code: Documentation
<https://core.tcl-lang.org/tcllib/doc/trunk/embedded/md/tcllib/files/devdoc/tcllib_devguide.md>
Section "Contributor":

As a contributor to Tcllib you are committing yourself to:

   1.

   keep the guidelines written down in *Tcl Community - Kind Communication
   <https://core.tcl-lang.org/tcllib/doc/trunk/embedded/md/tcllib/files/devdoc/tcl_community_communication.md>*
in
   your mind. The main point to take away from there is *to be kind to each
   other*.
   2.

   Your contributions getting distributed under a BSD/MIT license. For the
   details see *Tcllib - License
   <https://core.tcl-lang.org/tcllib/doc/trunk/embedded/md/tcllib/files/devdoc/tcllib_license.md>*

Contributions are made by entering tickets into our tracker, providing
patches, bundles or branches of code for inclusion, or posting to the
Tcllib related mailing lists.


Regards,

        Jan Nijtmans

Re: [TCLCORE] GPL Licence in TCLLib added

[Poor Y. <org...@po...>]

On 2024-11-05 17:27, Jan Nijtmans wrote:
> Op di 5 nov 2024 om 16:15 schreef Kevin Walzer:
> 
>> That means it should be removed, right?
>> 
> 
> I don't think so. Better ask Arjen Markus.
> 
> The "pyk", "mime" and "module-aes" branches, yes they
> should be removed (or modified to use the BSD license)
> 

Since when is the GPL license not allowed?

-- 
Yorick

Re: [TCLCORE] GPL Licence in TCLLib added

[Jan N. <jan...@gm...>]

Op di 5 nov 2024 om 16:15 schreef Kevin Walzer:

> That means it should be removed, right?
>

I don't think so. Better ask Arjen Markus.

The "pyk", "mime" and "module-aes" branches, yes they
should be removed (or modified to use the BSD license)

Regards,
    Jan Nijtmans

Re: [TCLCORE] GPL Licence in TCLLib added

[Kevin W. <kw...@co...>]

<div><img width="1" height="1" src='https://fedbdhd.r.bh.d.sendibt3.com/tr/op/f2ePDcw8puBEffnSdg78G_Kq82SaguK75cnYytO4YB3nyUTfXpDIA22D9gSzQqhmlRuo_hvqQq5PvQGo1qZSdH2qD6xdQSlPz99f3EP65GlTAyULBkxoUiYC2rHzBj7gd9K_t7hZbFG5Y4gOuKLX07YmHmsJZRyCP0BRBrGLxBF1fcUuYnVQaqU1isvctko0DbtZPlCK5d_37luL90Vy6KCr-wshbsT2' /></div>That means it should be removed, right?<br/><br/>> On Nov 5, 2024, at 9:49 AM, Poor Yorick <org...@po...> wrote:<br/>> <br/>> On 2024-11-05 16:39, Jan Nijtmans wrote:<br/>>> Op di 5 nov 2024 om 15:23 schreef Poor Yorick:<br/>>>> modules/math/filtergen.tcl is GPL.<br/>>> Well, I'm happy to report that filtergen.tcl is<br/>>> not GPL. It was derived from javascript code,<br/>>> which is GPL. The License for tcllib<br/>>> can be found in ./license.terms or in<br/>>> devdoc/tcllib_license.man<br/>>> Hope this helps,<br/>>>           Jan Nijtmans<br/>> <br/>> Uh... that makes filtergen.tcl GPL.<br/>> <br/>> --<br/>> yorick<br/>> <br/>> <br/>> _______________________________________________<br/>> Tcl-Core mailing list<br/>> Tcl...@li...<br/>> https://lists.sourceforge.net/lists/listinfo/tcl-core<br/>

Re: [TCLCORE] GPL Licence in TCLLib added

[Poor Y. <org...@po...>]

On 2024-11-05 16:39, Jan Nijtmans wrote:
> Op di 5 nov 2024 om 15:23 schreef Poor Yorick:
> 
>> modules/math/filtergen.tcl is GPL.
>> 
> 
> Well, I'm happy to report that filtergen.tcl is
> not GPL. It was derived from javascript code,
> which is GPL. The License for tcllib
> can be found in ./license.terms or in
> devdoc/tcllib_license.man
> 
> Hope this helps,
>            Jan Nijtmans

Uh... that makes filtergen.tcl GPL.

-- 
yorick