Re: Super Simple AI Policy proposal

Akseli Lahtinen <[email protected]> Sun, 15 Mar 2026 16:35:18 +0200
Newsgroups gmane.comp.kde.devel.core
Message-ID <5971669.DvuYhMxLoT@desktop>
On Sunday 15 March 2026 15:12:38 Eastern European Standard Time Chris Rizzi=
tello wrote:
> Should we note that code generated by llm is of unknown license if any ev=
en
> applies ?
>=20

If you can find proper legal documents for these things, I could link them =
to
the site, just so people can make the judgement call themselves.

> On Sun, Mar 15, 2026, 2:34=E2=80=AFAM Jin Liu <[email protected]> wrote:
>=20
> > Akseli Lahtinen <[email protected]> =E4=BA=8E2026=E5=B9=B43=E6=9C=881=
4=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_Contrib=
utions
> > >
> > > 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
> >
>=20

Best regards,
=2D Akseli