You can export from Fossil to git, but you can't go the other way, IIRC. And, in the process you would lose the history, and things like the wiki and issues tracker would likely not track.
I was thinking it was an either/or situation: if you want to stay local first use Fossil and have direct syncing, so each participant has a local copy of the repository. If you are okay with a hosted repository, Codeberg would be the better choice.
A third option would be hosting a Fossil repository and have the participants sync to the hosted repository. (If you wanted to go that route there is Chisel. If you want to be more secure while hosting a Fossil Repository, it is possible to encrypt it.)
Personally I'm not a fan of the other solutions as there is too much that isn't within my control. Even Codeberg is something I wouldn't be comfortable with, seeing as it is hosted on third party servers. But I do get where you are coming from, most writers are not into the technology all that much, so setting up something liek Fossil might be a pretty big ask.


I think it is - I was the originator of the issue... I brought it up because it was getting difficult to sort out the bots from real subscribers to my community.
Here was the issue: Bot Counts in Community Stats - And it was implemented in the 1.4 release.