Open-source discrimination
There is an ugly feeling growing against Microsoft in its attempts to have a few of its shared-source licenses certified as OSI (Open Source Initiative)-approved. The general sentiment is that OSI approval is for everyone except Microsoft.
I compete with Microsoft. My livelihood depends on beating Microsoft. I have worked for two companies that have been run over by Microsoft and its leveraging of monopoly power. I'm at least as familiar with Microsoft's legal and business tactics as most people, and probably more so than most. I've been on the losing end of Microsoft's monopoly power more than once.
But I don't believe in discrimination. Not even of the "bad guys."
Pamela Jones of Groklaw, whose opinion I value and with whom I normally concur, berated me for daring to suggest that we should welcome Microsoft's participation in open source:
Most of us do *not* want Microsoft to participate. I would like to personally barricade Microsoft out, until it alters its negative, rapacious and hostile behavior toward the GPL and FOSS. And so should you.
I've heard similar comments from others in the industry. But last time I checked, the Open Source Definition prohibits discrimination. It certainly doesn't encourage it. Here's the language and the OSI's rationale:
The license must not discriminate against any person or group of persons.
Rationale: In order to get the maximum benefit from the process, the maximum diversity of persons and groups should be equally eligible to contribute to open sources. Therefore, we forbid any open-source license from locking anybody out of the process.
This speaks of licenses, of course, but why should the process for submitting licenses be discriminatory while the licenses, themselves, are not?
Open-source licensing is about the license. This is one reason that Linus Torvalds chastised the Free Software Foundation over GPLv3: he felt that the FSF was making licensing political, while he liked GPLv2 because:
The beauty of the GPLv2 is exactly that it's a "tit for tat" license, and you can use it without having to drink the Kool-Aid.
In short, you don't have to care whether it's a Microsoft license or an FSF license or an Oscar the Grouch license: the license speaks for itself.
Is there a chance that Microsoft will use its OSI accreditation to the detriment of open source? Sure. But this, however, does not excuse anyone in discriminating against Microsoft, or any other person or organization, that wants to participate in the open-source licensing and development process.
Sometimes we fetish over labels (I'm very guilty of this). There are risks in removing labels, of course, but far greater damage comes from discriminating against labels, rather than people.
I'm not naive when it comes to Microsoft, but I'm also not vindictive. Microsoft should be allowed to participate the same way any other organization does. Period. Open-source licensing does not look to motives, whether IBM's, Microsoft's, Richard Stallman's or Linus Torvalds'.
Matt Asay is general manager of the Americas and vice president of business development at Alfresco, and has nearly a decade of operational experience with commercial open source and regularly speaks and publishes on open-source business strategy. He is a member of the CNET Blog Network and is not an employee of CNET. Disclosure.
- Topics:
-
Microsoft,
-
Open source
- Bookmark:
- Digg
- Del.icio.us







Link to judges discussion of MS's behavior:
http://www.albion.com/microsoft/findings-33.html
We should not emulate MS's anti competitive, dishonest (gee- this is just what our customers want us to do- they really do not like choice in the marketplace) behavior. Of course they will try to devise a means to stop open source using ANY method they think might work. But, if they want to open source some code, let them. Lets not sink to their level. Consider that, in my opinion, their behavior has alienated many consumers, and that the bad will toward them (created by their behavior) has a good chance of becoming a significant factor in the future deterioration of their monopoly. Lets not make the world an uglier place, do not emulate Microsoft.
Acts like this really pushes me away from Open Source...
Let Microsoft make one single REAL contribution to interoperability, JUST ONE, like openly publishing the API and protocols of their sekrit NTFS or network services or AD.
Dealing with Microsoft, except on the most superficial of levels, is like dealing with the beast - no good will ever come of it.
And for everyone that says 'it's just an operating system blah blah blah' (Like Stupid Steve), not an ideology, let me state right off that IT IS about ideology.
FOSS is about fair sharing and Microsoft is about profit, control and NO SHARING!
So just what kind of deal can you expect to make with Microsoft?
CD 'Bar' Baric
This applies to downstream developers and users, but what about the original owner? IANAL, but after the way MS used the Novell deal to make threats about patents, I do not trust them to not seek ways to threaten developers, and even users.
For instance, if a MS-PL app only works with one of their proprietary apps, does modification of the former to make it work with other FOSS apps give them the grounds for going to court? This kind of scenario has already happened (I don't remember if it was MS or not).
Granting OSI approval to MS licenses cannot be done purely on the merits of the license. Besides, there are plenty of OSI approved licenses, so I am really confused and suspicious as to why they won't use one of those.
Because of its sheer size and bank account, Microsoft can act as the proverbial "bull in the china shop" with virtual impunity. Suppose Microsoft violated a license and you wanted to take them to court. They can time you up until the cows come home and you go bankrupt and have to drop the case. For them, it's just a cost of doing business (and a pretty minor one at that). Microsoft continually demonstrates that it only wants to play by its own rules (witness OOXML, e.g.).