@RoyGreenhilt @tindall The problem is that code hosting platforms only have bug trackers built-in, and we don't have free and easy to use _discussion_ platforms that would be popular with people and could be used for support requests.
People misuse bug trackers for support requests, and repo maintainers get annoyed because indeed closing what is supposed to be a bug report is logically on the one who opened it, and having many open bug reports looks bad.
@dmbaturin @tindall I hear that, and you're right. (You don't know my background, but the opensource project I wrote was one of the very popular bug / support trackers back in the 90s). It could handle both support and bug requests, and was used for both.
In modern FOSS though, things like github's Issues are... issues. Bugs. Things that can be linked to PR's. Using them for support is definitely a weird mix.
@RoyGreenhilt @tindall Yeah, my point exactly. Sometimes I'm thinking of a free and, ideally, federated platform for "bugs+discussions", where discussions can be converted to bugs if needed, but are separate concepts.
GH/GitLab/Gitea issues have, well, multiple issues even as pure bug trackers, starting from the fact that they are limited to a single repo.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!