5 ms·

> and you owe it to them Stop right there. It's an open source project. You owe the users absolutely nothing.

• cwillu 3y ago
  If you perform marketing and/or evangelism for your project, it's not at all obvious that you owe your users nothing.
  • growse 3y ago
    The act of marketing software doesn't invalidate the license, which often explicitly states that the software comes as-is and free from warranty / support.
    • caturopath 3y ago
      Offering an as-is disclaimer doesn't rid someone of all social, moral, or legal responsibility. Saying things that conflict with that disclaimer does indeed chip away at the effect the disclaimer has on your responsibility.
• ImPostingOnHN 3y ago
  > You owe the users absolutely nothing. Stop right there. When you ask people for feedback, be it 1-on-1s or bug reports, ignoring the feedback is ruder than never having asked in the first place. If you decided to ask for feedback, and they're kind enough to take time out of their day and spend their efforts to help you out in the way you asked them to help you out, then yes, you DO owe it to the provider to not then tell them to bugger off with said feedback. If you were going to do that, you should have disabled bug reports from users, instead of asking users to help you by providing feedback. Here is a helpful tutorial on doing that on GitHub: [0] [0]: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/disabling-issues https://docs.github.com/en/repositories/managing-your-reposi...
• Dah00n 3y ago
  Sure you do. Anyone asking for feedback owe to respond on said feedback.
  • blitzar 3y ago
    Allowing feedback != Asking for feedback
    • deleted 3y ago
      [deleted]
    • ImPostingOnHN 3y ago
      opening your feedback system to users == asking users for feedback