I encountered an case in the office today where a co-worker recommended that we do not check code into our source code management system because it is accessible company wide. Obviously, this is a legal, ethical and moral issue.
However, this highlighted a problem with closed-source development. With open-source development, this would be a non-issue. The code is supposed to be publicly available anyway. So, the only ACL practices are there to control who can clobber the code if they wish to.
Personally, I think that even implementing ACL on our code repository would not fix the issue. Instead of anyone company-wide being able to steal the code, anyone in our team can do so. So, the ethical, legal and moral issues are still an issue. The whole idea of using a code repository is so that others can share the code. So, at some point, other people can ‘steal’ the code if they wish to.
The only true solution to this problem is to open-source the code. However, working in a closed-source company means that I would not be able to push this through. Everyone would just look at me in an odd way if I ever suggested it.
The trouble is that with this issue, some people may be hesitant on checking in their code. This would just screw up our development process.