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 4dyQ1R6lWvz2y1f for ; Fri, 23 Jan 2026 17:30:19 +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 4dyQ1N376sz2xLt for ; Fri, 23 Jan 2026 17:30:16 +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) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4dyQ1M5Kvqz9P; Fri, 23 Jan 2026 17:30:15 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1769189415; 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=+mTnvFQmkunW8RL8ax5RJGan3/FEuTMLfok9BIxI0dI=; b=s8ttyExr7EB78TiUXMugLBepbnfVCn4+zHTSpO/b2dhEo9ItQPk0HOwK5tpaTYuk4joV02 hH9tPJDdp7rqrkAA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1769189415; 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=+mTnvFQmkunW8RL8ax5RJGan3/FEuTMLfok9BIxI0dI=; b=XidBCFtXy7RuZBJ6MqTzYiIDV4iNQnARgFuqIoudkj81ILRrfyc8gY3i2S6AKU5fviL6Pl t5ziY2ZmaVOI+ZhWN22rTuGw73AzWqjUWVLEecgkX9l9gzx8ZJRPv0ifLgnzI4lrcD58xY Cpjyw+nH0qbPvsCwG3Nf+cu2ItjJTvfda3AGdJL4GeCxnh8vMIOk2bh0KCkVtV+x9yMgPR 1vvp0tdoqYQySxCbdEdbBXwRa0zbfbBwgxsVctzD9uHkkJHWzD72Hf03NVtslak0eWsJp/ V2fAj5ItuL6WbRduRVxaaySVYol/9RnI/x7JjoSajaDyhS2a4hXZS2krBNA/3w== Message-ID: <737628a6-73c1-4c21-bb17-068bb250bd81@ipfire.org> Date: Fri, 23 Jan 2026 18:30:15 +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 References: <825C0B91-4C7B-4352-9469-4148E6337AA0@ipfire.org> Content-Language: en-GB Cc: "IPFire: Development-List" From: Adolf Belka In-Reply-To: <825C0B91-4C7B-4352-9469-4148E6337AA0@ipfire.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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. 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. 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. Regards, Adolf. > > https://www.ipfire.org/docs/devel/ai-policy > > All the best, > -Michael