1) people that start a serious open source product must be self-assured and innately isolated from any external community/pressure in order to avoid distractions from their goal. Shame has likely 0 effect, or negative (i.e. the person/group doing the shaming would get banned from any future interaction). It takes a certain type of person that is likely "very thorny" to the outside world unless persuaded by desired qualities in other people that want to interact.
2) those projects often start as angry reactions to what is happening in the outside "meatspace" (corruption, vendor lock-in, "voluntary" censorship, you-can-buy-everyone, selling underwhelming/dangerous stuff for a lot of money etc.); doing things differently when they start working inevitably invokes feelings of superiority over people that "just don't get it"/"noobs" and it's difficult to resist temptation of showing off. Or external people are viewed as "conformists to old ways" that would prevent better things from happening in order not to disrupt current status quo they benefit from, hence interacting with them is not desirable (and arguably dangerous until project really makes it)
3) having to wade through a lot of new issues daily and cherry pick the ones that are worth examining is time consuming and tiring. After doing this for a while it likely leads to anger and telling off someone is a way to vent
4) popular free/open source projects that made it are often targeted by people trying to subvert them for their hidden agendas; any original developer intelligent enough can be at least disturbed if not outraged by that; harsh reactions following. "How would you punish those subverters?" is a better question than to penalize a developer that was easily provoked to an angry outburst by those poking at their weak areas (and that's often trivial with honest technical folks)
5) priority of creators is often getting things done as fast as they could; "unnecessary social talk" is often viewed as a waste of effort/time, and honestly it often is, unfortunately. If they decide that at some point "talking nice" is leading to being more efficient, they would do work on it, but not before they perceive it that way.
6) Many junior developers think that they are entitled to some coding celebrity's special attention instead of taking the hard way, improving themselves and then contributing when they are finally able to.
I may not have made myself clear, I'm already convinced that either vision of Shame-Driven Development was a bad idea. That being said, thanks for your thoughtful reply!
1) people that start a serious open source product must be self-assured and innately isolated from any external community/pressure in order to avoid distractions from their goal. Shame has likely 0 effect, or negative (i.e. the person/group doing the shaming would get banned from any future interaction). It takes a certain type of person that is likely "very thorny" to the outside world unless persuaded by desired qualities in other people that want to interact.
2) those projects often start as angry reactions to what is happening in the outside "meatspace" (corruption, vendor lock-in, "voluntary" censorship, you-can-buy-everyone, selling underwhelming/dangerous stuff for a lot of money etc.); doing things differently when they start working inevitably invokes feelings of superiority over people that "just don't get it"/"noobs" and it's difficult to resist temptation of showing off. Or external people are viewed as "conformists to old ways" that would prevent better things from happening in order not to disrupt current status quo they benefit from, hence interacting with them is not desirable (and arguably dangerous until project really makes it)
3) having to wade through a lot of new issues daily and cherry pick the ones that are worth examining is time consuming and tiring. After doing this for a while it likely leads to anger and telling off someone is a way to vent
4) popular free/open source projects that made it are often targeted by people trying to subvert them for their hidden agendas; any original developer intelligent enough can be at least disturbed if not outraged by that; harsh reactions following. "How would you punish those subverters?" is a better question than to penalize a developer that was easily provoked to an angry outburst by those poking at their weak areas (and that's often trivial with honest technical folks)
5) priority of creators is often getting things done as fast as they could; "unnecessary social talk" is often viewed as a waste of effort/time, and honestly it often is, unfortunately. If they decide that at some point "talking nice" is leading to being more efficient, they would do work on it, but not before they perceive it that way.
6) Many junior developers think that they are entitled to some coding celebrity's special attention instead of taking the hard way, improving themselves and then contributing when they are finally able to.