Hello - I would like to get involved in the Rails Core development. What's the process for getting involved?
We've been working with Rails since 2006 and really enjoy the framework but have some reservations around Rails 3's REST implementation and exposed Java Script. The former seems to be an over reach for a framework and is an application specific architectural decision. The latter takes something that should be handled by the framework (wrapped and tested) and exposes it. Migrating one project, both have made working with the framework slower, more cumbersome and overly complex. These issues block a clean upgrade path. An upgrade path of 're-write' is not really acceptable for complex applications done for serious usages. We have 10's of thousands of line applications that eventually need to be upgraded. We need to make and bake some core changes to make this possible. This should not effect the current Rails implementation but enable simple, direct migrations and make the framework more flexible for new projects. I'm fairly certain in our case it's quicker (and safer) to make these changes to Rails proper than to rewrite our apps. Since I'm positive we're not alone on this front, we would like to share that work. It's not clear how to get involved on this level but I'm willing to chip in my 30 years of experience and that fancy degree achieved along the way to the cause. If someone could point me the right direction, it would be greatly appreciated. Thanks, TT -- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-talk/-/jy9VM2QQWSYJ. For more options, visit https://groups.google.com/groups/opt_out.
