They're just describing the difference between good development practices and bad ones.
I disagree with the basic premise of the article that maintainers are obliged to merge code changes by default. One reason is that the maintenance burden falls on more than just the author, so there needs to be some…
I think it's also important to approach it with some humility about whether you fully understand the contours of the problem. Also I think you need to prove that you can and will do something about one problem before…
They're just describing the difference between good development practices and bad ones.
I disagree with the basic premise of the article that maintainers are obliged to merge code changes by default. One reason is that the maintenance burden falls on more than just the author, so there needs to be some…
I think it's also important to approach it with some humility about whether you fully understand the contours of the problem. Also I think you need to prove that you can and will do something about one problem before…