Paolo Vecchi wrote on 02/06/2022 22:59:
thanks for your extensive explanation which I really appreciate as I
appreciate your contributions both during your working hours and as a
We surely are all working with passion to reach the same goal and we
have specialisations that allow us to view things from different but
I know it is difficult to follow long threads where I provided further
You need help? :)
clarifications about my proposal but what you are saying has already
been taken in consideration.
IMO only partly. It is useful explanation to set realistic expectations.
Young and passionate developers with the will to learn and adapt will
not replace the tenders, they will start with focusing on areas that
haven't been covered by others as much as we wished.
It is indeed an important outcome of the discussion that there are ways
to complement, and not to compete with the commercial ecosystem.
Finding senior C++ or experienced LibreOffice developers willing to
mentor is very difficult and/or very expensive as they already have a
good and very well paid position so even if they have a huge passion for
LibreOffice and our community is unlikely we'll be able to match what
some large corporations can offer.
As from my proposal: "The developers will not need to have a narrow
specialisation in the proposed areas but a good understanding of them,
willingness to learn and to adapt will be necessary characteristics of
Their general role will be to fix bugs and features in full, fixing bugs
that are blockers for community contributors and to help evaluating
which complex tasks should be tackled by external specialists."
Thanks to the mentors that we already have in our team, if they have the
passion and the right attitude, they will grow to become excellent
developers and if they wish even join the ranks of mentors in the long
I love your optimism (well, not always), but as you can read in Lászlo's
mail: there's huge uncertainty.
run. Not all developers want to become mentors or do presentation in
public, some just prefer to focus on the development side and we should
enable our team to express their best skills the way they are most
That is true. However more mentoring power is needed to. So if we can
combine the two, it's better I would say.
There are surely risks in doing that but I believe there are even bigger
risks in not doing it. The biggest risk that we have in doing it is that
we invest in forming developers that then might go back on the market
You are thinking about a contract that forbids people to switch? ;)
and anyway contribute. That's one of our goals anyway. If we get it
right we'll have developers that start working on things that other
volunteers may want to take on again as they see that things are moving
in the right direction.
Let me not take that too negative, but I assume developers are driven by
the wish to make cool stuff. And there are enough opportunities for that
in the source/product.
What is clear is that the process I started with my proposal allowed to
bring to light areas that did not receive enough attention and now
commercial contributors, volunteers and in-house developers will start
working together to fix those areas.
IMO there is clearly room for that. See my mail from 23:17 CET
I'm sure there will be a lot of fun to be had for everyone ;-)
Could well be - let's hope it works out fine.
Cor Nouws, member Board of Directors
The Document Foundation, Kurfürstendamm 188, 10707 Berlin
Gemeinnützige rechtsfähige Stiftung des bürgerlichen Rechts
Legal details: http://www.documentfoundation.org/imprint
GPD key ID: 0xB13480A6 - 591A 30A7 36A0 CE3C 3D28 A038 E49D 7365 B134 80A6
mobile : +31 (0)6 25 20 7001
skype : cornouws
blog : cor4office-nl.blogspot.com
jabber : firstname.lastname@example.org
To unsubscribe e-mail to: email@example.com
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.documentfoundation.org/www/board-discuss/
Re: [board-discuss] Merged proposal for in-house developers at TDF · laszlo . nemeth
Re: [board-discuss] Merged proposal for in-house developers at TDF · Ilmari Lauhakangas
Re: [board-discuss] Merged proposal for in-house developers at TDF · Cor Nouws
- Re: [board-discuss] Merged proposal for in-house developers at TDF (continued)
Impressum (Legal Info)
: 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