>> ld argue strenuously against loosening this policy. Given that >> there have been over 1400 contributors to Rails so far, I think we >> have pretty good evidence that this policy is not too restrictive or >> onerous. >> > > I think this works great for new features or bug correction patches. > But > for small changes aiming at code cleaning or correcting method or > variable mispellings, this would be too much in my opinion.
You'd be wrong, frankly. If you dig through the Rails commit history, you'll find patches as small as one character. ... > > >> Or you could join us at the next BugMash (September 26) when >> experienced Rails developers and core committers will be available to >> help get you over the initial hurdles towards contributing. >> > > I would like to but the BugMash is target only to bugs. I'd prefer to > work in the :full_messages patch if it is possible. > This is also wrong. The BugMash targets cleaning up the patch queue in general. Mike --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
