Component Mergers

A component merger is responsible for 

• This code, functionality, backwards-compatibility and architecture and future development. A component merger has direct merge rights to this component. Any change can however be overruled by a Framework Merger or TYPO3 Project Leader. If a change touches various places outside of the component. 
• Developing a vision for this component for future improvements, and communication of this vision together with the TYPO3 Project Leader. A component merger must be in touch with the TYPO3 Project Leader at least once a month on a status update, blocking issues or questions to continue in this area. Any violations to misusing the merge rights or miscommunication can lead to immediate revocation of this status.

New components are defined by the TYPO3 Project Leader.

Not every part of TYPO3 Core is covered by a certain component (e.g. Hooks, Dependency Injection or Extension API), but these overall areas are then responsibility of the TYPO3 Core Framework.

Component focus

The following components are currently focussed on:

• CLI Integration: CLI Improvements & Composer Plugins
• Testing: Testing API / Testing Framework & Testing Infrastructure Improvements
• Documentation: Core Documentation / RSTs / Manuals maintained within TYPO3 Core Repository
• Extbase + Plugin API: Extbase Plugin Functionality
• Fluid Engine + Fluid Integration: Standalone Fluid Template Engine and Fluid system extension
• Issue Tracking / Reporting: Ticketing system structure, bug triaging
• Persistence + Database Layer + Workspaces: DataHandler, Doctrine DBAL and Overlay functionality
• SEO: SEO system extension & Frontend Meta Tag Rendering
• Link Validator: Improve the linkvalidation functionality
• UX: Backend User Experience

Vacant positions

Component merger positions are currently vacant in these focus areas:

• Extbase + Plugin API
• Persistence + Database Layer + Workspaces
• SEO
• Link Validator