Realistically, though, the better choice for small teams is going to be gitlab or github.
Using anything that isn't "boring technology" is going to introduce unnecessary friction and effort, which would be better spent on creating the product, especially given small team size.
Yeah, I'd be wary of using something other than git because if you hire a new graduate, there's a much higher chance that they'll have used Git (and most likely GitHub too) than that they've used Fossil. And most repositories outside your company that you ever need to interact with are most likely Git too.
Comments
Realistically, though, the better choice for small teams is going to be gitlab or github.
Using anything that isn't "boring technology" is going to introduce unnecessary friction and effort, which would be better spent on creating the product, especially given small team size.
Yeah, I'd be wary of using something other than git because if you hire a new graduate, there's a much higher chance that they'll have used Git (and most likely GitHub too) than that they've used Fossil. And most repositories outside your company that you ever need to interact with are most likely Git too.
It's easy to import and export to git: https://fossil-scm.org/home/doc/tip/www/inout.wiki
I argue this would come under
Git does seem to be that.
Or gitea if you want a self hosted option that is lighter and less effort to use than gitlab.