I like SVN, but I have not looked into how you can maintain CVS and SVN at the same time, or why you would do that. But if Gustaf is correct about a time delay in commits becoming visible, this is a disaster. Maybe the delay is only for non-developers? Otherwise the whole concept of the repository is lost. I have experienced downtimes with SourceForge, but I don't maintain code there, so I don't know how much it would affect a developer, but downloads via CVS seem slow. Also, AOLserver code is hosted there and you get split discussions with the AOLserver mailing list, and nearly unreadable messages from SourceForge on bugs.