I only worry about collaboration via github. I don't need an issue tracker or CI on my local repo. Github issues and PRs are discussions, not records. That's the point of the self contained repo commit messages.
You seem to be under the impression that OP was criticizing your approach. Your usage of Github is not representative of the majority of cases. You are only in Github for visibility, and the commit history/repo hosting are already distributed, which is fine. You can move away at any time.
What OP was criticizing was these larger FOSS projects who don't seem to mind that they are doing all their work on a closed platform, and that they have a lot to lose if Github decides to pull the rug from under them.
I went off a bit into more personal cases in the thread. But my original post was aimed at other/larger projects. If they maintained a proper git repo and used the platform tools as secondary tools (eg. discussion oriented instead of record oriented) then they wouldn't be locked into Github. I agree that a bunch of ones don't do it correctly and put the context that should be in the repo/messages into the PRs or issues. That is a mistake. But switching from Github won't help that... they'll just do the same thing elsewhere and lock themselves into that site or tool (ie. lockin doesn't require a service, just tools that do more than manage the repo).
