From: "trans (Thomas Sawyer)" Date: 2012-12-14T02:57:45+09:00 Subject: [ruby-core:50881] [ruby-trunk - Feature #7549] A Ruby Design Process Issue #7549 has been updated by trans (Thomas Sawyer). @jonforums I disagree. It may not be in the same branch of conversation as preceding posts but I do not think it tangential. If the main line of Ruby development were in Ruby itself it would greatly effect this **process**, probably much more than anything else that's been discussed or agreed to thus far. Moreover, if history tells us anything, we've see this **process** discussion before (aka RCR). And like before, it won't amount to much. ---------------------------------------- Feature #7549: A Ruby Design Process https://bugs.ruby-lang.org/issues/7549#change-34716 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/