July 20–24, 2015
Portland, OR

Creating an open source office: Lessons from Twitter

Chris Aniszczyk (Cloud Native Computing Foundation)
2:30pm–3:10pm Thursday, 07/23/2015
Collaboration Portland 255
Average rating: ****.
(4.00, 6 ratings)

Prerequisite Knowledge

A desire to learn about how open source, otherwise my goal is to make the material easy enough to understand for non-technical folks.

Description

According to some studies, open source is being adopted by well over half the companies in existence. Common challenges when companies start adopting open source is how do you contribute back or what do you even open source. Companies like Google, Intel, Facebook, and Twitter have chosen to establish open source offices to facilitate working with open source communities.

In this session, I will speak from my perspective of creating and running Twitter’s open source office (@TwitterOSS). From a historical perspective, in 2011 Twitter embarked on the journey of creating an open source office to facilitate its collaboration with open source projects and communities the company depended on. We will dig in on why we started an open source office and how we established our open source culture. Furthermore, we’ll also go over some lessons learned on top of discussing why we open sourced certain projects and why we didn’t open source others.

We hope you will walk away with an idea on how to start an open source office along with ideas you can bring to improve open source collaboration within your organization.

Photo of Chris Aniszczyk

Chris Aniszczyk

Cloud Native Computing Foundation

Chris Aniszczyk is an engineer by trade with a passion for open source and building communities. At Twitter, he created their open source program and leads their open source efforts. He also sits on the Eclipse Foundation’s board of directors representing the committer community. In a previous life, he bootstrapped a consulting company, made many mistakes, led and hacked on many eclipse.org and Linux related projects.