What is it?
The idea behind code sprints is to bring a group of developers together in one place to work on a specific topic for a few days. Instead of discussing concepts and ideas via email, messenger or mailing lists, the developers can exchange ideas directly. This saves time, avoids misunderstandings and enables intensive work on the product - without the usual disruptive factors and misunderstandings.
Where? When? Who?
Code sprints are commonplace in software development - and this also applies to the further development of Neos, the "next-generation open source content management system" of the TYPO3 community. With the upcoming release of Neos version 1.2, it was time again in the fall: From September 27 to October 5, Aske Ertmann, Release Manager of Neos 1.2, "invited" to a code sprint in the south of Denmark. But not, as usual, in a humdrum office. No, to Lungholm Castle, a stately manor house from the 16th century. With four-poster beds, a swimming pool and a dining room. But unfortunately without staff. They had to do their own shopping and cooking - but that didn't matter. 26 developers had accepted the invitation, from Germany, Denmark, the Netherlands, Russia, the USA and even Cambodia. And the two of us. It was the third Neos Code Sprint for me and the first for Daniel. But certainly not the last.
How?
At the start of the code sprint, we were divided into different groups to work on different topics. For example, translating the TYPO3 Neos user interface or improving the documentation. However, the focus ofpunkt des code sprint was on finalizing Neos 1.2 Beta 1. Many of the new features had already been developed, so it was mainly about the finishing touches: fixing bugs, improving stability and thus optimizing the user experience, to name just a few of our tasks. A lot of work. But there was no shortage of fun either - in the form of daily walks, a game of pool or social gatherings in the evening. The main topic of discussion was Neos 1.3, true to the motto: always think one step ahead. And one thing is already certain for us: when the next version is ready to be released, we'll be back at the Code Sprint!
