by omahpop1.omah.uswest.net with SMTP; 27 Nov 1998 00:31:43 -0000
Date: Thu, 26 Nov 1998 18:31:41 -0600 (CST)
From: "Open Systems Inc." <opsys@open-systems.net>
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
cc: Artur Grabowski <art@stacken.kth.se>, 
    Adrian Filipi-Martin <adrian@ubergeeks.com>, Greg Lehey <grog@lemis.com>, 
    Alicia da Conceicao <alicia@internetpaper.com>, netbsd-advocacy@NetBSD.ORG, 
    FreeBSD advocacy list <FreeBSD-advocacy@FreeBSD.ORG>, advocacy@openbsd.org
Subject: Re: Merging Net/Free/Open-BSD together against Linux 
In-Reply-To: <3605.912124752@zippy.cdrom.com>
Message-ID: <Pine.BSF.3.96.981126180808.16382A-100000@pinkfloyd.open-systems.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


	Of course its work. I've heard before from FreeBSD people that behind 
the scenes face to face the netbsd and freebsd people can talk and share
ideas but once they leave the room and resort to email it just turns into
flames and disputes. But I could be mis-informed. 

	In my mind the architects from the 3 BSD's getting together is the
best way to go. It's just an idea, that I think has the best chance of
working. And im not saying it can be done. The 3 groups may never get
along well enough to come together on anything. And thats fine. Im
perfectly happy with the way things are. I run FreeBSD, I'm very pleased
with the people behind it. As I am sure the NetBSD people are with NetBSD
and OpenBSD people with OpenBSD. It would be nice to get us all together
in a more coherent manor but that just might not be in the cards.

	It just seems to me that if you cant get a few of the
architects on each side to come together on things the foot soldiers
(commiters) are not likely to do so either. Jordan, Theo, and Charles are
more likely to know the way things really are. I could be totally out in
left field.
		
	Greg's idea may be a better idea. It might be better to just
forget about the pipe dream of a mutually represented committee of the 3
BSD's, and just try and share ideas and code. Setup a forum to discuss
drivers and other code and maybe setup a box that can be used by all.
Maybe that wont work either. Who gets commit privs, etc..

	I dunno maybe it just cant be done. Unless like someone said
earlier someone of impecable standards that NO ONE would argue with like
kirk stepped in and tried to get things working. But I think we all know
how likely that would be :-) This discussion has taken place many times
before and maybe it will just die again and nothing will come of it.
But maybe this time something might give. Who knows. Ill be interested in
new ideas that pop up and how things turn out this time around though.
Seeing the 3 work together would be nice. But im happy if things stay the
same. So either way is a win IMO.

Chris

"If you aim the gun at your foot and pull the trigger, it's UNIX's job to 
ensure reliable delivery of the bullet to where you aimed the gun (in
this case, Mr. Foot)." -- Terry Lambert, FreeBSD-Hackers mailing list.

===================================| Open Systems FreeBSD Consulting.
  FreeBSD 2.2.7 is available now!  | Phone: 402-573-9124
-----------------------------------| 3335 N. 103 Plaza #14, Omaha, NE 68134
   FreeBSD: The power to serve!    | E-Mail: opsys@open-systems.net
      http://www.freebsd.org       | Consulting, Network Engineering, Security
===================================| http://open-systems.net

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: 2.6.2

mQENAzPemUsAAAEH/06iF0BU8pMtdLJrxp/lLk3vg9QJCHajsd25gYtR8X1Px1Te
gWU0C4EwMh4seDIgK9bzFmjjlZOEgS9zEgia28xDgeluQjuuMyUFJ58MzRlC2ONC
foYIZsFyIqdjEOCBdfhH5bmgB5/+L5bjDK6lNdqD8OAhtC4Xnc1UxAKq3oUgVD/Z
d5UJXU2xm+f08WwGZIUcbGcaonRC/6Z/5o8YpLVBpcFeLtKW5WwGhEMxl9WDZ3Kb
NZH6bx15WiB2Q/gZQib3ZXhe1xEgRP+p6BnvF364I/To9kMduHpJKU97PH3dU7Mv
CXk2NG3rtOgLTEwLyvtBPqLnbx35E0JnZc0k5YkABRO0JU9wZW4gU3lzdGVtcyA8
b3BzeXNAb3Blbi1zeXN0ZW1zLm5ldD4=
=BBjp
-----END PGP PUBLIC KEY BLOCK-----