Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Baptiste Coudurier <baptiste.coudurier@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] Cherry picks vs merges
Date: Wed, 4 Jun 2025 13:42:42 -0700
Message-ID: <C5D85863-E8B0-426F-BB53-859BA0003BE9@gmail.com> (raw)
In-Reply-To: <b58a0962bdcfcc69a19e3167a7a0ee85fba3eae7.camel@haerdin.se>


> On Jun 4, 2025, at 11:06 AM, Tomas Härdin <git@haerdin.se> wrote:
> 
> sön 2025-06-01 klockan 21:23 +0200 skrev Michael Niedermayer:
>> 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.
> 
> These conflicting texts are reason enough not to touch this code unless
> we're fine with upgrading the license to GPLv2. I don't think the
> project should get into a legal fight over something like this

There are no legal fights until somebody starts one.
The courts are here to settle disagreements and different understandings.

The fact is that there is even disagreement on whether there is ambiguity
on the way the fork was re-licensed. Interpretation can be subtle.

> Given how everything has moved to the cloud, upgrading to GPLv2
> wouldn't necessarily be a bad thing. We should also consider upgrading
> the fftools to AGPL for the same reason
> 
>> 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.
> 
> This is incredibly spooked. Paul plays the license game the way he sees
> fit, as does everyone else

We are also free to play the same license game.

Nonetheless, if the modifications are good, we need to incorporate them in
some way, so what is the alternative proposed ?

New filters and codecs will be added with —enable-gpl, that’s a given.

— 
Baptiste
_______________________________________________
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".

  reply	other threads:[~2025-06-04 20:42 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
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 [this message]
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=C5D85863-E8B0-426F-BB53-859BA0003BE9@gmail.com \
    --to=baptiste.coudurier@gmail.com \
    --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