Save up to 50% on HP Products
- Related Stories
-
Lawmakers gear up for patent system overhaul
February 15, 2007 -
Two Linux consortia band together
January 21, 2007 -
Open-source leader leaving Novell for Google
December 21, 2006 -
Microsoft makes Linux pact with Novell
November 2, 2006
In particular, the Free Software Foundation wants to use the ongoing revision of the General Public License that controls Linux and other major open-source programs to hamstring this deal and to prevent other software distributors, whether proprietary or open-source, from adopting anything similar.
It is an interesting situation, because "FSF" is not synonymous with "open-source community," even though many news reports seem to equate the two.
The FSF is often equated to a religion, and the comparison is apt. It regards proprietary software as immoral, patents as the work of the devil, digital rights management as an unacceptable infringement on freedom, and markets for intellectual creations as undesirable or irrelevant.
In contrast, Microsoft and Novell are the antithesis of religions. They are integrated into the world of commerce and day-to-day affairs. And in this world, one rule is paramount: The customers win, because they control the marketplace.
From this perspective, the deal between the two is dictated by a simple reality. The customers want what the deal provides. They want interoperability of open-source and proprietary programs--the ability to run both types of program in heterogeneous environments--without being required to perform the integrations for themselves. This means that open-source and proprietary software providers must create a structure that allows them to cooperate on finding technical solutions to their customers' demands. It is not possible to solve the customers' problems for open source without also solving them for proprietary companies, and vice versa.
Customers also want freedom from concern about potential intellectual property problems. They do not want to worry whether someone might come out of left field claiming the right to enjoin some mission-critical application.
The FSF may not be required to care about these customer demands, but most other members of the open-source community cannot be so cavalier. They value the freedom and sharing of the church of open source, but they all have a foot or two, and maybe a leg, in the commercial world as well. They must have, if they are to make a living in any way except flipping burgers by night to finance code writing by day.
So community members collect paychecks from computer companies that value open-source software as an adjunct to their hardware/software/services offerings, many of which are, of course, heavily dependent upon patent protection to maintain their competitive positions. Or they work for cooperative development labs funded by these companies. Community members act as selectors and packagers of open-source systems, or they sell consulting services, or they add proprietary applications, or (like Google) they use open-source software to provide end-use services, often very profitably, and again often very dependent on intellectual property, in the form of patents.
In all of these worldly roles, open-source community members must pay attention to the customers. They might not like it; they might prefer the purity of the FSF approach, but that is not the choice on offer. If you don't want to pay attention to customers, then either arrange to have rich parents, or learn to flip burgers. (What! You call this rare?) It won't even work to get a grant from a foundation--there is no customer more imperious.
Value of the deal
Given this reality--that most members of the open-source community cannot escape the commercial world and the needs of customers--the Microsoft-Novell deal has a lot to offer.
It creates a template that can be adopted by any Linux distributor.
On the intellectual property front, the deal is highly favorable to open source. Microsoft can promise indemnity against any patent violations contained in its software. It is much harder for any open-source company to promise the same, given the less-structured nature of its creation.
Both approaches to software will profit from the expansion of the market that always accompanies lowered transaction costs and increased interoperability, not to mention customer happiness at avoiding risks of lock-in by either type of vendor. (Who would you rather have controlling your fate--FSF President Richard Stallman or Microsoft CEO Steve Ballmer? Most people check "none of the above.")
The FSF wants to make it impossible for industry participants to use standard market-based techniques, such as licensing, to solve the problems. This will not make interoperability and intellectual property issues go away; it will just push them onto customers to solve for themselves, and the customers are already saying loudly that they do not want this. Customers want solutions, not more problems, and denying this is not "software freedom," but plain bad policy that will make open-source software platforms less attractive for enterprise customers.
It will be unfortunate if the FSF is allowed to use its control of the drafting pen in the revision of the GPL to override the interests of the other stakeholders. And if the stakeholders allow this, it will be interesting to see how they explain their acquiescence to their management, their shareholders and most of all, their customers.
Biography
James V. DeLong is special counsel for Kamlet Shepherd & Reichert.
He is also vice president and senior analyst for the Convergence Law Institute. The opinions expressed here are the author's alone.
See more CNET content tagged:
Free Software Foundation,
open-source community,
open source,
freedom,
Novell Inc.
"the safe middle ground"
http://www.os2hq.com/archives/linmemo1.htm
Re: "OS/2's kernel is under the watchful oversight of IBM, which contributes to the stability of the OS/2 development process. That is to say, maintaining compatibility with OS/2 is much easier than with Windows -- because MS has so many conflicting versions of its stuff out there -- but it may be easier to maintain such compatibility with OS/2 than with Linux as well. I'd be interested to find out what kind of compatibility issues currently exist among various Linux app development staffs, and how these will be resolved. It may be that divergent kernels make localized compatibility solutions possible, but may prevent a broader reach into the consumer market. On the other hand, that hasn't stopped MS. The OS/2 model of steady kernel-API foundations combined with a dynamic development community just seems to me to be the safe middle ground...."
<phhhhhzzzzttt>
The big point of contention? If you try to contribute code involving something that you someone else has pretty much already patented, it doesn't go into the GPLv3 project.
Note the following:
1) this does not prevent an end user from including patented stuff into the code and using it internally - just that it cannot be distributed or sold with that patented code in it.
2) No one is forcing any developer to use GPLv3 in their project... GPLv2 is still there. Use it if you like.
3) No one forces any distro maker from including (or not including) GPL v2, v3, or proprietary stuff in their products. They can mix n' match as they desire, so long as the more restricted stuff has all licensing fees respected and/or paid as required by license holders.
The rest is pure crap on the author's part. The FSF has its own stringent sense of morals, yes - but it is not a religion.
Nobody has to give a crap what RMS thinks about politics or life to use (or not use) his licensing products... otherwise we'd all be using HURD right now and not Linux.
The GPL is all about insuring maximum freedom for the end-user. If proprietary-leaning corporations get all pinched in the rectum about it because their business model isn't sufficient to profit from it, too bad; this hasn't stopped IBM, RedHat, Oracle, Sun, or a whole host of other companies from pitching in for Linux and making a profit at the same time.
As for Novell? They made their bed, they can lie in it.
As for Microsoft? Put Up or Shut Up. IMHO, they have nothing, else they would've done one of two things:
1) feed that info to SCO, and SCO would've been successful by now, instead of their current position, which is that of a man drowning in a self-made septic tank of litigation.
2) filed suit against RedHat and would've named patents.
The only reason Ballmer stops short at bluff is because he fears getting on IBM's bad side in any patent dispute (as IBM has released a ton of patents for use in Linux). See, MSFT fears that whatever patents they think Linux abuts into may be one that IBM has had for years prior, and Ballmer is scared stiff of coming down on the wrong side of such a squabble (while IBM would likely be more than happy to stick it to MSFT once and for all, considering history).
The rest is just sheer ignorance and not a little disingenuity on the author's part.
/P
The FSF didn't come to prominence only through drafting the GPL. They own one of the largest bodies of useful free software, and have the right to license it as they choose. It is blatantly hypocritical to complain that "the FSF is allowed to use its control of the drafting pen in the revision of the GPL to override the interests of the other stakeholders." When's the last time Microsoft licensed its software to appeal to other stakeholders?
***
The FSF is often equated to a religion, and the comparison is apt. It regards proprietary software as immoral
***
This part is incorrect. Morality has nothing to do with the stance taken by the FSF.
***
patents as the work of the devil
***
Again incorrect. The FSF does not regard patents as the work of the devil, they just believe that copyright is all of the protection that software needs. Heck, Bill Gates is on record as saying the same thing.
***
digital rights management as an unacceptable infringement on freedom
***
Well yes. I don't know ANYONE on the "consumption" side who is in favor of DRM. A lot of the artists aren't in favor of DRM either.
***
and markets for intellectual creations as undesirable or irrelevant.
***
Totally incorrect. The FSF is in favor of a strong copyright law - and copyright is what affects software.
***
They want interoperability of open-source and proprietary programs--the ability to run both types of program in heterogeneous environments--without being required to perform the integrations for themselves.
***
In that case they should talk to Microsoft. Microsoft's apparent inability to produce product that uses standards properly is legendary in the industry.
I could go on,but I'll limit myself to one more point. Mr. DeLong mentions his association with the Progress and Freedom Foundation. He does not mention that Microsoft is a donor to the Foundation. Whether Microsoft had any input on the article or not is of no importance, the fact that he has a relation to Microsoft is however pertinent. Since Mr. DeLong did not mention the relationship, I believe he was trying to hide it, and therefore that this article should be removed from CNET.
Urban Terrorist
Biography:
The Urban Terrorist is a programmer, sales representative, and musician. He uses Open Source programs for Web Surfing and Content Authoring because he finds that they are more reliable, and give better value than most of their closed source counterparts.
While it is possible that Microsoft had no influence on the article