head	1.16;
access;
symbols
	TIGRIS_1_1_0RC2:1.9.6.3
	TIGRIS_1_1_0RC1:1.9.6.3
	TIGRIS_1_1:1.9.6.3.0.2
	TIGRIS_1_0_8:1.9.6.1
	TIGRIS_1_0_8RC3:1.9.6.1
	TIGRIS_1_0_8RC2:1.9.6.1
	TIGRIS_1_0_8RC1:1.9.6.1
	TIGRIS_1_0_7:1.9.6.1
	TIGRIS_1_0_7RC3:1.9.6.1
	TIGRIS_1_0_7RC2:1.9.6.1
	TIGRIS_1_0_7RC1:1.9.6.1
	TIGRIS_1_0_6:1.9.6.1
	TIGRIS_1_0_6RC5:1.9.6.1
	TIGRIS_1_0_6RC4:1.9.6.1
	TIGRIS_1_0_6RC3:1.9
	TIGRIS_1_0_6RC2:1.9
	TIGRIS_1_0_6RC1:1.9
	TIGRIS_1_0_5:1.9
	TIGRIS_1_0_5RC6:1.9
	TIGRIS_1_0_5RC5:1.9
	TIGRIS_1_0_5RC4:1.9
	TIGRIS_1_0_5RC3:1.9
	TIGRIS_1_0_5RC2:1.9
	TIGRIS_1_0_5RC1:1.9
	TIGRIS_1_0_4:1.9
	TIGRIS_1_0_3:1.9
	TIGRIS_1_0_2:1.9
	TIGRIS_1_0_1:1.9
	TIGRIS_1_0:1.9.0.6
	TIGRIS_1_0_0:1.9
	TIGRIS_1_0_0_RC1:1.9.0.2;
locks; strict;
comment	@# @;


1.16
date	2001.08.23.22.59.14;	author tberry;	state Exp;
branches;
next	1.15;

1.15
date	2001.07.26.22.46.48;	author tberry;	state Exp;
branches;
next	1.14;

1.14
date	2001.06.27.22.57.39;	author lori;	state Exp;
branches;
next	1.13;

1.13
date	2001.06.21.07.07.40;	author jefflove;	state Exp;
branches;
next	1.12;

1.12
date	2001.06.11.03.14.33;	author jefflove;	state Exp;
branches;
next	1.11;

1.11
date	2001.06.04.21.04.10;	author lori;	state Exp;
branches;
next	1.10;

1.10
date	2001.05.09.16.12.48;	author lori;	state Exp;
branches;
next	1.9;

1.9
date	2001.03.15.03.31.12;	author lori;	state Exp;
branches
	1.9.6.1;
next	1.8;

1.8
date	2001.03.12.23.31.55;	author lori;	state Exp;
branches;
next	1.7;

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

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

1.5
date	2001.02.11.18.29.47;	author jrobbins;	state Exp;
branches;
next	1.4;

1.4
date	2001.02.09.01.04.13;	author susank;	state Exp;
branches;
next	1.3;

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

1.2
date	2001.02.05.16.41.58;	author lori;	state Exp;
branches;
next	1.1;

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

1.9.6.1
date	2001.06.13.00.36.34;	author lori;	state Exp;
branches;
next	1.9.6.2;

1.9.6.2
date	2001.07.17.21.14.26;	author tberry;	state Exp;
branches;
next	1.9.6.3;

1.9.6.3
date	2001.08.01.19.23.58;	author csjank;	state Exp;
branches;
next	;


desc
@@


