500 error was occured in the following steps:

1. user1 creates new team "team1".
2. Assign team1 to project1.
3. Sign in as admin. This admin is not a member of team1.
4. Open project1 team setting page (/project1/team).
5. Click "team1" link in "Assigned teams" area.
6. 500 error.

Fixed this issue.

Conflicts:
	Gemfile.lock
	app/models/ability.rb
	app/models/project.rb
	app/views/snippets/_form.html.haml
	db/schema.rb
	features/steps/shared/paths.rb
	spec/factories.rb
	spec/models/project_spec.rb

user_color_scheme_class with no current_user

fixed commit tab page shows commit log twice

Add api to collect owned user projects. Api deploy_key.create: Enable deploy key if it exist in other owned project

This refactors the `user_color_scheme_class` to use
a hash with a default.  This prevents problems
with workers that don't have access to the
current_user.

Fixes issue #2758

Fix bug with team assignation on project from #4109

Group/Team Atom feed 500 error

Fix for https://github.com/gitlabhq/gitlabhq/issues/4157

Fix for https://github.com/gitlabhq/gitlabhq/issues/4157

Fix rake gitlab:env:info command line in Issue tracker guidelines.

Style target notes for easy visual identification

Fix not displaying a slash after namespace.

Remove user directory path assumptions

Update api docs and remove old attribute from User entity.

Update suggestion for Check.rake

grammar fix in an error message (very minor change)

adding update info regarding gitlab-shell config.yml (re: dashboard update problems)