Update validate_taxon_multiname from master

README.md

@@ -41,3 +41,47 @@ access to the configuration, please ask to have your credentials
 added, or add it yourself in a clone and push the changes. Once you
 let an administrator know, you can be added to the keyring and gain
 decryption privledges.
+
+
+## Building the application
+
+
+### Dependencies
+
+This writeup assumes you have access to a Linux-like environment. If you run Windows, set up [Bash on Ubuntu on Windows (WSL)](https://msdn.microsoft.com/en-us/commandline/wsl/about) for best results.
+
+Your life will also be a lot easier if you have [Homebrew](https://brew.sh/) or [LinuxBrew](http://linuxbrew.sh/) installed.
+
+
+#### Build dependencies
+
+- [Yarn](https://yarnpkg.com/lang/en/docs/cli/) You can install Yarn by running `brew install yarn`
+- [Grunt](http://gruntjs.com/). You can install Grunt from the command line by running `yarn global add grunt-cli`.
+- Recommended: [Coffeescript](http://coffeescript.org) and [Less](http://lesscss.org/). They're included locally but often behave better globally via `yarn global add coffee-script less`
+- Run `yarn install` to install local dependencies.
+
+#### Deploy dependencies
+
+- [Blackbox](https://github.com/StackExchange/blackbox) You can install Blackbox by runing `brew install blackbox`
+
+
+### Deploying
+
+You can update the whole application, with dependencies, by running
+`grunt build` at the root directory.
+
+If you don't need to update dependencies, just run `grunt qbuild`.
+
+#### Installation
+
+##### Configuration Files
+
+If you're part of the project, your PGP public key should already be registered in the application. If you need to make changes, do:
+
+```sh
+blackbox_edit_start PATH/TO/FILE.ext.gpg
+# Edit your file
+blackbox_edit_end PATH/TO/FILE.ext
+```
+
+The two primary configuration files are `CONFIG.php.gpg` and `admin/CONFIG.php.gpg`

less/fa/.github/ISSUE_TEMPLATE/bug-report.md

@@ -0,0 +1,29 @@
+### Describe the problem
+
+<!--- What happened? What are you seeing? How did you arrive here? -->
+
+### What did you expect?
+
+<!--- How would you like this to work instead? -->
+
+### What version and implementation are you using?
+
+Version: <!--- Give us the version number here -->
+Browser and version: <!--- If applicable give us the browser specs -->
+
+- [ ] SVG with JS
+- [ ] Web Fonts with CSS
+- [ ] SVG Sprites
+- [ ] On the Desktop
+
+### Reproducible test case
+
+<!--- Insert a URL to your test case - use codepen.io, jsfiddle.net, jsbin.com, codesandbox.io, or whatever -->
+
+<!--- Describe any details about the test case that we need to know like "whatever you do, don't click the red button" -->
+
+### Bug report checklist
+
+- [ ] I have filled out as much of the above information as I can
+- [ ] I have included a test case because my odds go _way_ up that the team can fix this when I do
+- [ ] I have [searched for existing issues](https://github.com/FortAwesome/Font-Awesome/issues) and to the best of my knowledge this is not a duplicate

less/fa/.github/ISSUE_TEMPLATE/feature-request.md

@@ -0,0 +1,25 @@
+### Describe the problem you'd like to see solved or task you'd like to see made easier
+
+<!--- What steps or tasks are you trying to complete along the way? -->
+
+### Is this in relation to an existing part of Font Awesome or something new?
+
+<!--- If so, what part of Font Awesome? -->
+
+### What is 1 thing that we can do when building this feature that will guarantee that it is awesome?
+
+<!--- e.g. make finding icons while I'm designing super fast  -->
+
+### Why would other Font Awesome users care about this?
+
+<!--- e.g. because everyone wants icons that fly  -->
+
+### On a scale of 1 (sometime in the future) to 10 (absolutely right now), how soon would you recommend we make this feature?
+
+<!--- e.g. 5 - "while we're young" -->
+
+### Feature request checklist
+
+- [ ] This is a single feature (i.e. not a re-write of all of Font Awesome)
+- [ ] The title starts with "Feature request: " and is followed by a clear feature name (Ex: `Feature request: moar cowbell`)
+- [ ] I have [searched for existing issues](https://github.com/FortAwesome/Font-Awesome-Pro/issues) and to the best of my knowledge this is not a duplicate

less/fa/.github/ISSUE_TEMPLATE/icon-request.md

@@ -0,0 +1,15 @@
+### What can it be used for?
+
+<!--- describe how this could be used / the use case for this icon -->
+
+### Example image (optional)
+
+<!--- insert the example image here if necessary -->
+
+### Icon request checklist
+
+- [ ] This is a single icon or matched pair (Ex: `lock` / `unlock`)
+- [ ] The title starts with "Icon request: " and is followed by the requested icon name (Ex: `Icon request: magical-unicorn`)
+- [ ] I have [searched for existing issues](https://github.com/FortAwesome/Font-Awesome/issues) and to the best of my knowledge this is not a duplicate
+- [ ] I have included at least one example image if it could be helpful (optional)
+- [ ] The request is for a concrete object (it's harder to make an icon to represent happiness, it's easier to make a smiley face. ☺)

less/fa/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,6 @@
+<!--- WARNING Pull Requests made to this repository cannot be merged -->
+
+I understand that:
+
+- [ ] I'm submitting this PR for reference only. It shows an example of what I'd like to see changed but
+  I understand that it will not be merged and I will not be listed as a contributor on this project.