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 4dyLRD177bz2ys7 for ; Fri, 23 Jan 2026 14:48:56 +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 server-signature ECDSA (secp384r1 raw public key) server-digest SHA384 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail01.haj.ipfire.org", Issuer "R12" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4dyLR84RFmz2xHm for ; Fri, 23 Jan 2026 14:48:52 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4dyLR65dg9znl; Fri, 23 Jan 2026 14:48:50 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1769179730; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=7uHMeBj4TTKOCmt0Lxj8IrtENU0VN0G1+0mt0J0uWIE=; b=auO9W7xtrzripZ8oSdo0BV4DEZ14k26SE43Y/nfmkdJYQfkEcoUqtt5MbAWN/myyAHmCux wpKKELtDUHAnwuDw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1769179730; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=7uHMeBj4TTKOCmt0Lxj8IrtENU0VN0G1+0mt0J0uWIE=; b=G4E4OYIjLDBjYFmcibVrfm5rShuvUVqewHQuy1g6ofKZVpqYe11xEKunutkWE1K8WerbHx KxQkTy0saYo7XAtuny3VTwtcHL7YwbJYB5vTLczNgmwCuAfFHZOmspDDGq5ONNMHeJlTCI 2XLh3IHxTJkiphKh87Yl+OMbDW46hNTpYYIke8UAWb6pIFXEy+KvJTQ1ENGN71GfIIiXGE MmdwNUrOX/sJaqjsD41q4SsjA8ddhPo7wU4F7QMubWtYr+YITDusQVVY9NWTDIJICRojd2 aZW8jKm7O9cbWI4N8Upp9/VpA2he/N5LfCobJ7Y/h52SPCN/oRxRYm05buv60g== From: Michael Tremer Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: Mime-Version: 1.0 Date: Fri, 23 Jan 2026 14:48:50 +0000 Subject: An AI Usage Policy for IPFire Message-Id: <825C0B91-4C7B-4352-9469-4148E6337AA0@ipfire.org> To: "IPFire: Development-List" 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=