How to contrubute to IronRuby?

Hi all,
someone can resume me how to contribute to IronRuby project?
where, and how, send patches? and if there’s a todo list…

I’ve already read the wiki page
http://ironruby.rubyforge.org/wiki/wiki.pl?ContributingToIronRuby
but I’m a bit confused and I need a more detailed guide…

Here’s how I understand it:

Follow the instructions on that wiki page to sign the contributor
agreement.

You’re already at rubyforge, everything is there:
Bug List:
http://rubyforge.org/tracker/?atid=16798&group_id=4359&func=browse

The ToDo list is empty, but pretty much consists of “Make it work”

The project page: http://rubyforge.org/projects/ironruby/

also has links to a patch submission tracker.

But to be honest I don’t think any offical “contribution” policies
have been laid out but the core team.

On Feb 13, 2008 4:31 AM, 1115201006 [email protected] wrote:


Ironruby-core mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/ironruby-core


Michael L.
[Polymath Programmer]
http://michaeldotnet.blogspot.com

Read John L.s blog http://www.iunknown.com/2008/02/ironruby-sun-an.html

Nice news about getting debugging support for IronRuby more close to
completion: “We have debugging and stack backtraces working.”

I was wondering if this means that IronRuby 1.0 release can be expected
to ship with a plug-in or similar to VisualStudio to enable such
debugging with the IDE?

Robert B.
Software architect
Napa Ltd
Tammasaarenkatu 3, Helsinki FI-00180
P.O.Box 470, Helsinki FI-00181

Tel. +358 9 22 813 1
Direct. +358 9 22 813 611
GSM +358 45 11 456 02
Fax. +358 9 22 813 800

Email: [email protected]
www.napa.fi

John L. (DLR) wrote:

Robert B.:

Keep in mind that this in no way is a complete language service. As the
good folks over at Sapphire in Steel will tell you, there’s a ton more
work to do than just getting syntax coloring and debugging working (in
their case it was actual work since they had to write a debugger and a
scanner and parser).

I can confirm that :wink:

It’s been our experience that many people hugely underestimate the work
required to create a first class IDE for Visual Studio. It’s a constant
frustration to us that people usually refer to our IDE, Ruby in Steel,
as a ‘plugin’ (which makes it sound trivial) whereas in actual fact it
is a ‘package’ which is a completely different beast from a plugin - a
package is really deep integrated with VS, just like the ‘standard’
languages such as C# and VB.NET. I can tell you that creating this kind
of IDE is a massive undertaking.

We are just about to look at the IronRuby debugger and we aim to
integrate a visual IronRuby debugger into an alpha or beta release of
Ruby In Steel for IronRuby asap. In the meantime, we’ll be releasing the
alpha of our IronRuby IDE to our customers in the next week or two -
this will have the form designer but not yet the debugger. See here:
http://www.sapphiresteel.com/IronRuby-Developments-the-Visual

best wishes
Huw

SapphireSteel Software
Ruby and Rails In Visual Studio
http://www.sapphiresteel.com

Huw C.:

We are just about to look at the IronRuby debugger and we aim to
integrate a visual IronRuby debugger into an alpha or beta release of
Ruby In Steel for IronRuby asap. In the meantime, we’ll be releasing
the alpha of our IronRuby IDE to our customers in the next week or two

The good news is that you should just be able to reuse our work to get
debugging support working. AFAIK there was almost no work required to
enable debugging in VS once we got IronRuby + DLR generating the correct
PDBs.

Thanks,
-John

Robert B.:

I was wondering if this means that IronRuby 1.0 release can be expected
to ship with a plug-in or similar to VisualStudio to enable such
debugging with the IDE?

Yes. We’re working on a rudimentary language service and we’re hoping to
get debugging on par with what IronPython provides today. The ETA for
the debugging check-in is sometime next week. The language service will
take a while longer to whip into shape, and we’ll likely be showing it
off at MIX.

Keep in mind that this in no way is a complete language service. As the
good folks over at Sapphire in Steel will tell you, there’s a ton more
work to do than just getting syntax coloring and debugging working (in
their case it was actual work since they had to write a debugger and a
scanner and parser).

Today we don’t have plans to fully productize IronRuby a’la C# or
JScript in VS. Consider this the min bar of what my team will provide:
syntax coloring, some kind of project system, and VS debugging support.

Thanks,
-John

John L. (DLR) wrote:

The good news is that you should just be able to reuse our work to get
debugging support working. AFAIK there was almost no work required to
enable debugging in VS once we got IronRuby + DLR generating the correct
PDBs.

That’s good to hear. It should be a lot less work for us to get the
IronRuby debugger integrated than it was to write a fast debugger for
standard Ruby :wink:

I must say that I’ve really started enjoying using IronRuby now we have
a workable form designer. The big thing I’ve missed up to now has been
the debugger so that’s going to be a great addition.

best wishes
Huw

SapphireSteel Software
Ruby and Rails In Visual Studio
http://www.sapphiresteel.com