1.16
log
@added in index pieces.
Issue number:
Obtained from:
Submitted by:
Reviewed by:
@
text
@<div class="docs" id="projectsource">
   <h2>Project Source</h2>

   <div class="toc">
    <h3>Project resources for members: Index</h3>

    <ul> <li>
     <a href="Learning.html">Learning about projects</a> </li>
     <li>
      <a href="ProjectMemberResources.html">Project resources for members</a> 

        <ul>
          <li><a href="ProjectHome.html">Project Home Page</a></li>
          <li><a href="ProjectNews.html">Project News</a></li>
          <li><a href="ProjectMemberList.html">Project Members</a></li>
          <li><a href="ProjectMail.html">Project Mailing Lists</a></li>
          <li><a href="ProjectDocuments.html">Project Documentation</a></li>
          <li> <strong>You are here:</strong> Project Source Code 
            <ul>
              <li><a href="#browsesource">Browsing a project's source repository 
                with CVSWeb</a></li>
              <li><a href="#getsource">Getting your working copy of project source 
                files</a></li>
              <li><a href="#cvsclients">CVS client downloads</a></li>
            </ul>
          </li>
          <li><a href="ProjectIssues.html">Project Issues</a></li>
        </ul>
     </li><li><a href="hostedtools.html">Hosted tools</a></li>
      <li><a href="ProjectAdd.html">Creating a new project</a></li>
    </ul>

    <h3>CVS tool documentation</h3>

    <ul>
     <li><a href="ddCVS.html">About CVS versioning control</a></li>

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

     <li><a href="ddUsingWinCvs.html">Site guide for using WinCVS</a></li>

     <li><a href="ddUsingCVS_command-line.html">Site guide for using command line CVS</a></li>
    </ul>
   </div>

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

   <h3><a id="browsesource" name="browsesource">Browsing a project's source repository with CVSWeb</a></h3>

   <p>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").</p>

   <ol>
    <li>From your Project Home page, click on Source in the Project Resources toolbar.</li>

    <li>Click on "Browse project source files" to access the project's source repository through CVSWeb.</li>
   </ol>

   <p>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.</p>

   <div class="courtesylinks">
    <p><a href="ddSourceBrowse.html">More information about CVSWeb</a></p>
   </div>

   <h3><a id="getsource" name="getsource">Getting your working copy of project source files</a></h3>

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

   <p>A <i>working copy</i> 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.</p>

   <p>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.</p>

   <h3><a id="cvsclients" name="cvsclients">CVS client downloads</a></h3>

   <ul>
    <li><a href="http://www.cyclic.com/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="/servlets/HelpTOC">Back to main Help index</a></p>
   </div>
  </div>
 


@


1.15
log
@removed link to ProjectDownload.  This feature no longer exists.

Issue number:
Obtained from:
Submitted by:
Reviewed by:
@
text
@d1 1
a1 1
  <div class="docs" id="projectsource">
d7 2
a8 1
    <ul>
d29 2
a30 1
     </li>
@


1.14
log
@removed space in link to ProjectSource servlet
@
text
@a10 16
      <ul>
       <li><a href="ProjectHome.html">Project Home Page</a></li>

       <li><a href="ProjectNews.html">Project News</a></li>

       <li><a href="ProjectDownload.html">Project Download</a></li>

       <li><a href="ProjectMemberList.html">Project Members</a></li>

       <li><a href="ProjectMail.html">Project Mailing Lists</a></li>

       <li><a href="ProjectDocuments.html">Project Documentation</a></li>

       <li>
        <strong>You are here:</strong> Project Source Code 

d12 15
a26 5
         <li><a href="#browsesource">Browsing a project's source repository with CVSWeb</a></li>

         <li><a href="#getsource">Getting your working copy of project source files</a></li>

         <li><a href="#cvsclients">CVS client downloads</a></li>
a27 4
       </li>

       <li><a href="ProjectIssues.html">Project Issues</a></li>
      </ul>
@


1.13
log
@html usage revision
@
text
@d76 1
a76 1
   <p>To obtain (or "check out") your own working copy of project files, step-by-step instructions are included on the <a href="/templates/org/tigris/helm/project/Project%20Source.wm">Project Source page</a> for both command line CVS and WinCvs. These instructions also show the exact cvsroot to set for the current project. The <i>cvsroot</i> points to the server location of the project's source repository.</p>
@


1.12
log
@extensive markup rework - first pass toward house xhtmlification
@
text
@d1 2
a2 6
<!DOCTYPE html PUBLIC "-//CollabNet//DTD XHTML 1.0 Transitional//EN"
"http://collabnet.com/dtds/collabnet_transitional_10.dtd">
<html>
 <head>
  <title>Project Resources for Members</title>
 </head>
d4 2
a5 3
 <body>
  <div class="docs" id="projectsource">
<h2>Project Source</h2>
d7 3
a9 3
  <p><b>Project resources for members: Index</b></p>
   <dl>
    <dt><a href="ProjectMemberResources.html">Project resources for members</a></dt>
d11 2
a12 1
    <dd><a href="ProjectHome.html">Project Home Page</a></dd>
