3 ms·

Where are they going? If its not self hosted I don't see it not ending up like github.

crazysim 5mo ago
codeberg I had a repo with more than a dozen forks banned on GitHub for some unclear TOS violations. Ticket has been sitting for a week plus now, asking for clarification and guidance. So, it lives in codeberg now. https://codeberg.org/nelsonjchen/op-replay-clipper https://codeberg.org/nelsonjchen/op-replay-clipper
- zuzululu 5mo ago
  this just looks like a reskinned gitea
  - crazysim 5mo ago
    It's a running a fork (codeberg specific) of a fork of gitea called forgejo (https://codeberg.org/forgejo/forgejo https://codeberg.org/forgejo/forgejo) so it's not surprising. The people behind it were a bit miffed at Gitea doing some questionable commercial endeavors in their view and also not dog-fooding Gitea for Gitea.
    - zuzululu 5mo ago
      huh i did not know that . thanks for forgejo guess im moving
  - throawayonthe 5mo ago
    it's the "main" instance of forgejo, a gitea fork https://codeberg.org/forgejo/forgejo https://codeberg.org/forgejo/forgejo
phoronixrly 5mo ago
There exist competent operations people and competent developers.
arealaccount 5mo ago
Why do people not like gitlab? I’ve always found it a better experience than github
- stronglikedan 5mo ago
  same. so much more intuitive
- selfhoster1312 5mo ago
  Gitlab's UI changes every now and then, for seemingly no reason. The UI is very full of stuff (hard to find your way around), and very slow. Notably in the past months, they've changed the issues/tickets board into a "work items" board which feels infinitely slower to load, has such a vague meaning that nobody can find it (especially when translated), and brings exactly 0 use to anyone i know. They just seem to be doing that with every feature and every part of the interface. On the server side, gitlab was always very hard to selfhost with many moving parts, many requirements, and using much resources. gitlab-runner is not very explicit about things when you're not in the happy path (why is it not picking up jobs?). I'm not even a minimalist. I've been running gitea/forgejo for the past 8 years or so and it's been a miracle in comparison: lightweight server, easy setup/upgrades, and super simpler UI/UX that everybody understands on the first try. Forgejo (gitea community fork) learns from everything that Github historically made good (UX) without any enshitiffication in sight (developed by a non-profit). I highly recommend it.
- plagiarist 5mo ago
  If you're leaving based on security failures, Gitlab is not the place to go.
- parliament32 5mo ago
  Personally, they're going wayyy too hard on the AI stuff. I just want an interface to git and maybe an issue tracker.
- dwedge 5mo ago
  I tried self hosting gitlab. I installed it and got miffed that it wouldn't let me change password complexity requirements for a user, so I left it but left it running for "maybe later". Two weeks later it had spammed 50GB of logs to the disk and was idling at 11GB RAM. With zero repos and zero active users. I don't want a git interface to be full of bloat. That's why I don't like it. I'm moving a client from gitlab to forgejo at the moment.

codeberg I had a repo with more than a dozen forks banned on GitHub for some unclear TOS violations. Ticket has been sitting for a week plus now, asking for clarification and guidance. So, it lives in codeberg now. https://codeberg.org/nelsonjchen/op-replay-clipper https://codeberg.org/nelsonjchen/op-replay-clipper

zuzululu 5mo ago
this just looks like a reskinned gitea
- crazysim 5mo ago
  It's a running a fork (codeberg specific) of a fork of gitea called forgejo (https://codeberg.org/forgejo/forgejo https://codeberg.org/forgejo/forgejo) so it's not surprising. The people behind it were a bit miffed at Gitea doing some questionable commercial endeavors in their view and also not dog-fooding Gitea for Gitea.
  - zuzululu 5mo ago
    huh i did not know that . thanks for forgejo guess im moving
- throawayonthe 5mo ago
  it's the "main" instance of forgejo, a gitea fork https://codeberg.org/forgejo/forgejo https://codeberg.org/forgejo/forgejo

phoronixrly 5mo ago

There exist competent operations people and competent developers.

arealaccount 5mo ago

Why do people not like gitlab? I’ve always found it a better experience than github

stronglikedan 5mo ago
same. so much more intuitive
selfhoster1312 5mo ago
Gitlab's UI changes every now and then, for seemingly no reason. The UI is very full of stuff (hard to find your way around), and very slow. Notably in the past months, they've changed the issues/tickets board into a "work items" board which feels infinitely slower to load, has such a vague meaning that nobody can find it (especially when translated), and brings exactly 0 use to anyone i know. They just seem to be doing that with every feature and every part of the interface. On the server side, gitlab was always very hard to selfhost with many moving parts, many requirements, and using much resources. gitlab-runner is not very explicit about things when you're not in the happy path (why is it not picking up jobs?). I'm not even a minimalist. I've been running gitea/forgejo for the past 8 years or so and it's been a miracle in comparison: lightweight server, easy setup/upgrades, and super simpler UI/UX that everybody understands on the first try. Forgejo (gitea community fork) learns from everything that Github historically made good (UX) without any enshitiffication in sight (developed by a non-profit). I highly recommend it.
plagiarist 5mo ago
If you're leaving based on security failures, Gitlab is not the place to go.
parliament32 5mo ago
Personally, they're going wayyy too hard on the AI stuff. I just want an interface to git and maybe an issue tracker.
dwedge 5mo ago
I tried self hosting gitlab. I installed it and got miffed that it wouldn't let me change password complexity requirements for a user, so I left it but left it running for "maybe later". Two weeks later it had spammed 50GB of logs to the disk and was idling at 11GB RAM. With zero repos and zero active users. I don't want a git interface to be full of bloat. That's why I don't like it. I'm moving a client from gitlab to forgejo at the moment.