Octopus Deploy may have started as a closed source project, but the company now has more than 50 public repositories in GitHub, many of which contain core product functionality. This has raised some eyebrows, but companies as large as Microsoft have been making similar steps, opening what used to be proprietary.
Opening up a closed codebase can bring significant benefits, but there are legitimate fears around losing intellectual property, exposing security flaws, or even just showing the world that your code isn’t perfect. Damian Brady shares how and why Octopus Deploy decided to go down this path and offers lessons that can be applied to any company considering the same journey.
Damian explores Octopus Deploy’s decision to start opening its code, how the company decided what needed to keep private and how it makes that decision on an ongoing basis as the product grows, and the practical complexities around development, including how Octopus Deploy works with both public and private repositories and how it isolates the codebases. Damien concludes by highlighting the benefits Octopus Deploy has seen as the community has started participating and the challenges with keeping everyone happy.
Damian Brady is a solution architect for Octopus Deploy. A Microsoft MVP, Damian spends a lot of time training development teams on how to deliver their software better, be it through improving their Agile process, code quality, or DevOps strategy. He is a developer and a Pluralsight and book author, and he regularly speaks at conferences, user groups, and other events around the world. Damian recently moved to Toronto, Canada from Brisbane, Australia.
©2017, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org