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



On 08/10/2021 10:37, Emiliano Vavassori wrote:
Il 06/10/21 14:46, Simon Phipps ha scritto:
I will note none of the text has been supplied to or discussed by the legal committee (where I am a volunteer).

I really appreciate your activity in the project and the Foundation. I will welcome very thankfully your involvement (and by extension, of any other volunteer) for the future versions of a CoI Policy.

Just to re-iterate this: I personally find Simon's work on the legal committee invaluable. Simon regularly provides the benefit of his very considerable experience to the great benefit of TDF, in a most timely and helpful way in that context.

I believe it would be extremely useful to include him into the timely review of this policy given his experience across many FLOSS projects.

        Thanks Simon,

                Michael.

--
michael.meeks@collabora.com <><, GM Collabora Productivity
Hangout: mejmeeks@gmail.com, Skype: mmeeks
(M) +44 7795 666 147 - timezone usually UK / Europe

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