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

I wonder, though, how would the fixed bug integrate into the code
maintained by the LibO crew.
It is open to anyone, and anyone is welcome to contribute so that
wouldn't be an issue. Interesting discussion happening here, please keep
it alive and pass the word :-D

I haven't seen a message in this thread from someone with an libreoffice
e-mail address...  is this at all 'sanctioned' by the project?   Someone
in the project on-board?  Someone credible is vouching that  is legit and on-the-level?

I am a contributor for LibreOffice both in development and QA. I wouldn't
say it's "sanctioned" (ie. we're not saying definitely use this service)
but it has been used successfully at least once or twice before. This being
said, it's still no guarantee that it'll get your enhancement done
immediately but it's okay to offer funding to have your bug fixed. It's
just up to developers to decide if the payment is a) necessary for them and
b) enough that they'll do it :)

We are currently working on getting these details on the website along with
are certified developer list with their fee schedules. Not sure when this
will be done but it's a work in progress

Best Regards,

*Joel Madero*
LibreOffice QA Volunteer

For unsubscribe instructions e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.