[IronPython] The Future of IronPython
charles.c.strahan at gmail.com
Thu Oct 21 17:22:53 PDT 2010
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.
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.
On Thu, Oct 21, 2010 at 6:09 PM, Jeff Hardy <jdhardy at gmail.com> wrote:
> As Dino recently posted, this is the last release of IronPython by
> Microsoft. As of today, myself, Michael Foord, Jimmy Schementi, and
> Miguel de Icaza are the coordinators for the IronPython project (Jimmy
> and Miguel will also handle IronRuby). More information can be found
> from Jason Zander:
> Do note that Zander doesn't actually come out and *say* that Microsoft
> is no longer funding IronPython/IronRuby, but that's what has
> happened. Any future participation from MS employees will be on an
> unofficial, spare-time basis.
> All that said, I hope this isn't the end of IronPython. There's a good
> community here, and I think we can do just as good a job as Microsoft
> did. You can now contribute patches to IronPython, but that means you
> will have to if you want the it to flourish. A good Open Source
> community requires a core of regular contributors, but also requires a
> mass of occasional ones that are just scratching their particular
> From here, my goal is to get IronPython 2.7 final out the door in a
> timely manner. Let's leave discussions about things like source
> control or external libraries aside for a bit and get a solid release
> -- then we can start those discussions. I fear that starting a major
> overhaul will kill any momentum we have and cause the 2.7 release to
> be unacceptably delayed.
> I wouldn't have signed up to do this if I thought IronPython didn't
> have a future.
> - Jeff
> Users mailing list
> Users at lists.ironpython.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Users