Hi 
I am sorry about both those 2 previous emails.
There is some (limited) documentation at
http://www.libreoffice.org/get-help/documentation/
or
http://wiki.documentfoundation.org/Documentation
The documentation team would greatly appreciate any help and they are a very
helpful team. It's a great way to learn a lot and to learn it fast.
The documentation is mostly already written but needs a substiantial re-working
from the old OpenOffice guides before it can be put on the website i just gave a
link to. Partly this is due to extra functionality that has been developed by
LibreOffice devs but also the screen-shots need updating and some that was
work-in-progress anyway. The first release has only been completed for Writer
and Calc and the Starter Guide. Base is the one that needs the most work as a
lot of it needs to be pulled together from scratch or scattered blogs and bits
of training programs. People are actively working on Draw, Impress and i think
Math so more guides should appear over the next few weeks.
Lulu are publishing proper books that can be bought
http://stores.lulu.com/opendocument
with a good percentage of the profit going to TDF.
The wiki is a good place to hunt for things that are works-in-progress from the
various different teams
http://wiki.documentfoundation.org/Main_Page
I couldn't find the FAQ page because there seemed to be different ones for each
different app (Writer, Calc, Impress etc) and in a lot of different languages.
I think the release notes for whichever version you are using might be more
useful because each release seems to cure more issues and has more
functionality. Development is fast-paced even in the stable 3.3.x branch.
Similar questions do arise from new people all the time and that is fine.
Different people have different tehnical backgrounds but may be noobs at certain
other areas so it's not always easy to guess whether someone might be insulted
by a non-technical answer or feel hopelessly overwhelmed by one that is too
technical. Usually the best way is to keep asking questions and perhaps give an
indication of your own background.
Yday in a different forum in a question about getting a printer to work the
person had been a web-designer for 20 years but had apparently never needed to
trouble-shoot a printer! Asking them to "ping the printer" was the nudge they
needed and they were then able to 'guess' the new ip-address for the new printer
and their Network Admin was able to take that and fix the Dhcp server to
re-issue the old ip-address to the new printer. Errr and an early stage had
been someone hadn't plugged the network cable in! So the early answer of "check
the leads" helped! None of them could solve the entire problem on their own but
together they got it done with just a gentle couple of nudges that a different
bunch of people might not have understood and would have had to solve
differently.
Giving the same advice to different people time-after-time is not a problem. As
you pointed out Faqs and Documentation can often help and need to be updated
even after they are done first time. Copy&paste can also help but usually
questions introduce new slants or bring in different side-issues.
The person from earlier needs to take the advice given earlier in other threads
where that person has asked the same question; of talking to the devs mailing
list, or post a bug-report or check to see if they still have a problem after
using the work-arounds. If they had asked the question under a different name
or if a different person had asked the question then i would have given a
shorter, and more polite, possibly even friendly answer combining some of those
ways of moving forwards.
Regards from
Tom 