[DOCS] Add a miscellaneous issue form

[Panquesito7]

Feature description

By adding a miscellaneous/other issue template/form, we can make other types of issues that do not fit any of the provided templates.
The benefits of adding this would include the ability to:

• Create good first issues, which are beginner-friendly opportunities.
• Create GitHub repository discussion issues, such as the Code of Conduct, licenses, and other community files.
• Make to-do lists for improving the repository or such.
• Prevent blank issues to be created with no information. The miscellaneous template can have a required field that asks for a description.

What do you think about this? Thanks. 🙂

[swaindhruti]

Can you please specify that "adding miscellaneous/other issue template or form" means to add it to the repo or add it to one of the particular repo folders? And what type of output do you expect from the form?

[Panquesito7]

I mean to the repository itself when reporting an issue.
What do you mean exactly by output? 🤔

[swaindhruti]

By output I mean that what do you want that form to do mean to categorize the issues with the help of description to avoid unnecessary and unsubscribed issues or any thing else?

[Panquesito7]

By output I mean that what do you want that form to do mean to categorize the issues with the help of description to avoid unnecessary and unsubscribed issues or any thing else?

I'm not sure I understand well. 😅

[swaindhruti]

nah my fault I was just getting too deep in the issue; I might solve it, and I'll let you know if I do.Thanks for replying to my queries 😊

[Aryank1310]

In addition, having a miscellaneous template could also facilitate the creation of to-do lists for repository improvements, which can help to organize and prioritize tasks more effectively. By requiring a description in the miscellaneous issue template, it can also help to prevent blank or incomplete issues from being created.

[Panquesito7]

CC: @cclauss, @dhruvmanila, what do you think about this?
Should I create a pull request for this or?

[dhruvmanila]

I have no opinion on this. If you think it's useful, you can go ahead with the PR :)