[einpoklum]

It seems to me people don't give enough thought to the possibility of hosting themselves elsewhere, and only "mirroring" onto GitHub for the presence effect.

GCC does this (edit: LLVM half-does-it, in that issues are handled elsewhere). So does MonetDB and I'm sure there are a million more examples.

[saagarjha]

The GitHub repository for LLVM is the official one: https://llvm.org/docs/Proposals/GitHubMove.html

[jefft255]

This doesn’t solve the issues of stuff like Bugzilla, plus these mirror only offer a fraction of what GitHub truly offers (issues, CI, pull requests with nice interface).

Basically, if you think your home grown infra sucks, a GitHub mirror doesn’t address that.

[einpoklum]

Neither does hosting your code on GitHub. Its issues mechanism is very limited compared to Bugzilla (or JIRA or whatnot). As for CI - GitHub itself doesn't give you CI. Travis does and they've gone mostly/wholly commercial. etc.

I'm just saying you don't need to be fully on GitHub to be visible on GitHub.

[olmideso]

Actually LLVM has their official repository there, not a mirror as GCC[0]. But they still do reviews and merges outside of github. linux kernel project does a similar thing.

[0] https://github.com/llvm/llvm-project

[pengaru]

The "linux kernel project" does not have its official tree on github, Linus just has a read-only mirror there.

You can confirm this by reading one of the bot replies to a PR [0]:

Linux kernel development happens on mailing lists, rather than on GitHub - this GitHub repository is a read-only mirror that isn't used for accepting contributions. So that your change can become part of Linux, please email it to us as a patch.

[0] https://github.com/torvalds/linux/pull/805#issuecomment-5933...

[olmideso]

I know that the discussions and reviews happen on mailing lists and believed that this github repo is the official one there all these patches go, but apparently it's not.

Thanks for the correction.