I left GitHub for self-hosted Forgejo on a hardened NUC. The reason is digital sovereignty, not reliability outages. Here's the thinking and the architecture.
it doesn’t need to be fancy, just the ref impl. just like you may find lemmy terrible and prefer mbin. the ground work is there tho: a MR is a chat with a diff attached. we really should be making mails easier, rather than inventing a whole new centralized and then federated code forge stack
hey at least it wasn’t (exclusively) gpg!! be grateful
I’m not sure how that would work without something around git. It would require push rights to your git instance: you’d need to add a bunch of tooling to protect yourself:
stop people from pushing junk to your server e.g large files, endless while loop that pushes issues filled with random characters or just counting endlessly
stop people from pushing malicious stuff that can infect you by running the git hook that checks the content
ensure you have protected branches (again probably a git hook?)
You’d need notifications that somebody has create and issue and PR, or a web interface around git so you can see it.
radicle has made something that works, but it required a gossip protocol to do a lot of work. There’s git-bug, but that also runs into the problem of allowing others access to your git.
A simple standard won’t cut it. There is way more that has to be considered besides a simple file format. That’s exactly why git-forges exist. I’m not saying it’s impossible, but way more difficult than a git forge (IMO).
Mailing lists are terrible. That’s part of why source forges became a thing. You can send pretty much anything into mailinglist in any format you like.
Exactly this. IMO we just need better ways of rendering a mailing list inbox as a series of issues/PRs. And maybe better tooling from IDEs to “open a PR” using git send-email.
Source hut is close to my ideal here, but still seems rather complex. Maybe I just don’t appreciate the necessary problems it solves yet.
Btw, can we please create a standard for issues & pull requests, independent from platforms, just like plain git?
git send-email
…is terrible.
it doesn’t need to be fancy, just the ref impl. just like you may find lemmy terrible and prefer mbin. the ground work is there tho: a MR is a chat with a diff attached. we really should be making mails easier, rather than inventing a whole new centralized and then federated code forge stack
hey at least it wasn’t (exclusively) gpg!! be grateful
I’m not sure how that would work without something around git. It would require push rights to your git instance: you’d need to add a bunch of tooling to protect yourself:
You’d need notifications that somebody has create and issue and PR, or a web interface around git so you can see it.
radicle has made something that works, but it required a gossip protocol to do a lot of work. There’s git-bug, but that also runs into the problem of allowing others access to your git.
A simple standard won’t cut it. There is way more that has to be considered besides a simple file format. That’s exactly why git-forges exist. I’m not saying it’s impossible, but way more difficult than a git forge (IMO).
Fossil scm does that
That’s not git
I didn’t mean into git itself. And also not with the kitchen sink, that’s tooling around it. Only some format to ease changing platforms.
Mailing lists are … ok. Not ideal.
Got it. Yeah, that makes sense. I think ForgeFed did.
Ohh, looks interesting. Thanks!
And that’s how we’re back to mailing lists :D
Mailing lists are terrible. That’s part of why source forges became a thing. You can send pretty much anything into mailinglist in any format you like.
Exactly this. IMO we just need better ways of rendering a mailing list inbox as a series of issues/PRs. And maybe better tooling from IDEs to “open a PR” using
git send-email.Source hut is close to my ideal here, but still seems rather complex. Maybe I just don’t appreciate the necessary problems it solves yet.