> It’s open to objections: first, Github does this already, so it’s a solved problem
No, you're misunderstanding the feature (or they don't explain it well). GitHub solves the problem on their platform yes, but not in the protocol (git) itself.
Fossil embeds that data in the repository, all the data is local. Fossil works perfectly with the "local first" doctrine, something Git also does, but not for everything around Git, that Fossil embeds into the repository.
Basically, Fossil is Git + GitHub but self-hosted and offline first. You pull down a Fossil repository is like pulling down the Git repository + all related GitHub data.
> Why would VCS experts be good at designing a compelling forum or ticketing system?
They don't have to be experts about something to make it good enough. For a lot of us with poor internet connectivity, the offline first doctrine is essential in a lot of the work we do, as internet can disappear at any notice. Fossil works much better for this, as I can still read the wiki and tickets when my internet drops, while if I were using GitHub, I'd have to results to writing my own code/use 3rd party software to get the same experience.
I don't find these arguments persuasive. My point was that if I want wiki, ticketing etc., I can get it right now on an industry standard platform. Yes, I get that they embed it in the software itself. So what? Suppose someone said "our new operating system includes a web browser". But I already have a web browser? "Yes, but we embed it in the kernel itself!" Why would that be compelling?
The other argument, that this is needed for offline use, is more meaningful. I don't personally think this is a big enough deal to be the USP. But sure, for some people it may be.
No, you're misunderstanding the feature (or they don't explain it well). GitHub solves the problem on their platform yes, but not in the protocol (git) itself.
Fossil embeds that data in the repository, all the data is local. Fossil works perfectly with the "local first" doctrine, something Git also does, but not for everything around Git, that Fossil embeds into the repository.
Basically, Fossil is Git + GitHub but self-hosted and offline first. You pull down a Fossil repository is like pulling down the Git repository + all related GitHub data.
> Why would VCS experts be good at designing a compelling forum or ticketing system?
They don't have to be experts about something to make it good enough. For a lot of us with poor internet connectivity, the offline first doctrine is essential in a lot of the work we do, as internet can disappear at any notice. Fossil works much better for this, as I can still read the wiki and tickets when my internet drops, while if I were using GitHub, I'd have to results to writing my own code/use 3rd party software to get the same experience.