From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.ffmpeg.org (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTPS id 4DA324BB2E for ; Sun, 24 Aug 2025 12:09:12 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id 1AFDE68E6FB; Sun, 24 Aug 2025 15:09:08 +0300 (EEST) Received: from relay9-d.mail.gandi.net (relay9-d.mail.gandi.net [217.70.183.199]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTPS id 800C068013F for ; Sun, 24 Aug 2025 15:09:01 +0300 (EEST) Received: by mail.gandi.net (Postfix) with ESMTPSA id CEBE74320D for ; Sun, 24 Aug 2025 12:09:00 +0000 (UTC) Date: Sun, 24 Aug 2025 14:08:59 +0200 To: FFmpeg development discussions and patches Message-ID: <20250824120859.GB29660@pb2> References: <20250821113202.GH29660@pb2> <20250823203314.GU29660@pb2> <20250824105618.GZ29660@pb2> MIME-Version: 1.0 In-Reply-To: X-GND-State: clean X-GND-Score: -90 X-GND-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdefgdduieelgeejucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuifetpfffkfdpucggtfgfnhhsuhgsshgtrhhisggvnecuuegrihhlohhuthemuceftddunecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenfghrlhcuvffnffculddutddmnecujfgurhepfffhvffukfhfgggtuggjsehgtderredttddvnecuhfhrohhmpefoihgthhgrvghlucfpihgvuggvrhhmrgihvghruceomhhitghhrggvlhesnhhivgguvghrmhgrhigvrhdrtggtqeenucggtffrrghtthgvrhhnpedvheejueehveeftefhvdeutdeutefgjeejgffgueegtedvleekheekkeehudetgfenucffohhmrghinhepjhgskhgvmhhpfhdrtghomhenucfkphepgedurdeiiedrieehrddujeeinecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehinhgvthepgedurdeiiedrieehrddujeeipdhhvghloheplhhotggrlhhhohhsthdpmhgrihhlfhhrohhmpehmihgthhgrvghlsehnihgvuggvrhhmrgihvghrrdgttgdpnhgspghrtghpthhtohepuddprhgtphhtthhopehffhhmphgvghdquggvvhgvlhesfhhfmhhpvghgrdhorhhg X-GND-Sasl: michael@niedermayer.cc Subject: Re: [FFmpeg-devel] Legal Advice Was: [POLL][RFC] Merge vs Cherry pick for integration of changes X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Michael Niedermayer via ffmpeg-devel Reply-To: FFmpeg development discussions and patches Cc: Michael Niedermayer Content-Type: multipart/mixed; boundary="===============8130109482357471081==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============8130109482357471081== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="76rAEbYIYxc+0bIE" Content-Disposition: inline --76rAEbYIYxc+0bIE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Kieran On Sun, Aug 24, 2025 at 12:11:20PM +0100, Kieran Kunhya via ffmpeg-devel wr= ote: > On Sun, 24 Aug 2025, 11:56 Michael Niedermayer via ffmpeg-devel, < > ffmpeg-devel@ffmpeg.org> wrote: >=20 > > Hi Kieran > > > > On Sun, Aug 24, 2025 at 07:53:45AM +0100, Kieran Kunhya via ffmpeg-devel > > wrote: > > > On Sat, 23 Aug 2025, 21:33 Michael Niedermayer via ffmpeg-devel, < > > > ffmpeg-devel@ffmpeg.org> wrote: > > > > > > > Hi > > > > > > > > Here is the legal advice that i was given. > > > > The GA has the full text and that is much more detailed. > > > > Iam posting the relevant parts so the whole community can see it. > > > > > > > > "a claim that there is GPLv2 code in a file of > > > > FFmpeg origin that has the LGPLv2.1 license would be a breach of t= he > > > > FFmpeg's > > > > LGPLv2.1 license. While section 3 of the LGPLv2.1 would have allow= ed > > him > > > > to > > > > take the original FFmpeg files and change the license for them to > > GPLv2, > > > > he > > > > didn't follow the necessary steps to effectively change the licens= e. > > So > > > > the > > > > original code he is building from is still under LGPLv2.1. Since c= ode > > > > contributions to a copyleft work have to be under the /same /licen= se > > as > > > > the > > > > code you are contributing to (Section 2(c), "You must cause the wh= ole > > of > > > > the > > > > work to be licensed at no charge to all third parties under the te= rms > > of > > > > this > > > > License"), Paul's contributions to LGPLv2.1 files are under the > > LGPLv2.1 > > > > license because he didn't exercise the option to change them to GP= Lv2 > > > > first. A > > > > claim otherwise would be admitting he is in breach of the FFmpeg > > license." > > > > > > > > "You can safely assume that any new file he created with a license > > > > identifier in the file of LGPLv.2.1 is under the LGPLv2.1 license." > > > > > > > > "Paul's response to your use of his code may be to relicense his co= de > > under > > > > the AGPL,* but he cannot change the license retroactively - you wo= uld > > > > have to > > > > accommodate the AGPL license for any later changes you adopt, but = not > > for > > > > any > > > > code you are using from before a license change." > > > > > > > > thx > > > > > > > > [...] > > > > > > > > > > Can you confirm the FFlabs lawyer said something different? > > > > I cannot confirm this. I dont remember ever seeing the reply or the > > question. > > > > My communication with the FFlabs lawyer was through a intermediary > > developer, > > who was very busy and the mails where also terse > > > > IIRC i also had to ask multiple times to get any awnser > > >=20 > Translation: The FFlabs lawyer didn't agree with my agenda and so I went > and found one that did. >=20 > It's funny how you are reluctant to post that lawyers opinion [because it > didn't agree with you] when you happily leak private discussions (e.g from > the CC) on this list all the time. >=20 > To use Anton's words "tin-pot dictator" behaviour in action. Date: Sun, 08 Jun 2025 14:40:25 +0200 =46rom: Jean-Baptiste Kempf To: Michael Niedermayer Subject: Re: License question Hello, Lawyer says that, most likely,the COPYING file that comes after (newer) tha= n the headers of the file prevails. So all his changes are GPLv2. :( BEst, On Sat, 7 Jun 2025, at 15:31, Michael Niedermayer wrote: > Hi jb > > any news ? > have you had time to ask the lawyer ? > > Its bad for FFmpeg to lack features that our competitors have. > (and thus also bad for FFlabs) > > librempeg has 36 decoders that FFmpeg does not have, id like to > get these into FFmpeg and even after the lawyer reply it will > still need likely a vote between cherry picking vs merging > > thx > > On Mon, Jun 02, 2025 at 10:34:27PM +0200, Michael Niedermayer wrote: >> Hi jb >> >> On Mon, Jun 02, 2025 at 09:50:53PM +0200, Jean-Baptiste Kempf wrote: >> > Hello, >> > >> > "All Librempeg modifications, and any new files >> > not available in FFmpeg, are licensed under GPL v2, unless stated >> > otherwise." >> > >> > Where is that from? >> >> git show paul/master:LICENSE.md >> >> the files themselfs contain unmodified LGPL headers >> >> thx >> >> [...] >> -- >> Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB >> >> I have often repented speaking, but never of holding my tongue. >> -- Xenocrates > > > > -- > Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB > > Those who would give up essential Liberty, to purchase a little > temporary Safety, deserve neither Liberty nor Safety -- Benjamin Franklin > > Attachments: > * signature.asc -- Jean-Baptiste Kempf - President +33 672 704 734 https://jbkempf.com/ [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB it is not once nor twice but times without number that the same ideas make their appearance in the world. -- Aristotle --76rAEbYIYxc+0bIE Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEKAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCaKsA2AAKCRBhHseHBAsP q5uvAJ4paV+YvvUresioT2Rks+1DEykVEQCbB+qjEDfqIayoG5Qzds9nQn7ae9k= =Bc5h -----END PGP SIGNATURE----- --76rAEbYIYxc+0bIE-- --===============8130109482357471081== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 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". --===============8130109482357471081==--