From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Russel Winder <russel@winder.org.uk>
Cc: DVB_Linux_Media <linux-media@vger.kernel.org>,
"Sebastian Dröge" <slomo@coaxion.net>
Subject: Re: libdvbv5 licencing
Date: Tue, 19 Apr 2016 16:36:34 -0300 [thread overview]
Message-ID: <20160419163634.5ee8de2c@recife.lan> (raw)
In-Reply-To: <1460562055.28492.27.camel@winder.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]
Em Wed, 13 Apr 2016 16:40:55 +0100
Russel Winder <russel@winder.org.uk> escreveu:
> On Tue, 2016-04-12 at 11:19 -0300, Mauro Carvalho Chehab wrote:
> […]
>
> > Yes. We had some discussions in the past to re-license it to LGPL,
> > if this is going to be used by some other OSS project that would
> > require that. Most of the code was written by me, and, in the past
> > the other developers that worked on that also agreed on re-licensing
> > as LGPL.
> >
> > So, basically, if gstreamer is willing to use libdvbv5, we'll
> > relicense it to LGPL.
>
> I have volunteered to rewrite the DVB plugin for GStreamer and proposed
> use of libdvbv5, a proposal which was stated as being entirely
> acceptable, but only if libdvbv5 was LGPL. So if libdvbv5 becomes an
> LGPL library, my rewrite of the GStreamer DVB plugin will certainly use
> it. I will then put forward my rewrite for incorporation into the
> GStreamer bad plugins (seriously misnamed library, but…).
License changed.
--
Thanks,
Mauro
[-- Attachment #2: Assinatura digital OpenPGP --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-04-19 19:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-26 6:13 libdvbv5 licencing Russel Winder
2016-04-12 14:19 ` Mauro Carvalho Chehab
2016-04-13 15:40 ` Russel Winder
2016-04-19 19:36 ` Mauro Carvalho Chehab [this message]
2016-04-22 8:25 ` Russel Winder
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=20160419163634.5ee8de2c@recife.lan \
--to=mchehab@osg.samsung.com \
--cc=linux-media@vger.kernel.org \
--cc=russel@winder.org.uk \
--cc=slomo@coaxion.net \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox