Improve Rails Documentation
Published about 7 years ago
This is almost a cross post from my email to rails-core mailing list :
Lately there had been many tiny doc patches at trac, which could easily escape our normal verification cycle. On top of that, we’re entering the whole new git-era of social development which eliminates the notion of “core” in a way.
I plan to give commit access to everyone who in the past have written a decent doc patch. Or anyone who is interested in writing one ( and can prove the quality of it by submitting at least one patch via whatever method ). And I’ll be syncing it with main Rails repository every week or so, after verifying all the changes.
So if you’re interested, you could email me directly or even easier is to catch me on IRC ( nick : lifo ). And once I add you to the doc-rails github project, you can commit directly to the repository without forking it ( and not bother about chasing anyone to pull your changes ).
Due to nature of this project/experiment, we’re gonna have to follow a strict set of guidelines for committers :
Violation of any rule will result in lose of commit rights.
This is just a start. Moving forward, we could even do hackfest for writing docs and probably try to convince caboose doc fund holders to support this move in any way possible. But it all really depends on how things work out with doc-rails.
So anyone who has ever complained about quality of Rails API docs, now is your chance.
The project received a very positive response on the first day. We got whopping 8 patches !!