Git development
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@suse.cz>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
	David Schwartz <davids@webmaster.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	git@vger.kernel.org
Subject: Re: The GPL: No shelter for the Linux kernel?
Date: Sat, 23 Sep 2006 20:14:06 +0200	[thread overview]
Message-ID: <20060923181406.GC11916@pasky.or.cz> (raw)
In-Reply-To: <Pine.LNX.4.64.0609231051570.4388@g5.osdl.org>

  (Quoting in full for the git@ people.)

Dear diary, on Sat, Sep 23, 2006 at 08:00:23PM CEST, I got a letter
where Linus Torvalds <torvalds@osdl.org> said that...
> On Sat, 23 Sep 2006, Jan Engelhardt wrote:
> > 
> > Now that you raise it: I think developers can already have done that 
> > if they wish - properly name author and conditions who may possibly 
> > change the license to what. Not that I have seen such code yet, but you 
> > never know.
> 
> Side note: in "git", we kind of discussed this. And because the project 
> was started when the whole GPL version discussion was already in bloom, 
> the git project has a note at top of the COPYING file that says:
> 
>  Note that the only valid version of the GPL as far as this project
>  is concerned is _this_ particular version of the license (ie v2, not
>  v2.2 or v3.x or whatever), unless explicitly otherwise stated.
> 
>  HOWEVER, in order to allow a migration to GPLv3 if that seems like
>  a good idea, I also ask that people involved with the project make
>  their preferences known. In particular, if you trust me to make that
>  decision, you might note so in your copyright message, ie something
>  like
> 
>         This file is licensed under the GPL v2, or a later version
>         at the discretion of Linus.
> 
>   might avoid issues. But we can also just decide to synchronize and
>   contact all copyright holders on record if/when the occasion arises.
> 
> but note how it's still at the discretion of the actual developers (ie 
> when you add a file, you can either not specify any extensions, in which 
> case it's "GPLv2 only", or you can specify "GPLv2 or any later", or you 
> can specify the "GPLv2 or any later at the discretion of Linus Torvalds".
> 
> The silly thing, of course, is that I'm not even the maintainer any more, 
> and that Junio has done a kick-ass job of maintaining the thing, and is 
> definitely the main author by now. So the whole "discretion of Linus" is a 
> bit insane.
> 
> [ Although exactly _because_ Junio has been such a great maintainer, I'd 
>   bow down to whatever decision he does, so my "discretion" would be to 
>   let him decide, if he wanted to. At some point, you have to trust some 
>   people, and just let go - if they do more than you do, they damn well 
>   have more rights than you do too. "Maintainership has its privileges" ]
> 
> Anyway, I suspect the git language was a mistake. We should just have done 
> what the kernel did - make the version number be clear and fixed, so that 
> people don't even have to worry about exactly what conditions might cause 
> a relicensing to happen.

  Actually, this didn't catch on very well anyway, I guess because most
people just know it's GPLv2 and don't even bother to peek at COPYING, we
are a bit sloppy about copyright notices and most of them don't mention
licence at all (if there are any in the file at all), and adding
explicit copyright notices to mails isn't too popular either.

	$ git grep 'discretion'
	COPYING:        at the discretion of Linus.
	git-annotate.perl:# at the discretion of Linus Torvalds.
	git-relink.perl:# Later versions of the GPL at the discretion of Linus Torvalds
	git-request-pull.sh:# at the discretion of Linus Torvalds.

and I've found no patches with such special assignment.

  I think people don't really want to bother with thinking too much
about licences at all unless absolutely necessary, they just want to do
the fun part (coding). :-)

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
#!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1
lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)

       reply	other threads:[~2006-09-23 18:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <MDEHLPKNGKAHNMBLJOLKIEJNOJAB.davids@webmaster.com>
     [not found] ` <Pine.LNX.4.61.0609231004330.9543@yvahk01.tjqt.qr>
     [not found]   ` <Pine.LNX.4.64.0609231051570.4388@g5.osdl.org>
2006-09-23 18:14     ` Petr Baudis [this message]
2006-09-24  7:53       ` The GPL: No shelter for the Linux kernel? Jan Engelhardt
2006-09-24 16:34         ` Linus Torvalds
2006-09-25  5:59           ` Jan Engelhardt
2006-09-25 15:14             ` Linus Torvalds

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=20060923181406.GC11916@pasky.or.cz \
    --to=pasky@suse.cz \
    --cc=davids@webmaster.com \
    --cc=git@vger.kernel.org \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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