Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: ff--- via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: ff@hawaiiantel.net
Subject: [FFmpeg-devel] Re: question about submitting security patches
Date: Thu, 13 Nov 2025 10:59:41 -0800
Message-ID: <d89b4cc0f2be23d6859d0c7963ea1f28@hawaiiantel.net> (raw)
In-Reply-To: <eaa556ac-a7b6-4890-ad4f-82f3316a2d4a@rothenpieler.org>

On 2025-11-13 06:50, Timo Rothenpieler via ffmpeg-devel wrote:
> On 13/11/2025 04:06, Michael Niedermayer via ffmpeg-devel wrote:
>> Hi Kieran
>> 
>> On Wed, Nov 12, 2025 at 12:09:00AM -0800, Kieran Kunhya via 
>> ffmpeg-devel wrote:
>>> On Mon, 10 Nov 2025, 19:00 Michael Niedermayer via ffmpeg-devel, <
>>> ffmpeg-devel@ffmpeg.org> wrote:
>>> 
>>>> Hi Remi
>>>> 
>>>> On Mon, Nov 10, 2025 at 06:03:38PM +0200, Rémi Denis-Courmont via
>>>> ffmpeg-devel wrote:
>>>>> Le lauantaina 8. marraskuuta 2025, 10.34.24 Itä-Euroopan 
>>>>> normaaliaika
>>>> Thomas
>>>>> Dullien via ffmpeg-devel a écrit :
>>>>>> What's the best way to submit these patches? There is the bug 
>>>>>> tracker,
>>>>>> there is this mailing list - what's the best way to contribute 
>>>>>> them?
>>>>> 
>>>>> I don't think that DNN-generated patches are compatible with the 
>>>>> LGPL in
>>>> the
>>>>> first place, or it is at best very uncertain that they are. So then 
>>>>> you
>>>> cannot
>>>>> contribute DNN-generated patches in any useful way at all.
>>>> 
>>>> If you have concrete legal analysis or case law that supports this 
>>>> claim,
>>>> please share it.
>>>> 
>>> 
>>> If an LLM was trained on the leaked Microsoft Windows source code and 
>>> it
>>> used elements of that code when asked to write an FFmpeg patch, would 
>>> that
>>> patch be acceptable in your eyes?
>> 
>> If a human was trained on the leaked Microsoft Windows source code and 
>> he
>> used elements of that code when asked to write an FFmpeg patch, would 
>> that
>> patch be acceptable in your eyes?
>> 
>> We should forbid human written code?
> 
> I mean, that is in fact generally how situations like that are handled.
> At least I have seen it multiple times on Projects like the Dolphin 
> Emulator that people who read the leaked Nintendo code were barred from 
> ever contributing again once found out, cause it would give Nintendo 
> legal ground to take down the project.

the small fixes to regular code in ffmpeg wont be fixed with 1000 lines 
of windows/nintendo source code so its a bit of a moot point.

-compn
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

  reply	other threads:[~2025-11-13 19:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-08  8:34 [FFmpeg-devel] " Thomas Dullien via ffmpeg-devel
2025-11-10 16:03 ` [FFmpeg-devel] " Rémi Denis-Courmont via ffmpeg-devel
2025-11-10 16:19   ` Thomas Dullien via ffmpeg-devel
2025-11-11  2:59   ` Michael Niedermayer via ffmpeg-devel
2025-11-11  6:49     ` Rémi Denis-Courmont via ffmpeg-devel
2025-11-11  8:27       ` Gyan Doshi via ffmpeg-devel
2025-11-12  8:09     ` Kieran Kunhya via ffmpeg-devel
2025-11-13  3:06       ` Michael Niedermayer via ffmpeg-devel
2025-11-13  3:52         ` Kieran Kunhya via ffmpeg-devel
2025-11-13 18:38           ` Michael Niedermayer via ffmpeg-devel
2025-11-13 14:50         ` Timo Rothenpieler via ffmpeg-devel
2025-11-13 18:59           ` ff--- via ffmpeg-devel [this message]
2025-11-14  7:40           ` Tobias Rapp via ffmpeg-devel
2025-11-12  8:24     ` Christophe Gisquet via ffmpeg-devel
2025-11-12 10:26       ` Thomas Dullien via ffmpeg-devel
2025-11-13  5:36 ` compn 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=d89b4cc0f2be23d6859d0c7963ea1f28@hawaiiantel.net \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=ff@hawaiiantel.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