+ to the open source project. Wonderful!</p>
+
+ <p>This is a step-by-step guide explaining how to do it.</p>
+
+ <h3>dygraphs style</h3>
+ <p>First of all, please try to follow the style of the existing dygraphs
+ code. This will make the review process go much more smoothly.<p>
+
+ <p>A few salient points:</p>
+ <ol>
+ <li> I try to adhere to Google's <a
+ href="http://google-styleguide.googlecode.com/svn/trunk/javascriptguide.xml">
+ JS style guide</a> and would appreciate it if you try to as well. This
+ means:
+ <ul>
+ <li>No tabs! Indent using two spaces.
+ <li>Use camelCase for variable and function names.
+ <li>Limit lines to 80 characters.
+ </ul>
+
+ <li>Please run 'lint.sh' to see if you've introduced any new violations.
+
+ <li>If you've added a new feature, add a test for it (in the tests/
+ directory) or a gallery entry.
+
+ <li>If you've added an option, document it in
+ dygraph-options-reference.js. You'll get lots of warnings if you don't.
+
+ <li>If you've fixed a bug or added a feature, add an auto_test for
+ it.<br/>
+ This ensures that we won't inadvertently break your feature in the
+ future. To do this, either add to an existing auto_test in
+ auto_tests/tests or run "auto_tests/misc/new-test.sh your-test-name" to
+ create a new one. You can run your auto_test in any browser by visiting
+ auto_tests/misc/local.html.
+ </ol>
+
+ <h3>Sending a Pull Request</h3>
+
+ <p>dygraphs is hosted on github, which uses a "pull request" model. They
+ have a good writeup <a
+ href="http://help.github.com/send-pull-requests/">here</a>. These
+ instructions discuss dygraphs more specifically.</p>