Gitea (@gitea@social.gitea.io)
social.gitea.io
#Gitea is joining the fediverse 🎉 We can now announce we've been accepted into the #NLnet funding round that we applied to. https://nlnet.nl/project/Gitea/ Thank you to @NGIZero@mastodon.xyz @dachary@mastodon.online @forgefriends@mastodon.online and so many others for getting us to this point. We are very much looking forward to many wonderful things that federation within forges can support.

#Gitea is joining the fediverse 🎉 We can now announce we’ve been accepted into the #NLnet funding round that we applied to. https://nlnet.nl/project/Gitea/

  • handvat@lemmy.ml
    4·
    3 years ago

    I’m wondering how far the the federation is being planned. Is it just that an user on Gitea instance A can discover projects on instance B? Or can an user on instance A also open issues, pull-requests etc on a project on instance B, assuming the user has the required permissions?

    If it is the latter, I believe that would be awesome. Right now, I feel like as a starting project, if you want to be discovered and get contributors you basically need to be on a large, centralised code platform or instance such as codeberg, gitlab.com or github.com. I hope that it will lessen the barrier for people already on another Gitea instance to contribute to a project on another instance.

    • Bilb!@lemmy.ml
      1·
      3 years ago

      Discovery, like with all fediverse software, probably isn’t going to be very robust if present at all.

    • poVoq@lemmy.ml
      1·
      3 years ago

      I think opening and commenting on issues would be the minimum requirement for it to make any sense at all.

      PRs would be nice, but maybe complicated as this involves interacting directly with git. However a patch like done in the git email flow should be easy to do (but I am not sure if Gitea supports that).