I first thought about creating a feature request on LightHouse, but then: "Creating a feature request
Please don't. If you want a new feature in Rails, you'll have to pull up your sleeves and get busy yourself. Or convince someone else to do it. See the contributor guide on how to get going. But posting them here is just going to lead to ticket root." But that is the problem: I would like to ask for some high-level documentation about Rails internals to easy contributions from others than the core team. But how could I pull up my sleeves if I don't know how Rails internals work so that I could write the documentation? Rails has method and code snipets documentation. But if one tries to understand how Rails initialize itself and its dependencies, how things are structured, what is the Rails way for writing internal code, how class reloading works in development mode and other high level stuff, he/she will need to dive into a lot of code to try to figure it out by himself/herself. This makes it very hard to get new contributors to Rails core since it seems every railer is busy and chances are small that they have enough time to figure out the Rails internals by themselves so that they can contribute small changes. There are a lot of plugin contributions since its documentation is well written. I think there could be more contributors if we had a README.internals that explained the whole idea about how Rails is structured and the reasons behind it. Then, each major update to Rails internal structure could be reflected in this document... I was just trying to add a :full_message parameter to validations, so that I could prepare a patch to LightHouse, but was stuck trying to figure out how ActiveRecord is loaded, how Validations are included in ActiveRecord without being required (when I discovered they are autoloaded), what are the differences between ActiveModel and ActiveRecord and several other doubts. It would be much easier if such a README.internals document exists. I spent about 2 hours doing really nothing useful to Rails itself, while I could use this time to actually write a useful patch... I would like to know what is the Rails core team opinion about that. Thanks, Rodrigo. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
