[#50466] [ruby-trunk - Bug #7492][Open] Segmentation fault at DL::TestDL#test_call_double on x64 Windows 8 — "phasis68 (Heesob Park)" <phasis@...>

23 messages 2012/12/02

[#50558] [ruby-trunk - Feature #7511][Open] short-circuiting logical implication operator — "rits (First Last)" <redmine@...>

12 messages 2012/12/04

[#50575] [ruby-trunk - Feature #7517][Open] Fixnum::MIN,MAX — "matz (Yukihiro Matsumoto)" <matz@...>

20 messages 2012/12/05

[#50755] Becoming a committer — Charlie Somerville <charlie@...>

Hi ruby-core,

21 messages 2012/12/11
[#50759] Re: Becoming a committer — Yukihiro Matsumoto <matz@...> 2012/12/11

Hi,

[#50784] Re: Becoming a committer — Charles Oliver Nutter <headius@...> 2012/12/11

It's really this easy? If so, I'll send over my public key today :)

[#50795] Re: Becoming a committer — Yukihiro Matsumoto <matz@...> 2012/12/11

Hi,

[#50806] [ruby-trunk - Feature #7548][Open] Load and Require Callbacks — "trans (Thomas Sawyer)" <transfire@...>

12 messages 2012/12/12

[#50810] [ruby-trunk - Feature #7549][Open] A Ruby Design Process — "brixen (Brian Ford)" <brixen@...>

34 messages 2012/12/12

[#50867] [ruby-trunk - Bug #7556][Assigned] test error on refinement — "usa (Usaku NAKAMURA)" <usa@...>

14 messages 2012/12/13

[#50900] [ruby-trunk - Bug #7564][Open] r38175 introduces incompatibility — "tenderlovemaking (Aaron Patterson)" <aaron@...>

14 messages 2012/12/14

[#50951] [ruby-trunk - Bug #7584][Open] Ruby hangs when shutting down an ssl connection in gc finalization — "bpot (Bob Potter)" <bobby.potter@...>

12 messages 2012/12/17

[#51076] [ruby-trunk - Feature #7604][Open] Make === comparison operator ability to delegate comparison to an argument — "prijutme4ty (Ilya Vorontsov)" <prijutme4ty@...>

12 messages 2012/12/22

[ruby-core:50839] Re: Ruby Implementers Meeting Summary

From: Jon <jon.forums@...>
Date: 2012-12-12 17:50:28 UTC
List: ruby-core #50839
> Here is a summary of the implementers meeting.  I am not an expert
> summarizer, so you should also visit the wiki for a full log
> (http://bugs.ruby-lang.org/projects/ruby/wiki/DevelopersMeeting20121210).


Thank you for making the discussion available. This level of transparency is valuable even to we of the users/non-implementors clan.

As a user (CRuby and JRuby on Ubuntu Server, Arch, and Windows 7) I was very pleased to see the following:

  [16:19:16] <matz_> I am not going to stop being the dictator, but I want you
             guys to participate in the process of improving the language
  [16:19:28] <headius> clarifying a point made earlier: 100% consensus means
             any no vote acts as veto…so the question is really whether matz
             can inject a feature into standard ruby without 100% consensus
  ...
  [16:20:49] <matz_> headius, I would keep the privilege, but I promise I will
             not use it often

Design-by-committee, or decision-by-committee, or spec-by-committee (which, regardless of the words used, is the reality when 100% concensus is the process) is bad for users and innovation. It's a very different monster than (improved) lightweight collaboration combined with leadership that (a) recognizes when meaningful course corrections are needed, and (b) takes appropriate and timely action.

I feel much better for Ruby's future (both language and the multiple impl's) knowing that spec-by-committee has been clearly rejected. That said, I hope the other points that Brian raised in his design process blog are not dismissed en masse simply because #7 is the wrong way forward.

As a user, I'm also glad to see the back-n-forth happening very publicly rather than disappearing into ShadowLand. Or worse, talented devs simply abandoning ship because of frustration, or feeling they have no voice, or feeling ideas for improvements are always rejected without thoughtful consideration.

Jon

In This Thread

Prev Next