From: Leo Izen <leo.izen-at-gmail.com@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [RFC] Introducing policies regarding "AI" contributions
Date: Thu, 3 Jul 2025 19:44:57 -0400
Message-ID: <478a92ed-d402-4b77-bf7d-cd0a7eccf1d6@gmail.com> (raw)
In-Reply-To: <mailman.4919.1751367511.1384.ffmpeg-devel@ffmpeg.org>
On 7/1/25 06:58, Alexander Strasser via ffmpeg-devel wrote:
> _______________________________________________
While I agree with you on the merits that LLM-generated code tends to be
low quality, ideally that will be caught during code review. I think a
blanket ban on it makes more sense because of the legal implications of
including LLM-generated code in our codebase.
I am not a lawyer, so I cannot say for certain how the legality plays
out, and it may be safer to just not permit it than try to hire a laywer
to figure out how to permit it, if it's even possible.
- Leo Izen
_______________________________________________
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".
next prev parent reply other threads:[~2025-07-03 23:45 UTC|newest]
Thread overview: 10+ 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-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 [this message]
2025-07-04 10:15 ` Michael Niedermayer
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=478a92ed-d402-4b77-bf7d-cd0a7eccf1d6@gmail.com \
--to=leo.izen-at-gmail.com@ffmpeg.org \
--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