Making issue and PR templates better & discussions

[blackfalcon]

The issue templates as we have them now were designed to serve a purpose. The question here is, are they still serving that purpose?

There have been many instances where the template of a PR or Issue has been ignored, if not deleted, and absolutely minimal information was entered into the textareas.

I am also inspired by Shoelace's configuration of their Issues landing page that pushed users asking for new features or help over to the Discussions board. https://github.com/shoelace-style/shoelace/blob/next/.github/ISSUE_TEMPLATE/config.yml

It's not a bad idea to have an open discussion board for all of Auro's repos where anyone can suggest new work and not have the confusion of creating a new issue for the feature.

Microsoft's FAST UI has some interesting things in its issue and PR templates.
https://github.com/microsoft/fast/tree/master/.github

[blackfalcon]

Something else I want to add to this conversation is updating the FEATURE issue template is to replace "Describe alternatives you've considered" with "What is the cost of not doing this work?"

Reasoning the cost of not doing the update is a very real conversation. There are a lot of resources out there that speak to this, but the real discussion to have is, sure there is a cost of time and materials for DOING the work, but what will it cost the team, our users, etc... if we do not make this update?