From owner-freebsd-current Thu Feb 28 9:35:25 2002 Delivered-To: freebsd-current@freebsd.org Received: from outboundx.mv.meer.net (outboundx.mv.meer.net [209.157.152.12]) by hub.freebsd.org (Postfix) with ESMTP id F112C37B400; Thu, 28 Feb 2002 09:35:18 -0800 (PST) Received: from meer.meer.net (mail.meer.net [209.157.152.14]) by outboundx.mv.meer.net (8.11.6/8.11.6) with ESMTP id g1SHZEs27537; Thu, 28 Feb 2002 09:35:14 -0800 (PST) (envelope-from gnn@neville-neil.com) Received: from neville-neil.com ([209.157.133.226]) by meer.meer.net (8.9.3/8.9.3/meer) with ESMTP id JAA1667989; Thu, 28 Feb 2002 09:34:35 -0800 (PST) Message-Id: <200202281734.JAA1667989@meer.meer.net> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Robert Watson Cc: current@FreeBSD.ORG Subject: Re: Discussion of guidelines for additional version control mechanisms (fwd) In-Reply-To: Message from Robert Watson of "Thu, 28 Feb 2002 11:14:23 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 28 Feb 2002 09:34:34 -0800 From: "George V. Neville-Neil" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > What I mean by "imposing structure" is: > > - Identify patterns of development and structure that seem to have evolved > naturally as part of the maturing of the FreeBSD Project > - Determine which patterns tend to result in the most productive and > parallel development efforts, not to mention which are the most popular > - Selectively reinforce those patterns to improve the ability of > developers to rely on the patterns This sounds fine to me but we're going to have to write it down somewhere and then discuss it. This tossing ideas in the ether is not going to work because to refer back to earlier points we have to either have huge emails with everyone's comments in them, or constantly be reading the archives. So, please, if you think this is important write down your findings/current beliefs somewhere (I think TWiki or something like it is perfect for this) and let everyone comment and modify them until we have an understanding. Then lets figure out what structure we need and write that down as well. Think of it as a FreeBSD constitution if you must, only much more lightweight. You're obviously taking the lead here and that's fine, every project (and this discussion is really a project) needs a leader. > I think we're in the same boat here. You believe that process can help > streamline the development process, and be used to help avoid the > disagreements we've run into recently (assuming I read you correctly :-). > I think so too. I agree we can't bring too much process--that won't work > for a large number of reasons. But a little bit of process can go a long > way. In particular, I'm looking for a little bit of process that will > help address the perceived problems of the current situation. > Yes, you read me correctly. My mantra is, "Write it down." :-) Later, George -- George V. Neville-Neil gnn@neville-neil.com NIC:GN82 "Those who would trade liberty for temporary security deserve neither" - Benjamin Franklin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message