No, seriously: I apply patches which fit the vision, do not break the reference implementation on BCC, and do not cost me time from things I value in life. Happy to have them. That is, ballpark, half of patches. (The most common reason for not taking a patch is that people break Rails 2 behavior when trying to bug fix for Rails 3. The second is sometimes patches generate work, and if a "I have reasonable project rates" email is less work, that is what I'll usually do.)
No, seriously: I apply patches which fit the vision, do not break the reference implementation on BCC, and do not cost me time from things I value in life. Happy to have them. That is, ballpark, half of patches. (The most common reason for not taking a patch is that people break Rails 2 behavior when trying to bug fix for Rails 3. The second is sometimes patches generate work, and if a "I have reasonable project rates" email is less work, that is what I'll usually do.)