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).
The only reason I even knew about SIT is because #Pijul and its #Nest code hosting platform was talking about embedding it in order to get shared bug-tracking built into the #DVCS.
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.
As #Pijul approaches version 1.0, they’re working on stabilizing data and storage formats. There were a couple of changes recently, which for the first time, were mostly backwards compatible. https://pijul.org/posts/2021-06-28-two-changes/ [pijul org]
Correction: #Pijul ... it is a #dvcs / #scm system written in #Rust, and an evolution of some of the ideas behind #Haskell's #Darcs, including fleshing out the theoretical basis and solving a couple of major bugs.
I’m not doing that. There’s another way to get Rustup, and I can make it use the OS installation as default, too. It’ll allow me to use their then-current version when I need to without losing the OS-installed default.
(I’m so very glad that both #gdc and #ldc for !DLang, along with #dub, are in Debian / Ubuntu and work fine. I’m not a #Rustacean or #Rusticrucian, so I don’t want something that I’ll forget to update between my occasional uses.)
Okay, I think I'm going to temporarily stop the efforts to install #Pijul #scm #vcs ... the forum suggests that installing the latest Rustup would fix things, but there's a checksum error showing up.
On the other hand, I now have a current version of #Darcs installed (on Windows; the Ubuntu repositories only have 2.14).
@bthall had some problems compiling #Pijul, so I’m testing it. On the Win10 machine, it failed on libsodium. On Kubuntu, it is still going, with all 4 CPU cores pegged at 98%+ and using all the swap.
I also noticed that the newest version of #Darcs now has a pre-compiled binary for Windows ... but I decided to try to compile it (in progress).