ryan.riley at panesofglass.org
Sat Oct 23 02:50:45 EDT 2010
Jim, Jimmy, Tomas, and Miguel:
Shri used to offer pair programming sessions to people interested in helping out with the project. I know at least a few participated, and I found it really helpful. Is there any chance of starting this up again? I don't mean for you to necessarily be the ones to do it, but you might know some food candidates. This might help onboard people like Mike who are interested but unsure where to begin.
Sent from my iPhone
On Oct 22, 2010, at 8:26 PM, Mike Moore <blowmage at gmail.com> wrote:
> On Fri, Oct 22, 2010 at 6:59 PM, Tomas Matousek <Tomas.Matousek at microsoft.com> wrote:
> 2) It is not a holdover. It makes a lot of sense actually for at least the following reasons:
> a) Some IronRuby tests test interop between these languages. So there is a direct dependency. When you debug issues in language interop you need to have IronPython source code as well to step thru and make sense of the interactions.
> I don't understand why the code needs to exist within the same git repo for this then. Can you not have a Visual Studio solution that includes multiple projects with their own repository? Can't you have your automated build system pull both the IronRuby and IronPython projects to run the integration tests?
> b) DLR has two parts – the “inner ring” that shipped in .NET Framework 4.0 and the “outer ring”, which hasn’t shipped. Although the outer ring is pretty stable there are still many improvements that can/should be done. Obviously when you change the DLR you should run tests for both languages so that you don’t break anything. Thus IronPython’s test suite in the repo is handy. Also, if you change public API in the outer ring you might need to change both IronPython and IronRuby. All of this could be done in stages across different repos and even source control systems, but that’s obviously much more complicated than having it just work.
> I assumed the DLR was fixed. If that is not the case then shouldn't the DLR should be its own separate git repo as well?
> Is size of the repo really an issue? If not, what is?
> No, its not the size of the repo, rather the amount of tangental code. As someone who hasn't looked at the code for well over a year, I am struck by the amount of orthogonal concerns that are front and center. I find it too busy and off-putting as a developer looking to become familiar with the code or make a small contribution. I don't doubt there aren't reasons it is the way it is, just that it can be better if you want to really open the floodgates of contributions.
> Ironruby-core mailing list
> Ironruby-core at rubyforge.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ironruby-core