RCR Submission Guidelines and Procedures

Before you submit an RCR...

Here is some important advice that you should follow if you are thinking of submitting an RCR:

Do not submit an RCR if Ruby is new to you. The Ruby community welcomes everyone, but experience suggests that it pays to spend some time with the language, and in its community, before suggesting changes to the language.
Read the advice in .
Consider discussing your RCR idea on IRC (#ruby-lang on freenode.net). This can help you troubleshoot your idea, and see whether anyone brings up any important problems with it up front.

Once you decide to submit an RCR, you should keep the following in mind:

An RCR has several components: title, abstract, problem, proposal, analysis, implementation.
These components are described in detail so that you understand them before you start writing an RCR.
Make sure your RCR involves only one change. Do not combine multiple requests into one.
Choose a meaningful title for your RCR; don't use a cutesy or joking title.
If at all possible, include an implementation of your RCR, preferably in Ruby. This is not mandatory, but can be very helpful as people try to evaluate what you're proposing.