incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Weir <>
Subject Re: Regional AOO sites [was: Re:]
Date Wed, 28 Mar 2012 20:52:47 GMT
On Wed, Mar 28, 2012 at 3:26 PM, Claudio Filho <> wrote:

> Hi
> 2012/3/14 Rob Weir <>:
> > 2) Domain name ""
> >
> > Both are likely confusing to the consumer and falsely imply the
> > identity and source of their goods.
> >
> > BTW, I created a place in Bugzilla to track things like this:
> >
> >
> Rob, a NL related question: if someone of us bring up a website for
> regional/local group, in native language, how do you will see this
> act?
We have the ability to host such sites here at Apache, as subdomains of the domain.  For example, is for
German.  It then redirects to which is a
subdirectory of our web site's content tree.

If a website is done that way, then project committers have direct access
to checking in changes, via the CMS or Subversion.  Other contributors can
submit patches.

> A example was here, in Brazil. At begin, the "" was
> with us, and we created a portal with Drupal, talking in brazilian
> portuguese all news about ODF/OOo in our country and the world (with
> the respective translation, when was the case). At final, in function
> of the trademark problems with "openoffice", we changed to "broffice",
> but always clearly linked with main project.
> Can we follow this strategy?
Which strategy? Calling something "BrOffice"?

> A CMS can give us a more flexibility to work. Is possible? What you
> (and Apache) think about?
For a website hosted at Apache, as part of the website, the
CMS is available by default.

It is also certainly possible to have your own website, external to Apache,
and run by local volunteers.  But it would be important to choose a domain
name that did not imply that it was an official OpenOffice website.

The simplest thing, I think, would be to host your website at Apache,
something like  Would that work?


> best,
> Claudio

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message