this post was submitted on 20 Aug 2024
160 points (90.4% liked)

Selfhosted

40113 readers
855 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

I've recently set up my own Gitea instance and I figured I'd share a simple guide on how to do it yourself. Hopefully this will be helpful to anyone looking to get started.

If you have any feedback please feel free to comment it bellow.

you are viewing a single comment's thread
view the rest of the comments
[–] TheFrenchGhosty@lemmy.pussthecat.org -1 points 2 months ago (1 children)

That's not what happened at all.

Forgejo is actually the one in the wrong. It's an hostile fork that exist only because 3 devs were mad that they weren't hired by the company created so that the core devs of Gitea could do it full time.

You're just repeating their lies.

The Forgejo people never "owned" Gitea.

[–] copygirl@lemmy.blahaj.zone 3 points 2 months ago* (last edited 2 months ago)

Could you please provide some sources for that? I'd like to know more.

First of all though, there is no such thing as a "hostile fork". Being able to fork a project, for any reason, is the entire point of open source. And to be fair, not wanting to continue working for a for-profit company for free is a very good reason.

And yeah, when you suddenly turn a FOSS project that's been developed with the help of a bunch of contributors, into a for-profit company, without making a big fuss about it beforehand and allow the contributors and community to weigh in, then yeah, that's a hostile takeover of sorts, at least in my opinion. Developers gotta make money, but they could've done that by creating a new brand instead of taking over that of a previously completely FOSS project. Forgejo is preventing that exact thing from happening by joining Codeberg (a non-profit).