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


You are right.

There's a big difference between "average joe" users and power users.

Despite power users often contribute the projects with feedback and
even code, most users have no clue and just worry about having the
application ready to use. The more easy is to have the application up
to date and constantly improved to the mainstream needs, the better
for them.

So auto-updating is a feature no needed by Linux users or power users,
but these kind of average users. Google Chrome and others got many
advantages about that, having the features  and bugfixes constantly
updated by those "lusers" without knowing it.

So an easy to disable auto-updating feature would benefit them,
LibreOffice would be known as being better after time without needing
to be manually updated. Most computers run very ancient software
versions because they don't care at all about maintenance, mainly
because lack of proper computer education these days (educative
systems are mostly very lacking in lots of areas).

About having repeating stuff in bugtracker is a very negative thing,
it also means a total lack of maintenance of the bugtracker. That's
unfortunately a too much common mistake in free and propietary
projects that must be totally avoided, never have the bugtracker
filled with lots of items (even less if being repeated ones with
different wording, that should be prohibited)!


Regards.


On Fri, Dec 28, 2012 at 12:26 PM, Florian Monfort
<florian.monfort@gmail.com> wrote:
Even if it's Firefox, upgrading itself?

And I don't think you can apply that reasoning to the average user, because
the average user won't notice ;)


On Fri, Dec 28, 2012 at 12:19 PM, Jean Weber <jeanweber@gmail.com> wrote:

I assume that a "silent update" needs to download itself. If anything
attempts to download to my computer without my permission, I am not
happy when I find out about it, which I will. My usual reaction is to
delete the offending software and not use it again.

--Jean

On Fri, Dec 28, 2012 at 9:02 PM, Florian Monfort
<florian.monfort@gmail.com> wrote:
---------- Forwarded message ----------
From: Florian Monfort <florian.monfort@gmail.com>
Date: Fri, Dec 28, 2012 at 12:02 PM
Subject: Re: [libreoffice-marketing] Silent Updates
To: Jean Weber <jeanweber@gmail.com>


Hi Jean,

Not sure I understand what you mean. Silent updates are usually...
Silent.
How can people tell whether they like it or not?

Companies are a different topic, and OF COURSE you would be able to turn
it
off. Not even debatable :).


On Thu, Dec 27, 2012 at 9:47 PM, Jean Weber <jeanweber@gmail.com> wrote:

On Thu, Dec 27, 2012 at 8:34 PM, Florian Monfort
<florian.monfort@gmail.com> wrote:
Hi,

I've seen a lot of browsers recently moving towards silent updates.

I was wondering whether this could be a relevant approach for
LibreOffice
or not.

Indeed I've seen many people complaining about LibreOffice features,
UI
etc. While using LibreOffice 3.4... Of course the first advice is
"just
upgrade" but for people I doesn't seem like such a good think to do,
just
like it somewhat scares them. I'm pretty sure that happens with at
least
half of our userbase.

What do you guys think? I think this would improve the overall
quality of
our userbase making sure that almost everyone has the very last stable
version, with all the fixes and improvements it brings.

Plus, for once we wouldn't be copying MS Office...

--
*Monfort Florian*


If it's an option the user can choose, that can be a good move. If
it's not an option, it would be a VERY BAD move. Many people hate
silent updates, and many companies will not allow them. I'll accept
the option being the default, as long as it's easy to turn off.

--Jean




--
*Monfort Florian*
BM2 Student at France Business School
Marketing Apprentice at Red Hat
Marketing Team Member at The Document Foundation
florian.monfort@gmail.com
Mobile : +33 6 58 97 15 61



--
*Monfort Florian*
BM2 Student at France Business School
Marketing Apprentice at Red Hat
Marketing Team Member at The Document Foundation
florian.monfort@gmail.com
Mobile : +33 6 58 97 15 61

--
Unsubscribe instructions: E-mail to
marketing+help@global.libreoffice.org
Problems?
http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/marketing/
All messages sent to this list will be publicly archived and cannot be
deleted





--
*Monfort Florian*
BM2 Student at France Business School
Marketing Apprentice at Red Hat
Marketing Team Member at The Document Foundation
florian.monfort@gmail.com
Mobile : +33 6 58 97 15 61

--
Unsubscribe instructions: E-mail to marketing+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/marketing/
All messages sent to this list will be publicly archived and cannot be deleted


-- 
Unsubscribe instructions: E-mail to marketing+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/marketing/
All messages sent to this list will be publicly archived and cannot be deleted

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.