While I am a little bummed that Microsoft is cutting funding for these Iron* projects, I do think it's great news that the ball is now in our court.<div><br></div><div>What's more concerning is the fact that Microsoft, as of right now, has little incentive (that I'm aware of) to extend the DLR.</div>
<div><br></div><div>-Charles<br><br></div><div><br><div class="gmail_quote">On Thu, Oct 21, 2010 at 6:09 PM, Jeff Hardy <span dir="ltr"><<a href="mailto:jdhardy@gmail.com">jdhardy@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
As Dino recently posted, this is the last release of IronPython by<br>
Microsoft. As of today, myself, Michael Foord, Jimmy Schementi, and<br>
Miguel de Icaza are the coordinators for the IronPython project (Jimmy<br>
and Miguel will also handle IronRuby). More information can be found<br>
from Jason Zander:<br>
<a href="http://blogs.msdn.com/b/jasonz/archive/2010/10/21/new-components-and-contributors-for-ironpython-and-ironruby.aspx" target="_blank">http://blogs.msdn.com/b/jasonz/archive/2010/10/21/new-components-and-contributors-for-ironpython-and-ironruby.aspx</a>.<br>
Do note that Zander doesn't actually come out and *say* that Microsoft<br>
is no longer funding IronPython/IronRuby, but that's what has<br>
happened. Any future participation from MS employees will be on an<br>
unofficial, spare-time basis.<br>
<br>
All that said, I hope this isn't the end of IronPython. There's a good<br>
community here, and I think we can do just as good a job as Microsoft<br>
did. You can now contribute patches to IronPython, but that means you<br>
will have to if you want the it to flourish. A good Open Source<br>
community requires a core of regular contributors, but also requires a<br>
mass of occasional ones that are just scratching their particular<br>
itches.<br>
<br>
>From here, my goal is to get IronPython 2.7 final out the door in a<br>
timely manner. Let's leave discussions about things like source<br>
control or external libraries aside for a bit and get a solid release<br>
-- then we can start those discussions. I fear that starting a major<br>
overhaul will kill any momentum we have and cause the 2.7 release to<br>
be unacceptably delayed.<br>
<br>
I wouldn't have signed up to do this if I thought IronPython didn't<br>
have a future.<br>
<br>
- Jeff<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.ironpython.com">Users@lists.ironpython.com</a><br>
<a href="http://lists.ironpython.com/listinfo.cgi/users-ironpython.com" target="_blank">http://lists.ironpython.com/listinfo.cgi/users-ironpython.com</a><br>
</blockquote></div><br></div>