Board Decision: FAIR Server
- Start of voting
-
5 April 2026
- Voting deadline
-
17 April 2026
- Decision owner
- Decision status
-
✅ Accepted, with 7 yes
Attendance and voting
| Board Member | Attendance | Vote |
|---|---|---|
| Olivier Dobberkau | Asynchronous | ✅ Yes |
| Stefan Busemann | Asynchronous | ✅ Yes |
| Boris Hinzer | Asynchronous | ✅ Yes |
| Rachel Foucard | Asynchronous | ✅ Yes |
| Martin Helmich | Asynchronous | ✅ Yes |
| Jana Höffner | Asynchronous | ✅ Yes |
| Thomas Maroschik | Asynchronous | ✅ Yes |
Decision description
Facts/Problem
The Core Team submitted the following request:
- At a recent hackathon, Core Team members implemented the FAIR protocol (a JSON API). A FAIR repository (similar to packagist.org) collects metadata from various sources, such as the TER (extensions.typo3.org).
- Later on, the FAIR protocol can also be used to introduce SBOM and package signing, providing a standardised approach built into the TYPO3 Core.
- To deliver the FAIR integration, a new dedicated server should be set up via the Server Team, for example under
packages.ortypo3. org fair.. The TER remains unchanged for the time being.typo3. org - The server will cost approx. 200 CHF per month, so the Server Team budget would need to be increased for 2026 and subsequent years. Maintenance of the application will be handled by Core Team members.
Objective
Increase the Server Team Budget by 3,060 EUR.
Obligations to cooperate
Extension Maintainers and Extension Users will benefit from the implementation of the FAIR protocol.
Financial and human resources impacts
- HR - none
- Financial Impact 3,000 EUR per year
Resolution/Petitum
Increase the Server budget by 3,000 EUR of the so far unused budget.
Discarded alternatives
None
Attachments
None
Comments
None