Re: [BK] upgrade will be needed

[Larry McVoy]

> >So how would you suggest that we resolve it?  The protection we need is
> >that people don't get to
> >
> >   - use BK
> >   - stop using BK so they can go work on another system
> >   - start using BK again
> >   - stop using BK so they can go work on another system
> 
> What??? Why not? BK is a PROGRAM. You can't tell somebody
> that once they use some program in one job, they can't
> use it again. What kind of "protection" are you claiming?

It is a program that comes with a license.  Licenses have terms which
survive the termination of the license, that's industry standard, they
all have such terms.

In this case the situation is unusual because we have a program that is
ahead, in some ways, of all the other programs out there that do the
same thing.  We'd like to protect that lead.  We put that lead at risk
by giving you BK for free, that's more or less suicide because the open
source world has a long track record of copying that which they find
useful.  We don't want you to copy it.  If you can't agree to not copy
it then you don't get to use it in the first place.

This is not that weird people, people sign NDA's which are far more
draconian every day.  Read any software license, they all have the
non-compete as well, they hide it in the reverse engineering restriction.
Those licenses don't care if you are competing with them or not, they
do a blanket do-not-reverse-engineer no matter who you are.  We tried
to be specific so that we were restricting the tiny subset of the world
that wants to hack SCM, not everyone else.  Because that's different
than standard language we get screamed at.  What you aren't figuring
out is that the standard language is more restrictive, not less.
-- 
---
Larry McVoy                lm at bitmover.com           http://www.bitkeeper.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/