...The challenge faced by the Open Source Team is to take the current goodwill around Zalando’s open source work and professionalize it. This will enable Zalando to use and create open source in a consistent manner. With consistency, we can scale and streamline our open source activities and evaluate their impact and value, ensuring they are aligned with Zalando’s longer-term vision...
Work done in 2018...
2018 has by design had fewer releases than in the high activity years of 2015 and 2016. However, all other activity indicators are higher than any previous year. Releases, Pull Requests, Commits and contributions from external sources have all increased compared to 2017.
Pull Requests Created
Community and contribution
Of our org members are contributing
Out of the current 510 people in Zalando organisations on GitHub, half of them have made an accepted code contribution to a Zalando open source project - this is a 4% increase since June 2018.
For all current projects, 31% of all pull requests are from non-employees.
Contributions made to techradar projects
Zalandos contributed to 18 projects on the Techradar "Adopt" tier, which are part of our tech stack and have a high strategic value to Zalando
Average time to get a pull request merged
The average response time to pull requests have increased from 85 hours to 91, the number is within an acceptable response time.
Open source activity by Zalando employees (purple) is at a overall stable level with seasonal variations (summer holidays and the run up to black friday are typical low-activity periods). We are however seeing a positive increase in External contribution (blue) to our projects. The single big spike in the chart above is caused by a GitHub bot doing over 100 automated pull requests.
Our goal for responding to pull requests is 80 hours, this includes weekends and holidays, we generally succeed at keeping our reponse time at a satisfactory level for pull requests by employees but are seeing spikes more often for external contributions. Average across all pull requests is 91 hours. Unfortunately, this year we had 45 contributions which did not see a response in over 100 days.
Top contributors in 2018
While open source is encouraged at Zalando, it is a small number of contributors who drives the majority of all open source contributions. Just 17 Zalando employees are responsible for 50% of all commits made, and 80% of all open sourced Zalando code is contributed by 50 employees.
What we share
New releases in 2018 included 3 projects focused on machine learning: Flair, a natural language processing framework built on top of
Pytorch. Famos, an adversarial framework for image stylization and
Darty, a data dependency manager.
3 projects related to our work with Kubernetes was released during 2018: Cluster-lifecycle-manager, to provision multiple kubernetes clusters, Stackset-controller, a kubernetes resource lifecycle manager and Kube-metrics-adapter for Kubernetes HPA metrics collection.
The Zalando open source team released documentation and tooling for managing and releasing open source projects: Roadblock and Trafficlight.
Most Popular Projects
As technology and trends shift, we see the average activity for a project drop after 24 months to a generally lower level. After approximately 45 months this drops further as many of our projects enter a state of decline or maintenance mode. This is in line with the general trend of open source project activity.
Past 6 months
The past 6 months, the Open Source team has been focused on creating clearity of Zalando open source policies, remove barriers of entry and spread the culture of open source among current maintainers and new hires. The list below is the open source team's roadmap for second half of 2018 along with a status of each task.
Website launched May 2018 - updated on a weekly basis
Restructure completed August 2018
Training program initiated October 2018 for all new tech hires
New project incubation process introduced in September 2018, promotion framework piloted November 2018
First round of project maintainer training in January 2019 - mandatory for all new projects
While internal developer ruleset has been updated we still see room for improvements in regards to how ownership and copyright is managed
Top priorities for the open source team in the coming 6 months.