TYPO3 Association Policy for Committees & Official Teams

Please read Decision-Making Processes, Contribution and Participation to understand the terms Committees and Official Team.

Goals of the Policy

  • Clear definition of responsibilities
  • Transparent processes concerning empowerment and disempowerment within a team or committee
  • Clear rights and obligations
  • Clear lines of communication
  • A transparent organisation
  • Commitment to contribution


A temporary group working on a specific topic. No rights or obligations.

Official Teams

A community-driven team with specific responsibilities within an area. 

Founding an Official Team: A request must be submitted to  the TYPO3 Association Board.

Disbanding an Official Team: The Board or the General Assembly of the Association can disband a team. A team can be disbanded by the Association Board if it violates the expectations for more than 6 months.

Benefits for Official Teams

  • The leader and any other active team member can receive a typo3.org e-mail address. The address will be retained until the role ends (12 months of no activity in any team).
  • A team can maintain a team page at typo3.org.
  • A team member is allowed to call himself “Member of the TYPO3 [team name] Team“ as long as the member is active in the team.
  • A team can be assigned a budget (funding) by the Association or TYPO3 GmbH.

What is Expected of an Official Team?

  • A single leader (primary contact person) and one co-leader
  • At least three members when founded
  • The founding of a new team must be announced to the Team Leader Group
  • To become an official team, a team must have existed for longer than 6 months and fulfill all the requirements. This list makes up the requirements: 
    • A mission statement is required: What are the team’s general tasks, what do we want to achieve, which services do we offer, maintain, or answer for.
    • Four reports per year (news article at typo3.org) about what was achieved and what is planned.
    • An annual written report must be given at the General Assembly, containing an overview of the team’s activities during the last 12 months and plans for the coming year.
    • A clear definition of the team's tasks, responsibilities, and goals.
    • The team decides whether or not to allow new members. Entry requirements should exist in writing and be publicly available at typo3.org (community section) . New team members should be brought in based on a fair and equal process.
    • The Leader of the Team  (or a representative)  should attend Team Leader Meeting regularly.
  • The team defines itself and the roles within it.
  • In case of a dysfunctional team, any team member can escalate the topic to the TYPO3 Association or the Team Leader Group via an ombudsperson or through an official request to one of the board members.


An Association-driven team working towards the goals of the Association.

Committees are initiated by the TYPO3 Association Board and have to report to the General Assembly.

Disbanding a Committee: The Board or the General Assembly of the Association can disband a committee.

What is Expected of an Official Committee?

  • Committees are the direct responsibility of the Association. The Association takes responsibility that the committee exists and is active.
  • The TYPO3 Association aims to have one committee for each type of membership (for example, agencies, universities, partners) to have representatives of those groups.
  • The expectations for Official Teams also apply to Committees.
  • A member of the Board must be a member of each committee (but does not have to be the leader).


Committees enjoy the same benefits as official teams.

Closing Words

All members of a team have to respect the code of conduct. The Team and Committee Leaders have additionally to respect the policy for teams

Responsible for this document: Board of the TYPO3 Association