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

Dear Community,

find below the agenda for our

-> TDF board meeting with a public part, and followed by a private part -> on Friday, September 11th at 1300 Berlin time

For time zone conversion, see e.g.

-> at

We meet on jitsi, and please, if possible use Chrome browser and do not use video and until not speaking up please mute.


Public Part

1. Q&A: Answering Questions from the community (All, max. 10 min)
Rationale: Provide an opportunity for the community to ask questions to the board and about TDF.

2. Inform & Discuss: Open letter of the membership committee to the board (Board members, all 10 min) Rationale: Feedback and further steps for mentioned issues with old and/or new MC, especially handling of minutes of board meetings

3. Discuss & Organize: Status & further steps in the subgroups with: a) marketing plan b) tender streamlining c)app store offering TDF d) TM licensing (All 10 min)
   Rationale: Discuss and identify the next steps
   Redmine ticket(s):

 a) LibreOffice 7.0/7.1 marketing plan
Status: Paolo, Franklin, Michael, Thorsten, Mike, Italo continue working on this, Follow-up when everyone is back from holidays

 b) KG22.01 - Streamline Tendering Process in 24 months
Status: Nicolas, Lothar and Florian had first call. Documents and process description in the works. Next call September 10.

    KG22.01.1 - Two more tenders signed in 6 months
Status: ODF 1.3 delta is written, can be published when approval is given, Thorsten following-up with Regina atm

 c) form sub-group to work out and publish business entity proposals
Status: Draft proposal for Luxemburg entity published - Thorsten, Michael, Nicolas, Paolo, Lothar: due to holidays a part of the subgroup did coordinate, Lothar will update his criteria list/problem statement with feedback, Paolo to follow-up with ministry for clarification of details

d) from subgroup tp work out proposal for handling outrunning TM licenses End of September

4. Inform & Discuss: Status of redmine tickets of last board meetings (Lothar, Stephan/Florian, All 5 min) Rationale: Clarifying what is pending, questions to reports in redmine tickets, and what todo, who is caring, until when, it is not the intention to speak about all, but the important or urgent ones

   Just to be discussed if any news on:

   Membership Committee election (Florian)
   Status: tbd

   coordination of LibOCon internal meetings (Sophie)
   Status: tbd

Agenda items of Private Part

5. Inform & Discuss: Pending questions wrt. the license inquiry of an Italian Company about LibreOffice online (Florian, all 10min)
   Reason why in private: confidential information about trademark inquiry
Rationale: clarify pending questions/trademark grants, evaluation and further steps

6. Inform & Discuss: wealth management for foundation capital stock, evaluating the two proposals, further steps (Lothar, board members 5min) Reason why in private: confidential information about finance decision making
   Redmine ticket: do we need one?
Rational: evaluation and further steps, do we need a presentation from both banks in a board meeting?

Florian Effenberger, Executive Director (Geschäftsführer)
Tel: +49 30 5557992-50 | Mail:
The Document Foundation, Kurfürstendamm 188, 10707 Berlin, DE
Gemeinnützige rechtsfähige Stiftung des bürgerlichen Rechts
Legal details:

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
Privacy Policy:


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.