[#33640] [Ruby 1.9-Bug#4136][Open] Enumerable#reject should not inherit the receiver's instance variables — Hiro Asari <redmine@...>

Bug #4136: Enumerable#reject should not inherit the receiver's instance variables

10 messages 2010/12/08

[#33667] [Ruby 1.9-Bug#4149][Open] Documentation submission: syslog standard library — mathew murphy <redmine@...>

Bug #4149: Documentation submission: syslog standard library

11 messages 2010/12/10

[#33683] [feature:trunk] Enumerable#categorize — Tanaka Akira <akr@...>

Hi.

14 messages 2010/12/12
[#33684] Re: [feature:trunk] Enumerable#categorize — "Martin J. Dst" <duerst@...> 2010/12/12

[#33687] Towards a standardized AST for Ruby code — Magnus Holm <judofyr@...>

Hey folks,

23 messages 2010/12/12
[#33688] Re: Towards a standardized AST for Ruby code — Charles Oliver Nutter <headius@...> 2010/12/12

On Sun, Dec 12, 2010 at 9:55 AM, Magnus Holm <judofyr@gmail.com> wrote:

[#33689] Re: Towards a standardized AST for Ruby code — "Haase, Konstantin" <Konstantin.Haase@...> 2010/12/12

On Dec 12, 2010, at 17:46 , Charles Oliver Nutter wrote:

[#33763] [Ruby 1.9-Bug#4168][Open] WeakRef is unsafe to use in Ruby 1.9 — Brian Durand <redmine@...>

Bug #4168: WeakRef is unsafe to use in Ruby 1.9

43 messages 2010/12/17

[#33815] trunk warnflags build issue with curb 0.7.9? — Jon <jon.forums@...>

As this may turn out to be a 3rd party issue rather than a bug, I'd like some feedback.

11 messages 2010/12/22

[#33833] Ruby 1.9.2 is going to be released — "Yuki Sonoda (Yugui)" <yugui@...>

-----BEGIN PGP SIGNED MESSAGE-----

15 messages 2010/12/23

[#33846] [Ruby 1.9-Feature#4197][Open] Improvement of the benchmark library — Benoit Daloze <redmine@...>

Feature #4197: Improvement of the benchmark library

15 messages 2010/12/23

[#33910] [Ruby 1.9-Feature#4211][Open] Converting the Ruby and C API documentation to YARD syntax — Loren Segal <redmine@...>

Feature #4211: Converting the Ruby and C API documentation to YARD syntax

10 messages 2010/12/26

[#33923] [Ruby 1.9-Bug#4214][Open] Fiddle::WINDOWS == false on Windows — Jon Forums <redmine@...>

Bug #4214: Fiddle::WINDOWS == false on Windows

15 messages 2010/12/27

[ruby-core:33938] Re: Getting involved in Ruby

From: Benoit Daloze <eregontp@...>
Date: 2010-12-27 21:54:47 UTC
List: ruby-core #33938
On 25 December 2010 18:44, NARUSE, Yui <naruse@airemix.jp> wrote:
> Hi,
>
> I was 19 when I became a comitter.

I'm happy to know that. There is no age limit when there is real
interest I think.

>> 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.

Sure.

>> 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.

I am used to report but not to solve them.
That would be indeed helpful, I'll give a try.
(I just fear many need very specific knowledge, or are obvious and
then the reporter already gives a patch)

> 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.

I'm already used to look last Ruby's commits, even if I do not
consider myself reviewing them.
That is surely a good way to dig in the code.

> 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.

I should definitely look into RubySpec and make some.

> 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.

That path seems good to me, although I still doubt of my ability to
solve these bugs.

Thank you for the advices and ideas,

Best regards,
Benoit Daloze

P.S.: Now I have my exams, so I will likely be more active when I'll
have finished them.

In This Thread