d14 1
a14 1
    <dd><a href="ProjectNews.html">Project News</a></dd>
d16 1
a16 1
    <dd><a href="ProjectDownload.html">Project Download</a></dd>
d18 1
a18 1
    <dd><a href="ProjectMemberList.html">Project Members</a></dd>
d20 1
a20 1
    <dd><a href="ProjectMail.html">Project Mailing Lists</a></dd>
d22 1
a22 1
    <dd><a href="ProjectDocuments.html">Project Documentation</a></dd>
d24 2
a25 2
    <dd>
     <b>You are here: Project Source Code</b>
d27 2
a28 2
     <ul>
      <li><b><a href="#browsesource">Browsing a project's source repository with CVSWeb</a></b></li>
d30 1
a30 1
      <li><b><a href="#getsource">Getting your working copy of project source files</a></b></li>
d32 3
a34 3
      <li><b><a href="#cvsclients">CVS client downloads</a></b></li>
     </ul>
    </dd>
d36 4
a39 1
    <dd><a href="ProjectIssues.html">Project Issues</a></dd>
d41 1
d43 2
a44 5
   </dl>
<div class="courtesylinks">
<a href="/servlets/HelpTOC">Back to main Help index</a>
</div>
  <p><b>CVS tool documentation</b></p>
d46 1
a46 3
  <dl>
   <dt><a href="ddCVS.html">About CVS versioning control</a><br />
   </dt>
d48 1
a48 1
   <dt><a href="ddCVS_cvsglossary.html">A version control glossary</a></dt>
d50 3
a52 2
   <dt><a href="ddUsingWinCvs.html">Site guide for using WinCVS</a><br />
   </dt>
d54 3
a56 4
   <dt><a href="ddUsingCVS_command-line.html">Site guide for using command line CVS</a></dt>
  </dl>
  
  <h3><a id="browsesource" name="browsesource">Browsing a project's source repository with CVSWeb</a></h3> 
d58 1
a58 1
  <p>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").</p>
d60 1
a60 1
  
d62 2
a63 3
  <ol>
   <li>
    From your Project Home page, click on Source in the Project Resources toolbar. 
d65 2
a66 2
    
   </li>
d68 1
a68 2
   <li>Click on "Browse project source files" to access the project's source repository through CVSWeb.</li>
  </ol>
d70 3
a72 1
  <p>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.</p>
d74 1
a74 3
  <p><a href="ddSourceBrowse.html">More information about CVSWeb</a></p>
  
  <h3><a id="getsource" name="getsource">Getting your working copy of project source files</a></h3> 
d76 1
a76 1
  <p>To obtain (or "check out") your own working copy of project files, step-by-step instructions are included on the <a href="/templates/org/tigris/helm/project/Project%20Source.wm">Project Source page</a> for both command line CVS and WinCvs. These instructions also show the exact cvsroot to set for the current project. The <i>cvsroot</i> points to the server location of the project's source repository.</p>
d78 1
a78 1
  <p>A <i>working copy</i> 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.</p>
d80 1
a80 1
  <p>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.</p>
d82 1
a82 3
  
  
  <h3><a id="cvsclients" name="cvsclients">CVS client downloads</a></h3> 
d84 2
a85 2
  <ul>
   <li><a href="http://www.cyclic.com/downloads.html">Command line clients for many systems</a></li>
d87 1
a87 1
   <li><a href="http://www.cvsgui.org/download.html">WinCVS: a Windows CVS client</a></li>
d89 1
a89 1
   <li><a href="http://www.jcvs.org/">jCVS: a Java CVS client</a></li>
d91 2
a92 2
   <li><a href="http://cervisia.sourceforge.net">Cervisia: a KDE CVS Client</a></li>
  </ul>
d94 5
a98 6
  
  
<div class="courtesylinks"><a href="/servlets/HelpTOC">Back to main Help index</a></div> 
 </div>
</body>
</html>
@


1.11
log
@fixed broken index link to Project Members help doc; issue 4348
@
text
@d1 2
d4 3
a6 1
<head>
d8 3
a10 1
<title>Project Resources for Members</title>
d12 18
a29 2
</head>
<body>
a30 64
<p>
    <span class="Header" nowrap>Project Source</span>  
 <p>

