Some important terminology used in CVS

Repository: The master copy where CVS stores a project's full revision history. Each project has exactly one repository.
Check out: To request a working copy from the repository. Your working copy reflects the state of the project as of the moment you checked it out; when you and other developers make changes, you must use the commit and update commands to "publish" your changes and view others' changes.
Commit: To send changes from your working copy into the central repository. Also known as check in.
Conflict: The situation when two developers try to commit changes to the same region of the same file. CVS notices and points out conflicts, but the developers must resolve them.
Log message: A comment you attach to a revision when you commit it, describing the changes. Others can page through the log messages to get a summary of what's been going on in a project.
Revision: A committed change in the history of a file or set of files. A revision is one "snapshot" in a constantly changing project.
Update: To bring others' changes from the repository into your working copy and to show whether your working copy has any uncommitted changes. Be careful not to confuse this with the commit operation; they are complementary, not identical, operations. Here's a mnemonic to help you remember: update brings your working copy up to date with the repository copy.
Working copy: The copy in which you actually make changes to a project. There can be many working copies of a given project; generally, each developer has his or her own copy.

Using CVS for kinbech@IOELIVE

Installing TortoiseCVS

Go to http://tortoisecvs.org/ and download the TortoiseCVS Installer.
To install, run the executable and follow the instructions.
Since TortoiseCVS is a shell extension, you need to reboot your machine.

Checking out kinbech@IOELIVE project

Make sure you have made an account on SourceForge.net, and you got that added as a developer to the project [ kinbech@IOELIVE ] you are going to work on. A project administrator needs to do this.

First register at Sourceforge and then e-mail your username to
<< ioelive at gmail dot com >> with subject "Developer addition request". You can only have COMMIT (write) access to the CVS after addition of your username to developer's list.CHECKOUT access is available to any user.

In Windows Explorer go to the folder that you would like to check the code out into.
Right click and from the context menu choose the command CVS Checkout...; it's next to the Tortoise icon.
You will need your user name on SourceForge.net, and the project UNIX name. Fill in the dialog as follows: Protocol: Secure Shell (:ext)
Server: cvs.sourceforge.net
Directory: /cvsroot/kinbech
Username: your_user_name
Module: kinbech
Click Fetch List to get a choice of modules. You will need to enter your password in the dialog at this point. Then pick the module that you would like.
Choose OK.TortoiseCVS will now check out the code. You will need to enter your password.
You can now alter files and then select CVS Commit on the top level folder to make your changes in the repository. For more information read the TortoiseCVS User's Guide.

Get an error?
If you get an error saying something like Could not chdir to home folder /home/users/i/io/ioelive: No such file or folder then you need to log into the server with SSH to force creation of your home folder. Do this by connecting to username@cvs.sf.net either with Putty or a command line SSH.

For Further reading refer to this sourceforge document.