3 ms·

I'm inclined to look at tools like fossil again, for it's distributed issue tracking and wiki capability https://fossil-scm.org/home/doc/trunk/www/index.wiki h

• edgyquant 5y ago
  I had forgotten about that, thanks!
• JonChesterfield 5y ago
  Fossil is faultless for a team size of one. I've been using it for nearly a decade, doing totally non-optimal things like using versions released years apart on different OSs with the same database. I also ctrl-c it when I spot a typo in a commit message and check in binaries. Never missed a beat. As headcount goes up I think the inability to locally rewrite history into easily reviewable patches would be sorely missed. So it's git for team stuff and fossil for my own.