Hi softworkz On Mon, Jun 02, 2025 at 08:23:41AM +0000, softworkz . wrote: > > > > -----Original Message----- > > From: ffmpeg-devel <ffmpeg-devel-boun...@ffmpeg.org> On Behalf Of Marton > > Balint > > Sent: Montag, 2. Juni 2025 09:41 > > To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> > > Subject: Re: [FFmpeg-devel] [RFC] Cherry picks vs merges > > > > > > > > On Sun, 1 Jun 2025, 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. > > > > +1. Yeah, Paul changing the license was not nice, but ffmpeg as a project > > merging his work against his will would not be nice either, even if it > > might be legally OK, it certainly would not be OK morally. > > > > Regards, > > Marton > > _______________________________________________ > > Assuming for a moment, we would not care about moral behavior at all. > (which doesn't mean I don't) > > What would happen if we merge everything? >
> - We would gain 2.5 years of work yes, thats true if we merge back improvments we gain these improvments, thats always true for every improvment. > - He will change all license headers Everyone who forked can change all license headers 2 years ago, 1 year ago, today, tomorrow, in a year or never. The license one chooses certainly has an impact on them What exact impact does this have on us ? we merge new codecs and filters (that we otherwise do not have) with GPL headers and conditional on --enable-gpl We can still provide every codec or filter where someone made significant improvments under GPL as a seperate filter or codec > - The doors will be closed for all future As i predicted elsewhere privately, I do not belive Paul will return unless his fork fails. The more successfull his fork is, the less likely it is that he will return Also its like 18 months since paul forked and the way he speaks really doesnt sound like he intends to return currently. We have a ship that we need to sail we cant keep looking at a new competitor thats moving ahead hoping he will turn around and join us. We have to accelerate. He will join us when he falls behind not when he is ahead. thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB The greatest way to live with honor in this world is to be what we pretend to be. -- Socrates
signature.asc
Description: PGP signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
