[Ironruby-core] Contributing?

Michael Letterle michael.letterle at gmail.com
Fri Oct 22 23:02:19 EDT 2010

Along the lines of IronRuby on mono, a small change was required for
now since Mono doesn't implement one of the newer Monitor.TryEnter
overloads, see my branch here:

compiles with:

xbuild /property:TreatWarningsAsErrors=false
/property:DefineConstants="DEBUG MONO" Ruby.csproj

Working on getting IronRuby.Console compiled now... already ran into a
casing issue >.<

On Fri, Oct 22, 2010 at 9:02 PM, Jonathan Allen <grauenwolf at gmail.com> wrote:
> I would caution you against moving too far away from Microsoft Technology,
> lest you alienate Windows developers.
> 1. If this project is going to be owned by Mono, then it would be reasonable
> to move to GitHub. But to drop CodePlex just because you feel like being
> stubborn isn't.
> 3. One of the biggest barriers for Windows developers who want to contribute
> to Mono is the project/build system. When looking at it for the first time
> it is really hard to just figure out where to start. And they certainly
> don't want to go back to editing source files with notepad. So while being
> able to build without Visual Studio is important, be careful not to remove
> the VS/MSBuild option.
> Jonathan Allen
> On Fri, Oct 22, 2010 at 5:10 PM, Mike Moore <blowmage at gmail.com> wrote:
>> With a brave new world ahead for IronRuby, what do you all think about the
>> following ideas?
>> 1) Move to GitHub - I won't likely contribute if I have to use CodePlex.
>> And I'd like to contribute. Can we do like the rest of Mono and make GitHub
>> the central repository and source of all truth? Please?
>> 2) Detach IronPython - Looking through the code, it seems that IronPython
>> is in the same repo. I'm sure this is a holdover of how Microsoft had
>> everything organized. And I'm sure it made sense then, but I don't think it
>> makes sense now. I'd like to work on IronRuby, and I honestly don't care
>> about having to check IronPython. Now that the DLR API is fixed, and there
>> is no longer one Microsoft group in charge of both projects, can we move
>> these into separate repos?
>> 3) Detach from Visual Studio - I'm not on Windows, and I won't be using
>> Visual Studio. I'd prefer everything to build with rake tasks on Windows and
>> Mono. I assume things are the way they are right now because of Microsoft's
>> build process. And right now it does not seem possible for me to build
>> without Visual Studio. What about devs who are using MonoDevelop? Or any of
>> the more powerful text editors? I'm convinced this is a major hurdle to
>> getting many of the other Rubyist language implementors involved. Assuming I
>> am not alone on this, is it possible we can make this project reflect the
>> realities of the majority of folks that would like to contribute?
>> 4) Remove ancillary projects into their own repos - IronRuby.Rack should
>> live in its own repo, IMO. So should the Visual Studio tools. This is
>> similar to separating IronPython into its own repo, but it needs to go
>> further. Are there any reasons this should not be done?
>> What else do you guys think needs to change now that IronRuby is free from
>> Microsoft's processes?
>> _______________________________________________
>> Ironruby-core mailing list
>> Ironruby-core at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/ironruby-core
> --
> Jonathan Allen
> 619-933-8527
> _______________________________________________
> Ironruby-core mailing list
> Ironruby-core at rubyforge.org
> http://rubyforge.org/mailman/listinfo/ironruby-core

Michael Letterle
IronRuby MVP

More information about the Ironruby-core mailing list