Created a verbose spec for testing Vote#new_votes
Added Vote.new_votes and Vote#find_users_in_tree to allow notifications to be built based off new votes.
Added preferences hstore to the User model, to allow for the storage of notification preferences
Mapped out the first part of the notification builder. NotificationBuilder.organize_daily_email will be the function that is called by the scheduler.

NotificationBuilder.create_notify_list handles interaction with the Vote model, gathering what users need to be informed about which votes.

NotificationBuilder.key_value_crossover is required to correctly switch over the keys (being vote_ids) and the values (being an array of user_ids) to the opposite. As in, keys that are user_ids that have values of an array of vote_ids that the user needs to be informed about.
Merge remote-tracking branch 'upstream/master' into notifier
Added the mandrill-api gem to handle the creation, formatting and sending of emals.
Configuration details to use Mandrill via STMP
organize_daily_email acts as the controller for the rest of the NotificationsBuilder. It's logic is more or less defined as is.

The check_preferences method has been stubbed out. It's purpose is to take the notify list and compare each of the users in it to their notification preferences. If they don't want to recieve emails, those notifications will be stripped out of the notify_list

Added a email_test method, which successfully spams my account.

Added a defaultish email method.
Added premailer-rails gem. Premailer-rails inlines styling for outgoing mails in an efficient manner. It was picked over the Roadie gem because it is already updated to work with Rails 4.

Removed Mandrill gem, as it seems that using Action-mailer and things that tie into that will be a better design choice.
Results of the Rails generate mailer voter_mailer command. Mailer, views and spec created.
Added email_spec to facilitate testing the mailer
So, we have a lot of SMTP configuring going on right now....

It's happening in the initializer and then in part being overwritten in the environment files
Added a spec for notification mailers. Largely pillaged from https://github.com/railsforcharity/spokenvote/pull/269/files
Created the vote_notification action in the VoterMailer

It will pass a User object representing the Recipient and an array of Vote objects representing the votes that the recipient is meant to be notified about.

I've included the attachment as specified in the previous mailer branch
https://github.com/railsforcharity/spokenvote/pull/269/files
Tweaked subject of notification email

Edited method in notification builder
Created basic mailer view folder and vote_notification views

Set up mail interceptor for Dev ENV
Unstyled mail done. All mail_spec tests passing.
This current set up allows me to mail successfully from the DEV environment. We need to clarify how we want this to run in the prod ENV, since there are different things referred to in the ENV variables.

When the init smtp settings were uncommented out, te mailer would break because I don't have all of those ENV variables set in my dev ENV.
Fixed up the VoterMailer action #vote_notification to work with a different datashape for the argument. Moved from expecting a hash to expecting two separate arguments (an integer and an array of integers)

Commented out the attachment since it's not currently being used but left line as reference for later implementation
Trashed the Mandrill API related code, since we are going the Action Mailer route.

Changed the .organize_daily_email method to pass two arguments to the vote_notification and to actually .deliver the mail object returned from the VoterMailer