Oh no, our decentralized VCS will be… decentralized!

Seriously though the big problem to solve will be squatters, when there are three logical places for a module to be hosted. That could create issues if you want to migrate.

I would rather have this happening after a contender to git has surfaced. Something for instance with more project tracking built in so migration were simpler.

> fragmented ecosystem

This sounds a bit like an oxymoron. More diversity will only help the ecosystem IMHO.

You say fragmented I say decentralized.

Hopefully one of the efforts to build distributed pull requests will take off, so that all the forges other than github can band together and interoperate.

All those different 'git forges' use git as version control system and the same issue and PR workflows. There is no fragmentation, unless you consider one git url being different from another git url 'fragmentation' ;)

The D in DVCS working as expected.

Git itself comes out as a very decentralized tool to me.

I prefer a pletora of code hosting sites, that one massive hub controlled by a single one. We can see how bad is when there is a monopoly or cuasi-monopoly.