Issue templates

[TomasTorsvik]

Hi all,
I have added some templates for the issue tracker in the NorESM repository. The main objective is to have a checklist for what should go into an issue (e.g. for bug fix, what NorESM version, machine settings have been used), and assign persons who should be main responsible to respond to specific types of issues (assignees can be changed after an issue has been raised, if the "first responder" is not closest to the problem that is raised).

I hope that this system can be helpful or us, but we should fill it with some content specific for NorESM (now it's mostly generic github templates). Could you have this as a discussion point for the next noresm-core meeting?

• what issue templates should we have? (probably it's good to have a fairly short list, and keep on "general issues" in case nothing fits)
• who should be assigned to the different issues? (maybe one or two persons for each issue type?)
• what content should be in the issue template?