Event sessions now use a date picker for their y/m/d component.

Event forms now start with one session.
Event sessions now have names.

Changed the appearance of footer links on all pages: Now they're bootstrappy gradient btn things.

Messed around with the style for the event's show page.
Detect native datepicker and use it instead of jqui when available

Session date is shown in the form in ISO format (yy-mm-dd) for
  browsers without a datepicker. Datepicker browsers probably
  choose whatever's in your locale or what ever.
Updated profile to include Outreach and removed Hacker, Coordinator, and Evangelize
Organizers do not see a 'Volunteer' link for their own events

Rsvp is now a nested resource of Event
Merge branch 'profile' of https://github.com/jforbe/bridge_troll into jforbe-profile
Session name shows up when RSVPing for sessions
Session dates show day of the week

https://www.pivotaltracker.com/story/show/43285565https://www.pivotaltracker.com/story/show/43285565
adding rsvp associations to event_session

this should be mostly a noon commit
allow some html in event details

we allow default sanitize tags.  so no script tags.
Organizers can assign volunteer roles
Organizer can check volunteers in to event sessions
Reorder profile skills so 'outreach' is not lumped in with the OSes
Adding rake tasks to import data from meetup
Sanitize event description from meetup API to deal with bad UTF-8 in event 62909402
Import locations from meetup venue data

Locations now have address_1, address_2, city, state, and zip
(instead of just 'address')
removing deprecated iconv
Fix crash on event show page when rendering location
fixed bug where details can include unclosed html tags
Import volunteer/organizer RSVPs from Meetup.

New routes for looking at imported meetup data: /meetup_users and /meetup_users/:id

Meetup Users live in their own table: MeetupUser. Only their full name + meetup ID is stored.
In the future we could potentially store their profile photos from meetup.

rsvps now has a polymorphic association back to 'user', so an Rsvp could potentially be
for a regular (bridgetroll) User, or a MeetupUser. MeetupUser is configured to act like a user
who answered 'false' to all profile questions.

Because you can't use has_many :through polymorphically, the 'volunteers' and 'organizers'
associations on event still just return bridgetroll users. The 'legacy_volunteers' and
'legacy_organizers' associations will return MeetupUser records, and the methods
'volunteers_with_legacy' and 'organizers_with_legacy' add the two associations together.

The added complexity here is to support users adopting their MeetupUser RSVPs when
they sign up for Bridgetroll. We'll see if this technology holds up.

jquery datatables plugin is included for the benefit of sorting /meetup_users page.