From owner-freebsd-chat Tue Mar 28 7:14: 8 2000 Delivered-To: freebsd-chat@freebsd.org Received: from jasper.nighttide.net (jasper.nighttide.net [216.227.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 24DB837BF76 for ; Tue, 28 Mar 2000 07:14:03 -0800 (PST) (envelope-from darren@nighttide.net) Received: from localhost (darren@localhost) by jasper.nighttide.net (8.9.3/8.9.3) with ESMTP id KAA09817 for ; Tue, 28 Mar 2000 10:13:42 -0500 (EST) Date: Tue, 28 Mar 2000 10:13:42 -0500 (EST) From: Darren Henderson To: freebsd-chat@FreeBSD.ORG Subject: Re: BSDCon East In-Reply-To: <4.2.2.20000327164841.04665500@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 27 Mar 2000, Brett Glass wrote: > At 01:30 PM 3/27/2000 , John wrote: > > >Very good points, but it would be nice to be able to allow a maximum amount of people to be able to *drive* as well. > > Well, once you get off of the West Coast, the distribution of BSD users is fairly uniform throughout the country. I've seen concentrations in Texas, Denver/Boulder/Colorado Springs, Phoenix, New York, Atlanta, and Massachusetts. OpenBSD has (naturally) a bigger presence in Canada. > > Due to this far-flung constituency, I'm not sure how we'd select a physical location if the goal were to minimize the number of people who drove. Hmmmm.... Maybe the answer is not to have a physical location at all? I hear that someone once did a very successful "virtual" science fiction convention that lasted a whole weekend. Maybe we could do a "virtual BSDCon?" Actually, Cincy, in terms of air access, is pretty central for the east. Of course my preferance would be for costal Maine, but then I'm prejudiced and I don't like to travel... ______________________________________________________________________ Darren Henderson darren@nighttide.net Help fight junk e-mail, visit http://www.cauce.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message