Lessons Learned from starting an Open Source Office*
Twitter recently created an Open Source Office. Throughout this adventure, many lessons were learned and should be shared.
In late 2011, Twitter created an Open Source Office to support a variety of open source organizations and maintain a healthy, reciprocal relationship with open source communities important to the company.
There is no book really out there on starting open source program. This talk will describe our journey of creating an open source program and instilling an open source culture throughout the company. We’ll discuss our philosophy, licensing decisions and lessons learned.
I've spoken at many conferences before, here's a list:
Chris Aniszczyk is a software architect by trade with a passion for open source and cultivating communities. At Twitter, he’s responsible for creating their open source program office and crafting their open source strategy. He also has the honor to sit on the Eclipse Foundation’s Board of Directors representing the committer community. In a previous life, he bootstrapped a consulting company, made many mistakes, hacked on many eclipse.org and linux related projects. He also fancies running long distances and prefers hitting the trails.