summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorzzak <zzak@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2013-11-28 10:29:54 +0000
committerzzak <zzak@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2013-11-28 10:29:54 +0000
commit85076c0160fc0ef8220b7bf25712414dc78d1f68 (patch)
treedfb893aa523665c212e4f39826134bc1827d543b /doc
parent743305413d2089e10773b82b03cc111bd793f38a (diff)
* 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
Diffstat (limited to 'doc')
-rw-r--r--doc/contributing.rdoc18
1 files changed, 18 insertions, 0 deletions
diff --git a/doc/contributing.rdoc b/doc/contributing.rdoc
index 85f7c92..e11d76f 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