Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261716AbVBONTs (ORCPT ); Tue, 15 Feb 2005 08:19:48 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261719AbVBONTr (ORCPT ); Tue, 15 Feb 2005 08:19:47 -0500 Received: from main.gmane.org ([80.91.229.2]:43956 "EHLO ciao.gmane.org") by vger.kernel.org with ESMTP id S261718AbVBONT2 (ORCPT ); Tue, 15 Feb 2005 08:19:28 -0500 X-Injected-Via-Gmane: http://gmane.org/ To: linux-kernel@vger.kernel.org From: Tristan Wibberley Subject: Re: [BK] upgrade will be needed Date: Tue, 15 Feb 2005 13:24:31 +0000 Message-ID: References: <20050214020802.GA3047@bitmover.com> <58cb370e05021404081e53f458@mail.gmail.com> <20050214150820.GA21961@optonline.net> <20050214154015.GA8075@bitmover.com> <87wttbq8fd.fsf@freitag.home.jstuber.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: host81-158-66-156.range81-158.btcentralplus.com User-Agent: Pan/0.14.2.91 (As She Crawled Across the Table (Debian GNU/Linux)) X-Gmane-MailScanner: Found to be clean X-Gmane-MailScanner: Found to be clean X-Gmane-MailScanner-SpamScore: sss X-MailScanner-From: glk-linux-kernel@m.gmane.org X-MailScanner-To: linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1603 Lines: 29 On Tue, 15 Feb 2005 02:46:04 +0000, Tristan Wibberley wrote: > On Mon, 14 Feb 2005 19:54:14 +0100, Juergen Stuber wrote: > >> g BK, I can immediately start working on another SCM >> but I can't go back to BK immediately > > IMHO, it should be the other way around, and more like two years. Hmm, I wasn't really clear here. I think that after using BK, you shouldn't be able to work on another SCM until 2 years have past. But you can shorten that time by paying bitmover 1/12 of a BK license for each month you want to shorten it. That covers the problem of people needing to switch, they just have to pay. Then the following applies: > Two years would be more > appropriate since you need to make sure that coders who've worked on the > other SCM before are well and truly out of touch with the code when they > go back. With that scheme, if you have a serious business case for > writing a new SCM *today* you just have to factor an extra cost into > your plans (double BK license), and if you want to work on an open > source one, you just have to wait while BitMover gets another two years > on their head-start. Now only people with determined plans can switch > from using BK to working on an SCM, and BitMover can get new users > benefiting from their kindness and lifting their market penetration as > easily as possible. -- Tristan Wibberley - 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/