3 ms·
" You're already generating a gemspec for GitHub, why not using it for RubyForge?" Because then I first have to ask Tom to create new project for me. :) That'
by jamesbritt 17y ago
" You're already generating a gemspec for GitHub, why not using it for RubyForge?"
Because then I first have to ask Tom to create new project for me. :)
That's not a tremendous barrier, but with GitHub, whenever I get some code that looks like something I can spin off as a gem, it's almost frictionless to do it GitHub style.
That said, I have to give Joe a spin and see how it stacks up against Mr. Bones, which is what I've been using.
- djanowski 17y ago:-) Fortunately they changed their minds and gems are auto-approved now, so the barrier is still there, just a little bit easier to lift ;-) Again, GitHub rocks. We tried to create a simple script to make it easier for us to also deploy to RubyForge (mainly because of the username prepending and the --source). We'll be looking forward to your feedback, James!