From: Tom Copeland <tom@...>
Date: 2007-01-17T01:25:32+09:00
Subject: Re: RubyForge website

> A lot of projects in RubyForge have no website, other than 
> the "Hopefully coming soon..." message.  Might I suggest that 
> the site default to the RDoc of that gem (or gems)?

Yup, or have that in one of the tabs for each project.

> > Advantages:
> * Every project has a site letting you know what it does 
> (sometimes there is next to no info on the project page).
> * Encourages developers to keep the RDoc up to date
> * The most common site that projects do have is simply their 
> RDoc.  So, we've removed one step for all of those projects.
> 
> Disadvantages:
> * Requires a little processing on the rubyforge server (to extract the
> RDoc)

Is there any security aspect to this - does running RDoc on a gem
require installing it or executing any of the code in the gem?  I
suppose it could be done on a different machine and uploaded to
RubyForge, though...

Yours,

Tom