<span class="PlainText"><b>Project resources for members: Index</b>
<p>
 <ul><dl>
        <dt><a href="ProjectMemberResources.html">Project resources for members</a>
        <dd><a href="ProjectHome.html">Project Home Page</a>
        <dd><a href="ProjectNews.html">Project News</a>
        <dd><a href="ProjectDownload.html">Project Download</a>
	<dd><a href="ProjectMemberList.html">Project Members</a>
        <dd><a href="ProjectMail.html">Project Mailing Lists</a>
	<dd><a href="ProjectDocuments.html">Project Documentation</a>
        <dd><b>You are here: Project Source Code
			<ul>
			<li><a href="#browsesource">Browsing a project's source repository with CVSWeb</a>
			<li><a href="#getsource">Getting your working copy of project source files</a>
			<li><a href="#cvsclients">CVS client downloads</a>
			</ul></b>
        <dd><a href="ProjectIssues.html">Project Issues</a>
<dt><a href="/servlets/HelpTOC">Back to main Help index</a>
  </dl>
</ul>
<p>
<span class="PlainText">
<b>CVS tool documentation</b>
	<dl>
	<dt><a href="ddCVS.html">About CVS versioning control</a><br>
	<dt><a href="ddCVS_cvsglossary.html">A version control glossary</a>
	<dt><a href="ddUsingWinCvs.html">Site guide for using WinCVS</a><br>
	<dt><a href="ddUsingCVS_command-line.html">Site guide for using command line CVS </a>
</dl>
<p>
<hr noshade size=1>
<span class="InputHeader"><a name="browsesource"></a>Browsing a project's source repository with CVSWeb</span>
<span class="PlainText">
<p>
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").
<p>
      <ol>
       <li>From your Project Home page, click on Source in the Project Resources toolbar.
      <p>
       <li>Click on "Browse project source files" to access the project's source repository through CVSWeb.
	  </ol>
<p>
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.

<p><a href="ddSourceBrowse.html">More information about CVSWeb</a>

<p>
<hr noshade size=1>
<a name="getsource"></a><span class="InputHeader">Getting your working copy of project source files</span>
<p>
To obtain (or &quot;check out&quot) your own working copy of project files, step-by-step instructions are included on the <a href="/templates/org/tigris/helm/project/Project Source.wm">Project Source page</a> for both command line CVS and WinCvs. These instructions also show the exact cvsroot to set for the current project. The <i>cvsroot</i> points to the server location of the project's source repository.
<p>
A <i>working copy</i> 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. 
<p>
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.
<p>

<p>
<hr noshade size=1>
<span class="InputHeader"><a name="cvsclients">CVS client downloads</a></span>
d32 1
a32 2
     <li><a
      href="http://www.cyclic.com/downloads.html" target="_new">Command line clients for many systems</a></li>
d34 1
a34 1
      <li><a href="http://www.cvsgui.org/download.html" target="_new">WinCVS: a Windows CVS client</a></li>
d36 3
a38 1
      <li><a href="http://www.jcvs.org/" target="_new">jCVS: a Java CVS client</a></li>
d40 1
a40 3
      <li><a href="http://cervisia.sourceforge.net" target="_new">Cervisia: a KDE CVS Client</a></li>
     </ul>
<p>
d43 2
a44 1
<hr noshade size=1>
d46 18
d65 1
a65 1
</span>
d67 40
d109 2
@


1.10
log
@added paragraph about ability to browse deleted source files depending upon CVSWeb's hide/don't hide config
@
text
@d20 1
a20 1
		<dd><a href="ProjectMembers.html">Project Members</a>
d22 1
a22 1
		<dd><a href="ProjectDocuments.html">Project Documentation</a>
@


1.9
log
@added cvsroot info, other minor edits
@
text
@d4 1
a4 1
<title>Project Resouces for Members</title>
d25 1
a25 1
			<li><a href="#browsesource">Browsing a project's source repository</a>
d44 1
a44 1
<span class="InputHeader"><a name="browsesource"></a>Browsing a project's source repository</span>
d54 3
@


1.9.6.1
log
@updating branch with latest help files
@
text
@d4 1
a4 1
<title>Project Resources for Members</title>
d20 1
a20 1
	<dd><a href="ProjectMemberList.html">Project Members</a>
d22 1
a22 1
	<dd><a href="ProjectDocuments.html">Project Documentation</a>
