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


Hi Simon,

On 07/06/2022 21:40, Simon Phipps wrote:
Kendy made a merged version and shared it with us all...

No, once again he took my document and copy/pasted bits of Michael Meeks proposal on it to completely change the logic of the proposal.

That proposal doesn't really fit with the budget planned, senior developers mostly focused on mentoring are very difficult to find and very expensive, and anyone with basic HR skills would never let employees be managed by a committee in which third party companies have can have so much influence as seen in recent minutes.


It's really a waste of time to cherry-pick and update a legacy document instead of the one multiple people have been working on.

The "legacy document" has actual contributions from many people of the community and TDf's team, the document on which Kendy pasted some text has only contributions from Michael Meeks and you (BTW please remove your only contribution as it names a potential supplier).

Ciao

Paolo


--
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


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.