Server Team Status Report — November 2024

Categories: Community, Server Created by Andri Steiner
Close-up of computer servers with various colored cables connected to the ports. The focus is on the blue and white cables plugged into the front panel, indicating data or network connections.
Photo: Brett Sayles / Pexels
Time flies, and with the fourth community sprint of the year almost complete, we’re ready to look back on another year of server maintenance work in the TYPO3 universe.

Sprint Participation

We’ve been able to join the June and November community sprints at TYPO3 HQ in Düsseldorf, Germany. It is always great to hang out and work with members of other teams, and we’re looking forward to see all of you again at the sprints next year.

New Team Member

In July, we welcomed Steffen Hastädt as new member in our team. Steffen is a seasoned TYPO3 developer working for RTP GmbH, Zürich. He is already familiar with our server stack, and we’re happy to have him with us.

Achievements

Among many other things, we worked on and finished the following projects during remote days and community sprints:

  • Streamlined the GDPR process, once again. Meanwhile, your accounts in most systems will be removed automatically should you decide to terminate your my.typo3.org account.
  • Improved our web server configuration to make our infrastructure more resilient regarding massive bot requests.
  • All servers have been migrated to the latest Debian version 12 (beside one where we have to wait for an update).
  • Throughout the year, we installed numerous updates on our systems, such as Gerrit, GitLab, HedgeDoc, Mailcow, Matomo, OTOBO, and Redmine.

Meet, Join, and Follow Us

During the year, we see each other in monthly video calls to coordinate our tasks. These meetings are public, and everyone is welcome to join us for questions or even just to say hello. Every few months, we meet in person at one of the community sprints or other TYPO3 events.

We aim for open communication and processes. You can follow our work in GitLab, on our Status Page, and on Mastodon.

Additional contributors for this article
  • Copy Editor : Felicity Brand
  • Content Publisher : Mathias Bolt Lesniak