I think the problem isn't it being open source but it being GitHub flavored open source. If you're building a product, you probably should not be having it on GitHub with issues enabled.

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

You can restrict issue creation/comments etc to certain users if you don’t want to open it to the public. You can also use a separate repo: https://docs.github.com/en/repositories/creating-and-managin...

It’s a choice the maintainer has to make.

To me this is mostly self inflicted pain…

Yes and no.

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.

I think you’ve just argued that devs have a lack of knowledge and just do what other people do with very little agency of their own, despite all the controls being available to them to them to solve problems. I agree with you. Devs need to be stronger willed and have more self respect. You can’t wait for rando users to stop being a-holes.

I can't feel that this stance will could soon evolve into "it is completely insane how any random individual ... can access the source code".

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).

> Slippery slope fallacy out of nowhere

> 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.

That's absurd. The source code being open and redistributable is the key point.

No open source maintainer is obligated to run a public issue tracker or listen to users at all if they don't want to.

I support a product that have been packaged in many Linux distributions. I have no "ticket" system whatsoever to speak of. I read email whenever I feel like. I delete all email I just dont care about as if it was spam, and respond only to messages which estimulate me.

Why do people feel that maintaining open-source software is stressful again?

some people don't like saying no, even if it is silently by not responding to email

Open source doesn't mean open support, nor open contribution for that matter.

I wish Github would allow me to hide the Issues and PR tabs from my projects.

You can hide the Issues tab, but not PRs. In the PRs you can set a PR template the says you don’t accept PRs and set up a very simple GitHub Action workflow that auto-closes and locks PRs opened by others.

At that point you are better off hosting the code elsewhere (e.g. on your own server). The only real reason to use GitHub is for low-friction collaboration.

..followed by "YOUR PROGRAM IS +*ç% AND YOU ARE INCOMPETENT".

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.

Or "my antivirus doesn't like your unsigned executable pls fix".

Meh, I've maintained open source projects before and these comments are trivially easy to ignore.

You have not maintained popular open source projects for consumers then. There is a reason why the VLC repo no longer has an Issues tab: https://github.com/videolan/vlc

PRs can’t be blocked and you can already see some junk there: https://github.com/videolan/vlc/pulls

No, that's because the VLC GitHub repo is only a mirror and the main repo is on their own GitLab at https://code.videolan.org/videolan/vlc/

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.