GitHub Gem Import

I have nearly readied the GitHub gem import, hopefully once this is in then I will setup the Gem imports to run on an automated basis once every few hours, to make sure we have the latest gems ready for review.

One question on my mind, while I really think we should have GitHub gems in here, will it dilute the data? Will it be confusing to see that davidsmalley-eventmachine doesn’t work while bobjobs-eventmachine does work? I am slightly worried that it might dilute the overall impression we get of Ruby 1.9.1 compatibility. Are there any features that can help overcome this or should I just go ahead and get the data imported already :)

Not sure. Do we think the majority of gems on github are forks of stuff on Rubyforge? Or are they mostly original projects?

We could attempt match up github gems with rubyforge gems as display them as forks, or related projects, that are possibly displayed differently? Maybe not even showing those github gems in the search directly? They’ll be false positive, though few.

Maybe just a “Github” prefix will be enough for now to clearly identify them, possibly boosting the relavancy of Rubyforge gems slightly so they show up higher in the search if they both have equal term matches? (easy to do with Ferret)

Personally, I’d like to see GitHub gems displayed specially – have the same features for GitHub fork as you do for version number.

That is, for gems pulled from GitHub …

• Attach it to the non-GitHub-username-prefixed version
• Allow commenters to chose from a dropdown which GitHub username, or RubyForge, they installed from

@elliottcable that’s a good idea. We’re looking in to how best to do this and hopefully we’ll have something live soon.