head	1.11;
access;
symbols
	TIGRIS_1_1_0RC2:1.5.6.2
	TIGRIS_1_1_0RC1:1.5.6.2
	TIGRIS_1_1:1.5.6.2.0.2
	TIGRIS_1_0_8:1.5.6.1
	TIGRIS_1_0_8RC3:1.5.6.1
	TIGRIS_1_0_8RC2:1.5.6.1
	TIGRIS_1_0_8RC1:1.5.6.1
	TIGRIS_1_0_7:1.5.6.1
	TIGRIS_1_0_7RC3:1.5.6.1
	TIGRIS_1_0_7RC2:1.5.6.1
	TIGRIS_1_0_7RC1:1.5.6.1
	TIGRIS_1_0_6:1.5.6.1
	TIGRIS_1_0_6RC5:1.5.6.1
	TIGRIS_1_0_6RC4:1.5.6.1
	TIGRIS_1_0_6RC3:1.5
	TIGRIS_1_0_6RC2:1.5
	TIGRIS_1_0_6RC1:1.5
	TIGRIS_1_0_5:1.5
	TIGRIS_1_0_5RC6:1.5
	TIGRIS_1_0_5RC5:1.5
	TIGRIS_1_0_5RC4:1.5
	TIGRIS_1_0_5RC3:1.5
	TIGRIS_1_0_5RC2:1.5
	TIGRIS_1_0_5RC1:1.5
	TIGRIS_1_0_4:1.5
	TIGRIS_1_0_3:1.5
	TIGRIS_1_0_2:1.5
	TIGRIS_1_0_1:1.5
	TIGRIS_1_0:1.5.0.6
	TIGRIS_1_0_0:1.5
	TIGRIS_1_0_0_RC1:1.5.0.2;
locks; strict;
comment	@# @;


1.11
date	2001.08.24.00.17.12;	author tberry;	state Exp;
branches;
next	1.10;

1.10
date	2001.07.24.18.36.50;	author tberry;	state Exp;
branches;
next	1.9;

1.9
date	2001.06.21.07.07.40;	author jefflove;	state Exp;
branches;
next	1.8;

1.8
date	2001.06.11.03.14.33;	author jefflove;	state Exp;
branches;
next	1.7;

1.7
date	2001.05.21.23.37.26;	author lori;	state Exp;
branches;
next	1.6;

1.6
date	2001.05.17.23.42.45;	author lori;	state Exp;
branches;
next	1.5;

1.5
date	2001.03.10.02.21.28;	author lori;	state Exp;
branches
	1.5.6.1;
next	1.4;

1.4
date	2001.02.22.01.02.52;	author lori;	state Exp;
branches;
next	1.3;

1.3
date	2001.02.11.18.29.47;	author jrobbins;	state Exp;
branches;
next	1.2;

1.2
date	2001.02.09.00.59.20;	author susank;	state Exp;
branches;
next	1.1;

1.1
date	2001.01.29.19.44.19;	author lori;	state Exp;
branches;
next	;

1.5.6.1
date	2001.06.13.00.37.08;	author lori;	state Exp;
branches;
next	1.5.6.2;

1.5.6.2
date	2001.07.24.18.51.21;	author tberry;	state Exp;
branches;
next	;


desc
@@


1.11
log
@added index infor.
Issue number:
Obtained from:
Submitted by:
Reviewed by:
@
text
@  <div class="docs" id="ddcvs">
   <h2>About source code version control with CVS</h2>

   <div class="toc">
    <h3>Project resources for developers: Index</h3>
 <ul>
      <li> <a href="Learning.html">Learning about projects</a> </li>
      <li> <a href="ProjectMemberResources.html">Project resources for members</a> 
      </li>
      <li><a href="hostedtools">Hosted tools</a>
      <ul>
        <li><strong>You are here:</strong> About source code version control with 
          CVS 
          <ul>
            <li><a href="#aboutcvs">About CVS</a></li>
            <li><a href="#commitaccess">Getting CVS commit access on open source 
              projects</a></li>
            <li><a href="#morecvsdoc">Further CVS documentation</a></li>
            <li><a href="#cvsclients">CVS clients</a></li>
          </ul>
        </li>
        <li><a href="ProjectAdd.html">Creating a new project</a></li>
      </ul></li>
      <li> More help for CVS 
        <ul>
          <li><a href="ddCVS_cvsglossary.html">A version control glossary</a></li>
          <li><a href="ddUsingCVS_command-line.html">Using command-line CVS to 
            access project source files</a></li>
          <li><a href="ddCVS_cvscontributing.html">Contributing source code changes 
            with CVS</a></li>
          <li><a href="ddCVS_cvsmanaging.html">Managing project files and directories 
            with CVS</a></li>
        </ul>
      </li>
    </ul>
   </div>

   <div class="courtesylinks">
    <p><a href="/servlets/HelpTOC">Back to main Help index</a></p>
   </div>

   <h3><a id="aboutcvs" name="aboutcvs">About CVS</a></h3>

   <p>The Concurrent Versions System (CVS) is a version control system for keeping track of all modifications to project source code files. CVS is widely used in both open source and proprietary software development projects, and is generally considered to be the best freely available, full-featured version control tool. Two special features make CVS particularly suited to collaborative development across the Internet:</p>

   <ol>
    <li>CVS allows multiple developers to edit their own working copies of files simultaneously, then deals with combining all the changes and notifying developers when there are conflicts.</li>

    <li>Remote access to source code file repositories. Developers who are project members can obtain and modify project files from virtually anywhere.</li>
   </ol>

   <p>CVS is a client-server system. The CVS repository is maintained on a web server; clients run on users' machines and connect to the server via the Internet. You must have a CVS client on your local machine to access the CVS server for projects hosted on this site. <a href="#cvsclients">Clients</a> are available for nearly all platforms including: Unix, Windows, Macintosh, and any Java-based platform. This documentation includes instructions for running CVS in a Unix shell or WinCVS.</p>

   <p>As a project member, CVS allows you to:</p>

   <ul>
    <li>Check out source files and directories</li>

    <li>View differences between versions of files</li>

    <li>View change log history and comments</li>

    <li>Commit changes made in your local copy of the source files to the main source code repository</li>

    <li>Update your local project files when you want to remain in sync with changes committed by other project members</li>
   </ul>

   <p>If you are new to CVS, one the best ways to learn about it is simply to jump in and begin using it. When you click on the <i>Source Code</i> link in the Project Resources tool bar, you can follow the instructions in that page for checking out your own working copy of a particular project's source files. You can also find further, more specific information in this site's three-part CVS tool document, <a href="ddUsingCVS_command-line.html">Using command-line CVS</a> or <a href="ddUsingWinCVS.html">Using WinCVS</a>.</p>

   <p>For those looking for a step-by-step orientation of CVS, <a href="http://cvsbook.red-bean.com/cvsbook.html#A_Day_With_CVS">A Day with CVS</a>, excerpted from the online version of Karl Fogel's book, <b><i>Open Source Development with CVS</i></b>, is highly recommended. Much of the CVS help information on this site comes from this authoritative source.</p>

   <h3><a id="commitaccess" name="commitaccess">Getting CVS commit access on open source projects</a></h3>

   <p>Suppose you are interested in joining an open source project but you are unknown to the project owner and other project members. The logical first step is requesting to join the project, of course, but you can take some basic preliminary steps toward establishing yourself as a potential contributor, thereby raising the likelihood of gaining membership approval.</p>

   <ol>
    <li>Subscribe to <b>and regularly read</b> the relevant mailing lists so that you know what is going on in the particular area of development you are interested in.</li>

    <li>When you post your first message to a discussion mailing list, introduce yourself and include the following:</li>

    <li>
     <ul>
      <li>who you are</li>

      <li>a few words on your background</li>

      <li>your interest in the project, and</li>

      <li>what you would like to see happen with the project.</li>
     </ul>
    </li>

    <li>Make sure you have browsed through the existing source code and understand what it is doing and how. If something is poorly documented, confusing, or you just can't grasp what is going on, ask on the associated mailing list for a summary.</li>

    <li>Mention in writing that you understand the licensing governing the code that you will be working on, and your agreement that any changes you contribute are your own and these can be incorporated under that license.</li>

    <li>Request project membership to gain cvs check-in permissions on an area of the code base, and explain what sorts of things you are interested in doing with it. You will need to communicate frequently with the people who already maintain that area of code, so make sure there is consensus about what you should be working on.</li>

    <li>When the project owner approves your project membership, you will get a CVS check-in account, probably restricted to a certain area. Make sure you understand which CVS branch you are supposed to be working on!</li>

    <li>Submit some patches to establish that you know what you are doing.</li>

    <li>When you make modifications and enhancements, seek feedback and discussion about these on the associated mailing lists.</li>
   </ol>

   <h3><a id="morecvsdoc" name="morecvsdoc">Further CVS documentation</a></h3>

   <ul>
    <li><a href="http://www.gnu.org/manual/cvs/index.html">CVS Manual</a></li>

    <li><a href="http://www.cyclic.com/">CVS Home Page at Cyclic</a></li>

    <li><a href="http://www.loria.fr/~molli/cvs-index.html">Pascal Molli's CVS page</a></li>

    <li><a href="http://dmoz.org/Computers/Software/Configuration_Management/Tools/CVS/">CVS Page on Dmoz</a></li>
   </ul>

   <h3>CVS Books</h3>

   <ul>
    <li><a href="http://www.amazon.com/exec/obidos/ISBN%3D0132408546/cyclicsoftwareA/">Practical Software Configuration Management</a></li>

    <li><a href="http://cvsbook.red-bean.com/">Open Source Development with CVS</a> (online chapters version)</li>
   </ul>

   <h3><a id="cvsclients" name="cvsclients">CVS Clients</a></h3>

   <ul>
    <li><a href="http://www.cvshome.org/downloads.html">Command line clients for many systems</a></li>

    <li><a href="http://www.cvsgui.org/download.html">WinCVS: a Windows CVS client</a></li>

    <li><a href="http://www.jcvs.org/">jCVS: a Java CVS client</a></li>

    <li><a href="http://cervisia.sourceforge.net">Cervisia: a KDE CVS Client</a></li>
   </ul>

   <div class="courtesylinks">
    <p><a href="ProjectSource.html">Back to Project Source help</a><br />
     <a href="/servlets/HelpTOC">Back to main Help index</a></p>
   </div>
  </div>
 


