Thanks for taking the time to reply.
This is reported many times
Yes, it was, and all reported issues are closed, and yet the problem is not solved. In my report, I make reference to those other reports and state clearly why their solution is not sufficient.
A good chunk of reported issues are:
- Not correctly reported i.e. lack any kind of actionable info
- Duplicates / old issues
- just random cries for help
There’s only so much we can do, so to prioritize stale bot has to be there.
I’ve been around in open source long enough (+25y) to know the challenges well.
I fully agree with you that many issues fall into one of the mentioned categories. But by applying stale rules indiscriminantly against all reports, no matter if they fall into one of those categories or not, is disheartening for those who are indeed trying to make a real contribution.
Here is how other, successful projects handle the same challenge:
Insufficient information: Feedback is requested from the reporter. Here, a stale bot could indeed support with removing/closing issues if no feedback is provided after some time.
Duplicates: Linking to the duplicate with subsequent closure of the report. This also helps future visitors understand that the issue is actually resolved.
Random cries for help: Remind the reporter that the forum is the place for general discussions and close the issue.
ERPNext is an open source project. Some users, such as myself, may be paying for services but no one is paying for the software. I understand that my issue must be interesting for enough people, particulary developers, for it to be looked at and solved. As an alternative, if the issue is that important to me, I can pay someone to have a go at it.
But just because no one feels the need to work on my issue, does not mean that it’s not an issue or, worse, that it has been solved. On the opposite, the issue I reported is “actively affecting humans”, as you put it in your justification.
So, by closing my issue without putting any work into it, you actually do set false expectations to visitors of your GitHub page because it will seem that your team is a lot more active than it actually is.
If there has been no interaction with an issue whatsoever, it should not be closed.