Re: We should require AI disclosure

--===============5216321710505180977==
Content-Type: multipart/signed; boundary="nextPartID4ic_yeTreJDJ0wLBurAw";
 micalg="pgp-sha512"; protocol="application/pgp-signature"

--nextPartID4ic_yeTreJDJ0wLBurAw
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; protected-headers="v1"
From: Goffi <[email protected]>
To: XMPP Standards <[email protected]>
Subject: Re: [Standards] We should require AI disclosure
Date: Tue, 07 Jul 2026 17:55:54 +0200
Message-ID: <[email protected]>
In-Reply-To: <[email protected]>
References: <[email protected]>
MIME-Version: 1.0

Hi,

This discussion is stalling.

Meanwhile, we've got specification(s?) which have been clearly written with=
 AI,=20
and I guess it will be more and more often the case.

As a reviewer with my council hat, I would really love to at least have=20
disclaimer when AI is used (is it for writing whole sections, to extract a=
=20
table, to write example, to check spelling/grammar).

Many big projects have a statement on AI use, e.g., CPython:
https://devguide.python.org/getting-started/ai-tools/

I think XSF should have one too.

Do we need more discussion on standard, or should the board discuss that an=
d=20
ask a team to work on a AI statement?

Thanks
Goffi


Le lundi 11 mai 2026, 09:50:19 heure d=E2=80=99=C3=A9t=C3=A9 d=E2=80=99Euro=
pe centrale Goffi a =C3=A9crit :
> Hello everybody,
>=20
> I would like to bring a discussion on AI policy. We can't really ignore=20
> anymore that modern models have become very capable, and I suspect that t=
hey=20
> are used for spec authoring.
>=20
> This raises, I believe, copyright issues: if someone use AI to redact a=20
whole=20
> section of a spec, how can we be sure that it's not an existing specs for=
=20
some=20
> other place, possibly under copyright, that is copied or paraphrased? How=
=20
can=20
> an author guarantee that it's original work (hint: they can't)?
>=20
> I think that there are 3 distinct uses:
>=20
> 1. As a light formatting/checking help, for instance to generate a table=
=20
from=20
> a human written section, to correct the formulation of a sentence, or to=
=20
draft=20
> an example. This is notably useful for non native English speakers.
>=20
> 2. As a help to search existing state of art on some feature, or any kind=
 of=20
> data, without writing anything in a protoXEP.
>=20
> 3. As a way to generate whole sections.
>=20
> Instinctively, and If we put aside ethical and ecological concerns about=
=20
LLMs,=20
> I think that 1. and 2. are OK, and 3. should be forbidden. And in all cas=
es,=20
> it should be disclosed.
>=20
> I would like your feedback on this matter, in particular people with lega=
l=20
> knowledge.
>=20
> I would like to avoid a flamewar, I know that this topic is sensitive and=
=20
there=20
> opinions are highly divided, please express your opinion calmly. The fact=
=20
is,=20
> we can't ignore this anymore.
>=20
> Should this be discussed with board or council?
>=20
> Thanks.
>=20
> Best,
> Goffi


--nextPartID4ic_yeTreJDJ0wLBurAw
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEsNZvWyEnjW9SVudbKqmcu6xuKwwFAmpNIYoACgkQKqmcu6xu
Kwxszgf/Y5g/Fws+YFW+VFCsJP/tsfTnsSDUuNV7bDhU6kw90pvqE695wYdC53Xv
NZtaKSFA4WYKPqdXgYAr8SpUu41R0NVFgUBrpaQVwSa6rGH3k8ZKTLcuIQi+5BQG
iVNzCmxL0L0wfw07e3kR2kdJKur5273dnyRQOhemdwN+aFF0tzjLDF+4JgkKnBPX
txXFdLEhFBok4qXtTz2eujgujm413NqPHvztwmJGPcLzC8cwdIGjnuEILTaix3CH
/+/htpdXoSHyWIIHx0ssP7iW+cVLy3M49E6C6RPAeB5pF/5VLju6na10aNLht5Yg
z+qh0P+NvAYg+l/3Ss4QZ6TEZtOUrg==
=17pN
-----END PGP SIGNATURE-----

--nextPartID4ic_yeTreJDJ0wLBurAw--




--===============5216321710505180977==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Standards mailing list -- [email protected]
To unsubscribe send an email to [email protected]

--===============5216321710505180977==--