From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [IPv6:::1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4dyQz43TKCz2y1f for ; Fri, 23 Jan 2026 18:13:20 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [IPv6:2001:678:b28::25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519) (Client CN "mail01.haj.ipfire.org", Issuer "R12" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4dyQz10Pphz2xKR for ; Fri, 23 Jan 2026 18:13:17 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4dyQz03j1sz1wh; Fri, 23 Jan 2026 18:13:16 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1769191996; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=6ppNR+27DAW7T/9gz8GG0QrFTJtjGSeuyeq2YnBxVpg=; b=upbUvK3xj1FSfkLuj1QrPOiGMWMgo6o4VwaAlQWe0B+MyLRyrf9xTUCQcLOW5tf8xwjTX5 99EjaAGKr6VdbNBg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1769191996; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=6ppNR+27DAW7T/9gz8GG0QrFTJtjGSeuyeq2YnBxVpg=; b=AfsO/68A4ymOwPunre6UyQuhbA4ABSFZuKGptLTb+FoxOHOdU99tXvDCMEbYM6CFD7wKsx A9hDyYApaW0UCNRWH4k0PX0+b2sQc0aXdI3ObmJALQOz9XaduJ5FnXgvGIvkOzV5kZvVlf pm6PvQaq9s5q4THIH2gOrRzW0qAOMjt0QXPaNglpzbRhegk+HN+4Tn+QzvwXU0jF56Pi8m OESOjqnJPo8CerZC4C5mx9LI7lJ8BKtUUbjlct/KChqxNL1VoFrQlc/HrJMsGs2E//HiFo 9ai9nnOMOcH7YS+sXri8se26cbraXcSPitdpH2nIgx5TI0bbEGPL2r8LWsnZFA== Message-ID: Date: Fri, 23 Jan 2026 19:13:13 +0100 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: MIME-Version: 1.0 Subject: Re: An AI Usage Policy for IPFire To: Michael Tremer Cc: "IPFire: Development-List" References: <825C0B91-4C7B-4352-9469-4148E6337AA0@ipfire.org> <737628a6-73c1-4c21-bb17-068bb250bd81@ipfire.org> <142BE0A0-8402-4051-AFE0-2950B718C9D2@ipfire.org> Content-Language: en-GB From: Adolf Belka In-Reply-To: <142BE0A0-8402-4051-AFE0-2950B718C9D2@ipfire.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi Michael, On 23/01/2026 18:50, Michael Tremer wrote: > Hello Adolf, > > Thanks for reviewing this. > >> On 23 Jan 2026, at 17:30, Adolf Belka wrote: >> >> Hi Michael, >> >> On 23/01/2026 15:48, Michael Tremer wrote: >>> 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: >> >> Most of it seems fine to me and I agree with it. > > Good! > >> The only concerns are that it refers to pull requests from external users but as far as I am aware we generally don't accept pull requests, certainly not in the GitHub repo. If any IPFire GitHub pull request has any merits then an IPFire developer has to take the pull request and convert it into an IPFire patch submission supplied to the IPFire Development mailing list. > > The original version used “Pull Request” whenever they talked about a contribution. We don’t normally use those, certainly not using GitHub. > > There is however some documentation about PRs in case there are huge patch sets. You know well how good Patchwork is with huge patch sets. It is documented here: > > https://www.ipfire.org/docs/devel/git/pull-requests > > We pretty much never use this, but that does not mean that we won’t in the future. So in this sense I kept pull request in one place of the policy. Actually we are talking about any kind of contribution. I hope the text is inclusive of all of this. I feel you are being too optimistic. I suspect any user looking at it will just think of the GitHub type of Pull Request. I feel that Pull Request in the two lines in the policy should be replaced by something related to Patch Submissions. > >> If the intent of pull request as mentioned in the AI Policy is different than what I have described above then it is not clear to me from the policy wording. > > We definitely don’t mean GitHub PRs. Those are shit and actually a huge contributor to why so many projects are receiving so many AI slop as they make these drive-by “contributions” so easy. Then I would say we should also have a section in the AI policy that says that we don't accept GitHub Pull Requests whether based on AI or not. Then there could be a link to the documentation about submitting patches. That way we close that door also via the AI Policy. Regards, Adolf. > > -Michael > >> Regards, >> >> Adolf. >> >> >>> https://www.ipfire.org/docs/devel/ai-policy >>> All the best, >>> -Michael >> >> >