I'll second that. It's politics, and unfortunately, you need a business case to push policy. Wait until the next production outage caused by nasty, ad-hoc chang

I'll second that. It's politics, and unfortunately, you need a business case to push policy. Wait until the next production outage caused by nasty, ad-hoc changes and point at the version control system and say, "If we had this, we could just roll it back." I'd almost say your build process has to accommodate version control first. Capistrano is pretty good at that. If you have a developer with production access, you're bound to get stuff like this.