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

Hi Fernand,

Fernand Vanrie wrote (23-06-11 16:08)
I hope Michael and other TDF-members are reading this.

As we love to have a Email body when sending emails with the API, our
company is willing to fund this kind of repair work.

Repair or enhancement...
(Side note on the subject: I can imagine that somehow the Python component could be useful.)

The interested makes a Enhancement request
The TDF put a price on it
The interested pays TDF in advance
After TDF and interested is satisfied TDF pays the Developer or keeps
the money for other projects
Simple ?

Sounds reasonable.
However ... TDF does not employ developers.
Developers are employees of sponsoring companies, or students, or (other) volunteers, or self employed...

So either your company makes a deal with one of the supporting companies for the work, or find another developer to do the work.

Of course it makes most sense if the developer that picks up the task has experience with LibreOffice/OpenOffice.

I have hardly any experience in other open source projects, but I can imagine that setting up a page with bounty-projects, is a reasonable approach to broadcast both your and other wishes/possibilities.

What do you think?


 - Cor

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.