550 sats \ 4 replies \ @k00b 20 Jan 2023 \ on: Jack paying 1.2+ BTC bounty for best github clone on nostr nostr
Recommendations: store the issues in the git repo itself. New issues are “pull requests” to the main repo but ux should abstract that away … (Pull requests are really just metadata about a branch’s link to other branches.)
Use nostr for discovery, profiles, reputation, and other types of metadata.
I’d recommend not hosting files on nostr, but merely point to a git repo hosted at a public IP/domain or attempt some kind of NAT hole punching.
write
preview
10 sats \ 1 reply \ @kristapsk 20 Jan 2023
Haven't looked more into this, but there is project about doing bug / issue tracking in pure git itself - https://github.com/MichaelMure/git-bug.
Also, meta issue about decentralized / federated GitHub alternative - https://github.com/JoinMarket-Org/joinmarket-clientserver/issues/1302.
reply
0 sats \ 0 replies \ @k00b 21 Jan 2023
I remember coming across git-bug when I was building https://gitern.com ... It's how I was planning to do issues.
reply
0 sats \ 1 reply \ @om 20 Jan 2023
I’d recommend not hosting files on nostr, but merely point to a git repo hosted at a public IP/domain
Why not though? A relay might advertise that it's willing to host git files.
reply
10 sats \ 0 replies \ @k00b 21 Jan 2023
That's fair actually! I was mostly saying don't store git repos as nostr messages.
reply