kotovalexarian-likes-github/ruby--ruby
1
0
Fork 0
mirror of https://github.com/ruby/ruby.git synced 2022-11-09 12:17:21 -05:00
Code Releases Activity

* doc/contributing.rdoc: [DOC] Add notes about slideshow proposals

Browse source 
from wiki page: HowToRequestFeatures


git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@43897 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
This commit is contained in:
zzak 2013-11-28 10:29:54 +00:00
parent 743305413d
commit 85076c0160
2 changed files with 23 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
ChangeLog
View file

@ -1,3 +1,8 @@
Thu Nov 28 19:29:04 2013 Zachary Scott <e@zzak.io>
* doc/contributing.rdoc: [DOC] Add notes about slideshow proposals
from wiki page: HowToRequestFeatures
Thu Nov 28 17:34:42 2013 Masaki Matsushita <glass.saga@gmail.com>
* st.c: add st_values() and st_values_check().

18
doc/contributing.rdoc
View file

@ -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