From: Josh Triplett <josh@kernel.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-sparse@vger.kernel.org
Subject: Sparse licensing
Date: Thu, 2 Jul 2009 16:08:36 -0700 [thread overview]
Message-ID: <20090702230836.GI19009@feather> (raw)
In-Reply-To: <4A4D3468.1010202@garzik.org>
On Thu, Jul 02, 2009 at 06:27:52PM -0400, Jeff Garzik wrote:
> Can you weigh in on the licensing threads, pretty please? That is
> still blocked on you, AFAIK.
Sure.
For my part, I'd *love* to see Sparse relicensed to something more
palatable. Ideally, I'd love to see Sparse become GPL-compatible. I'd
prefer a stronger copyleft over a weaker one.
I have no problem with relicensing Sparse to any of the following
licenses, in rough order of preference:
- GPL (v2 or v3, with or without "or any later version")
- LGPL (v2.1 or v3, with or without "or any later version")
- Either of the above with some kind of additional exception similar to
those used for GCC and related libraries.
- Any of the above dual-licensed with the OSL, if people care about
preserving that for some reason. Seems unnecessarily complex to do
so, though.
I'd prefer not to see Sparse relicensed to something entirely
non-copyleft like the MIT license, but if the rest of the Sparse
community wants that for some reason, I won't stand in the way.
If you need any more formal approval from me, please let me know.
Thanks,
Josh Triplett
next prev parent reply other threads:[~2009-07-02 23:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 21:43 Meet the new maintainer Josh Triplett
2009-07-02 22:27 ` Jeff Garzik
2009-07-02 23:08 ` Josh Triplett [this message]
2010-01-21 12:08 ` Sparse licensing Dan Carpenter
2009-07-03 0:34 ` Meet the new maintainer Chris Li
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=20090702230836.GI19009@feather \
--to=josh@kernel.org \
--cc=jeff@garzik.org \
--cc=linux-sparse@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).