d25 1
a25 1
			<li><a href="#browsesource">Browsing a project's source repository with CVSWeb</a>
d44 1
a44 1
<span class="InputHeader"><a name="browsesource"></a>Browsing a project's source repository with CVSWeb</span>
a53 3
<p>
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.

@


1.9.6.2
log
@took space out of link to projectsource.wm
Issue number:
Obtained from:
Submitted by:
Reviewed by:
@
text
@d63 1
a63 1
To obtain (or &quot;check out&quot) your own working copy of project files, step-by-step instructions are included on the <a href="/templates/org/tigris/helm/project/ProjectSource.wm">Project Source page</a> for both command line CVS and WinCvs. These instructions also show the exact cvsroot to set for the current project. The <i>cvsroot</i> points to the server location of the project's source repository.
@


1.9.6.3
log
@fixed broken link to ProjectSource
Issue number:
Obtained from:
Submitted by:
Reviewed by:
@
text
@d63 1
a63 1
To obtain (or &quot;check out&quot) your own working copy of project files, step-by-step instructions are included on the <a href="/templates/org/tigris/helm/project/ProjectSource">Project Source page</a> for both command line CVS and WinCvs. These instructions also show the exact cvsroot to set for the current project. The <i>cvsroot</i> points to the server location of the project's source repository.
@


1.8
log
@updating version to reflect latest content changes
@
text
@d60 1
a60 1
To obtain (or &quot;check out&quot) your own working copy of project files, step-by-step instructions are included on the <a href="/templates/org/tigris/helm/project/Project Source.wm">Project Source page</a> for both command line CVS and WinCvs.
a86 2
</tr>
</table>
@


1.7
log
@content edits and index revisions
@
text
@d1 2
a2 2
<HTML>
<HEAD>
d4 1
a4 1
<TITLE>Project Resouces for Members</TITLE>
d6 41
a46 41
</HEAD>
<BODY>
<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
  <TR>
<P>
    <SPAN CLASS="Header" NOWRAP>Project Source</SPAN>  
 <P>

<SPAN CLASS="PlainText"><B>Project resources for members: Index</B>
<P>
 <UL><DL>
        <DT><A HREF="ProjectMemberResources.html">Project resources for members</A>
        <DD><A HREF="ProjectHome.html">Project Home Page</A>
        <DD><A HREF="ProjectNews.html">Project News</A>
        <DD><A HREF="ProjectDownload.html">Project Download</A>
		<DD><A HREF="ProjectMembers.html">Project Members</A>
        <DD><A HREF="ProjectMail.html">Project Mailing Lists</A>
        <DD><B>You are here: Project Source Code</B>
			<UL>
			<LI><A HREF="#browsesource">Browsing a project's source repository</A>
			<LI><A HREF="#getsource">Getting your working copy of project source files</A>
			<LI><A HREF="#cvsclients">CVS client downloads</A>
			</UL>
        <DD><A HREF="ProjectIssues.html">Project Issues</A>
<DT><A HREF="/servlets/HelpTOC">Back to main Help index</A>
  </DL>
</UL>
<P>
<SPAN CLASS="PlainText">
<B>CVS tool documentation</B>
	<DL>
	<DT><A HREF="ddCVS.html">About CVS versioning control</A><BR>
	<DT><A HREF="ddCVS_cvsglossary.html">A version control glossary</A>
	<DT><A HREF="ddUsingWinCvs.html">Site guide for using WinCVS</A><BR>
	<DT><A HREF="ddUsingCVS_command-line.html">Site guide for using command line CVS </A>
</DL>
<P>
<HR NOSHADE SIZE=1>
<SPAN CLASS="InputHeader"><A NAME="browsesource"></A>Browsing a project's source repository</SPAN>
<SPAN CLASS="PlainText">
<P>
d48 16
a63 16
<P>
      <OL>
       <LI>From your Project Home page, click on Source in the Project Resources toolbar.
      <P>
       <LI>Click on "Browse project source files" to access the project's source repository through CVSWeb.
	  </OL>
<P><A HREF="ddSourceBrowse.html">More information about CVSWeb</A>

