Date: prev next · Thread: first prev next last
2020 Archives by date, by thread · List index

Hi Marina, all,

Le 11/11/2020 à 11:09, Marina Latini a écrit :
On 09.11.2020 16:04, Italo Vignoli wrote:

Hello Italo and Community,
thanks for your inputs here.

and thanks for yours, I fully share your analysis :) Jumping to your

1. Product Label for the community supported version provided by TDF

COMMUNITY: I like it and this was my instinctive initial idea. After
some researches I understood what Italo told about the "open core"
meaning of this tag. As much as I like this proposal, I think our
business model is not the open core one and always with the
target-origin approach in mind my fear is that this could be misleading.
Our community is made of volunteers, ecosystem and investors/donors and
this tag is not a way to differentiate what the version provided by TDF
with volunteers support is in the reality.>
PERSONAL: always with this target-origin approach, I'm missing the
origin here. Which tag should be used for example by the Limux project
or by SUSE or by all the others that are investing in our project with a
contract with one of the ecosystem companies for fixing specific issues
without using their LTS branded version? Why we should ask to these
contributors to use a personal tag giving the wrong impression to their
users that the software is for "for personal use only" and they are the
"bad folks" not contributing to our open source project in the proper way?
agreed on both

ROLLING/TUMBLEWEED: I can be biased here as openSUSE community member
but "rolling" is not only something unstable. ;)
Look for example at openSUSE Tumbleweed. The distro is a rolling one, in
constant evolution, it's true, you can get all the updated software
available from upstream projects and the distro has in any case a really
extensive quality work done by SUSE, its partners and by the openSUSE
community. At the end, this tumbleweed concept is not like using a
master version of LibreOffice but is closer to chose fresh instead of
still. ;)
The concept of rolling is something that I really like. it's a shared
effort from all the contributors (volunteers, ecosystem and investors)
to deliver something that works as expected without providing a long
term support version. With this rolling concept I can't see a negative
outcome also for public administrations like Munich or companies like
SUSE supporting our project in a different way. I like "tumbleweed" more
than rolling to be honest but if this concept will be selected we can
try to find a more effective and visual word too.

yes I really like it too :) I tried to think further on the word
Tumbleweed and its representation. I would like to propose Spring which
represent the season (where everything is coming to life or growing),
the source of water but also the resilience.

CLASSIC: can be an idea too but for my taste, classic looks also like
something old, aged and I can see it more close to the distinction we
have for LibreOffice still and LibreOffice fresh instead of a way to
differentiate who is doing what and how.

BASIC: with "basic" I can see the same issues already mentioned with
"PERSONAL" plus the negative connotation that the basic version has less
features or it has something less if compared with the supported
version. The difference I see here is much more than the lack of
professional support.
also agreed on both


Sophie Gautier
GSM: +33683901545
IRC: sophi
Foundation coordinator
The Document Foundation

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
Privacy Policy:


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.