From: "NARUSE, Yui" Date: 2010-12-26T02:44:25+09:00 Subject: [ruby-core:33876] Re: Getting involved in Ruby Hi, (2010/12/24 5:45), Benoit Daloze wrote: > I'm Benoit Daloze, and I have been coding with Ruby for a few years now. > I am a 19 years old Belgian student in computer science. I was 19 when I became a comitter. > My knowledge of C is a bit rusted, but I believe coding for my > favorite language will make it soon more accurate. > (and I recently wrote a few Ruby C extensions, so I think I could get > along relatively quick with the code). Yeah. Moreover when you write the code, the problem is usually almostresolved. > I would love to see your answer on this thread, matz, especially since > I saw your 2010 keynote at EuRuKo concluding with "See you at > ruby-core@ruby-lang.org". > Well, here I am, how can I help ? > > So, what would you (ruby-core coders) advise me to get better implied > in the core of Ruby ? > > Is it any specific library which especially needs help ? Many known problems are reported in our Redmine. http://redmine.ruby-lang.org/projects/ruby-19/issues But most remained bugs are remained because they are not reproducible or can't make a small reproducible code. So if you can do it, it's a valuable thing. Reviewing each commit of Ruby or each source code are also important. Ruby must have many bugs but almost of them are hidden in source. Reviewing commits prevent them before they are hidden. Reviewing codes can find hidden bugs. RubySpec can be a good starting point to find such bugs. RubySpec sometimes checks edge of Ruby. Edge is the nest of bugs; so you can find them easily. If you find a bug or a strange behavior, please report it to ruby-core (or make a ticket to redmine). After you report some bugs, you'll be able to fix it yourself. After you send many of patches, we invite you as a comitter. -- NARUSE, Yui