linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Triplett <josh@joshtriplett.org>
To: Dan Carpenter <error27@gmail.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: relicensing Sparse
Date: Thu, 11 Aug 2011 13:49:34 -0700	[thread overview]
Message-ID: <20110811204934.GA16486@leaf> (raw)
In-Reply-To: <20110811103908.GI3777@shale.localdomain>

On Thu, Aug 11, 2011 at 01:39:08PM +0300, Dan Carpenter wrote:
> On Wed, Aug 10, 2011 at 04:09:39PM -0700, Josh Triplett wrote:
> > On Thu, Aug 11, 2011 at 01:08:06AM +0300, Dan Carpenter wrote:
> > > All of you probably know that I've been contacting people to try get
> > > permission to relicense Sparse to the MIT license.  The Transmeta
> > > code was relicensed some years ago but we needed to collect all
> > > the copyright holders to do a full relicense.  I basically did a git
> > > blame and if you have over 10 lines of Sparse code, then I sent you
> > > an email.
> > 
> > Thank you very much for your continued effort on this.  I'd wondered
> > what still blocked that effort.
> > 
> > Checking "git blame" doesn't seem sufficient; I think you really want to
> > contact anyone who has a commit in the git log. Try "git shortlog -se".
> > Who appears on the latter list and not your list from "git blame"?
> 
> Most of the people who I missed would have been filtered out anyway
> by my ten lines of code minimum contribution requirement.  Perhaps I
> should just contact everyone.
> 
> I looked at how Mozilla did the relicensing and they pretty much went
> by who had their name in a copyright notice at the top of the file.
> For files without a copyright notice they looked at the history.  So
> it seems like tiny contributions were ignored.
> 
> I'm obviously not a lawyer.  Contacting everyone is probably doable
> if that's what you think is best.

I don't necessarily think you *have* to successfully contact everyone,
but trying seems worthwhile.  When the list gets short enough, we can
review the remaining contributions and figure out if we need to worry.

Nonetheless, I certainly think you've taken the right approach of
focusing on the major contributions first.

- Josh Triplett

  reply	other threads:[~2011-08-11 20:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-10 22:08 relicensing Sparse Dan Carpenter
2011-08-10 23:09 ` Josh Triplett
2011-08-11 10:39   ` Dan Carpenter
2011-08-11 20:49     ` Josh Triplett [this message]
2011-08-11 22:47     ` Christopher Li
2011-08-11 22:52       ` Dan Carpenter
     [not found] <20110226173414.GN18043@bicker>
2011-02-26 18:10 ` Alexey Dobriyan
2011-02-26 18:24   ` Dan Carpenter

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=20110811204934.GA16486@leaf \
    --to=josh@joshtriplett.org \
    --cc=error27@gmail.com \
    --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).