All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Jeff Garzik <garzik@havoc.gtf.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OFF TOPIC] BK license change
Date: Mon, 22 Apr 2002 15:52:42 -0700	[thread overview]
Message-ID: <20020422155242.O18800@work.bitmover.com> (raw)
In-Reply-To: <20020421095715.A10525@work.bitmover.com> <20020422143527.K18800@work.bitmover.com> <20020422182214.A18907@havoc.gtf.org>

On Mon, Apr 22, 2002 at 06:22:14PM -0400, Jeff Garzik wrote:
> On Mon, Apr 22, 2002 at 02:35:27PM -0700, Larry McVoy wrote:
> > So that leaves a more selective approach.  We can add a clause that says
> > we reserve the right to insist you either
> > 
> >     a) maintain your changes in public within 90 days of making them, or
> >     b) buy closed use seats, or
> >     c) cease to use the product.
> 
> A (IMO -- feel free to debunk me :)) troublesome point is dead software.
> 
> What do I do if I start a project under BK, code on it for three months,
> and abandon the project / slack off / have the manager kill it.
> 
> Are they still obligated to make the software public?

What I had in mind was having BK refuse to build changesets on top of
more than 3 month old changesets.  So you would get a 3 month window
in which to play around and either kill it, leave it alone, or
publish it.

I'm not sure it's going to work, I think people have a legit point 
that there are legit uses for which this doesn't work.
-- 
---
Larry McVoy            	 lm at bitmover.com           http://www.bitmover.com/lm 

  reply	other threads:[~2002-04-22 22:54 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
2002-04-21 23:34           ` Daniel Phillips
2002-04-22 22:22   ` Jeff Garzik
2002-04-22 22:52     ` Larry McVoy [this message]
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=20020422155242.O18800@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=garzik@havoc.gtf.org \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.