We have found #funding and https://fedeproxy.eu is starting 🚀
Our #foss project team is *very* motivated to do the right thing, and we need your input and help 🙏
We'll offer @activitypub federation between #code #forges to provide seamless interop between repo's wherever they are hosted.
1st question: What's your preferred forge?
#Fossil
#Gitea
#GitHub
#GitLab
#Gogs
#Launchpad
#Pagure
#Phabricator
#Savannah
#SourceForge
#SourceHut
Other (please respond)
Boosts appreciated!
@dachary @activitypub I suggest nixing #Gitea because there are already many decent public gitea instances, but not many of the other packages: https://git.sdf.org/humanacollaborator/humanacollabora/src/branch/master/forge_comparison.md
Of all code forges #gitea is most likely to be the first that implements native #forgefed support. The team members are excited about it.
See on Gitea where @cj elaborated the work that is needed: https://github.com/go-gitea/gitea/issues/14186
And this mention on #codeberg where @6543 is a Gitea team member: https://codeberg.org/Codeberg/Community/issues/397
@humanetech @cj @dachary @clacke ah, just realized I gave a snap answer w/out knowing what fedeproxy.eu is doing. Some of the work could be done by incorporating this tool: https://github.com/MichaelMure/git-bug Periodically running "git bug bridge pull" would import the bug reports into git. From there, it would just be a matter of using a git command to get the new reports which could then feed Mastodon.
@resist1984 @cj @dachary @clacke
Agree, git-bug is very cool! I brought it to attention to the ForgeFed team in the past, as they are tracking all that is out there in terms of code forges.