Live data from Hacker News

Chris Wanstrath "defunkt" GitHub cofounder and former CEO is banned on GitHub

twitter.com

81–85 of 85 posts

Re: Chris Wanstrath "defunkt" GitHub cofounder and former CEO is banned on GitHub

#81

calm down its already back

Irrelevant. Makes no difference at all. This incident alone means no company should have github as a mission critical component of their software development.

That's why companies self host GitHub for Enterprise.

I know of no reason why a company should use public GitHub for private business.

Every company I have contracted or worked for, all used on-prem GHE.

Re: Chris Wanstrath "defunkt" GitHub cofounder and former CEO is banned on GitHub

#82

Here's a term you need to start saying to management of your company: "software supply chain risk". github just became a business risk and a software supply chain risk. I recently worked for a very large company that was 100% all in on github. And now its clear that in an instant and single developer or perhaps the entire organisation can be finished as far as github goes. Any CTO would now be negligent to have an or…

Use GitHub for Enterprise and self-host, like most modern companies.

Re: Chris Wanstrath "defunkt" GitHub cofounder and former CEO is banned on GitHub

#83
post #65
post #37

Earlier quoted context omitted.

I have the same nightmare, so to mitigate risk I run a self hosted instance of Gitea [1] and set up nightly mirroring. The folder with the mirrors is then uploaded to a backup provider, in my case Borgbase [2] 1. https://github.com/go-gitea/gitea 2. https://www.borgbase.com/

Does it also backup PRs ans issues and all the comments?

It has settings for mirroring prs, issues, and other stuff. I don't need it my own mirrors so I've never tested them.

Re: Chris Wanstrath "defunkt" GitHub cofounder and former CEO is banned on GitHub

#84

Earlier quoted context omitted.

Git is already a distributed VCS. Just host someplace other than Github, honestly.

Putting the source somewhere else: easy, git push and change the URL in your doc. Moving all the issues: hopefully someone must have done a script to fetch the issue and convert them. Moving your CI: just rewrite your GitHub action away from these horrible yaml command. This is just going to be a bit more expensive than the 100% free GitHub plan. Getting the community of millions of user that can report issues, propo…

> Getting the community of millions of user that can report issues, propose PR and star your repository. Good luck with that.

Oh my stars! The network effect of "the community" is the worst part of Github. Your life and your project will be much better without whiny entitled people spamming the same issues expecting free support, and endless "i got an error" bug reports.

Post reply on HN