There's BS and cool on both sides of PRs. - MYOB fail, as mentioned, sigh. - Closing issues before they're resolved. Proper etiquette is to let the filer clos

There's BS and cool on both sides of PRs. - MYOB fail, as mentioned, sigh. - Closing issues before they're resolved. Proper etiquette is to let the filer close it after it's fixed and working. - People demanding features or making vague trouble reports. - Submitting a properly-tested PR that fixes an issue without need for a fix-it issue. - Committers open to some globally-beneficial change only to change their mind after it's already done. - People refactoring your commit with something better. - Rust and a lot of small languages have tiny, good communities of generally humble badasses. - People changing whitespaces or switching to British grammar. SMH. I look at it this way: you gotta take the shit with sugar. Not trying to contribute upstream is consuming without producing... I'm against this because it helps no one and it's uncool.