I’ve had extremely frustrating and contentious discussions with maintainers who choose to put forms in front of their issues in their repositories.<p>It’s bad enough that<p>1) if I use the project and can’t easily switch from it, I will simply not contribute in any way to the project from that point forward (I’ve filed two issues with Vue.js projects; I will not be filing any more, because they are horribly user-hostile);<p>2) if I don’t use the project, I will _never_ use the project and generally question why people are using the project (remarkjs).<p>Having an issue template is fine. Closing issues that don’t follow the template is (mostly) fine. Taking me to an entirely _different_ website to fill in your form and yelling throughout the whole thing that your bug will be closed if you don’t follow the steps of the time warp _exactly_…is user hostile. I get it that there are entitled users of projects. But by disabling issues or putting a form in front of issue reporting…you have told me that you don’t actually _want_ users, so I’m happy to oblige.<p>I was looking for an excuse to try Svelte anyway.
Maintainer of the repo here.<p>I disabled the issues of most of my projects.
Over the years I have observed that people who actually contribute value, do not need the issue section. They will directly open a PR with a change or at least some code that explains their problem.<p>People started arguing with me about this topic. But these where never the people that actually contributed to any open source project that was not their own, so I do not care at all.<p>I opened the discussion section so people can actually discuss there, without wasting the time of the maintainer.
Slightly related to this, I can't understand why Github doesn't offer a "read-only" mode for issues. Once a repo is archived or issues are disabled, all issues are then unavailable. This is super annoying as it causes many broken links.
While I understand the frustration caused by people not respecting maintainer's time, I don't understand the reluctance of looking for an additional maintainer to help curate the issues.<p>What's your take on this?
Do you have any experience in this area?