Super Simple AI Policy proposal
Akseli
akselmo at akselmo.dev
Mon Mar 16 08:18:15 GMT 2026
On 15 March 2026 16.34.37 EET, Akseli Lahtinen <akselmo at akselmo.dev> wrote:
>On Sunday 15 March 2026 08:34:25 Eastern European Standard Time Jin Liu 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")?
>
>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.
>>
>> -Jin
>>
>
>Best regards,
>- Akseli
>
>
I updated this part to make it bit more clear
More information about the kde-core-devel
mailing list