but converting the current cvs repository to svn is not really trivial ... because of different branch handling ...
some people have branches in their external folders, which would probably be converted to subfolders ... making the directory structure a bit messy ...
i've made good experiences with cvs2svn. Certainly branches would be converted to subfolders because this is the nature of svn. One could try what cvs2svn on the current cvs, then restructure the repo (which should be no great deal with svn), then release it for the community.
greetings Thomas