Linked by Thom Holwerda on Fri 13th Jun 2008 18:09 UTC, submitted by wakeupneo
"It's official: Microsoft will not accept any external code contributions to its planned Dynamic Language Runtime, which will run Microsoft's new scripting languages for the web and Silverlight content on .NET. Microsoft will, though, continue to accept source-code contributions to its slowly emerging implementation of Ruby for .NET, IronRuby. Contributions are helping to build IronRuby and shepherd the language towards the first-full release. The Register has learned, meanwhile, that Microsoft will start accepting external contributions to its other great scripting language project, putting Python on .NET - IronPython - in the "near future". The promise by Microsoft IronRuby lead John Lam comes nearly a year after the topic was first raised. The reason Microsoft decided to leave the DLR closed, despite taking contributions to the languages that will run inside it, is to protect itself from unwanted licenses and IP claims."
Thread beginning with comment 318435
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Member since:2005-07-06
The general problem MS has with accepting outside code is that they don't really know where it comes from.
Strange. No one else has this problem. That's what open source development is all about, and there are lots of established procedures for this sort of thing.
If they had to yank the DLR, that would be another story.
I can assure you that it has nothing to do with that ;-).
Member since:2006-02-05
Strange. No one else has this problem. That's what open source development is all about, and there are lots of established procedures for this sort of thing.
There are no established procedures, there are common practices. Some projects just dont pay attention at all to it, others require an eula style disclaimer, others actually require your signature on a contract saying you actually own the code and are allowed to contribute it.
As I said before, microsoft is in the unique position of being the largest target of litigation in the industry, it is not that difficult to understand their position on this when you think about it.
I can assure you that it has nothing to do with that ;-).
Well, thats what John Lam said. What do you think the reason is, and what qualifications do you have that make you more of an authority on this then him?
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2006-02-05
I just finished listening to a DotNetRocks with John Lam, and he sort of explained this.
The general problem MS has with accepting outside code is that they don't really know where it comes from. Since they are the biggest litigation target in the industry (everyone remember Eolas?), their lawyers do not want core technology that is basically undefendable in court.
The reason IronRuby and IronPython are able to accept pulls from the community is that they are not core technology, will never ship with windows, and only be available as either an optional download or as a component in another program (for example, there is talks of making IRuby the recommended scripting language for dotnet, finally killing the abomination that is vba once and for all)
If MS is ever in a position where it has to yank IRuby or IPython from its sites and products that will suck, but it wont be disastrous. If they had to yank the DLR, that would be another story.