2 ms·
I agree. If a user reports a legitimate bug, it lies on the maintainer to act on this information. If the maintainer ignores the bug and makes other random cha
by teddyh 5y ago
I agree. If a user reports a legitimate bug, it lies on the maintainer to act on this information. If the maintainer ignores the bug and makes other random changes to the code, it still is the maintainer’s responsibility to fix the bug – the fact that they made it harder to find the bug by altering the code is entirely their own doing. It does not fall upon the bug reporter to test the code for bugs for every change made. To demand this, and to close the bug when they do not comply, is entirely the wrong thing to do.
- xtracto 5y ago> If a user reports a legitimate bug, it lies on the maintainer to act on this information. If the maintainer ignores the bug and makes other random changes to the code, it still is the maintainer’s responsibility to fix the bug This mentality is what prevents me from open sourcing most of my for-fun projects. The fact that there is people that as soon as I publish my code in Github, and someone finds it useful, they will put me as "responsible" for fixing whatever bug is affecting someone else. In my view, if I were to open source some of my code, it will be on an "as is" basis. If someone gets my code and burns his house, it is not my problem. I do my code to scratch my own itches, and don't really agree with catering to some 3rd party entitlement over some free text I share on the internet.
- teddyh 5y agoJust because you are the author does not make you the maintainer. If you, obviously and clearly, announce to all users that this software is effectively unmaintained, then I have no problem. It’s when authors try to eat their cake and have it too that I have a problem; i.e. when authors want the fame and renown of being seen as responsible for widely-used software without doing the maintenance work necessary, then I have a problem.