Author of GitSocial here. It is now possible to break most hosting dependencies by using such tools as Walgit or GitSocial to store all collaboration data in git itself and pushing it all to an S3-compatible bucket. https://gitsocial.org/ is hosted on an R2 bucket. Cross-forge, cross-bucket collaboration is built in to it, further decentralizing hosting. Happy to answer any questions!
Artifacts is a vendor lock-in, as you can't easily migrate. Much better alternative would be git being able to pull and push to object storage natively.
Were you aware of git-bug when you created gitsocial? If so, which patterns did you reuse and which ones did you decide to diverge from? Or would you say the two projects embody fundamentally different visions?
You can use GitSocial to mirror to your own bucket for situations like this:
`gitsocial mirror https://gitlab.com/owner/repo s3://s3.example.com/mybucket/repo`
This is exactly what GitSocial does: https://gitsocial.org/. Plus it can generate static sites for repositories, letting you serve it all from a bucket.
Not that I know of as I don't have a way track this. I did test importing and mirroring everything for Ghostty and Meshtastic projects, found out that initial import and push steps may take a while.
Great to have issues, PRs, etc in git, but requires each participant to set up a fork to participate.
No CI though, but an extension to capture job logs is on the roadmap.
I'm working on CLI/TUI tool that stores all code collaboration (issues, PRs, etc) in git itself. It lets you publish repositories as static sites to S3 buckets and use them as remotes:
Creator of GitSocial here: it's a Go binary CLI/TUI that lets you store all your issues, PRs, etc. in the git itself and self-host on any S3-compatible bucket: https://gitsocial.org/.
On more detailed level, it allows forgeless issue management, cross-forge PRs, git-native discussions, and much more.
It has not dependencies, just git itself. Happy to answer any questions!
