Earlier quoted context omitted.
I still find this argument hard to follow. You have a person who wants to contribute code to you open source project, but that person is stymied by requiring an account on a service other than GitHub. What kind of people are you expecting to be doing drive-by code contributions and what kind of code quality are you expecting from them?
"I don't want to have to jump through hoops to contribute to your project". I've made a few OSS contribs that were fork, clone and edit locally (or edit online in one case), push, test, pull request. That was all, they took ~20 minutes, if that. Adding in "create an account", "figure out the new UI's method of forking/pulling", and "link myself to another random webservice that I'll only use once" is too much frictio…
One more point: although the contributions are not made for the recognition alone, a bit of it never hurts. We ended up with a badge system for https://community.rhodecode.com , where code contributors get rights to moderate discussions (since they ARE the core users of RhodeCode).