Hi :) No. I do not have a clue about how to start working as a dev in LO or what type of coding is best or how to get involved with Easy Hacks or how soon might be good to move on and where to move on to or what systems they use. Hopefully there is enough external stuff that can be linked to in order to try to keep the guide fairly short and useful as a reference guide.
Someone has said that while devs might not be helpful in initially writing documentation they might become involved if the first published version is sufficiently inaccurate or misleading but close enough to be annoying. It's not an ideal approach but i guess it means don't worry too much about being great. I am wondering if it might be good to start it as a wiki guide a bit like Ubuntu's "Community Documentation"? Regards from Tom :) --- On Wed, 12/10/11, Robert Ryley <[email protected]> wrote: From: Robert Ryley <[email protected]> Subject: Re: [libreoffice-documentation] Documentation for new Devs :) Fw: Re: [steering-discuss] Candidacy for Board: Michael Meeks To: [email protected] Date: Wednesday, 12 October, 2011, 23:09 Tom, I'm in the middle of a move now, but I'll be taking a closer look at the developer docs, to do some re-branding, and hopefully get acquainted with the API enough to help out. Is there anything specific you would like someone to look at? Robert On Mon, Oct 10, 2011 at 6:51 AM, Tom Davies <[email protected]> wrote: > Hi :) > At last we got a sensible answer from one of the candidates for the BoD > elections. > > Non-candidates had been fairly unhelpful and hostile in response to a simple > question turning something that could have been a quick Q&A session into a > flame-war. I think people get a bit over-defensive sometimes. > > Anyway to make things a bit more open i am forwarding to you guys my response > to Michael Meeks along with his statement. > Regards from > Tom :) > > > --- On Mon, 10/10/11, Tom Davies <[email protected]> wrote: > > From: Tom Davies <[email protected]> > Subject: Re: [steering-discuss] Candidacy for Board: Michael Meeks > To: [email protected] > Date: Monday, 10 October, 2011, 11:34 > > Hi :) > Thanks :) I'm not going to be at Paris but thanks for the offer. > > Documentation on how to join in with other teams (including the Docs Team > (following recent upgrades to their infrastructure)) also needs to be done. > > I don't know what UNO is. It seems to be something that depends on > javascript or .Net or something?? Seems a bit strange. Of the links i found > this link made the most sense > http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/FirstSteps/Programming_with_UNO > and even that was a tad confusing imo. Does the limited guidance on how to > add a language or new translation push people into using UNO? > > Oddly we don't get many calls for how to translate or how to add a new > language and when we do people seem satisfied with the links we give them to > specific teams > or to the global translations list. We do need to get decent guides for > those things but we get a lot more people asking about how to join in with > programming and people seldom seem happy with what we can give them. > > It would be good to have a proper LO Guide that reflects LO's direction > instead of the direction under Sun. > > If there are other guides that could be usefully added to the collection that > would be great. Anyone can either edit the page or pass the links to the > documentation list. > > Anyway, thanks hugely for your considerate reply. > Regards from > Tom :) > > > > --- On Mon, 10/10/11, Michael Meeks <[email protected]> wrote: > > From: Michael Meeks <[email protected]> > Subject: Re: [steering-discuss] Candidacy for Board: Michael Meeks > To: > [email protected] > Date: Monday, 10 October, 2011, 10:11 > > Hi Tom, > > On Sat, 2011-10-08 at 18:02 +0100, Tom Davies wrote: >> One of the top priorities for the Documentation Team right now >> is a guide to help people that want to start programming for >> LibreOffice. > > Cool ! :-) and of course, it's something that can be dead useful. > >> There is already a good one for Extensions > > Right - and of course, we'd prefer people to write code that can be > integrated into the core cleanly, and have code sharing between > different implementations (it's easier to hack that up, debug it, and > deploy it too FWIW). > >> At the moment the Docs Team can only point to >> http://wiki.documentfoundation.org/Documentation#Other_Documentation_and_Resources > > I like the collection; it'd be great to excerpt / re-write some more > functionally focused flows for the things we know happen lots: > > "How to add a new language" > "How to add a new translation" > > But of course many things are simply not documented at all; and worse > most of the existing docs are *heavily* UNO focused, which is (IMHO) a > big mistake. > > Anyhow - there were some starter tasks I mentioned to David, when > they're done - lets have a call & brainstorm on what more can be done, > and how best to do it; will you be in Paris to discuss ? > > I suspect there is enough out there to dig out and re-hash in a helpful > way. As an example if we systematically discard anything that talks > about > UNO - and condense what little is left (code structure diagrams / > functional descriptions etc.) I think we might end up with something > quite useful for new core hackers: or at least a nucleus to work from. > > Thanks, > > Michael. > > -- > [email protected] <><, Pseudo Engineer, itinerant idiot > > > -- > Unsubscribe instructions: E-mail to > [email protected] > Problems? > http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ > Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette > List archive: http://listarchives.documentfoundation.org/www/steering-discuss/ > All messages sent to this list will be publicly archived and cannot be deleted > > -- > Unsubscribe instructions: E-mail to [email protected] > 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/documentation/ > All messages sent to this list will be publicly archived and cannot be deleted > > -- Unsubscribe instructions: E-mail to [email protected] 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/documentation/ All messages sent to this list will be publicly archived and cannot be deleted -- Unsubscribe instructions: E-mail to [email protected] 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/documentation/ All messages sent to this list will be publicly archived and cannot be deleted
