The kinds of people we provide SVN for have almost no technical skills whatsoever. You could spend a month trying to explain what a merge was and they wouldn't

The kinds of people we provide SVN for have almost no technical skills whatsoever. You could spend a month trying to explain what a merge was and they wouldn't understand. But they do need to produce content (which they'd like to be version controlled) that they expect my team to put up on our website. From our point of view, SVN is a near-perfect solution: explain how to check $SOMETHING out and how to check it back in when you've amended it (using the excellent TortoiseSVN). Once they've checked their work back in they email our team email address and one of us runs SVN UP on the relevant server, and we're done.