3 ms·

> It's rather unreasonable to be annoyed. I disagree. If you discover that a bug that makes an open source library unusable to you, after spending time on lear

by arijun 7mo ago

> It's rather unreasonable to be annoyed. I disagree. If you discover that a bug that makes an open source library unusable to you, after spending time on learning and using that library, and the authors close the bug as a wontfix, I think being annoyed is quite reasonable, even expected.

nradov 7mo ago
If that type of thing annoys you then you should restrict your use of open source projects to those backed by corporations with a paid support business model.
- kurtis_reed 7mo ago
  For feature requests, sure, but not for bug reports
grey-area 7mo ago
Not really no, you got the support you were willing to pay for.
- kurtis_reed 7mo ago
  If the maintainer merely doesn't fix the bug, then yes. If they close the bug report so it gets lost and other contributors are discouraged from working on it, then no.
  - grey-area 7mo ago
    Closed reports are not lost, they are still searchable/linkable, they are just not in the list of work to do. This is entirely up to the maintainer, who puts in the work and gives up their time/money to do so. If you want to be in charge on a given repo, put in the work and become a real contributor, if not accept the rules the maintainers choose.
    - kurtis_reed 7mo ago
      You know what I mean. If the issue is closed, it looks like it's been solved. A new issue may be created that duplicates it, etc. Obviously it's up to the maintainer. I'm saying what the maintainer should do, not what they can do.
      - grey-area 7mo ago
        Dupe reports are a signal all by themselves, that's really not harmful, nor does something being closed implied solved. You shouldn't presume to know what is best for an open source maintainer of any given project - projects vary, reports vary in quality, and the job of maintenance is not an easy one.
lucisferre 7mo ago
It's open source software. If you discover the bug, have written a failing test that demonstrates it, and a proposed solution to it, then maybe you can be annoyed when the authors close it as wontfix. Otherwise OSS is pretty much as-is, where-is, with the exception of very widely used and corporately supported projects.

by arijun 7mo ago

nradov 7mo ago

If that type of thing annoys you then you should restrict your use of open source projects to those backed by corporations with a paid support business model.

kurtis_reed 7mo ago
For feature requests, sure, but not for bug reports

grey-area 7mo ago

Not really no, you got the support you were willing to pay for.

kurtis_reed 7mo ago
If the maintainer merely doesn't fix the bug, then yes. If they close the bug report so it gets lost and other contributors are discouraged from working on it, then no.
- grey-area 7mo ago
  Closed reports are not lost, they are still searchable/linkable, they are just not in the list of work to do. This is entirely up to the maintainer, who puts in the work and gives up their time/money to do so. If you want to be in charge on a given repo, put in the work and become a real contributor, if not accept the rules the maintainers choose.
  - kurtis_reed 7mo ago
    You know what I mean. If the issue is closed, it looks like it's been solved. A new issue may be created that duplicates it, etc. Obviously it's up to the maintainer. I'm saying what the maintainer should do, not what they can do.
    - grey-area 7mo ago
      Dupe reports are a signal all by themselves, that's really not harmful, nor does something being closed implied solved. You shouldn't presume to know what is best for an open source maintainer of any given project - projects vary, reports vary in quality, and the job of maintenance is not an easy one.

lucisferre 7mo ago

It's open source software. If you discover the bug, have written a failing test that demonstrates it, and a proposed solution to it, then maybe you can be annoyed when the authors close it as wontfix. Otherwise OSS is pretty much as-is, where-is, with the exception of very widely used and corporately supported projects.