public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: Andreas Dilger <adilger@clusterfs.com>,
	Larry McVoy <lm@bitmover.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [OFF TOPIC] BK license change
Date: Mon, 22 Apr 2002 19:12:47 -0400	[thread overview]
Message-ID: <20020422191247.H914@redhat.com> (raw)
In-Reply-To: <20020421095715.A10525@work.bitmover.com> <E16zPbZ-0001NE-00@starship> <20020422222922.GM3017@turbolinux.com> <E16zQCP-0001NN-00@starship>

On Mon, Apr 22, 2002 at 12:52:48AM +0200, Daniel Phillips wrote:
> Larry's proposing to turn BitKeeper into an automated GPL enforcement machine, 
> even poking it's nose into areas the GPL isn't concerned about.  This is a
> horribly broken reason for adding let more t&c's do the license.

You didn't read Larry's initial email very close.  He isn't trying to turn 
BK into a GPL enforcing machine, he's trying to turn BK into a BK License 
enforcing machine.  Larry lets certain people (such as linux kernel 
hackers) use BK for free.  He does that specifically for contributors 
to open source projects.  Some people are, in essence, signing up to use 
the software as though they are working on open source projects but they 
are never actually open sourcing their work (or are intentionally 
obfuscating parts of it).  Since that violates the spirit of what Larry is 
trying to do by letting people use BK in a non-commercial manner, he is 
trying to find appropriate wording and possibly algorithms that can be put 
into BK to enforce the original spirit of the free use license that BK 
allows certain people.  So, he's not poking his nose into the GPL, he's 
trying to find a way to make sure that people who claim to be using BK on 
GPL projects (and free of charge as a result) are actually doing so.  
That's perfectly within his rights as owner of BK.

-- 
  Doug Ledford <dledford@redhat.com>     919-754-3700 x44233
         Red Hat, Inc. 
         1801 Varsity Dr.
         Raleigh, NC 27606
  

  reply	other threads:[~2002-04-22 23:12 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-21 16:57 [OFF TOPIC] BK license change Larry McVoy
2002-04-21 12:12 ` Daniel Phillips
2002-04-21 16:29 ` Greg KH
2002-04-22  7:33 ` Simon Fowler
2002-04-22 21:35 ` Larry McVoy
2002-04-21 22:14   ` Daniel Phillips
2002-04-22 22:29     ` Andreas Dilger
2002-04-21 22:52       ` Daniel Phillips
2002-04-22 23:12         ` Doug Ledford [this message]
2002-04-21 23:34           ` Daniel Phillips
2002-04-22 22:22   ` Jeff Garzik
2002-04-22 22:52     ` Larry McVoy
2002-04-25 15:01   ` Pavel Machek
2002-04-27  9:30     ` Florian Weimer
2002-04-27 13:45       ` Mr. James W. Laferriere
2002-04-27 20:34       ` Larry McVoy
2002-04-26  4:22         ` Pavel Machek
2002-04-29 19:34           ` Rik van Riel
2002-04-29 19:45             ` Larry McVoy
2002-04-30  5:36               ` Pavel Janík
  -- strict thread matches above, loose matches on Subject: below --
2002-04-27 18:13 Christoph Lameter
2002-04-27 18:25 ` Russell King
2002-04-27 18:30 ` Alexander Viro
2002-04-27 21:50   ` Martin Dalecki
2002-04-28 16:55     ` Richard Gooch

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=20020422191247.H914@redhat.com \
    --to=dledford@redhat.com \
    --cc=adilger@clusterfs.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    --cc=phillips@bonn-fries.net \
    /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