@


1.10
log
@fixed broken link

Issue number:
Obtained from:
Submitted by:
Reviewed by:
@
text
@d5 6
a10 6
    <h3>CVS tool documents: Index</h3>

    <ul>
     <li>
      <strong>You are here:</strong> About source code version control with CVS 

d12 23
a34 23
       <li><a href="#aboutcvs">About CVS</a></li>

       <li><a href="#commitaccess">Getting CVS commit access on open source projects</a></li>

       <li><a href="#morecvsdoc">Further CVS documentation</a></li>

       <li><a href="#cvsclients">CVS clients</a></li>
      </ul>
     </li>

     <li>
      More help for CVS 

      <ul>
       <li><a href="ddCVS_cvsglossary.html">A version control glossary</a></li>

       <li><a href="ddUsingCVS_command-line.html">Using command-line CVS to access project source files</a></li>

       <li><a href="ddCVS_cvscontributing.html">Contributing source code changes with CVS</a></li>

       <li><a href="ddCVS_cvsmanaging.html">Managing project files and directories with CVS</a></li>
      </ul>
     </li>
@


1.9
log
@html usage revision
@
text
@d129 1
a129 1
    <li><a href="http://www.cyclic.com&lt;/UL&gt;&lt;/ul&gt;m/downloads.html">Command line clients for many systems</a></li>
@


1.8
log
@extensive markup rework - first pass toward house xhtmlification
@
text
@d1 9
a9 11
<!DOCTYPE html PUBLIC "-//CollabNet//DTD XHTML 1.0 Transitional//EN"
"http://collabnet.com/dtds/collabnet_transitional_10.dtd">
<html>
 <head>
  <title>About CVS</title>
<style type="text/css">
 li.c3 {list-style: none}
 div.c2 {margin-left: 2em}
 dt.c1 {font-weight: bold}
</style>
 </head>
d11 2
a12 10
 <body>
  <div class="docs" id="ddcvs">
<h2>About source code version control with CVS</h2>
 <p>
 <b>CVS tool documents: Index</b> 
</p>

  <div class="c2">
   <dl>
    <dt>You are here: About source code version control with CVS</dt>
d14 1
a14 3
    <dd>
     <ul>
      <li><b><a href="#aboutcvs">About CVS</a></b></li>
d16 1
a16 1
      <li><b><a href="#commitaccess">Getting CVS commit access on open source projects</a></b></li>
d18 3
a20 1
      <li><b><a href="#morecvsdoc">Further CVS documentation</a></b></li>
d22 2
a23 3
      <li><b><a href="#cvsclients">CVS clients</a></b></li>
     </ul>
    </dd>
d25 2
a26 1
    <dt>More help for CVS</dt>
d28 1
a28 1
    <dd><a href="ddCVS_cvsglossary.html">A version control glossary</a></dd>
d30 1
a30 1
    <dd><a href="ddUsingCVS_command-line.html">Using command-line CVS to access project source files</a></dd>
d32 5
a36 1
    <dd><a href="ddCVS_cvscontributing.html">Contributing source code changes with CVS</a></dd>
d38 3
a40 1
    <dd><a href="ddCVS_cvsmanaging.html">Managing project files and directories with CVS</a></dd>
d42 1
a42 3
    <dt><a href="/servlets/HelpTOC">Back to main Help index</a></dt>
   </dl>
  </div>
