Email or username:

Password:

Forgot your password?
All posts Forgejo's posts Post Back to profile
Forgejo

Forgejo forks its own path forward πŸš€

Forgejo started as a soft fork of Gitea. Over time, it developed its own identity, adopted both development and governance practices - to ensure the stability, quality, and openness of the project - that made it more challenging to remain a soft fork. In early 2024, a decision was made to become a hard fork, and for Forgejo to forge its own path going forward. This post explains the consequences this decision will have.

forgejo.org/2024-02-forking-fo

15 February at 23:09 | Open on floss.social
16 comments
Trolli Schmittlauch πŸ¦₯

"With the decision to become a hard fork, [being a drop-in replacement for Gitea] will no longer be guaranteed. It will remain possible to upgrade from the latest #Gitea version released at the time of the hard fork, but versions past that will not have such a guarantee.

As such, if you were considering upgrading to #Forgejo, we encourage you to do that sooner rather than later"

#lastBoost

15 February at 23:30 | Open on toot.matereal.eu
Codeberg.org

We are excited about @forgejo becoming a hard fork, and trust the maintainers to double down on their commitment to a secure and reliable software forge. It was a pleasure to work with #Forgejo in the past year, and we thank everyone involved for turning the fork into a successful project.

15 February at 23:44 | Open on social.anoxinon.de
π˜‹π˜ͺ𝘳𝘬

@forgejo Time to finally getting rid of all gitea in my configuration, I guess πŸ˜ƒ … Will there be some sort of guide for also β€œhard-forking” the configuration when hosting an instance using Docker?

15 February at 23:44 | Open on gts.0x7be.net
Wuzzy

@forgejo Bravo! πŸ‘ I really love the "no compromises" approach to free software development.

Its unfortunate the problem with proprietary components couldn't have been resolved within Gitea but I think the fork was the right decision after all.

16 February at 0:17 | Open on cyberplace.social
thagomizer_
Aral Balkan

@forgejo Excellent decision and thank you for the work you do :)

16 February at 7:32 | Open on mastodon.ar.al
lime360
Mike, First of His Name

@forgejo I went all-in on Forgejo last yeah, renaming all the gitea references in my systemd and configs and everything.

Keep it up, you're doing great!

16 February at 7:58 | Open on social.chinwag.org
utzer [Pleroma]
@forgejo TL;DR no change yet, switching from #Gitea to #Forgejo is possible any time, but there is no guarantee it will be possible in the future. So take a decision if you want to use Gitea or Forgejo. Rather switch sooner than later.
16 February at 8:01 | Open on soc.utzer.de
piegames

@forgejo now all you need is an actually good name for the project

16 February at 8:05 | Open on flausch.social
piegames

@forgejo I'm serious about this by the way. To be more constructive: Currently ForgeJo is most likely to be pronounced as /fΙ”ΙΉdΝ‘Κ’'dΝ‘Κ’oʊ/. The double /dΝ‘Κ’/ between the syllables really breaks the flow of the word.
What about "Forgeo" or "Forjo" (/fΙ”ΙΉdΝ‘Κ’oʊ/) instead for example?

16 February at 8:45 | Open on flausch.social
Andreas Bulling

@forgejo I switched immediately after learning that gitea is not a 100% non-profit. And now I hope that I will never have to switch back. All the best!

16 February at 8:07 | Open on mastodon.social
γ€Œ Fristi 」
EffJot

@forgejo I like some of the features and roadmap of Forgejo, and I really would've liked to have introduced #Forgejo instead of #Gitea at work. However, there we are limited to a Windows environment and I don't have the time and experience to build it from scratch, so we're stuck with Gitea. πŸ˜” (My main work is in hydrogeology and GIS, not application development.) But I'll keep an eye on Forgejo and maybe one day get lucky. πŸ˜‰

16 February at 8:13 | Open on mstdn.science
lime360

@fj @forgejo i've tried hosting forgejo on windows through wsl

16 February at 8:14 | Open on mstdn.social
Go Up