The Story Behind Capital One’s Fork of an Open Source Project – InApps is an article under the topic Software Development Many of you are most interested in today !! Today, let’s InApps.net learn The Story Behind Capital One’s Fork of an Open Source Project – InApps in today’s post !
Read more about The Story Behind Capital One’s Fork of an Open Source Project – InApps at Wikipedia
You can find content about The Story Behind Capital One’s Fork of an Open Source Project – InApps from the Wikipedia website
For large open source projects, it can be difficult to manage all of the pull requests that come in from different parties, so, naturally, the need to automate the approval of pull requests has led to the creation of several open source projects. LGTM (Looks Good to Me) is one such automated system, built around GitHub. It locks pull requests from being merged upstream until a given number of approvals have been received.
LGTM does not come pre-configured for being bolted into certain implementers’ existing tool chains. Now, as it is a general-purpose project, perhaps no one should expect it to be configured this way. But then what’s the purpose of the open source development process if not to open up integration capabilities to implementers?
At the last OSCON conference, Capital One lead software engineer Jon Bodner tells the story of how LGTM’s principal developer gave his team his blessing to produce a fork that adds functionality that may be more specific not just to Capital One or another financial institution, but any organization of its magnitude.
“When you have pull requests, you want to make sure there’s been some sort of code review, that somebody’s actually checked to make sure that you’re merging in something that’s been validated,” Bodner explained to InApps’s Alex Williams. “And oftentimes people see pull requests, they merge it, they’re done. But you don’t really know who’s doing that merging. It could be the same person who did the pull requests in the first place. And at bigger places like Capital One, you want to have some sort of control over the process.”
Learn more about how Bodner’s efforts could lead to a more role-based, policy-oriented request management system, in this edition of InApps Makers podcast from the last OSCON in Austin, Texas.
Also available on Apple Podcasts, Google Podcasts, Overcast, PlayerFM, Pocket Casts, Spotify, Stitcher, TuneIn
In This Edition:
1:00: Bodner’s presentation at OSCON 2017.
5:33: Capital One’s internal open source process.
9:18: How Capital One uses Boolean logic.
13:47: What iterative patterns Capital One is building upon.
14:48: What gaps Bodner is seeing in the software development process.
16:42: How Capital One captures knowledge for its future projects long-term.
Capital One is a sponsor of InApps.
Let’s create the next big thing together!
Coming together is a beginning. Keeping together is progress. Working together is success.