Date: Mon, 14 Feb 2005 20:44:28 +0100
From: Matthias Andree <matthias.andree@gmx.de>
To: lm@bitmover.com, Jeff Sipek <jeffpc@optonline.net>,
       Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
       linux-kernel@vger.kernel.org
Subject: Re: [BK] upgrade will be needed
Message-ID: <20050214194428.GC8763@merlin.emma.line.org>
Mail-Followup-To: lm@bitmover.com, Jeff Sipek <jeffpc@optonline.net>,
	Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	linux-kernel@vger.kernel.org
References: <20050214020802.GA3047@bitmover.com> <58cb370e05021404081e53f458@mail.gmail.com> <20050214150820.GA21961@optonline.net> <20050214154015.GA8075@bitmover.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20050214154015.GA8075@bitmover.com>
User-Agent: Mutt/1.5.8i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1950
Lines: 48

On Mon, 14 Feb 2005, Larry McVoy wrote:

> 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
>     ...

Add a cancellation period or a relicense block to BK/Free.

For instance:

1. $licensee can cancel his license with 30 days period before end of a
   month

2. BK/Free license is not available to (1) people who have worked on a
   system essentially similar to BK in the past six weeks, (2) people
   who have had their BK/Free license terminated within the past six
   weeks for any reason other than a new BK version becoming available.

> So what do you want us to do?  This isn't a change to take stuff from
> you, it's a change that some of your peers asked us to do so they could
> use BK (and it would be nice if the people who wanted this are reading
> this thread and will speak up so it doesn't look like I'm making it up).

This is, by your leave, ridiculous. I was, so far, allowed to stop using
BK/Free on day #1 and hack non-BK SCM on day #2. I understand you don't
want users to repeat this sequence, use BK on every odd day of month and
hack non-BK SCM on every even day, and I haven't done that (I haven't
hacked SCM).

> What we've been doing so far is telling people who were worried to act as
> if there were a year long gap and they have been happy with that answer
> but they are asking for us to put it in the license so they don't have
> to depend on some email based side agreement.

So have them send a SSAE and pass that note in writing.

-- 
Matthias Andree
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/