initial

.gitignore

@@ -0,0 +1,6 @@
+node_modules/
+bower_components/
+*.log
+
+build/
+dist/

_.editorconfig

@@ -0,0 +1,21 @@
+# EditorConfig helps developers define and maintain consistent
+# coding styles between different editors and IDEs
+# editorconfig.org
+
+root = true
+
+
+[*]
+
+# Change these settings to your own preference
+indent_style = space
+indent_size = 2
+
+# We recommend you to keep these unchanged
+end_of_line = lf
+charset = utf-8
+trim_trailing_whitespace = true
+insert_final_newline = true
+
+[*.md]
+trim_trailing_whitespace = false

_.gitattributes

@@ -0,0 +1 @@
+* text=auto

_.gitignore

@@ -0,0 +1,29 @@
+### node etc ###
+
+# Logs
+logs
+*.log
+
+# Runtime data
+pids
+*.pid
+*.seed
+
+# Directory for instrumented libs generated by jscoverage/JSCover
+lib-cov
+
+# Coverage directory used by tools like istanbul
+coverage
+
+# Grunt intermediate storage (http://gruntjs.com/creating-plugins#storing-task-files)
+.grunt
+
+# Compiled Dirs (http://nodejs.org/api/addons.html)
+build/
+dist/
+
+# Dependency directorys
+# Deployed apps should consider commenting these lines out:
+# see https://npmjs.org/doc/faq.html#Should-I-check-my-node_modules-folder-into-git
+node_modules/
+bower_components/

_.jshintrc

@@ -0,0 +1,21 @@
+{
+    "node": true,
+    "esnext": true,
+    "bitwise": true,
+    "camelcase": true,
+    "curly": true,
+    "eqeqeq": true,
+    "immed": true,
+    "indent": 2,
+    "latedef": true,
+    "newcap": true,
+    "noarg": true,
+    "quotmark": "single",
+    "regexp": true,
+    "undef": true,
+    "unused": true,
+    "strict": true,
+    "trailing": true,
+    "smarttabs": true,
+    "white": true
+}

_.travis.yml

@@ -0,0 +1,4 @@
+language: node_js
+node_js:
+  - '0.8'
+  - '0.10'

_CONTRIBUTING.md

