More so than these, imo, the standardization of contributing to a project was far more valuable.
Everyone knows how to open an issue, fork a project, and open a PR. GitHub Flow became a common pattern that devs could use as a common reference.
Otherwise GitLab and BitBucket would be just as big as GitHub.
I used to use Bitbucket and issues were more in JIRA.
Fair. Framing this proposal as nostr solution for the entire GitHub value prop is a bit presumptuous.
But there IS value for nostr in having an implementation possibility wherein users can verify external resources.
The proposal isn't the full solution, it's the technical specification of the NIP required for the solution.
This proposal doesn't provide the entire GitHub value proposition by itself. It needs a substantial application to be built on top of it.
It was inspired by thinking through how we could support GitHub using Nostr, hence the thread. I want others to be able to follow the thought process.
The long-term goal is to use this NIP to enable that exact GitHub workflow using Nostr identity with a distributed backend.
