I think all bugs should be tracked on GitHub issues over forem.dev posts. The problem is it is really hard to know what is a bug and what is not. I don't think there is a wrong post for GitHub issues either. I understand why active FOSS projects try to push user support out of GitHub issues because supporting the user base can often cause a bunch of noise for contributors that are trying to fix bugs and add features.
An example would be forem.dev/avalerionv/difficulty-in... which most likely should have been a GitHub issue to start out with but it was going to be a lot of work to ask the user to open an issue instead of following up in their forem.dev #help post.
I just want to help people use Forem as quickly and easily as possible and it is easier for me to track everything GitHub because that is where the code changes/fixes will get pushed. I don't think there is a wrong spot for this kind of stuff and it is going to be a mix between the two systems.
For further actions, you may consider blocking this person and/or reporting abuse
I think all bugs should be tracked on GitHub issues over forem.dev posts. The problem is it is really hard to know what is a bug and what is not. I don't think there is a wrong post for GitHub issues either. I understand why active FOSS projects try to push user support out of GitHub issues because supporting the user base can often cause a bunch of noise for contributors that are trying to fix bugs and add features.
An example would be forem.dev/avalerionv/difficulty-in... which most likely should have been a GitHub issue to start out with but it was going to be a lot of work to ask the user to open an issue instead of following up in their forem.dev #help post.
I just want to help people use Forem as quickly and easily as possible and it is easier for me to track everything GitHub because that is where the code changes/fixes will get pushed. I don't think there is a wrong spot for this kind of stuff and it is going to be a mix between the two systems.