TYPO3 Association Board Meeting Protocol (14 October 2026)

Project Ambassador Mathias Bolt Lesniak informed that collaboration on conversation-based, AI-aided event reports has successfully enhanced report quality and established helpful content guidelines for the community.

Insights from a recent DrupalCon attendance highlighted that the project shares similar public perception challenges with other open-source communities, where product quality surpasses external visibility. A key takeaway is the importance of communicating directly with end users rather than focusing solely on developers.

Additionally, the partnership agreement with the European Open Source Association has been finalized and signed, with official activities slated to begin in November. This collaboration is expected to open up new avenues for engagement in European open-source policy.

The board reviewed the ongoing status and handover tasks for the Governance Working Group and unit kickoff preparations. Action items include inviting suggested participants to the upcoming kickoff events via designated communication channels. Planning documents and participant lists are actively being organized to support the establishment of the new units.

Association Members are currently being asked to vote on a new Governance Structure. Current team leads and members have previously been asked to suggest initial members for the newly-to-be-formed TYPO3 Units.

Preparations for the upcoming Extraordinary General Assembly (EGA) are progressing with several immediate action items assigned. Informational pages regarding proposed bylaw changes are scheduled for publication on typo3.org alongside member invitations. Registration is being set up via the official Extraordinary General Assembly registration form, and the voting infrastructure is being prepared for launch. Additionally, the English version of the proposed bylaws is being updated to clearly highlight all modifications.

The compliance officer’s update covered ongoing work concerning Cyber Resilience Act (CRA) obligations in coordination with the security team. Insights and feedback from these discussions are being integrated into compliance documentation, following a recent presentation at a prominent PHP forum. Upcoming engagements include code and compliance events in Brussels focusing on the CRA and AI Act, as well as policy summits and meetup participation early next year. Plans are also underway to invite the PHP Foundation to join the Open Website Alliance.