d44 1
a44 1
  <h3><a id="aboutcvs" name="aboutcvs">About CVS</a></h3>
d46 2
a47 1
  <p>The Concurrent Versions System (CVS) is a version control system for keeping track of all modifications to project source code files. CVS is widely used in both open source and proprietary software development projects, and is generally considered to be the best freely available, full-featured version control tool. Two special features make CVS particularly suited to collaborative development across the Internet:</p>
d49 2
a50 2
  <ol>
   <li>CVS allows multiple developers to edit their own working copies of files simultaneously, then deals with combining all the changes and notifying developers when there are conflicts.</li>
d52 1
a52 2
   <li>Remote access to source code file repositories. Developers who are project members can obtain and modify project files from virtually anywhere.</li>
  </ol>
d54 1
a54 1
  <p>CVS is a client-server system. The CVS repository is maintained on a web server; clients run on users' machines and connect to the server via the Internet. You must have a CVS client on your local machine to access the CVS server for projects hosted on this site. <a href="#cvsclients">Clients</a> are available for nearly all platforms including: Unix, Windows, Macintosh, and any Java-based platform. This documentation includes instructions for running CVS in a Unix shell or WinCVS.</p>
d56 2
a57 1
  <p>As a project member, CVS allows you to:</p>
d59 1
a59 2
  <ul>
   <li>Check out source files and directories</li>
d61 1
a61 1
   <li>View differences between versions of files</li>
d63 1
a63 1
   <li>View change log history and comments</li>
d65 2
a66 1
   <li>Commit changes made in your local copy of the source files to the main source code repository</li>
d68 1
a68 2
   <li>Update your local project files when you want to remain in sync with changes committed by other project members</li>
  </ul>
d70 1
a70 1
  <p>If you are new to CVS, one the best ways to learn about it is simply to jump in and begin using it. When you click on the <i>Source Code</i> link in the Project Resources tool bar, you can follow the instructions in that page for checking out your own working copy of a particular project's source files. You can also find further, more specific information in this site's three-part CVS tool document, <a href="ddUsingCVS_command-line.html">Using command-line CVS</a> or <a href="ddUsingWinCVS.html">Using WinCVS</a>.</p>
d72 1
a72 3
  <p>For those looking for a step-by-step orientation of CVS, <a href="http://cvsbook.red-bean.com/cvsbook.html#A_Day_With_CVS">A Day with CVS</a>, excerpted from the online version of Karl Fogel's book, <b><i>Open Source Development with CVS</i></b>, is highly recommended. Much of the CVS help information on this site comes from this authoritative source.</p>
  
  
d74 1
a74 1
  <h3><a id="commitaccess" name="commitaccess">Getting CVS commit access on open source projects</a></h3>
d76 2
a77 1
  <p>Suppose you are interested in joining an open source project but you are unknown to the project owner and other project members. The logical first step is requesting to join the project, of course, but you can take some basic preliminary steps toward establishing yourself as a potential contributor, thereby raising the likelihood of gaining membership approval.</p>
d79 1
a79 2
  <ol>
   <li>Subscribe to <b>and regularly read</b> the relevant mailing lists so that you know what is going on in the particular area of development you are interested in.</li>
d81 3
a83 1
   <li>When you post your first message to a discussion mailing list, introduce yourself and include the following:</li>
d85 1
a85 3
   <li class="c3">
    <ul>
     <li>who you are</li>
d87 1
a87 1
     <li>a few words on your background</li>
d89 3
a91 1
     <li>your interest in the project, and</li>
d93 1
a93 3
     <li>what you would like to see happen with the project.</li>
    </ul>
   </li>
d95 1
a95 1
   <li>Make sure you have browsed through the existing source code and understand what it is doing and how. If something is poorly documented, confusing, or you just can't grasp what is going on, ask on the associated mailing list for a summary.</li>
d97 1
a97 1
   <li>Mention in writing that you understand the licensing governing the code that you will be working on, and your agreement that any changes you contribute are your own and these can be incorporated under that license.</li>
d99 1
a99 1
   <li>Request project membership to gain cvs check-in permissions on an area of the code base, and explain what sorts of things you are interested in doing with it. You will need to communicate frequently with the people who already maintain that area of code, so make sure there is consensus about what you should be working on.</li>
d101 1
a101 1
   <li>When the project owner approves your project membership, you will get a CVS check-in account, probably restricted to a certain area. Make sure you understand which CVS branch you are supposed to be working on!</li>
d103 2
a104 1
   <li>Submit some patches to establish that you know what you are doing.</li>
d106 1
a106 4
   <li>When you make modifications and enhancements, seek feedback and discussion about these on the associated mailing lists.</li>
  </ol>
  
  
d108 2
a109 1
  <h3><a id="morecvsdoc" name="morecvsdoc">Further CVS documentation</a></h3>
d111 1
a111 2
  <ul>
   <li><a href="http://www.gnu.org/manual/cvs/index.html">CVS Manual</a></li>
d113 1
a113 1
   <li><a href="http://www.cyclic.com/">CVS Home Page at Cyclic</a></li>
d115 2
a116 1
   <li><a href="http://www.loria.fr/~molli/cvs-index.html">Pascal Molli's CVS page</a></li>
d118 1
a118 2
   <li><a href="http://dmoz.org/Computers/Software/Configuration_Management/Tools/CVS/">CVS Page on Dmoz</a></li>
  </ul>
d120 2
a121 1
  <h3>CVS Books</h3>
d123 2
a124 2
  <ul>
   <li><a href="http://www.amazon.com/exec/obidos/ISBN%3D0132408546/cyclicsoftwareA/">Practical Software Configuration Management</a></li>
d126 1
a126 4
   <li><a href="http://cvsbook.red-bean.com/">Open Source Development with CVS</a> (online chapters version)</li>
  </ul>
  
  
d128 2
a129 1
  <h3><a id="cvsclients" name="cvsclients">CVS Clients</a></h3>
d131 1
a131 2
  <ul>
   <li><a href="http://www.cyclic.com&lt;/UL&gt;&lt;/ul&gt;m/downloads.html">Command line clients for many systems</a></li>
d133 1
a133 1
   <li><a href="http://www.cvsgui.org/download.html">WinCVS: a Windows CVS client</a></li>
d135 2
a136 1
   <li><a href="http://www.jcvs.org/">jCVS: a Java CVS client</a></li>
d138 6
a143 8
   <li><a href="http://cervisia.sourceforge.net">Cervisia: a KDE CVS Client</a></li>
  </ul>
  
  <div class="courtesylinks"><a href="ProjectSource.html">Back to Project Source help</a><br />
 <div class="courtesylinks"><a href="/servlets/HelpTOC">Back to main Help index</a></div></div>
 </div>
</body>
</html>
@


