incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis E. Hamilton" <>
Subject RE: domains transferred to ASF
Date Thu, 18 Aug 2011 01:33:47 GMT
It is not unusual to have subdomains map to folders.

That is, you might maintain

and have map to it.  Even if someone navigated to the former, it
might appear to have redirected to the second case.  (Try going to <>.)

My impression is that even works for add-on domains.  You could map
to that subdomain which is actually anchored on a folder of the overall web-site tree.

My existence proof is the fact that my web hosting service provides all of these cases and
they run Apache httpd.  (I have only one web-hosting account and primary domain name.  Although
the subdomains exist I don't publicize them, but the add-on domains are the many ones I own
such as,,, etc.)

 - Dennis

PS: Technically, you could even have and served
from the same pages, though I think that is not such a hot idea, especially at the outset.

-----Original Message-----
From: Marcus (OOo) [] 
Sent: Wednesday, August 17, 2011 13:41
Subject: Re: domains transferred to ASF

Am 08/17/2011 10:00 PM, schrieb Rob Weir:
> On Wed, Aug 17, 2011 at 2:55 PM, Shane Curcuru<>  wrote:
[ ... ]
> Most of these don't appear to have much independent content.  I wonder
> whether something like this would be more maintainable going forward,
> to have a destination page for each language:
> Assuming our eventual TLP home is:, then
> we could have:
> and so on.
> Then have the existing domain names redirect to these.

Yes, should be a good way to have one home that we have to maintain but 
some redirects when a user has spelled the domain name not 100% correctly.

> Alternatively, we could do this via addresses:
> or even via subdomains:
> http://pl.openoffice.orgl
> Any committer should be able to add a new language at
>, but wouldn't adding a new subdomain
> require working with Apache Infra.  Or is there some magic we can do

My favorite way would be the [language] pattern as it 
looks better and more professional.

However, if it is way easier maintainance to have the[language] pattern, then we should go this way.

> with Apache server to make these map automatically via a rule?
> But I think this all leads back to the same basic question:  Do we
> want users to have a different home page than project volunteers?  I
> think so.  But we can still do that page via markdown, stored in SVN.

I haven't seen other voices in the past. So I think it is agreed in the 


> The question is only what domain names we direct to those pages.
>> Reminder: Apache projects normally host all their content on a *
>> domain.  I believe that in ooo's case, the future project will want to host
>> some content on other, non-a.o domains; however we should strive to make
>> most of the project be on an Apache site.
>> - Shane

View raw message