What's in a name? former Native-Language projects and structure

Hello all,

Several volunteers have approached board and MC members about one
seemingly secondary issue, which has not been dealt in any way since the
beginning of the LibreOffice project: what structure, and what name,
should we give to the former Native-langage projects that are even to
this day an essential and invaluable part of our community.

A short reminder of what native-language projects are: they're not only
localization projects. They do translation (localization) of
LibreOffice, users support in a specific language, local promotion and
marketing, documentation translation, QA of localized builds, etc.

Because of that, the name is somewhat a non-trivial decision, and it
also calls for a more formalized structure of these teams.

I thought I would start this discussion as I was the lead of the
"Native-Language Confederation" during the times of the old
OpenOffice.org project. Now I no longer work on this, but at least some
of you know me :slight_smile: .

Your ideas are welcome.

best,

Following LibreUmbria nice composition between "libre" and the
geographical name, the Italian community has just decided - well, there
is a benevolent dictator here, and only a few people would like to have
a real disscussion with him :wink: - that LibreItalia is a very good name
for the native language community.

Hello Italo,

> Because of that, the name is somewhat a non-trivial decision, and it
> also calls for a more formalized structure of these teams.

Following LibreUmbria nice composition between "libre" and the
geographical name, the Italian community has just decided - well, there
is a benevolent dictator here, and only a few people would like to have
a real disscussion with him :wink: - that LibreItalia is a very good name
for the native language community.

Very nice and beautiful name!
I was wondering about how we should call the "native-language" projects,
and whether we should formalize them more. ... Do we want to call them
"native-language projects"again?

best,

LibreProject France, LibreProject Italia, LibreProject Germany, etcetera

Hi all,

using country names may be is not a good option.

What about languages spoken in many countries but with a single
LibreOffice "native-language" team, as Spanish or English.In the other
hand, there are languages and teams without an reference country, like
Esperanto or Catalan.

Yours,

Joan Montané

No, we are speaking about languages, not regions or countries and we are
searching for a name that will cover all of our local projects.

But, Charles, thanks a lot for opening this discussion. Yes we need a
name that represent us and all the work we are doing aside localization.
When I saw the presentation of the Japanese group in Berlin, I thought
that we should really be able to exchange more between us but also
advertize our work.

Kind regards
Sophie

You are right, I am biased because my native language is spoken in a single country, but the concept is the same: LibreProject French or Français, LibreProjet Castillan or Castellano, and so on.

Of course, LibreProject Catalan or Català, as I am in Barcelona now, and Català is the language spoken here (and I start to get some words out of a discussion, but I am still more familiar with Castillan).

Hi Charles, all,

Hello Italo,

Because of that, the name is somewhat a non-trivial decision, and it
also calls for a more formalized structure of these teams.

Following LibreUmbria nice composition between "libre" and the
geographical name, the Italian community has just decided - well, there
is a benevolent dictator here, and only a few people would like to have
a real disscussion with him :wink: - that LibreItalia is a very good name
for the native language community.

Very nice and beautiful name!
I was wondering about how we should call the "native-language" projects,
and whether we should formalize them more. ... Do we want to call them
"native-language projects"again?

I'm not against Native-Language Project, even if it's difficult to
translate, I think it illustrates quite well who we are :slight_smile:

Kind regards
Sophie

Simply LibreProjects, we must grow our brand awareness, and we should use "libre" as much as possible. Native Language Project does not have any association with TDF or LibreOffice, and might be associated with anything (and it was associated with OOo, and Andrea Pescetti is trying to associate it with Apache OO, if you look at one of his presentations at ApacheCon). I am for changing the name to something different and more catchy, and associated with LibreOffice.

LibreProjects can be associated with Marketing, Native Languages, Localization, Documentation (although there is ODFAuthors), and many other things, and helps with the branding.

Italo Vignoli wrote (05-11-12 14:45)

Simply LibreProjects, we must grow our brand awareness, [...]

I like the word, but the current users of LibreProjects might like to be involved in discussing or see that there is some reasonable distinction that makes clear that we talk about LibreOffice related projects.

Another idea: LibreOffice NLP Dutch, LibreOffice NLP Italy/Italian (just what people would think fits best for their situation), ...

