From: Paul Moore <pmoore@redhat.com>
To: Josh Boyer <jwboyer@gmail.com>, "H. Peter Anvin" <hpa@zytor.com>
Cc: libseccomp-discuss@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
Will Drewry <wad@chromium.org>, Kees Cook <keescook@chromium.org>
Subject: Re: ANN: libseccomp
Date: Tue, 10 Apr 2012 16:29:17 -0400 [thread overview]
Message-ID: <1673842.NkbWD6ec4k@sifl> (raw)
In-Reply-To: <1524909.RpscfJeEfO@sifl>
On Monday, April 09, 2012 05:28:41 PM Paul Moore wrote:
> On Monday, April 09, 2012 04:14:15 PM Josh Boyer wrote:
> > On Mon, Apr 9, 2012 at 4:02 PM, H. Peter Anvin <hpa@zytor.com> wrote:
> > > On 04/09/2012 12:25 PM, Josh Boyer wrote:
> > >> Do you think the GPLv2 license will limit adoption of it's usage across
> > >> a wider variety of software projects? I'm not anti-GPL by any means
> > >> but I am slightly surprised libseccomp is using it.
> > >>
> > >> josh
> > >
> > > Yes, on the surface of it this would seem more like LGPL material.
> > >
> > > Other than that, very much needed!
> >
> > Agreed on both points. I only brought this up now as it's very early
> > in the project's lifetime. If a relicense were to happen it would be
> > better to do it before a larger number of developers started
> > contributing to the project.
>
> You both bring up a good point, the LGPL seems like a better choice. I
> chose GPLv2 when I started simply out of habit; it is a license I am both
> familiar and comfortable with so it has a tendency to get used when I start
> a new chunk of code.
>
> As you pointed out, the project is still very new with only a handful of
> authors beyond myself. I'll get in touch with them privately to make sure
> they are comfortable with the relicense and assuming there are no problems
> I'll report back when everything has been changed.
Just an update, the project has just been relicensed under the LGPLv2.1
license.
--
paul moore
security and virtualization @ redhat
next prev parent reply other threads:[~2012-04-10 20:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 18:58 ANN: libseccomp Paul Moore
2012-04-09 19:16 ` Kees Cook
2012-04-09 21:32 ` Paul Moore
2012-04-09 21:51 ` Will Drewry
2012-04-09 22:46 ` Paul Moore
2012-04-13 20:14 ` Paul Moore
2012-04-14 2:47 ` Henrique de Moraes Holschuh
2012-04-16 14:15 ` [libseccomp-discuss] " Paul Moore
2012-04-09 22:56 ` Serge Hallyn
2012-04-09 19:25 ` Josh Boyer
2012-04-09 20:02 ` H. Peter Anvin
2012-04-09 20:14 ` Josh Boyer
2012-04-09 21:28 ` Paul Moore
2012-04-10 20:29 ` Paul Moore [this message]
2012-04-11 0:27 ` Josh Boyer
[not found] ` <CAEXv5_jiZsd6t=H1KWMNhUdgMez0B-WdC5XAHzdHffjOQh_J4A@mail.gmail.com>
2012-04-15 16:20 ` Kees Cook
2012-04-16 14:09 ` [libseccomp-discuss] " Paul Moore
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=1673842.NkbWD6ec4k@sifl \
--to=pmoore@redhat.com \
--cc=hpa@zytor.com \
--cc=jwboyer@gmail.com \
--cc=keescook@chromium.org \
--cc=libseccomp-discuss@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=wad@chromium.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
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