From: James Britt <james_b@...>
Date: 2005-10-19T02:08:01+09:00
Subject: Re: Why Write Ruby Docs? (was Re: [SUMMARY] Text Image (#50))

Gavin Sinclair wrote:
> Kev Jackson wrote:
> 
> 
>>If I could get paid to write docs I'd be all over it like something all
>>over something else.  But if someone could point to some area that needs
>>documenting I'd be more than happy to help - I was a technical author a
>>few years ago, and I have contributed code and docs to several open
>>source projects (mainly Java), I just didn't realise that more hands
>>were needed - please push links etc to me I'll help out with doco
> 
> 
> Hi Kev,
> 
> Documentation of core and library classs is written in the source code
> (be it C or Ruby).  Thus to contribute, you want to avail yourself of
> (anonymous) CVS access (it's easy).  Then you edit files, create a
> patch, and get it committed.  That last step has been the problem in
> the past; mea culpa.  Suggested process: email the patch to me and/or
> James Gray (sorry, James!).  Bug me mercilessly if nothing's being
> done.
> 


BTW, what is the copyright on submitted docs, and is it made clear to 
those submitting documentation?


James Britt

-- 

http://www.ruby-doc.org - The Ruby Documentation Site
http://www.rubyxml.com  - News, Articles, and Listings for Ruby & XML
http://www.rubystuff.com - The Ruby Store for Ruby Stuff
http://www.jamesbritt.com  - Playing with Better Toys