The #Forgejo monthly update was published ✨ It is a high level overview of the project activities.
All the best for the new year from Forgejo. We are in the preparations for the upcoming v10 release, have improved testing and automation. A a big thanks to everyone who makes Forgejo a success, including upstream projects and libraries Forgejo depends on.
The #Forgejo monthly update was published ✨ It is a high level overview of the project activities.
A security audit and internal preparations have lead to unprecedented security releases for Forgejo and the Forgejo Actions runner. The migration to a new k8s cluster has made huge progress and is now powering the Forgejo-specific services in production. Improvements have been made to the performance and stability of Forgejo as well as to the automated testing process.
The #Forgejo monthly update was published ✨ It is a high level overview of the project activities.
A security audit and internal preparations have lead to unprecedented security releases for Forgejo and the Forgejo Actions runner. The migration to a new k8s cluster has made huge progress and is now powering the Forgejo-specific services in production. Improvements have been made to the performance and stability of Forgejo as well as to the automated testing process.
The #Forgejo monthly update was published ✨ It is a high level overview of the project activities.
Forgejo is two years old and has been a lively human adventure, a story worth telling. A hackathon organized by Codeberg generated thousands of new translations. Forgejo v9.0.0 was published, as well as a security patch release which was backported to Forgejo v7. A kubernetes cluster was created to replace the current infrastructure, running Forgejo from the Helm Chart.
The #Forgejo monthly update was published ✨ It is a high level overview of the project activities.
Forgejo is two years old and has been a lively human adventure, a story worth telling. A hackathon organized by Codeberg generated thousands of new translations. Forgejo v9.0.0 was published, as well as a security patch release which was backported to Forgejo v7. A kubernetes cluster was created to replace the current infrastructure, running Forgejo from the Helm Chart.
It is the first version to be released under a copyleft license. Forgejo has early support for a soft-quota that can protect your server from high disk usage due to abuse. It also removes support for go-git, considered too hazardous for daily usage compared to Git. The translations saw an unprecedented number of improvements thanks to the hackathon organized by Codeberg.
It is the first version to be released under a copyleft license. Forgejo has early support for a soft-quota that can protect your server from high disk usage due to abuse. It also removes support for go-git, considered too hazardous for daily usage compared to Git. The translations saw an unprecedented number of improvements thanks to the hackathon organized by Codeberg.
The #Forgejo monthly update was published ✨ It is a high level overview of the project activities.
Forgejo v9.0 release candidates are available for testing to prepare for the release scheduled 16 October 2024. The contributor and testing documentation were improved with the goal of encouraging more diverse participation. The infrastructure dedicated to Forgejo development suffered a downtime because of excessive crawling and mitigation measures were implemented.
The #Forgejo monthly update was published ✨ It is a high level overview of the project activities.
Forgejo v9.0 release candidates are available for testing to prepare for the release scheduled 16 October 2024. The contributor and testing documentation were improved with the goal of encouraging more diverse participation. The infrastructure dedicated to Forgejo development suffered a downtime because of excessive crawling and mitigation measures were implemented.
Forgejo v8.0 is available with new features (support for workflow dispatch, better defaults to avoid spam on new instances etc.), a new approach to UI and UX, careful upgrade of dependencies to improve stability and security. Foundation parts for ActivityPub based federation and data portability were merged, bringing these features closer to completion, but they're not available yet. ✨
Forgejo v8.0 is available with new features (support for workflow dispatch, better defaults to avoid spam on new instances etc.), a new approach to UI and UX, careful upgrade of dependencies to improve stability and security. Foundation parts for ActivityPub based federation and data portability were merged, bringing these features closer to completion, but they're not available yet. ✨
The #Forgejo monthly update was published ✨ It is a high level overview of the project activities.
The User Research effort that gained momentum two months ago continues with a new round of user testing sessions. It is key to build a roadmap.
Building blocks for both ActivityPub federation and data portability improvements were merged into the codebase. They are not yet used for any user visible feature but they are a stepping stone.
Forgejo is looking for input from #Forgejo administrators.
We are considering dropping support for using Microsoft SQL Server as a database that can be used with Forgejo. We would love to hear your input, especially those using it (if there are any 👀), on this matter. See our rationale and current discussion at https://codeberg.org/forgejo/discussions/issues/122, we're looking forward to your input on this matter.
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 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 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!
@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. 😉
Forgejo v1.21 is available and comes with significant improvements to Forgejo Actions and the Forgejo runner. It also brings better user blocking, many documentation improvements, a shortcut button to open new PRs, mail notifications when new users are created and more. ✨