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 <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 23:31:49 +0200
Message-ID: <20250601213149.GX29660@pb2> (raw)
In-Reply-To: <f259c8ee-48b4-4f89-bb1b-88a7ff2dcc7c@gmail.com>


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

Hi James

On Sun, Jun 01, 2025 at 05:01:09PM -0300, James Almer wrote:
> On 6/1/2025 4:23 PM, Michael Niedermayer wrote:
> > 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.
> 
> This is the technicality i was talking about. The fact he copy-pasted a
> boilerplate LGPL header in all new files being used as a way to invoke the
> "unless stated otherwise" part of the notice.
> 

> I'm not against merging his changes, and i apologize if what i said before
> sounded like an accusation, but the way i want this to go forward is with
> him being ok with it, and not us trying to find a way to workaround what was
> seemingly his intention to license his changes a certain way.

If Paul and everyone agrees, of course thats better and I would prefer that too.

But also keep in mind he didnt ask us if he can take our LGPL code.


> 
> > 
> > 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
> 
> Paul showed up on IRC a week or so ago and said you did not email him. If
> that changed in the last couple days, why didn't you or him mention it?

The dates & subject of the mails i sent to paul:
80754  sF 0527  0:26 To Paul B Mahol (1,4K) Collaboration and Contributions to FFmpeg
80755  sF 0527  1:42 To Paul B Mahol (1,8K) Re: Collaboration and Contributions to FFmpeg
80757  sF 0527 14:05 To Paul B Mahol (2,6K) Re: Collaboration and Contributions to FFmpeg
80759  sF 0527 15:30 To Paul B Mahol (6,2K) Re: Collaboration and Contributions to FFmpeg
80780  sF 0529 22:15 To Paul B Mahol (2,5K) Re: Collaboration and Contributions to FFmpeg

I also received replies from him between these

He was pissed that he was not considered / contacted by fflabs. I showed him a small
part of a private mail that i sent to jb in 2016. Where paul was #2 of the people
i recommanded for FFlabs.

My last mail (only the part i wrote) (and this mail remains unawnsered as of today):

I cannot read your mind, if there is something that you want,
you have to tell me, what you want.

One thing i can propose, is that you could become libavfilter subsystem
maintainer. This would give you authority in libavfilter.

About FFlabs, if you want to join FFlabs, you have to say so.
What i can say is, that i will support that and i expect that this
request would be successfull.

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

The difference between a dictatorship and a democracy is that every 4 years
the population together is allowed to provide 1 bit of input to the government.

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

  reply	other threads:[~2025-06-01 21:31 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 [this message]
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=20250601213149.GX29660@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