Hello, feature proposers for Ruby 2.2,
What’s the status on your feature proposal? No progress
because no reply form matz?
I’d like to announce a big chance to accelerate your proposal!
You may know, we’ll release Ruby 2.2 on 25 Dec.
I’m planning to hold a developer meeting (including matz)
to judge feature requests, on July at Tokyo.
If matz says “accept!” for your proposal there, your
proposal is accepted. Congratulations!
But, at present, there are more than many feature tickets.
We never have enough time to review the all.
So, to facilitate our meeting, aspiring proposers’s help
will be very much appreciated.
What I ask you:
Please create “one-minute slide-show for your proposal”
-
one-page slide (or corresponding material)
- MUST show a corresponding ticket number
- make it visual
- MUST include a figure and/or short example code
- SHOULD have less sentence in natural language
(try to write less than 140 characters) - it is RECOMMENDED to itemize: motivation/use case, propoasl,
pros/cons - medium: PDF
-
patch (optional)
- a patch for trunk
- we’ll review to check the behavior of edge cases
-
submission deadline: 7/24
(Expected) FAQ:
Q. How should I submit my slide?
A. Attach it to the corresponding feature ticket.
I’ll then reply “received”. If I missed, please remind me in any
fashion.
Q. What would happen after the deadline?
A. I’ll hold a developer meeting and review the slides.
They will be accepted, rejected, or feedback.
Q. I’d like to present my slide myself.
A. We will take just two minites per proposal.
Let us reduce the cost of presenter rotation.
Q. Will my proposal be rejected unless I create a slide?
A. No, not necessarily. However, the possibility that it
is accepted for 2.2 will be certainly decreased.
Q. My proposal is not so simple to present in one minute.
Only “cheap” proposals can be accepted in this method?
A. More or less, it may be true. But leaving it untouched
does not brings any worth.
Feature proposers have to exlpain your proposal plainly,
even whether this method is used or not. Consider matz
as a busy angel investor, and try “elevator pitch.”
Q. My ticket is not a feature request, but a bug report.
Should I also submit a slide?
A. No, it is not needed if it is really a bug ticket.
But, I often find some bug reports to be feature
request in effect. It would be a good idea to re-check
if your bug report is really about a bug.
Q. Is there advice to create a slide?
A. Write “use case”!
Q. Such a method will really work?
A. At least 2.0 and 2.1 uses this method, and it work at some level.
Looking forward to your appealing slides!