Thoughts on Fossil support?

[rpdillon]

nb's support for git is an awesome feature. Fossil is another SCM that provides most (all?) the features git does, and adds a bit more. It's trivial to self-host, even on shared hosting with CGI, and, with only a single executable, offers a web interface to the repository, complete with markdown rendering and searching. Fossil also supports "auto-sync", which automatically propagates commits to remotes, and those remotes are as easy to host privately as publicly. Overall, I think the philosophy behind nb and Fossil is quite aligned.

Fossil's ability to easily host an auto-syncing private repository that renders markdown notes is useful to provide web access to notes, and also allows Termux users on Android to both sync notes through fossil, as well as render the entire fossil ui locally on-device using fossil ui.

Given that background, I'm wondering what folks think about adding support to nb for Fossil. I haven't read through the source code for nb yet, so I'm asking about both how complex folks think this might be, as well as whether others would find this feature useful at all. I know I would, but I don't think I'm necessarily a representative user.

If there's real interest, I'm happy to take a stab at it, but I thought I'd ask here first.

[xwmx]

@rpdillon Interesting idea. Fossil is pretty cool. Most of the git functionality in nb is contained within the git subcommand, with some additional functionality in remote and sync. It's very conceivable that this could be implemented by developing a fossil subcommand in a plugin that mirrors the git subcommand functionality. There is a related open issue about disabling git (#97).

[gour]

I'm a Fossil user myself and would like to see support for it as well as #97!