Testing if OG works on code.forgejo.org
| Forgejo | https://forgejo.org |
| Forgejo | https://forgejo.org |
@mxfraud Allowing AI contributions is misleading and not what the agreement is about.
If you think about (problematic) ways that people use AI for you would see that the agreement would not allow it. The allowed use of AI is really limited.
I encourage you to read the discussion that lead to this agreement, this is the best outcome IMO - pushing anything beyond this would not have been possible. There's no BDFL, it had to be agreed by those involved in Forgejo which include people that use AI in some form.
https://codeberg.org/forgejo/discussions/issues/366
I can totally understand that anything that isn't a total AI ban is not good (I myself would've liked to see this too), but achieving that is not realistic if you work with a diverse group of people. This is the best compromise.

Hey everyone, I'd like to continue the discussion from https://codeberg.org/forgejo/forgejo/pulls/8285 because I think it is an important one to have. There have been bilateral conversations about this matter between me and several other team members, but I suppose that it's time to discuss th...
Testing if OG works on code.forgejo.org
Oh no! a wild security feature for @forgejo has appeared that even Github doesn't have! https://codeberg.org/forgejo/forgejo/pulls/4662
- When a person loses access to their TOTP (e.g. phone wiped) and didn't properly save their TOTP's scratch code they have to; they have to rely on the instance admins to authenticate with them that it is really their account, this can be a quite difficult and lengthy process to safely verify thi...
For the past month or so, I have been working on a soft quota implementation for #Forgejo. I submitted the initial draft pull request two weeks ago, today I marked it ready for review.
This has been a massive undertaking, which shows in the diffstats too: 3811 lines of tests, and 2929 lines of code is quite a lot! But I'm very happy about how it turned out. Even more so, because this is the first (partial) copyleft contribution to Forgejo: while the core feature is under the MIT license, the tests are under EUPL-1.2.
The aim was to create something that would support both large instances like Codeberg with complex requirements, and small instances that just want to say "You have 1Gb of space to use, use it well". I think I nailed it.
Of course, there are lots of things that can and will be improved, but the pull request above lays down a solid foundation, and is already usable in its current form.
Because various forms of quotas have been requested by #Gitea users over the years, this might be of interest to them too. Mind you, I have no plans to submit the pull request to Gitea myself.
The goal of the engine is to be flexible and future proof: to be nimble enough to build on it further, without having to rewrite large parts of it. It might feel a little more complicated than necessary, because the goal was to be able to support scenarios only very few Forgejo instances need, s...
@codey would you be willing to help with the maintenance of the upcoming Forgejo 7.0.0 LTS release? 🙏
A low hanging fruit would be to review and document the dependency updates.
https://codeberg.org/forgejo/forgejo/pulls?poster=165503
* look at the release notes
* figure out if and how they relate to Forgejo
* add a comment to the pull request with your findings
* recommend the dependency is upgraded or not
* add to the Forgejo release notes if the changes are user visible
Please be patient while Codeberg recovers from the DDoS that happened today. 😭
@forgejo is partially unavailable as a result. The releases cannot be downloaded at the moment.