as users who have used ngit to create proposals / repo events and interact with them on gitworkshop.dev, what level of information would have helped you grok what you need to grok?
nostr:npub1l5sga6xg72phsz5422ykujprejwud075ggrr3z2hwyrfgr7eylqstegx9z nostr:npub107jk7htfv243u0x5ynn43scq9wrxtaasmrwwa8lfu2ydwag6cx2quqncxg nostr:npub1896p07z8xngpct5ma00mdrad4gqfnwfwdqcl706wrm25ajynahhs27x5ge
Would calling proposals PRs help? How can we communicate the enduring need for a source git repo but not forks?
Thanks for that explanation Dan.
I noticed in all flows you referred to them as pull requests, despite the differences. What about using this familiar terminology and not changing it, but when the user first interacts with a PR, we explain to them how it's different from Github, in as few words as possible.
No replies yet.
