Consider Fossil[1], which packages the entire repository state—code history, wiki, tickets, forum—into a single file, and that state gets cloned.
When/if you need to change hosting providers, you get to lose zero data in Fossil because of it.
When/if you need to change hosting providers, you get to lose zero data in Fossil because of it.
network effects. I just can not bring my team to use fossil. They have to share code with others. Other departments. And everyone (99%+) uses git. It just feels like a disservice to force them to use fossil. It is a catch-22.
It is similar to so many other things in the tech space. Trying to get fellow developers to use functional style idioms. Trying to enforce immutability. It is like something big (like a facebook or google project) has to force the community to get on board.