David Alan Black writes:

	"there are discussions and comments there [on RubyGarden] that
	do relate to what I mean, but the wiki itself is not what I
	mean...

	The same is true of Colin's Ruby Cookbook.  These are very
	useful things, but what I'm clumsily groping for is something
	that has more to do with actual code production and
	execution."

Let me try to restate what I *think* you're asking for, David, and if
I'm wrong, just say so. :)

Your first post - the one starting this thread - posited the need for
a solution to the problem of saving Ruby code for reuse that was
inappropriate for either an RCR or the RAA.

Your lastest post, excerpted above, when read in conjunction with the
comments on RubyGarden to which you refer, seems to outline a somewhat
different issue.  To wit, that the Ruby community needs a resource for
the colloborative development of code, which also facilitates its
archival and distribution (read: reuse).

Am I near the mark with these two restatements?

If so, then I think that there are a couple of solutions out there for
the first need you've identified.  (Though there's room for
improvement.)

The second issue is intriguing, however, and I can't think of anything
that solves this problem... but perhaps it would help if you
elaborated a bit.

-- 
Colin Steele
colin / webg2.com / www.colinsteele.org / www.rubycookbook.org


		   From "The Hacker's Dictionary":
  wizardly: adj. Pertaining to wizards.  A wizardly {feature} is one
	 that only a wizard could understand or use properly.