Le 2010-10-27 06:21, Sebastian Spaeth a écrit :
On Tue, 26 Oct 2010 19:52:20 +0200, leif<leiflodahl@gmail.com> wrote:
Many large installations are very irritated about the registration
screen. The DisableFirstStartWisard solves some of the problem *but* its
version dependant.
IMHO we should remove the *registration* completely. We are not after
marketing addresses and I don't see a benefit in LibO requiring (or even
inviting) users to register.
Sebastian
From a marketing point of view, not knowing how or from where people
are using LibO is working in the dark. LibO is such an essential piece
of software, we need to know at the very least where it is being used.
With these statistics, we would be better equipped to target sectors
where there is little use or sectors where we could improve the suite to
better serve groups.
In my view, the registrations process for LibO is quite an important tool.
It should and should always be left up to the individual's discretion to
register.
I also agree, we should work on a better way to implement it in large
installations.
Marc
--
Unsubscribe instructions: Email to discuss+help@documentfoundation.org
Posting guidelines: http://netmeister.org/news/learn2quote.html
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived ***
Context
Re: [tdf-discuss] Better defaults · Valter Mura
Re: [tdf-discuss] Better defaults · AG
Re: [tdf-discuss] Better defaults · leif
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.