@@ -0,0 +1,175 @@
+# Contributing
+
+## General Workflow
+
+1. Fork the repo
+1. Cut a namespaced feature branch from master
+  - bug/...
+  - feat/...
+  - test/...
+  - doc/...
+  - refactor/...
+1. Make commits to your feature branch. Prefix each commit like so:
+  - (feat) Added a new feature
+  - (fix) Fixed inconsistent tests [Fixes #0]
+  - (refactor) ...
+  - (cleanup) ...
+  - (test) ...
+  - (doc) ...
+1. When you've finished with your fix or feature, Rebase upstream changes into your branch. submit a [pull request][]
+   directly to master. Include a description of your changes.
+1. Your pull request will be reviewed by another maintainer. The point of code
+   reviews is to help keep the codebase clean and of high quality and, equally
+   as important, to help you grow as a programmer. If your code reviewer
+   requests you make a change you don't understand, ask them why.
+1. Fix any issues raised by your code reviwer, and push your fixes as a single
+   new commit.
+1. Once the pull request has been reviewed, it will be merged by another member of the team. Do not merge your own commits.
+
+## Detailed Workflow
+
+### Fork the repo
+
+Use github’s interface to make a fork of the repo, then add that repo as an upstream remote:
+
+```
+git remote add upstream https://github.com/makersquare/<NAME_OF_REPO>.git
+```
+
+### Cut a namespaced feature branch from master
+
+Your branch should follow this naming convention:
+  - bug/...
+  - feat/...
+  - test/...
+  - doc/...
+  - refactor/...
+
+These commands will help you do this:
+
+``` bash
+
+# Creates your branch and brings you there
+git checkout -b `your-branch-name`
+```
+
+### Make commits to your feature branch. 
+
+Prefix each commit like so
+  - (feat) Added a new feature
+  - (fix) Fixed inconsistent tests [Fixes #0]
+  - (refactor) ...
+  - (cleanup) ...
+  - (test) ...
+  - (doc) ...
+
+Make changes and commits on your branch, and make sure that you
+only make changes that are relevant to this branch. If you find
+yourself making unrelated changes, make a new branch for those
+changes.
+
+#### Commit Message Guidelines
+
+- Commit messages should be written in the present tense; e.g. "Fix continuous
+  integration script".
+- The first line of your commit message should be a brief summary of what the
+  commit changes. Aim for about 70 characters max. Remember: This is a summary,
+  not a detailed description of everything that changed.
+- If you want to explain the commit in more depth, following the first line should
+  be a blank line and then a more detailed description of the commit. This can be
+  as detailed as you want, so dig into details here and keep the first line short.
+
+### Rebase upstream changes into your branch
+
+Once you are done making changes, you can begin the process of getting
+your code merged into the main repo. Step 1 is to rebase upstream
+changes to the master branch into yours by running this command
+from your branch:
+
+```bash
+git pull --rebase upstream master
+```
+
+This will start the rebase process. You must commit all of your changes
+before doing this. If there are no conflicts, this should just roll all
+of your changes back on top of the changes from upstream, leading to a
+nice, clean, linear commit history.
+
+If there are conflicting changes, git will start yelling at you part way
+through the rebasing process. Git will pause rebasing to allow you to sort
+out the conflicts. You do this the same way you solve merge conflicts,
+by checking all of the files git says have been changed in both histories
+and picking the versions you want. Be aware that these changes will show
+up in your pull request, so try and incorporate upstream changes as much
+as possible.
+
+You pick a file by `git add`ing it - you do not make commits during a
+rebase.
+
+Once you are done fixing conflicts for a specific commit, run:
+
+```bash
+git rebase --continue
+```
+
+This will continue the rebasing process. Once you are done fixing all
+conflicts you should run the existing tests to make sure you didn’t break
+anything, then run your new tests (there are new tests, right?) and
+make sure they work also.
+
+If rebasing broke anything, fix it, then repeat the above process until
+you get here again and nothing is broken and all the tests pass.
+
+### Make a pull request
+
+Make a clear pull request from your fork and branch to the upstream master
+branch, detailing exactly what changes you made and what feature this
+should add. The clearer your pull request is the faster you can get
+your changes incorporated into this repo.
+
+At least one other person MUST give your changes a code review, and once
+they are satisfied they will merge your changes into upstream. Alternatively,
+they may have some requested changes. You should make more commits to your
+branch to fix these, then follow this process again from rebasing onwards.
+
+Once you get back here, make a comment requesting further review and
+someone will look at your code again. If they like it, it will get merged,
+else, just repeat again.
+
+Thanks for contributing!
+
+### Guidelines
+
+1. Uphold the current code standard:
+    - Keep your code [DRY][].
+    - Apply the [boy scout rule][].
+    - Follow [STYLE-GUIDE.md](STYLE-GUIDE.md)
+1. Run the [tests][] before submitting a pull request.
+1. Tests are very, very important. Submit tests if your pull request contains
+   new, testable behavior.
+1. Your pull request is comprised of a single ([squashed][]) commit.
+
+## Checklist:
+
+This is just to help you organize your process
+
+- [ ] Did I cut my work branch off of master (don't cut new branches from existing feature brances)?
+- [ ] Did I follow the correct naming convention for my branch?
+- [ ] Is my branch focused on a single main change?
+ - [ ] Do all of my changes directly relate to this change?
+- [ ] Did I rebase the upstream master branch after I finished all my
+  work?
+- [ ] Did I write a clear pull request message detailing what changes I made?
+- [ ] Did I get a code review?
+ - [ ] Did I make any requested changes from that code review?
+
+If you follow all of these guidelines and make good changes, you should have
+no problem getting your changes merged in.
+
+<!-- Links -->
+[pull request]: https://help.github.com/articles/using-pull-requests/
+[DRY]: http://en.wikipedia.org/wiki/Don%27t_repeat_yourself
+[boy scout rule]: http://programmer.97things.oreilly.com/wiki/index.php/The_Boy_Scout_Rule
+[squashed]: http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html
+<!-- A link to your directory of tests on github -->
+[tests]: tests/

_PRESS-RELEASE.md

@@ -0,0 +1,44 @@
+# Project Name #
+
+<!-- 
+> This material was originally posted [here](http://www.quora.com/What-is-Amazons-approach-to-product-development-and-product-management). It is reproduced here for posterities sake.
+
+There is an approach called "working backwards" that is widely used at Amazon. They work backwards from the customer, rather than starting with an idea for a product and trying to bolt customers onto it. While working backwards can be applied to any specific product decision, using this approach is especially important when developing new products or features.
+
+For new initiatives a product manager typically starts by writing an internal press release announcing the finished product. The target audience for the press release is the new/updated product's customers, which can be retail customers or internal users of a tool or technology. Internal press releases are centered around the customer problem, how current solutions (internal or external) fail, and how the new product will blow away existing solutions.
+
+If the benefits listed don't sound very interesting or exciting to customers, then perhaps they're not (and shouldn't be built). Instead, the product manager should keep iterating on the press release until they've come up with benefits that actually sound like benefits. Iterating on a press release is a lot less expensive than iterating on the product itself (and quicker!).
+
+If the press release is more than a page and a half, it is probably too long. Keep it simple. 3-4 sentences for most paragraphs. Cut out the fat. Don't make it into a spec. You can accompany the press release with a FAQ that answers all of the other business or execution questions so the press release can stay focused on what the customer gets. My rule of thumb is that if the press release is hard to write, then the product is probably going to suck. Keep working at it until the outline for each paragraph flows. 
+
+Oh, and I also like to write press-releases in what I call "Oprah-speak" for mainstream consumer products. Imagine you're sitting on Oprah's couch and have just explained the product to her, and then you listen as she explains it to her audience. That's "Oprah-speak", not "Geek-speak".
+
+Once the project moves into development, the press release can be used as a touchstone; a guiding light. The product team can ask themselves, "Are we building what is in the press release?" If they find they're spending time building things that aren't in the press release (overbuilding), they need to ask themselves why. This keeps product development focused on achieving the customer benefits and not building extraneous stuff that takes longer to build, takes resources to maintain, and doesn't provide real customer benefit (at least not enough to warrant inclusion in the press release).
+ -->
+
+## Heading ##
+  > Name the product in a way the reader (i.e. your target customers) will understand.
+
+## Sub-Heading ##
+  > Describe who the market for the product is and what benefit they get. One sentence only underneath the title.
+
+## Summary ##
+  > Give a summary of the product and the benefit. Assume the reader will not read anything else so make this paragraph good.
+
+## Problem ##
+  > Describe the problem your product solves.
+
+## Solution ##
+  > Describe how your product elegantly solves the problem.
+
+## Quote from You ##
+  > A quote from a spokesperson in your company.
+
+## How to Get Started ##
+  > Describe how easy it is to get started.
+
+## Customer Quote ##
+  > Provide a quote from a hypothetical customer that describes how they experienced the benefit.
+
+## Closing and Call to Action ##
+  > Wrap it up and give pointers where the reader should go next.