Why SQLite Does Not Use Git

"Nobody really understands git" is the truest part of that. While hyperbolic, it really has a lot of truth. It's always a bit frustrating when working with a team because everyone understands a different part of git and has slightly different ideas of how things should be done. I still routinely have to explain to others what a rebase is and others have to routinely explain to me what a blob really is. In a team of the most moderate…

"When I want to see what has been happening on SQLite, I visit the timeline and in a single screen I see a summary of the latest changes, on all branches. In a few clicks, I can drill down as much detail as I want. I can even do this from a phone. GitHub and GitLab offer nothing comparable. The closest I have found is the network, which is slow to render (unless it is already cached), does not offer…

I’ve tried Fossil a number of times, but several oddly-rigid aspects always manage to turn me off. Take, for example, the integrated bug tracker, which is novel and a big draw for me. Say I write up a bug and then notice an error in the description… I can’t edit it! I can merely append more comments, which also can't be edited or removed. The recommendation I found was that I should close (there's no delete!) the bug and create…

One thing to remember while reading all that is that SQLite is not open contribution. You cannot submit PRs with Fossil. You can’t fork the code and share with others without standing up your own server.