Add PR, Issues for bugfix and feature request templates. (#167)

* add PR templates for feature and bugfix
Change-Id: Iad15dd1a584f4bd2fbaadf88359a55efd7b1925c
* add codeowners for automatic review requests
Change-Id: If6050e6411519223f514435801e09a63ed696a02
* Update CODEOWNERS

.github/CODEOWNERS

@@ -0,0 +1,13 @@
+# This is a comment.
+# Each line is a file pattern followed by one or more owners.
+# Order is important; the last matching pattern takes the most
+# precedence.
+
+# Everything in ufs-weather-model should be also be owned by the UFS Weather Model Gatekeepers
+* @ufs-community/ufs-wm-gatekeepers
+
+# The components are owned by their respective teams
+/FV3/ @noaa-emc/fv3atm-team
+/NEMS/ @noaa-emc/nems-team
+#/FMS/ @noaa-emc/fms-team
+#/FMS/ @noaa-gfdl/fms-team

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,41 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+## Description
+Provide a clear and concise description of what the bug is.
+Also give a description of what behavior you expected to happen.
+
+
+### To Reproduce:
+What compilers/machines are you seeing this with?
+Give explicit steps to reproduce the behavior.
+1. do this
+2. then that
+3. then, oops, look at the bug
+
+
+## Additional context
+Add any other context about the problem here.
+Directly reference any issues or PRs in this or other repositories that this is related to, and describe how they are related. Example:
+- needs to be fixed also in noaa-emc/nems/issues/<issue_number>
+- needed for noaa-emc/fv3atm/pull/<pr_number>
+
+
+## Output
+
+**Screenshots**
+If applicable, drag and drop screenshots to help explain your problem.
+
+**output logs**
+If applicable, include relevant output logs.
+Either drag and drop the entire log file here (if a long log) or
+
+```
+paste the code here (if a short section of log)
+```

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,22 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: enhancement
+assignees: ''
+
+---
+
+## Description
+Provide a clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+## Solution
+Add a clear and concise description of what you want to happen.
+
+## Alternatives
+If applicable, add a description of any alternative solutions or features you've considered.
+
+## Related to
+Directly reference any issues or PRs in this or other repositories that this is related to, and describe how they are related. Example:
+- required to support noaa-emc/nems/issues/<issue_number>
+- needed by noaa-emc/fv3atm/pull/<pr_number>

.github/pull_request_template.md

@@ -0,0 +1,35 @@
+## Description
+
+(Instructions: this, and all subsequent sections of text should be removed and filled in as appropriate.)
+Provide a detailed description of what this PR does.
+What bug does it fix, or what feature does it add?
+Is a change of answers expected from this PR?
+
+
+
+### Issue(s) addressed
+
+Link the issues to be closed with this PR, whether in this repository, or in another repository.
+(Remember, issues should always be created before starting work on a PR branch!)
+- fixes #<issue_number>
+- fixes noaa-emc/fv3atm/issues/<issue_number>
+
+
+
+## Testing
+
+How were these changes tested?
+What compilers / HPCs was it tested with?
+Are the changes covered by regression tests? (If not, why? Do new tests need to be added?)
+
+
+
+## Dependencies
+
+If testing this branch requires non-default branches in other repositories, list them.
+Those branches should have matching names (ideally)
+
+Do PRs in upstream repositories need to be merged first?
+If so add the "waiting for other repos" label and list the upstream PRs
+- waiting on noaa-emc/nems/pull/<pr_number>
+- waiting on noaa-emc/fv3atm/pull/<pr_number>