Re: JNIPort - is there anyone willing to maintain it?

--0000000000005e8e1c064234e201
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

This license is so ridiculous that I would not even bother to try it, and
use Pharo instead.Even for private I would want to publish my stuff in a
private Github repository.

Am Di., 28. Okt. 2025 um 08:41 Uhr schrieb Joachim Geidel <
[email protected]>:

> Hi Jeremy,
>
> good to hear that Cincom Smalltalk is available for personal use again!
>
> However, there are three rules in the Personal Use License which make it
> impossible to use CST for developing or maintaining any non-profit open
> source project like JNIPort.
>
> I am sure that Cincom=E2=80=99s legal department has all the best intenti=
ons to
> protect Cincom=E2=80=99s intellectual property. However, what=E2=80=99s C=
incom=E2=80=99s position
> regarding non-profit open source projects? Should the developers contact
> Cincom to get an individual permission to use Cincom Smalltalk for the
> project, or are they supposed to buy a commercial license if they don=E2=
=80=99t
> already have one?
>
> This is the rule which explicitly forbids open source development under
> the PUL, and there are no exemptions in the license text:
>
> =E2=80=9E1.6 =E2=80=A6 Any code, components or software developed using t=
he Product under
> this license must remain strictly for Your personal use.=E2=80=9C
>
> This clearly prohibits to use CST for developing anything which is
> published in any form and for any purpose, including contributions to CST=
.
>
> The next one even prohibits the use of CST for just reviewing or debuggin=
g
> code of someone else=E2=80=99s open source project and telling the author=
 about
> your findings:
>
> =E2=80=9E1.3 =E2=80=A6 You may not use the Product to =E2=80=A6 support a=
ny external projects,
> regardless of whether compensation is involved.=E2=80=9C
>
> And this one makes it complicated to use common Smalltalk development
> practices in an open source project:
>
> =E2=80=9E1.6 =E2=80=A6 If any portion of the Product is provided in sourc=
e code form, You
> may view, study and modify such code solely for personal, non-commercial
> exploration or experimentation on Your local devices. You may not: (i)
> publish or share the source code or any modifications; (ii) upload it to
> any public or private repository (e.g., GitHub, GitLab, Bitbucket); (iii)
> include it in any project, product or system intended for commercial use =
or
> distribution; or (iv) use it to create derivative works that are shared,
> sublicensed or deployed outside of Your own private use.=E2=80=9C
>
> It is often necessary to override a method by implementing a modified
> version of the method in a subclass, or directly override a method in an
> existing class (although I avoid that if I can). However, such a method
> can=E2=80=99t be included in an open source project, as this is not =E2=
=80=9Efor personal,
> non-commercial exploration or experimentation on Your local devices=E2=80=
=9C, and
> it is not allowed to publish such code =E2=80=9Eto any public or private
> repository=E2=80=9C. Which by the way also excludes the Cincom Public Rep=
ository.
>
> Best regards
> Joachim Geidel
>
>
> > Am 08.10.2025 um 18:16 schrieb Jordan, Jeremy <[email protected]>:
> >
> > Yes, Colin!  You are correct and we are very excited to announce PUL 9!
> In case any of you aren't on the Cincom Smalltalk Digest newsletter
> subscription, here's the announcement we put out on Tuesday of last week:
> >
> > PUL 9: A Giant Leap Forward: Now Compatible with macOS!
> >
> > Cincom is excited to announce PUL 9, a groundbreaking upgrade that
> brings full macOS compatibility to our personal use non-commercial licens=
e
> version that empowers developers to build and maintain applications
> seamlessly across platforms.
> >
>
>

