From: Alexander Strasser via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: Alexander Strasser <eclipse7@gmx.net> Subject: Re: [FFmpeg-devel] [RFC] Introducing policies regarding "AI" contributions Date: Mon, 7 Jul 2025 00:29:44 +0200 Message-ID: <mailman.5490.1751840992.1384.ffmpeg-devel@ffmpeg.org> (raw) In-Reply-To: <20250704101528.GS29660@pb2> [-- Attachment #1: Type: message/rfc822, Size: 7259 bytes --] From: Alexander Strasser <eclipse7@gmx.net> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [RFC] Introducing policies regarding "AI" contributions Date: Mon, 7 Jul 2025 00:29:44 +0200 Message-ID: <aGr42Lb6W9A7X53l@metallschleim.local> Hi Michael! On 2025-07-04 12:15 +0200, Michael Niedermayer wrote: > The use of tools to assist developers is growing and will > continue to grow. Its not going away. > And what one can and cannot do with these tools will evolve > > I dont think i understand the thought process behind this policy. I did not propose any policy in particular yet. So I'm not sure what you are referring to. > Licenses need to be complied to, code needs to be of good quality. With the way the technology works, I can't see how the quality goals should be reached, but maybe someone else can explain it. Sure it can support. Or give inspiration like Nicolas mentioned and you rewrite it almost completely before submission. More importantly I see no way for the license part to work out automagically. In how far is the result a derivative other works? How would we apply attribution where original works demand it? How do we now the generated code is not just a mostly exact copy of the original training material? We cannot just relicense e.g. GPL as LGPL. So I would say at least some policy stating the obvious and that it also applies to LLM outputs is in order. It's not about being able to control it, but to make it more visible and also what I replied to Remi. Pointing people to it and increasing awareness. Maybe encouraging marking of LLM generated content be it in code (docs), tickets or mails would also be a good idea. [Remainder of your mail skipped that seems not relevant to this discussion] Best regards, Alexander [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ 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-06 22:29 UTC|newest] Thread overview: 20+ 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-06 22:29 ` Alexander Strasser via ffmpeg-devel [this message] 2025-07-07 0:10 ` Michael Niedermayer 2025-07-07 0:35 ` Marvin Scholz 2025-07-07 2:52 ` Michael Niedermayer 2025-07-07 2:01 ` Michael Niedermayer 2025-07-05 11:20 ` Rémi Denis-Courmont 2025-07-05 12:22 ` Kacper Michajlow 2025-07-06 22:18 ` Alexander Strasser via ffmpeg-devel
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=mailman.5490.1751840992.1384.ffmpeg-devel@ffmpeg.org \ --to=ffmpeg-devel@ffmpeg.org \ --cc=eclipse7@gmx.net \ /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