From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [ANNOUNCEMENT] almpeg
Date: Mon, 26 May 2025 11:00:42 +0300
Message-ID: <5901AC65-0CC1-449F-ACC9-F5B927F0479F@remlab.net> (raw)
In-Reply-To: <20250525192252.GM29660@pb2>
Hi,
Le 25 mai 2025 22:22:52 GMT+03:00, Michael Niedermayer <michael@niedermayer.cc> a écrit :
>Note the license of this code is a bit wonky. The files have one
>license and theres another one in LICENSE.md.
>While I belives legally this allows one to choose either. I suggest
>you check this with a lawyer.
You do realise that FFmpeg does the exact same thing:
- have a top-level license file (with the same name even) explaining, or trying to explain, which file is under which license,
- carry a copy of every GNU licenses as separate files.
Do you think that means that anyone can pick any listed license for FFmpeg? Are you saying that anyone can take your FFmpeg IP under MIT or BSD licenses? Or take the GPL code as LGPL code?
I and probably most people here think otherwise. That's not how this works and as a major copy-left open-source developer, you should know that.
Librempeg, as a whole, is AGPL. And if you strip the AGPL bits, it's GPLv2. All you're going to achieve with this mail is infuriate Paul by encouraging people to literally steal his IP.
And then it's utterly impossible for such a massive changeset to be reviewed. So even if it weren't for the license incompatibilities, there's no way we could merge into FFmpeg.
_______________________________________________
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-05-26 8:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-25 19:22 Michael Niedermayer
2025-05-25 22:29 ` Kieran Kunhya via ffmpeg-devel
2025-05-25 23:11 ` compn
2025-05-26 8:00 ` Rémi Denis-Courmont [this message]
2025-05-26 9:27 ` softworkz .
2025-05-26 11:26 ` Rémi Denis-Courmont
2025-05-26 11:44 ` softworkz .
2025-05-26 11:37 ` Michael Niedermayer
2025-05-26 11:49 ` softworkz .
2025-05-26 12:21 ` softworkz .
2025-05-26 17:21 ` Michael Niedermayer
2025-05-26 17:56 ` softworkz .
2025-05-26 20:59 ` Michael Niedermayer
2025-05-26 21:10 ` softworkz .
2025-05-26 21:35 ` softworkz .
2025-05-26 21:56 ` softworkz .
2025-05-26 16:36 ` Michael Niedermayer
2025-05-28 1:09 ` 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=5901AC65-0CC1-449F-ACC9-F5B927F0479F@remlab.net \
--to=remi@remlab.net \
--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