From: Stefan Schantl <stefan.schantl@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: An AI Usage Policy for IPFire
Date: Sun, 25 Jan 2026 18:38:23 +0100 [thread overview]
Message-ID: <53ba3fe3aa6c9384fb1e5c5dc547802dd9558baa.camel@ipfire.org> (raw)
In-Reply-To: <825C0B91-4C7B-4352-9469-4148E6337AA0@ipfire.org>
Hello Michael,
thanks for working this out.
I've read through the document and it is very good written. Similar to
Adolf I would clarify a bit more what a "Pull request" is and what kind
of requests we accept and which not.
Best regards,
-Stefan
> Hello everyone,
>
> While eating my lunch today I stumbled over the AI Usage Policy that
> the Ghostty project has come up with. I quite liked it and I think
> that IPFire should also have a policy for AI usage in place. We have
> not received such an overwhelming amount of AI-generated patches
> unlike Ghostty and cURL, but we have received some that have been
> very low quality and when asked questions, the person who submitted
> this patch raised his hands and dropped out. This is just a waste of
> time for everyone involved.
>
> This policy that I have slightly adapted for IPFire demands that any
> kind of AI usage is allowed, but has to be disclosed. The point is to
> avoid any kind of low-quality, time-wasting submissions. I too
> believe that we should make this known upfront so that we can all be
> on the same page and make the job easy for us in case we need to
> reject any kind of patch submission.
>
> On the other hand, the policy is encouraging AI usage as there are
> indeed tasks where AI can help. But just because it is AI-generated
> does not mean that something is good.
>
> I would like you all to have a look at this and see if this is
> working for you as well or if you would like to have any changes made
> to it:
>
> https://www.ipfire.org/docs/devel/ai-policy
>
> All the best,
> -Michael
next prev parent reply other threads:[~2026-01-25 17:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 14:48 Michael Tremer
2026-01-23 17:30 ` Adolf Belka
2026-01-23 17:50 ` Michael Tremer
2026-01-23 18:13 ` Adolf Belka
2026-01-25 17:38 ` Stefan Schantl [this message]
2026-01-26 17:13 ` Michael Tremer
2026-01-26 20:17 ` Re[2]: " Jon Murphy
2026-01-27 10:37 ` Michael Tremer
2026-01-26 20:21 ` Adolf Belka
2026-01-27 10:45 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53ba3fe3aa6c9384fb1e5c5dc547802dd9558baa.camel@ipfire.org \
--to=stefan.schantl@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox