Hi :) The devs team has a list of "Easy Hacks". The docs team are working at producing something similar. The marketing team have a list of specific tasks from fairly simple to quite complex&involved. I imagine the design team have something similar but you never know with artists. The website team almost certainly has a list of things they wish they had time for. Translations teams seem to have a list of the chapters with completed, work-in-progress and unclaimed ones clearly identified. Translations and docs teams always appreciate someone stepping in to proof-read. QA has a list of bug-reports that haven't been triaged yet (probably best to treat as multiple choice and avoid getting bogged down in ones you can't handle yet (return to them later)).
Each team has something but it might not be immediately obvious without joining the specific team and asking for their jobs (or whatever) list. Regards from Tom :) >________________________________ > From: Carl Paulsen <carlpaul...@comcast.net> >To: users@global.libreoffice.org >Sent: Monday, 19 November 2012, 13:34 >Subject: Re: [libreoffice-users] Re: OpenOffice to be dumped in Freiburg ? > >Thanks, Regina. I know there are other ways to contribute, but I don't >necessarily know what they are. Templates is one way, but the real issue I >see is going from MSO to LO/OO. We can't control the other end. > >So is there a simple list of SPECIFIC ways users can contribute (templates is >a good example) that is easily found? I've seen some general lists of how to >contribute, but I haven't searched much for more specifics. In any case it >should probably be front and center on the website (again, not the develop, >donate $$, etc. generic list, but more specifics). > >Carl > > >On 11/19/12 8:09 AM, Regina Henschel wrote: >> Hi, >> Carl Paulsen schrieb: >>> In practical use, I would NOT say LO (or OOo) has a "high" file >>> compatibility with MS Office. Virtually every file I receive from MS >>> Office users has some kind of problem (bullet lists almost NEVER convert >>> correctly, at least from MSO to LO). I'm only an occasional Office >>> suite user so I put up with it (plus I'm on a Mac), but I've never been >>> able to convince others to use LO for this reason alone. And I mostly >>> work with non-profits who, for several reasons, should be avid LO users. >>> >>> I also realize MSO, with it's market share, stands only to gain from >>> keeping it's formatting a moving target. With that in mind, I just >>> can't imagine how a project like LO could hope to keep up and make inroads. >>> >>> Wish I could help with making it work better, but I know nothing about >>> contributing to development. >> >> You do not need to be a developer to help. One idea for interoperability I >> heard on LibOCon, is to make templates, that can be converted nicely. So if >> you have access to MSO, then examine, what kind of things are dangerous for >> converting and what kind of things convert without problems. Make a Wiki >> site with your observations and create good templates based on this >> rationale. >> >> Kind regards >> Regina >> >> > >-- For unsubscribe instructions e-mail to: users+h...@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+h...@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
