Start using strong_parameters

Replaces attr_accessible. Started using it on BigbluebuttonRoom and its
controller only, the other models are still with the old method.
Had to update rspec to 2.14 to test it properly. This is triggering several
deprecation messages for methods that should be updated.
Fix deprecated methods on rspec 2.14
Update shoulda-matchers to 2.2.0 and update specs

More information about the matchers that were replaced at:
http://robots.thoughtbot.com/post/47031676783/shoulda-matchers-2-0
Finish migrating to strong_parameters in all models

Several attr_accessible's used before are not necessary anymore. They were
there to allow the application to call update_attributes at some methods
and actions that are not triggered by the user.
Prevent actions from breaking if parameters are not informed

The actions 'update' and 'create' in all controllers shouldn't break if the
parameters informed don't have the key they expect it to have.
Specially now with 'strong_parameters' that all controllers have a method to
filter the attributes allowed to be in the hash.
Add therubyracer to the bundle

Necessary when running commands with 'bundle install'.
Merge branch 'master' into strong_parameters

Conflicts:
	Gemfile.lock
	README.rdoc
	app/models/bigbluebutton_recording.rb
	spec/controllers/bigbluebutton/recordings_controller_json_responses_spec.rb
	spec/controllers/bigbluebutton/servers_controller_json_responses_spec.rb
	spec/models/bigbluebutton_recording_spec.rb
Default use of params[:redir_url] whenever possible

Added it to actions that didn't support it yet and refactored the ones that
already had it. Now most of the methods support this option.
Setting `cache_classes`to false so classes are reloaded by spork

As it was before, changes in the files in the gem were not detected and
required spork to be restarted.
Add basic model and migration for meetings, refs #1032

Added the model, migrations, and methods on BigbluebuttonRoom to update the
associated meeting when the room is updated.
Update meetings on create, join, end and periodically, refs #1032

Using resque to schedule a job that will update the meetings. The job is
schedule always when one of these calls is made upon a room: create, join
and end.
There's also a rake task that is triggered periodically by cron to check for
meetings that were running and are not anymore.
Add resque as a dependency
Update meetings when getMeetingInfo is called

A kind of shortcut to update the meetings faster in case getMeetingInfo is called,
otherwise the meetings will only be updated when someone joins, when end is
called or in the synchronization cycles (~10min)
Associate meetings with recordings

When a recording is created it tries to find the BigbluebuttonMeeting instance
that created the recording and associates it with the recording.

refs #1032
Use MysQL as default in development and testing

Discovered a few issues when querying for datetime attributes in sqlite3.
Switched to MySQL because of it and because it is the database already being
used in Mconf-Web, hence the database recommended for BigbluebuttonRails.

refs #1032
Add a few missing strings to the locale

They are used in Bigbluebutton::RoomsController#external_auth.
Update README with info about dependencies

resque, strong_parameters and whenever.
Created a way to let users change the layout of the rooms.

To do this, a new model was created to receive the options from the room. In this model a user can set the default layout who he wanted. A new function was created in this model to return all the layouts allowed in the server, for now this function just return a list of fixed layouts.

Refs #962
Update rooms_controller.rb

Adding a restriction for allowed parameters on rooms. Now the parameter default_layouts can be modified.

Refs #962
Initial changes to use dynamic config.xml to join meetings with a specific configuration

Created a new function in bigbluebutton_room model to generate a new token with all configurations changed by the user.

Refs #962