I'm new to CVS, and these are the notes I made for myself concerning accessing/using the python code that we just posted. Hope this is useful to someone. For those of you who will be posting code, I may need to set you up as developers on the OpenCyc project on SourceForge.
---------------

# These instructions are for Linux. For Windows, the method of setting
# environment variables will be different. "sf" means SourceForge.

# EACH TIME:

# set environmental variable to CVS_RSH to ssh
# This has to happen for every new xterm that will issue CVS commands
# related to SourceForge.
export CVS_RSH=ssh

# FIRST TIME:

# Make a dirctory locally (in your home dir?) to keep
# your version of the files from sf CVS.
makedir opencyc-cvs
cd opencyc-cvs

# You should only need to do the following once
export CVSROOT=sourceforgeloginname@cvs.opencyc.sourceforge.net:/cvsroot/opencyc

# Initial checkout of python code
cvs -z3 checkout python

# Initial checkout of Java code (optional -- if you're interested)
cvs -z3 checkout org

# AS NEEDED:

cvs update -d #updates local directory you're in and below and creates new dirs

cvs commit #commits your changes up into the sf repository; prompts for comments

# After creating a file locally, do the following to add it to sf CVS tree
cvs add filename #do it locally, doesn't take effect until commit

cvs add directoryname # Same as above, but for directories

cvs remove filename #removes file from sf CVS tree; do after deleting file locally; doesn't take effect until commit

cvs remove -f filename #removes file from sf CVS tree and deletes file locally; change to cvs tree takes effect after commit