Here’s a quick recap of what happened — and why these sprints are always worth showing up for.
A new month, a new Monday. So it's time again for the Remote Code Sprint, which has become a regular event, working on the Tea example (tea) extension. Even though one participant had to leave early (Bernd wasn’t with us for the final huddle in the afternoon), it was still a successful and satisfying day for all participants.
A Running Start
The code sprint started punctually at 11:00 on Monday. Everyone was in a good mood. I played at The Grand Jam at the weekend and rocked the stadium in Dresden together with around 1000 other musicians. Oli was happy because the temperatures were a bit more pleasant again at the weekend, and Daniel and Bernd were just happy to see us and rock this Code Sprint together. So we really stepped on the gas, and it was no wonder that after less than 10 minutes we were already through with the kickoff and the planning for the day. That's what I call being effective. But then again, we are all old-timers. So let's rock it
Newcomers Welcome
That said, these sprints aren’t just for old hands. Anyone who has the time and inclination is welcome to join us on the first Monday of the month for the Best Practices Team Remote Code Sprint. It doesn't matter whether you're an old-timer or a newbie.
So take heart! Just turn up. No need to register. If you’re there, jump in! We’ll find something for you to work on. Only have an hour or two? Totally fine. Not confident in your English? Also not a problem — German is often our default anyway, and we’ll make sure you feel included. The important part is showing up.
What We Accomplished
We were able to merge a total of 10 pull requests and close some of the open tickets as a result. Oli focused on reviews, while the rest of us cleaned up a lot of code, rewrote sections, and got things ready for TYPO3 v13 compatibility. We also improved the documentation in a few places.
Thanks and See you Next Time
Finally, thanks again to my employer Undkonsorten, who regularly gives me the opportunity to participate in these sprints during work hours.
The next remote code sprint will take place on 4 August 2025. Maybe just ask your agency if there are any opportunities to take part in the code sprint? we’ll meet at 11:00 in the Slack channel of the Best Practices Team (#best-practices-team). Until then, happy coding!.