From 85076c0160fc0ef8220b7bf25712414dc78d1f68 Mon Sep 17 00:00:00 2001 From: zzak Date: Thu, 28 Nov 2013 10:29:54 +0000 Subject: * doc/contributing.rdoc: [DOC] Add notes about slideshow proposals from wiki page: HowToRequestFeatures git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@43897 b2dd03c8-39d4-4d8f-98ff-823fe69b080e --- ChangeLog | 5 +++++ doc/contributing.rdoc | 18 ++++++++++++++++++ 2 files changed, 23 insertions(+) diff --git a/ChangeLog b/ChangeLog index 0aa9cc5b56..c5700e0600 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +Thu Nov 28 19:29:04 2013 Zachary Scott + + * doc/contributing.rdoc: [DOC] Add notes about slideshow proposals + from wiki page: HowToRequestFeatures + Thu Nov 28 17:34:42 2013 Masaki Matsushita * st.c: add st_values() and st_values_check(). diff --git a/doc/contributing.rdoc b/doc/contributing.rdoc index 85f7c920a9..e11d76f904 100644 --- a/doc/contributing.rdoc +++ b/doc/contributing.rdoc @@ -146,6 +146,24 @@ A good template for feature proposal should look something like this: [See also] Links to the other related resources +=== Slideshow + +On Ruby Developer Meeting Japan, committers discuss about Feature Proposals together at Tokyo. We'll judge proposals accept, reject, or feedback. If you have a stalled proposal, making a slide to submit is good way to get feedback. + +Slides should be: + +* One-page slide +* Include a corresponding ticket number +* 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, corner case +* PDF or Image (Web browsers can show it) + +Please note: + +* Even if the proposal is generally acceptable, it won't be accepted without writing corner cases in the ticket +* Slide's exapmle: DevelopersMeeting20130727Japan + == Backport Requests When a new version of Ruby is released it starts at patch level 0 (p0), and -- cgit v1.2.3