Don't try to make the deploy group-writable.

The fast-remote-cache only really works when everyone who deploys,
deploys as the same user. This is because of the use of hard-links,
combined with the default deployment option in deploy:finalize_update
that tries to chmod the most recent release. Also, deploys go
significantly faster when you don't have to chmod an entire directory
tree. :)

recipes/fast_remote_cache.rb

@@ -16,17 +16,6 @@
     end
   end
 
-  desc <<-DESC
-    Make sure the cached-copy is group writable. This ensures that when used
-    in a team environment, multiple individuals may deploy using this
-    strategy.
-  DESC
-  task :make_writable, :except => { :no_release => true } do
-    cache = File.join(shared_path, fetch(:repository_cache, "cached-copy"))
-    sudo "chmod -R g+w #{cache}; true"
-  end
-
 end
 
 after "deploy:setup", "fast_remote_cache:setup"
-before "deploy:update_code", "fast_remote_cache:make_writable"