Re: [tlug] Precheck of open source Ruby projects

[Al Hoang <hoanga@example.com>]

On Fri, Dec 08, 2006 at 12:10:37PM +0900, Zev Blut wrote:
> Hello TLUGers,
> 
> I have a few projects written in Ruby that are open sourced and hosted
> on Rubyforge.  This is the first release for them and all the software
	Wow very cool.

> is done and should work, but as usual they could stand to have better
[snip]
> software to the Ruby lists sometime next week.  If any of you are
> interested I would appreciate any comments or suggestions of what I
> can improve before making an announcement.

	Is your project generating rdoc-ified API documentation?
If so in your release process, it'd be nice to put up the latest
release rdoc APIs on the website for easier access of the documentation.  
I understand Gems can handle generating rdocs locally after you have
installed a library but I find the ability to browse to a well known
location to browse the API very helpful too.

	After that, I'd imagine some useful things (and probably
time consuming) to do might be:
1. Examine rubyforge for other tools that do a similar function and
   provide a comparison on why your tool is more appropriate
2. Fill out meta-data in the project summary for the Trove Software map
   (One thing I find usefu meta-data is whether the library is a pure
    ruby implementation or uses some C or something else)
3. What is 1.0 supposed to do?  (I notice lots of OSS projects don't
   put down what a 1.0 release is supposed to do so maybe this isn't
   an issue but it's always nice to know what the author has in mind
   for the future of the project)


Just my 0.02Y.
Alain