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…
This was the original model of launchpad.net, it was supposed to be a hub of Foss that pulled in from the decentralised VCS's, and provide them all via bzr. But bzr lost the battle, Canonical was slow to adopt Git, lack of investment in the platform, so it was another lunch that got taken from them.
Leaving GitHub for Forgejo
371–380 of 380 posts
Re: Leaving GitHub for Forgejo
#372Everyone 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…
That "everyone" is just a small, vocal community if you look at the total numbers of repos on GitHub (which is still climbing)[1] Yes, I understand that people are upset about the Copilot issues and maybe even the "frequent" outages (which usually only affect fringe parts of the site not everyone uses daily) It's good that there are other solutions (forge, sourcehut, whatever) but most projects are still alive and ve…
Re: Leaving GitHub for Forgejo
#373Earlier quoted context omitted.
This was the original model of launchpad.net, it was supposed to be a hub of Foss that pulled in from the decentralised VCS's, and provide them all via bzr. But bzr lost the battle, Canonical was slow to adopt Git, lack of investment in the platform, so it was another lunch that got taken from them.
Canonical should just rename themselves to Not Invented Here. Their inability to work with others and instead reinventing the same thing badly is beyond comical at this point.
Re: Leaving GitHub for Forgejo
#374Everyone 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…
I do not mean for this to come across as a nit, but think it's worth stating explicitly: > Everyone seems to be leaving GitHub A small minority is leaving Github; this group is more likely to write articles about the choice than those who still use Github.
Re: Leaving GitHub for Forgejo
#375I have also moved my git repositories to a self-hosted NUC. I have not yet bothered with a HTTP frontend to share it with the world, mostly because I don't want to provide AI scrapers with content and don't want to put the work in to block them. It's a shame that all these companies that benefited from open source have poisoned the industry like this
Why would someone gladly provide their work as open source but draw the line at AI reading it and using that knowledge to help more programmers later? It makes no sense to me. I actively want all of my code to be read by AI.
Re: Leaving GitHub for Forgejo
#376Earlier quoted context omitted.
> It's a shame that all these companies that benefited from open source have poisoned the industry like this Open Source and the OSI are an industry plant. Look at who sponsors it. The monopoly hyperscaler conglomerates get free labor and use it to build the world we despise: tracking panopticons, phones we can't install things on, device attestation, browser monoculture with no adblock, etc. etc. Google made people…
One problem with all of these licenses is that however the code is available, we can’t practically prevent the LLM companies from training on it (especially given that they don’t respect IP laws anyway). No idea what to do about this. Wonder if communities will have to move to some kind of fractured system where source is gated behind a login. Rough times out there for transparent organizations.
Same thing book writers did when the printing press brought the possibility for others to copy their books for free.
There are also other options that have been used historically but they tend to be a lot more bloody.
Re: Leaving GitHub for Forgejo
#377Earlier quoted context omitted.
It's about offloading blame. If a server nukes, it's on infra to get a guy to unscrew it. If a service nukes, infra guy says "welp it's down", keeps on clicking. It doesn't matter what happens 6m-2y down the road, your odds of being laid off or job hopping are high in the current regime so this all makes sense. You pay some amount of your budget to make your life "easier" in the now. The trouble comes 2-5y down the l…
> tbh, migration is not that hard, but the org will act like it is It actually would be hard to impossible if done properly - meaning no lost information and no dead links.
Sorry if this sounds really grim / cynical, I've simply seen enough of these kinds of migrations to know that it is fundamentally opposite of my perception of engineering philosophy. It often becomes more of a question of business rather than correctness. (Can we simply fire the smaller customers? -> yes.)
Re: Leaving GitHub for Forgejo
#378Earlier quoted context omitted.
IP law is a farce, and the open source licenses are built upon that farce. If a single good thing comes out of LLMs, it will be forcing society to recognize “intellectual property” for the dystopic stupidity that it is. I doubt it though.
That is a pipe dream. The current direction is the opposite of that - knowledge becomes even more centralized and only rented out to individuals.
Re: Leaving GitHub for Forgejo
#379Earlier quoted context omitted.
That "everyone" is just a small, vocal community if you look at the total numbers of repos on GitHub (which is still climbing)[1] Yes, I understand that people are upset about the Copilot issues and maybe even the "frequent" outages (which usually only affect fringe parts of the site not everyone uses daily) It's good that there are other solutions (forge, sourcehut, whatever) but most projects are still alive and ve…
Why do you think total numbers of repos is a relevant metric here? If anything, the slop spam on GitHub is a problem and a core part of why people are leaving.
Re: Leaving GitHub for Forgejo
#380Earlier quoted context omitted.
To be generous to OP, none of this is intrinsic to FOSS. I write a library. I put it up online, for other people to use, if they like. At what point did I assume any responsibility to play nice with others? Or work with others at all? There's FOSS licenses, and then there's the social expectations around collaborative online development, and the latter is nowhere implied in the former. FOSS was not historically weigh…
Spot on. And with the slop pull request currently plaguing the open collaboration model I foresee more projects moving (back) to the take-it-or-leave-it model.