(Draft) agenda of in-person board meeting 2023-07-08 and 2023-07-09

Find below the, from what I can tell not yet published, draft agenda for the in-person board meeting 2023-07-08 and 2023-07-09
From what I remember, the meeting was attended not by all board members
I don’t have minutes nor did I attend the meeting, so I share what I found in Nextcloud

Saturday Agenda (draft)

Boards procedures and …

  • there are open wishes
  • clear suggestions in [REDACTED: external communication consultant] report
    • focus on advise in second part of the report
    • some input has already been sent to directors-list
  • fiduciary duties & further CC suggestions
    • there is this folder [REDACTED: board-only folder]
    • The folder includes examples of Board Members Agreement and Code of Ethics which also contain elements that help in protecting members of staff from directors
    • and discussion on tdf-internal
  • in order to get to decisions on our meetings in Bucharest, we need to agree on a clear procedure, time-line & steps, allowing input from relevant sides, time for thinking and discussion etc.

TDF’s Manifesto

  • that’s still to be done
  • in order to get to a decision in Bucharest, we need
  • a procedure, time-line & steps,
  • allowing input from relevant sides, time for thinking and discussion etc.
  • what already has been done:
    • [REDACTED: board-only link]

Online

  • LOOL and the message / decision
    • atticization?

Products and Downloads

  • app store pricing
  • app store evidence for [REDACTED: external entity] (take in consideration that companies of the ecosystem operated independently of TDF when developing app store version of their products and helped TDF little or nothing at all to do that)
  • status and plan LibreOffice in the app stores

Board’s marketing & communication

  • next decade manifesto / vision
  • improve board communication
    • minutes
    • community interactions
    • calls
    • members-only board call section?

Misc

  • apply with LibreOffice as digital public good
    • further fund-raising opportunities?
  • legal backlog handling - see Sunday
  • FSF AB seat - postpone?
  • CoC committee and policy
  • minuting of board meetings
    • currently the directors need to put a lot of energy to check drafts
    • find a professional?
  • external moderation
    • discuss the status

Sunday Agenda (draft)

Staff items

  • staff / board policy
  • team interactions

Strategy items

  • source: [REDACTED: board-only link]
    • direct democracy
    • catch up with industry
    • move away from desktop
    • 10% of project budget decided by members
    • incentivize voting by members
    • lobby EU for more LibreOffice use
    • find new markets and users
    • double number of developers
    • be on every students’s computing device
    • be among top 5 EU orgs for FOSS and digisov questions
    • have teaching LibO be on the course canon for EU learning institutions
    • have ODF docs advertized on EU gov pages
    • rework project / toolchain, to improve on-ramp
    • increase contributions from non-EU citizens
    • increase community metrics
    • spend 10% on education
    • be fully interoperable
    • further professionalize the org
    • increase number of in-person community meetings
    • brand and logo refresh
    • marketing to differentiate between product and project
    • increase diversity
    • get 2 additional companies into project
    • become largest FOSS community w/o larger conflicts

Strategic goals as decided in Milano

  • [REDACTED: board-only link]

Review legal backlog

  • check what is still relevant

Surveys

  • MC / membership review
    • [REDACTED: board-only link]
    • update
    • actions

Votes

  • Approve Technical Budgetting procedure
  • 2023 budget finalization

I’ve not read all of this massive text dump - but am interested to correct this un-attributed statement. I remember us investing to do the work to make LibreOffice work at all in the app-sandbox, then ongoing maintenance and bug-fixing while contributing code back, funding some Mac improvements, as well as providing TDF with advice on financials, market-demand-curves, meetings, not to mention donations from the proceeds of our work to help support TDF - and IIRC ultimately offering to help-out with getting TDF’s own replacement app version shipped. Hands on help may not have been needed at that point - fair enough - Cloph is a clever chap :slight_smile: and much of the heavy-lifting was already done & in the codebase at that point. I think that adds up to some very substantial help.