Howdy, I'm a CPython developer by trade, but I've been watching IronPython evolve and have recently started playing around with 2.6rc1 for a number of smaller projects [1][2].
While evaluating IronPython, I've run across a couple of issues [3] that
I think I'm capable of helping to fix but I notice that there's this
note in the FAQ regarding external contributions:
Does the IronPython Team accept back source contributions into the
IronPython and DLR codebases?
I'm curious as to whether this is still the case, FePy looks somewhat...
sleepy/out-of-date. How does the CodePlex Foundation fit into this? Does
it change things?
I know for some other projects (Mono comes to mind) they require an
MIT/X11 to commit to core and some paperwork with Novell (presumably so
they have their bases covered for commercializing the IP). Is this
something that might help open up IronPython to community contributions?
Furthermore, to the tune of the "development cycle" it's quite unclear
from the site how long the "release candidate" cycle is going to be
before the final version of 2.6.0 is released; how long are these cycles
typically?
I'm really excited about the prospects of incorporating IronPython 2.6
into more of my projects (particularly on top of Mono), but I'd like to
able to contribute back where I can to push the project forward.
Appreciate any feedback/thoughts :)
Cheers,
-R. Tyler Ballance
[1] http://github.com/rtyler/IronWatin
[2]
http://unethicalblogger.com/posts/2009/10/crazysnake_ironpython_and_java_just_monkeying_around
[3] http://ironpython.codeplex.com/WorkItem/View.aspx?WorkItemId=24533
pgpuecesVa2y4.pgp
Description: PGP signature
_______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
