Sometimes they are a help desk, because many times newer users of a framework don't know enough about how the framework was built to determine if something is a

Sometimes they are a help desk, because many times newer users of a framework don't know enough about how the framework was built to determine if something is a bug with the framework or a bug in their code. Some JS stuff moves so quickly that a new version is cut weekly and bugs are introduced as often / previously-working code breaks in ways the non-framework developers don't understand. In these cases, reporting the issue against the GitHub project can help them solve it, so I'd argue that it's not a bad thing to be posting error reports assuming they're actually unique issues which you're reasonably certain are something in the framework / library / whatever. I'm guessing that your point though is that it shouldn't just fill the same role as SO where less-experienced devs are posting problems with easier / more obvious solutions, but defining where that line is is very difficult.