Add bug form

[juancarlospaco]

• Continuation of RFC Form RFCs#459 (comment)
• No code in this PR just GitHub repo metadata stuff.
• Form for bug reports and feature requests.
• Users can fill in information about OS, Hardware, etc that can be useful for devs (users can choose "Unknown" too).
• See how it works at https://github.com/nim-lang/RFCs/issues/new?assignees=&labels=unconfirmed&template=bug_report.yml

I changed the existing template in the repo to a GitHub issue form, just 2 YAML.

https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema

Just improving the UX and making things easier for the users. 🙂

[ringabout]

Thanks for your hard work! I think there are too many required selections. Collecting info regarding "Where are you from" doesn't seem necessary (anyway, using continent instead of country and Region could be better).

[juancarlospaco]

Collecting info regarding "Where are you from" doesn't seem necessary.

I prefer to ask the user (if they want to reply) than adding user-tracking to Nim:

• Analytics data dom96/choosenim#144 (comment)
• Move choosenim under Nim org RFCs#374 (comment)

[konsumlamm]

Thanks for your hard work! I think there are too many required selections. Collecting info regarding "Where are you from" doesn't seem necessary (anyway, using continent instead of country and Region could be better).

I agree. I don't see how disk storage, memory capacity, CPU cores, internet connection, web browser are relevant either. For most bug reports, it just creates useless clutter in the issue report and in the few cases where that information is relevant, I think we can expect the creator to include that information.

[juancarlospaco]

I think we can expect the creator to include that information.

I think the problem usually is that bug reports have too scarce information,
bug reports with too much information is not a very frequent problem.

As a dev myself I think it is very useful,
example if the user says uses Linux, you can just reply with Bash commands to fix it,
if the user says 32bit Windows maybe the hardware is too old for the software, etc,
gives more context of the problem, instead of the typical "shit wont work lol" kind of reports.

You can just not fill it in anyway... 🤷

[Araq]

You can just not fill it in anyway... 🤷

You can also just not fill in a bug report if the task appears to be overwhelming...

[juancarlospaco]

You can also just not fill in a bug report

I agree, sending a PR instead is also an alternative, as the current template suggests too.

@Araq
Let me know what do you want to remove or add to the form.

[Araq]

I don't understand it, your screenshot is about RFCs, not about bug reports.

[juancarlospaco]

your screenshot is about RFCs, not about bug reports.

True, I removed the screenshots.

It is similar to the one on the RFC repo, but for this repo,
I added fields to the form for info that may be useful for devs to get more context of the bug,
but it is easy to remove the fields, no problem,
it is flexible to whatever you think a bug report form should look like,
what do you want to know when you read a bug report ?

[ringabout]

Here is the preview

https://github.com/nim-lang/Nim/blob/184b5abb92d5d40b886694d92110cebc17d8276d/.github/ISSUE_TEMPLATE/bug_report.yml

https://github.com/nim-lang/Nim/blob/184b5abb92d5d40b886694d92110cebc17d8276d/.github/ISSUE_TEMPLATE/feature_request.yml

[juancarlospaco]

Here is the preview

Thanks @xflywind thats a lot more direct lol 🙂:+1:

[juancarlospaco]

@Araq
Any blockers to merge this?, it is not even code, so should be easy to merge,
if some field needs to be removed let me know, any user can improve it later anyways.

[github-actions]

Thanks for your hard work on this PR!
The lines below are statistics of the Nim compiler built from 2f3980f

Hint: mm: orc; threads: on; opt: speed; options: -d:release
163582 lines; 12.474s; 841.172MiB peakmem