Decision process of future rubyspec about spec

[anthonycrumley]

I like this definition of "Benevolent Dictator". http://en.wiktionary.org/wiki/benevolent_dictator

[eregon]

Agreed, we need some coding style and rules.

I am not sure what you mean by "the honest dictator model", could you elaborate a bit?

I do think there should not be only one person able to accept changes in RubySpec, that is fundamental for me.
And I think coding style/rules should be established based on the existing ones and should be agreed by most concerned parties (MRI committers contributing to RubySpec and active external contributors).

[anthonycrumley]

Concerning coding style, here are some links to the rubyspec website repo for current style which may be helpful.

• https://github.com/rubyspec/rubyspec.github.io/blob/archive/organization.markdown
• https://github.com/rubyspec/rubyspec.github.io/blob/archive/style_guide.markdown

Concerning project process, the process from the ZeroMQ community has a lot of ideas that I like (http://rfc.zeromq.org/spec:22). The Ruby Rogues podcast interviewed the guy who leads the process (http://devchat.tv/ruby-rogues/188-rr-community-building-with-pieter-hintjens). The most attractive part of it to me is the focus on growing the community and thereby speeding development of the project.

[nurse]

I am not sure what you mean by "the honest dictator model", could you elaborate a bit?

Like Ruby or Rails, a decision is done by a person like matz or DHH. This is better than committee model on bikeshed issues like naming or styles, or fundamental issues like what should RubySpec cover, or fundamentally they must define "What is RubySpec". Of course they must consider concerned parties and resolve their conflicts.

In other words, they must handle nobu, who has his own vision.

[nurse]

For example, they must decide (or defer) #34 even if there are no comments.

[eregon]

@nurse I see, but like matz or DHH the honest dictator would not need to get involved for merging a straightforward change? Who would be that honest dictator?

[nurse]

@eregon Yes, daily merging don't need them. Who would be is difficult issue. I had expected brixen could be that...

[anthonycrumley]

I think that would be "Benevolent Dictator". http://en.wikipedia.org/wiki/Benevolent_dictator_for_life

[anthonycrumley]

The person chosen for this role needs to be "Benevolent" enough to resolve conflict without creating more conflict. Yet, they need to have a vision of what the project should be and make difficult decisions that some people won't like. They need to be able to move the project along without causing detrimental forks.

They also need to be a person who is able to build up a community around RubySpec because the Ruby language is vast in scope. A significant group of developers is needed for RubySpec to realize its potential.

[eregon]

I would like to propose myself as benevolent dictator of the new RubySpec at ruby/rubyspec.

Does someone else want this role?
It seems very clear brixen does not want it anymore at least.

My main goal is to augment contributions while maintaining good project standards in order to improve the coverage and the quality of the specs.

@nurse @hsbt @headius @anthonycrumley Do you agree with this?

[nurse]

Agree!

[anthonycrumley]

👍 Agree!

[hsbt]

Agreed!

[bruno-]

👍
long live rubyspec

[eregon]

I guess we can close this 😄