Re: Super Simple AI Policy proposal

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

Should we note that code generated by llm is of unknown license if any even
applies ?

On Sun, Mar 15, 2026, 2:34=E2=80=AFAM Jin Liu <[email protected]> wrote:

> Akseli Lahtinen <[email protected]> =E4=BA=8E2026=E5=B9=B43=E6=9C=8814=
=E6=97=A5=E5=91=A8=E5=85=AD 20:49=E5=86=99=E9=81=93=EF=BC=9A
> > Digging out this old thread, I wrote a draft in here:
> >
> >
> https://community.kde.org/Guidelines_and_HOWTOs/Maintainers_and_Contribut=
ions
> >
> > I did not expect it to already publish, but I welcome feedback + more
> guidelines if
> > needed.
> >
> > Best regards,
> > - Akseli
>
> I'm unsure about the "Avoid proprietary tools" section. Say if someone
> uses one of the
> proprietary (but free to use) IDEs from JetBrains, are we here just
> encouraging this
> person to try open source alternatives, or are we really asking the
> contributor to do
> so (like in "Check the licenses" or "Be patient")?
>
> Or maybe it only applies if the contribution would introduce
> proprietary tools in the
> build process or future development work? E.g., when the contribution
> contains an art
> whose source format need a proprietary tool to edit.
>
> -Jin
>

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

<div dir=3D"auto">Should we note that code generated by llm is of unknown l=
icense if any even applies ?=C2=A0</div><br><div class=3D"gmail_quote gmail=
_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, Mar 15, 202=
6, 2:34=E2=80=AFAM Jin Liu &lt;<a href=3D"mailto:[email protected]">m.liu=
[email protected]</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Aksel=
i Lahtinen &lt;<a href=3D"mailto:[email protected]" target=3D"_blank" rel=
=3D"noreferrer">[email protected]</a>&gt; =E4=BA=8E2026=E5=B9=B43=E6=9C=
=8814=E6=97=A5=E5=91=A8=E5=85=AD 20:49=E5=86=99=E9=81=93=EF=BC=9A<br>
&gt; Digging out this old thread, I wrote a draft in here:<br>
&gt;<br>
&gt; <a href=3D"https://community.kde.org/Guidelines_and_HOWTOs/Maintainers=
_and_Contributions" rel=3D"noreferrer noreferrer" target=3D"_blank">https:/=
/community.kde.org/Guidelines_and_HOWTOs/Maintainers_and_Contributions</a><=
br>
&gt;<br>
&gt; I did not expect it to already publish, but I welcome feedback + more =
guidelines if<br>
&gt; needed.<br>
&gt;<br>
&gt; Best regards,<br>
&gt; - Akseli<br>
<br>
I&#39;m unsure about the &quot;Avoid proprietary tools&quot; section. Say i=
f someone<br>
uses one of the<br>
proprietary (but free to use) IDEs from JetBrains, are we here just<br>
encouraging this<br>
person to try open source alternatives, or are we really asking the<br>
contributor to do<br>
so (like in &quot;Check the licenses&quot; or &quot;Be patient&quot;)?<br>
<br>
Or maybe it only applies if the contribution would introduce<br>
proprietary tools in the<br>
build process or future development work? E.g., when the contribution<br>
contains an art<br>
whose source format need a proprietary tool to edit.<br>
<br>
-Jin<br>
</blockquote></div>

--000000000000e3c7bf064d0fdb64--