Gitea VS gitlab

It's on the radar (as Gitea is also actively working on this - https://github.com/go-gitea/gitea/pull/35295), but I suspect you can not expect anything for a while:

"Upstream Proposal: Repository Grouping/Subgroups in Forgejo":

https://codeberg.org/fedora/forgejo-deployment/issues/224

"feat: extend Forgejo URL structure from organisation/repository to organisation/project/repository":

https://codeberg.org/forgejo/forgejo/issues/9550

Here's an example off the top of my mind:

https://github.com/go-gitea/gitea/blob/main/go.sum

I bounced away from Gitea because they don't (last time I checked) have OIDC. I started[0] trying to revive-and-drive a previous PR[1] to add it, but the test failures are beyond my motivation to investigate and resolve.

[0] https://github.com/go-gitea/gitea/pull/33945

[1] https://github.com/go-gitea/gitea/pull/25664

It’s coming: https://github.com/go-gitea/gitea/pull/20311

I would be willing to guess that self hosting gitea as a backup mirror is less work than doing the same for Bluesky. But, just speculating

As I mentioned in a previous post - you can use "git" without Github by hosting an instance of the open-source Gitea service.

https://github.com/go-gitea/gitea

As mentioned in the last post, I keep my notes in git repositories. I originally used Obsidian for years as my note-taking application of choice after migrating away from Google Keep, using the vast library of community plugins (namely obsidian-livesync and obsidian-git) to back up and sync my notes on an interval to my 3 remotes; GitHub, my private Gitea instance for my private "second brain" type notes, and my Otterwiki instance (a wiki that runs on a git server of markdown files).

The solution to this is to use fake e-mails.

I can't say what Forgejo has over Gitea, but I can tell you Forgejo is missing everything from the 888 merged PRs in Gitea 1.23: https://github.com/go-gitea/gitea/releases/tag/v1.23.0-rc0

Repo license support, integrated Arch package repository, automatic issue suggestions, and the new review+homepage UIs would be notable ones for me.

See this issue: https://github.com/go-gitea/gitea/issues/1029

For years, "self-hosting" Gitea wasn't done because it was missing a bunch of useful collaboration features. Now, it looks like that gap has been closed. All of the specific features mentioned in that issue seem to have been fixed, and the big remaining task is figuring out below to actually migrate all the existing data out of GitHub -- which doesn't seem to be super high on the priority list.

Is it any better ?

We had that last year, with the full premium stuff ("pay as much as we can" mindset)

Please see this: a basic feature, much needed by lots of people (those who are stuck on azure ..): https://gitlab.com/gitlab-org/gitlab/-/issues/360592

Please read the entire thread with a particular attention to the timeline

I ran into a similar bug in Git Lab where the v18 upgrade didn’t replace now-unsupported time zones so things like scheduled pipelines simply stopped running and were labeled inactive in the UI without explanation.

https://gitlab.com/gitlab-org/gitlab/-/issues/556779#note_26...

The fix is simply to change them to the non-backwards linked names but it caused some confusing API errors since data which would no longer pass validation was already in the database and didn’t look wrong.

I am not trying to start trouble, or a heated debate, but I did want to say that my experience was the same as OPs and I am also coming from a static typing background so that likely explains my having a similar experience and expectations. I did for sure use RubyMine for attempting a change, so not "vim and yolo" but rather world class tooling and trying to discern where any random symbol came from was oppressively hard

That's not even getting into attempting to use their "happy path" <https://gitlab.com/gitlab-org/gitlab/-/blob/v18.2.1-ee/.gitp...> -> https://gitlab.com/gitlab-org/gitlab-development-kit#local which I found just incredibly challenging getting it to use my copies of the repos. But, just like in every one of these conversations, it's been a number of years since I tried it so maybe it's much better now

For more details, please check out gitlab templates

GitHub is also from them and brings the very same risks. The solution would be to build viable open source alternative but decentralized. GitLab Federation [1] or Forgejo (Codeberg) Federation [2] might be the answer.

[1] https://gitlab.com/gitlab-org/gitlab/-/issues/6468

[2] https://codeberg.org/forgejo-contrib/federation/src/branch/m...

There's another issue with a more complete proposal

https://gitlab.com/gitlab-org/gitlab/-/issues/216351

> The more typical way of doing this would be to call piece of the code but without the elaborate setup you argue you'd need.

But how do you call the code if you don't know where it's called from?

Let's have a concrete example. In this `initialize` method how do I know what the arguments are meant to be?

https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitla...

There's no type annotation so the main ways to know are documentation (haha) and seeing what it is called with in existing code. But how do you find where that method is called?

(Note this isn't the best example because I would imagine the `initialize` isn't magically generated, but it is still difficult to search for so it's almost as bad as the magic identifiers.)

The missing feature is federation! In my view, centralized structures like a giant source repository such as github are something we as a developer community need to avoid. Unfortunately, features like federated merge requests in gitlab ( https://gitlab.com/gitlab-org/gitlab/-/issues/14116 ) are something we've been waiting for for 9 years and nothing seems to be happening there. This feature alone would enable a lot of new collaboration without forcing everyone to work on a centralized system to use git - a decentralized versioning system - with high efficiency.

In case someone from Gitlab is watching: there is a long-standing issue that Gitlab Dependency Proxy does not work with containerd rewriting (https://gitlab.com/gitlab-org/gitlab/-/issues/350485), making it impossible to use as a generic Docker Hub mirror.