From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from atuin.qyliss.net (localhost [IPv6:::1]) by atuin.qyliss.net (Postfix) with ESMTP id 347668E18; Wed, 05 Aug 2026 16:23:23 +0000 (UTC) Received: by atuin.qyliss.net (Postfix, from userid 993) id 958ED8E0E; Wed, 05 Aug 2026 16:23:21 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-26) on atuin.qyliss.net X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,DMARC_MISSING,RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H2, SPF_HELO_PASS autolearn=unavailable autolearn_force=no version=4.0.1 Received: from fout-a8-smtp.messagingengine.com (fout-a8-smtp.messagingengine.com [103.168.172.151]) by atuin.qyliss.net (Postfix) with ESMTPS id 7B1638E0D for ; Wed, 05 Aug 2026 16:23:20 +0000 (UTC) Received: from phl-compute-10.internal (phl-compute-10.internal [10.202.2.50]) by mailfout.phl.internal (Postfix) with ESMTP id B64D8EC02C4; Wed, 5 Aug 2026 12:23:19 -0400 (EDT) Received: from phl-frontend-03 ([10.202.2.162]) by phl-compute-10.internal (MEProxy); Wed, 05 Aug 2026 12:23:19 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alyssa.is; h=cc :cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm2; t=1785946999; x=1786033399; bh=MMuvrnX4BD fZD1VXMLuwzWox3bKmaXATfAba+6d7xPI=; b=hP2fQL2uZOA6VkhG7PI48RhsbB w9jrMejr5F1plWe+EUDrP6Es1ji/o+IRVX/Foulcu+nyWQx3/qT42wzViKLpFJoT g99sxeI/cQDo+ZUEKrUx3zd0zvNjlTKMnOjtHwm10A9dcFCNFZ8stTw50eQYzXRb n/I61st/yOxzMVZlK4w6U6JuF4R+eXDXkjCmzbs0cIYoKpO5FcdlyC1GTsdYsEYL NzL5DDTlEbbnis4zq4TWbs6E/fn44MMxePG2gxDtxTtpGOK1L3MQnHl1le/PT1zq 1mYyZXOvraT0V/RRlRnMHoudBY6bo6CJpSkOr3L4KyjG+ICMbuGLgfDU4z3Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t= 1785946999; x=1786033399; bh=MMuvrnX4BDfZD1VXMLuwzWox3bKmaXATfAb a+6d7xPI=; b=E6VqgxZayxt5M4/J/9lyh3uTCF8a8wat5c5LaKv3hOiWzmlir39 oaZhb31MUsDYF5YaGyZj+acawecVGVFSj2zG+sPJmCP3zNuFmF5mf/bJKdThGKhq fZiSXQ+UQm8UavVDzym4TT8VvkshFKBa6w6Ctw1s2JtFAAzyuNyNGabbUorsXdPe zIr4Kv6ZL5kecyOa/ujzw6sND3k4eFrPySJ+YhLQrGDO8/0EIhqjed+CDrfSsCQz D7n87REXg/3JC9D7FhayDZn1EvoczVP0aL/EVVxsoYtHR7Y6m5l9tKU+6ph4Xwls F+8lFBrfFO0oWeIwhO5Z6moN6G4u6T83KzA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: dmFkZTF7nhEUqmJyN4ojM6wHs9J7GEpMy2zWpkSH/a7Anv2ni60sVlsikae19kgZoutUEp V80bej2ukoMUdRlD04VX9475ODMCxLbI++06tE1Y228i4S0HtR0pWhUU3UhFzKbD/o9Nwz 6N1PrRXf5WYGoMeq+4FWzFkGhpMbVa8zdXiZHfrJ//Fhlk/+t46x8Fpw1Dn8BraiEFZgJn n9j7pCfLRvLYwkX6JIdJN4B6wp5MwKzIXRuWegcUNOVZXEsaANs/KeyeLeoeUxu8huj81n o7bj2DvZHXkzSxkc1z1HYYqiizf5HQYb4eSAQEWJYohaoJtPCZP3MC/r2C9AapAXAdoils qkMe1lz+gQDQv38cNThiNHsUWVwxkvVUh6kRqZySZSsVT8pBz65Vugjb/i2qXeDBrR8WxL d2ak+IGM7AmxpddaVP9uxuM0s5Ya2yssVe+B+URqJLUlZPQjQ4iQYTYsiDmHsY1ZpqTRTA i/InAY3QyhXmQUmMEwbp7yagBLx7WXheGgPB+3bSMSoJ0qCxVNA3qDNCAIQOwI28vv3NUR TxPonVn32ORk1SDT5TdBg2v4l7C3ylSRFGu8GDvDV4ykyLT8ZnJ0Q1tRAR5pMW3ujipcPC h4YQWL8f++LSsw27OzYv4wVetsiCXDISwZoiqOZmd4Eeh3hPl2Kn9L6EIUVw X-ME-Proxy: Feedback-ID: i12284293:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 5 Aug 2026 12:23:19 -0400 (EDT) Received: by fw12.qyliss.net (Postfix, from userid 1000) id A6583C78088B; Wed, 05 Aug 2026 18:23:17 +0200 (CEST) Date: Wed, 5 Aug 2026 18:23:17 +0200 From: Alyssa Ross To: Demi Marie Obenour Subject: Re: [PATCH] Documentation: document expectations around AI use Message-ID: References: <20260804164109.175987-2-hi@alyssa.is> <8fbfc3eb-7910-4570-bab7-064041483f8a@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="eh5q2ocs6lvymavu" Content-Disposition: inline In-Reply-To: <8fbfc3eb-7910-4570-bab7-064041483f8a@gmail.com> Message-ID-Hash: EDER2XUWKZOIH65XF3ZLYQXBCQ2AVELS X-Message-ID-Hash: EDER2XUWKZOIH65XF3ZLYQXBCQ2AVELS X-MailFrom: hi@alyssa.is X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-devel.spectrum-os.org-0; header-match-devel.spectrum-os.org-1; header-match-devel.spectrum-os.org-2; header-match-devel.spectrum-os.org-3; header-match-devel.spectrum-os.org-4; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: devel@spectrum-os.org, Valentin Gagarin , Vaida =?utf-8?B?UGxhbmt5dMSX?= , Yureka , colbyt X-Mailman-Version: 3.3.10 Precedence: list List-Id: Patches and low-level development discussion Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --eh5q2ocs6lvymavu Content-Type: text/plain; protected-headers=v1; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Subject: Re: [PATCH] Documentation: document expectations around AI use MIME-Version: 1.0 On Tue, Aug 04, 2026 at 04:58:45PM -0400, Demi Marie Obenour wrote: > On 8/4/26 12:41, Alyssa Ross wrote: > > It's been suggested to me a couple of times recently that having some > > statement about AI use in contributions would be helpful, for a couple > > of different reasons: > > > > =E2=80=A2 It resolves uncertainty contributors may feel about whether = their > > AI-assisted contributions will be welcome, since there is a wide > > range of acceptance among open source software projects currently. > > > > =E2=80=A2 It teaches people submitting assisted contributions to avoid > > pitfalls that might reduce the success of their contributions > > without otherwise having been obvious to them. > > > > =E2=80=A2 It protects against precious reviewer time being spent tryin= g to > > sift through verbose and confusing LLM-generated descriptions, > > which tends to be much less efficient for the reviewer. > > > > I've tried to keep it as simple and minimally invasive as possible, > > focusing on remedying specific problems that are likely to come up. > > Each expectation has a brief explanation, because I expect people will > > be happier following the guidance if they understand the reason for > > it, but I've avoided going into too much detail to keep it easy to > > read, understand and remember the whole thing. There's some slight > > deliberate ambiguity, because the important thing here is that people > > follow the spirit of the expectations. They don't need to get in the > > way in situations where it would obviously make sense to do something > > different; for example I can imagine certain situations where it > > would be useful to share some LLM-generated prose. > > > > Signed-off-by: Alyssa Ross > > --- > > We had a conversation about this on Matrix a little while ago, and I > > hope this captures the consensus we had at the time. > > > > I'm CCing everybody who's posted to the list recently (I think =E2=80= =94 sorry > > if I missed someone), because it's of course important to make sure > > there's broad awareness of and agreement on the expectations. > > > > I expect to apply this on top of my nav_order renumbering patch from > > earlier, so this would show up in the documentation index after > > "Communication channels" and before "Sending Your Patch", since it's > > important context for people to have before sending their first patch. > > > > Documentation/doc/contributing/ai.adoc | 23 +++++++++++++++++++++++ > > 1 file changed, 23 insertions(+) > > create mode 100644 Documentation/doc/contributing/ai.adoc > > > > diff --git a/Documentation/doc/contributing/ai.adoc b/Documentation/doc= /contributing/ai.adoc > > new file mode 100644 > > index 00000000..7535578e > > --- /dev/null > > +++ b/Documentation/doc/contributing/ai.adoc > > @@ -0,0 +1,23 @@ > > +=3D Use of AI in Spectrum contributions > > +:page-nav_order: 150 > > + > > +// SPDX-FileCopyrightText: 2026 Alyssa Ross > > +// SPDX-License-Identifier: GFDL-1.3-no-invariants-or-later OR CC-BY-S= A-4.0 > > + > > +Non-trivial Large Language Model (LLM) output in Spectrum contribution= s should > > +be clearly marked as such. > > +This is important context for reviewers, because humans and LLMs are p= rone to > > +different kinds of mistakes. > > + > > +LLM-generated prose is discouraged. > > +It tends to be overly verbose, and can be confusing because misunderst= andings or > > +false assumptions tend to be more difficult to spot in prose from LLMs= than from > > +humans.> + > > +Contributors should ensure they understand and are able to answer ques= tions about > > +contributions they submit, in their own words. > > +It's generally unhelpful to send LLM output in response to questions, = because it > > +can be expected that reviewers can ask LLMs questions themselves if LL= M-generated > > +answers would be useful to them. > > +If a reviewer asks a contributor a question, it's because they want th= at > > +contributor's answer, not an LLM's. > > > > base-commit: 9dc81e02d6382ef7fc89b9bb246a71ff0fcc68ff > > What about LLM translation and LLM spelling/grammar checkers? I think it would be difficult to argue that spelling/grammar checkers are non-trivial LLM output or produce LLM-generated prose, no? Translation I think is covered by "LLM-generated prose is discouraged." It's not forbidden, so people can use it if they really need to, but it's probably unhelpful in comparison to posting human generated text, even if that's in another language. That allows others who speak the language to understand the original, and non-speakers without access to a human speaker can use translation tools themselves, and with the original text even have the option to use multiple if one tool produces results that seem unclear or implausible. --eh5q2ocs6lvymavu Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQQGoGac7QfI+H5ZtFCZddwkt31pFQUCanNjdAAKCRCZddwkt31p FW/QAP9IPIGj8lkNuYrStYGtH+oibKGsATjPWX/r/e5NjNNtJwEA7ZqIU6yXIvlP OYGdSN/ShCgUvEXQqCIAuYmPG9yfIgs= =5JPC -----END PGP SIGNATURE----- --eh5q2ocs6lvymavu--