The integrity of the open-source development process is under fire, and that may lead to some changes
Say what you will about SCO Group's allegations of source-code misappropriation (certainly, much of what has been said couldn't be printed here), the controversy raises questions about how open-source software gets assembled. While the community approach to open-source development undoubtedly leads to innovation and quality software, the process lacks some of the controls used in commercial software environments. If Linux is to keep growing, does the freewheeling network that creates it need to change? Some experts say it must.
SCO Group, with its $3 billion intellectual-property lawsuit against IBM and threat of legal action against users running the Linux operating system, started the debate over the operating system's lineage, but the intellectual-property issues facing Linux may not go away even if that case does. SCO officials say other Unix vendors have inappropriately contributed SCO's code to Linux, too. And Microsoft chairman and chief software architect Bill Gates, in a recent meeting with financial analysts, suggested the problem is even wider. "There's no question that, particularly in some of the more cloning-type activities, intellectual property from many, many companies, including Microsoft, is being used in open-source software," Gates said.
Uncertainty over the integrity of Linux code has led some IT analysts to warn companies to proceed with caution, and the discomfort level is rising among business-technology managers who have bet on the platform. "Something definitely needs to be done [differently]," says the CIO of a large company that has deployed hundreds of Linux servers.
Some Linux developers acknowledge they need to do a better job of proving that the code they submit for inclusion in Linux, under the General Public License, is squeaky clean. "There's no doubt about it. There needs to be more thought put into validating where a particular code contribution comes from," says Ian Murdock, founder of the no-cost Debian version of Linux and co-founder of Linux distributor Progeny Linux Systems.
Contributions to Linux code at the Open Source Development Lab must go through a structured process, CEO Cohen says.
Photo of Stuart Cohen by John Gress
Not everyone agrees that the open-source model needs fixing. "Nothing about SCO's case against IBM tells us that our system has failed us," says Mark Webbink, general counsel for leading Linux distributor Red Hat Inc. Adds Stuart Cohen, CEO of the Open Source Development Lab, which is creating Linux-based software stacks for data-center workloads, there's "a very structured process for getting code into the kernel."
The development lab gets its funding from Hewlett-Packard, IBM, Intel, and other computing companies that back Linux. Among the checks and balances in place, Cohen says, are that code contributions must pass muster with Linus Torvalds--the Linux founder who recently went to work for the lab--as well as with Andrew Morton, who maintains the Linux kernel, and end users. Corporate members generally run potential contributions past their legal departments.
Holger Dyroff, director of sales with distributor SuSE Linux AG, says the very openness of open source makes it easy for an individual or a company to check if there's any concern over potential intellectual-property violations.
But the system isn't foolproof, and Torvalds doesn't want open-source developers doing intellectual-property legwork. "It is not engineers who should look up patents, it is patent lawyers," he wrote via E-mail in response to a question. "Having engineers try to look up patents only taints them and opens them up for willful infringement." Torvalds wrote that lawyers employed by the development lab's member companies should be the ones to watch for any problems.
A degree of uncertainty is inevitable with open-source software, says Stuart Meyer, a partner in the intellectual-property and litigation groups at law firm Fenwick & West LLP. But open-source developers could reduce uncertainty by being more "cognizant" of patent and intellectual-property issues and reviewing their work to ensure that it doesn't violate someone else's rights. "Some people are being ostriches and not doing this review," he says. "Others are working on it extensively."
Building A Mobile Business MindsetAmong 688 respondents, 46% have deployed mobile apps, with an additional 24% planning to in the next year. Soon all apps will look like mobile apps – and it's past time for those with no plans to get cracking.
Join us for a roundup of the top stories on InformationWeek.com for the week of December 14, 2014. Be here for the show and for the incredible Friday Afternoon Conversation that runs beside the program.