From: Cameron McBride <cameron.mcbride@...>
Date: 2009-05-19T06:42:46+09:00
Subject: Re: [ANN] Introducing RubyScience on GitHub!

On Mon, May 18, 2009 at 15:49, Juan Zanos <juan_zanos@talkhouse.com> wrote:
> On May 18, 2009, at 3:27 PM, Joshua Ballanco wrote:
>> In the tradition of actions vs. words, I present to you:
>>
>> RubyScience - A Collection of Ruby Science Libraries and Projects
>> http://github.com/jballanc/RubyScience
>>
>
> I like the git idea a lot.   Last year I ported a Ruby science library to
> Ruby 1.9, made it into a gem, sent the changes to the maintainer and nothing
> became of it.   Not the maintainers fault.  He was just too busy.   If it's
> distributed that's just not a problem.

This is a neat idea; basically to wrestle unmaintained or
not-quickly-updated libraries into the useable limelight.  This alone
could be a fantastic accomplishment worthy of the project.

But I'm not clear on logistics.  Is the idea to import other peoples
code into github if they don't already exist there?  That seems like a
lot of work, not just initially but also to keep up with releases.

The other problem is what would constitute a pseudo-official
"release"?  Whose fork or repo would incorporate other efforts or
resolve which of two different forks of, say, ruby-gsl to include?

Maybe the github community has acceptable solutions for these
situations.  I haven't followed the social aspect of github at all.

Cameron