Hi :)
The documentation team needs a LOT more people. At the moment it barely has enough to just work on
the guides (which were extremely well received at Scale btw).
If these other attempts at documentation are done through by individuals through blogs and personal
spaces then when/if those individuals "run out of steam" or if outside life takes over then the
work would be lost or difficult to carry on with - or even difficult to find at all. By joining
the Documentation Team you can use centralised resources such as their ODFAuthors site to make the
work more likely to be continued by others. Other people in the team are often helpful and
encouraging and are experienced at writing for non-technical end-users and can help gain consistent
use of terms and phrases. Joining the team means your work will not get wasted if unforeseen
circumstances (such as suddenly gaining a shed load more clients) conspire to reduce the amount of
time you can spend on the work.
People are encouraged to join in with the work they are currently doing in order to gain some
experience with their process and then perhaps use that experience to get on with their original
plans.
Regards from
Tom :)
________________________________
From: Adam Tauno Williams <awilliam@whitemice.org>
To: users@global.libreoffice.org
Sent: Sunday, 24 February 2013, 19:32
Subject: Re: [libreoffice-users] Re: Looking for PyUno Contributor(s)
On Sun, 2013-02-24 at 16:56 +0100, Wolfgang Keller wrote:
If I'm incorrect, please let me know what is correct - but I'm pretty
sure that someone with some PyUno skills will be needed.
I would guess that those are rare, since PyUNO is at about the best
kept secret of LO(/OO).
+1 +1 +1
I've even attempted to make several runs at it. The documentations is a
*@(^&@*$^&@*# crime. There are silly trivial "Hello World" examples,
and there is the dump of the API. And nothing in between.
If someone implements this as a contribution to the project *PLEASE
PLEASE PLEASE* do a step-by-step BLOG article/series of it. I'll send
them a six-pack; just let me know the URL.
There really seems to be an *AMAZING* amount of power just sitting there
to be used - but it is completely obscured to anyone not aleady familiar
with UNO's syntax and vocabulary.
Especially with the introduction of CMIS support it really seems a great
time to facilitate real automation via LibreOffice.
--
Adam Tauno Williams GPG D95ED383
Systems Administrator, Python Developer, LPI / NCLA
--
For unsubscribe instructions e-mail to: users+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/users/
All messages sent to this list will be publicly archived and cannot be deleted
--
For unsubscribe instructions e-mail to: users+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/users/
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.