Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 9 Nov 2002 05:11:48 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 9 Nov 2002 05:11:48 -0500 Received: from [132.69.253.254] ([132.69.253.254]:48103 "HELO vipe.technion.ac.il") by vger.kernel.org with SMTP id ; Sat, 9 Nov 2002 05:11:47 -0500 Date: Sat, 9 Nov 2002 12:18:24 +0200 (IST) From: Shlomi Fish To: Subject: An Analysis of BitKeeper and BitMover's Strategy Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1592 Lines: 42 As part of the "Better SCM" site (that is still under construction), I wrote a few essays about BitKeeper: http://better-scm.berlios.de/bk/ I am a former user of BitKeeper and the bkbits.net service who used it for maintaining the code of two of my pet projects. The articles include: An analysis of the suitability of BitKeeper for Free Software Developers - analyzes the product itself, the support given by BitMover, the BKBits.net service and the license. Contains some tips for new users. Why a change of the BitKeeper licensing would be a good idea (from BitMover's POV) - a rational analysis why a change in BitMover's strategy can yield them a greater advantage in the long run. (note that I do not recommend completely Open-Sourcing it) There's also an old and slightly deprecated article entitled "GPLing BK" which gives several advantages that a more liberal BitKeeper license would give BitMover. (it is deprecated because I no longer thing a complete freeing would be a good idea at this point). Comments, suggestions, corrections and flames are welcome. Regards, Shlomi Fish ---------------------------------------------------------------------- Shlomi Fish shlomif@vipe.technion.ac.il Home Page: http://t2.technion.ac.il/~shlomif/ He who re-invents the wheel, understands much better how a wheel works. - 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/