1.7
log
@changed name of internal link reference
@
text
@d1 2
d4 14
a17 57
<head>
<title>About CVS</title>
</head>
<body>
<span class="Header" nowrap>About source code version control with CVS</span>  

      <p></p>

<span class="PlainText"><b>CVS tool documents: Index</b>
<p></p>
<ul>
<dl>
<dt><b>You are here: About source code version control with CVS
	<ul>
	<li><a href="#aboutcvs">About CVS</a>
	<li><a href="#commitaccess">Getting CVS commit access on open source projects</a>
	<li><a href="#morecvsdoc">Further CVS documentation</a>
	<li><a href="#cvsclients">CVS clients</a>
	</ul></b>
<p></p>
<dt><b>More help for CVS</b>
<dd><a href="ddCVS_cvsglossary.html">A version control glossary</a>
<dd><a href="ddUsingCVS_command-line.html">Using command-line CVS to access project source files</a>
<dd><a href="ddCVS_cvscontributing.html">Contributing source code changes with CVS</a>
<dd><a href="ddCVS_cvsmanaging.html">Managing project files and directories with CVS</a>
<dt><a href="/servlets/HelpTOC">Back to main Help index</a>
</dl>
</ul>
<p>

<hr noshade size=1>
<a name="aboutcvs"></a><span class="InputHeader">About CVS</span>

      <p>The Concurrent Versions System (CVS) is a version control system for keeping track of all modifications to project source code files. CVS is widely used in both open source and proprietary software development projects, and is generally considered to be the best freely available, full-featured version control tool. Two special features make CVS particularly suited to collaborative development across the Internet:</p>

<ol>
<li>CVS allows multiple developers to edit their own working copies of files simultaneously, then deals with combining all the changes and notifying developers when there are conflicts.</li>
<p></p>
<li>Remote access to source code file repositories. Developers who are project members can obtain and modify project files from virtually anywhere.</li>
</ol>

     <p>CVS is a client-server system. The CVS repository is maintained on a web server; clients run on users' machines and connect to the server via the Internet. You must have a CVS client on your local machine to access the CVS server for projects hosted on this site. <a href="#cvsclients">Clients</a> are available for nearly all platforms including: Unix, Windows, Macintosh, and any Java-based platform. This documentation includes instructions for running CVS in a Unix shell or WinCVS.</p>

<p>
As a project member, CVS allows you to:</p>
      <ul>
        <li>Check out source files and directories</li>
        <li>View differences between versions of files</li>
        <li>View change log history and comments</li>
        <li>Commit changes made in your local copy of the source files to the main source code repository</li>
        <li>Update your local project files when you want to remain in sync with changes committed by other project members</li>
      </ul>
<p>
If you are new to CVS, one the best ways to learn about it is simply to jump in and begin using it. When you click on the <i>Source Code</i> link in the Project Resources tool bar, you can follow the instructions in that page for checking out your own working copy of a particular project's source files.
You can also find further, more specific information in this site's three-part CVS tool document, <a href="ddUsingCVS_command-line.html">Using command-line CVS</a> or <a href="ddUsingWinCVS.html">Using WinCVS</a>.</p>
<p>
For those looking for a step-by-step orientation of CVS, <a href="http://cvsbook.red-bean.com/cvsbook.html#A_Day_With_CVS" target="_new">A Day with CVS</a>, excerpted from the online version of Karl Fogel's book, <b><i>Open Source Development with CVS</i></b>, is highly recommended. Much of the CVS help information on this site comes from this authoritative source.
d19 73
a91 34
      
<hr noshade size=1>
<a name="commitaccess"></a><span class="InputHeader">Getting CVS commit access on open source projects</span>
     <p>
Suppose you are interested in joining an open source project but you are unknown to the project owner and other project members. The logical first step is requesting to join the project, of course, but you can take some basic preliminary steps toward establishing yourself as a potential contributor, thereby raising the likelihood of gaining membership approval.</p>
      <ol>
       <li>Subscribe to <b>and regularly read</b> the relevant mailing lists so that you know what is going on in the particular area of development you are interested in.</li>
     <p>
       <li>When you post your first message to a discussion mailing list, introduce yourself and include the following:</li>
     <p>
      <ul>
       <li>who you are</li> 
       <li>a few words on your background</li> 
       <li>your interest in the project, and</li> 
       <li>what you would like to see happen with the project.</li>
      </ul>
     <p></p>
       <li>Make sure you have browsed through the existing source code and understand what it is doing and how. If something is poorly documented, confusing, or you just can't grasp what is going on, ask on the associated mailing list for a summary.</li>
     <p></p>
       <li>Mention in writing that you understand the licensing governing the code that you will be working on, and your agreement that any changes you contribute are your own and these can be incorporated under that license.</li>
     <p></p>
	   <li>Request project membership to gain cvs check-in permissions on an area of the code base, and explain what sorts of things you are interested in doing with it. You will need to communicate frequently with the people who already maintain that area of code, so make sure there is consensus about what you should be working on.</li>
     <p></p>
       <li>When the project owner approves your project membership, you will get a CVS check-in account, probably restricted to a certain area. Make sure you understand which CVS branch you are supposed to be working on!</li>
     <p></p>
       <li>Submit some patches to establish that you know what you are doing.</li> 
	<p></p>
       <li>When you make modifications and enhancements, seek feedback and discussion about these on the associated mailing lists.</li>
     </ol>
<p></p>

<hr noshade size=1>
<a name="morecvsdoc"></a><span class="InputHeader">Further CVS documentation</span>
<p></p>
d93 13
a105 1
      <li><a href="http://www.gnu.org/manual/cvs/index.html" target=_new>CVS Manual</a></li>
d107 1
a107 1
      <li><a href="http://www.cyclic.com/" target=_new>CVS Home Page at Cyclic</a></li>
d109 1
a109 1
      <li><a href="http://www.loria.fr/~molli/cvs-index.html" target=_new>Pascal Molli's CVS page</a></li>
d111 15
a125 2
      <li><a href="http://dmoz.org/Computers/Software/Configuration_Management/Tools/CVS/" target=_new>CVS Page on Dmoz</a></li>
     </ul>
d127 2
a128 5
<span class="InputHeader">CVS Books</span>
     <ul>
      <li><a href="http://www.amazon.com/exec/obidos/ISBN=0132408546/cyclicsoftwareA/"  target="_new">Practical Software Configuration Management</a> </li>
      <li><a href="http://cvsbook.red-bean.com/" target="_new">Open Source Development with CVS</a> (online chapters version)</li>
     </ul>
d130 1
a130 1
<p>
d132 2
a133 5
<hr noshade size=1>
<a name="cvsclients"></a><span class="InputHeader">CVS Clients</span>
     <ul>
     <li><a
      href="http://www.cyclic.com</UL></ul>m/downloads.html" target="_new">Command line clients for many systems</a></li>
d135 4
a138 1
      <li><a href="http://www.cvsgui.org/download.html" target="_new">WinCVS: a Windows CVS client</a></li>
