Developers Meeting 2012-12-10¶
This meeting was held on 2012-12-10 at 15:00 Pacific Time at irc://chat.freenode.net/#ruby-implementers.
- Eric Hodel - drbrain (moderator)
- tenderlove (Aaron Patterson)
- wycats (Yehuda Katz)
- n0kada (nobu)
- sora_h (sorah)
- unak (usa)
- nurse (naruse)
- emboss (Martin Boßlet)
- marcandre (Marc-André Lafortune)
- eregon (Benoit Daloze)
- tarui (tal)
- brixen (Brian Ford)
- dbussink (Dirkjan Bussink)
- evan (Evan Phoenix)
- headius (Charles Nutter)
- enebo (Tom Enebo)
- phlebas (Tim Felgentreff)
- lrz (Laurent)
- ferrous26 (Mark Rada)
- jballanc (Joshua Ballanco)
We'll keep this meeting to one hour long.
- How to improve current process (tenderlove)
- Experimental feature?
- Other issues after scope reduction?
- Ruby 2.0 clarifications
- Open floor
- This Meeting
- Should we do it again?
- How often?
- How long?
Proposal of "Ruby Language Team"¶
- There are many implementations of Ruby
- Only one Ruby language
- We should form a group to define "Ruby" called Ruby Language Team
- The team consists of representatives from different implementation teams
- There will be a new way to propose features
- Features require Champions
- Champions belong to the Language Team
- Champions refine proposals until the Language Team reaches consensus
- When consensus is reached, proposal is approved
- Approved proposals are added to RubySpec
- After addition to RubySpec, the change is now considered "Ruby"
- Implementations are allowed to have experimental features
- Brixen will ensure smooth entry of feature in to RubySpec
- Specs will be in a central repository
- The person proposing the feature should write documentation to
- Brixen shouldn't be single point of failure
- If an implementation can't implement something, is it not "ruby"?
- Is 100% concensus really necessary?
- What about stdlib?
- Is it OK that we communicate in English?
- Rigid process is not great
- Having an executable spec that can be gradually translated to RubySpec is good
- "And I want to make sure as long as I live on this mortal
state, you need my approval before adding something as official Ruby" -- matz
- We should try having more meetings among implementers
- Maybe we should maintain a flag to identify official "Ruby" features?
- Matz wants to remain dictator, but still have participation from implemeters.