Fossil
Fossil source code management system is the only realistic alternative to Git, and has had 15 years of development and testing. I now use Fossil.
Why Not Git or GitHub?
I don't think Git is bad, and GitHub was a major advance on SourceForge in the same way that SourceForge was a major advance on plain CVS. All my Fossil code is mirrored on GitHub, and it is a good place to search for existing projects.
However I wanted to find an alternative to Git and GitHub because:
- I could not convince GitHub to fix visual accessibility problems, and I had multiple team members with visual impairments. GitHub have billions in the bank, and I spoke to several very polite managers at length, but GitHub still refuse to implement years-old W3C accessibility standards. That's not acceptable.
- Even if you only ever use a git commandline, Git comes with a lot of pain... software developers much more skilled than me wrestle with Git and its complexities. It doesn't feel right to me that a development team should need to worry about losing work, or use an interface so complex that paradoy man pages look real!.
- Git is not an append-only, non-repudiable Merkle tree with strong crytographic guarantees, which is what I wanted. Fossil is exactly that.
- Git encourages merging of privately-maintained trees, or the 'bazzar' development model, which seems to me to be delaying discussion until after code is written. I wanted my projects to instead be a tighter 'cathederal-style' development community, with discussion happening as code is developed and all branches visible to everyone.
Then there are Git security issues. LumoSQL and Sweet Lies are EU-domiciled open source projects which focus on security, and:
- GitHub has US Cloud issues, and so should not be used in the EU
- Git actively encourages users to break the Merkle tree. Rather than an inviolate historical record, it's a curated version (especially with 'rebase')
- It is difficult to find the descendants of check-ins in Git. It is so difficult that neither native Git nor GitHub provide this capability, and you need to write code to crawl the commit log. This makes it hard to find what descendent code may have been affected by an upstream bug.
The Fossil website has a pretty balanced comparison of Fossil v Git that is much more comprehensive than what I have written here.
Work Done on Fossil
Before I could use Fossil, I needed some changes:
- Fossil was not then a commodity, off-the-shelf SCM, and I needed users to be able to just get it easily for their favourite operating system.
- Fossil only had one implementation. That made me uncomfortable with Git too. Why would we have a vital standardised data format with only one set of very complex tools that can read it?
So I invested significantly in Fossil, and these problems were fixed:
- I became a temporary packaging intermediary with the main distributions. This has been successful... recent operating systems all carry recent versions of Fossil, and this now appears to be self-sustaining. There was a lot of private community interaction to make this happen.
- I somewhat assisted Stephan Beal's libfossil to roar back into life as a second, completely independent implementation of the Fossil data model. Multiple implementations are really important and being a library means the world can have multiple front-ends alternatives to the official Fossil app. I don't want my projects locked into Fossil any more than Github, although I am perfectly happy with Fossil for now. libfossil is great insurance.
- I completed a privacy review of Fossil, and debated my proposal in public. Some of that involved discussion of privacy arcanae.
- After being accepted as a code contributor, I have made 31 commits to the Fossil tree so far
- I have made over 150 forum postings
Fossil as a LumoSQL Test Case
Not only is Fossil a better SCM for the needs of my projects, but it is also a very demanding test case for LumoSQL. Fossil is built on SQLite, in fact Fossil and SQLite are symbiotic projects, and Fossil is the one SQLite application all SQLite developers are guaranteed to use. If Fossil can run on LumoSQL without a problem, and potentially even with some advantages, then it will have passed a major milestone.