[FEA] Enable discussions

[jarmak-nv]

Description

This PR removes the Question issue type and template in favor of using GitHub Discussions. The new file, config.yml, adds a link in our discussions in the submit issue page so it works just like an issue template.

Reasoning

[QST] issues are largely inactionable and hard to act upon, it's better for us to discuss a question/comment/thought and then file a feature/bug/doc request as needed at the end of the conversation. It allows for free-form discussion and prevents the problem of 'when is a question done?' for closing the issue.

This should not be merged until Discussions are enabled, so the https://github.com/rapidsai/cuspatial/labels/5%20-%20DO%20NOT%20MERGE label has been applied. (Thanks @raydouglass!)

Checklist

• I am familiar with the Contributing Guidelines.
• New or existing tests cover these changes.
• The documentation is up to date with these changes.

[harrism]

/merge

[ajschmidt8]

@harrism, it looks like your /merge comment had some trailing whitespace which prevented it from working properly. I will re-comment.

[ajschmidt8]

/merge

[harrism]

I can't see any trailing whitespace, even if I click edit on my comment. Perhaps /merge should ignore trailing whitespace?

[ajschmidt8]

I can't see any trailing whitespace, even if I click edit on my comment. Perhaps /merge should ignore trailing whitespace?

I saw some new lines when I clicked Edit on your comment.

But agreed. This is the second time this week that whitespace prevented a merge from working correctly.

Just pushed the commit below to trim whitespace from the merge comment. It will be deployed and take effect in a few minutes.

• rapidsai/ops-bot@da0cfa7

[harrism]

Thanks!