Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Rémi Denis-Courmont" <remi@remlab.net>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [RFC] Introducing policies regarding "AI" contributions
Date: Sat, 05 Jul 2025 14:20:57 +0300
Message-ID: <5020747.31r3eYUQgx@basile.remlab.net> (raw)
In-Reply-To: <mailman.4919.1751367511.1384.ffmpeg-devel@ffmpeg.org>

Le tiistaina 1. heinäkuuta 2025, 13.58.23 Itä-Euroopan kesäaika Alexander 
Strasser via ffmpeg-devel a écrit :
> (...) I want this thread to start a discussion, that eventually leads
> to a policy about submitting and integrating "AI" generated content.

Well, you can define a policy and/or make a public statement on FFmpeg.org, but 
as others said, just like we can't prevent someone misattributing their 
contributions and violating copyrights, we can't credibly prevent (mis)use of 
LLMs to generate code.

There is also a problem of definition. While I don't personally use computer 
assistance, I think it's fine to use language servers to automatically generate 
or suggests boilerplate, possible contextual completions, etc. While this sort 
of technology predates LLMs and is clearly distinct from it **at the moment**, 
it's going to be hard to define "AI" and where to draw a line.

Ultimately, I think you need to define the problem(s) as far as FFmpeg-devel is 
concerned. Potential copyright violations are not new, and I think the current 
policies and license terms are adequate, regardless of AI.

Low quality patches are also not really a new problem, and they can be 
rejected with the current processes too.

*Maybe* LLM usage will (willingly or unwittingly) lead to a denial of service 
attacks on the review capacity and motivation of the FFmpeg-devel, TC and GA 
membership, but that remains highly speculative, and I think we don't need to 
solve that what-if problem yet. And again, this attack does not necessarily 
need an LLM to be carried.

-- 
ヅニ-クーモン・レミ
Tapio's place new town, former Finnish Republic of Uusimaa



_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

  parent reply	other threads:[~2025-07-05 11:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-01 10:58 Alexander Strasser via ffmpeg-devel
2025-07-01 11:20 ` Gyan Doshi
2025-07-03 23:42   ` Alexander Strasser via ffmpeg-devel
2025-07-01 12:44 ` Kacper Michajlow
2025-07-03 23:31   ` Alexander Strasser via ffmpeg-devel
2025-07-04 16:43     ` compn
2025-07-04 18:11   ` softworkz .
2025-07-03  0:16 ` Gerion Entrup
2025-07-03 23:14   ` Alexander Strasser via ffmpeg-devel
2025-07-04  7:10     ` Nicolas George
2025-07-03 23:44 ` Leo Izen
2025-07-04 10:15 ` Michael Niedermayer
2025-07-05 11:20 ` Rémi Denis-Courmont [this message]
2025-07-05 12:22   ` Kacper Michajlow

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5020747.31r3eYUQgx@basile.remlab.net \
    --to=remi@remlab.net \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git