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


Hi :)
Ahh, i meant the docs team are good at supporting and helping people that want to do documentation 
tasks.  They are not precious about it or offended if people go off and do their own thing.  

Btw those links look good.  Please can you add the links to the 3rd party wiki?
https://wiki.documentfoundation.org/Documentation/Other_Documentation_and_Resources

I'm not completely happy with the name in that url.  I would prefer something like one of these
https://wiki.documentfoundation.org/Documentation/3rdPartyGuides
https://wiki.documentfoundation.org/Documentation/UnofficialGuides
or make it a sub-page off the Publications page so something like
https://wiki.documentfoundation.org/Documentation/Publications/Unofficial
https://wiki.documentfoundation.org/Documentation/Publications/ThirdParty

Other suggestions or which would you prefer?  I tried asking on the Docs Team's list but got 
distracted and never got a clear answer.  Once i have a good name i can create an auto-redirect 
from the current page (which got named in a hurry without really thinking about it)

Regards from
Tom :)  





________________________________
From: Adam Tauno Williams <awilliam@whitemice.org>
To: "users@global.libreoffice.org" <users@global.libreoffice.org> 
Sent: Sunday, 24 February 2013, 22:29
Subject: Re: [libreoffice-users] Re: Looking for PyUno Contributor(s)

On Sun, 2013-02-24 at 19:56 +0000, Tom Davies wrote:
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. 

I agree completely - but it would help to get people off-the-ground and
using the technology.  I cannot document a technology that I can't [very
easily] get up and rolling with.  I'm just saying not to make the
perfect the enemy of the good [which happens terribly often in Open
Source land].

Aside:  PUNO <http://www.wstech2.net/index.php?do=0a,01,05> which is an
UNO connector for PUNO is a nice bit of code; we use that to generate
documents on our website/webservice.

Various UNO getting started guides:

<http://openofficejava.blogspot.com/2009/05/openofficeorg-api.html>

<http://drbacchus.com/openoffice-python-uno-interface>

<http://tirania.org/blog/archive/2008/Jun-12.html>

<http://www.devshed.com/c/a/Python/Python-and-OpenOfficeorg/>


-- 
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.