Board Decision: Dutch Committee 

Start of voting

24 November 2025

Voting deadline

8 December 2025

Decision owner

Olivier Dobberkau

Decision status

✅ Accepted, with 5 yes and 2 no

Attendance and voting 

Board Member Attendance Vote
Olivier Dobberkau Asynchronous ✅ Yes
Stefan Busemann Asynchronous ❌ No
Boris Hinzer Asynchronous ✅ Yes
Rachel Foucard Asynchronous ✅ Yes
Martin Helmich Asynchronous ❌ No
Jana Höffner Asynchronous ✅ Yes
Thomas Maroschik Asynchronous ✅ Yes

Decision description 

Facts/Problem 

The Dutch TYPO3 Committee proposes a comprehensive plan to increase TYPO3's visibility and market share in the Netherlands. This initiative aims to revitalize TYPO3's position in the Dutch market, which currently holds a 0.2% share compared to the German market's 160,000 instances of TYPO3. The plan addresses current market challenges, including the dominance of WordPress and Drupal, as well as the limited TYPO3 agency ecosystem in the Netherlands.

Objective 

The objective of this decision is to formally approve and support the action plan for the Dutch TYPO3 Committee. This will lead to:

  • Increased awareness and visibility of TYPO3 CMS within the Netherlands.
  • Expansion of TYPO3's market share among Dutch organizations.
  • Fostering collaboration and knowledge sharing between Dutch TYPO3 agencies.
  • Establishment of a recognizable point of contact within the international TYPO3 community.
  • Development of a sustainable and vibrant TYPO3 ecosystem in the Netherlands.

Obligations to cooperate 

  • TYPO3 Association: Provide project-based support and negotiate revenue reinvestment.
  • Dutch TYPO3 Committee Members: Actively participate in all initiatives, including formalizing the committee, platform development, community building, and strategic considerations.
  • Participating Dutch TYPO3 Partners: Provide annual contributions to fund the project.
  • TYPO3 Team Leader Group: Receive official team requests and reports.
  • Dutch TYPO3 Agencies, Developers, and Users: Participate in community initiatives, utilize support structures, and contribute to the growth of the TYPO3 ecosystem.

Financial and human resources impacts 

Financial Impact:

  • Funding: A simple and transparent funding structure based on annual contributions from participating Dutch TYPO3 partners (precisely: back every EUR raised by the Dutch committee by 0.25 EUR in Association Funding, up to 9.000 EUR), supplemented by project-based support from the TYPO3 Association.
  • Revenue Reinvestment: Exploration with the TYPO3 Association for reinvesting a portion of Dutch-generated revenue (partner contributions, ELTS, memberships) back into the Dutch market.
  • Budget Allocation: Funds will be used for content creation, promotion, meetups, and technical support.

Human Resources Impact:

  • Committee Composition: Leader, Co-Leader, and Founding Members are already identified.
  • Roles and Responsibilities: The team will define internal roles and responsibilities within the committee.
  • No immediate hiring or firing of employees is indicated, but active participation and collaboration from existing TYPO3 professionals are essential.

Resolution/Petitum 

The Board resolves to:

  1. Approve the establishment of the Dutch TYPO3 Committee as a temporary initiative to become an official TYPO3 team after a 6-month formation period.
  2. Endorse the immediate actions (Q3-Q4 2025) as outlined in the proposal, including formalizing committee structure, establishing governance, securing funding, and activating the existing community.
  3. Approve the platform development initiatives, specifically the design of a Dutch product website, content strategy, and SEO groundwork.
  4. Support community-building efforts, including event participation, outreach to partnerships, and the implementation of KPI tracking systems.
  5. Authorize the committee to pursue strategic considerations, such as competitive analysis, negotiation for revenue reinvestment with the TYPO3 Association, and long-term planning.
  6. Commit to exploring the possibility of reinvesting a portion of revenue generated in the Netherlands back into the Dutch market to support strategic initiatives.

Discarded alternatives 

None

Attachments 

[Link to original proposal by the initiators]

Comments 

  1. Martin Helmich: "I voted 'no', because I felt the open discussions about the possible interpretations of 'Revenue Reinvestment' have not sufficiently been addressed."