GitHub Discussions for questions and translations

[Zeitsperre]

Pull Request Checklist:

• This PR addresses an already opened issue (for bug fixes / features)
  • This PR fixes Adopt Category Forms for Community Questions #1571
• Tests for the changes have been added (for bug fixes / features)
  • (If applicable) Documentation has been added / updated (for bug fixes / features)
• CHANGES.rst has been updated (with summary of main changes)
  • Link to issue (:issue:number) and pull request (:pull:number) has been added

What kind of change does this PR introduce?

• Migrates the Question/Support Issue Template to a GitHub Discussion Template
• Adds a new page for coordinating translation efforts
• Added a link to PAVICS for PAVICS-specific questions. Once we have a Discourse up and running, we'll be able to funnel all PAVICS-specific question there.

Does this PR introduce a breaking change?

Not really. This makes it so that the following can happen more easily:

• Answered support requests will more easily be found by users with similar usage questions. This will make it simpler for users as answering a discussion post does not hide the post like closing an issue does.
• Translation efforts can now more easily be coordinated outside of Pull Requests for users wishing to contribute translations in languages other than English or French. In a previous attempt, the major translation effort was performed in a Pull Request with 100+ comments in it and was impossible to navigate near the end. I've noticed similar translation efforts (using GitHub Discussions) organized in other projects, such as FastAPI (https://github.com/tiangolo/fastapi/discussions/categories/translations).

Other information:

https://docs.github.com/en/discussions/managing-discussions-for-your-community/creating-discussion-category-forms

[bzah]

I would suggest to also update the Readme, in particular the Contributing to xclim section in order to guide user to the github discussion forum instead of gitter.

[Zeitsperre]

I would suggest to also update the Readme, in particular the Contributing to xclim section in order to guide user to the github discussion forum instead of gitter.

That's a good idea. I don't seem to have admin access over the Gitter room, so I can't make changes. Does anyone know who created the room? @huard?

[Zeitsperre]

Update: so in order to retire the Gitter room, I need to manually kick everyone out of it (and ask any existing moderators to leave). It doesn't seem like there's an easy way to close down a room other than booting everyone and making it private.

I've saved the chat log (it wasn't very long, TBF), so once this Pull Request is in, I'll start the process of winding the Gitter down.

[coveralls]

coverage: 90.304%. remained the same
when pulling db440a7 on discussions-templates
into dd9db13 on master.