The WORKSPACE permission has changes its semantic so it does not make sense to be so restrict as before.

There should be an option so that users can revert the old behaviour. But when this issue has been resolved, then source files will be visible even if a user has no WORKSPACE permission. Otherwise we won't see the issues in our CI builds (ci.jenkins.io) in the source code.