Re: Super Simple AI Policy proposal
Akseli <[email protected]> Mon, 16 Mar 2026 10:18:15 +0200
| Newsgroups | gmane.comp.kde.devel.core |
|---|---|
| Message-ID | <[email protected]> |
On 15 March 2026 16=2E34=2E37 EET, Akseli Lahtinen <akselmo@akselmo=2Edev> = wrote: >On Sunday 15 March 2026 08:34:25 Eastern European Standard Time Jin Liu w= rote: >> Akseli Lahtinen <akselmo@akselmo=2Edev> =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=2Ekde=2Eorg/Guidelines_and_HOWTOs/Maintainers_and_C= ontributions >> > >> > I did not expect it to already publish, but I welcome feedback + more= guidelines if >> > needed=2E >> > >> > Best regards, >> > - Akseli >>=20 >> I'm unsure about the "Avoid proprietary tools" section=2E Say if someon= e >> 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=2E 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=2E > >What would be good way to write it? > >"Prefer FOSS tooling?" > >>=20 >> Or maybe it only applies if the contribution would introduce >> proprietary tools in the >> build process or future development work? E=2Eg=2E, when the contributi= on >> contains an art >> whose source format need a proprietary tool to edit=2E >>=20 >> -Jin >>=20 > >Best regards, >- Akseli > > I updated this part to make it bit more clear