Use issues for confirmed bugs and accepted features, use Discussions for Q/A Help and Show and Tell!

[reconbot]

💥 Proposal

What feature you'd like to see

I want to separate out bugs, new features and support and maybe start using the Issue forms to gather requirements on bug reports.

Motivation

I'm inspired but a bunch of other open source projects graphql-ws for example. That have started to use the discussions tab in github. It's super clear what open issues there are with the project and where to go for help.

Pitch

I want to move proposals and help issues to discussions, and keep issues for accepted proposals and confirmed bugs. I think once that's in place issue forms might help ensure good bug reports.

[reconbot]

cc @HipsterBrown @GazHank @fivdi @frank-dspeed and probably half a dozen people from support issues that have been incredible at helping others.

[GazHank]

If it results in zero open issues (per graphql-ws) then who could argue with that!

Just let me know how I can help 👍🏼

[frank-dspeed]

Splitting it up is clear a hugh win while issues get the most attention i think handling issues more clear is better then splitting. Unless the splitted diskussions get as much attention as issues. So if you got a big team that handels that go for that. If not Stay with issues.

[reconbot]

It's done #2285

[reconbot]

Added a bug issue form and directed people to discussions for support.

Try it out! https://github.com/serialport/node-serialport/issues/new?assignees=&labels=&template=1-bug-report.yml