this post was submitted on 18 Jul 2024
93 points (93.5% liked)

Open Source

31256 readers
236 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
 

I've been on Codeberg for over a year now and the experience has been great. It has been around for a while, it's fast, thanks to Forgejo, the self-hostable open-source software that Codeberg uses, which also offers great features.

However, it lacks a good CI/CD system. I feel like Woodpecker (the CI/CD system Codeberg uses) can't do more complex things. Forgejo/Gitea have their own CI/CD system which is better, but Codeberg still uses Woodpecker.

But other than that, why isn't Codeberg more widely adopted? Even privacy advocates continue to use GitHub, despite its acquisition by Microsoft. I agree with the sentiment that GitHub has a large user base, and its widespread adoption is undeniable, but I still think more people should try Codeberg or even self-host their own Forgejo/Gitea instances.

So, I'm curious to hear your perspective. What are the reasons that keep you tied to GitHub? Do the features and network outweigh the privacy concerns? Are there specific functionalities that you rely on and haven't found elsewhere?

you are viewing a single comment's thread
view the rest of the comments
[–] Lazycog@sopuli.xyz 26 points 4 months ago* (last edited 4 months ago) (5 children)

I would have given it a go, but reading their terms it seems they don't like people having non-foss code there, and I would like to have both my foss and non-foss projects together on one platform.

I've been thinking about self-hosting forgejo though!

Edit: I did move from GitHub to GitLab, but don't really wanna stay on GitLab either.

[–] buffaloseven@lemmy.ca 5 points 4 months ago (1 children)

I've been self-hosting Forgejo for a while now and I really quite like it.

load more comments (3 replies)