d140 1
a140 1
      <li><a href="http://www.jcvs.org/" target="_new">jCVS: a Java CVS client</a></li>
d142 2
a143 3
      <li><a href="http://cervisia.sourceforge.net" target="_new">Cervisia: a KDE CVS Client</a></li>
     </ul>
<p>
d145 1
a145 3
<hr noshade size=1>
<a href="ProjectSource.html">Back to Project Source help</a><br>
<a href="/servlets/HelpTOC">Back to main Help index</a></p></span>
d147 1
d149 6
a154 1
</span> 
d157 2
@


1.6
log
@changing structure of doc index to include 'More help for CVS' heading with following docs all at same indent level
@
text
@d17 1
a17 1
	<li><a href="#checkinaccess">Getting CVS check-in access on open source projects</a>
d62 1
a62 1
<a name="checkinaccess"></a><span class="InputHeader">Getting CVS check-in access on open source projects</span>
@


1.5
log
@fixed broken link
@
text
@d1 59
a59 59
<HTML>
<HEAD>
<TITLE>About CVS</TITLE>
</HEAD>
<BODY>
<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
  <TR>
    <SPAN CLASS="Header" NOWRAP>About source code version control with CVS</SPAN>  

      <P>

<SPAN CLASS="PlainText"><B>CVS tool documents: Index</B>
<P>
<UL>
<DL>
<DT><B>You are here: About source code version control with CVS
	<UL>
	<LI><A HREF="#aboutcvs">About CVS</A>
	<LI><A HREF="#checkinaccess">Getting CVS check-in access on open source projects</A>
	<LI><A HREF="#morecvsdoc">Further CVS documentation</A>
	<LI><A HREF="#cvsclients">CVS clients</A>
	</UL></B>
<DT><A HREF="ddCVS_cvsglossary.html">A version control glossary</A>
<DD><A HREF="ddUsingCVS_command-line.html">Using command-line CVS to access project source files</A>
<DD><A HREF="ddCVS_cvscontributing.html">Contributing source code changes with CVS</A>
<DD><A HREF="ddCVS_cvsmanaging.html">Managing project files and directories with CVS</A>
<DT><A HREF="/servlets/HelpTOC">Back to main Help index</A>
</DL>
</UL>
<P>

<HR NOSHADE SIZE=1>
<A NAME="aboutcvs"></A><SPAN CLASS="InputHeader">About CVS</SPAN>

      <P>The Concurrent Versions System (CVS) is a version control system for keeping track of all modifications to project source code files. CVS is widely used in both open source and proprietary software development projects, and is generally considered to be the best freely available, full-featured version control tool. Two special features make CVS particularly suited to collaborative development across the Internet: 

<OL>
<LI>CVS allows multiple developers to edit their own working copies of files simultaneously, then deals with combining all the changes and notifying developers when there are conflicts.
<P>
<LI>Remote access to source code file repositories. Developers who are project members can obtain and modify project files from virtually anywhere.
</OL>

     <P>CVS is a client-server system. The CVS repository is maintained on a web server; clients run on users' machines and connect to the server via the Internet. You must have a CVS client on your local machine to access the CVS server for projects hosted on this site. <A HREF="#cvsclients">Clients</A> are available for nearly all platforms including: Unix, Windows, Macintosh, and any Java-based platform. This documentation includes instructions for running CVS in a Unix shell or WinCvs. 
     <P>

As a project member, CVS allows you to:
      <UL>
        <LI>Check out source files and directories</LI>
        <LI>View differences between versions of files</LI>
        <LI>View change log history and comments</LI>
        <LI>Commit changes made in your local copy of the source files to the main source code repository</LI>
        <LI>Update your local project files when you want to remain in sync with changes committed by other project members</LI>
      </UL>
<P>
If you are new to CVS, one the best ways to learn about it is simply to jump in and begin using it. When you click on the <I>Source Code</I> link in the Project Resources tool bar, you can follow the instructions in that page for checking out your own working copy of a particular project's source files.
You can also find further, more specific information in this site's three-part CVS tool document, <A HREF="ddUsingCVS_command-line.html">Using command-line CVS</A> or <A HREF="ddUsingWinCvs.html">Using WinCvs</A>.
<P>
For those looking for a step-by-step orientation of CVS, <A HREF="http://cvsbook.red-bean.com/cvsbook.html#A_Day_With_CVS" TARGET="_new">A Day with CVS</A>, excerpted from the online version of Karl Fogel's book, <B><I>Open Source Development with CVS</I></B>, is highly recommended. Much of the CVS help information on this site comes from this authoritative source.
<P>
d61 73
a133 74
<HR NOSHADE SIZE=1>
<A NAME="checkinaccess"></A><SPAN CLASS="InputHeader">Getting CVS check-in access on open source projects</SPAN>
     <P>
Suppose you are interested in joining an open source project but you are unknown to the project owner and other project members. The logical first step is requesting to join the project, of course, but you can take some basic preliminary steps toward establishing yourself as a potential contributor, thereby raising the likelihood of gaining membership approval.
      <OL>
       <LI>Subscribe to <B>and regularly read</B> the relevant mailing lists so that you know what is going on in the particular area of development you are interested in.
     <P>
       <LI>When you post your first message to a discussion mailing list, introduce yourself and include the following:
     <P>
      <UL>
       <LI>who you are,<BR> 
       <LI>a few words on your background,<BR> 
       <LI>your interest in the project, and<BR> 
       <LI>what you would like to see happen with the project.<BR>
      </UL>
     <P>
       <LI>Make sure you have browsed through the existing source code and understand what it is doing and how. If something is poorly documented, confusing, or you just can't grasp what is going on, ask on the associated mailing list for a summary.
     <P>
       <LI>Mention in writing that you understand the licensing governing the code that you will be working on, and your agreement that any changes you contribute are your own and these can be incorporated under that license.
     <P>
	   <LI>Request project membership to gain cvs check-in permissions on an area of the code base, and explain what sorts of things you are interested in doing with it. You will need to communicate frequently with the people who already maintain that area of code, so make sure there is consensus about what you should be working on.
     <P>
       <LI>When the project owner approves your project membership, you will get a CVS check-in account, probably restricted to a certain area. Make sure you understand which CVS branch you are supposed to be working on!
     <P>
       <LI>Submit some patches to establish that you know what you are doing. 
	<P>
       <LI>When you make modifications and enhancements, seek feedback and discussion about these on the associated mailing lists.
     </OL>
<P>

