Framework Mergers
Framework mergers are allowed to merge to any part of TYPO3 Core and its components and subsystems. This is a group of active people with enough knowledge of the architecture and feature-set of TYPO3 Core, as well as a broad perspective.
Their responsibility is to ensure a consistent, secure and stable API throughout all maintained branches of TYPO3 and its components. All members of this group are required to participate actively in helping other contributors to build a consistent API across the source code and documentation. All members ensure the code quality is increased and the feature set defined by the TYPO3 Project Leader is implemented properly. They are responsible for all parts of TYPO3 Core. It is required that all members know state-of-the-art technical functionality (currently PHP8, JavaScript/TypeScript, SCSS/CSS and HTML5).
Regular communication with a maximum response time of 48 hours within the framework merger group is required. In addition, it is necessary that framework mergers coordinate development in a monthly meeting call. A total of 8 (eight) framework mergers (excluding TYPO3 Project Leader and Product Team, which overrule changes by framework mergers) is planned to keep communication tight and effective.
All framework mergers have full responsibility for every line of code or documentation within TYPO3 Core or their components, and are required to maintain actively on solving existing bugs or reviewing and improving existing changes.
Members
Andreas Kienast
Framework Merger
Andreas Nedbal
Framework Merger
Anja Leichsenring
Framework Merger
Benjamin Franzke
Framework Merger
Christian Kuhn
Framework Merger
Garvin Hicking
Framework Merger
Georg Ringer
Framework Merger
Oli Bartsch
Framework Merger
Stefan Bürk
Framework Merger