Hi Andras,
Andreas Mantke wrote on 08/02/2022 18:58:
The best person that can teach you how to fish is an experienced
fisherman.
My example would be fruit grower and fruit picker (after all, the apple
came before the fisherman ;) ) but apart from that:
but it wouldn't improve the situation, if - like today - the experienced
fisherman / fishermen take every new talented fisher immediately from
the free software developer (volunteer) market.
Could be. After all it is one of the ideas behind for example GSoC.
On the other hand, in case it works out like that, it is good news on
two fronts: apparently the commercial ecosystem party has enough income
to hire someone extra; and also there still will be budget for us to
hire mentors.
We also know that developers from commercial ecosystem parties are
involved in getting mentors up to speed. So the whole picture does not
have to look that bad, I think.
So spending that are intended to further grow the possibility of
(relative new) developers to contribute (by mentoring, tooling, events),
are a strong impulse to grow that side of the developer community and
enabling more working people to help with code they think is useful.
Thus there is now chance for a divers market with a lot of small and
local businesses around the LibreOffice project. Thus the (business)
I remember we discussed possibilities in the past, that would enable
relative independent new developers to get funded for work on
LibreOffice. I think that is a good idea to grow the commercial ecosystem.
user of LibreOffice will not get the opportunity to choose between
different service provider.
Compared to various other open source projects, TDF/LibreOffice isn't
doing that bad.
On the other hand, we can't blame projects for how they work as long as
people are free to study, change, share, fork, ..
If this situation will not change immediately the LibreOffice
certification program will not give a competitive edge.
I love TDF for its work: being the place where all stakeholders meet and
try to bring the best in the shared projects.
Then with my experience in a broad variety of commercial, volunteer and
public entities, I'm far from convinced that it leads to anything good
when a foundation tries to bend the forces that drive a commercial market.
Cheers,
Cor
--
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 : cor4office@jabber.org
--
To unsubscribe e-mail to: board-discuss+unsubscribe@documentfoundation.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.documentfoundation.org/www/board-discuss/
Privacy Policy: https://www.documentfoundation.org/privacy
Context
Re: [board-discuss] Enable TDF to contribute more code to LibreOffice with in-house developers to address our donors specific needs · Cor Nouws
Re: [board-discuss] Enable TDF to contribute more code to LibreOffice with in-house developers to address our donors specific needs · Heiko Tietze
[board-discuss] Re: Enable TDF to contribute more code to LibreOffice with in-house developers to address our donors specific needs · sophi
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.