swift-http-import

> This README was generated with <3 by readme-md-generator No, it wasn't. This is the antithesis of love. This is what "lovingly" hand-crafted READMEs look like: https://github.com/sapcc/castellum https://github.com/sapcc/swift-http-import None of that templated "please star if you like this" bullshit (your project's README is NOT the place to be explaining GitHub's UI), but all of the information that people actually need to use the program. I just can't stand this phony corporate bullshiting about how "we at $ANONYMOUS_CORPORATION are your friends and want to help you succeed" that's just a plain lie everytime. It seems to be an American thing. When I interact with American managers, they're all about "being passionate about X" or whatever. The German managers are much more focused on the actual tasks, i.e. boring in all the good ways.

> I enforce high-quality release notes like you describe. Representative example: https://github.com/sapcc/swift-http-import/blob/master/CHANG.... (note that this also takes SemVer seriously) Nitpick: you are not using SemVer. A normal version number MUST take the form X.Y.Z where X, Y, and Z are non-negative integers, and MUST NOT contain leading zeroes. X is the major version, Y is the minor version, and Z is the patch version. Each element MUST increase numerically. For instance: 1.9.0 -> 1.10.0 -> 1.11.0.[1] [1]https://semver.org/#spec-item-2 Some of your version numbers lack the patch version.

God yes! For the apps that I maintain (and which have users outside my team), I enforce high-quality release notes like you describe. Representative example: https://github.com/sapcc/swift-http-import/blob/master/CHANG... (note that this also takes SemVer seriously)

> you were likely broken (or using a specialized build tool that handled this for you) Or you're using the isolated-GOPATH trick. $ mkdir -p .gopath/src/github.com/foo $ ln -s ../../../.. .gopath/src/github.com/foo/bar $ GOPATH=$PWD/.gopath go install github.com/foo/bar For example, this is one of my Go projects where you can unpack the release tarball anywhere and `make && make install` just works: https://github.com/sapcc/swift-http-import

I'm trying to make a habit of adding a "Do NOT use if..." section near the top of my projects' READMEs whenever there are simple exclusion criteria. For example https://github.com/sapcc/swift-http-import#do-not-use-if -- This particular instance was born out of watching users bending over backwards to use the software even though standard software does the job just fine or better in their concrete case.