So, who's still left on GitLab?
-
Back to what is Internet : learn to host your own git repository.
It is what @neil do.
From what I understood, @neil is a lawyer, not a computer scientist.
-
I am happily using Forgejo for some stuff, and just a plain old remote git instance for other bits, but I'll freely say that my requirements are very limited.
@neil I've moved over 30 repositories from github (when they started pushing their AI stuff) to codeberg.org and I have a gitolite installation on 1 VPC and 4 home computers/laptops/rpi/orangepis that run Linux. So now my git repositories have at least 4 remotes. I'm pretty happy with this setup.
-
It rather depends on your requirements. If you want to collaborate easily with others, for instance, or have a fancy CI pipeline, or whatever.
One could just run git, locally, and back it up. All the benefits of git branches, with nothing to host.
Or one could also run a remote instance of git, and push from local to remote from time to time too. Perhaps convenient if one is using multiple machines.
One could look at a self-hosted "forge", like Forgejo, or pay Codeberg to run it.
-
I am happily using Forgejo for some stuff, and just a plain old remote git instance for other bits, but I'll freely say that my requirements are very limited.
@neil damn i was just getting used to switching to Mercurial from Subversion
-
So, who's still left on GitLab?
Time to find a new project home?
> AI is the substrate on which future software gets built. Agents will plan, code, review, deploy, and repair.
@neil it gets worse:
> Agents merge requests in parallel, trigger pipelines around the clock, and push commits at a rate no human team ever did. Git itself wasn't designed for that load, and bolting AI onto platforms not built for agents is the biggest mistake of this era. We're doing a generational rebuild of the underlying infrastructure to handle agent-rate work as the default. Git itself is being reengineered for machine scale.
-
@Juankprada @neil For open source stuff: codeberg. Otherwise, self hosting forgejo isn't too hard.
-
@neil it gets worse:
> Agents merge requests in parallel, trigger pipelines around the clock, and push commits at a rate no human team ever did. Git itself wasn't designed for that load, and bolting AI onto platforms not built for agents is the biggest mistake of this era. We're doing a generational rebuild of the underlying infrastructure to handle agent-rate work as the default. Git itself is being reengineered for machine scale.
> The monolith is giving way to modern, API-first, composable services. And agent-specific APIs are being built so agents can act as first-class users of the platform, not as bolted-on consumers of human-shaped interfaces.
-
It rather depends on your requirements. If you want to collaborate easily with others, for instance, or have a fancy CI pipeline, or whatever.
One could just run git, locally, and back it up. All the benefits of git branches, with nothing to host.
Or one could also run a remote instance of git, and push from local to remote from time to time too. Perhaps convenient if one is using multiple machines.
One could look at a self-hosted "forge", like Forgejo, or pay Codeberg to run it.
One could just push from git on one local machine to git on another. Fundamentally the same as the "central server" model, since it is all p2p anyway, but perhaps a different mental model.
-
So, who's still left on GitLab?
Time to find a new project home?
> AI is the substrate on which future software gets built. Agents will plan, code, review, deploy, and repair.
@neil GNOME and related projects
https://gitlab.gnome.org/explore/groups/active -
I am happily using Forgejo for some stuff, and just a plain old remote git instance for other bits, but I'll freely say that my requirements are very limited.
@neil For me, the main attractions of Github were remote git hosting and free building and testing of my code on Mac OS and Windows. When Github started pushing their Copilot nonsense, I started looking for alternatives. Forgejo doesn't give me Mac/Windows testing, but for my own projects it's easier to just drop Windows support altogether. In the past I tried to make sure my code was reasonably portable and worked on exotic platforms like Windows, but I do this in my free time and Microsoft doesn't care about developers like me, so I don't really see the point anymore.
-
So, who's still left on GitLab?
Time to find a new project home?
> AI is the substrate on which future software gets built. Agents will plan, code, review, deploy, and repair.
@neil yay (not yay). So much meaningless fluff packed in around that too. I really can't wait for this thing to actually pop and done if these companies and CEOs to disappear in clouds of smoke
-
@Juankprada @neil Forgejo (there's a few instances)
Source Hut
Tangled's an up-and-comer
Niche stuff like gitolite
-
@Juankprada @neil Forgejo (there's a few instances)
Source Hut
Tangled's an up-and-comer
Niche stuff like gitolite
@Juankprada @neil I'm largely moving to Forgejo because they have largely compatible Actions, good mirroring features, and working on ActivityPub-based federation.
Plus, Forgejo's relationship with Codeberg means there's some resemblance of a financial plan.
-
@Juankprada @neil I'm largely moving to Forgejo because they have largely compatible Actions, good mirroring features, and working on ActivityPub-based federation.
Plus, Forgejo's relationship with Codeberg means there's some resemblance of a financial plan.
@Juankprada @neil because of Teahouse Hosting, I rank forges by "do they have CI/CD, and do they have OIDC tokens?"
GitHub, GitLab, and Forgejo do (and BitBucket, kinda).
Gitea is working on it.
Source Hut and Tangled don't have OIDC.
-
So, who's still left on GitLab?
Time to find a new project home?
> AI is the substrate on which future software gets built. Agents will plan, code, review, deploy, and repair.
@neil gitlab is a prime example of a product succeeding despite the best efforts of the product team.
We used them for 4 years right up until 2020. When it worked it was great, it’s just it had the same uptime as GitHub has now.
-
@neil GNOME and related projects
https://gitlab.gnome.org/explore/groups/active -
I am happily using Forgejo for some stuff, and just a plain old remote git instance for other bits, but I'll freely say that my requirements are very limited.
@neil I'll chime in here and say that if one is looking for something very fully-featured and is gonna sysadmin it themselves, Phorge (the currently-maintained community phork of Phabricator) is pretty swell.
A buncha years back at my work we were looking to finally ditch the proprietary bugtracker we used which supported up to Ubuntu 12.04 (!!!) and I did a survey of the options out there and it was the only one that didn't seem to majorly suck. And despite having a ton of features, frankly more than most people could possibly need, it runs fine on a toaster . . . barring LLM scraping doing DDoS attacks all the time, at least.
So yeah, for a single user self-hosting only Git repos Phorge is probably overkill, but if one finds oneself with any particular requirements or really wants All The Features (bugtracker! stackoverflow-style Q&A! code review! a hierarchical wiki! blogging! meme storage! countdowns! calendar! time tracking!) it gets ya *a lot* with rather little overhead. -
I am happily using Forgejo for some stuff, and just a plain old remote git instance for other bits, but I'll freely say that my requirements are very limited.
@neil I’m currently running a GitLab instance. It was good for some years but the writing’s been on the wall for a while - performance has been going downhill (private instance, can’t blame bots), questionable communication from leadership and signs of “AI” popping up.
Migration’s not quite trivial though, the faff of moving tasks/issues is real. Worse, Forgejo’s CI is very basic and at minimum needs a new runner that supports something other than Linux Docker containers. -
So, who's still left on GitLab?
Time to find a new project home?
> AI is the substrate on which future software gets built. Agents will plan, code, review, deploy, and repair.
@neil Ugh, expect software quality to go down hill.
-
R relay@relay.infosec.exchange shared this topic
