After a six hour walk around Copenhagen, one of the best cities on earth, I have a few hours before the flight to stop and think what this week meant for me.
Where I’ve been to last week
It is not so simple to explain. It was not a vacation. But I would not call it work either… It was not a conference, nor was it a tutition or a school. Bunch of people, literally from all over the world, come together to share a common passion: building a content management system (CMS) that does not suck. We call it a code sprint. None of us was paid for participation, we did it from pure passion. But none of us had to pay either, thanks to our amazing sponsors!
To summarize: bunch of geeks living in a XVth century castle, building best CMS on earth – TYPO3 Neos.
A kickoff meeting to start the sprint
What I have learnt
Going to the sprint I knew I would probably learn a few things… You see, I’m at peers with computers since ‘95, since ‘05 doing professional web development, so I had hoped that I would have learnt a few things by then. But compared with the guys that were at the sprint, my knowledge in all areas was an absolute zero. And that is such a cool and humbling experience!
Some of the lead developers in action
I had never been learning so intensively in my whole life. Ever. It felt like all of the participants were jumping on top of my poor head, trying to shove into it as many things as possible.
As a result:
- I got an overview of the core of TYPO3 Neos;
- learned to set up Vagrant boxes;
- learned to write unit and functional tests;
- learned working with JIRA and Gerrit code reviews;
- improved my Git skills;
- got to feel what working agile is like;
- got a few insights on how RESTful services should work;
- and even began using VIM mode in SublimeText… Geekish!
Dining with style…
What was done
But, of course, the sprint is not a programming school, and we came together to contribute, not just to learn.
It’s really hard to imagine what amount of work 30 passionate developers can pull off during one week! ACL, backend translation, content dimensions, countless bugfixes, finalizing a release of Neos version 1.2 is just a very shallow overview.
I joined a team that focused on improving editor experience. Fixing bugs, improving error detection and notification: all of those things that could get you frustrated with Neos pretty quickly! Also I managed to add a few features like TypoScript inclussion globbing, TypoScript image object and a few other improvements.
My typical workplace
Contributing to Open Source projects is a win-win solution for both agencies and freelancers alike. You get the tool that really fits your needs like a glove, that you learn throughout and can fix yourself, in case things go wrong. But also you contribute to something bigger than yourself and your bussiness interests, something that adds real value to life of editors and developers throughout the world. This is the spirit Kasper Skaarhoj has put into our community from the start, and I really care we will be able to keep it breathing among us.
A few personal things
Cooking and cleaning up together, conversasions during long walks, morning runs: everything was so natural and welcoming, that I could barelly remember that it was my first event in TYPO3 community. I’m especially grateful to Aske Ertmann, who took all of the bitter organizational tasks for himself. No doubt 1.2 will be a very solid release, with such a release manager!
And one more thing. It is so enjoyable that my contribution to the NEOS project is possible as part of my work time at our amazing St Philaret’s Christian Institute. Now we finally have a chance for cool new website made with Neos :)
One of the daily walks. Checking out the surroundings
My amazing room mate, Visay from Cambodia(!)