[IronPython] The elephant in the room: source control for IronPython
Miguel de Icaza
miguel at novell.com
Fri Oct 29 02:31:48 CEST 2010
We could, for example, drop the source control from CodePlex and just
> use the IronRuby github repo - it's already set up and we could start
> developing tomorrow
This is my preference.
The GitHub guys have great support for "Organizations", we use that for
Mono, and it has nice administration tools for Organizations, allows
administrations per module and have lots of hooks and web tools to explore,
manage and collaborate as well as providing some 60 different popular hooks
for services that can be offered.
Moving to Git seems like a no brainer to me: we only have to move IronPython
there. If we were to pick another of the open source source code
management systems we would be moving both Ruby and Python away.
If the concern is the UI for checking code out for Git, there is a
transparent bridge that exposes the tree to Subversion which has good
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ironpython-users