The Ruby Documentation Project is dedicated to getting MRI Ruby fully documented. To achieve this goal as fast as possible, we offer a support system geared towards making it easy to prepare and submit documentation patches. We encourage you to take advantage of this opportunity to give back to open source in general and to Ruby in particular.
Why Documentation?
- Only about 75% of Ruby is adequately documented
- Existing documentation could use some polish in form of clearer descriptions and better examples
- Writing documentation is a gentle, but effective introduction to contributing to open source
- Great way to solidify your Ruby fundamentals
- Many prominent Rubyists and core contributors have started out this way
What We Provide
- Detailed step-by-step guide to take you through the process of contributing documentation patches
- Guides on particular aspects, such as preparing patches using git
- A list of undocumented areas, so that you can pick something that interests you
- Answers to your questions via the mailing list and on IRC
- Reviews of your documentation patch before you submit it
How It Works (In a Nutshell)
Generally, Ruby documentation patches need to be submitted to the Redmine Ruby Issue Tracking System. We pave the way to ensure a successful submission by setting up an internal review process through Github. To take advantage of this workflow you need to:
- Create your own fork of this fork of ruby
- Indicate what you want to work on by opening an issue. This is mostly to avoid duplication of efforts.
- Submit a pull request on Github which will trigger a review process
- Then prepare your patch for submission to the Ruby Issue Tracker
For more details on the entire process Read our step-by-step guide
