I had a chat with Greg Stein about ViewCVS on the ApacheCon (I think Jon Travis and Gregory Trubetskoy where there as well, but my memory is a bit hazy) and since he's probably in some airplane over the atlantic right now, I'll run away and steal his idea ;) We were kind of reflecting how nice it would be if we could have ViewCVS, instead of cvsweb, on SourceForge. The nice thing about ViewCVS is that it's a lot more efficient than cvsweb, and it doesn't need write access to the repository itself. So how about we run ViewCVS on python.sourceforge.net ourselves ? We could do it now, in fact, with the complete CVS snapshot that gets made every once in a while (that *does* still get made & backupped, right ?) though it would obviously be a lot more useful if ViewCVS just had direct access to the repository. I'm not sure how accessible that repository is, however. Cursory searches on shell.sourceforge.net doesn't show anything, except that the python-cvs.tgz that's in /home/projects/python is apparently the one used for the move to sourceforge :-) Can we get access to the repository directly, even if it's only semi-realtime ? (I wouldn't mind doing a couple of rsync's in cron to keep it up to date) If anything, running ViewCVS will show SourceForge how much nicer it is... ;-) -- Thomas Wouters <thomas@xs4all.net> Hi! I'm a .signature virus! copy me into your .signature file to help me spread!