<P>
<HR NOSHADE SIZE=1>
<A NAME="getsource"></A><SPAN CLASS="InputHeader">Getting your working copy of project source files</SPAN>
<P>
To obtain (or &quot;check out&quot) your own working copy of project files, step-by-step instructions are included on the <A HREF="/templates/org/tigris/helm/project/Project Source.wm">Project Source page</A> for both command line CVS and WinCvs.
<P>
A <I>working copy</I> 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. 
<P>
d65 1
a65 1
<P>
d67 6
a72 6
<P>
<HR NOSHADE SIZE=1>
<SPAN CLASS="InputHeader"><A NAME="cvsclients">CVS client downloads</A></SPAN>
     <UL>
     <LI><A
      HREF="http://www.cyclic.com/downloads.html" TARGET="_new">Command line clients for many systems</A></LI>
d74 1
a74 1
      <LI><A HREF="http://www.cvsgui.org/download.html" TARGET="_new">WinCVS: a Windows CVS client</A></LI>
d76 1
a76 1
      <LI><A HREF="http://www.jcvs.org/" TARGET="_new">jCVS: a Java CVS client</A></LI>
d78 3
a80 3
      <LI><A HREF="http://cervisia.sourceforge.net" TARGET="_new">Cervisia: a KDE CVS Client</A></LI>
     </UL>
<P>
d83 2
a84 2
<HR NOSHADE SIZE=1>
<A HREF="/servlets/HelpTOC">Back to main Help index</A>
d86 3
a88 3
</SPAN>
</TR>
</TABLE>
d90 2
a91 2
</BODY>
</HTML>
@


1.6
log
@revised doc index format
@
text
@d35 1
a35 1
<B>Other version control documentation available on this site</B>
d38 1
a38 1
	<DT><A HREF="ddCVS_cvsprimer.html">A version control primer (basic concepts)</A>
d40 1
a40 1
	<DT><A HREF="ddUsingCVS.html">Site guide for using command line CVS </A>
d74 1
a74 1
      <LI><A HREF="http://www.wincvs.org/download.html" TARGET="_new">WinCVS: a Windows CVS client</A></LI>
@


1.5
log
@added <title> tags to all files
@
text
@a9 1
<SPAN CLASS="PlainText">Project resources for members</SPAN>
d14 2
a15 1
<SPAN CLASS="PlainText">
d17 2
a18 2
        <DT><A HREF="ProjectMemberResources.html">Project resources for members</A></A></DT>
        <DD><A HREF="ProjectHomePage.html">Project Home Page</A>
@


1.4
log
@corrected "back to main Help" link... missing leading / made it tack on the filepath to the preexisting one
PR:
Obtained from:
Submitted by:
Reviewed by:
@
text
@d1 7
d90 2
@


1.3
log
@removed window's nasty line breaks, and corrected more links in HelpBox files
PR:
Obtained from:
Submitted by:
Reviewed by:
@
text
@d77 1
a77 1
<A HREF="servlets/HelpTOC">Back to main Help index</A>
@


1.2
log
@updated for new help format
@
text
@d1 82
a82 82
<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
  <TR>
<SPAN CLASS="PlainText">Project resources for members</SPAN>
<P>
    <SPAN CLASS="Header" NOWRAP>Project Source</SPAN>  
 <P>

<SPAN CLASS="PlainText">
 <UL><DL>
        <DT><A HREF="ProjectMemberResources.html">Project resources for members</A></A></DT>
        <DD><A HREF="ProjectHomePage.html">Project Home Page</A>
        <DD><A HREF="ProjectNews.html">Project News</A>
        <DD><A HREF="ProjectDownload.html">Project Download</A>
		<DD><A HREF="ProjectMembers.html">Project Members</A>
        <DD><A HREF="ProjectMail.html">Project Mailing Lists</A>
        <DD><B>You are here: Project Source Code</B>
			<UL>
			<LI><A HREF="#browsesource">Browsing a project's source repository</A>
			<LI><A HREF="getsource">Getting your working copy of project source files</A>
			<LI><A HREF="#cvsclients">CVS client downloads</A>
			</UL>
        <DD><A HREF="ProjectIssues.html">Project Issues</A>
<DT><A HREF="/servlets/HelpTOC">Back to main Help index</A>
  </DL>
</UL>
<P>
<SPAN CLASS="PlainText">
<B>Other version control documentation available on this site</B>
	<DL>
	<DT><A HREF="ddCVS.html">About CVS versioning control</A><BR>
	<DT><A HREF="ddCVS_cvsprimer.html">A version control primer (basic concepts)</A>
	<DT><A HREF="ddUsingWinCvs.html">Site guide for using WinCVS</A><BR>
	<DT><A HREF="ddUsingCVS.html">Site guide for using command line CVS </A>
