TYPO3 Association Board Meeting Protocol (22 July 2026)

The board voted unanimously in favor of excluding six members who had been failing to pay their TYPO3 Association membership fees for several months as of the meeting date, following article 8 of the Association By-Laws.

This action followed a discussion regarding the ongoing management of non-paying members and the status of several overdue invoices. This item was classified as confidential due to the sensitive nature of member financial standing and account status.

The board discussed a case involving a member's repeated and continuous violation of the association's trademark usage policy. The Board voted unanimously to initiate a formal exclusion process following article 8 of the Association By-Laws, while deciding against immediate litigation.

A roadmap for this process was outlined, which includes sending a registered letter, giving the member the opportunity to formally object and potentially addressing the matter at the General Assembly if no response is received. This item was classified as confidential to protect member privacy during the disciplinary process.

The board reviewed a proposal to establish an official committee dedicated to enterprise customers. Discussion on the proposal will happen asynchronously until the next board meeting.

The proposal aims to create a structured channel for large organizations running TYPO3 to provide feedback on roadmap and strategy, with a requested budget for a 2026 sprint.

The Association Secretary, Martin Helmich, provided an update on the governance workflow for policy changes, which utilizes a Git repository and pull requests to enforce rules automatically based on the type of change.

The board confirmed the workflow is active and is currently being used for the AI code policy, noting the transparency it provides. Future improvements will focus on versioning, change logs, and establishing consistent documentation standards

Details on the governance workflow can be found in the TYPO3 Policy Repository.

The working group is drafting rules for a Unit structure and a Unit Coordination Panel, with a proposed structure for units being represented on the Association Board with two seats.

The group aims to present these drafts to the Board and the Team Leaders on Monday 27 July 2026, and to the community as a whole in time for the TYPO3 Developer Days in August. Further discussion is planned to refine the structure.

The board addressed a discrepancy in the membership system regarding a status downgrade that had not been processed correctly. Responsibilities were clarified, reaffirming that membership and dunning-related requests should be directed to the Treasurer.

The Compliance Officer, Rachel Foucard provided an update on ongoing efforts, including the development of a service description with an external ombudsperson provider and plans for a remote meeting to share these updates with the community.

Additionally, the Association is actively collaborating with the Security Team to ensure compliance with the Cyber Resilience Act by the 11 September deadline and has joined the Open Regulatory Compliance Working Groups, specifically co-leading a group focused on the AI Act.

The review of outcome agreements for various board members was scheduled for asynchronous completion. This follows up on prior discussions regarding 2026 performance goals.