ForgejoThe #Forgejo monthly report was published ✨
The Forgejo v15.0 branch has been cut and the release is scheduled for April 16. Security releases for Forgejo were published.
The AI-Agreement was updated.
code.forgejo.org is not a free public git hosting.
Artha 🐲🏳️⚧️@forgejo Hurray on the AI agreement update!
FLOSSbOxIN@fbinin
Relevant change: https://codeberg.org/forgejo/governance/pulls/381
The updated file: https://codeberg.org/forgejo/governance/src/commit/57bf0779bec61e2facd1679efc9bc5839e631d40/AIAgreement.md
Relevant change: https://codeberg.org/forgejo/governance/pulls/381
The updated file: https://codeberg.org/forgejo/governance/src/commit/57bf0779bec61e2facd1679efc9bc5839e631d40/AIAgreement.md
AIAgreement: clarify Forgejo project's current understanding wrt/ LLM/AI copyright
When the AI Agreement was authored, it was not clear whether there would be a way to satisfy point 2 in the AI Agreement in the near-future. This has led to some confusion over how a contributor can satisfy this point in the agreement. This PR amends the point to represent the current state of ...
𝘋𝘪𝘳𝘬
Thomas
Albirew@forgejo btw, any news about federation?
last entry i read about it was around v8 release blog post iirc...
last entry i read about it was around v8 release blog post iirc...
@Albirew It is a huge topic which needs a lot of work, but work continues. It also affects the codebase in really basic areas which means reviewing takes more time too.
There is often in monthly reports a section e.g. here in the report from January: https://forgejo.org/2026-01-monthly-report/#federation
~ @beowulf
Orca 🌻 | 🎀 | 🪁 | 🏴🏳️⚧️@forgejo Congrats! Will be looking forward to v15 excitedly.