It's a relic from a time before the class subclassed a Backbone.Collection

Conflicts:
	converse.js

When using show_only_online_users, roster item DOM elements are removed from
the DOM if their status changed from 'online' to something else.

When their status changed to 'online' again, they were re-added.

Their views (RosterItemView) instances however didn't listen to events anymore.

Calling delegateEvents on the view after calling $.remove() fixed this.

Instead we build manually. Fixed paths in build.js

Conflicts:
	Gruntfile.js

If true, only users with a status of 'online' will be shown in the contacts
roster.

Move all module-level functions/variables and Backbone Modules/Views together.
Add headings to indicate logical sections.
Make statuses variable module-level and indicate that it's a constant (all caps)

This method shouldn't be called when contact requests aren't allowed because
roster items are then not created for contact requests.

- Register handlers that depend on the roster inside initRoster and the
  message handler inside chatboxes.onConnected. This solves problem of presence
  stanzas being received before handlers are initialized. Updates #65

- Check if MUC is allowed during feature discovery

Conflicts:
	tests_main.js

Conflicts:
	locale/locales.js

Conflicts:
	index.html

Add Russian translation by bkocherov (actually made against master branch)

This will happen in the background and in the meantime roster contacts will
appear under their JIDs.

Avoiding clash with bootstrap

Using #chatpanel in front of every css class to avoid css name clashing
with bootstrap and other css frameworks