[next] i18n cleanup (coralproject#2456)

* fix: removed english translations from es files

* feat: improved github messaging

.github/ISSUE_TEMPLATE/BUG.md

@@ -0,0 +1,30 @@
+---
+name: Bug report
+about: Create a report to help us improve
+labels: "bug"
+---
+
+<!--
+Please provide as much detail as possible, including a screenshot or copy-paste of any related error messages, logs, or other output that might be related. Places to look for information include your browser console, server console, and network logs. The more information you can give the better.
+
+Please help us by doing the following steps before logging an issue:
+  * Search: https://github.com/coralproject/talk/search
+  * Read the docs: https://docs.coralproject.net
+
+Please fill in the *entire* template below.
+-->
+
+**Expected behavior:**
+
+**Actual behavior:**
+
+**Related Issues:** <!-- Did you find other bugs that looked similar? -->
+
+**Versions:**
+
+- NodeJS:
+- NPM:
+- MongoDB:
+- Redis:
+- Browser:
+- OS:

.github/ISSUE_TEMPLATE/FEATURE.md

@@ -0,0 +1,27 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+labels: "feature idea"
+---
+
+<!--
+
+Please help us by doing the following steps before logging an issue:
+  * Search: https://github.com/coralproject/talk/search
+
+-->
+
+## Search Terms
+
+<!-- List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily -->
+
+## Suggestion
+
+<!-- A summary of what you'd like to see added or changed -->
+
+## Use Cases
+
+<!--
+What do you want to use this for?
+What shortcomings exist with current approaches?
+-->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,10 @@
+<!--
+Thank you for submitting a pull request!
+
+Please verify that:
+* [ ] Code is up-to-date with the base branch
+* [ ] You've successfully run `npm run test` locally
+
+Refer to CONTRIBUTING.MD for more details.
+  https://github.com/coralproject/talk/blob/master/CONTRIBUTING.md
+-->

CODE_OF_CONDUCT.md

@@ -0,0 +1,7 @@
+# Vox Media Code of Conduct
+
+## Introduction
+
+This code of conduct governs the environment of the Vox Product team. We created it not because we anticipate bad behavior, but because we believe that articulating our values and obligations to one another reinforces the already exceptional level of respect among the team and because having a code provides us with clear avenues to correct our culture should it ever stray from that course. We make this code public in the hopes of contributing to the ongoing conversation about inclusion in the tech, design, and media communities and encourage other teams to fork it and make it their own. To our team, we commit to enforce and evolve this code as our team grows.
+
+Read the rest here: http://code-of-conduct.voxmedia.com/

CONTRIBUTING.md

@@ -0,0 +1,66 @@
+# Contributor's Guide
+
+Welcome! We are very excited that you are interested in contributing to Coral.
+
+This document is a companion to help you approach contributing. If it does not
+do so, please [let us know how we can improve it](https://github.com/coralproject/talk/issues)!
+
+By contributing to this project you agree to the
+[Code of Conduct](CODE_OF_CONDUCT.md).
+
+## What should I Contribute?
+
+There are at least three ways to contribute to Coral:
+
+- Writing Code
+- Providing Translations
+
+## Writing Code
+
+Conversation surrounding contributions begins in
+[issues](https://github.com/coralproject/talk/issues).
+
+### When should I create an issue?
+
+File an issue as soon as you have an idea of something you'd like to contribute.
+We would love to hear what you're thinking and help refine the idea to make it
+into the Coral ecosystem.
+
+Please file issues if you would like to contribute to Coral.
+
+### What should I include?
+
+Coral has adopted an iterative, agile development philosophy. All contributions
+that make it into the Coral repository should start with a user story in this
+form:
+
+> As a [type of Coral user] I'd like to [do something] so that I can [get some result/value].
+
+This exercise does two things:
+
+- allows us to ground our technical choices in a clear, simple product need.
+- expresses that product need in a way that doesn't imply a specific technical
+  solution allowing for debate as to the best way to solve the problem.
+
+Please feel free to provide as much detail as possible when filing the issue but
+please do keep the initial issue specific to one need and try to avoid including
+technical or design solutions.
+
+If you have a specific technical or design solution in mind, please submit it as
+the first comment on the thread.
+
+## Localization
+
+We use the [fluent](http://projectfluent.org/) library and store our
+translations in [FTL](http://projectfluent.org/fluent/guide/) files in
+`src/locales/` and `src/core/server/locales/`.
+
+Strings are added or removed from localization bundles in the translation files
+as needed. Strings **MUST NOT** be _changed_ after they've been committed and
+pushed to master. Changing a string requires creating a new ID with a new name
+(preferably descriptive instead of incremented) and deletion of the obsolete ID.
+It's often useful to add a comment above the string with info about how and
+where the string is used.
+
+Once a language has enough coverage, it should be added to
+`src/core/common/helpers/i18n/locales.ts`.