On Jun 19, 2011, at 8:44 AM, Michael Klishin wrote:

> Chuck Remes escribió:
>> The concern becomes project ownership of these benchmarks. Should it be 
>> under the JRuby or Rubinius organizations? What happens when we add MRI or 
>> Maglev or IronRuby or ?? to the list of supported runtimes?
>> 
>> I suggest that the benchmarks be spun off to a new "ruby community" 
>> organization. This change will ensure more open access to runtimes that are 
>> not part of the Engine Yard ecosystem (if that's a concern to anyone) while 
>> also providing a semblance of impartiality.
> Chuck,
> 
> I think at least initially this project can reside under github.com/rubyspec 
> umbrella. rubyspec is what (hopefully) all Ruby implementations collaborate 
> on and many people in the Ruby community are aware of this fact. Vendor 
> neutrality was also one of the rubyspec goals.
> 
> Just an idea.

Good point. I like the idea.

cr

-- 
--- !ruby/object:MailingList
name: rubinius-dev
view: http://groups.google.com/group/rubinius-dev?hl=en
post: [email protected]
unsubscribe: [email protected]

Reply via email to