View quoted note →
Once upon a time I started hosting my small projects on a self-hosted Gitea (I think this was it) server. The problem was that once someone showed up and wanted to make a contribution they were totally unable to. They had to create an account on that stupid server, then the ssh access didn't work for them, then they lost their password on my server and I didn't have SMTP configured to send them a password reset, it was all very very painful.
It would have been beautiful if they could have done
- git nostr send-patch <branch>
And then I would do
- git nostr list-patches
- git nostr apply-patch <event id>
Or my repositories could have webpages that would list pending patches found on relays and also allow people to comment on them from their browsers.
Login to reply
Replies (3)
Have and still use Gitea, mostly via command line.
Nostr + Gitea integration could be interesting.
The login part could be solved with SSO, gitea already has some support for that.
This is what Sourcehut has done, only with `git send-email` and project mailing lists. They even have CI driven by patch emails.
It's a proven workflow. You're just replacing email with nostr, right?
SourceHut adds continuous integration for mailing lists
sourcehut is a network of useful open source tools for software project maintainers and collaborators, including git repos, bug tracking, continuou...