> Deleted all the forks I had on GitHub, moved the very few repos I care about over to Codeberg
I believe moving over to #Codeberg is a big improvement over relying on #GitHub (which, as #SourceForge once was, is the center of gravity for FOSS projects' development).
I closed all my repos on GH some years back. I kept one or two repos on #BitBucket for years, but they were basically dead. When BB rid itself of #Mercurial ( #hg ) and switched solely to #git, I took advantage of the opportunity to close my account there.
That said, large numbers of people moving en mass from GitHub to Codeberg would just move the problem to a different platform. The problem being people rely heavily on a centralized service.
As for GitHub, I still have my account, and with job-hunting, I really need to put something there. Seriously, I have had some places send rejection notices because they couldn't see any evidence (on GitHub) that I knew anything about the job. But I really only want GH to be a secondary mirror of a main repo hosted elsewhere.
Most of what I do goes into my #Fossil repo, but I'm also trying to use #Darcs, #Breezy, #Pijul, and #Hg enough to be able to fairly say which ones work best for me.
You'll notice that #Git is not in that list. I'm having to use git whenever I deal with other people's code projects, so I already know that it isn't tailored for my needs.
I also think that our #code-hosting solutions needn't presume #git. All of #hg, #fossil, #darcs, #pijul, #brz can be viable depending on the project & organization.
@geniusmusing I find #git to be too big and complex for my needs (and arguably for most projects). I know it “won” and even some projects that formerly used another #VCS ( such as Mercurial #hg, #darcs, Bazaar #bzr / Breezy #brz ) are switching.
In the plans: a very limited #Kallithea install (with git and Mercurial) and #Fossil for Federati ... when I have more funds and energy to devote to getting it going on its own VPS.
I think y’all know I favor the #Fossil #SCM / #DVCS over #Git (though I’m giving #Mercurial ( #Hg ) another look as well. I’m resource-constrained as well as energy-limited, but I have been thinking of standing up a miniature software forge for !FNetworks projects and users, likely using Kallithea (which can use both Hg and Git) and also having some Fossil repos (but not as part of a forge).
Before I slam #Node.JS entirely, I should admit that I’m considering making one implementation of my #vaporware #socnet project with Node. (There were _two_ such project in mind, but it looks like the source for the other vaporware project [in Python / Django] may have been deleted when #BitBucket dropped #Hg repositories. I was just going to take over where the original person left off, but if I’d need to rewrite it from scratch, it is no longer the same project and I may as well just implement it as part of the other project)