I agree really strongly with 99% of this. I make a fairly niche command-line application, and I'm convinced that it would have exactly zero users if I didn't pu

I agree really strongly with 99% of this. I make a fairly niche command-line application, and I'm convinced that it would have exactly zero users if I didn't put as much time into documenting it as I do. I think the GitHub stats make this point fairly well: Pushed 79 commits to h2s/ppl Apr 14 - Apr 20 Pushed 34 commits to h2s/ppladdressbook.org Apr 14 - Apr 20 That's almost a documentation commit for every other commit to the application itself. It's a lot of work, but seriously, what's the fucking point otherwise? I also agree about abandonware. I keep encountering this, and it's pretty tiresome. Somebody built some well-received little tool a year or five ago, and for a time they loved it. Now they're bored of it, and they make just enough of a token effort to sustain the project to temporarily fool you into using it. I even have a different project of my own that's starting to creep into this territory. Hopefully I will not make a hypocrite of myself when the time comes. The only thing I don't agree with particularly is this. > Make sure the title starts with ANN or [ANN] to > indicate that it is an announcement, e.g. > ANN Welle 1.5.0 is released This seems an oddly specific recommendation to be making. We're doing Hungarian Notation for project blog post titles now? Anyways, that minor thing aside, I think this is an absolutely excellent primer for anybody considering starting an open source project. If, while reading this, you find yourself thinking "How silly, ain't nobody got time fo' dat", then you're probably starting out your project with quite a low ceiling on its potential usefulness.