nielliesmons on Nostr: I think we can do better than the "copy GitHub and add stuff" approach Biz . 1) Once ...
I think we can do better than the "copy GitHub and add stuff" approach Biz (npub1ehh…zjqv) .
1) Once you have a reply section on the repo event, the Issues can be
focussed on bugs and requests.
2) I think a solution that lets the author target his repo to multiple communities is better than having a chat per repo. Why do you even need a chat for the repo, if you already have a reply section on it + a gazillion other events in there that can each receive replies too. The conversations already happen there and in the Communities (plural!!) that work with this repo.
Look into #communikeys for making that part work.
3) Why not use Indexed Wiki entries (30040 with 30818s inside) for
Docs?
4) Labels > Stars
5) Zaps & Pricing are huge for collaboration
1) Once you have a reply section on the repo event, the Issues can be
focussed on bugs and requests.2) I think a solution that lets the author target his repo to multiple communities is better than having a chat per repo. Why do you even need a chat for the repo, if you already have a reply section on it + a gazillion other events in there that can each receive replies too. The conversations already happen there and in the Communities (plural!!) that work with this repo.
Look into #communikeys for making that part work.
3) Why not use Indexed Wiki entries (30040 with 30818s inside) for
Docs? 4) Labels > Stars
5) Zaps & Pricing are huge for collaboration