introducing Jasmine

I was worried that I would have to jump through some arcane hoops
(like forking pivotal/jasmine-py on GitHub, editing it, and telling Pip
to use that repo) after Jasmine 2.0.0 failed to install because one of
the dependencies of its dependencies tried to call os.getcwdu (a
Python-2-ism). But 2.0.1 (released twelve days ago) worked.

[finishes #7]
JavaScript test coverage for tagging
introducing Underscore for the sake of its pretty templating engine
cancel-comment button
towards voting feedback

The JavaScript library directory is called libs/ instead of lib/
because of my personal beliefs about how .gitignore works and how I
had wanted to put the borrowed snippet that changes the Underscore
templating delimiters in its own file there in order to avoid
duplication, because Jasmine needs to know about it, too, not just
base.html. But then I actually couldn't figure out how to get Jasmine
to recognize it (you'd think (apparently having an episodic memory of)
putting it in the src_files list in jasmine.yml would be enough!?), so
it's at the top of finetooth.js for now.
voting feedback

It's really ugly (as is much of the site), but the core functionality
seems to work. Thanks to http://stackoverflow.com/a/7317489 for
telling me that CSS transitions are a thing.
merge branch 'a_dazzling_place_I_never_knew'

Conflicts:
	README.md
don't use the initial_data fixture name; correct libs/ path in README

Django has historically treated fixtures with the name initial_data
specially (loading them as, well, initial data), but apparently that's
changing with 1.7, and I don't really have time to understand the
details right now, but I think we want to use another name for the
fixture because it just blew up on me
("django.db.utils.OperationalError: Problem installing fixture
'/home/zmd/Code/Finetooth/core/fixtures/initial_data.json': Could not
load contenttypes.ContentType(pk=1): no such table:
django_content_type" while performing sanity checks after creating the
merge commit 4dd57ee5b in a dev environment that had fallen behind
master).

I've verified that this version behaves sanely through an
initial syncdb and loading the sample_data.json fixture.

Also, the wget command in the README should match the Jasmine configs
to reduce confusion and despair.