Cancel
Start searching
This search is based on elasticsearch and can look through several thousand pages in miliseconds.
Learn more
This search is based on elasticsearch and can look through several thousand pages in miliseconds.
Learn more
Together with my punkt.de colleagues Weiye and Joachim and our two core developers Daniel and Sebastian, I took part in the Neos Sprint in Hamburg at sitegeist at the end of March. It was the first code sprint for Joachim, Weiye and me and we were very excited to see how the Neos team was organized and how we could contribute to the project.
We three newcomers were a little self-conscious at the beginning, trying to find our way in. Where can we find work for ourselves, where are we needed? Is there a list of tasks that we can look at? Do I even have the skills to solve one of the tasks?
The personal closeness and impartiality of the core developers very quickly lowered the inhibition threshold for asking supposedly stupid questions - and each of us found an issue on Github that we could try our hand at. In most cases, the right core contact person also emerged from the task. While Joachim and Weiye worked on Neos, I took a task from Flow, the framework on which Neos is based.
Basic questions about contributing to the projects are explained in detail on neos.io. If you still have questions, the Neos Slack is a good place to go.
We soon had active pull requests on Github, in which we discussed our implementations with the core developers on site or elsewhere in the world. While working together, we got to know the process of a pull request and were hit on the fingers more often than we would have liked by the test mechanisms that check the code for style and run tests.
The feeling of elation when the tests were all green and the core developers involved in the review had also given their approval was all the better for it. Afterwards, pressing the button that unites our implementation with the project released us from the pull request, exhausted but proud and highly motivated. We didn't allow ourselves much of a break, however, and immediately moved on to the next task.
Outstanding tasks and issues are documented in the issue trackers for Neos and Flow.
An introduction to pull requests can be found in the Github documentation.
I am particularly proud of the feature that I was able to implement for the Flow framework. This allows package developers to generate translation files in XLIFF format for any language. If there is already an XLIFF file with labels for the standard language, the translation files for the new languages are automatically filled with the existing labels so that the developer only has to enter the translations.
Shortly before the Neos sprint, Joachim developed a Vagrant box based on the punkt.de-proServer, in which the Neos development project is stored when the box is started. This box served Joachim, Weiye and I as the basis for our developments at the sprint and is freely available to any motivated contributor.
Our Vagrant box based on the punkt.de-proServer offers an easy-to-install development environment.
A prerequisite for using the box is the installation of Vagrant and VirtualBox.
