Repository: optuna/optuna
Pull request: Add an issue template.
This PR adds an issue template.
Close https://github.com/pfnet/optuna/issues/370 after merging this PR.

Problem statement:
Request for issue template
Could you provide some issue templates such as feature request and bug report?

Also, it'd be really helpful if there is a piece of information about how to get help when I find difficulty in using optuna?
For example, chainer officially says I can get help in Slack, Google groups, and stackoverflow.

Hints from issue discussion:
Thank you for your request.
We are creating the issue template that includes information to get support. The current version is as follows:

```
If your issue is a **request for support in using Optuna**,
please post it on [Stack Overflow](https://stackoverflow.com/questions/tagged/optuna).
Support is also available on `#general` channel of [chainer slack](https://bit.ly/join-chainer-slack)
and [chainer-jp slack](https://bit.ly/join-chainer-jp-slack).

On registering an issue, write precise explanations on how you want Optuna to be.

Bug reports must include necessary and sufficient conditions to reproduce the bugs.
More specifically, it is helpful for us if you include the following information:

- Conditions
  - Optuna version
  - Python version
  - OS
  - Machine Learning library to be optimized
- Code to reproduce
- Error messages, stack traces, or logs

Feature requests are supposed to include what you want to do
(and why you want to do, if needed) with Optuna.
You can contain your thoughts on how to realize it into the feature requests, 
though what part is most important for discussions.

Thank you for your cooperation!
```

Hopefully, it will be released in a week or so.
If you have any feedback, please let us know.
Thank you for your response.
I drop some *NOT* critical comments.

---
> You can contain your thoughts on how to realize it into the feature requests, 
> though what part is most important for discussions.

The 2nd line seems interrogative and this makes the sentence a bit complex to me.

---

> - Conditions
>   - Optuna version
>   - Python version
>   - OS
>   - Machine Learning library to be optimized
> - Code to reproduce
> - Error messages, stack traces, or logs

I prefer the below template to the above.

**Conditions**
  - Optuna version: 
  - Python version: 
  - OS:
  - Machine Learning library to be optimized: 

**Code to reproduce**
```
# python code
```
**Error messages, stack traces, or logs**
```
# stack traces
```
Thank you for your suggestion. I agree with you.
The current version is as follows:

---
If your issue is a **request for support in using Optuna**,
please post it on [Stack Overflow](https://stackoverflow.com/questions/tagged/optuna).
Support is also available on `#general` channel of [chainer slack](https://bit.ly/join-chainer-slack)
and [chainer-jp slack](https://bit.ly/join-chainer-jp-slack).

On registering an issue, write precise explanations on how you want Optuna to be.

Bug reports must include necessary and sufficient conditions to reproduce the bugs.
More specifically, it is helpful for us if you include the following information:

**Conditions**
- Optuna version:
- Python version:
- OS:
- Machine Learning library to be optimized:

**Code to reproduce**

```
# python code
```

**Error messages, stack traces, or logs**

```
# stack traces
```

Feature requests are supposed to include what you want to do
(and why you want to do, if needed) with Optuna.
You can optionally contain your thoughts on how to realize it into the feature requests.

Thank you for your cooperation!

---
Please give us a little more time for further review of the template.

This is nice to me. Thanks.

Commit message: Add an issue template.

Patch to review:
diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md
new file mode 100644
index 00000000000..fd9cc2ac1d5
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE.md
@@ -0,0 +1,34 @@
+If your issue is a **request for support in using Optuna**,
+please post it on [Stack Overflow](https://stackoverflow.com/questions/tagged/optuna).
+Support is also available on `#general` channel of [chainer slack](https://bit.ly/join-chainer-slack)
+and [chainer-jp slack](https://bit.ly/join-chainer-jp-slack).
+
+On registering an issue, write precise explanations on how you want Optuna to be.
+
+Bug reports must include necessary and sufficient conditions to reproduce the bugs.
+More specifically, it is helpful for us if you include the following information:
+
+**Conditions**
+- Optuna version:
+- Python version:
+- OS:
+- Machine Learning library to be optimized:
+
+**Code to reproduce**
+
+```
+# python code
+```
+
+**Error messages, stack traces, or logs**
+
+```
+# stack traces
+```
+
+Feature requests are supposed to include what you want to do
+(and why you want to do, if needed) with Optuna.
+You can optionally contain your thoughts on how to realize it into the feature requests.
+
+Thank you for your cooperation!
+


Code review comments:
diff_hunk: @@ -0,0 +1,34 @@
+If your issue is a **request for support in using Optuna**,
path: .github/ISSUE_TEMPLATE.md
text: @user1:
For improving readability of the raw text (this is what users see immediately after pressing `New issue` button), I think it is better to rewrite the first sentence as follows (the generated HTML is identical as before):
```markdown
If your issue is a **request for support in using Optuna**, please post it on [Stack Overflow].
Support is also available on `#general` channel of [chainer slack] and [chainer-jp slack].

[Stack Overflow]: https://stackoverflow.com/questions/tagged/optuna
[chainer slack]: https://bit.ly/join-chainer-slack
[chainer-jp slack]: https://bit.ly/join-chainer-jp-slack
```


@author:
Sounds good! I've fixed it.
Thank you for your suggestion.