Initial commit

.editorconfig

@@ -0,0 +1,13 @@
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+indent_style = space
+indent_size = 4
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[package.json]
+indent_style = space
+indent_size = 2

.eslintrc.json

@@ -0,0 +1,3 @@
+{
+    "extends": "@vimeo/eslint-config-player/es6"
+}

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,9 @@
+### Expected Behavior
+
+### Actual Behavior
+
+### Steps to Reproduce
+
+<!--
+If you cannot reproduce on the demo page, please link to the page where you’re seeing the issue. It’s helpful for us if you can make a test case using [CodePen](https://codepen.io), [JSFiddle](https://jsfiddle.net), or something similar.
+-->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,9 @@
+<!--
+Please make sure to read our contributing guidelines first. Please try to limit the scope, provide a general description of the changes, and remember, it’s up to you to convince us to merge it.
+
+If this fixes an open issue, link to it in the following way: `Fixes #321`.
+
+New features and bug fixes should come with tests.
+-->
+
+Fixes #.

.gitignore

@@ -0,0 +1,4 @@
+coverage
+node_modules
+.nyc_output
+.DS_Store

.npmrc

@@ -0,0 +1,2 @@
+message = "Update to version %s"
+save-exact = true

.travis.yml

@@ -0,0 +1,14 @@
+sudo: false
+language: node_js
+node_js:
+  - node
+cache:
+  directories:
+    - node_modules
+branches:
+  only:
+    - master
+before_script:
+  - npm prune
+after_success:
+  - npm run report-coverage

CONTRIBUTING.md

@@ -0,0 +1,34 @@
+# Contributing to the Vimeo Player API
+
+The following is a set of guidelines for contributing to the Vimeo Player API, which are hosted in the [Vimeo Organization](https://github.com/vimeo) on GitHub. These are just guidelines, not rules, so use your best judgment and feel free to propose changes to this document in a pull request.
+
+Also, make sure to check out the [Contributing to Open Source on GitHub](https://guides.github.com/activities/contributing-to-open-source/) guide.
+
+## Submitting Issues
+
+You can create an issue [here](https://github.com/vimeo/player.js/issues/new), but before you do, follow these guidelines:
+
+* We fire lots of errors to help you debug, so make sure you use a `try...catch` around the Player constructor, and `.catch()` on all promises.
+* Make sure that you are using the latest version.
+* Make sure to include the browser(s) where you are seeing the issue.
+* Include a link to the page that has the issue. Even better, create a test case using [CodePen](https://codepen.io), [JSFiddle](https://jsfiddle.net), or something similar.
+* Please set up a [profile picture](https://help.github.com/articles/how-do-i-set-up-my-profile-picture) to make yourself recognizable and so we can all get to know each other better.
+
+## Pull Requests
+
+Before you send a pull request, fill out our [Contributor License Agreement](https://developer.vimeo.com/cla).
+
+* Please follow our coding conventions. ESLint will enforce most of them, so make sure that you run it before you commit (with `npm run lint`).
+* If you are fixing a bug, please describe the issue and provide a test case.
+* Don’t forget to add tests!
+
+## Git Commit Messages
+
+See [How to Write a Git Commit Message](http://chris.beams.io/posts/git-commit/) for the full details.
+
+* Use the present tense (“Add feature” not “Added feature”)
+* Use the imperative mood (“Move cursor to...” not “Moves cursor to...”)
+* Limit the subject line to 50 characters or less
+* Capitalize the subject line
+* Use the body to explain what and why vs. how
+* Reference issues and pull requests liberally

LICENSE.md

@@ -0,0 +1,7 @@
+Copyright (c) 2016 [Vimeo](https://vimeo.com)
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.