Bump version to 0.0.6 (sprint6)
Simplify task model

Only include projectId, title, and description as main
fields for tasks.  The rest can likely be done with tags.
Migrate popovers to requirejs module

Instead of popovers just being functions in a js
file, make them a formal AMD module.  The reason
for this is that popovers require bootstrap to
be loaded before they can execute.  Hopefully this
will solve some of the weirdities I've been seeing.
Add SSL nginx config

Make it easier to put up sites with nginx using SSL
by including a default nginx template that can be
modified.  Or put your keys in `/etc/nginx/ssl/` and
everything will just work.
Eliminating the notion of volunteers

For now, just let people participate by starting a new
topic in the comments.  So there is no notion of
apply or having a specific volunteer.  May add it
back in later as requirements dictate, but not
necessary for now.
Create utils; update comments to support tasks

Created a new directory called `utils` in services in
preparation for tasks.  Include project.js and task.js
that provide the `authorized` function for checking whether
a given userId is authorized to view a particular project
or task.

Updated CommentController by refactoring the comment query
and processing code into a helper function which can be called
by both findAllByProjectId and findAllByTaskId.
Add a policy for task authorization

Tasks need a way to check if a given userId is authorized
to access that task.  Prevents unauthorized access to
endpoints.
Policy updates to control access

Be more comprehensive about what can and cannot be done.

There's a lot more to be done to prevent malicious access,
but this covers a lot more cases.

Need to be able to:
- check that you own an event before updating or deleting
- check that you own a comment before updating or deleting
- ... I'm sure there's a lot more.
Implement tag functions for tasks

Add `findAllByTaskId` in the TagController. Factor out
the tag lookup code so that it can be used by either
project or task tag lookups.  Update destroy to check
permissions for either project or task depending on which
is specified.
More policy work for tasks

Add `taskId` to check if taskId is specified in the body,
then make sure that you have ownership.

Additional changes to create/update/destroy
More policies to prevent malicious data access
Fix typo; fix policies for likes

Unbreak the build (whoops) by fixing a typo
in TagController and updating the create policy for
likes.
Checking in work from today.

- I implemented a change of how event form renders, and instead of using
  a class that inserts into the dom chose to use a class data-attribute.
  My opinion is that since we are aiming for IE at a certain point we
  can use classes to implement these DOM flags, as data-attributes are
  not compatible with certain versions of IE.
Forgot to checkin Tasks from Today.

- Here are the basics for the idea of a madlib in the task creation
  area.  I put them all on seperate lines with 100% width so that we can
  make sure this is how Azmir pictured it going.  Not sure if I was
  reading the document properly.
- I also updated the project structure to contain a base show view and
  show_controller as well as show_template.
Pulled in commits from local task branch.

A local branch I had got ahead of sprint6 on origin, so just pulling in
all my local commits to sprint6 instead of creating a seperate branch on
origin - no need really.
Pulling in update from out of sync hotfix branch.

- Pulling in another update from an out of sync branch that fixes a bug
  from the other day.  This fix is for issue #10.
Refactored toggleRSVP Method.

- I removed the concept of a featured_event from the iteration cycle,
  and instead rendered it using the iterator context itself.  So the
  first event always becomes the featured event as it is the 'next
  event' relative to date/time.
- Minor cleanup in the DOM to reflect prev change.
Pass params to souces when querying

By passing the HTTP parameters to the data source when
querying it, the source can use those extra optional
parameters.  This allows more dynamic querying, like:

http://localhost/ac/tag?q=foo&type=bar

Update the model source to require explicitly defined
parameters, and then check if any of those parameters
are present in the query.

NOTE: This commit requires that you reset your
sources.ex.js.  Just do
cp config/settings/sources.ex.js config/settings/sources.js
Added new rendering method to comments.

- I added an $el based rendering method for comments, so comment's on
  topics are scoped to the $el of the list under that individual topic.
  This way there are no collisions in the data-flow, and thus it is
  easier to implement the next step: forms for comments and re-rendering
  with no bugs.
Adding in the form to the proper Topic.

1) Iterate through topics.
2) Iterate through comments.
3) Place form at the very bottom of all comments.