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

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.

It seems to me that we are now going to abandon the recognized brand name of "LibO" (well-known internally, and somewhat externally recognized by the communities) and try to establish a more generic brand "Libre" which is usually associated with a movement, and, we have already established that there is a pronunciation problem with some of our communities with the word "Libre".

The "LibO" brand is already tied into the "LibreOffice" project name, why not expand its use? We have already reserved it in domain names, project names such as LibOx, we are already using it as an unofficial wiki page naming convention, and it could easily be tied in with a brand mascot -- I am not sure that a "Libre" mascot is quite as sexy.

I don't believe that "LibO" has contributed to the dilution of our brand, but reinforced it. It is recognizable and easily pronounced by all, it is unique!!!, and, most of all, it is catchy. If any group wanted to claim it as their own, we can already claim the word "LibO" as our own by proof of usage with our project (prior use). Is this not what we are looking for?

Cheers,

Marc

I do not want to abandon LibO, but I want to strengthen Libre, because the name of the software is LibreOffice and there is a huge number of people who use LO and call it OOo based on 10 years habits.

In addition, strengthening "libre" will reinforce the association between our software and Liberty, as the two words share the same root (and Liberty is a very well know word in English, which seems to be the native pronunciation with the highest number of problems).

I am also using "libre" as a distinctive word for our project, by adding the tagline *because "libre" is better than "open"* to every presentation I make around the world. Of course, I am playing on both words here, and I am sure that there will be people unhappy about this tagline (but none of us is supposed to make all people happy).

Best, Italo

Hi Charles,

Charles-H. Schulz wrote (05-11-12 21:11)

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

Ah, so not how each native-language project should call itself :slight_smile:

If people that contacted you/board on the issue did not deliver a ready-to-use-for-us solution, I would keep it at "LibreOffice native-language project".
Simply because I have no better idea. Sorry., I mean: how else make something comprehensive, compact and nice sounding from "support, marketing, testing and localization"?

And the structure...? Isn't it enough if we try to listen, cooperate and support each other?
For me that is more important then if group X from language/region Y is a foundation, society, informal team, two people, er even a sub-entity of TDF.

And as for the names they use, see below.

Cheers,
Cor

Hello Cor,

Hi Charles,

Charles-H. Schulz wrote (05-11-12 21:11)

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

Ah, so not how each native-language project should call itself :slight_smile:

Finally someone who understands :slight_smile:

If people that contacted you/board on the issue did not deliver a
ready-to-use-for-us solution, I would keep it at "LibreOffice
native-language project".
Simply because I have no better idea. Sorry., I mean: how else make
something comprehensive, compact and nice sounding from "support,
marketing, testing and localization"?

Indeed. One nuance though is that it would not be about keeping
native-language projects as a denomination but rather reintroducing the
term (officially , there are only "communities" and no native-language
project here). But I'm not the one to decide, it's up to you folks here.

And the structure...? Isn't it enough if we try to listen, cooperate and
support each other?
For me that is more important then if group X from language/region Y is
a foundation, society, informal team, two people, er even a sub-entity
of TDF.

I think the same but it seems not everyone does, and people expect
structure...

best,
Charles.

Hi Italo, all,

It seems to me that we are now going to abandon the recognized brand
name of "LibO" (well-known internally, and somewhat externally
recognized by the communities) and try to establish a more generic brand
"Libre" which is usually associated with a movement, and, we have
already established that there is a pronunciation problem with some of
our communities with the word "Libre".

I do not want to abandon LibO, but I want to strengthen Libre, because
the name of the software is LibreOffice and there is a huge number of
people who use LO and call it OOo based on 10 years habits.

In addition, strengthening "libre" will reinforce the association
between our software and Liberty, as the two words share the same root
(and Liberty is a very well know word in English, which seems to be the
native pronunciation with the highest number of problems).

I am also using "libre" as a distinctive word for our project, by adding
the tagline *because "libre" is better than "open"* to every
presentation I make around the world. Of course, I am playing on both
words here, and I am sure that there will be people unhappy about this
tagline (but none of us is supposed to make all people happy).

But Italo, it's not about the brand here, I agree with you that we
should stress LibreOffice instead of any other name for our suite or the
international community.

We are talking here about the name of the language communities we
represent and we need a unique name that show the world who we are and
the work we are doing for this product and the overall community.
We need a name that is easy to use, easy to remember, with no ambiguity
about the languages vs countries.

Even if we keep the name LibreOffice Native-Language Project - in short
LONLP ;-), there is no issue at all, what I would like is that everybody
behind this name feel happy with it and feel part of it wherever we
speak about it. I think that this is what Charles was asking to them.

Kind regards
Sophie

Charles-H. Schulz wrote (07-11-12 11:47)

Finally someone who understands :slight_smile:

:wink: thanks to your endurance in explaining

Indeed. One nuance though is that it would not be about keeping
native-language projects as a denomination but rather reintroducing the
term (officially , there are only "communities" and no native-language
project here).

Then I would say "LibreOffice native-language communities" / "NLC"

I think the same but it seems not everyone does, and people expect
structure...

What is expected that a structure would deliver?
Money from TDF for activities? Acknowledgement that helps the NLC with it's work (being locally accepted)? Invitations for events? ...?

Cheers,

Hi Italo,

It seems to me that we are now going to abandon the recognized brand
name of "LibO" (well-known internally, and somewhat externally
recognized by the communities) and try to establish a more generic brand
"Libre" which is usually associated with a movement, and, we have
already established that there is a pronunciation problem with some of
our communities with the word "Libre".

I do not want to abandon LibO, but I want to strengthen Libre, because
the name of the software is LibreOffice and there is a huge number of
people who use LO and call it OOo based on 10 years habits.

In addition, strengthening "libre" will reinforce the association
between our software and Liberty, as the two words share the same root
(and Liberty is a very well know word in English, which seems to be the
native pronunciation with the highest number of problems).

I am also using "libre" as a distinctive word for our project, by adding
the tagline *because "libre" is better than "open"* to every
presentation I make around the world. Of course, I am playing on both
words here, and I am sure that there will be people unhappy about this
tagline (but none of us is supposed to make all people happy).

Best, Italo

A big problem with using/pushing "Libre" is that there is no way that we could ever claim copyright on it at all. At least with LibO, we already hold some kind of rights; this is something of quite large importance in name usage marketing.

Cheers,

Marc

Bonjour Sophie,

But Italo, it's not about the brand here, I agree with you that we
should stress LibreOffice instead of any other name for our suite or the
international community.

We are talking here about the name of the language communities we
represent and we need a unique name that show the world who we are and
the work we are doing for this product and the overall community.
We need a name that is easy to use, easy to remember, with no ambiguity
about the languages vs countries.

Even if we keep the name LibreOffice Native-Language Project - in short
LONLP ;-), there is no issue at all, what I would like is that everybody
behind this name feel happy with it and feel part of it wherever we
speak about it. I think that this is what Charles was asking to them.

Kind regards
Sophie

Just FYI, we had debated the use of LO and had agreed that the pronunciation in EN "LO" came too close to the word "Low" which could easily be used to belittle our office suite by competitors.

I would suggest that using "LO" would not be a good choice for this reason.

Cheers,

Marc