You hate tickets without repro? Enjoy the barrage of “help. Doent work”, “me too” and “HELLO IT’S BEEN 3 DAYS” messages.
There are very good reasons why the support processes of commercial entities that build products are the way they are. You do want a lot more friction and you do likely want to limit support to paying customers.
GitHub-style public issue trackers are just a bad idea overall IMO. They only work if the "public" is only "public" because everyone _in theory_ could take part. In practice however, you only want to grant such unlimited write access to vetted individuals. This happened to happen automatically previously (because getting to the point where you even know where to open a ticket _was_ part of the vetting process), but with GitHub as the default for everyone and everything, it needs to be a conscious effort.
If you think about it, it is completely insane how any random individual just has to press one button to publish whatever they want to a super prominent part of what is effectively your products/projects website. That simply shouldn't be a power random individuals have
It’s a choice the maintainer has to make.
To me this is mostly self inflicted pain…
Sure, countermeasures exist, but the issue is that you first need to be aware of what exactly the problem is before you can take these countermeasures.
The reality however is that people just hear "You should do GitHub" and then for some inexplicable reason slowly descend into feeling bad without any clear reason why. After all, they're following all the "best practices" laid out by people that clearly know what they're doing and surely have their best interest in mind.
Open source was built on the spirit of openness. Rather than closing it, I think solutions should be proposed to improve it (thinking of it, it's a good place for using LLM-s - you don't need perfection for checking a bug report makes some sense and filtering people a bit).
> Throw magic at the problem to further scale resources to sustain a problem instead of actually solving said problem
I can only encourage people to counter bullshit with minimum resource investment. Full-sentence answers should be limited to those statements deserving of them.
No open source maintainer is obligated to run a public issue tracker or listen to users at all if they don't want to.
Why do people feel that maintaining open-source software is stressful again?
I wish Github would allow me to hide the Issues and PR tabs from my projects.
Cannot underestimate mental health issues after a barrage fire of those messages, usually by people who could not bother to read the README.1ST - been there, done that.
PRs can’t be blocked and you can already see some junk there: https://github.com/videolan/vlc/pulls
Slightly higher friction for reports from the unwashed masses might be a slight side benefit but not having multiple separate issue trackers already is it's own reason.