Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "softworkz ." <softworkz-at-hotmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [ANNOUNCEMENT] almpeg
Date: Mon, 26 May 2025 21:35:41 +0000
Message-ID: <DM8P223MB0365646A2AEE3F143CC39D23BA65A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <DM8P223MB0365CDCBDED32B66B14FE722BA65A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>



> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of softworkz .
> Sent: Montag, 26. Mai 2025 23:10
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [ANNOUNCEMENT] almpeg
> 
> 
> 
> > -----Original Message-----
> > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Michael
> > Niedermayer
> > Sent: Montag, 26. Mai 2025 23:00
> > To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> > Subject: Re: [FFmpeg-devel] [ANNOUNCEMENT] almpeg
> >
> > Hi sw
> >
> > On Mon, May 26, 2025 at 05:56:06PM +0000, softworkz . wrote:
> > [...]
> >
> > > > But i certainly was and am open to talk with paul.
> > >
> > > I'd make at least an attempt before going the hard way.
> >
> > I intended to wait for him to contact me, but sure ill
> > mail him first then
> 
> ┈┈┈┈┈┈▕▔╲
> ┈┈┈┈┈┈┈▏▕
> ┈┈┈┈┈┈┈▏▕▂▂▂
> ▂▂▂▂▂▂╱┈▕▂▂▂▏
> ▉▉▉▉▉┈┈┈▕▂▂▂▏
> ▉▉▉▉▉┈┈┈▕▂▂▂▏
> ▔▔▔▔▔▔╲▂▕▂▂▂▏
> ⠀
> 
> 
> > > > > And when you really need something, you can still cherry-pick it
> anyway.
> > > >
> > > > but we dont really contaminate anything with GPL code
> > >
> > > Okay, so if all this will just remain in "almpeg" with GPL - what's the
> > > benefit?
> > > He appears to be updating regularly from FFmpeg, so if I would want
> > > FFmpeg + his work under GPL - then I could use his project directly - no?
> >
> >
> > in what you write, replce GPL by LGPL as in:
> >
> > > He appears to be updating regularly from FFmpeg, so if I would want
> > > FFmpeg + his work under LGPL - then I could use his project directly - no?
> >
> > I mean, you seem to think this argument doesnt work if the license is LGPL
> > why would it be different with the GPL?
> 
> Ah yes - that's because it is a built-in "feature" of the LGPL that everybody
> is allowed to relicense derivative work from LGPL code under a GPL license.
> But it is not allowed to do this in the other direction.

Sorry, I falsely assumed this was commonly known (I'm not primarily an OSS guy).
Now, you might probably need to re-read my messages in this thread, because without
knowing about that "one-way" issue, most of what I wrote, won't have made much sense, I fear 😊 

Thanks
sw






_______________________________________________
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-05-26 21:35 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
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 . [this message]
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=DM8P223MB0365646A2AEE3F143CC39D23BA65A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
    --to=softworkz-at-hotmail.com@ffmpeg.org \
    --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