Code, conflict, and conduct

Posted Sep 21, 2018 2:12 UTC (Fri) by tedd (subscriber, #74183)
In reply to: Code, conflict, and conduct by mtaht
Parent article: Code, conflict, and conduct

You don't think 1/3 is statistically significant?

to post comments

Code, conflict, and conduct

Posted Sep 21, 2018 14:10 UTC (Fri) by jwarnica (subscriber, #27492) [Link] (1 responses)

It is, but then, why are they "afraid" of rejection?

"Good enough to work", "good enough to ship" and "good enough to be included upstream" are three different technical thresholds. It is quite possible that many or most people "afraid of rejection" are aware that their code isn't up to the required quality.

Code, conflict, and conduct

Posted Sep 23, 2018 3:30 UTC (Sun) by giraffedata (guest, #1954) [Link]

"Good enough to work", "good enough to ship" and "good enough to be included upstream" are three different technical thresholds.

Don't forget "good enough to be accepted by whoever's in charge of upstream," because that's not the same as "good enough to be included upstream." A potential contributor may be afraid that his perfectly good work would not be acknowledged as such. Thus, it could be a truly emotional "afraid" based on lack of validation by another human being as well as a practical "afraid" just meaning you don't want to risk wasting your time.

I had many patches I thought were great rejected by various projects - some just ignored, others explicitly rejected, which led to a decision many years ago just to keep my code to myself from now on.