Re: Super Simple AI Policy proposal

El dilluns, 16 de mar=C3=A7 del 2026, a les 9:18:15 (Hora est=C3=A0ndard d=
=E2=80=99Europa=20
central), Akseli va escriure:
> On 15 March 2026 16.34.37 EET, Akseli Lahtinen <[email protected]> wrot=
e:
> >On Sunday 15 March 2026 08:34:25 Eastern European Standard Time Jin Liu=
=20
wrote:
> >> Akseli Lahtinen <[email protected]> =E4=BA=8E2026=E5=B9=B43=E6=9C=88=
14=E6=97=A5=E5=91=A8=E5=85=AD 20:49=E5=86=99=E9=81=93=EF=BC=9A
> >>=20
> >> > Digging out this old thread, I wrote a draft in here:
> >> >=20
> >> > https://community.kde.org/Guidelines_and_HOWTOs/Maintainers_and_Cont=
rib
> >> > utions
> >> >=20
> >> > I did not expect it to already publish, but I welcome feedback + more
> >> > guidelines if needed.
> >> >=20
> >> > Best regards,
> >> > - Akseli
> >>=20
> >> 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")?
> >
> >Maybe I could word it differently. What I mean with "Avoid" is that
> >we should try to strive for using our own tools or any other open tools
> >over proprietary tools.
> >
> >What would be good way to write it?
> >
> >"Prefer FOSS tooling?"
> >
> >> 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.
> >>=20
> >> -Jin
> >
> >Best regards,
> >- Akseli
>=20
> I updated this part to make it bit more clear

That section still needs a rewrite.

There's two different kind of tools:

A) Tools everyone has to use
B) Tools you are using in your computer and don't leak to anyone else

=46or B you can use whatever you want (assuming the tools don't place=20
restrictions on the output you generate)
=46or A the tools MUST be free software. [*]

Example:
 * You can use coverity if you want to scan for code issues, that's a YOU=20
thing
 * You can not commit a photoshop file to the repository and say "this is t=
he=20
icon of the app", since you are forcing everyone that wants to change the i=
con=20
to use photoshop

Cheers,
  Albert

* I guess with the exception of stuff like "well on windows you use MSVC=20
compiler"