Re: [OFF TOPIC] BK license change

Larry McVoy
2002-04-22T22:54:21Z

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