Open source seeks to eat its young (again)
At Hogwarts, only the Slytherins seem to care whether you're a pure blood or a mudblood. In the open-source community, too, some open-source advocates have never seen a corporate open-source contribution that couldn't have gone farther or been done with nobler purposes.
Alas! It wasn't open enough, at least, not for Chris Messina, who promptly criticized the move as "open washing, applying the tastes-great, less-filling label, while doing everything they can to maintain their control and dominance in a given area--further cementing the historic distinction between 'free' and 'open.'"
Messina raises some good points in his post, but what he doesn't do is come to grips with Adobe's news: it did exactly what it said it did, which was to open source code under an OSI-approved license (MPL 1.1). Messina may believe Adobe did so with devious intent, but can we at least wait for the ink to dry on the press release before hounding Adobe for its move?
Similarly, the response to Microsoft's open-sourcing of a few Linux device drivers is puzzling. Red Hat said "congratulations" out of one side of its mouth while pestering Microsoft to outdo IBM, HP, and other companies that heavily use open source in a refusal to future patent claims against any open-source developers or users.
Roy Schestowitz, perhaps predictably, argued that Microsoft only did it because Linux can't be ignored. Indeed, the argument is now circulating that Microsoft was legally bound to release the device drivers as open source. It didn't really want to! It's a sneaky company that only contributes under duress!
Sigh. In open source, no good deed goes unpunished. There is no greater enemy to open source than itself.
A more charitable view on Adobe, Microsoft, and other companies that are experimenting with open source is that they are making progress, learning to use open source to suit various business and technical needs. Microsoft says that it's learning to use open source to lower sales and marketing costs in new markets, but also to make its software development process more efficient.
Perhaps it's lying, but why start from that premise?
I think it's fair to say that Microsoft, in particular, has made significant progress in its understanding of and appreciation for open source these past few years. Yes, as Novell's leading Linux developer Greg Kroah-Hartman articulates, "companies [like Microsoft] are big" with conflicting agendas, which can make them seem insincere in their open-source efforts.
But why would anyone expect Microsoft and its ilk to continue to court a community that ridicules and second-guesses its every attempt at perestroika? I know from conversations with several companies that they're actually scared to engage the open-source community because the responses have been so intemperate and ideological.
I'm convinced that this element of the open-source community, vocal and sometimes vicious, is a minority. I'm equally convinced that we'd better off if this enemy within would spend more time analyzing its own behavior rather than shouting down the supposed "mudbloods" of open source.
Follow me on Twitter @mjasay.
Matt Asay brings a decade of in-the-trenches open-source business and legal experience to The Open Road, with an emphasis on emerging open-source business strategies and opportunities. Matt is vice president of business development at Alfresco, a company that develops open-source software for content management. He is a member of the CNET Blog Network and is not an employee of CNET. Disclosure. You can follow Matt on Twitter @mjasay. 




In the case of the Adobe example, they were giving a way to create more content using Flash. Adobe doesn't have a fully functional Flash plugin for Linux yet but they want to create ways to give developers more ability to create Flash content. Where's the guarantee the developers will even be able to see the content they create?
In the case of the 20k lines of code for three drivers by Microsoft, why wouldn't they just add those drivers into Hyper-V? Even better, why wouldn't they build the drivers with help from the community and use a newer version of the GPL? It would go a lot farther with the community to ask for help and the developers might actually learn something (20k lines for three drivers in Linux is a huge amount).
MS also can't use a newer version of the GPL for Linux drivers. Neither can anyone else. The Linux kernel is GPLv2 only so any contributions must be GPLv2. I agree it's something of a code-dump but there may have been technical limitations such as required knowledge of the hypervisor which is not available outside of MS.
Because we haven't been in a coma for the past 25 years?
I'm not suggesting that the community shouldn't accept code from MS or Adobe -- on that score, you and I are in agreement; they may be strange bedfellows but if their contribution allows for greater interoperability, that's a good thing.
However, suggesting that we should just assume benign motives from the company that sent the feds after Sklyarov and the one that recently sued TomTom is suggesting that we should close our eyes and plug our ears.
I'm not saying code from Adobe and MS can't be used to positive ends. I'm just saying that pretending they're doing it for any reason other than to protect their existing market share is absurd.
Agreed with the parent post - though I can simply shorten my version of it to this: Past and Present History.
Maybe because it needs to pay salary to the engineers who develop and support it?
And Adobe doesn't even control the PDF specification. It's now in the hands of ISO, you know, that international standards thingee. Adobe is one company in one country that contributes to the ISO 32000 standard. Adobe also released the essential patents that read on PDF as RAND-RF at he same time... so don't suggest patent blocking.
And by the way, the country votes for the approval of this standard was unanimous.
So, if giving up control of PDF, and building tools that follow an international standard that many others also follow is closed, I'd suggest reading a good dictionary.
davemc
@wshwe: A point of a company is to make money. It is not to cator to cheapskates like yourself who want everything for free.
@Thad boyd and Random_Walk: Why do you care what their motivations or history are? If you want to live in some imaginary world where everything is free and people sing kumbaya. Good luck.
On the same note, you can't really blame open-sourcers from being suspicious. Microsoft has been trying to stamp us out for years. I consider myself to be a very pragmatic open source advocate, but I don't trust Microsoft. They built their business on theft and the assimilation of their opponents. So am I just being paranoid? Or realistic? Neither? I don't know.
It's like an episode of Tom and Jerry where Tom tries to call a truce and offers Jerry a piece of cheese. When Jerry accepts, a giant anvil falls out of the sky and lands on his head. Can you blame us for twitching?
@thad boyd - Yup. MS act like ejits in the past, and expect is to believe they've come over all cuddly over night ? Yeah, right. And *then* it turns out it wasn't out of the goodness of their heart, or even for commercial reasons, but because their lawyers made them ? Meh !
Per The Register ( http://www.theregister.co.uk/2009/07/23/microsoft_hyperv_gpl_violation/ ), MS released Hyper-V code under the GPL because...it was a GPL violation otherwise.
Oh, those open-source zealots, always eating their young by assuming MS might have an ulterior motive for embracing a license it has previously compared to cancer. Clearly a bunch of idiots with axes to grind, formulating conspiracy theories that couldn't possibly have any basis in reality.
- by nbahn August 19, 2009 4:06 PM PDT
- It's not surprising that there would be such trenchant suspicion and criticism of Microsoft. Who can forget the bad old days when it acted both immorally and illegally with impunity?
- Like this Reply to this comment
-
(19 Comments)