Slashdot Mirror
Microsoft Seeks Open Source Certification
eldavojohn writes "Microsoft is applying for OSI certification for its Shared Source Initiative. The move is described in a blog post by an MS OSS lab worker: 'Today, we reached another milestone with the decision to submit our open licenses to the OSI approval process, which, if the licenses are approved, should give the community additional confidence that the code we're sharing is truly Open Source. I believe that the same voices that have been calling for Microsoft products to better interoperate with open source products would voice their approval should the Open Source Initiative itself open up to more of the IT industry.' According to PC World, reaction from the community has been mostly positive."
If MS is interested in becoming part of the OSS scene and playing nice with everyone else, why can't they use an existing license? What makes their new licenses better than the established ones?
I think this is what they need to address in order to be trusted because it looks to me like the only reasons they would need to create a new license are to try to get away with something the existing licenses wouldn't allow or (more likely) to try to cast a shadow of doubt on the appropriateness and safety of the licenses everyone else in the community uses.
I'd rather be lucky than good.
the same voices that have been calling for Microsoft products to better interoperate with open source products would voice their approval should the Open Source Initiative itself open up to more of the IT industry.
What a pile of M$. The only barrier to products that interoperate better is them. Everyone else has bent over backwards for years, only to treated as a pawn in the quest for M$ dominance of everything. M$ is the only organization using such sleazy language. The goal is not some kind of imperfect interoperation, it's the use of real standards, the end of M$'s silly games and the beginning of real freedom. Without the four freedoms, everything M$ does is just another game.
If M$ sends the OSI software freedom, great. If they don't and the OSI certify it, the OSI will not have raised M$ in anyone's opinion, they will have disgraced themselves and further diluted the terms "free" and "open". We will all be able to judge for ourselves, but I don't expect anything useful from a company that's rabidly threatening everyone with patents.
At this point, M$ has very little of value to offer and the best thing they can do is cease hostilities and start to repair the damage they have done. It would take the community a decade to fix the mess Windoze and Intel BIOS are. It will take even longer to undo the DMCA, software patents and other evil stuff they have promoted. The market itself is doing a better job of fixing the problem by ignoring them.
Friends don't help friends install M$ junk.
If not, I don't see any reason for you to apologize. Even if you are, it's not like you're duping an article within a couple of days or less. Because I've bitched about dupes many times before. Many times. Which implies that I hold the editors to a high standard. If I can't be a standard candle for them when I submit stories, how can I expect them to hold these artificially high standards I force them to?
Too many times, I've said that if they just went to Google or Google news and typed "site:slashdot.org Microsoft OSI" they would find the dupe from a few days ago about a story with basically the same keywords. I mean, you could even build a link on the admin page for them to click and do that search.
I apologized because I submitted before taking my own advice, leading to what I considered a dupe.
I apologized for being a hypocrite. It's a basic idea of not contradicting yourself that was ingrained into me when I was a child & seems to be lost these days. You act like you would want someone else to act (the ultimate maxim) and it's clear to me that everyone hates a dupe so I apologize.
My work here is dung.
First they ignore you, then they ridicule you, then they fight you, then they pretend to join you and stab you in the back at the first opportunity. Never trust Microsoft.
Gandhi (somewhat adapted)
Loose lips lose spit.
This is just a PR stunt so that Microsoft can reap the benefit of open sources good reputation. If they wore genuinly interested in working with the community all they had to do would be to release current specs for their various document formats and network protocols. I really hope the OSI take a long hard gander and turn every single stone before agreeing to anything. Microsofts history tells you to watch your back. Microsofts shared source license should not in any way be let in without complete abolishment of the windows platform clause. OSS licenses should not tell you what platform you can use the code on.
HTTP/1.1 400
the farmer found the snake freezing in the winter
the snake said 'please help me out, pick me up in your coat and i wont freeze to death'
the farmer said 'but you are a snake, you will kill me...'
the snake said 'no, i promise i wont. please help me'
so the farmer picks up the snake and puts him in his coat. after a while, the snake warms up.
his natural instincts take over. the snake bites him.
as the farmer lays dying, he says 'what on earth has happened. you rascal!'
the snake said 'you knew i was a snake when you picked me up!'
I believe that the same voices that have been calling for Microsoft products to better interoperate with open source products would voice their approval should the Open Source Initiative itself open up to more of the IT industry.
I think they'd voice their approval much quicker should Microsoft make a concerted effort to actually interoperate better with other products, open source or not. It's interoperation that is really the key... for example: back in the early '80s the yet-to-be-named open source community embraced UNIX not because it was open source - in fact at the time it wasn't - but because it was designed to be easy to interoperate with at every level.
It's not good enough to provide open source components that only actually work on top of your API, or to provide libraries that allow people to talk to your protocols through the cut-out of your system software, you need to open the black box and commit to supporting documented and non-proprietary wire protocols and file formats.
Otherwise what you've got is better described as an "open pit-trap".