create issue and pull request template. (dotnet#765)

* Initial draft of issue and pull request template.

These will provide guidance when someone creates a new issue, or a new
pull request respectively.

* reference CONTRIBUTING.md in issue

* Update based on feedback

First cycle of feedback

* move files to .github directory

* update from feedback

* Respond to feedback.

Trying to simply both templates as much as possible.

* Updates based on @tdykstra review

* Updates from final review

Author: BillWagner

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,37 @@
+# Issue Title
+
+Be as descriptive as you can with your title. If your issue requests
+a new topic, preface the title with [NewTopic].
+
+# General
+
+We use issues to drive the discussion for changes to
+existing topics and the creation of new topics.
+
+This way, we have those discussions before significant
+effort is spent writing a new topic. Click on the Guidelines
+for Contributing link above for details.
+
+## Issues with Existing Topics
+
+If the issue is a simple typo or similar correction, you can just submit a PR.
+Otherwise, let us know what's wrong or what we should improve. Include a
+link to the topic.
+
+## Requests for new Topics
+
+1. Tell us where this topic should go in the Table of Contents.
+
+   - Consider where you looked for this information before opening an issue.
+
+2. Write an abstract
+
+   - In one **short** paragraph, describe what this topic will cover.
+
+3. Fill in an outline
+
+    - Write a complete outline for the new topic. We'll help review the outline and approve that before anyone writes a topic.
+
+4. Suggest reviewers
+
+    - If you know someone who can provide feedback, use '@' to ask them to review.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,30 @@
+# Title
+
+On the title describe
+what you've fixed (or created) with this Pull Request (PR).
+
+## Summary
+
+Insert a short (one or two sentence) summary here.
+
+Fixes #Issue_Number
+
+>Note: The "Fixes #nnn" syntax in the PR description causes
+>GitHub to automatically close the issue when this PR is merged.
+> Remove that line if you don't have issues associated with this
+> PR. Click on the Guidelines for Contributing link above for details.
+
+## Details
+
+Explain your changes, and why you made them. If that
+information is already available in the issue referenced
+above, just referencing the issue is preferred to copying
+the text.
+
+This may not be necessary depending on the scope of the PR 
+changes. For example, "fix typo in introduction.md" is
+sufficient to describe that PR.
+
+## Suggested Reviewers
+
+If you know who should review this, use '@' to request a review.