From: Paulo Schreiner <paulo@...>
Date: 2002-02-23T08:15:58+09:00
Subject: Re: Setting the Ruby continued

Ok, I can't take part in developing ruby not becouse of the language
problem, but becouse don't have enough knowledge of the ruby source,
wich is well commented, and I could help in developing ruby, if I took
time studying it.
The fact that the -dev list is not on english makes me think, not that I
can't make patches and help by myself, but that I'm missing most of what
happens with ruby.
I would fell better, if, at least for every patch accepted on the
ruby-dev list, there would be a summary in english in ruby-talk, so all
the community could review the patches. I think the greatest strength of
open source cose is not the ability to change it yourself, but to lurk
in the devel lists, see what's discussed and whenever you have simething
to say, you do it. It's better if find problems on code BEFORE
integrating it, and the more people looking at it, fewer chances
something goes wrong.
Don't take me wrong, im just too curious and would like to know what is
being talked at ruby-dev...

Paulo S.

PS: I also cannot read "The Ruby Way" and the "Developers Guide" in
portuguese...


On Fri, 2002-02-22 at 13:44, TAKAHASHI Masayoshi wrote:
> Hello,
> 
> Paulo Schreiner <paulo@bewnet.com.br> wrote:
> > Also VERY important:
> > ruby-dev in english.
> > 
> > An open source language cannot be (too) popular if it's development is
> > done in a language that just a few understand.
> 
> Don't worry. 
> Do you rememeber "ruby-talk seperation" thread in January?
> On July 1997, Same suggestion was there in ruby-list, then
> we split ruby-list into ruby-list and ruby-dev.
> At that time, Ruby is developed in Japanese.
> 
> But now, ruby-talk has grown and its traffic is more than
> (ruby-list + ruby-dev + ruby-ext + ruby-math)'s traffic.
> When you have some questions, you can post it here. When you
> have some requests, you can write it in RubyGarden as RCR.
> When you find a bug, you can repont it on Ruby BTS.
> You can take part in the development of Ruby without Japanese,
> without ruby-dev.
> There are few problems to develop Ruby for English speaker
> (or, they have as many problems as Japanese developers have).
> 
> # In fact, we cannot read "The Ruby Way" and "Ruby Developer's
> # Guide" in Japanese! :-)
> 
> We should say Ruby is now developed in Japanese _and_ English.
> 
> # Other languages?  umm, it'll be realized if Matz learn it :-)
> 
> 
> Regards,
> 
> TAKAHASHI 'Maki' Masayoshi     E-mail: maki@rubycolor.org