Feature/doc fixes for open source (#150)

* Added .idea to gitignore

* PR feedback

Author: joshmarsh

.github/ISSUE_TEMPLATE/bug_report.md

@@ -8,23 +8,27 @@ assignees: ''
 ---
 
 **Version information**
+<!--
 - The version of DCE.
 - OS and version
 - Go version
 - Terraform version (if using directly)
+-->
 
 **Describe the bug**
-A clear and concise description of what the bug is.
+<!-- A clear and concise description of what the bug is. -->
 
 **To Reproduce**
+<!--
 Steps to reproduce the behavior:
 1. Go to '...'
 2. Click on '....'
 3. Scroll down to '....'
 4. See error
+-->
 
 **Expected behavior**
-A clear and concise description of what you expected to happen.
+<!-- A clear and concise description of what you expected to happen. -->
 
 **Additional context**
-Add any other context about the problem here.
+<!-- Add any other context about the problem here. -->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -8,13 +8,13 @@ assignees: ''
 ---
 
 **Is your feature request related to a problem? Please describe.**
-A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
 
 **Describe the solution you'd like**
-A clear and concise description of what you want to happen.
+<!-- A clear and concise description of what you want to happen. -->
 
 **Describe alternatives you've considered**
-A clear and concise description of any alternative solutions or features you've considered.
+<!-- A clear and concise description of any alternative solutions or features you've considered. -->
 
 **Additional context**
-Add any other context or screenshots about the feature request here.
+<!-- Add any other context or screenshots about the feature request here.-->

.github/pull_request_template.md

@@ -9,7 +9,7 @@ Describe the big picture of your changes here to communicate to the maintainers
 ## Types of changes
 
 <!--
-What types of changes does your code introduce to the module?
+What types of changes does your code introduce to the repo?
 Put an `x` in the boxes that apply
 -->
 
@@ -31,21 +31,6 @@ Put an `x` in the boxes that apply. You can also fill these out after creating t
 - [ ] I have updated the `CHANGELOG.md` under a `## next` release, with a short summary of my changes
 
 
-## Dependencies and Blockers
-
-
-
-<!--
-
-Is there anything preventing this PR from being merged and deployed to prod?
-
-eg. other PRs that are required, external blockers, etc.
-
-If so, this is a high-risk deployment, and we should call this out for manual attention
-
--->
-
-
 ## Relevant Links
 
 <!--

.gitignore

@@ -60,6 +60,7 @@ override.tf.json
 
 # Other stuff
 *.zip
+.idea/
 
 junit-report/
 test.output.txt

CONTRIBUTING.md

@@ -20,7 +20,7 @@ We have some general guidelines towards contributing to this project.
 
 *Go*
 
-The source code for this project is written in Go. You are welcome to add versions of files for other languages, however the core code will remain in Go.
+The Lambda and CodeBuild function code is written in Golang.  We prefer that similar contributed code also be written in Golang.  Please ensure your Golang code is formatted by [gofmt](https://golang.org/cmd/gofmt/) and linted by [golint](https://godoc.org/golang.org/x/lint).
 
 ## Pull Requests