On 10-10-13 04:41 PM, Chuck Remes wrote:
>
> On Oct 13, 2010, at 3:29 PM, Rajinder Yadav wrote:
>
>> On Wed, Oct 13, 2010 at 12:29 PM, Jeremy Bopp<jeremy / bopp.net>  wrote:
>>> On 10/13/2010 3:53 AM, Rajinder Yadav wrote:
>>>> I discovered the ruby-core website, instruction on there is lacking.
>>>> What does one do after they check out the code?
>>>
>>> You should build the code and install the binaries so that you can start
>>> using that version of Ruby.
>>>
>>>> If someone wants to start small and work their way up what is the
>>>> process? I would like to help with Ruby 2.0, with testing and improving
>>>> the doc, and eventually move on to fix bugs.
>>>
>>> I don't know for certain what the official processes is, assuming there
>>> is much of one at all.  The best I can do is point back into the link I
>>> sent earlier:
>>>
>>> http://www.ruby-lang.org/en/community/ruby-core/#patching-ruby
>>>
>>> That specific section details how to go about submitting patches and bug
>>> reports.  There are other links in that section containing information
>>> on how to make a patch that will be considered.
>>>
>>> If you just want to start fixing things, look for open issues in the
>>> defect tracker and make patches to correct the issues you find.  You'll
>>> find documentation (or items that need documentation) along with the
>>> code within the Ruby sources.  If you find a defect that you don't know
>>> how to fix yourself, open a new issue in the defect tracker and provide
>>> all the details you can in order to describe the defect.
>>>
>>> -Jeremy
>>
>> Hi Jeremy,
>>
>> thanks for your assistance. I got the source off the trunk and built
>> Ruby, I guess I'll start off by getting familiar with the source code
>> and layout of the project. I did a quick browse of the bug database
>> and have a better idea where to look.
>>
>> I guess my first step is to read the README and compile a C module I
>> can call from Ruby to get use to the build tool. I don't have a Linux
>> background, but at home I use it exclusively from Ruby and Rails.
>>
>> I'll push myself to find a easy bug to reproduce and fix just to get
>> use to the process of going through the motions.
>
> There is no need to limit yourself to working *only* on MRI Ruby (MRI = Matz's Ruby Interpreter).
>
> There are at least two other major Ruby runtimes that could use the time and talents of interested programmers. Plus, their code is a little more approachable than MRI's code base.
>
> JRuby
> http://github.com/jruby/jruby
>
> Rubinius
> http://github.com/evanphx/rubinius
>
> JRuby is written primarily in Java but it has quite a bit of pure Ruby too.
>
> Rubinius is written primarily in Ruby with a small C++ VM and a JIT using LLVM.
>
> cr
>
>

The Rubinius project sounds like something interesting to work on, but 
I'm not a fan of Java being a C++ guy =P

I'll take look at Rubinius.

-- 
Kind Regards,
Rajinder Yadav