Daniel Nadasi,Daniel Bentley (with Daniel Nadasi) It is a pain to openly release code for established projects that are developed internally within a corporation. This is particularly true for larger and more successful projects, which already have working processes. The open-source transition bothers engineers, introduces new tools, needs buy-in from “higher ups”, and requires more time and effort than management is usually willing to spend. So how do you do it? In this talk we are going to describe the problems that we have encountered trying to open source substantial projects from within Google, including Closure Tools and GWT, as well as the tools and procedures we have created to make this easier. We’ll also describe the open Make Open Easy (MOE) project, which was developed to allow open sourcing of closed internal projects with minimal effort - handling syncing of open and closed source repositories, propagating changes and maintaining diffs between open and closed development sources. Less