Crista Lopes discusses if scale affects the internal structure of projects and whether the popularity of libraries is correlated with internal software metrics such as bug density based on analyzing the source code of 30,000 open source Java projects.
Kristian von Bengtson discusses the challenges met developing space crafts in a nonprofit environment, plus political and legal loopholes which help to keep an amateur space program on track.
Sudhir Tonse presents Netflix' composable PaaS built with several components that have been open sourced.
Michael Hausenblas introduces Apache Drill, a distributed system for interactive analysis of large-scale datasets, including its architecture and typical use cases.
Peter Ledbrook discusses the benefits and drawbacks of open source, advising that it should not be treated as a no-cost solution. He also offers ideas for making the community more active and engaged.
Ryan Martens encourages citizen engineers to join forces with entrepreneurs in order to tackle world’s toughest problem using Design Thinking, Agile, Lean Startup, open source, biology and sociology.
Andy Piper discusses the current state of PaaS, and why its success lie in enabling developer productivity, openness and choice, considering Open Source in general, and Cloud Foundry in particular.
Michael Rauch and Christoph Gutmann explain how Eclipse Modeling technology is successfully applied to establish forward engineering in the domain of technical SOA. Modeling and code generation help them to drive standardization, increase quality and portability, reduce development effort and gain insight into dependencies.
The authors explore engaging audiences through play, and how open source software, interactive video, and 3D projection mapping invites a dialogue with the participants in a multi-media environment.
Theo Schlossnagle keynotes on the role of open source software and the breaking up of silos in the enterprise in creating scalable systems.
Steve Klabnik discusses the importance of having an open API, believing that those who have it will succeed in the long run, and the others will fail.
Johan Oskarsson explains how Twitter is using Zipkin to trace a pages in order to see their execution path and to determine the time spent for loading for performance monitoring and analysis.