From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [RFC] Cherry picks vs merges Date: Sun, 1 Jun 2025 21:23:20 +0200 Message-ID: <20250601192320.GV29660@pb2> (raw) In-Reply-To: <7fa92fbb-f6cb-40c1-b95e-3d6a77e6cbcf@gmail.com> [-- Attachment #1.1: Type: text/plain, Size: 2234 bytes --] Hi James On Sun, Jun 01, 2025 at 02:27:37PM -0300, James Almer wrote: > On 6/1/2025 12:22 PM, Michael Niedermayer wrote: > > Hi all > > > > almpeg is now merged upto 1 months ago. (and since last merge it contains > > bits of AGPL code) > > > > The question now is, how does the community want to proceed from here? > Full stop. > > Not only you're trying to bypass explicit a license notice on > technicalities, This is a serious accusation. Code is either under the LGPL license or it is not. It cannot be sometimes under the LGPL license, the license headers on the files in question, distrinbuted by Paul are unmodified LGPL headers. There is no extra notice or anything in these headers. If paul wants them to be GPL he can change these headers at any time. And the "explicit license notice" you refer to is this: "All Librempeg modifications, and any new files not available in FFmpeg, are licensed under GPL v2, unless stated otherwise." And it IS stated otherwise in these files by the license header in these files. That said, with open source and free software it is the morally correct thing, if one makes changes to code, to return these changes to the parent project under the same license as the parent project. This is morally the ONLY correct thing one can do. The technicality is that one can change the LGPL to a GPL or AGPL. The purpose of this is allowing to combine LGPL with GPL or AGPL NOT to fork a project and prevent the parent project and its users from having access to the modifications. You can listen to some interviews by linus torvalds if you think my point here is crazy. I will reply to the rest of your mail seperately to keep this from becoming too long But one thing id like to mention here, your accusation escalates this in a way that could reduce the chance of paul returning. And I tried my best and i talked (emailed) with paul in the last days. You knew i was working on this and i would have appreciated a private message over a public accusation thx -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB The misfortune of the wise is better than the prosperity of the fool. -- Epicurus [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 bytes --] [-- 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-06-01 19:23 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-06-01 15:22 Michael Niedermayer 2025-06-01 17:12 ` Kieran Kunhya via ffmpeg-devel 2025-06-01 17:27 ` James Almer 2025-06-01 19:23 ` Michael Niedermayer [this message] 2025-06-01 19:48 ` compn 2025-06-01 20:01 ` James Almer 2025-06-01 21:31 ` Michael Niedermayer 2025-06-02 4:46 ` Vittorio Giovara 2025-06-02 15:05 ` Michael Niedermayer 2025-06-02 7:41 ` Marton Balint 2025-06-02 8:23 ` softworkz . 2025-06-02 15:28 ` Michael Niedermayer 2025-06-02 15:57 ` Kieran Kunhya via ffmpeg-devel 2025-06-04 15:20 ` compn 2025-06-01 21:55 ` Kieran Kunhya via ffmpeg-devel 2025-06-02 4:36 ` Baptiste Coudurier 2025-06-02 15:38 ` Rémi Denis-Courmont 2025-06-03 13:09 ` Michael Niedermayer 2025-06-03 22:38 ` Kieran Kunhya via ffmpeg-devel 2025-06-04 14:51 ` Michael Niedermayer 2025-06-04 15:00 ` Kieran Kunhya via ffmpeg-devel 2025-06-04 15:35 ` Rémi Denis-Courmont 2025-06-04 18:06 ` Tomas Härdin 2025-06-04 20:42 ` Baptiste Coudurier 2025-06-04 22:41 ` 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=20250601192320.GV29660@pb2 \ --to=michael@niedermayer.cc \ --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