Identify support requests, feature requests in issues and pull requests

[gonzalo-bulnes]

Until now, the only official place for the community to interact was Issues. The newly introduced Discussions space is a better place to ask for support and to suggest or request new features.

Why?

Support

• The time I am willing to dedicate personally to support is limited, so support requests in issues would potentially remain unattended for a long time unless someone else can help.
• I have reasons to believe that Discussions could make easier for people to get involved and provide advice to others requesting support, they have a better name to start with!

Feature suggestions or requests

• Not every feature that could be added should be added. The decision to add new features requires a nuanced evaluation of the implications and calls for a discussion.
• While I think of "fork and showcase" would be a traditional way of testing and making a case for new features, I have only seen a few instances of it (good ones though, e.g. https://github.com/adamniedzielski/tiddle). I believe Discussions would again be a more accessible place to have design conversation before a lot of effort is invested in pull requests that are not necessarily adapted to the project goals.
• The project goals are unclear to most people opening pull requests (PRs), and I haven't been very successful at sharing that context in issues/PRs as far as can tell. Again, I've reasons to think that Discussions and Projects could be a better fit for that.

Goal

The goal of this action is to address https://github.com/gonzalo-bulnes/simple_token_authentication/projects/1#card-52075174.

Actions

• [x] Create labels if necessary
• [x] Label the open issues and pull requests
• [ ] (Maybe?) Label the closed/merged issues and pull requests as well?

[gonzalo-bulnes]

Created labels:

• support request: should probably be redirected to Discussions Q&A.
• feature request: should probably be redirected to Discussions Ideas.
• new feature: should probably be redirected to Discussions Ideas too. Some of them have been discussed in linked issues or the PR itself, but if they haven't been merged yet, it is worth having a chat about them.

That add themselves to:

• documentation request: should probably be redirected to the discussion on making documentation more useful: https://github.com/gonzalo-bulnes/simple_token_authentication/discussions/372.
• (closed) question: that I refer to as the FAQ in the README, and could certainly inform the same discussion (#372).