title: How do I make my colleagues not despise SVN?
body: <p>Many of my colleagues use SVN in groups of 1-5 people partly working on the specific project. Half of them are inexperienced students. In fact non of us are real software developers with year-long experience. Most of them use Eclipse and subclipse to read and write their contributions to the SVN repositories.</p>
  
  <p>Some of them have problems with the difference of:</p>
  
  <ul>
  <li>checking out (confused with update and merge)</li>
  <li>commiting (confused with update)</li>
  <li>updating (confused with commit and check out)</li>
  <li>merging (is the hardest. Whats a merge? Do i have to merge my code "into the SVN"?)</li>
  </ul>
  
  <p>They fear that the SVN might kill their work (they don't call it working branch) if they press the wrong button.</p>
  
  <p>They are committing their eclipse .project files to the repository, after adding some arbitrary library dependencies to their java projects. The other colleagues get compilation errors from these comitts and find it hard to resolve these.</p>
  
  <p>In general they say: <em>I'd like to work without SVN, I don't like it. It's too complex.</em></p>
  
  <p>Is there a e-learning project like "SVN for kids"? How can I make them like version control?</p>