I've had a pretty good response rate to issues posted via nostr. Then again, I am not a prolific nostr tester and issue raiser like you are. Can you post some examples issues? the clearly 'mileage may vary'.
Discussion
Even my own team. Been like pulling teeth. 😅
hrmm. thanks for shaing. I wonder whether they are not getting notifications in the clients they are using or whether, as its not in the main place they manage issues, it doesnt get seen.
The idea of a bridge so that you could look at nostr for all the issues has come up to address that second problem, but that has its own challenges.
It would probably help a lot, if they had a personal feed on GitWorkshop, actually. Like, my guys are responding to some repos, but not to others, because they're not actively working on those and forget to check on them.
I also have to click on like 10 repos, to see if someone responded. I sometimes miss notifications, even if they are sent, because I get drowned by notifications, sometimes.
there are a few usecases here: 1) discovery of new interesting content on git 2) notifications of content I have indicated I'm interested in; and 3) Inbox style - messages I definitely need to be looking at.
I'd like there to be experiences for all three on GitWorkshop.
I completely agree that notifications just for git related things is needed.
I haven't forgotten about this as a more PR focused inbox for ngit is also important
I'm reminded of the workflow of Greg Kroah-Hartman as discussed here https://www.youtube.com/watch?v=vyenmLqJQjs and how CLI tools (eg ngit) could aid in the workflow of maintainers.