Update copyright statements.
Change Create Article to tornado.

Also as part of this transition I'm starting to add in kombu as a
message queue plugin structure.  When we finally get mongodb behind
dbapi or similar we should be at a pluggable architecture without much
code required.
Re-add pika until it's gone.
Add RuntimeError to exceptions when vagrant is missing.
Move runtime catch to invocation of vagrant.
Add create article API call.

This only partially satisfies issue #58 but also begins work necessary
for issues #72 and #75 as well.

Using kombu makes the message queue portion of margarine pluggable
without adding any complexity.  It also allows pickling as a
serialization mechanism amongst others.

This only completes the top-half of issue #58 though.  It only
implements the necessary changes for tests to pass and blend having
support for creation of an article (popping relevant information into a
message queue).

Next steps will be adding corresponding updates to spread with unit
tests for that functionality and then adding integration tests for blend
and spread with an unmocked queue service (vagrant up queue).
Add worker framework for spread using kombu.

Lots of changes in this that are largely aesthetic.  The major changes
include adding a kombu framework for spread and the first task handler.

The unit tests for this first task has also been added.  This required a
bit of refactoring the test suite.

Work left to do, includes adding system tests that show an article can
be added and read through the API.
Add sanitize worker.

The addition of this work brought about many changes to the fixtures
being stored (not sure we have them right yet but it's closer).  The
addition of the tests increased the need for sharing of mocks and
generalization of some of that code as well as showed wht is required
for generating consistent etags.

Next steps should be integration and system tests for create and read of
an article through the API.
Add spread create article datastore integration test.

More refactoring of the test suite due to shared mechanisms.  It's going
to get hairier when we do the integration tests including queues.
Multiple inheritance for the win!  This test verifies that the spread
tasks (just create this round) properly integrates with the datastore
portion.
Add submitted spread create article test.

Added the final test for spread's article create task.  Also added a
little logic to simplify the isolation of tests that use the datastore
by purging it before each test.
Add spread sanitize test.

This test showed that more items needed to be factored out and that the
datetime mock needed a bit of finagling to properly pass through
unmocked items.
Add test of unparsed sanitize.

I'm not convinced that this test indeed tests what it needs to but I'm
committing it for now.  We should probably add bson stages to the
fixture.  That would the best solution.  Expected values then could be
communicated more easily.
Stagify or break into components the article fixture.

Only the unit tests have been updated with this transition to the staged
or componentized fixture.  Next up is fixing the integration tests while
moving them to functional tests.
Update integration tests for staged fixtures.
Add runtime fixes.

Minor issues cropped up when attempting to run the new blend and spread
code.  These have been fixed and the vagrant environment does function
correctly.  Once the proper tests have been added we can consider this a
1.0.0 release of margarine.