I'm afraid we've made a mess. Here's the background: Website was developed by a management company with a number of hourly workers. There was no repository. Website then developed by contracted programmers. Repository wasn't in place, and copies were moved around at various stages -- dev local machine, production machine test, development machine, and production machine live. There was not a very good discipline about deleting old copies, and we need to make sense of it all. A repository has been setup using SVN in a web app called CodebaseHQ. It is quite possible that the repository was not the latest/greatest. Here are some symptoms: - completed development work is surprisingly broken (was tested and aproved) - there are a few identified bugs in areas that were not changed recently - there is an uncertainty about the cause of new bugs by the developer Here is the list of tasks: - collect all the various copies of the source code and run a comparison - determine what is what - get rid of "extra" copies - create a (hopefully) known-good copy of the source files - publish a site based on the good copy of the source - delete the existing repository - push the good copy of the source into the SVN repository This sounds more difficult (and larger) than it really is. There are only two machines to look at, but a few drives and directories to investigate. This is a job for a person who has a talent at managing source code, and knows how to use SVN properly. It needs an individual who insists on using standard methods, and finds joy in fixing a mess like this. The sooner it can get done, the better. Desired Skills: Microsoft Visual Studio, File Comparison, IIS Administration, Source Code Management, svn Keywords: Project Management, Source, Studio, Management, Administration, IIS, File, Microsoft, svn, Code, Visual, Comparison