Microsoft Hands IronPython, IronRuby to Open Source Community
Microsoft has turned over the leadership of its IronPython and IronRuby dynamic language projects to the open source community. Jim Hugunin, who led IronPython, leaves for Google.
Microsoft has decided to spin out its dynamic language implementations, IronRuby and IronPython, and put them into the hands of the open source community at large.In an Oct. 21 blog post, Jason Zander, corporate vice president for the Visual Studio team in the Developer Division at Microsoft, said, Microsoft has " released several versions of both language environments (IronPython releases and IronRuby releases), and all of the source code has been released under open source licenses (recently moved to Apache License V2.0)." However, added Zander:
Today we are announcing new leadership for the Iron projects and a development model that will enable the broader community to contribute to their development:
- The community can now make source contributions to any component of IronPython and IronRuby.
- For both IronPython and IronRuby, we've made changes to the CodePlex projects to allow community members to make contributions without Microsoft's involvement or sponsorship by a Microsoft employee.
- We've already released the IronPython Tools for Visual Studio that we developed under Apache 2.0. We've received great early feedback on the IronPython language service for Visual Studio. Today we are releasing the prototype code for IronRuby Tools for Visual Studio, and we expect similar feedback for IronRuby tools as well. Releasing these components under the Apache 2.0 license allows for community members to use the functionality and also contribute to the IronPython and IronRuby language services.
- We have done a lot of ground work for the next version of IronPython v2.7 and IronRuby v1.9.
- We have fixed a lot of infrastructure so that the community should be able to regression test all language updates using our tests.
- We have enabled a full release work flow to produce builds and releases straight from the CodePlex projects. Previously, these could only easily be done from our own source depots.
"Microsoft's decision to abandon its investment in IronPython was a catalyst but not the cause of my leaving the company. While most of you know that I haven't been directly involved in IronPython for quite some time, the decision still provided a spur to cause me to reflect on my time at the company and realize that it was time to explore other career options. There would be something emotionally satisfying about leaving Microsoft in a fit of rage - preferably involving the illegal deployment of an emergency escape slide. However, I leave feeling respect for the many great people and products produced here. I will suffer some pain when I have to write code in Java now that I've learned to love the elegance of C#. I will suffer some frustrations when I have to use Google Docs instead of the finely polished UI in Microsoft Office. More than anything, I will always value the chance that I had to work with and learn valuable lessons from some truly great people."Hugunin's move indicates another key Microsoft engineer going to Google, including Brad Abrams and Chris Wilson. And Hugunin says he relishes being able to work on open source efforts in small teams. He contrasts what he expects to do at Google versus his efforts at Microsoft. Hugunin said: