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! -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
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). -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
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 On 8/8/07, Zee Jay <rails-mailing-list-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org> wrote:> > > 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). > -- > Posted via http://www.ruby-forum.com/. > > > >--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Jason Roelofs 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. > > JasonThanks, 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). -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
On Aug 8, 2007, at 1:15 PM, Zee Jay wrote:> Jason Roelofs 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).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 Biedenharn http://agileconsultingllc.com Rob-xa9cJyRlE0mWcWVYNo9pwxS2lgjeYSpx@public.gmane.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---