<HR NOSHADE SIZE=1>
<A NAME="morecvsdoc"></A><SPAN CLASS="InputHeader">Further CVS documentation</SPAN>
<P>
    <UL>
      <LI><A HREF="http://www.gnu.org/manual/cvs/index.html" TARGET=_NEW>CVS Manual</A></LI>

      <LI><A HREF="http://www.cyclic.com/" TARGET=_NEW>CVS Home Page at Cyclic</A></LI>

      <LI><A HREF="http://www.loria.fr/~molli/cvs-index.html" TARGET=_NEW>Pascal Molli's CVS page</A></LI>

      <LI><A HREF="http://dmoz.org/Computers/Software/Configuration_Management/Tools/CVS/" TARGET=_NEW>CVS Page on Dmoz</A></LI>
     </UL>

<SPAN CLASS="InputHeader">CVS Books</SPAN>
     <UL>
      <LI><A HREF="http://www.amazon.com/exec/obidos/ISBN=0132408546/cyclicsoftwareA/"  TARGET="_new">Practical Software Configuration Management</A> </LI>
      <LI><A HREF="http://cvsbook.red-bean.com/" TARGET="_new">Open Source Development with CVS</A> (online chapters version)</LI>
     </UL>

<P>

<HR NOSHADE SIZE=1>
<A NAME="cvsclients"></A><SPAN CLASS="InputHeader">CVS Clients</SPAN>
     <UL>
     <LI><A
      HREF="http://www.cyclic.com</UL></UL>m/downloads.html" target="_new">Command line clients for many systems</A></LI>

      <LI><A HREF="http://www.cvsgui.org/download.html" TARGET="_new">WinCVS: a Windows CVS client</A></LI>

      <LI><A HREF="http://www.jcvs.org/" TARGET="_new">jCVS: a Java CVS client</A></LI>

      <LI><A HREF="http://cervisia.sourceforge.net" TARGET="_new">Cervisia: a KDE CVS Client</A></LI>
     </UL>
<P>

<HR NOSHADE SIZE=1>
<A HREF="ProjectSource.html">Back to Project Source help</A><BR>
<A HREF="/servlets/HelpTOC">Back to main Help index</A></P></SPAN>


  </TR>
</TABLE>
</BODY>
</HTML>
@


1.5.6.1
log
@updating branch with latest help files
@
text
@d1 59
a59 59
<html>
<head>
<title>About CVS</title>
</head>
<body>
<span class="Header" nowrap>About source code version control with CVS</span>  

      <p></p>

<span class="PlainText"><b>CVS tool documents: Index</b>
<p></p>
<ul>
<dl>
<dt><b>You are here: About source code version control with CVS
	<ul>
	<li><a href="#aboutcvs">About CVS</a>
	<li><a href="#commitaccess">Getting CVS commit access on open source projects</a>
	<li><a href="#morecvsdoc">Further CVS documentation</a>
	<li><a href="#cvsclients">CVS clients</a>
	</ul></b>
<p></p>
<dt><b>More help for CVS</b>
<dd><a href="ddCVS_cvsglossary.html">A version control glossary</a>
<dd><a href="ddUsingCVS_command-line.html">Using command-line CVS to access project source files</a>
<dd><a href="ddCVS_cvscontributing.html">Contributing source code changes with CVS</a>
<dd><a href="ddCVS_cvsmanaging.html">Managing project files and directories with CVS</a>
<dt><a href="/servlets/HelpTOC">Back to main Help index</a>
</dl>
</ul>
<p>

<hr noshade size=1>
<a name="aboutcvs"></a><span class="InputHeader">About CVS</span>

      <p>The Concurrent Versions System (CVS) is a version control system for keeping track of all modifications to project source code files. CVS is widely used in both open source and proprietary software development projects, and is generally considered to be the best freely available, full-featured version control tool. Two special features make CVS particularly suited to collaborative development across the Internet:</p>

<ol>
<li>CVS allows multiple developers to edit their own working copies of files simultaneously, then deals with combining all the changes and notifying developers when there are conflicts.</li>
<p></p>
<li>Remote access to source code file repositories. Developers who are project members can obtain and modify project files from virtually anywhere.</li>
</ol>

     <p>CVS is a client-server system. The CVS repository is maintained on a web server; clients run on users' machines and connect to the server via the Internet. You must have a CVS client on your local machine to access the CVS server for projects hosted on this site. <a href="#cvsclients">Clients</a> are available for nearly all platforms including: Unix, Windows, Macintosh, and any Java-based platform. This documentation includes instructions for running CVS in a Unix shell or WinCVS.</p>

<p>
As a project member, CVS allows you to:</p>
      <ul>
        <li>Check out source files and directories</li>
        <li>View differences between versions of files</li>
        <li>View change log history and comments</li>
        <li>Commit changes made in your local copy of the source files to the main source code repository</li>
        <li>Update your local project files when you want to remain in sync with changes committed by other project members</li>
      </ul>
<p>
If you are new to CVS, one the best ways to learn about it is simply to jump in and begin using it. When you click on the <i>Source Code</i> link in the Project Resources tool bar, you can follow the instructions in that page for checking out your own working copy of a particular project's source files.
You can also find further, more specific information in this site's three-part CVS tool document, <a href="ddUsingCVS_command-line.html">Using command-line CVS</a> or <a href="ddUsingWinCvs.html">Using WinCVS</a>.</p>
<p>
For those looking for a step-by-step orientation of CVS, <a href="http://cvsbook.red-bean.com/cvsbook.html#A_Day_With_CVS" target="_new">A Day with CVS</a>, excerpted from the online version of Karl Fogel's book, <b><i>Open Source Development with CVS</i></b>, is highly recommended. Much of the CVS help information on this site comes from this authoritative source.
</p>
d61 74
a134 73
<hr noshade size=1>
<a name="commitaccess"></a><span class="InputHeader">Getting CVS commit access on open source projects</span>
     <p>
Suppose you are interested in joining an open source project but you are unknown to the project owner and other project members. The logical first step is requesting to join the project, of course, but you can take some basic preliminary steps toward establishing yourself as a potential contributor, thereby raising the likelihood of gaining membership approval.</p>
      <ol>
       <li>Subscribe to <b>and regularly read</b> the relevant mailing lists so that you know what is going on in the particular area of development you are interested in.</li>
     <p>
       <li>When you post your first message to a discussion mailing list, introduce yourself and include the following:</li>
     <p>
      <ul>
       <li>who you are</li> 
       <li>a few words on your background</li> 
       <li>your interest in the project, and</li> 
       <li>what you would like to see happen with the project.</li>
      </ul>
     <p></p>
       <li>Make sure you have browsed through the existing source code and understand what it is doing and how. If something is poorly documented, confusing, or you just can't grasp what is going on, ask on the associated mailing list for a summary.</li>
     <p></p>
       <li>Mention in writing that you understand the licensing governing the code that you will be working on, and your agreement that any changes you contribute are your own and these can be incorporated under that license.</li>
     <p></p>
	   <li>Request project membership to gain cvs check-in permissions on an area of the code base, and explain what sorts of things you are interested in doing with it. You will need to communicate frequently with the people who already maintain that area of code, so make sure there is consensus about what you should be working on.</li>
     <p></p>
       <li>When the project owner approves your project membership, you will get a CVS check-in account, probably restricted to a certain area. Make sure you understand which CVS branch you are supposed to be working on!</li>
     <p></p>
       <li>Submit some patches to establish that you know what you are doing.</li> 
	<p></p>
       <li>When you make modifications and enhancements, seek feedback and discussion about these on the associated mailing lists.</li>
     </ol>
