When Capital One was looking for a tool to help manage its software development pipeline, I suggested LGTM, an open source pull request approval system, as a starting point. After fixing bugs and adding new features to LGTM, I contacted Capital One’s open source office so I could return my changes to the community. And that’s where things got interesting.
I’ll talk about the process of forking an open source project for internal corporate use and what happens when you try to contribute it back. I expected it to be a straightforward process, but it was a story of heroes with interlocking concerns (and no villains). Along the way, I found a team of people to continue to develop the project internally, a community of users who provided feature requests and encouragement, corporate rules that vacillated between supportive and stifling, and an open source project with an uncertain future.
This session is sponsored by CapitalOne.
Jonathan Bodner is a technology fellow at Capital One, where he is working on a fork of the LGTM project that Capital One will be open sourcing soon. Jonathan’s team is helping to transform Capital One through the introduction and integration of new technologies, working to shorten release cycles, and generally pushing forward an open source-first culture. A software engineer, lead developer, and architect, Jonathan enjoys presenting and discussing open source, technology trends, and the future of software engineering. Over his 20-year career, he has worked in just about every corner of the software industry, including online commerce, education, finance, government, healthcare, and internet infrastructure. Jonathan is a frequent speaker at conferences, including DevFest DC, PyData DC, and at the Open Source Leadership Summit, as well as at internal corporate conferences at Capital One and Neustar.
©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