Which module needs most work?

Rails
1

Hi,

I have some time to spend on anything at all and figured that I’d try to
help out the Ruby/Rails community. If all goes well, this will both
improve the Rails environment and add to my list of accomplishments.

So, which parts of Rails or Ruby in general need improvement
(performance optimization, code refactoring/cleanup, etc)? And, what is
in most need of improvement or is the most difficult or tricky problem
to solve? Also, any gaps in the implementation for new development are
fair game too.

After receiving the submissions, I will pick my favorite idea and code
away.

Thanks in advance for all your ideas!

2

Zee Jay wrote:

Hi,

I have some time to spend on anything at all and figured that I’d try to
help out the Ruby/Rails community. If all goes well, this will both
improve the Rails environment and add to my list of accomplishments.

So, which parts of Rails or Ruby in general need improvement
(performance optimization, code refactoring/cleanup, etc)? And, what is
in most need of improvement or is the most difficult or tricky problem
to solve? Also, any gaps in the implementation for new development are
fair game too.

After receiving the submissions, I will pick my favorite idea and code
away.

Thanks in advance for all your ideas!

Should I take the lack of responses as a sign that everyone is too busy
to reply or that Ruby/Rails doesn’t need improvement or additional work?
I know it can’t be the latter because everything can be improved (and
beside that, I remember reading numerous articles stating that the
performance of Ruby/Rails is even slower than Java).

3

Jason R. wrote:

http://dev.rubyonrails.org/

Find open tickets and submit patches to them. Rails has grown immensely
from
people finding optimizations / bugs / feature improvements and
submitting
patches. The only list per-say of what can and needs to be done is at
dev,
no single person keeps track of everything that can / could be done.

Jason

Thanks, and that helps alot! But, I was really wanting input from
people who use Rails daily on which are the most important or difficult
tickets to consider (or maybe even something that hasn’t been submitted
to the ticket system yet).

4

http://dev.rubyonrails.org/

Find open tickets and submit patches to them. Rails has grown immensely
from
people finding optimizations / bugs / feature improvements and
submitting
patches. The only list per-say of what can and needs to be done is at
dev,
no single person keeps track of everything that can / could be done.

Jason

5

On Aug 8, 2007, at 1:15 PM, Zee Jay wrote:

no single person keeps track of everything that can / could be done.

Jason

Thanks, and that helps alot! But, I was really wanting input from
people who use Rails daily on which are the most important or
difficult
tickets to consider (or maybe even something that hasn’t been
submitted
to the ticket system yet).

First of all, do not let me dampen your enthusiasm at all.

Now, I’d much rather have tickets and patches done by someone who’s
directly interested in that area of Rails. If you haven’t used Rails
enough to have some opinion on this yourself, then jump into the
existing tickets and find one that interests you. Add tests. If the
documentation is sketchy, clean it up with a documentation patch
(which is just RDoc anyway).

There’s no sense seeking out places to tweak when there are so many
tickets already that others have taken the time to create. For some,
they may not have the skill to create the failing test cases that
demonstrate the desired change to the system. If you can give a
patch for the new tests separate from the patch that fixes the code,
even better!

-Rob

Rob B. http://agileconsultingllc.com
[email protected]