..

backend/node_modules/googleapis/.github/CLOSE_ISSUE_TEMPLATE.md

@@ -0,0 +1,14 @@
+Closing as this does not appear to be an issue. If you are convinced that this is really a bug, please feel free to re-open the issue and add more information such as:
+
+* Expected behavior
+* Actual behavior
+* Code samples
+* Version numbers
+* References docs or other links
+
+Or, consider opening a Pull Request.
+
+__Otherwise, support questions are handled on [Stack Overflow][stackoverflow].__ [![Ask a question on Stackoverflow][overflowimg]][stackoverflow]
+
+[overflowimg]: https://googledrive.com/host/0ByfSjdPVs9MZbkhjeUhMYzRTeEE/stackoveflow-tag.png
+[stackoverflow]: http://stackoverflow.com/questions/tagged/google-api-nodejs-client

backend/node_modules/googleapis/.github/CONTRIBUTING.md

@@ -0,0 +1,85 @@
+# Contributing
+
+Before making any contributions, please sign one of the contributor
+license agreements below.
+
+Fork the repo, develop and test your code changes.
+
+Install all dependencies including development requirements by running:
+
+``` sh
+$ npm install -d
+```
+
+Tests are run using mocha. To run all tests just run:
+
+``` sh
+$ npm test
+```
+
+which looks for tests in the `test/` directory.
+
+Your code should honor the [Google JavaScript Style Guide][js-guide].
+You can use [Closure Linter][c-linter] to detect style issues.
+
+Submit a pull request. The repo owner will review your request. If it is
+approved, the change will be merged. If it needs additional work, the repo
+owner will respond with useful comments.
+
+## Generating APIs
+
+If you're a developer interested in contributing to this library, the following
+section will be useful for you. Each of the files in `apis/` is generated from
+the discovery docs available online. You can generate these files by running
+the following command:
+
+``` sh
+npm run generate-apis
+```
+
+You can pass in custom Discovery URLs or paths to discovery docs:
+
+``` sh
+node scripts/generate http://discoveryurl.example.com /path/to/discoverydoc.json
+```
+
+## Generating Documentation
+
+You can generate the documentation for the APIs by running:
+
+``` sh
+npm run generate-docs
+```
+
+Documentation will be generated in `docs/`.
+
+## Preparing for release
+
+Before releasing a new version, you should generate all APIs, run tests,
+bump the version in `package.json` and create a git tag for the release. You
+can automate all this with a patch version bump (version += 0.0.1) by running:
+
+``` sh
+npm run prepare
+```
+
+## Contributor License Agreements
+
+Before creating a pull request, please fill out either the individual or
+corporate Contributor License Agreement.
+
+* If you are an individual writing original source code and you're sure you
+own the intellectual property, then you'll need to sign an
+[individual CLA][indv-cla].
+* If you work for a company that wants to allow you to contribute your work
+to this client library, then you'll need to sign a
+[corporate CLA][corp-cla].
+
+Follow either of the two links above to access the appropriate CLA and
+instructions for how to sign and return it. Once we receive it, we'll add you
+to the official list of contributors and be able to accept your patches.
+
+[js-guide]: https://google.github.io/styleguide/jsguide.html
+[c-linter]: https://code.google.com/p/closure-linter/
+[indv-cla]: https://developers.google.com/open-source/cla/individual
+[corp-cla]: https://developers.google.com/open-source/cla/corporate

backend/node_modules/googleapis/.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,9 @@
+**** DELETE THIS BLOCK ****
+
+Thanks for filing an issue!  Please keep keep issues limited to bug reports, feature requests, and other general issues. For support questions, please feel free to reach out on stack overflow: http://stackoverflow.com/questions/tagged/google-api-nodejs-client
+
+**** /DELETE THIS BLOCK ****
+
+<your detailed question and code samples go here>
+
+Thanks!

backend/node_modules/googleapis/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,8 @@
+Fixes #<issue_number_goes_here> (it's a good idea to open an issue first for discussion)
+
+- [ ] `npm test` succeeds
+- [ ] Pull request has been squashed into 1 commit
+- [ ] I did NOT manually make changes to anything in `apis/`
+- [ ] Code coverage does not decrease (if any source code was changed)
+- [ ] Appropriate JSDoc comments were updated in source code (if applicable)
+- [ ] Approprate changes to readme/docs are included in PR