What's The Rule For Embedding Open Source Software?
I just talked with two CIOs who have different takes on embedding open source software in their companies' products. One sees it as standard practice, the other approaches it like a snake in a bag.
I just talked with two CIOs who have different takes on embedding open source software in their companies' products. One sees it as standard practice, the other approaches it like a snake in a bag.One gentleman is the CIO of an engine manufacturing company. He says the engineers in his firm regularly embed open source software in the company's products. From what he was saying, it sounded like this was a standard practice in his industry, and that he didn't have much to do with it. Otherwise, his company didn't use much open source software in its IT environment.
The other gentleman is the CIO of a company that provides computing services to financial firms. He says his company is careful to prevent any open source software from creeping into the products and services it sells.
"We try to manage where we use open source software, to manage the IP risk in open source," he says.
There's technology that checks software code against known open source projects, like that from Black Duck Software, which CIOs should make it a point to use, he says.
So, what's the rule on embedding open source software in products? Is that a good thing or a bad thing? Or does it vary by industry -- some where it's standard practice and some where it should be approached with caution?
The Business of Going DigitalDigital business isn't about changing code; it's about changing what legacy sales, distribution, customer service, and product groups do in the new digital age. It's about bringing big data analytics, mobile, social, marketing automation, cloud computing, and the app economy together to launch new products and services. We're seeing new titles in this digital revolution, new responsibilities, new business models, and major shifts in technology spending.