Forward questions to github discussions

[PrivatePuffin]

Motivation and Context

The issue tracker currently contains a LOT of questions, but is not really designed to handle with them:

• Closing issues make them less accessable
• Question-Issues don't get closed as soon as the question is solved

With the enabling of "Github Discussions", we can start to actively move those issues to Github Discussions.

Description

When creating an issue, you get a page what type of issue you want to submit.
This page also points you towards other community channels, like the mailinglist.

This PR:

• Changes the link for questions, to the discussions system.
• Removes the old page to create "question" type issues.
• Rephrases it to include more general questions

How Has This Been Tested?

It's pretty basic, really.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Performance enhancement (non-breaking change which improves efficiency)
• Code cleanup (non-breaking change which makes code smaller or more readable)
• Breaking change (fix or feature that would cause existing functionality to change)
• Library ABI change (libzfs, libzfs_core, libnvpair, libuutil and libzfsbootenv)
• Documentation (a change to man pages or other documentation)

Checklist:

• My code follows the OpenZFS code style requirements.
• I have updated the documentation accordingly.
• I have read the contributing document.
• I have added tests to cover my changes.
• I have run the ZFS Test Suite with this change applied.
• All commit messages are properly formatted and contain Signed-off-by.

Signed-off-by: Kjeld Schouten-Lebbing [email protected]

[PrivatePuffin]

@behlendorf I'm also thinking we might want to start moving "feature" tagged issues to the "Idea's" board.
Just like questions they are not "really" issues and are also quite long-term...

[behlendorf]

@Ornias1993 yes, I had the same thought. After working through the open questions I think it makes sense to take a look at the features.

[PrivatePuffin]

@behlendorf I also spend some time looking at the features...
It's a bit less clear-cut:

1. We have 220(!) feature requests, about half of which are ancient, stale and sometimes not even relevant anymore
2. Having them as issues does give them additional visibility and they are often valid code improvements

I've debated if we should split them into features and enhancements, but going through them I noted: that doesn't solve anything and only makes things harder for the user.

1. Gets solved by moving them to discussions, as more active discussions get bumped to the top. So it provides a natural filter.
2. Most of the time either a feature request gets put in as a PR regardless of the request or the feature request never gets made anyway. It doesn't look like there actually is any relationship between feature-request issue creation and the feature being made.

So I think we can (at least) start by pointing feature-requests to the discussions system when creating an issue....
and start moving more feature requests, that would lower the issue count to a little more than 500, which is workable.