Oh, I used Fossil as my only VCS for 3 or 4 years.  On my biggest projects, I had a heavily tweaked ticketing system and probably a hundred wiki pages.  My experience with Fossil wasn&#x27;t a &quot;well the defaults suck, next thing&quot; kind of situation for me, I was pretty invested in it.<p>I also ditched it all 3 or 4 years ago, so my memory&#x27;s not great, but what got me about the ticketing was that, for whatever reason, I could not sit any non-technical user in front of it and have it make sense to them.  No amount of tweaking ever made it make sense for anyone but the devs.  I know that&#x27;s not specific, but this is all in the pretty distant past for me, and that&#x27;s the takeaway I had from it.<p>Fossil&#x27;s lack of any built-in emailing was also lousy.  I&#x27;m aware that some people rig up some hokey RSS-to-email system to accommodate that, but really, come on, that&#x27;s awful!<p>Hey, if fossil actually serves your needs, that&#x27;s great.  I like the value proposition--one file is your repo, wiki, tickets, the whole ball of wax, it&#x27;s cross-platform, it&#x27;s just that the execution of the idea didn&#x27;t work for me.<p>(As an aside, another thing I didn&#x27;t like about fossil was its community--tending toward defensiveness and &quot;it&#x27;s supposed to work that way&quot; instead of &quot;hey, maybe you, the user, are onto something&quot;.)