Selfhosted

39435 readers

2 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

185

Forgejo forks its own path forward (forgejo.org)

submitted 7 months ago by [email protected] to c/[email protected]

26 comments fedilink hide all child comments

This is from last month, but I haven't seen any discussion of it. Seems like Forgejo is now a hard fork of Gitea, instead of being a soft fork like it was over the previous year.

The main reason I'm posting it now is this: "As such, if you were considering upgrading to Forgejo, we encourage you to do that sooner rather than later, because as the projects naturally diverge further, doing so will become ever harder. It will not happen overnight, it may not even happen soon, but eventually, Forgejo will stop being a drop-in replacement."

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 27 points 7 months ago* (last edited 7 months ago) (2 children)

Thanks for the link. But is this really unseen in FOSS? My understanding is some FOSS projects do this so that it is easy to make major decisions without having to bring every person that has ever contributed to the project, kinda like how ZFS is stuck with license issues because they can't bring all contributors together to approve a license change.

[–] [email protected] 5 points 7 months ago (1 children)

I'm not one to fight for software taken over by a corporate that is against FOSS. If you like Gitea, stick with it till you have a problem

[–] [email protected] 1 points 7 months ago (1 children)

My concern is that this hard fork means "till you have a problem" might be too late for a smooth switch.

[–] [email protected] 1 points 7 months ago (1 children)

I'm not going to be able to convince people to move. I'm sticking with Forjego until something goes wrong.

[–] [email protected] 2 points 7 months ago

I'm not trying to start an argument, just looking for that balance between "gitea hasn't done anything wrong yet" and "what if forgejo runs out of steam and the project stalls"

[–] [email protected] 4 points 7 months ago* (last edited 7 months ago) (1 children)

There are some advantages but generally it's better for everyone to keep their copyright to prevent a company being able to take over and then deny users the software freedoms intended by the original license.

[–] [email protected] 2 points 7 months ago (1 children)

But everyone does keep their license. A company can not really take over in the sense that you lose your old code. They can stop developing in public but keep using your code, but so can you keep using the last public version and keep developing it. Or you can take your contribution and apply it elsewhere.

[–] [email protected] 1 points 7 months ago* (last edited 3 months ago)

You're right that the former license can't be taken away from other instances.

Some projects chooses a license specifically to stop people taking code without sharing code back upon redistribution via copyleft (ShareAlike). Getting around that by changing the license defeats the purpose (projecting users software freedom).