Hello everyone,
This is a short reminder about our policy concerning formal roles and
project team leads.
We usually refrain from making any sort of statement on whether this or
that team needs a project lead or doesn't need one. We believe that in some
cases a team will need a lead and in some others, it won't. However any
lead elected by the team must understand that it is only an informal role
that has been appointed by a social convention, and one that is easily
undone.
The Document Foundation and the LibreOffice project acknowledges only
project contributors or TDF members; other, more formal roles are described
in our bylaws. Similarly, a project team lead or a team cannot engage in or
commit to working on itstelf with commercial entities for purposes specific
to the team's work or the project team lead. In the unlikely event where
such a question were to be seriously asked this needs to be decided solely
by the BoD.
Best regards,
Charles-H. Schulz,
Member of the Board of Directors,
The Document Foundation.
--
Unsubscribe instructions: E-mail to board-discuss+help@documentfoundation.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/board-discuss/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- [board-discuss] On project leads and formal roles · Charles-H. Schulz
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.