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 4f0FWG5JGtz331l for ; Mon, 26 Jan 2026 17:14:02 +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 4f0FWC1nH5z2xSM for ; Mon, 26 Jan 2026 17:13:59 +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 4f0FW93DDkz5fG; Mon, 26 Jan 2026 17:13:57 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1769447637; 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=optX3CNFL+SNPu2PPiPzzqFM8GWBEygcvclF3JZ+yqg=; b=JtFDDbZHVd5owYL4TksXRgmCCR+mdrf0xcRX2fHOuI6xg9QYqVVo1G/e054KvUkeP65DAf SC1UW86rmBxr2QAg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1769447637; 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=optX3CNFL+SNPu2PPiPzzqFM8GWBEygcvclF3JZ+yqg=; b=Gk3CAADLneoCObAKDKfv4njZRcuVFfu6LCoyPX9vsFz22TKUi1jOcAWRM/OyMPQ/5Sndez /IE7Enh4pFZC4a/69gbRJy/q9SM8hAh8D93D58qFvBsymVdepSfRzbkvwnlku9CwqIIR7f nf/CVpEmP6Dsyrzjj7tKXfT2hWGD5AImIq5HTQ97Cjnpf+4EXXTfdX9rj0aGjGUCRbHcSt dxVq5u06kIZop9ZhJDFvRYjmTuEg51J8tiS/rOOgPztniXTLxX42dXhipnQarnT5u85cCx sXgqu8MWzS2jaBz2XyEtjP1ap95LuqYifrfOYsgfCnWLtaars3wG4QMz3N/plQ== Content-Type: text/plain; charset=utf-8 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 From: Michael Tremer In-Reply-To: <53ba3fe3aa6c9384fb1e5c5dc547802dd9558baa.camel@ipfire.org> Date: Mon, 26 Jan 2026 17:13:56 +0000 Cc: development@lists.ipfire.org Content-Transfer-Encoding: quoted-printable Message-Id: <73B417BD-FF07-4721-8BAA-101A5087C53D@ipfire.org> References: <825C0B91-4C7B-4352-9469-4148E6337AA0@ipfire.org> <53ba3fe3aa6c9384fb1e5c5dc547802dd9558baa.camel@ipfire.org> To: Stefan Schantl Hello, Sorry for not replying any earlier=E2=80=A6 I wanted to write up some more thoughts about basically closing our = GitHub account. This has been a long standing thought that I had since a = lot of Open Source projects have taken this step. Possibly for other = reasons, but I don=E2=80=99t believe that we are benefitting much from = our GitHub account at all. So initially we started this because we wanted to make sure that IPFire = will be available to more people. A GitHub search won=E2=80=99t show us = unless we have a copy of our repository, and it was also intended as a = backup in case our Git server is down for a moment. The backup is probably the only thing that is still a valid argument to = me. Otherwise, we have no option to disable PRs and we have seen a lot = of people who have always been ignoring any hints or even willingly went = against it and still opened any issues and PRs there. This has just = created extra work with no noticeable outcome. Other open source projects are prominently moving away from GitHub = because of Microsoft=E2=80=99s influence and although this argument is = not as strong for as because we are not using GitHub as our primary = space for any sources, I agree with the intentions of those projects. Initially I thought that we should only remove the ipfire-2.x = repository, but now looking at it again, I don=E2=80=99t see why else we = would host anything there whatsoever. Currently we have libloc and ddns = copied there, too: https://github.com/orgs/ipfire/repositories Does anyone have any feelings about this? Should we just close it and = therefore the whole PR problem in the test is resolving itself somewhat? -Michael > On 25 Jan 2026, at 17:38, Stefan Schantl = wrote: >=20 > Hello Michael, >=20 > thanks for working this out. >=20 > 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. >=20 > Best regards, >=20 > -Stefan >> Hello everyone, >>=20 >> 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. >>=20 >> 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. >>=20 >> 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. >>=20 >> 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: >>=20 >> https://www.ipfire.org/docs/devel/ai-policy >>=20 >> All the best, >> -Michael >=20