Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Michael Niedermayer <michael@niedermayer.cc>
Subject: Re: [FFmpeg-devel] Legal Advice Was: [POLL][RFC] Merge vs Cherry pick for integration of changes
Date: Sat, 23 Aug 2025 22:33:14 +0200
Message-ID: <20250823203314.GU29660@pb2> (raw)
In-Reply-To: <20250821113202.GH29660@pb2>


[-- Attachment #1.1: Type: text/plain, Size: 1729 bytes --]

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 the FFmpeg's
 LGPLv2.1 license. While section 3 of the LGPLv2.1 would have allowed 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 license. So the
 original code he is building from is still under LGPLv2.1. Since code
 contributions to a copyleft work have to be under the /same /license as the
 code you are contributing to (Section 2(c), "You must cause the whole of the
 work to be licensed at no charge to all third parties under the terms 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 GPLv2 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 code under
 the AGPL,* but he cannot change the license retroactively - you would 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

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

I know you won't believe me, but the highest form of Human Excellence is
to question oneself and others. -- Socrates

[-- 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".

      parent reply	other threads:[~2025-08-23 20:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-21 11:32 [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-08-21 16:56 ` Kieran Kunhya via ffmpeg-devel
2025-08-21 17:53   ` Michael Niedermayer via ffmpeg-devel
2025-08-21 17:58     ` Kieran Kunhya via ffmpeg-devel
2025-08-22 12:29 ` Niklas Haas via ffmpeg-devel
2025-08-22 12:45   ` Diederick C. Niehorster via ffmpeg-devel
2025-08-22 12:59   ` Michael Niedermayer via ffmpeg-devel
2025-08-23  7:09     ` Rémi Denis-Courmont via ffmpeg-devel
2025-08-23 10:58       ` Michael Niedermayer via ffmpeg-devel
2025-08-23 12:59         ` Kieran Kunhya via ffmpeg-devel
2025-08-22 13:45   ` Michael Niedermayer via ffmpeg-devel
2025-08-23 13:20 ` Michael Niedermayer via ffmpeg-devel
2025-08-23 20:33 ` Michael Niedermayer 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=20250823203314.GU29660@pb2 \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=michael@niedermayer.cc \
    /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