Super Simple AI Policy proposal

[Chris Rizzitello]

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

On Sun, Mar 15, 2026, 2:34 AM Jin Liu <m.liu.jin at gmail.com> wrote:

> Akseli Lahtinen <akselmo at akselmo.dev> 于2026年3月14日周六 20:49写道：
> > Digging out this old thread, I wrote a draft in here:
> >
> >
> https://community.kde.org/Guidelines_and_HOWTOs/Maintainers_and_Contributions
> >
> > 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20260315/0d3a5655/attachment.htm>