What does federating forgejo even mean? There's already a distributed VCS in it (git) and I can understand wanting the bug tracking be distributed too, but where does federation come in? For that matter, Fossil (fossil-scm.org) already does most of what is wanted. It's incompatible with git but I think there was some talk of fixing that.
LibreByte
Tecnologías libres para la comunidad.
Puedes enviar post a esta Comunidad sobre Tecnologías Libres en Español o Inglés.
the way i understand it, it's mainly about user accounts. people will not make a new account for every website they go to, that's the reason these centralized platforms are so dominant. The idea with forgejo (as i see it) is to allow people to register on one forgejo instance, and use that login to contribute to any other forgejo instance as well without first having to sign up.
as far as i know, git doesn't really have a concept of user accounts. yes there's signing commits, but the actual access to the repo has to be handled outside of git itself.
Now, federating forgejo and allowing other instances to contribute is only one step removed to simply opening it up to the entire internet. but i imagine instance owners will figure out ways to prevent spam and abuse quick enough.
Hmm, that is kind of interesting, but would OAuth have sufficed?