####Note#####
Presently this flag is only registering the motion creation, thus the before_create.
We could equally use the motion.created_at, but I thought I would leave this logic, which mirrors the discussion, until I get clarification of wether we intend to put other motion activity in the email such as closing a proposal or writing an outcome or even editing the proposal if it ever happens? @robguthrie what do reckon?

The :last_non_vote_activity_at flag is to minimise continual querying of the events table when building the email, which will happen every hour.  As mentioned above we could and probably should remove this if all we want to register as activity in the email is creation and new votes.

There was also some buggy behaviour in the motion model where the created_at was being thrown in with the votes:
```
  def latest_vote_time
    if last_vote_at.present?
      last_vote_at
    else
      # this seems incorrect behaviour
      # and without it this method could be removed
      created_at
    end
  end
```
...which is now no longer needed.