days
1
1
hours
1
9
minutes
4
1
seconds
3
8
Ruby on Rails

It is time that you gave back.

Jessica Thornsby

900+ Open Tickets for Rails 3

Ruby on Rails evangelist Ryan Bigg has posted a blog that spells out why Rails 3 is taking so long: because there are over 900 open tickets still open and no-one is doing anything about it.

Bigg uses the analogy of waiting in line at the supermarket, and the cashier’s till drawer breaking and scattering coins everywhere. Do you help the cashier pick them up, or do you stand there and wait?

“Well, in this analogy, you sit back and let the cashier do it all. All of you in the queue do. Nobody helps the poor cashier,” Bigg writes, because the people in the queue are people in an open source project’s community, what they’re queuing for is “The Next Big Release,” and the dropped coins are bug tickets.

Ruby on Rails is “suffering because of your ignorance,” Bigg continues. “It is time that you gave back.”

He cites being a Rails novice as a frequently-used excuse for developers failing to take their pick of the 900+ bug tickets currently wanting some attention. Bigg then chooses a bug ticket and walks the developer through dealing with it, stating that if it cannot be fixed by you alone, you can always find someone willing to lend a hand.

Biggs sees a worrying amount of the open source community grumbling “it’s been so long between releases,” instead of wondering why it’s been so long between releases and – crucially – how they can help speed up that release.

Author
Comments
comments powered by Disqus