My FOSS Story
I wish there was a well-understood convention to opt out of "social coding".  A way to put up a project under an open source license (or CC0/public-domain) along with a notice that says effectively, "feel free to fork, but don't file issues or submit patches."<p>You can put that in a README, but people won't read it. Github won't let you disable  i̶s̶s̶u̶e̶s̶ ̶l̶a̶s̶t̶ ̶I̶ ̶l̶o̶o̶k̶e̶d̶ pull requests, unless you archive the project (making it read-only).  Is it possible on one of the other hosting services, like Gitlab?<p>We need better ways to draw boundaries around open source projects and contributors.<p>ETA: How can we counter the <i>Bullshit Asymmetry Principle</i>? <a href="https://en.wikipedia.org/wiki/Bullshit#Bullshit_asymmetry_principle" rel="nofollow">https://en.wikipedia.org/wiki/Bullshit#Bullshit_asymmetry_pr...</a><p>> <i>The amount of energy needed to refute bullshit is an order of magnitude bigger than to produce it.</i>