From: Gyan Doshi via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Gyan Doshi <ffmpeg@gyani.pro>
Subject: [FFmpeg-devel] Re: question about submitting security patches
Date: Tue, 11 Nov 2025 13:57:26 +0530
Message-ID: <79b80b5d-84e4-4222-9b5f-51cecc60e75e@gyani.pro> (raw)
In-Reply-To: <F775A075-688D-47EF-AB96-6853263D761F@remlab.net>
On 2025-11-11 12:19 pm, Rémi Denis-Courmont via ffmpeg-devel wrote:
>
> Le 11 novembre 2025 04:59:42 GMT+02:00, Michael Niedermayer via ffmpeg-devel<ffmpeg-devel@ffmpeg.org> a écrit :
>> 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.
> You can check what LF, Fedora, QEMU, etc, and their lawyers already did on that front.
QEMU is the only one which forbids AI
https://github.com/qemu/qemu/commit/3d40db0efc
The others provide caveats but do provide a pathway for AI contributions.
The Linux Foundation says, "Code or other content generated in whole or
in part using AI tools can be contributed to Linux Foundation projects.
..."
https://www.linuxfoundation.org/legal/generative-ai
Fedora says, this, "You *MAY* use AI assistance for contributing to
Fedora, as long as you follow the principles described below..."
https://docs.fedoraproject.org/en-US/council/policy/ai-contribution-policy/
Regards,
Gyan
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
prev parent reply other threads:[~2025-11-11 8:28 UTC|newest]
Thread overview: 6+ 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 [this message]
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=79b80b5d-84e4-4222-9b5f-51cecc60e75e@gyani.pro \
--to=ffmpeg-devel@ffmpeg.org \
--cc=ffmpeg@gyani.pro \
/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