Cameron McBride
5/18/2009 8:58:00 PM
On Mon, May 18, 2009 at 15:38, Joshua Ballanco <jballanc@gmail.com> wrote:
> On May 18, 2009, at 4:20 PM, Cameron McBride wrote:
>
>> btw, there is already a rubyforge project (sciruby) that I started
>> with similar ambitions. =A0Initially, it's intention was just to provide
>> a separate "science centric" list for ruby discussions to augment Ara
>> Howard's sciruby wiki (which seem to have evaporated). =A0 The list
>> still exists, albeit the traffic is *very* light. =A0 I encourage any
>> interested party to sign up!
>>
>> In any case, it could easily be the connective bit to provide the
>> "distribution" gems. =A0Or to officially house anyone's original code
>> they don't want to publish separately. =A0 =A0Other suggestions are quit=
e
>> welcome.
>
> That sounds like a great idea. Probably the first thing I'm going to do i=
s
> figure out some simple rake tasks to add new libraries/projects and wrang=
le
> the indexes in interesting and useful ways. As I mentioned in the
> announcement, the idea is not for this to be a project in its own right, =
but
> rather to serve as a gathering place for other projects. In keeping with =
the
> tradition that github is for "in development" and rubyforge is for "relea=
sed
> to public", I think the sciruby project on rubyforge would be a perfect
> place to put gem(s) and hold discussion. In fact, since GitHub doesn't
> provide for mailing lists, I've added a link to the sciruby project on th=
e
> RubyScience wiki (and I'll update the README shortly).
I agree, very complementary approaches. Let's have a run at it.
If you (or anyone else interested in helping) want access to the
rubyforge project, just let me know.
Cameron