From: Sam Roberts <sroberts@...>
Date: 2005-03-04T09:59:03+09:00
Subject: Re: RAA Status & b

Quoting jamesUNDERBARb@neurogami.com, on Fri, Mar 04, 2005 at 03:37:54AM +0900:
> Curt Hibbs wrote:
> >Below, I posting the entire text of this blog entry:
> >
> >  http://sean.typepad.com/ditto/2005/03/the_problem_wit.html
> >
> >I think that this guy has really called it right. There have been a few
> >postings about a reworking of RAA... does anyone know the current status of
> >this effort?
> >
> >Curt
> >
> >==========================
> >http://sean.typepad.com/ditto/2005/03/the_problem_wit.html
> >The Problem with Ruby


I don't agree at all. I go first to RAA, then google, I've never
searched rubyforge.

Why should somebody have to put their package on rubyforge if they have
a place they'd rather do their development?

I do think that all rubyforge projects should automatically mirror to
RAA, as has been suggested before.

I also think that RAA entries should have a comments underneath them so
that people can add a rating/comment. That would help a bunch.

Also, the standard library docs are a mess, very incomplete, and
frustratingly hard to get documentation diffs into. I now maintain a
local tree of docs, and annotate the src with my docs as I figure out
how undocumented stuff works.

Cheers,
Sam

> <snip/>
> 
> Some possible solutions:
> 
> 1. Dump the RAA.
>   Don't bother fixing it.
>   Tell people to move their code to RubyForge.
> 
> 2. Dump the RAA
>    Tell people to find a home page for their
>    project and include "RAA" and "Ruby" in the keyword meta tag,
>    and let Google do the rest.
> 
> 2. Dump the RAA
>    Tell people to find a home page for their
>    project and tag it on del.icio.us with the tags 'Ruby'
>    and 'RAA', plus a brief description.
> 
> I get the sense that this blogger's opinion was based entirely on what 
> he  saw at the RAA.   RAA has pretty much fallen off my radar; If I'm 
> looking for a Ruby app or lib I turn to RubyForge or Google.  The RAA 
> has tended to be too incomplete or out-of-date.  I've listed things 
> there but have more or less forgotten about their respective pages; it 
> is just too much extra work to have a project, maintain the README and 
> home page for that project; AND have to duplicate much of that 
> information someplace else.
> 
> RubyForge was a godsend (thanks, InfoEtherites!) if for no other reason 
> that it facilitates one-stop shopping for both developer and end-user.
> 
> The RAA may be like a few other things in Rubyland: a good and 
> appropriate idea at the time of conception, but possibly past its prime 
> or superseded by more effective tools and infrastructure.
> 
> 
> 
> James
>