this post was submitted on 28 Nov 2023
263 points (94.3% liked)

Open Source

32843 readers
417 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 50 points 1 year ago (12 children)

From my personal experience running GitLab and Forgejo (Gitea Drop-In replacement/Fork):

  • Gitea/Forgejo is easier to get running
  • UI is less bloated/faster
  • GitLab redesigned their UI and imo it's shit now
  • No features locked behind a "Pro" Version (Pull or Bidirectional mirrors are for example unavailable on GitLab self-hosted unless you shell out for premium)
  • Gitea Actions is a lot more intuitive than GitLab CI, this is likely personal preference but it's still an important factor
[–] bionicjoey 11 points 1 year ago (5 children)

I have no experience with forgejo but I agree with all of the above in terms of gitea v gitlab

[–] [email protected] 5 points 1 year ago* (last edited 1 year ago) (3 children)

Forgejo has different development priorities but feature wise they should be identical since the Forgejo devs also push their code upstream into Gitea

[–] [email protected] 12 points 1 year ago (2 children)

Not anymore, since as of October Gitea requires a copyright assignment for contributions. More info here.

[–] [email protected] 7 points 1 year ago

huh, would you look at that. Pretty stupid move and something that makes this entire thing even more suspect. Glad I picked Forgejo over Gitea

[–] [email protected] 5 points 1 year ago

I didn't have a horse in the race when I was looking to self-host git, but I quickly backed Forgejo when the news came out re: Gitea

load more comments (1 replies)
load more comments (7 replies)