--0000000000005e8e1c064234e201
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>This license is so=C2=A0ridiculous that I would not e=
ven bother to try it, and use Pharo instead.Even for private I would want t=
o publish my stuff in a private Github repository.</div></div><br><div clas=
s=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_att=
r">Am Di., 28. Okt. 2025 um 08:41=C2=A0Uhr schrieb Joachim Geidel &lt;<a hr=
ef=3D"mailto:[email protected]">[email protected]</a>&gt;:<br=
></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;=
border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Jeremy,<br>
<br>
good to hear that Cincom Smalltalk is available for personal use again!<br>
<br>
However, there are three rules in the Personal Use License which make it im=
possible to use CST for developing or maintaining any non-profit open sourc=
e project like JNIPort.<br>
<br>
I am sure that Cincom=E2=80=99s legal department has all the best intention=
s to protect Cincom=E2=80=99s intellectual property. However, what=E2=80=99=
s Cincom=E2=80=99s position regarding non-profit open source projects? Shou=
ld the developers contact Cincom to get an individual permission to use Cin=
com Smalltalk for the project, or are they supposed to buy a commercial lic=
ense if they don=E2=80=99t already have one?<br>
<br>
This is the rule which explicitly forbids open source development under the=
 PUL, and there are no exemptions in the license text:<br>
<br>
=E2=80=9E1.6 =E2=80=A6 Any code, components or software developed using the=
 Product under this license must remain strictly for Your personal use.=E2=
=80=9C<br>
<br>
This clearly prohibits to use CST for developing anything which is publishe=
d in any form and for any purpose, including contributions to CST.<br>
<br>
The next one even prohibits the use of CST for just reviewing or debugging =
code of someone else=E2=80=99s open source project and telling the author a=
bout your findings:<br>
<br>
=E2=80=9E1.3 =E2=80=A6 You may not use the Product to =E2=80=A6 support any=
 external projects, regardless of whether compensation is involved.=E2=80=
=9C<br>
<br>
And this one makes it complicated to use common Smalltalk development pract=
ices in an open source project: <br>
<br>
=E2=80=9E1.6 =E2=80=A6 If any portion of the Product is provided in source =
code form, You may view, study and modify such code solely for personal, no=
n-commercial exploration or experimentation on Your local devices. You may =
not: (i) publish or share the source code or any modifications; (ii) upload=
 it to any public or private repository (e.g., GitHub, GitLab, Bitbucket); =
(iii) include it in any project, product or system intended for commercial =
use or distribution; or (iv) use it to create derivative works that are sha=
red, sublicensed or deployed outside of Your own private use.=E2=80=9C<br>
<br>
It is often necessary to override a method by implementing a modified versi=
on of the method in a subclass, or directly override a method in an existin=
g class (although I avoid that if I can). However, such a method can=E2=80=
=99t be included in an open source project, as this is not =E2=80=9Efor per=
sonal, non-commercial exploration or experimentation on Your local devices=
=E2=80=9C, and it is not allowed to publish such code =E2=80=9Eto any publi=
c or private repository=E2=80=9C. Which by the way also excludes the Cincom=
 Public Repository.<br>
<br>
Best regards<br>
Joachim Geidel<br>
<br>
<br>
&gt; Am 08.10.2025 um 18:16 schrieb Jordan, Jeremy &lt;<a href=3D"mailto:JJ=
[email protected]" target=3D"_blank">[email protected]</a>&gt;:<br>
&gt; <br>
&gt; Yes, Colin!=C2=A0 You are correct and we are very excited to announce =
PUL 9!=C2=A0 In case any of you aren&#39;t on the Cincom Smalltalk Digest n=
ewsletter subscription, here&#39;s the announcement we put out on Tuesday o=
f last week:<br>
&gt; <br>
&gt; PUL 9: A Giant Leap Forward: Now Compatible with macOS!<br>
&gt; <br>
&gt; Cincom is excited to announce PUL 9, a groundbreaking upgrade that bri=
ngs full macOS compatibility to our personal use non-commercial license ver=
sion that empowers developers to build and maintain applications seamlessly=
 across platforms.<br>
&gt; <br>
<br>
</blockquote></div>

--0000000000005e8e1c064234e201--