Skip to main navigation Skip to main content Skip to page footer

Stability & Compliance Unit

The Stability & Compliance Unit is responsible for continuously delivering a stable, secure, accessible and localizable TYPO3 product. It safeguards the quality of every supported TYPO3 version and supports the extension ecosystem in meeting the same standards, so that editors, integrators, agencies and site owners can rely on TYPO3 in production and meet their legal and regulatory obligations.

The unit exists to:

  • Keep TYPO3 stable — fix bugs and regressions, maintain supported and LTS branches, and ship dependable maintenance releases.
  • Keep TYPO3 secure — handle vulnerabilities in the Core and extensions under a policy of least disclosure, and inform the community through Security Bulletins.
  • Keep TYPO3 accessible — remove barriers in the backend, the default frontend output and the editing experience, measured against WCAG, ATAG, the EU harmonised standard and BITV.
  • Keep TYPO3 usable in every language — run the translation infrastructure for the Core and extensions.
  • Make compliance verifiable — turn security, accessibility and quality requirements into clear standards, guidelines and release criteria for the Core and the ecosystem.

The unit's focus is the quality of what exists. This also includes smaller features, however where a fix needs product or architecture changes, the unit works with the units that own them.

Responsibility Domain

The unit is responsible for the following areas of expertise, each led by one working group, in both the TYPO3 Core and the wider ecosystem.

  • Stability & maintenance
  • Security
  • Accessibility
  • Localization

Shared responsibilities of the unit:

  • Define release quality criteria for maintenance and security releases, covering stability, security, accessibility and localization.
  • Act as a single point of contact for other units on quality, security and compliance questions.
  • Review changes from other units for security, accessibility and localization impact before they ship.
  • Maintain public guidelines and policies in its areas (security guidelines, extension security policy, accessibility and localization guidance).
  • Track external requirements that affect TYPO3 and its users, and translate them into concrete work for the Core and guidance for the ecosystem.

Members

Georg Ringer

Unit Coordinator

Benni Mack

Deputy Unit Coordinator

Chris Müller

Unit Member

Maike Kiebele

Unit Member

Martin Pribyl

Unit Member

Peter Kraume

Unit Member

Stefan Bürk

Unit Member

Torben Hansen

Unit Member