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

[board-discuss] Personal Edition label and define is wrong.


https://nextcloud.documentfoundation.org/s/jzryGw7XDkJadmo
Going through the above slide deck I see a clear problem.

Page 32.
Tag: “volunteers supported, not suggested for production environments or strategic documents”

This statement is not 100 percent true with the current fresh and
stable.   Let's say I am in a production environment I need to open
excel spreadsheet 16,384 columns first version of Libreoffice that I
know of that is going to be able to-do that is the current 7.0 coming
out that you are attempting to label Personal.   Yes a document like
that could be a strategic document.    This has not been the first
time a new feature has appeared in the fresh branch that without it is
production breaking.

The use cases for current fresh does not meet this definition "not
suggested for production environments or strategic documents" because
the existing fresh has been suggested to be used in production
environments and on strategic documents in cases of document
compatibility issues that need new features to fix.

Page 32.
you are using the community supported version of LibreOffice, focused on needs of individual users

Again all the new features that appear in the fresh version/personal
edition are not 100 percent targeted at the needs of the individual
instead has been the new features that have not been well tested of
the enterprise needs as well like 16384 columns spreadsheet in version
7.0 your normal individual outside enterprise is unlikely to ever need
that feature.    So to test these new features properly we need
enterprise users to be using what you are attempting to rebrand
Personal Edition in a limited way.

Well will  all new enterprise need features now appear in the
"LibreOffice Enterprise" first and then "LibreOffice Enterprise" users
have to beta test them before they come to Personal Edition?   I guess
not as this will make production deployments more unstable.   I guess
everyone will want to keep the status quo where the fresh or what is
being rebranded here to Personal Edition to be worded as usable by
Enterprise users needing new features now.

Personal Edition itself clearly is stating not for Enterprise.
Fresh changing to Community Edition is better here as because
Community Edition can be enterprise and individual users.

I have had a lot of cases where I have been able to get Libreoffice in
next to Microsoft Office at first by it being free and licensed for
anyone to use.

Page 32
LibreOffice Enterprise: only from ecosystem members
Only from ecosystem members this means if this equals must pay someone
to get this version lot of my deployments in different businesses of
Libreoffice would never have happened.    Yes I can see those wanting
to make the "LibreOffice Enterprise" wanting as many paying customers
as possible.

Also think like openlp in churches using libreoffice to display
powerpoint presentations.   There are a lot of different use cases
like this of Libreoffice that are not individual and not really
enterprise either that would fall under title of Community that don't
fall under the title of Personal.

How would I fix this.
Personal Edition comes Community Edition.
Tag: “volunteers supported, not suggested for production environments or strategic documents
changes to 'Tag: “volunteers supported,   Recommend for Individual users."
Ok that's kind of the best I can do.    Because the existing not
suggested there are cases where it is going to be
suggested/recommended/advised for the very things the Tag says not
suggested this will lead to arguments between support people and end
users that we do not need.   One thing I can say clearly there is a
word you cannot use in this tag is the word 'not"  the license of
Libreoffice is for everyone and anything suggesting what Libreoffice
is really should not suggest otherwise as soon as you use the word not
you are most likely screwing up.   Everything needs to be written in
the positive/additive not the subtractive(not and so on is the
subtractive). If what is in the tag cannot be written in the positive
you have a problem.   Of course something the positive/additive text
does not list as supported does not mean a person cannot use it that
way also does not mandate you support them either because they are
using a non documented usage case basically the not stuff can be
implied by careful positive/additive text.   Yes the "Recommend for
Individual users" I put there suggests not suitable for production
environments or strategic documents without in fact stating it and
also not locking out that usage case completely.   This is the art of
the good marketing weasel(sorry Dilbert comic reference):  Write stuff
that suggests stuff never directly tell user/consumer how they must
use it.

you are using the community supported version of LibreOffice, focused on the needs of community 
users.
Swapping individual to community here allows the Community Version to
remain the testbed for new enterprise features.

There are a lot of projects that do Community and Enterprise editions
using those names make sense.   Personal editions with open source
software almost never make any sense and normally end up writing
something in conflict with license or their community.

Peter Dolding

--
To unsubscribe e-mail to: board-discuss+unsubscribe@documentfoundation.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.documentfoundation.org/www/board-discuss/
Privacy Policy: https://www.documentfoundation.org/privacy

Context


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.