[Documentation] Set up GitHub Issue Templates

[aonomike]

Set up TEMPLATE.md files to guide contributors creating new issues on the standard of the detail to include on their issues. Something more like this

[lpatmo]

FWIW, the minimum I'd like to see in an issue template, personally, are:

Context

Acceptance Criteria

[ ] Example task 1
[ ] Example task 2

Other implementation notes (to help the contributor who makes the PR)

[BethanyG]

@lpatmo - assigned the two of us, since we've been going back and forth on the PR templates, and you mentioned you wanted to look at issue templates as well. Happy to take a first shot at this, or you can. 😄

[BethanyG]

Just going to put this here as a possibility. You can have multiple issue templates:

[lpatmo]

Proposal for the types of issues we can have:

• Ask a question (linking to a new discussion under the question category)
• Bug
• Feature
• Refactor
• Documentation
• Other

(kind of paralleling what we have in the PR template)

... and TBD on the content that should go in each of them :D

[BethanyG]

That looks great!

I wonder if we also want Start a discussion? I go back and forth. On one hand, we're socializing the discussions pretty hard right now in the community. On the other - if someone has a proposal that they want to discuss - do we want them opening bug or feature issue about it (with maintainers moving things to discussion as needed) - or do we want to prompt contributors to do it the other way around? Either works. Really don't have a strong opinion there.

Other "categories" that come to mind are:

1. Tooling -- or is that generally covered under "other"?
2. Tests Needed - or is that just asking for trouble?

[BethanyG]

..with automation, we can also put appropriate tags on the templates, as well as putting them into a "triage" area in a project, assigning a team to review, etc. etc. Haven't read all of this - but here is the GitHub documentation

Here, also for ease of access is the current documentation for multiple issue templates in GitHub

[lpatmo]

Updated proposal (merging in your suggestions for Tests Needed and Start a Discussion):

Ask a question (linking to a new discussion under the question category)
Bug
Feature
Refactor
Documentation
Tests Needed
Start a Discussion
Other

[BethanyG]

Looks good! We can work on template drafts as we find time this week....or next! 😄

[lpatmo]

Thanks! ... yeah, looking more like next week :)

[BethanyG]

@lpatmo hate to "bump" this..but if we are going to work on it, now is probably a good time..before we get overrrun in Hackoberfest. 😄

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[BethanyG]

@lpatmo Is this something we still need/want to work on, or do we close this?

[lpatmo]

Sorry, this is still on my list! (Will try to get to this after I finish taking notes on Bill's deployment findings)