3 ms·
Yes, but that puts the onus on the maintainer to actively reject contributions that they don't like. It doesn't help that often people will implement something
by account42 4y ago
Yes, but that puts the onus on the maintainer to actively reject contributions that they don't like. It doesn't help that often people will implement something without even asking if its right for the direction of the project and then come with the expectation that upstream will accept it. You could say that thats on them for having the wrong expectation but that doesn't change that it isn't fun to tell people "no".
Still, forgoing all contributions for that or even keeping the source closed is throwing out the baby with the bathwater. Even if you don't want any features being contributed at all there is value in accepting patches for bugfixes.
- bartread 4y ago> it isn't fun to tell people "no". It gets even less fun when they won't take no for an answer and want to argue with you about it: it sucks up time and energy you may not want, or even have, to give. It becomes unnecessary noise and distraction, which is a huge problem if your life is already busy.