It's a good idea to browse a project's source repository first to learn how the files are organized. CVS refers to the top-level groupings of files as "modules" (rather than "directories").

1. From your Project Home page, click on Source in the Project Resources toolbar.

2. Click on "Browse project source files" to access the project's source repository through CVSWeb.

Each project's web content files are located in the "www/" module by default. Other project source modules are created and organized by each project owner or project members with CVS write permissions. If browsing deleted and removed project files is permitted, an "Attic/" module is displayed.

More information about CVSWeb

To obtain (or "check out") your own working copy of project files, step-by-step instructions are included on the Project Source page for both command line CVS and WinCvs. These instructions also show the exact cvsroot to set for the current project. The cvsroot points to the server location of the project's source repository.

A working copy refers to the replicated set of project source files you maintain and modify on your own local machine. If you are new to CVS, this is an important CVS concept to understand. These files reside in your workspace, and the CVS server does not track or know anything about your changes (or other developers' changes) until you commit modified files or add newly created files back into the main project repository.

This may be different from other versioning systems which explicitly track creation of workspaces. With CVS, you can check out working copies as many times as necessary. Keep in mind, however, that files in the project repository continually change over time as to reflect other developer contributions as the project progresses. It's critical to keep your working copies of files up to date with the repository.

• Command line clients for many systems
• WinCVS: a Windows CVS client
• jCVS: a Java CVS client
• Cervisia: a KDE CVS Client