4 ms·
Yes, exactly. Saying 'no' is a very important skill you should have. Of course you can learn it too (like I did :)) Also it is very important to reverse the em
by karussell 8y ago
Yes, exactly. Saying 'no' is a very important skill you should have. Of course you can learn it too (like I did :))
Also it is very important to reverse the emotional costs. I mean, usually people come to your repo and demand/ask for a feature. Instead of feeling overwhelmed from this request, say that you welcome contributions and without this this feature won't happen and the feature request will be closed (after 1/2 a year). Or if it is a bug report, ask for a reproduce with the latest master and so on ... so: try to reverse the demand to offload your maintaining work if it is no longer fun to you :)
- StavrosK 8y agoI usually say something like "I find this very useful and will work on it", "I think this is good but will probably not have time, so feel free to issue a PR for me to review if you want it", "I will accept a PR but not really expend effort to make this myself", or "I will not accept PRs for this as I don't think it's in scope, but feel free to import my library into your extension if you want".
- fourthark 8y agoIt's often hard to tell the difference between doing this honestly, and just stonewalling. Even when I'm completely honest about it and would like to see the fix happen, there is a level of my mind where I'm all, "great, now they won't respond and I can forget about this."