public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Russel Winder <russel@winder.org.uk>
Cc: DVB_Linux_Media <linux-media@vger.kernel.org>
Subject: Re: libdvbv5 licencing
Date: Tue, 12 Apr 2016 11:19:45 -0300	[thread overview]
Message-ID: <20160412111945.22846572@recife.lan> (raw)
In-Reply-To: <1458972788.3344.8.camel@winder.org.uk>

Hi Russel,

Em Sat, 26 Mar 2016 06:13:08 +0000
Russel Winder <russel@winder.org.uk> escreveu:

> I hadn't noticed previously, but it has been brought to my attention
> that libdvbv5 is licenced as GPLv2. This makes it impossible
> (effectively) for any non-GPL code to make use of libdvbv5. This seems
> to undermine the whole point of libdvbv5. 
> 
> In particular, I wanted to rip out all the Linux API based code from
> the GStreamer DVB plugins and replace it with use of libdvbv5. However
> because of the licencing (GStreamer is LGPL and must only use LGPL or
> more liberal licenced code), this is going to be impossible.
> 
> Instead of ripping out the current code (which is DVBv3) and using
> libdvbv5, it looks like I will be forced to recreate libdvbv5 but as
> LGPL code.
> 
> Is there any chance of relicencing libdvbv5 as LGPL code so that others
> may use it?

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.

Regards,
Mauro

  reply	other threads:[~2016-04-12 14:19 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 [this message]
2016-04-13 15:40   ` Russel Winder
2016-04-19 19:36     ` Mauro Carvalho Chehab
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=20160412111945.22846572@recife.lan \
    --to=mchehab@osg.samsung.com \
    --cc=linux-media@vger.kernel.org \
    --cc=russel@winder.org.uk \
    /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