by homeworld.cygnus.com with SMTP; 26 Nov 1998 23:48:55 -0000
	by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA23799;
	Fri, 27 Nov 1998 10:18:50 +1030 (CST)
	by freebie.lemis.com (8.9.1/8.9.0) id KAA31487;
	Fri, 27 Nov 1998 10:18:44 +1030 (CST)
Message-ID: <19981127101844.X67961@freebie.lemis.com>
Date: Fri, 27 Nov 1998 10:18:44 +1030
From: Greg Lehey <grog@lemis.com>
To: "Open Systems Inc." <opsys@open-systems.net>
Cc: netbsd-advocacy@NetBSD.ORG,
        FreeBSD advocacy list <FreeBSD-advocacy@FreeBSD.ORG>,
        advocacy@openbsd.org
Subject: Re: Merging Net/Free/Open-BSD together against Linux
References: <lubvhk2nq4v.fsf@pizza.stacken.kth.se> <Pine.BSF.3.96.981126171031.16281B-100000@pinkfloyd.open-systems.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <Pine.BSF.3.96.981126171031.16281B-100000@pinkfloyd.open-systems.net>; from Open Systems Inc. on Thu, Nov 26, 1998 at 05:21:54PM -0600
WWW-Home-Page: http://www.lemis.com/~grog
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062

On Thursday, 26 November 1998 at 17:21:54 -0600, Open Systems Inc. wrote:
>
> 	Here is my thought. As crazy as it may or may not be.
> If you want a collaboration between the 3 Free *BSD's why not have a BSD
> IETF group. Like the 3 primary architects from each *BSD, the kernel
> architect and the VM, and networking architect. Those 3 architects from
> each *BSD make up the BSD IETF. Thats 9 members. Those 9 work together to
> draw out RFC's the *BSD's can follow should they choose to implement
> something. Like threads for instance. They draw up the RFC on how threads
> should be done. and *IF* the various *BSD's decide to do threads there
> still doing it in their own Free|Net|Open BSD circles but they have to
> conform to the standard BSD RFC for threads.

I think it's a good idea to have some consensus on how things are
done.  But in the same anarchistic way that the individual BSDs
develop, it's unlikely that all groups would agree to implement all
points of the ``standard''.  On the other hand, it could help limit
gratuitous changes, and as Adrian Filipi-Martin suggested, it might
make sense to spend more time ensuring a more consistent userland.
This kind of initiative could help.

Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key