<p></p>

<hr noshade size=1>
<a name="morecvsdoc"></a><span class="InputHeader">Further CVS documentation</span>
<p></p>
    <ul>
      <li><a href="http://www.gnu.org/manual/cvs/index.html" target=_new>CVS Manual</a></li>

      <li><a href="http://www.cyclic.com/" target=_new>CVS Home Page at Cyclic</a></li>

      <li><a href="http://www.loria.fr/~molli/cvs-index.html" target=_new>Pascal Molli's CVS page</a></li>

      <li><a href="http://dmoz.org/Computers/Software/Configuration_Management/Tools/CVS/" target=_new>CVS Page on Dmoz</a></li>
     </ul>

<span class="InputHeader">CVS Books</span>
     <ul>
      <li><a href="http://www.amazon.com/exec/obidos/ISBN=0132408546/cyclicsoftwareA/"  target="_new">Practical Software Configuration Management</a> </li>
      <li><a href="http://cvsbook.red-bean.com/" target="_new">Open Source Development with CVS</a> (online chapters version)</li>
     </ul>

<p>

<hr noshade size=1>
<a name="cvsclients"></a><span class="InputHeader">CVS Clients</span>
     <ul>
     <li><a
      href="http://www.cyclic.com</UL></ul>m/downloads.html" target="_new">Command line clients for many systems</a></li>

      <li><a href="http://www.cvsgui.org/download.html" target="_new">WinCVS: a Windows CVS client</a></li>

      <li><a href="http://www.jcvs.org/" target="_new">jCVS: a Java CVS client</a></li>

      <li><a href="http://cervisia.sourceforge.net" target="_new">Cervisia: a KDE CVS Client</a></li>
     </ul>
<p>

<hr noshade size=1>
<a href="ProjectSource.html">Back to Project Source help</a><br>
<a href="/servlets/HelpTOC">Back to main Help index</a></p></span>


</span> 
</body>
</html>
@


1.5.6.2
log
@fixed broken link.
Issue number:
Obtained from:
Submitted by:
Reviewed by:
@
text
@d116 1
a116 1
      href="http://www.cvshome.org/downloads.html" target="_new">Command line clients for many systems</a></li>
@


1.4
log
@index revisions and other general html edits
@
text
@d56 1
a56 1
You can also find further, more specific information in this site's three-part CVS tool document, <A HREF="ddUsingCVS_command-line.html">Using command-line CVS</A> or <A HREF="ddUsingWinCvs.htlm">Using WinCvs</A>.
@


1.3
log
@added <title> tags to all files
@
text
@d3 1
a3 3

<TITLE>Source Code Version Control: CVS</TITLE>

d8 2
a9 6
    <TD class="Header" nowrap>Source code version control: CVS</TD>  
  </TR>
</TABLE>
<TABLE BORDER="0" CELLSPACING="2" CELLPADDING="2" BORDER="0" width="100%">
  <TR>
    <TD class="PlainText">
d12 19
a30 8
  <dl>
        <dt><A HREF="#aboutcvs">About CVS</A></dt>
        <dd><A HREF="ddCVS_cvsprimer.html">A version control primer (basic concepts)</A>
        <dt><A HREF="#accesscvs">Accessing a project's CVS repository</A></dt>
        <dd><A HREF="ddUsingCVS_command-line.html">Using command-line CVS to access project source files</a><br> 
        <dd><A HREF="ddSourceBrowse.html">Source code browsing</A></dd>
        <dt><A HREF="#morecvsdoc">Further CVS documentation</A></dt>
  </dl>
d32 2
a33 2

      <P><span class="InputHeader"><A NAME="aboutcvs">About CVS</A></span>
d38 1
a38 1
<LI>The use of file merging rather than locking. File locking prohibits other developers from accessing a file when someone else has checked it out. CVS allows a multiple check-outs of a single file, and then combines all the changes.
d40 1
a40 1
<LI>Remote access to source code file repositories. Developers can obtain and modify project files from virtually anywhere.
d43 1
a43 1
     <P>CVS is a client-server system. The CVS repository is maintained on a web server; clients run on users' machines and connect to the server via the Internet. Clients are available for nearly all platforms including: UNIX, Windows, Macintosh, and any Java-based platform.
d46 1
a46 1
      <span class="InputHeader">CVS allows you to:</span>
d49 2
a50 2
        <LI>View differences between versions</LI>
        <LI>View change log comments</LI>
d52 23
a74 1
        <LI>Do many other tasks; see links below</LI>
d76 20
d97 1
a97 9
      <P><span class="InputHeader"><A NAME="accesscvs">Accessing your project's CVS repository</A></span>
      <P>For instructions on using CVS for a specific project: 
     <OL>
       <LI>From your Project Home page, click on Source Code in the project menu
       <LI>Choose whether to download source code archives, browse the CVS repository, or to  of how to checkout CVS project/module files, which includes the location of your project's repository (CVSROOT).
       </OL>  
     <BLOCKQUOTE>
      <P>For command-line access to the CVS source code repository, use the following CVSROOT: <P>
      <b>:pserver:anoncvs@@cvs.PROJECT_NAME.DOMAIN.com:/home/MAIN_CVS_DIR</b></P>
d99 1
a99 1
       <P>You may use the login "anoncvs" with password "anoncvs" to gain read-only CVS access. If you have been given "write" access to the CVS repository, then replace "anoncvs" with your own login (e.g., "mylogin@@cvs.PROJECT_NAME.DOMAIN.com") and use your own user password.</P>
d101 2
a102 2
       <P>Read the "source/CVS" page for each project and/or component to learn how the source code is organized into CVS modules. For example, to get the source code for a module ("MODULE_NAME") in your project ("PROJECT_NAME"), you should checkout "MODULE_NAME/PROJECT_NAME". This is the top-level module containing the entire source code tree for that particular module. Other modules may contain the documentation and web site files associated with this module.
	 </BLOCKQUOTE>
d104 1
a104 1
    <span class="InputHeader"><A NAME="morecvsdoc">Further CVS Documentation</A> </span>    
d106 3
a108 1
      <LI><A href="http://www.gnu.org/manual/cvs/index.html" target=_new>CVS Manual</A></LI>
d110 1
a110 6
      <LI><A href="http://www.cyclic.com/" target=_new>CVS Home Page at Cyclic</A></LI>

      <LI><A href="http://www.loria.fr/~molli/cvs-index.html" target=_new>Pascal Molli's CVS page</A></LI>

      <LI><A href="http://dmoz.org/Computers/Software/Configuration_Management/Tools/CVS/" target=_new>CVS Page on Dmoz</A></LI>
     </UL>
