4 ms·
Practical aspects aside, having issue tracking in the repo prevents lock-in of that data - in the way that the github platform works, for example.
by kzrdude 6y ago
Practical aspects aside, having issue tracking in the repo prevents lock-in of that data - in the way that the github platform works, for example.
- Midar 6y agoThis is exactly what intrigued me and made me switch to Fossil. I don't want to have my issues, wiki etc. held hostage by some company. And if someone wants to fork it, they should be able to fork it including issues and wiki.
- mekster 6y agoSelf host Gitea?
- ncmncm 6y agoI was astonished and appalled to find that your Github bugs, wiki, and PRs were not all in your repo.
- m463 6y agoI think you can sync the wiki if you want: git clone https://github.com/project/name would have a wiki: git clone https://github.com/project/name.wiki I don't know if this is a special setup or not. Will they remove this? Are there ways to get to other stuff?
- nix23 6y agoI use fossil mostly as a Customer/Project KB/Documentation tool, when a new project starts i have all the documentation, code snippets/examples in one single file, when the project is finished, i have to give one sqlite.db file over to the customer and that's it. LOVE IT, a really great tool!