Issue #7549 has been updated by subwindow (Erik Peterson).


kosaki (Motohiro KOSAKI) wrote:
>  We are already discuss by English, right? You can't inhibit face to
>  face meeting language because it's totally meaningless. you anyway
>  don't listen such talk. That is language independent issue. I think.
>  
>  If you want to inhibit face to face discussion itself, it doesn't make
>  sense too because each rubist naturally talk about ruby when they meet
>  and get a lunch. Nobody can stop it.

Sorry if I was not clear, but I absolutely do not want to inhibit face-to-face discussion. I'm speaking strictly of online discussion that forms the rationale and details of changes to Ruby.

>  And your worry is just illusion. As far as I know, almost all feature
>  discussion was discussed on ruby-core. So no one can solve an
>  illusion.

I have no idea whether it is illusory or not. There is a lot of discussion in Japanese concerning changes to Ruby. I have no way of knowing how much of (for instance) ruby-dev makes its way onto ruby-core. I do not want to end Japanese-language discussion, but I believe a stronger effort should be made to translate those discussions into English so that the rest of the community can be informed.

I feel like this discussion of language is but a minor note in the larger (and more important) discussion of creating a more collaborative process for changes to Ruby.
----------------------------------------
Feature #7549: A Ruby Design Process
https://bugs.ruby-lang.org/issues/7549#change-34673

Author: brixen (Brian Ford)
Status: Open
Priority: Normal
Assignee: 
Category: 
Target version: 


Matz,

At RubyConf 2012, I gave a talk about a design process for Ruby (http://www.confreaks.com/videos/1278-rubyconf2012-toward-a-design-for-ruby). So far, over 12,000 people have viewed that talk. I think it is reasonable to say that many people are concerned about and interested in a design process for Ruby.

On Monday, we had an IRC meeting of Ruby implementers. Most of the points in my proposal were discussed but I'm concerned that a lot of confusion remains.

I have written a post that describes a Ruby design process and hopefully clarifies points that people found confusing:

http://brixen.io/2012/12/11/a-ruby-design-process

I would like to propose this process for making changes to Ruby. I am going to put a summary of the process at http://rubyspec.org/design and ask for people who support the process to submit their signature. I'd like to request that you consider the response from the community for my proposal.

Thank you,
Brian



-- 
http://bugs.ruby-lang.org/