You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Claudio Filho <fi...@gmail.com> on 2012/03/28 21:26:52 UTC
Regional AOO sites [was: Re: openoffice.fm]
Hi
2012/3/14 Rob Weir <ro...@apache.org>:
> 2) Domain name "openoffice.fm"
>
> 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:
>
> https://issues.apache.org/ooo/enter_bug.cgi?product=trademark
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?
A example was here, in Brazil. At begin, the "openoffice.org.br" 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?
A CMS can give us a more flexibility to work. Is possible? What you
(and Apache) think about?
best,
Claudio
Re: Regional AOO sites [was: Re: openoffice.fm]
Posted by Dave Fisher <da...@comcast.net>.
On Mar 29, 2012, at 7:11 AM, Rob Weir wrote:
> On Thu, Mar 29, 2012 at 9:29 AM, Claudio Filho <fi...@gmail.com> wrote:
>
>> Hi
>>
>> 2012/3/28 Rob Weir <ro...@apache.org>:
>>> We have the ability to host such sites here at Apache, as subdomains of
>> the
>>> openoffice.org domain. For example, http://de.openoffice.org is for
>>> German. It then redirects to http://www.openoffice.org/de/ which is a
>>> subdirectory of our web site's content tree.
>>
>> Yes, that is (practically) the same thing that before.
>>
>>> 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.
>>
>> I see different, Rob, why in this way is good to maintain a "core"
>> pages, like in Debian (where i help too) that all content are under
>> CVS using WML, giving a very good support to manage and see how old is
>> a translation. A example is this page[1].
>> [1]http://www.debian.org/devel/website/stats/pt#outdated
>>
>>
> I see three models:
>
> 1) Core English portal that is translated into other languages. So no
> local variation, other than translation.
>
> 2) Each language creates its own NL entry page, with design and content
> determined by the NL community
>
> 3) A core English page that is modular, that has core content that is
> translated for other languages, but also has a panel for local news
> stories, and additional NL-specific content available on pages linked to
> from the home page.
>
> Today, with the openoffice.org, we have a mix. And some would say we have
> a mess.
That we still have the whole mess is an achievement.
>
> My personal preference would be something like #3. Get a basic translation
> for all languages, with static content that will remain valid for a long
> period of time. We might not have a vibrant Bulgarian or Albanian
> community in the project today, but we can have a website translated once,
> and still be useful to end users. But then we need additional flexibility
> for active NL communities, so they can customize and enhance.
+1. I agree and when I have another volunteer window we can make some progress on improving the main, download, some policy pages, a how to contribute site translations. Also news feeds etc. We already discussed some of the technical details.
>
>
>>> Can we follow this strategy?
>>>>
>>> Which strategy? Calling something "BrOffice"?
>>
>> To have a regional site out of Apache's infra.
>>
>>> For a website hosted at Apache, as part of the openoffice.org website,
>> the
>>> CMS is available by default.
>>
>> humm... a Wiki can be considered as CMS, but isn't easy or with same
>> resources/features that a communicative site. But with this phrase i
>> understand that here isn't the correct place to discuss this, and yes
>> in mkting list. I will do it.
>>
>>
> The Apache CMS allows someone to edit files via a browser-based interface.
> So it is very easy for a committer to make changes. Not as easy as a wiki,
> but a lot easier than checking out files via SVN.
>
> And I think we could do a hybrid model as well. For example, we could have
> a static HTML homepage for a language, but then have the links from that
> page go to a wiki that the NL community maintains. That would give us a
> consistent "look & feel" for the homepage, but also give easier authoring
> for the other pages.
What's important to know in this discussion is that the modular parts that I plan should be in markdown and not html.
I already have the ability to have translated top nav buttons, branding text, search and home be translated
All these files so far are markdown / .mdtext files. I plan to have the modules be mdtext as well.
I have the plan, I just need to find the time.
Regards,
Dave
>
>
>
>
>>> 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.
>>
>> As BrOffice, always became clear that was a *community* website, and
>> was a strategy to bring more volunteers and promote the product, like
>> a "adaptation land" before to jump for international project. We can
>> receive good efforts from a non-english community speakers inside each
>> country/region, finding people that can to do this "bridge" (or
>> facilitator) for AOO project.
>>
>>
> I think this approach can be done at Apache as well. You have a pt_br
> mailing list for the NL community, to coordinate the contents of the
> website.
>
>
>
>>> The simplest thing, I think, would be to host your website at Apache,
>>> something like http://br.openoffice.org. Would that work?
http://www.openoffice.org/pt-br/ exists and already has a simple page.
I'd help if someone provided a translation for the topnav.
Or, shouldn't we work to co-ordinate with the pootle translators? Probably after 3.4. Meanwhile my plan can proceed and we can decide later what is special and what is piped in from pootle.
>>
>> As i said, I see fine to translate the portal for all languages, like
>> in Debian, but when we start to bring news, localized material (or
>> more specific like spreadsheets based in a local law), isn't
>> interesting to share. Others, like presentation templates, i agree
>> that is interesting to converge and to join.
>>
>> However, i will rewrite this email in mkting list.
Regards,
Dave
>>
>> Best,
>> Claudio
>>
Re: Regional AOO sites [was: Re: openoffice.fm]
Posted by Rob Weir <ro...@apache.org>.
On Thu, Mar 29, 2012 at 9:29 AM, Claudio Filho <fi...@gmail.com> wrote:
> Hi
>
> 2012/3/28 Rob Weir <ro...@apache.org>:
> > We have the ability to host such sites here at Apache, as subdomains of
> the
> > openoffice.org domain. For example, http://de.openoffice.org is for
> > German. It then redirects to http://www.openoffice.org/de/ which is a
> > subdirectory of our web site's content tree.
>
> Yes, that is (practically) the same thing that before.
>
> > 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.
>
> I see different, Rob, why in this way is good to maintain a "core"
> pages, like in Debian (where i help too) that all content are under
> CVS using WML, giving a very good support to manage and see how old is
> a translation. A example is this page[1].
> [1]http://www.debian.org/devel/website/stats/pt#outdated
>
>
I see three models:
1) Core English portal that is translated into other languages. So no
local variation, other than translation.
2) Each language creates its own NL entry page, with design and content
determined by the NL community
3) A core English page that is modular, that has core content that is
translated for other languages, but also has a panel for local news
stories, and additional NL-specific content available on pages linked to
from the home page.
Today, with the openoffice.org, we have a mix. And some would say we have
a mess.
My personal preference would be something like #3. Get a basic translation
for all languages, with static content that will remain valid for a long
period of time. We might not have a vibrant Bulgarian or Albanian
community in the project today, but we can have a website translated once,
and still be useful to end users. But then we need additional flexibility
for active NL communities, so they can customize and enhance.
>> Can we follow this strategy?
> >>
> > Which strategy? Calling something "BrOffice"?
>
> To have a regional site out of Apache's infra.
>
> > For a website hosted at Apache, as part of the openoffice.org website,
> the
> > CMS is available by default.
>
> humm... a Wiki can be considered as CMS, but isn't easy or with same
> resources/features that a communicative site. But with this phrase i
> understand that here isn't the correct place to discuss this, and yes
> in mkting list. I will do it.
>
>
The Apache CMS allows someone to edit files via a browser-based interface.
So it is very easy for a committer to make changes. Not as easy as a wiki,
but a lot easier than checking out files via SVN.
And I think we could do a hybrid model as well. For example, we could have
a static HTML homepage for a language, but then have the links from that
page go to a wiki that the NL community maintains. That would give us a
consistent "look & feel" for the homepage, but also give easier authoring
for the other pages.
> > 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.
>
> As BrOffice, always became clear that was a *community* website, and
> was a strategy to bring more volunteers and promote the product, like
> a "adaptation land" before to jump for international project. We can
> receive good efforts from a non-english community speakers inside each
> country/region, finding people that can to do this "bridge" (or
> facilitator) for AOO project.
>
>
I think this approach can be done at Apache as well. You have a pt_br
mailing list for the NL community, to coordinate the contents of the
website.
> > The simplest thing, I think, would be to host your website at Apache,
> > something like http://br.openoffice.org. Would that work?
>
> As i said, I see fine to translate the portal for all languages, like
> in Debian, but when we start to bring news, localized material (or
> more specific like spreadsheets based in a local law), isn't
> interesting to share. Others, like presentation templates, i agree
> that is interesting to converge and to join.
>
> However, i will rewrite this email in mkting list.
>
> Best,
> Claudio
>
Re: Regional AOO sites [was: Re: openoffice.fm]
Posted by Claudio Filho <fi...@gmail.com>.
Hi
2012/3/28 Rob Weir <ro...@apache.org>:
> We have the ability to host such sites here at Apache, as subdomains of the
> openoffice.org domain. For example, http://de.openoffice.org is for
> German. It then redirects to http://www.openoffice.org/de/ which is a
> subdirectory of our web site's content tree.
Yes, that is (practically) the same thing that before.
> 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.
I see different, Rob, why in this way is good to maintain a "core"
pages, like in Debian (where i help too) that all content are under
CVS using WML, giving a very good support to manage and see how old is
a translation. A example is this page[1].
[1]http://www.debian.org/devel/website/stats/pt#outdated
>> Can we follow this strategy?
>>
> Which strategy? Calling something "BrOffice"?
To have a regional site out of Apache's infra.
> For a website hosted at Apache, as part of the openoffice.org website, the
> CMS is available by default.
humm... a Wiki can be considered as CMS, but isn't easy or with same
resources/features that a communicative site. But with this phrase i
understand that here isn't the correct place to discuss this, and yes
in mkting list. I will do it.
> 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.
As BrOffice, always became clear that was a *community* website, and
was a strategy to bring more volunteers and promote the product, like
a "adaptation land" before to jump for international project. We can
receive good efforts from a non-english community speakers inside each
country/region, finding people that can to do this "bridge" (or
facilitator) for AOO project.
> The simplest thing, I think, would be to host your website at Apache,
> something like http://br.openoffice.org. Would that work?
As i said, I see fine to translate the portal for all languages, like
in Debian, but when we start to bring news, localized material (or
more specific like spreadsheets based in a local law), isn't
interesting to share. Others, like presentation templates, i agree
that is interesting to converge and to join.
However, i will rewrite this email in mkting list.
Best,
Claudio
Re: Regional AOO sites [was: Re: openoffice.fm]
Posted by Rob Weir <ro...@apache.org>.
On Wed, Mar 28, 2012 at 3:26 PM, Claudio Filho <fi...@gmail.com> wrote:
> Hi
>
> 2012/3/14 Rob Weir <ro...@apache.org>:
> > 2) Domain name "openoffice.fm"
> >
> > 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:
> >
> > https://issues.apache.org/ooo/enter_bug.cgi?product=trademark
>
> 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
openoffice.org domain. For example, http://de.openoffice.org is for
German. It then redirects to http://www.openoffice.org/de/ 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 "openoffice.org.br" 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 openoffice.org 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 http://br.openoffice.org. Would that work?
-Rob
> best,
> Claudio
>