[From nobody Thu Oct 11 16:55:56 2007 Return-Path: <brug-talk-bounces@rubyforge.org> Delivered-To: pv@xaop.com Received: (qmail 27414 invoked by uid 1010); 11 Oct 2007 20:52:35 -0000 Received: from unknown (HELO malachi.priorweb.be) (127.0.0.1) by malachi.priorweb.be with SMTP; 11 Oct 2007 20:52:35 -0000 Received: from rubyforge.org (unknown [205.234.109.19]) by malachi.priorweb.be (Postfix) with ESMTP for <peter@xaop.com>; Thu, 11 Oct 2007 22:52:31 +0200 (CEST) Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 3A36B185861C; Thu, 11 Oct 2007 16:52:31 -0400 (EDT) X-Original-To: brug-talk@rubyforge.org Delivered-To: brug-talk@rubyforge.org Received: from astra.telenet-ops.be (astra.telenet-ops.be [195.130.132.58]) by rubyforge.org (Postfix) with ESMTP id 2CC2D1858616 for <brug-talk@rubyforge.org>; Thu, 11 Oct 2007 16:52:28 -0400 (EDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by astra.telenet-ops.be (Postfix) with SMTP id 5813E38127 for <brug-talk@rubyforge.org>; Thu, 11 Oct 2007 22:52:28 +0200 (CEST) Received: from [84.193.22.47] (d54C1162F.access.telenet.be [84.193.22.47]) by astra.telenet-ops.be (Postfix) with ESMTP id 3B3403811D for <brug-talk@rubyforge.org>; Thu, 11 Oct 2007 22:52:28 +0200 (CEST) Message-ID: <470E8D0B.4090607@xaop.com> Date: Thu, 11 Oct 2007 22:52:27 +0200 From: Peter Vanbroekhoven <peter@xaop.com> User-Agent: Thunderbird 1.5.0.13 (X11/20070824) MIME-Version: 1.0 To: brug-talk@rubyforge.org References: <470E2D48.1030700@xaop.com> <ffe522d40710111258p7453f302g9f90751a12f59efd@mail.gmail.com> In-Reply-To: <ffe522d40710111258p7453f302g9f90751a12f59efd@mail.gmail.com> Subject: Re: [Brug-talk] [Brug-admin] Domain name X-BeenThere: brug-talk@rubyforge.org X-Mailman-Version: 2.1.9 Precedence: list Reply-To: brug-talk@rubyforge.org List-Id: <brug-talk.rubyforge.org> List-Unsubscribe: <http://rubyforge.org/mailman/listinfo/brug-talk>, <mailto:brug-talk-request@rubyforge.org?subject=unsubscribe> List-Archive: <http://rubyforge.org/pipermail/brug-talk> List-Post: <mailto:brug-talk@rubyforge.org> List-Help: <mailto:brug-talk-request@rubyforge.org?subject=help> List-Subscribe: <http://rubyforge.org/mailman/listinfo/brug-talk>, <mailto:brug-talk-request@rubyforge.org?subject=subscribe> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: brug-talk-bounces@rubyforge.org Errors-To: brug-talk-bounces@rubyforge.org X-Virus-Scanned: Passed X-Spam-Scanned: 0.0 X-Spam-Status: NO X-Scanned-By: PriorWeb mailfilter Alain Ravet wrote: > > This is something both Peter and I support, but we need to know > > what you guys think about this. > > Sounds good. > Just one remark : I think the redirect should be in the other redirection : > rubyist.be => rubybelgium.be > , with rubybelgium.be being the official/public address of the community. > > The rationale : urls are our signatures. > Each time we will communicate with the world (read: the others) we > will publish a url. > > > http://rubybelgium.be/conferences > > > speaks more and covers more ground than > > > http://rubyist.be/conferences > Hmmmm... The way I intended this was that *initially* http://rubybelgium.be/ would redirect to http://rubyist.be/ just as a way to use the rubybelgium.be domain and get the name out there. Anything but http://rubybelgium.be/ would be invalid on this domain such that only rubyist.be URLs get out there except for the root of rubybelgium.be. Then, at some point, rubybelgium.be could start leading its own life when we get the "Ruby Belgium" organization set up (could be a VZW/ASBL). Then there would be a http://rubybelgium.be/conferences, and a http://rubyist.be/brug, but not a http://rubyist.be/conferences or a http://rubyist.be/conferences, or at least not necessarily so nor with the same information. So basically, the address of the community would be rubyist.be, that of the Ruby Belgium organisation would be rubybelgium.be. One is the geeky side, the other the official side. Two faces of the same coin. Two sides that in a sense lead there own lives. The connection of the redirect would only be temporary. A good reason to have these two separate domains is that one would require a lot of care in setting up, taking marketing into consideration, and basically building our image. The other would allow us to be our own geeky selves without caring (too much) about our image. These are the two aspects that Peter hammered on at the BRUG meeting, and at the risk of a "here he goes again", I think it is a good thing that these are reflected in the domain names. Peter, did I get this right? Regards, Peter PS : should I change the reply-to here too? _______________________________________________ Brug-talk mailing list Brug-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/brug-talk ]