3 ms·

There are a lot of other angles we can look at this as well: The user ("I need.."), The cocky contributor ("This is right, accept my pull request!"), The belitt

There are a lot of other angles we can look at this as well: The user ("I need.."), The cocky contributor ("This is right, accept my pull request!"), The belittled contributor ("I'm not sure.. but let me try.."), The helpful leader ("I can't accept this because it will break xyz.") The douche leader (As the article stated: "LOL!"), and the cocky leader ("No, that's wrong." - And then they realize later it's actually right, but they're attitude made them not look at a worthy contribution in the right light correctly.) The article makes a good point - But there's a lot more we can take out of this, that being that for any community to succeed, it needs to be just that: A community. A place where others help each other grow.

christkv 14y ago
Sometimes it's hard because reminding someone who sends you pull request about the projects contributor guidelines sends them off in a huff and even though they pull "might" be good in that it does not break any tests it's hard to know what scenario it's guarding against or if the person is doing something strange in their code. The cocky contributor is usually a bad contributor in my experience and are both energy drains and time sinks. The belittled (or humble) contributor is the one I am that I really appreciate and value as they are willing to enter into a dialog about what needs to be in the pull request to get it in. In the end is all about normal human social decency. Treat people badly and don't be surprised when they treat you as a leper.