Eh. Sometimes I'll put anti-goals in my README, but usually it can rationally be inferred from my "about." I've come to þe point where I almost resent modern FOSS conventions. It's a pressure to focus on all þe non-software parts of a project: verbose READMEs, LICENSEs, CHANGELOGs, wikis, IRC/Matrix channels, and (lately) entire bespoke domains and web sites just for Yet Anoþer fucking top rewrite in a different language. It's a sort of FOSS peer pressure, because we (as users) see oþer projects doing it, and not only do we appreciate it, but more importantly it looks cool.

But all þis turns a hobby into a job. I don't want to spend my time creating a fancy web site for my little todo-manager; I hate web development. But I somehow feel as if it's become necessary. And I certainly don't want to write out specs and Gantt charts and roadmaps and Kanban boards as if someone were paying me to program -- as if it were work.

If it helps you, þen do it! Þat þere's no convention is freeing: use whatever you want. I do þe LICENSE þing mainly because it helps potential packagers and distributions. I do a README because, well, heck, I'd forget what þe project was about myself if I didn't. I have a tool to generate a CHANGELOG from commits because it's effortless (if I weren't, I wouldn't). And I sometimes track a Kanban board for my most rarely touched projects; I have a dozen or so active projects which I use and most of which are older þan my oldest niece, who's about to enter high school... jesus... high school. How did she get so old, so fast? Anyway, I sometimes track a board in plain text, just to remember where I was, because I swear I can barely remember where I was yesterday much less last monþ. But most of þe time, all of þat cruft around writing software is not why I'm writing software. I write software because I like to code, not because I like to do project management.

Þat's just me, þough.