First release with:

• The use of a testing infrastructure.
• With a Continuous Integration service.
• With some code coverage analysis (tied to tests).

This is meant to be a more solid and robust ground for our future refactorings towards a 1.0 release.

This first "stable enough" version should be our first version (say, v0.0) of the script to be uploaded to pypi.

We should focus on:

• getting some of the most pressing fixes
• getting the packaging done
• tagging the release
• upload to pypi

Then, after this is done, we can get wild and add more features and refactor stuff. This way, users will have at least a base version to refer to (and to fall back to) if they don't like our (certainly disruptive) changes.

Add some small features:

• Support George Washington University (issue #186).
• Minor organization of the code (splitting it into different files; e.g., moving constants to a constants module). No heavy refactorings.
• Add copious amounts of use of the logging module to aid with debugging when users hit problems with the program.

More stuff to add?

Introduce new features:

• Parallel processing of downloads.
• Downloads of subtitles in multiple languages.
• More???

Edit this as we see fit.