Does the IronPython Team accept back source contributions into the IronPython and DLR codebases?
The answer is currently no. Prior to the release of IronPython 1.0, there was a huge amount of legal red tape in this area that made it highly infeasible. While IronRuby has since established a precedent for taking back contributions, there are a few key benefits to limiting IronPython checkins to Microsoft employees. The most important being that some of our users have stated that they would be unable to install IronPython if it contained non-Microsoft intellectual property due to their employers’ policies. We’d like to enable as many people as possible to utilize IronPython, and feel this is a bit more important than taking back contributions. On a similar note, other teams at Microsoft are currently using IronPython to assist in building their products. They too would likely have to stop using it should we start taking back contributions. This said, there is indeed a non-Microsoft distribution of IronPython, IronPython Community Edition, which will happily accept back any contributi