Hi Cor,

Italo Vignoli wrote (05-11-12 14:45)

Simply LibreProjects, we must grow our brand awareness, [...]

I like the word, but the current users of LibreProjects might like to be
involved in discussing or see that there is some reasonable distinction
that makes clear that we talk about LibreOffice related projects.

Another idea: LibreOffice NLP Dutch, LibreOffice NLP Italy/Italian (just
what people would think fits best for their situation), ...

IMHO won't be that good:
NLP is nero-linguistic programming [1] and we should'nt associate with this.

[1] http://en.wikipedia.org/wiki/Neuro-linguistic_programming

Hi all,
[...]

Your ideas are welcome.

My first idea:
LibOn_[local]

means "LibreOffice national"

corresponding to:
- LibO (LibreOffice)
- LibOx (LibreOffice-Box)

and will nationalized looks like:
LibOn_EN
LibOn_FR
LibOn_NL
LibOn_DE
LibOn_CA-VAL
LibOn_PT-BR

Why not LibreON then? We must try to use "libre" as much as we can, in order to grow brand awareness.

Hi Italo,

Why not LibreON then?

1. Because of:

corresponding to:
- LibO (LibreOffice)

Must then be LibreO?

- LibOx (LibreOffice-Box)

Must then be LibreOx or LibrebOx (loosing most/all)

2. Shout it loud:

- LibreOn
- LibOn

> We must try to use "libre" as much as we can, in
> order to grow brand awareness.

Do we? Or can we have "LibO" even for brand awareness?

http://wiki.documentfoundation.org/Marketing/Branding#LibreOffice 1)

The acronym LibO *is* some kind of official now. Otherwise we should change all file names for downloading.

And so in following this brand awareness...

Of course that point will get a discussion about the branding and not about the name of NLP. And that should be an other thread.

Grüße
k-j

P.S.:
1) The link to
http://www.documentfoundation.org/lists/discuss/msg00430.html
is broken.

Hi
LibreOffice Brasil, period.
Olivier

LibO was created to stop a lengthy discussion on the pronunciation problem of LibreOffice, which is now over. Unfortunately, although I like it, it has contributed to the dilution of our brand equity and we should now try to avoid to use it for new names, while I would not change old and established ones.

So, I would not change LibOCon and LibOx, and any other name we already use, but I would try to use Libre as much as we can for new names, in order to strengthen the "libre" concept and association.

Brazil is a different story, you do not have a past and a present with OpenOffice.

In Italy, most people use LibreOffice and call it OpenOffice, including contributors: in this way, brand equity becomes a nightmare.

We should try to create a subliminal association between "libre" and office, by using libre as much as we can inside the project. Brand is a real issue, because is the main reason behind Apache OO downloads, and we must stop it ASAP.

LibO was created to stop a lengthy discussion on the pronunciation
problem of LibreOffice, which is now over.

So you'll find the same conversation for a native language community. We
need to be able to pronounce our name :wink:
Unfortunately, although I

like it, it has contributed to the dilution of our brand equity and we
should now try to avoid to use it for new names, while I would not
change old and established ones.

I think that this name is more internal and we should let our
contributors use the name they prefer. It's very important for those
projects to recognize themselves as part of the overall project and if
LibO is the one, let's use it. The brand will benefit of any names where
the community is behind.

So, I would not change LibOCon and LibOx, and any other name we already
use, but I would try to use Libre as much as we can for new names, in
order to strengthen the "libre" concept and association.

Libre is very difficult to pronounce for lot of us, so let stick with
something that is easier for our language communities to feel united.

Kind regards
Sophie

Sophie Gautier wrote (05-11-12 19:37)

Libre is very difficult to pronounce for lot of us, so let stick with
something that is easier for our language communities to feel united.

Would it be an idea to give the various groups the choice from 3, maybe 4 alternatives, which fits them best?

e.g LibreOffice x / LibreOffice Project x / LibO x ?

I think we won't have difficulty, as Sophie states, to recognise our own groups/people. And the communication purpose of the name is mostly local/regional.

Cheers,

Hi,

Quick note. It's not about each project's name but how do we call the
Libreoffice's native-language projects in general.

Best,
Charles.