Fun fact! This was a simple ngit init test and, after I realize that can work, I sent a FYI message to fiatjaf ( npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 / 3/15/24, 10:41 AM ). I don't know if was delivered (nip44?), but if it works why not ..... I didn't expect PRs or issues and it is clear that anything done here can't be easy integrated in github like this. We will see :) .
git over nostr scenario: a contributor wants a repository to use nostr instead of github but they are not a maintainer. what should they do? nostr:npub16r0tl8a39hhcrapa03559xahsjqj4s0y6t2n5gpdk64v06jtgekqdkz5pl nostr:npub10000003zmk89narqpczy4ff6rnuht2wu05na7kpnh3mak7z2tqzsv8vwqk
for the nips repository nostr:npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl and nostr:npub1896p07z8xngpct5ma00mdrad4gqfnwfwdqcl706wrm25ajynahhs27x5ge's instincts were to create a repo event for it and nostr:npub1896p07z8xngpct5ma00mdrad4gqfnwfwdqcl706wrm25ajynahhs27x5ge did so.
nostr:naddr1qqzxu6tswvqs6amnwvaz7tmwdaejumr0dspzqwt5zluywdxsrshfh67lk686m2sqnxuju6p3lul5u8k4fmyf8m00qvzqqqrhny64slsj
weeks went by and then nostr:npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl sent a patch to it. none of the nips repo maintainers as defined by github were automatically tagged in it.
nostr:npub1896p07z8xngpct5ma00mdrad4gqfnwfwdqcl706wrm25ajynahhs27x5ge realised he was listed as the only maintainer and is asking what he can do about that.
how can we make this work better? #ngit #gitworkshop
Discussion
Having the NIP stuff controlled over GitHub PRs is an antipattern. Can't have an open protocol and then manage changes over corporate junk that doesn't even let everyone have an account and doesn't let you post without an e-mail adress.
Ngit or just go full Wiki, IMO.
or can be radicle ( .xyz ).
What do you mean? Is that a relay?
Ah, okay.
I'm waiting for GitRepublic. 😉
I decided it doesn't matter. You're legit and you have a repo covering the initial commit I need, so I went for it. 😂