From: Gavin Sinclair <gsinclair@...>
Date: 2002-09-05T14:03:37+09:00
Subject: Re: suggestions to the Ruby community

> Hi
>
> [gratuitous snip]
>
>  1. Form a ruby-doc mailing list to begin discussions
>     related to documentation.

Great idea.

>  2. Form a Ruby Document Organizing Committee (RDOC)
>     for purpose of officially reviewing the document
>     standardization process and voting on
>     decisions (of course Matz has ultimate veto power).

Good idea.

>  3. Start a web page to publicize the activities
>     of the documentation project.

Fine.  Just be aware of other documentation webpages in existence.  This
is the purpose of an organization committee, I guess.)

>  4. Start the paper work for the standardization process.
>     a Gather Requirements and write Requirements specification.
>       i. get feedback from community
>       ii. have committee review and approve
>     b. Write functional specification
>       i. get feedback from community
>       ii. have committee review and approve
>     c. Create design document
>       i. get feedback from community
>       ii. have committee review and approve
>     4. Implement RDOC process and develop tools
>     5. Integrate 4 into releases of Ruby

Good plans.  Let's keep it simple too!  Also, remember that various
fragments of the above probably already exist.

> I welcome your comments along the lines:
>
>   a) this is a good idea, let's get going
>      and I want to be on the committee
>   b) what, are you crazy??
>   c) good idea, but I can do a lot better
>      job than you...
>   d) it's all hopeless, I am going back to
>      programming in perl.

My response is (a).  I second Jim Freeze's leadership!

>
> Cheers
> --
> Jim Freeze

--Gavin

> ----------
> Programming Ruby
>  def initialize; fun; end
> A language with class

I usually snip sigs, but that's a cool one.