linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Carpenter <error27@gmail.com>
To: Josh Triplett <josh@kernel.org>
Cc: Jeff Garzik <jeff@garzik.org>,
	linux-sparse@vger.kernel.org, madcoder@debian.org, lool@dooz.org
Subject: Re: Sparse licensing
Date: Thu, 21 Jan 2010 15:08:05 +0300	[thread overview]
Message-ID: <a63d67fe1001210408v34d47494m980e291df690319f@mail.gmail.com> (raw)
In-Reply-To: <20090702230836.GI19009@feather>

On 7/3/09, Josh Triplett <josh@kernel.org> wrote:
> 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
> --

I'm not a lawyer or anything.  Does this mean we're done?  Can the
Debian people move sparse out of non-free?  Can I re-license smatch?

I used the following command to find who might have to sign off.

git log 1bcc92138dcdf718dc3e0c694565f56e669d6ee3 master | grep Author
| cut -d : -f 2- | cut -d '<' -f 1 | sort | uniq -c | sort -n | less

Here are the list of people with other 5 commits.  Maybe you should
need at least 10 to get a vote?

      6  Blue Swirl
      6  Kamil Dudka
      6  Michael Stefaniuc
      7  Alexey Dobriyan
      7  Damien Lespiau
      7  terra@gnome.org
      8  Arnaldo Carvalho de Melo
      8  Johannes Berg
      9  Dave Olien
     12  Pavel Roskin
     16  Alexey Zaytsev
     16  Oleg Nesterov
     20  Luc Van Oostenryck
     45  Alexander Viro
     45  Jeff Garzik
     69  Christopher Li
     75  welinder@troll.com
    124  Al Viro
    195  Josh Triplett
   1250  Linus Torvalds

regards,
dan carpenter

  reply	other threads:[~2010-01-21 12:08 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   ` Sparse licensing Josh Triplett
2010-01-21 12:08     ` Dan Carpenter [this message]
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=a63d67fe1001210408v34d47494m980e291df690319f@mail.gmail.com \
    --to=error27@gmail.com \
    --cc=jeff@garzik.org \
    --cc=josh@kernel.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=lool@dooz.org \
    --cc=madcoder@debian.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).