The TYPO3 Server Team is responsible for management of lower-level services. Besides maintaining the server infrastructure of the TYPO3 project, the team is also in charge of administrating several central services and web sites. We see ourselves as a service provider towards the community and other teams, like the Core Teams or the Documentation Team.
Team Lead
The team currently consists of (in alphabetical order):
Former team members: Ingmar Schlecht, Joern Bock, Sebastian Kurfürst, Susanne Moog, Christian Trabold, Peter Niederlag, Fabien Udriot, Patrick Oberdorf, Steffen Gebert
We are open for new members! It doesn’t matter if you are more interested in administrating operating systems or some of the official web sites, but you shouldn't be afraid of devops basics (Configuration Management, Monitoring). Please get in touch with us, if you are interested to work with us!
Interested people can attend our regular online meetings and are also invited to team sprints. They can choose an introduction project to work on while we get to know each other... We take the liberty to wait for some time until we hand over the credentials for the complete infrastructure, so understand that this will not happen immediately.
We meet online every 2 weeks. Meeting reports will be published on our Gitlab team project.
You can also follow us in Slack (#typo3-server-team) and @TYPO3server on Twitter to receive updates from our team.
The email address admin(at)typo3.org serves as the central point to get in contact with the persons in charge for administration of typo3.org servers and web sites. In case we are not responsible, we will delegate your email to the persons in charge. We make use of OTRS as trouble ticket system for this job.
We manage all applications and services within the TYPO3 universe. If you as a TYPO3 team, or as a single person, want to offer a service to the TYPO3 community, please get in touch with us to offer you some web space or an entire virtual machine for your project.
We aim to openly publish all our work transparently. Apart from security related tasks, our current workload can be followed on our GitLab team board, and all technical configurations are stored in their respective service repository.
Among others, the following Open Source projects are currently used by us:
Technical details can be found in the corresponding service repository.
