On Mon, 9 Oct 2006, Tim Uckun wrote:

> I took a brief look at activemessaging. Looks great. Then I take a
> look at the roadmap and see that all the tickets logged are actually
> spam.
>
> No tickets logged, no milestones defined. I take a look at the
> timeline and it's all spam too so no code checked in either.
>
> To me this is one of the biggest frustrations of dealing with ruby and
> rails. The libraries are in a unfinished state and are not being
> worked on actively. Examples.
>
> The DBI ADO library is b0rked. The answer seems to be to use ODBC. I
> volunteered to work on the libraries if somebody could integrate my
> work with DBI but nobody is interested.
>
> I was excited about railscron and it's been dumped and replaced with
> something which has no cron functionality at all (threading problems
> from what I can gather).
>
> I tried various AGI implementation for asterisk and the same story.
> RAGI hasn't been touched in a year, the rubyforge forums questions go
> unanswered, patches that were submitted are not integrated, bugs not
> fixed, etc.
>
> I don't know what the answer is. I am grateful that talented people
> have dedicated their time and effort to create these libraries in the
> first place but it's very hard to tell which libraries are robust,
> which ones are abandoned, which ones are not being worked on because
> they are stable and don't need any more work.

google 'rpa' (ruby production archive).  for some reason, it didn't take off
like gems - imho it was a powerful idea...

cheers.

-a
-- 
in order to be effective truth must penetrate like an arrow - and that is
likely to hurt. -- wei wu wei