Live data from Hacker News

Leaving GitHub for Forgejo

jorijn.com

11–20 of 380 posts

Re: Leaving GitHub for Forgejo

#11

Everyone seems to be leaving GitHub, and forgetting the entire spirit of what git is in my eyes. Git was always meant to be decentralized, the problem here is that all the tooling around git was centralized to GitHub because it was a cleaner experience, they scaled nicely, and were properly maintained. I would prefer to still see mirrors on GitHub that are auto-synched because I've seen projects for years either self…

While I'm not forgetting the spirit of what Git is, I'm also remembering how GitHub used "all open repositories" to train their first Copilot without telling anyone.

So, no thanks. I'll not be committing any personal code there anymore.

And no, I don't care for the social aspects either. Discoverability, stars, and AI bot powered issue bombardment.

I'm fine like this.

Also, remember, "Open Source is not about You".

Re: Leaving GitHub for Forgejo

#12
In "What I gave up" section author mentions his social graph. It is possible to take your social graph and collaboration history using GitSocial. It also allows cross-forge pull requests between any git hosts. All without 3rd party dependencies.

Re: Leaving GitHub for Forgejo

#13

Everyone seems to be leaving GitHub, and forgetting the entire spirit of what git is in my eyes. Git was always meant to be decentralized, the problem here is that all the tooling around git was centralized to GitHub because it was a cleaner experience, they scaled nicely, and were properly maintained. I would prefer to still see mirrors on GitHub that are auto-synched because I've seen projects for years either self…

Yes, but GitHub is more than just git. The most important aspect of the platform that everybody seems to forget is the social component and how easy it made to create a persistent, off-site repository and collaborate across repos.

The "social component" is a big problem in actual FOSS.

Re: Leaving GitHub for Forgejo

#14
I’ve moved to self hosted gitea a year ago running in my homelab and not publicly accessible. No https, registrations disabled and repos are not public.

I’m thinking about making public instance and use it with https, but minimize the attack surface, any recommendations especially about gitea/forgejo?

Re: Leaving GitHub for Forgejo

#15
People constantly cry out for decentralization. In reality, however, most systems eventually end up centralized. Perhaps when people ask for decentralization, they are actually seeking a new center where they can become the new pioneers. It seems that when they feel they have no chance of winning under the existing rules, they use decentralization as a pretext to overturn the board.

Re: Leaving GitHub for Forgejo

#17
post #12

In "What I gave up" section author mentions his social graph. It is possible to take your social graph and collaboration history using GitSocial. It also allows cross-forge pull requests between any git hosts. All without 3rd party dependencies.

TIL. Thanks!

Re: Leaving GitHub for Forgejo

#18
One of my friends made fremforge.com (an EU-sovereign CI/CD with Git included). It's currently in closed beta but goes live next week (tm). It is built upon Forgejo and EU-based services using T-Cloud as the underlying hyperscaler. Have a look! I don't make any money from it, by the way. And yes, it will cost a little bit, but rest assured: because you are paying for it, you will not be the product.

Re: Leaving GitHub for Forgejo

#20
post #15

People constantly cry out for decentralization. In reality, however, most systems eventually end up centralized. Perhaps when people ask for decentralization, they are actually seeking a new center where they can become the new pioneers. It seems that when they feel they have no chance of winning under the existing rules, they use decentralization as a pretext to overturn the board.

If only you bothered to read the first line of the article, directly under the title:

>I moved my code from GitHub to a self-hosted Forgejo

Post reply on HN