On Thu, Nov 17, 2011 at 3:37 AM, Dan Lewis <email@example.com> wrote:
I agree with you. I just did not know if we were going to change
the Alfresco structure of the documentation.
We can change either. But maybe more likely the documentation at this
time. However, if docs contributors decided another way of working was
better, we could adapt the working methods instead.
I want to think about it some and perhaps come up with a suggestion
for the documentation to match what we are now doing. So, if I do this,
should I post my suggestions to this mailing list or edit the
documentation by inserting them with my name?
IMHO, the most-constructive thing would be to post questions here for
public discussion, and then be ready to edit the documentation when a
conclusion had been arrived at.
I think you will find that I will have quite a few questions so
that I can understand what is going on. Once in a while I might need
someone to tell me to "read the manual" which is fine as long as they
point me to the document that has the information that I need.
No problem for questions, please do ask. Then, if they're likely to
come up regularly, it would be great if we could make sure they're
answered in the documentation.
Unsubscribe instructions: E-mail to firstname.lastname@example.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/documentation/
All messages sent to this list will be publicly archived and cannot be deleted
Impressum (Legal Info)
: 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