RubyForge in Ruby?

On Jun 24, 2006, at 2:00 AM, M. Edward (Ed) Borasky wrote:

overwhelmed by all the “features” in GForge. How many projects are big
enough to use them? For that matter, how many projects on RubyForge
have
more than, say, three developers?

The closest I’ve seen to what I’d call an “agile” software project
management web app is Trac … but that’s in Python, right? :frowning:

Amen brother, amen!

I think sometimes a little reinvention can be a healthy thing. You
get to rethink the elements that make something what it is.

Obviously Trac is missing a couple of things needed to replace
GForge, but I agree that it’s a lot closer to my ideal.

James Edward G. II

On 24-jun-2006, at 23:06, Ryan D. wrote:

Or you could quit being a drama-queen and be a bit more realistic.
It was not my intention to insult anybody. A very odd response, if I
might say so.

Not counting login it takes exactly 1 form to create a new release
including uploading the file.
Shall the file be one. If they are many though… (and a normal
release usually has at least two)

Currently there are like 3 different Rake tasks for publishing
gems (all of them UNOFFICIAL) and I had problems with all of these.

That has little (if anything) to do with rubyforge itself.

Uhm… Let’s say that I don’t agree but as you are in the mood of
name calling I will just shut up.

On 6/24/06, James Edward G. II [email protected] wrote:

slippery values of @something, @that and @work. And a little voice
Amen brother, amen!

I think sometimes a little reinvention can be a healthy thing. You
get to rethink the elements that make something what it is.

Obviously Trac is missing a couple of things needed to replace
GForge, but I agree that it’s a lot closer to my ideal.

James Edward G. II

It wouldn’t need to be done from scratch, Bounty Source is written in
Rails
and has been open sourced:

https://www.bountysource.com/

Curt

On Jun 24, 2006, at 2:29 PM, Julian ‘Julik’ Tarkhanov wrote:

On 24-jun-2006, at 23:06, Ryan D. wrote:

Or you could quit being a drama-queen and be a bit more realistic.
It was not my intention to insult anybody. A very odd response, if
I might say so.

If you’re going to exaggerate things out of proportion, I’m going to
call you on it.

Not counting login it takes exactly 1 form to create a new release
including uploading the file.
Shall the file be one. If they are many though… (and a normal
release usually has at least two)

Your original words:

  1. you have to click ten forms in a row just to publish one
    gawddamn file

Currently there are like 3 different Rake tasks for publishing
gems (all of them UNOFFICIAL) and I had problems with all of these.

That has little (if anything) to do with rubyforge itself.

Uhm… Let’s say that I don’t agree but as you are in the mood of
name calling I will just shut up.

Disagreeing with me is just fine. My latter point was that having
problems with the rake tasks has more to do with their implementation
than it has to do with rubyforge itself.

Welcome to the internet. Here’s your thicker skin.

On Jun 24, 2006, at 10:51 PM, Curt H. wrote:

It wouldn’t need to be done from scratch, Bounty Source is written
in Rails
and has been open sourced:

https://www.bountysource.com/

That’s a neat sight. Thanks for sharing!

James Edward G. II

On 6/24/06, Julian ‘Julik’ Tarkhanov [email protected] wrote:

I am talking about something completely different. What I am talking
about is making the release of a rubygem/tarball to rubyforge not
500% painful as it is now, because:

  1. you have to click ten forms in a row just to publish one gawddamn
    file
  1. your only option if you want to avoid the n. 1 is to write a
    script that clumsily simulates the No 1 and breaks every other minute.

Currently there are like 3 different Rake tasks for publishing gems
(all of them UNOFFICIAL) and I had problems with all of these.

Which ones have you tried? Have you tried the variants in Net::LDAP?
Those are modern modifications to what I used in my last release of
PDF::Writer and are more reliable than any other form that I’ve used.

It literally takes about thirty seconds or so to publish to RubyForge
when you use this sort of thing.

-austin

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs