Nice, I like the idea!
I'm sure you already thought about how to handle forks, multiple maintainers, and more? For example, since Git is already content-addressed, I guess we could detect full repo forks by watching for the same hashes to be published to other Git servers/URLs which are initialized (published to nostr) by other npubs. And multiple maintainers wouldn't even need to be solved via Nostr, since their merge permissions can still be managed on Gitea, etc., right?
Login to reply
Replies (1)
The repo announcement event can optionally list other maintainers.
A fork, in the tradition sense, can be created by issuing a repo announcement using a different identifier.
Alternatively, using the same identifier by an npub thats not listed as maintainer in the original; but it's polite to use a different identifier / name to avoid confusion.