Alejandro Colomar [off-list ref] writes:

On Wed, Oct 15, 2025 at 09:03:28PM +0200, Alejandro Colomar wrote:

quoted

Hi Sam,

On Wed, Oct 15, 2025 at 07:49:50PM +0100, Sam James wrote:

quoted

quoted

quoted

We should base the contribution policy on things we can objectively
measure and claim.

Rejecting AI content in contributions is objective and measurable
since you can't attest the DCO clearly with this content.

Rejecting AI content would follow the first concern, but the second and
third concerns would be entirely ignored by a policy that permits AI
static analyzers.

It is hard in my mind to justify rejecting TTS or similar that may be
based on AI.

BTW, I assume TTS means text-to-speech.  Please don't use abbreviations
not supported by wtf(1), or parenthesize their meaning in the first use.

I normally try to honour that. Anyway, I'm not interested in discussing
further at this time. I don't think the way you've suggested this
subproposal is constructive.

quoted

The following is enough, IMO, as justification:

	Ethical concerns.
		The business side of AI boom is creating serious ethical
		concerns.  Among them:

		-  Commercial AI projects are frequently indulging in
		   blatant copyright violations to train their models.
		-  Their operations are causing concerns about the huge
		   use of energy, water, and other natural resources.
		-  The advertising and use of AI models has caused
		   a significant harm to employees and reduction of
		   service quality.
		-  LLMs have been empowering all kinds of spam and scam
		   efforts.

	Quality concerns.
		Popular LLMs are really great at generating plausibly
		looking, but meaningless content.  They pose both the
		risk of lowering the quality of a project, and of
		requiring an unfair human effort from contributors and
		maintainers to review contributions and detect the
		mistakes resulting from the use of AI.

		AI tools should be considered adversarial, as if they
		were a black box with Jia Tan inside them.


Cheers,
Alex

-- 
<https://www.alejandro-colomar.es>
Use port 80 (that is, <...:80/>).