# How-to Contribute to IronRuby

**URL:** <https://www.ruby-forum.com/t/how-to-contribute-to-ironruby/203850>\
**Category:** IronRuby\
**Created:** [February 28, 2011, 6:37pm UTC](https://www.ruby-forum.com/t/how-to-contribute-to-ironruby/203850 "2011-02-28T18:37:16Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![luislavena](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/0ea827/32.png) [@luislavena](https://www.ruby-forum.com/u/luislavena)\
**Post date:** [February 28, 2011, 6:37pm UTC](https://www.ruby-forum.com/t/how-to-contribute-to-ironruby/203850/1 "2011-02-28T18:37:16Z")

</div>

I’ve been trying to find information on how to contribute to the  
project.

Given the recent changes to the solution source and website, is the  
information on becoming a contributor still current?

My hope was that I could work on issues as a way to get my feet wet.  
Are these tracked exclusively on the main branch on GitHub? I checked  
yesterday and I only saw 2 active issues.

I think this is a fantastic project. I love being able to use my .NET  
assemblies. Using something like Cucumber and RSpec to test my .NET  
classes is huge and honestly very exciting. I also really like the  
prospect to using Ruby to code my Silverlight/WPF/Win Phone 7  
applications. I’m not as interesting in hosting Ruby code in my CLR  
code.

As an outsider, it looks like IronRuby is dying a slow death given the  
last 6 months or so. I want to try to do my part to keep this project  
not just alive, but vibrant. Certainly we can offer a CLR-integrated  
Ruby  
interpreter that is as capable as JRuby.

Come on, put me to work! 🙂

---

<div class="post-metadata">

**Author:** ![ghoti143](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/90db22/32.png) [@ghoti143](https://www.ruby-forum.com/u/ghoti143)\
**Post date:** [February 28, 2011, 8:38pm UTC](https://www.ruby-forum.com/t/how-to-contribute-to-ironruby/203850/2 "2011-02-28T20:38:46Z")

</div>

This information should be up to date:

> **[Home](https://github.com/IronLanguages/main/wiki)**
>
> Work for this repo has moved to https://github.com/IronLanguages/ironpython2 - IronLanguages/main

if you find any discrepancies, let us know.

Bugs are tracked on CodePlex:  
[http://ironruby.codeplex.com](http://ironruby.codeplex.com)

There is a plenty of failing specs that also need to be fixed – see

> **[main/Languages/Ruby/Tests/mspec/ironruby-tags-19 at master · IronLanguages/main](https://github.com/IronLanguages/main/tree/master/Languages/Ruby/Tests/mspec/ironruby-tags-19)**
>
> master/Languages/Ruby/Tests/mspec/ironruby-tags-19

If you find something interesting you’d like to work on send an e-mail  
to the list so that others know what you are up to.

Thanks!  
Tomas

---

<div class="post-metadata">

**Author:** ![ghoti143](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/90db22/32.png) [@ghoti143](https://www.ruby-forum.com/u/ghoti143)\
**Post date:** [February 28, 2011, 10:57pm UTC](https://www.ruby-forum.com/t/how-to-contribute-to-ironruby/203850/3 "2011-02-28T22:57:24Z")

</div>

This reminds me… we need to sync to the latest Ruby specs time to  
time.

> **[main/Languages/Ruby/Tests/mspec/rubyspec at master · IronLanguages/main](https://github.com/IronLanguages/main/tree/master/Languages/Ruby/Tests/mspec/rubyspec)**
>
> master/Languages/Ruby/Tests/mspec/rubyspec

Every time we do that we need to generate tags, mark critical tests that  
crash the test runner and push our changes to the specs up to the main  
rubyspec repo (and get them approved).

Any volunteers for this?

Tomas