</DL>
<P>
<HR NOSHADE SIZE=1>
<SPAN CLASS="InputHeader"><A NAME="browsesource"></A>Browsing a project's source repository</SPAN>
<SPAN CLASS="PlainText">
<P>
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").
<P>
      <OL>
       <LI>From your Project Home page, click on Source in the Project Resources toolbar.
      <P>
       <LI>Click on "Browse project source files" to access the project's source repository through CVSWeb.
	  </OL>
<P><A HREF="ddSourceBrowse.html">More information about CVSWeb</A>

<P>
<HR NOSHADE SIZE=1>
<A NAME="getsource"></A><SPAN CLASS="InputHeader">Getting your working copy of project source files</SPAN>
<P>
To obtain (or &quot;check out&quot) your own working copy of project files, step-by-step instructions are included on the <A HREF="/templates/org/tigris/helm/project/Project Source.wm">Project Source page</A> for both command line CVS and WinCvs.
<P>
A <I>working copy</I> 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. 
<P>
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.
<P>

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

      <LI><A HREF="http://www.wincvs.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="servlets/HelpTOC">Back to main Help index</A>

</SPAN>
</TR>
</TABLE>

@


1.1
log
@new and revised help documentation for v1.0
@
text
@d3 22
a24 13
    <TD CLASS="Header" NOWRAP>Project Source</TD>  
  </TR>
</TABLE>

<TABLE BORDER="0" CELLSPACING="2" CELLPADDING="2" BORDER="0" WIDTH="100%">
  <TR>
    <TD CLASS="PlainText" VALIGN="top">
<DL>
<UL>
<DT><A HREF="#browsesource">Browsing a project's source repository</A>
<DT><A HREF="getsource">Getting your working copy of project source files</A>
<DT><A HREF="#otherdocs">Other CVS documentation available on this site</A>
<DT><A HREF="#cvsclients">CVS client downloads</A>
d26 8
d36 1
a36 1
<HR noShade SIZE=1>
d38 1
a38 1
<span class="PlainText">
d50 1
a50 1
<HR noShade SIZE=1>
d53 1
a53 1
To obtain (or &quot;check out&quot) 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.
d57 1
a57 1
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 you need to. Keep in mind, however, that files in the project repository continually change over time as to reflect other developer contributions as the project progresses. Tracking and assimilating all <I>contributed</I> changes in one central place is the purpose of CVS.
d59 1
a59 4
<HR noShade SIZE=1>
<A NAME="otherdocs"></A><SPAN CLASS="InputHeader">Other CVS documentation available on this site</SPAN>
<P>
For general information about CVS, see:
d61 2
a62 11
<A HREF="ddCVS.html">About CVS versioning control</A><BR>
<A HREF="ddCVS_cvsprimer.html">A version control primer (basic concepts)</A>
<P>
For information about specific CVS commands essential to working and contributing to a project's source repository, see the following how-to documents:
<P>
<A HREF="ddCVS_UsingWinCvs.html">Using WinCVS to work with project source files</A><BR>
<A HREF="ddCVS_UsingCVS.html">Using command-line CVS to work with project source files</A><BR>
<A HREF="ddCVS_cvscontributing.html">Contributing changes with command-line CVS</A>
<P>
<HR noShade SIZE=1>
<span class="InputHeader"><A NAME="cvsclients">CVS client downloads</A></SPAN>
d65 1
a65 1
      HREF="http://www.cyclic.com/downloads.html" target="_new">Command line clients for many systems</A></LI>
d67 1
a67 1
      <LI><A HREF="http://www.wincvs.org/download.html" target="_new">WinCVS: a Windows CVS client</A></LI>
d69 1
a69 1
      <LI><A HREF="http://www.jcvs.org/" target="_new">jCVS: a Java CVS client</A></LI>
d71 1
a71 1
      <LI><A HREF="http://cervisia.sourceforge.net" target="_new">Cervisia: a KDE CVS Client</A></LI>
d76 2
a77 2
<HR noShade SIZE=1>
<a href="Help.html">Back to main Help index</a></p></span>
a79 2
</SPAN>
</TD>
@

