From: Gavin Sinclair <gsinclair@...>
Date: 2005-10-14T21:31:54+09:00
Subject: Re: Why Write Ruby Docs? (was Re: [SUMMARY] Text Image (#50))

Kev Jackson wrote:

> Ok so I've looked at the site (and at the status report).  I presume
> that to get working on them I'd need to get the actual ruby sources and
> start adding comments/doc/examples into the source files, but then how
> do I push changes in the original sources back so that the RDoc can be
> extracted/published?  If the sources are part of the stdlib (which ships
> with ruby itself), is there a bugzilla/issu tracker or something to
> attach patches to?

Damn, thought I replied earlier but ... it hasn't appeared, so I guess
I didn't.  Sorry if this is a duplicate.

You do need to get the Ruby sources (anonymous CVS is best) and work
with those.  There's no bugzilla or similar for doc patches.  This part
of the process has been a failure and I take responsibility for that.
If you have a patch, email it to me and/or James Gray.  One of us will
massage it through ruby-core back into CVS, and James Britt and I will
regenerate the bits and pieces on ruby-doc.org/{core,stdlib}.

Thanks for any help, and feel free to ask any questions.

Cheers,
Gavin