You misunderstood, the project name becomes the subdomain name associated with the website
there is no project called ‘ooo’ so ‘ooo.apache.org’ will not be accepted. Also, we would not redirect away from the *.apache.org domain, if anything, it would be the other way around. Apologies for top posting, one of the sins of replying to html email. Gav… From: [email protected] [mailto:[email protected]] On Behalf Of Alexandro Colorado Sent: Tuesday, 12 July 2011 5:58 PM To: [email protected]; [email protected] Subject: Re: OpenOffice.org (was Re: Ooo blog) On Tue, Jul 12, 2011 at 2:41 AM, Gavin McDonald <[email protected]> wrote: > -----Original Message----- > From: Marcus (OOo) [mailto:[email protected]] > Sent: Tuesday, 12 July 2011 5:11 PM > To: [email protected] > Subject: Re: OpenOffice.org (was Re: Ooo blog) > > Am 07/12/2011 08:55 AM, schrieb Pavel Janík: > >> It seems to me that a lot of the problem arises in keeping the > development project and the product brand names exactly the same. > > > > Another proposal: > > > > Product name: OpenOffice.org. > > > > Project name: Apache OpenOffice.org. > > > > I'm strongly against mixing OOo and OO here. > > +1 > > Keep it simpe for the users and don't make any possibility for > misunderstandings. With domain names for ALL Apache projects coming under the pattern of $projectname.apache.org how you propose that would work if Apache OpenOffice.org is the project name? (only openofficeorg.apache.org springs to mind if you intend to keep org in the project name) (And a shocking name that becomes imho) Thanks Gav... Since apache will own the openoffice.org domain you can as easily put a redirector from http://ooo.apache.org to http://apache.openoffice.org > > Marcus -- Alexandro Colorado OpenOffice.org Español http://es.openoffice.org
