On Thu, Feb 3, 2011 at 12:44 PM, Ken Springer <snowshed@dishmail.net> wrote:
:
It's user support where things fall flat on it's face. I only have one
person in my family and friends who would even have a clue as to how to
utilize a mailing list. It's way too cumbersome and clunky for the people I
know. Even I had trouble figuring this one out! LOL
Thank you for that long and thorough description of what is wrong with
(most) help features around. While I have been around for a long time
and am fairly good at finding what I don't already know how to do, the
help files and forums are not intuitively obvious to the average
computer user (what I used to refer to as idiots, but I try to avoid
that word in this regard) and even sometimes to advanced old-timers
like me.
That said, I encourage people to use FOSS because it is generally much
higher quality than that paid junk and *I will shepherd them
personally through any support or help issues they find, and I am
happy to do so. Depriving others of access to FOSS does them a
disservice, whereas helping them learn about how to find what they
need to know elevates them beyond the base level beginner and sets
them on the road to competence.
You keep up your good work and I'll do mine, too. Onward, LibreOffice!
--
Unsubscribe instructions: E-mail to users+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/users/
*** All posts to this list are publicly archived for eternity ***
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.