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

Hi *,

with the lively discussion ensuing here, it is perhaps worth sharing
my position ahead of the board call tomorrow:

Paolo Vecchi wrote:
Enable TDF to contribute more code to LibreOffice with in-house developers
to address our donors specific needs

I think it is worth considering, whether TDF should employ dedicated
developers. I'm not in general against it.

It is putting the cart in front of the horse though, to start with:

* we want TDF to contribute more code to LibreOffice

and then follow with

* therefore we must employ two developers

I believe it is more productive to start thinking about what we want
to achieve, in order to fulfill our mission. It is therefore
encouraging to read some good thoughts about that (RTL/CTL, a11y, and
other under-developed areas with little ecosystem contributions).

The board can then ponder what is the best way to achieve those goals,
relative to other demands. It is possible, but by no means certain,
that actually hiring specialised staff is indeed the most economic way
forward (e.g. for an area like a11y).

It should be noted though, also to manage expectations, that mastering
even a small area in LibreOffice takes many years to learn. So hiring
for a role has long-term implications then on which kind of tasks,
features or bugfixes can be done in-house.


-- Thorsten

Attachment: signature.asc
Description: PGP signature


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.