#[3]
I think the way this bounty is stated is put is not the ideal. I think most people will read this and think we need a big website that is just like GitHub but using Nostr somehow. I think that is not what we should see (and hopefully that's not what #[1] wants either).
What I would want to see are multiple apps that can interoperate and are able to perform separate functions:
- browse code
- comment on code (referenced by a commit)
- create issues and comment on issues
- send patches
- comment on patches
And how these should be done? I am not sure, but here's what I have in mind:
- most of the comment things should probably be kind:1 events, I don't know, with some extra tags (so they could be interacted with from the normal "social" Nostr clients? or not?)
- code should probably be hosted by standalone dedicated git servers -- and there could be centralized providers offering these services but they should interoperate seamlessly between themselves and with standalone personal servers
- sending patches should probably be done using something like this approach by #[0]: http://git.jb55.com/git-nostr-tools/file/README.txt.html
#[2] has opened a discussion on this topic on the NIPs repository that could possibly be used to coordinate the efforts: https://github.com/nostr-protocol/nips/pull/223
I think we could have multiple different smallish webapps, native apps and specially command-line tools that implement one or multiple of the separate functions described above, and with that we can achieve a much better result both in terms of quality and of decentralization than if someone or some big team decides to tackle the entire cake and come up with some centralizing architecture on their own.
💯
I was lazy with my description and overly used GitHub as a shortcut.
Either approach works (many small apps to achieve tool set, or one cohesive project). I’m a fan of the former as well, as each can probably be used for other things too, and it would move faster.
Many small apps seems more robust.
Moving Bitcoin Core development off GitHub sounds really hard to do independent of how it’s done.
But it would be awesome.
I contributed on nostr-based github replacement and we"ll continue for other nostr-apps.
Link to source?
Hey #[5] I would love to read what’s your vision and some use cases for asking this instead of going over the specs. This is what I think every time I read nostr-GitHub
note19j7avfhnjun4q5t9r9enr8fqnkwylayl7840dcq7p5tuc7h7rfcqah7j7g
Hey Jack, we created a NIP for that https://github.com/nostr-protocol/nips/pull/358(Currently also implementing 2 clients(CLI & web) and would like to know what community thinks by having your repost lol
For some clients: "(" is not splitted from url so you would need to delete that manually 😐
