Developer's Toolkit

Blog archive

No Good Deed Goes Unpunished

There are at least two sides to every story. Those science fiction fans among you might remember Larry Niven's Gripping Hand, a tale of aliens with two smallish arms on the right side and one large, um, gripping hand on the left. This led to a certain way of thinking about tradeoffs involving three sides. Rather than the two hands upon which we look at the sides of an issue, there were two considerations of note, but one additional and overriding factor upon which every good decision was based.

Well, the story last week of Microsoft and Novell teaming to add a level of legal assurance to Linux may not be a good deed in the pure sense of the term, but it did succeed for a brief time in providing a measure of comfort to enterprise CIOs who would like to employ Linux but are afraid to do so because of patent or other intellectual property (IP) implications. As we learned in the still-ongoing SCO case, users of disputed IP can also be pulled into a legal no-win situation as easily as the vendor.

Now Eben Moglen, the general counsel of the Free Software Foundation, has announced that the next version of the GPL will specifically forbid such deals (http://money.cnn.com/blogs/legalpad/index.html). The FSF believes that the fact that it gives the Novell SuSE distro an advantage not available to other distributions makes the agreement untenable. And with ownership of the license verbiage, the FSF has the ability to do just that, even after the fact.

I admire Richard Stallman. I don't necessarily agree with him, but I do admire his single-minded pursuit of a radical ideal over the course of more than twenty years, and the eventual acceptance of the salient parts of that ideal by the industry mainstream (though one of his original precepts in the GNU Manifesto, that software developers should be paid through a tax on hardware, remains a nonstarter for good reason).

However, the vast majority of Linux advocates and users (or GNU/Linux, as Stallman insists) are not license purists. They have jobs to do, and Linux provides a reasonable way of doing their jobs. By and large, the GPL in and of itself has not been a deal-killer in many enterprises. But IP issues are different, and even if enterprises have accepted that risk, surely it keeps some CIOs up at night.

According to Moglen, GPL version 3 will be adjusted so the effect of the current deal is that Microsoft will by giving away access to the very patents Microsoft is trying to assert. It will be interesting to see if the GPL can legally make that assertion, seeing as Microsoft is not a party to the GPL and does not license any of its own software using that license. So for enterprise IT shops looking for legal guidance on open source in general and Linux in particular, the uncertainty continues. This uncertainty may become the gripping hand that prevents further acceptance of Linux by mainstream organizations.

Posted by Peter Varhol on 11/15/2006


comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube