3 ms·
Part of the cause, I suspect, is that the Rails Trac (http://dev.rubyonrails.org/ http://dev.rubyonrails.org/) has a rather strict policy. Unlike, say, Firefox
by ken 19y ago
Part of the cause, I suspect, is that the Rails Trac (http://dev.rubyonrails.org/ http://dev.rubyonrails.org/) has a rather strict policy. Unlike, say, Firefox's or GNOME's Bugzilla, where a feature request with a halfhearted patch can stay open for years, the Rails folks will immediately close ("WONTFIX") any feature request that doesn't also contain a working patch, documentation updates, and unit tests.
The upshot of this is that I've contributed many patches to GNOME, but none to Rails. If I come up with something useful, I'll blog about it so others can see, and then let it go. The entry barrier to get it in Rails is just too high.
I suppose I could make it a plugin, but a lot of these things seem like they should really be in Rails itself, so trying to factor them out to be a usable plugin is just a different kind of pain.
- jrockway 19y agoWhy do features need to be in the core? Why can't you just make a gem or something available? For Catalyst, we have the same policy. Send us some random patch with no tests or docs and there's no way it will ever see core. However, we are very successful at getting people to resubmit with docs and tests. But usually, the patch to core doesn't need to be a patch to core, it can be Some Other Module.
- rsanheim 19y agoIf you don't care enough to write tests or clean up your code, why would anyone else? If you just want to throw out a proof of concept, a blog or paste site is really the best place for it.