d112 2
a113 1
     <span class="InputHeader">CVS Clients</span>
d116 1
a116 1
      HREF="http://www.cvshome.org/downloads.html" target="_new">Command line clients for many systems</A></LI>
d118 1
a118 1
      <LI><A HREF="http://www.wincvs.org/" target="_new">WinCVS: a Windows CVS client</A></LI>
d120 1
a120 1
      <LI><A HREF="http://www.jcvs.org/" target="_new">jCVS: a Java CVS client</A></LI>
d122 1
a122 1
      <LI><A HREF="http://cervisia.sourceforge.net" target="_new">Cervisia: a KDE CVS Client</A></LI>
d124 1
d126 3
a128 5
     <span class="InputHeader">CVS Books</span>
     <UL>
      <LI><A HREF="http://www.amazon.com/exec/obidos/ISBN=0132408546/cyclicsoftwareA/"  target="_new">Practical Software Configuration Management</A> </LI>
      <LI><A HREF="http://cvsbook.red-bean.com/" target="_new">Open Source Development with CVS (many chapters free online)</A></LI>
     </UL>
a129 2
<HR noShade SIZE=1>
<a href="Help.html">Back to main Help index</a></p></span>
a130 1
    </TD>
@


1.2
log
@removed window's nasty line breaks, and corrected more links in HelpBox files
PR:
Obtained from:
Submitted by:
Reviewed by:
@
text
@d1 7
d100 2
@


1.1
log
@new and revised help documentation for v1.0
@
text
@d1 92
a92 92
<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
  <TR>
    <TD class="Header" nowrap>Source code version control: CVS</TD>  
  </TR>
</TABLE>
<TABLE BORDER="0" CELLSPACING="2" CELLPADDING="2" BORDER="0" width="100%">
  <TR>
    <TD class="PlainText">
      <P>

  <dl>
        <dt><A HREF="#aboutcvs">About CVS</A></dt>
        <dd><A HREF="ddCVS_cvsprimer.html">A version control primer (basic concepts)</A>
        <dt><A HREF="#accesscvs">Accessing a project's CVS repository</A></dt>
        <dd><A HREF="ddUsingCVS_command-line.html">Using command-line CVS to access project source files</a><br> 
        <dd><A HREF="ddSourceBrowse.html">Source code browsing</A></dd>
        <dt><A HREF="#morecvsdoc">Further CVS documentation</A></dt>
  </dl>


      <P><span class="InputHeader"><A NAME="aboutcvs">About CVS</A></span>

      <P>The Concurrent Versions System (CVS) is a version control system for keeping track of all modifications to project source code files. CVS is widely used in both open source and proprietary software development projects, and is generally considered to be the best freely available, full-featured version control tool. Two special features make CVS particularly suited to collaborative development across the Internet: 

<OL>
<LI>The use of file merging rather than locking. File locking prohibits other developers from accessing a file when someone else has checked it out. CVS allows a multiple check-outs of a single file, and then combines all the changes.
<P>
<LI>Remote access to source code file repositories. Developers can obtain and modify project files from virtually anywhere.
</OL>

     <P>CVS is a client-server system. The CVS repository is maintained on a web server; clients run on users' machines and connect to the server via the Internet. Clients are available for nearly all platforms including: UNIX, Windows, Macintosh, and any Java-based platform.
     <P>

      <span class="InputHeader">CVS allows you to:</span>
      <UL>
        <LI>Check out source files and directories</LI>
        <LI>View differences between versions</LI>
        <LI>View change log comments</LI>
        <LI>Commit changes made in your local copy of the source files to the main source code repository</LI>
        <LI>Do many other tasks; see links below</LI>
      </UL>

      <P><span class="InputHeader"><A NAME="accesscvs">Accessing your project's CVS repository</A></span>
      <P>For instructions on using CVS for a specific project: 
     <OL>
       <LI>From your Project Home page, click on Source Code in the project menu
       <LI>Choose whether to download source code archives, browse the CVS repository, or to  of how to checkout CVS project/module files, which includes the location of your project's repository (CVSROOT).
       </OL>  
     <BLOCKQUOTE>
      <P>For command-line access to the CVS source code repository, use the following CVSROOT: <P>
      <b>:pserver:anoncvs@@cvs.PROJECT_NAME.DOMAIN.com:/home/MAIN_CVS_DIR</b></P>

       <P>You may use the login "anoncvs" with password "anoncvs" to gain read-only CVS access. If you have been given "write" access to the CVS repository, then replace "anoncvs" with your own login (e.g., "mylogin@@cvs.PROJECT_NAME.DOMAIN.com") and use your own user password.</P>

       <P>Read the "source/CVS" page for each project and/or component to learn how the source code is organized into CVS modules. For example, to get the source code for a module ("MODULE_NAME") in your project ("PROJECT_NAME"), you should checkout "MODULE_NAME/PROJECT_NAME". This is the top-level module containing the entire source code tree for that particular module. Other modules may contain the documentation and web site files associated with this module.
	 </BLOCKQUOTE>

    <span class="InputHeader"><A NAME="morecvsdoc">Further CVS Documentation</A> </span>    
     <UL>
      <LI><A href="http://www.gnu.org/manual/cvs/index.html" target=_new>CVS Manual</A></LI>

      <LI><A href="http://www.cyclic.com/" target=_new>CVS Home Page at Cyclic</A></LI>

      <LI><A href="http://www.loria.fr/~molli/cvs-index.html" target=_new>Pascal Molli's CVS page</A></LI>

      <LI><A href="http://dmoz.org/Computers/Software/Configuration_Management/Tools/CVS/" target=_new>CVS Page on Dmoz</A></LI>
     </UL>

     <span class="InputHeader">CVS Clients</span>
     <UL>
     <LI><A
      HREF="http://www.cvshome.org/downloads.html" target="_new">Command line clients for many systems</A></LI>

      <LI><A HREF="http://www.wincvs.org/" target="_new">WinCVS: a Windows CVS client</A></LI>

      <LI><A HREF="http://www.jcvs.org/" target="_new">jCVS: a Java CVS client</A></LI>

      <LI><A HREF="http://cervisia.sourceforge.net" target="_new">Cervisia: a KDE CVS Client</A></LI>
     </UL>

     <span class="InputHeader">CVS Books</span>
     <UL>
      <LI><A HREF="http://www.amazon.com/exec/obidos/ISBN=0132408546/cyclicsoftwareA/"  target="_new">Practical Software Configuration Management</A> </LI>
      <LI><A HREF="http://cvsbook.red-bean.com/" target="_new">Open Source Development with CVS (many chapters free online)</A></LI>
     </UL>

<HR noShade SIZE=1>
<a href="Help.html">Back to main Help index</a></p></span>

    </TD>
  </TR>
</TABLE>
@

