No description provided.
No, sorry, just reporting here... Please let me know if creating bugs without pull requests are discouraged and I'll stop sending them.
No. It is fine, but doesn't hurt ask for a pull request ;). Thank you for reporting.
Ok, sorry if I was rude. It is just that I didn't have a great experience trying to contribute to Rails in the past so it is unlikely that I'll spend a fair amount of time writing patches for Rails. I'd rather invest my time on other projects where it is usually easier for me to contribute...
What can be done to make it easier?
The problem is that I spent a considerable amount of time working on some feature and at some point I didn't get any feedback and the feature was closed due to inactivity, so it is more of a social issue than a technical one... The same thing happened to Gitorious a while back and I stopped contributing there too... Sorry, but I'm not too patient with regards to open-source so I prefer to invest my time in projects that respond faster to my pull requests...
@rosenfeld it's best to first ask if a feature is likely to get accepted. Also, pull requests with bug fixes are usually merged faster. New features can add value, but can also add maintenance costs, that's why it's harder to justify some of them.
I've asked for about that feature before implementing it. I just got no feedback about how to document it as the documentation would change for lots of helpers and they were not dry. I simply got no replies by that time...
Don't add sqlite3 to gemspec with -O on rails plugin new
@rosenfeld I've fixed the issue, thanks for the report!
thank you, very much, @drogus! Have a nice weekend! :)