I'm starting to wonder whether operating a shared #code-hosting platform is only possible with sponsorship. #Gitorious collapsed because their paid hosting couldn't cover their costs (which includes the cost of free hosting). I don't believe #Github ever publicly released figures, but I do remember hearing a rumor that they were not profitable before #Microsoft purchased them. #Bitbucket still persists, but #Atlassian has made so many changes to their offerings that IMO, using their platform is putting everything that touches it at risk. #SourceForge went to all sorts of dangerous extremes to try to monetize the huge number of repositories they host (most of which appear to be residue of projects that have either died or moved their active repos 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.
Is the #Fossil #scm #vcs a #blockchain? Maybe not, but the article illustrates how many concepts of a blockchain are used in fields other than cryptocurrencies.
If you’re interested in !TclTk, then you may find #jsish interesting, because its internals are designed based on some of Tcl’s internals, and because it integrates the #Fossil #DVCS and can be updated using standard Fossil commands.
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).