Added points to setup
Implemented TaskType (Issue #3) and ExpenseType (Issue #4)
Implemented Task (Issue #2)
Rewriting task_model.feature and step definitions, for instructive purposes
Added 2 new scenarios to consider for task_model.feature

These 2 scenarios were not explicitly dealt with in the original project spec, but they are worth considering:

1. When a TaskType is deleted, what should we expect to happen to all the Tasks that use that TaskType?
2. When a User is deleted, what should we expect to happen to all of that user's Tasks?
Issue #2: Fixing up FactoryGirl

* Added created task to created user (i.e. reloads DB to memory model)
* No changes for the task.rb model
Added Cucumber transforms to handle NUMBER, TASK, and USER

Replaced features/step_definitions/tasks.rb with my version, which also uses Cucumber Transforms (defined in features/support/transform.rb).  Modified the app/models/tasks.rb file accordingly to get tests to pass.
Merge with WIP-alvin
Issue #2 Reordering commits to push password feature to top.

* I implmeneted my own password feature in my branch.
* I'm trying to push it to the top so that others can pull the
  canonical features for themselves when I merge into master.
Issue #1 Optional feature: password requirement for user

Finished adding password capability to User model.

* Passwords must be between 6 and 256 (inclusive) in length.
* Passwords have to include one non-alphabetic character.
* FactoryGirl modified appropriately.
* DB migrated appropriately.
* Cucumber tests added. Missing test is testing/implementing that the password must equal the password confirmation but this is automatically implemented by Rails.