3 ms·

> When I say that I can't guarantee this code won't cause harm (e.g. destroy HW or files on your HD), I mean that. Okay, but imagine for a moment that you don'

> When I say that I can't guarantee this code won't cause harm (e.g. destroy HW or files on your HD), I mean that. Okay, but imagine for a moment that you don't say that. The README is silent on the issue of potential problems. Are you violating any social contract then? Or suppose an issue is reported to you. You don't feel like fixing it, close the issue, and even delete it, and don't add a mention of the problem to the README. Are you violating any social contract at that point? If you don't like the term "social contract", would you agree that you would be violating some norms?

BeetleB 5y ago
Of course I'm violating some contract/norm. I am also conforming to some contract/norm. That was the whole point of: > There is no "the" social contract. There are many social contracts, and they are not all compatible with one another. Similarly, those expecting my code won't cause damage are also violating certain social norms. The code is there for anyone to do what they want with it. Do with it what you will, and own the consequences. > Or suppose an issue is reported to you. You don't feel like fixing it, close the issue, and even delete it, and don't add a mention of the problem to the README. My Github repositories are very low in importance on my list of important things in life. I reroute most notifications to a folder and will go through that folder only a few times a year, so I likely won't even know about any such issues for months. Now personally, I do put a disclaimer in the README stating that people should view the code as unsupported and unmaintained (even though I do update the code from time to time), but I do it merely as a courtesy, not as an expectation. I do not at all endorse that people should put such disclaimers.
- webmaven 5y ago
  If you don't check the notifications, you aren't closing/deleting reported issues, so potential users have a chance of seeing the report.

BeetleB 5y ago

Of course I'm violating some contract/norm. I am also conforming to some contract/norm. That was the whole point of: > There is no "the" social contract. There are many social contracts, and they are not all compatible with one another. Similarly, those expecting my code won't cause damage are also violating certain social norms. The code is there for anyone to do what they want with it. Do with it what you will, and own the consequences. > Or suppose an issue is reported to you. You don't feel like fixing it, close the issue, and even delete it, and don't add a mention of the problem to the README. My Github repositories are very low in importance on my list of important things in life. I reroute most notifications to a folder and will go through that folder only a few times a year, so I likely won't even know about any such issues for months. Now personally, I do put a disclaimer in the README stating that people should view the code as unsupported and unmaintained (even though I do update the code from time to time), but I do it merely as a courtesy, not as an expectation. I do not at all endorse that people should put such disclaimers.

webmaven 5y ago
If you don't check the notifications, you aren't closing/deleting reported issues, so potential users have a chance of seeing the report.