Collaboration Summit 2014

Companies often create projects internally in order to address some particular need. The LF and others have been trying hard and succeeding in getting companies to open their code and work together. So what does it take to create a project? How does a project attract a community and retain it? What should the governance look like? Projects started by companies also face a special category of concerns, like protecting the company's IP, dealing with confidential data, dealing with people being reassigned to different projects, etc. If not handled correctly, those issues could derail a project.

This presentation will try and cover many of those topics. It is not meant to exhaust the subject, but serve as a discussion starting point. The presenter will will draw heavily from the experiences in making Qt and Tizen openly-governed projects, a subject he's been involved with for many years.

The audience should be people working for companies interested in opensourcing some internal code and creating open source projects out of them, as well as those interested in participating in projects created by such companies, to understand what issues "the other side" faces and how to deal with them.

This presentation is meant to explore the subject of what an Open Source Project (with a capital P) is, how they can be established and to get the discussion going on what best known methods might exist.