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.
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.
@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).
@moonman My feelings exactly. I didn't have anything original there ( #Github ) in the first place, but I had patches for others' projects. I removed everything several years ago. Yes, a couple of potential employers have passed on hiring me because my GH account was empty. I just (A) don't want to support centralized facilities like GH or SourceForge any more, when you can host your own #git / #hg / #darcs / fossil; and (B) as my role at work has changed more toward user support, I'm not creating or using such patches any more, so if someone found and started using them, they'd be potentially doing it wrong / importing security holes.
( For a while, I had my own #Fossil repo with some original stuff, but thanks to hosting changes are $EMPLOYER work scheduling / hotel Internet, that's all gone, too. )
I discovered there is another git group, so even though I was not able to join in, I'm going to take that alias off of !vcs ...probably to replace with #hg
@musicman I normally only use #git when I have no other choice. Its commands seem obtuse when compared with mercurial ( #hg ) and #fossil ( which is still my favorite dvcs [ and favorite vcs in general, as I never used #cvs or #svn ] ). I have to look up everything I want to do with it.
@xj9 @moonman #Fossil is my favorite. #Git is too complicated for anything I've ever done. (Planning to look at Mercurial #hg and #Darcs and Bazaar #bzr sometime.)
If #git isn't the right version-control system for your work, there are others that may or may not fit your needs. Look at #hg (mercurial), #bzr (bazaar), #fossil, #darcs, or #svn (subversion). I know svn has a gui tool available for Windows. Not sure what kind of gui tools the others may offer.
@question Yes, #git uses #SHA-1 for its hashes. So does #fossil and #hg (mercurial) and #darcs, but hg (and probably the others too) is working toward replacing SHA-1 with a stronger hash function.