Requirements and deliverables for patch submission

Checklist before submitting for review

 * 1) Tests: Check that 100% of the code you modified is covered by unit tests, with no errors or warnings, for both JS and Python code.
 * 2) jslint: run jslint static/js/jquery.cardstories.js and fix all warnings
 * 3) Comments: check that the code you modified or added is properly documented, in a way that makes it easier for a new developer to understand the logic and will facilitate maintenance.
 * 4) Browsers: Test the patch with the following browsers to ensure it works: Firefox 3.6, 4.0, 5.0; Chromium (latest stable); IE 8.0, 9.0; Safari (latest stable).
 * 5) Copyrights: Did you write all the code contained in the patch? (if not, make sure you add the proper credits to the LICENSE.txt file)
 * 6) Commit: Make sure the patch is an isolated commit (one per ticket) with a thorough commit message, containing "closes #14" (replacing 14 with the ticket number)
 * 7) Repository: Publish your commits on a public git repository (for example gitorious)
 * 8) Ticket update: Post the URL to the repository on the ticket
 * 9) Patch maintenance: Until the patch is merged, keep up to date with the repositories of the other developers (see below)

Installing jslint
jslint is in the jscoverage source package but it is not available in the .deb, so you'll need to compile it from source: