Time to reset the counter once again. Now everything there is degraded performance. Oh dear.
Consider a self-hosted alternative or have one as a backup like I have said before.
[0] https://news.ycombinator.com/item?id=27192869
[1] https://news.ycombinator.com/item?id=27172443
I’m tired of them now, anyone using hosted solutions should know this by now and they’ve made that choice.
Personally I believe people underestimate how easy it is to host your own services.
But I’m sick of having the conversation over and over, if people aren’t willing to investigate then, what’s the saying: “you can lead a horse to water but you can’t make them drink”
Security risk isn't a one-and-done decision. It's a changing landscape and, arguably, there are far too many eggs in the GitHub basket for this not to be something people might want to think twice about now.
Yeah, you might be able to self-host gitlab/gitea/etc but their free offering for organizations is so good that for my 30 commits/week open source project, I can deal with half an hour of downtime once in a while.
Combined with free hosting, it's really not that much of a stretch that people are willing to put up with this, especially as there have been periods of time with less outages before, though that's been a while now.
Github hasn't been reliable for a while now.
P.S. Most people here attribute being a "hacker" to curiosity.
I dont know reviewable so it might have more sauce than the recommendations
Side note, I honestly seriously think we need much better tooling than just these 2 for code reviews.
It combines concepts from GitHub, Gerrit, and other good review tools out there to make it easy and fast to reach consensus (which is what it's all about).
If you want to hear more you can email me at sam at habosa dot com
The best example to learn from is ReactOS who while has moved to GitHub they at least have a self-hosted backup just in case GitHub falls over. [1]
For the ones who are not on GitHub and are self-hosting (OpenBSD, Mozilla, Linux Kernel Project, GNOME, xfce, wireguard) I don't hear any complaints from them.
This assumes that your self-hosted Git service will have better uptime than Github.
Piece of cake. But it will also have better performance.
This is why it makes no sense to go 'all in' or try to "centralize everything to GitHub". At least (if you're a company or an organisation) have a self-hosted backup and don't jump into the 'goin all in' hype train.
I completely agree with you, to reiterate what I said last time we had this discussion 3 months ago:
> I wouldn't call it prudent to go all-in on any cloud service [0]
I've never used Github as anything more than a managed git service with a nice web interface. At work, any time the topic of moving our CI/wiki/project management/issue tracking onto GitHub has come up, I've been vocally opposed.
If GitHub went down, and didn't come back up, it would be trivial to migrate to Gitlab/CodeCommit/Bitbucket. The most time consuming thing would be setting up new web hooks for our CI.