Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Marvin Scholz <epirat07-at-gmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] Introducing policies regarding "AI" contributions
Date: Mon, 07 Jul 2025 02:35:38 +0200
Message-ID: <71ADCF87-98DE-4F0B-B596-55B598C97506@gmail.com> (raw)
In-Reply-To: <20250707001008.GD29660@pb2>



On 7 Jul 2025, at 2:10, Michael Niedermayer wrote:

> Hi
>
> On Mon, Jul 07, 2025 at 12:29:44AM +0200, Alexander Strasser via ffmpeg-devel wrote:
>> Date: Mon, 7 Jul 2025 00:29:44 +0200
>> 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
>>
>> 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.
>
> a policy is premature.
>
>
> [...]
>
>> 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?
>
> How do you know that a student that was a tought C by teaching
> materials licensed under AGPL will not produce work that falls under AGPL ?
>
> We should work on FFmpeg, review patches, fix bugs get the release done.
> And let people use the tools that work best for them.
>
> I do not want to have to spend time to think about if the use of
> tools (code completion?, some few line function prototype,
> LLM that fixed spelling errors, ...)
> requires a pariah mark on the patch or is "allowed"
>
> Such rules are IMHO not compatible with free software.
>
> It also would be another huge "go away" sign for the next generation
> of developers.

IMHO if something is a huge "go away" it is the lack of a modern development
workflow, like what a modern Git forge offers…

>
> Such marking is also a source of disagreements (2 people can easily
> disagree on what needs to be marked)
>
> Also if we have a AI policy, we would have to update it as technology
> changes. Thats more wasted resources.
>
> thx
>
> [...]
>
> -- 
> Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
>
> Freedom in capitalist society always remains about the same as it was in
> ancient Greek republics: Freedom for slave owners. -- Vladimir Lenin
> _______________________________________________
> 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".
_______________________________________________
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".

  reply	other threads:[~2025-07-07  0:35 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
2025-07-07  0:10     ` Michael Niedermayer
2025-07-07  0:35       ` Marvin Scholz [this message]
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=71ADCF87-98DE-4F0B-B596-55B598C97506@gmail.com \
    --to=epirat07-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