head	1.16;
access;
symbols
	TIGRIS_1_1_0RC2:1.13.6.1
	TIGRIS_1_1_0RC1:1.13.6.1
	TIGRIS_1_1:1.13.6.1.0.2
	TIGRIS_1_0_8:1.13.6.1
	TIGRIS_1_0_8RC3:1.13.6.1
	TIGRIS_1_0_8RC2:1.13.6.1
	TIGRIS_1_0_8RC1:1.13.6.1
	TIGRIS_1_0_7:1.13.6.1
	TIGRIS_1_0_7RC3:1.13.6.1
	TIGRIS_1_0_7RC2:1.13.6.1
	TIGRIS_1_0_7RC1:1.13.6.1
	TIGRIS_1_0_6:1.13.6.1
	TIGRIS_1_0_6RC5:1.13.6.1
	TIGRIS_1_0_6RC4:1.13.6.1
	TIGRIS_1_0_6RC3:1.13
	TIGRIS_1_0_6RC2:1.13
	TIGRIS_1_0_6RC1:1.13
	TIGRIS_1_0_5:1.13
	TIGRIS_1_0_5RC6:1.13
	TIGRIS_1_0_5RC5:1.13
	TIGRIS_1_0_5RC4:1.13
	TIGRIS_1_0_5RC3:1.13
	TIGRIS_1_0_5RC2:1.13
	TIGRIS_1_0_5RC1:1.13
	TIGRIS_1_0_4:1.13
	TIGRIS_1_0_3:1.13
	TIGRIS_1_0_2:1.13
	TIGRIS_1_0_1:1.13
	TIGRIS_1_0:1.13.0.6
	TIGRIS_1_0_0:1.13
	TIGRIS_1_0_0_RC1:1.13.0.2;
locks; strict;
comment	@# @;


1.16
date	2001.06.21.07.07.40;	author jefflove;	state Exp;
branches;
next	1.15;

1.15
date	2001.06.11.03.14.33;	author jefflove;	state Exp;
branches;
next	1.14;

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

1.13
date	2001.03.16.21.14.24;	author lori;	state Exp;
branches
	1.13.6.1;
next	1.12;

1.12
date	2001.03.14.19.10.50;	author lori;	state Exp;
branches;
next	1.11;

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

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

1.9
date	2001.03.10.01.32.36;	author tberry;	state Exp;
branches;
next	1.8;

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

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

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

1.5
date	2001.02.15.21.43.30;	author lori;	state Exp;
branches;
next	1.4;

1.4
date	2001.02.11.18.29.47;	author jrobbins;	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.37.35;	author lori;	state Exp;
branches;
next	1.1;

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

1.13.6.1
date	2001.06.13.00.35.41;	author lori;	state Exp;
branches;
next	;


desc
@@


1.16
log
@html usage revision
@
text
@  <div class="docs" id="projectowneredit">
   <h2>Editing and maintaining the Project Home page</h2>

   <div class="toc">
    <h3>Project help for project owner administration: Index</h3>

    <ul>
     <li>
      <a href="ProjectOwnerAdmin.html">Project owner administration</a> 

      <ul>
       <li>
        <strong>You are here:</strong> Editing and maintaining the Project Home page 

        <ul>
         <li><a href="#updatehome">Maintaining project information</a></li>

         <li><a href="#useindex">About the 'Use Project Home Page' option</a></li>

         <li><a href="#ownersmessage">Updating the owner's message</a></li>

         <li><a href="#aboutlists">About configuring project mailing lists</a></li>

         <li><a href="#aboutlocking">About project locking</a></li>
        </ul>
       </li>

       <li><a href="ProjectOwnerNews.html">Managing project site news</a></li>

       <li><a href="ProjectOwnerFiles.html">Managing project files</a></li>

       <li><a href="ProjectOwnerMembers.html">Adding project members and approving roles</a></li>

       <li><a href="ProjectOwnerMailingLists.html">Managing project mailing lists</a></li>

       <li><a href="ProjectOwnerDocuments.html">Managing project documentation</a></li>

       <li><a href="ProjectOwnerSource.html">Managing project source code</a></li>

       <li><a href="ProjectOwnerIssues.html">Tracking and managing project issues</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="updatehome" name="updatehome">Maintaining project information</a></h3>

   <p>The <strong>Project Home</strong> page is the entry point for all project users, members as well as potential contributors. The primary role of the <strong>Project Home</strong> page is to highlight the project's mission, primary goals, current status, and ongoing needs.</p>

   <p><strong>NOTE</strong>: For a good example of summarizing project goals and status, see the open source <a href="http://subversion.tigris.org/">Subversion project home page</a>.</p>

   <p>Project information can be modified through the <b>Administer Projects</b> page, accessed by one of the following methods:</p>

   <ul>
    <li>At first login, the home page has a <strong>My Projects</strong> link as well as an <strong>Admin</strong> link to the <strong>Project Edit</strong> page.</li>

    <li>Once you are on your <strong>Project Home</strong> page or other project pages, use the <strong>Admin</strong> link in the Project Resources tool bar at the top of every screen.</li>
   </ul>

   <p>The <strong>Project Home</strong> page has the following fields which are also part of the project creation process:</p>

   <ul>
    <li>Project Name</li>

    <li>Summary</li>

    <li>Description</li>

    <li>License</li>

    <li>Project Category.</li>
   </ul>

   <p>By clicking on the <strong>Edit this Project</strong> link you can modify the information in each of these fields. Because the description field accommodates html formatting and graphics, you can use this to customize and add information to your project home page.</p>

   <p>There are several additional fields in the <b>Administer Projects</b> page that do not appear during the project creation process:</p>

   <ul>
    <li>Message From the Owner(s)</li>

    <li>Edit this Project</li>

    <li>Request New Project Role</li>
   </ul>

   <h3><a id="useindex" name="useindex">About the 'Use Project Home Page' option</a></h3>

   <p>Your <b>Project Home</b> page by default displays the content that you entered in the Description field in the <b>Administer Project</b> page.</p>

   <p>Because some projects require more complex home pages, however, you have the option to store and display special home page content from a different file. The "Use Index" flag in the <b>Administer Project</b> page indicates that your project home page should display the contents of the "index.html" file instead of displaying description field information from the database. This file is located in:</p>

   <p>http://yourprojectname.this domain/www/index.html</p>

   <p>This file is part of the project's source code repository under CVS version control. If you check the "Use Index" flag, this means you must update your home page content by editing the index.html file, saving it, and then committing it into CVS to display the newest file revision in your project's home page. When you use the index.html file, you can include HTML formatting, graphics, and other more complex elements for your project's home page.</p>

   <h3><a id="ownersmessage" name="ownersmessage">Updating the owner's message</a></h3>

   <p>Initially you use the field to identify yourself as the project owner and convey project goals. As the project progresses, use the Owner's Message to highlight project milestones, list changing requirements, and identify particular resource needs. For example, you may advertise the types of development expertise currently being sought:</p>

   <blockquote>
    <p>"Desperately seeking experienced Java servlet developers with a passion for creating apps that will change the world."</p>
   </blockquote>

   <p>Or, you can give updates about the current status of development and what's coming up next.</p>

   <p>However you use this field, your Owner's Message should be updated frequently: usually once a week, but no less than monthly. Fresh messages convey a sense of excitement and momentum; critical perceptions to the growth of development projects.</p>

   <h3><a id="aboutlists" name="aboutlists">About configuring project mailing lists</a></h3>

   <p>The <strong>Project Edit</strong> page is also the place to administer your project's mailing list. To find out more about this, see <a href="ProjectOwnerMailingLists.html">Configuring and managing project mailing lists</a>.</p>

   <h3><a id="aboutlocking" name="aboutlocking">About project locking</a></h3>

   <p>If you have received email notification that your project is locked, you should contact a site administrator immediately for further information. Project locking means that site administrators have temporarily disabled your project. This may be due to site policy matters, technical issues, or other reasons.</p>

   <p>When you load your <b>Project Home</b> or <b>Project Edit</b> page, you encounter the "Locked" flag in red at the top. All site-related project activity is suspended in locked projects. Your project pages can still be accessed and all existing project data is intact, however <b><i>you and your project members temporarily have read-only access</i></b> to the source code repository, email archives, issue database, project files, and documents. No one -- including you -- can commit source code, enter issues, upload or download files and documents, change web content, or subscribe to or modify mailing lists. If your locked project is a public project, other site users can still view your project's home page but the project is flagged as "locked."</p>

   <p>A site administrator must unlock your project to reactivate it. You will receive email notification when this action is taken also.</p>

   <div class="courtesylinks">
    <p><a href="ProjectOwnerAdmin.html">Back to Help for project owner administration</a><br />
    <a href="/servlets/HelpTOC">Back to main Help index</a></p>
   </div>
  </div>
 


@


1.15
log
@extensive markup rework - first pass toward house xhtmlification
@
text
@d1 2
a2 11
<!DOCTYPE html PUBLIC "-//CollabNet//DTD XHTML 1.0 Transitional//EN"
"http://collabnet.com/dtds/collabnet_transitional_10.dtd">
<html>
 <head>
  <title>Project Help for Project Owner Administration</title>
<style type="text/css">
 p.c3 {font-style: italic}
 blockquote.c2 {font-weight: bold}
 div.c1 {margin-left: 2em}
</style>
 </head>
d4 2
a5 3
 <body>
 <div class="docs" id="docid">
<h2>Editing and maintaining the Project Home page</h2>
d7 3
a9 1
  <p><b>Project help for project owner administration: Index</b></p>
d11 3
a13 1
  
d15 2
a16 3
  <div>
   <dl>
    <dt><a href="ProjectOwnerAdmin.html">Project owner administration</a></dt>
d18 1
a18 2
    <dd>
     <strong>You are here: Editing and maintaining the Project Home page</strong>
d20 1
a20 2
     <ul>
      <li><strong><a href="#updatehome">Maintaining project information</a></strong></li>
d22 1
a22 1
      <li><strong><a href="#useindex">About the 'Use Project Home Page' option</a></strong></li>
d24 3
a26 1
      <li><strong><a href="#ownersmessage">Updating the owner's message</a></strong></li>
d28 1
a28 1
      <li><strong><a href="#aboutlists">About configuring project mailing lists</a></strong></li>
d30 1
a30 3
      <li><strong><a href="#aboutlocking">About project locking</a></strong></li>
     </ul>
    </dd>
d32 1
a32 1
    <dd><a href="ProjectOwnerNews.html">Managing project site news</a></dd>
d34 1
a34 1
    <dd><a href="ProjectOwnerFiles.html">Managing project files</a></dd>
d36 1
a36 1
    <dd><a href="ProjectOwnerMembers.html">Adding project members and approving roles</a></dd>
d38 1
a38 1
    <dd><a href="ProjectOwnerMailingLists.html">Configuring and managing project mailing lists</a></dd>
d40 5
a44 1
    <dd><a href="ProjectOwnerDocuments.html">Managing project documentation</a></dd>
d46 3
a48 1
    <dd><a href="ProjectOwnerSource.html">Managing project source code</a></dd>
d50 1
a50 1
    <dd><a href="ProjectOwnerIssues.html">Tracking project issues</a></dd>
d52 1
a52 3
    <dt><a href="/servlets/HelpTOC">Back to the main Help index</a></dt>
   </dl>
  </div>
d54 1
a54 3
  
  
  <h3><a id="updatehome" name="updatehome">Maintaining project information</a></h3> 
d56 1
a56 1
  <p>The <strong>Project Home</strong> page is the entry point for all project users, members as well as potential contributors.&#160;The primary role of the <strong>Project Home</strong> page is&#160;to highlight the project's mission, primary goals, current status, and ongoing needs.</p>
d58 2
a59 1
  <p><strong>NOTE</strong>: For a good example of summarizing project goals and status, see the open source <a href="http://subversion.tigris.org/">Subversion project home page</a>.</p>
d61 2
a62 1
  <p>Project information can be modified through the <b>Administer Projects</b> page, accessed by one of the following methods:&#160;</p>
d64 1
a64 2
  <ul>
   <li>At first login, the&#160;home page has a&#160;<strong>My Projects</strong> link as well as an&#160;<strong>Admin</strong> link to the <strong>Project Edit</strong> page.</li>
d66 2
a67 2
   <li>Once you are on your <strong>Project Home</strong> page or other project pages, use the <strong>Admin</strong> link in the Project Resources tool bar at the top of every screen.</li>
  </ul>
d69 1
a69 1
  <p>The <strong>Project Home</strong> page has the following fields which are also part of the project creation process:</p>
d71 1
a71 2
  <ul>
   <li>Project Name</li>
d73 1
a73 1
   <li>Summary</li>
d75 2
a76 1
   <li>Description</li>
d78 1
a78 1
   <li>License</li>
d80 1
a80 2
   <li>Project Category.</li>
  </ul>
d82 2
a83 1
  <p>By clicking on the <strong>Edit this Project</strong> link you can modify the information in each of these fields. Because the description field accommodates html formatting and graphics, you can use this to customize and add information to your project home page.</p>
d85 1
a85 1
  <p>There are several additional fields in the <b>Administer Projects</b> page that do not appear during the project creation process:</p>
d87 2
a88 2
  <ul>
   <li>Message From the Owner(s)</li>
d90 1
a90 1
   <li>Edit this Project</li>
d92 1
a92 2
   <li>Request New Project Role</li>
  </ul>
d94 1
a94 3
  
  
  <h3><a id="useindex" name="useindex">About the 'Use Project Home Page' option</a></h3> 
d96 1
a96 1
  <p>Your <b>Project Home</b> page by default displays the content that you entered in the Description field in the <b>Administer Project</b> page.</p>
d98 1
a98 1
  <p>Because some projects require more complex home pages, however, you have the option to store and display special home page content from a different file. The "Use Index" flag in the <b>Administer Project</b> page indicates that your project home page should display the contents of the "index.html" file instead of displaying description field information from the database. This file is located in:</p>
d100 1
a100 3
  <blockquote class="c2">
   http://yourprojectname.this domain/www/index.html
  </blockquote>
d102 1
a102 1
  <p>This file is part of&#160; the project's source code repository under CVS version control. If you check the "Use Index" flag, this means you must update your home page content by editing the index.html file, saving it, and then committing it into CVS to display the newest file revision in your project's home page. When you use the index.html file, you can include HTML formatting, graphics, and other more complex elements for your project's home page.</p>
d104 3
a106 3
  
  
  <h3><a id="ownersmessage" name="ownersmessage">Updating the owner's message</a></h3> 
d108 1
a108 1
  <p>Initially you use the field&#160;to identify&#160;yourself as the project owner and convey project goals. As the project progresses, use the Owner's Message&#160;to&#160;highlight project milestones, list changing requirements, and identify particular resource needs. For example,&#160;you&#160;may advertise the types&#160;of development expertise currently being sought:</p>
d110 1
a110 3
  <blockquote>
   <p class="c3">"Desperately seeking experienced Java servlet developers with a passion for creating apps that will change the world."</p>
  </blockquote>
d112 1
a112 1
  <p>Or, you can give updates about the current status of development and what's coming up next.</p>
d114 1
a114 1
  <p>However you use this field, your Owner's Message should be updated frequently:&#160;usually once a week, but&#160;no less than monthly. Fresh messages convey a sense of excitement and momentum; critical perceptions to the growth of development projects.</p>
d116 1
a116 3
  
  
  <h3><a id="aboutlists" name="aboutlists">About configuring project mailing lists</a></h3> 
d118 1
a118 1
  <p>The <strong>Project Edit</strong> page is also the place to administer your project's mailing list. To find out more about this, see <a href="ProjectOwnerMailingLists.html">Configuring and managing project mailing lists</a>.</p>
d120 1
a120 3
  
  
  <h3><a id="aboutlocking" name="aboutlocking">About project locking</a></h3> 
d122 1
a122 1
  <p>If you have received email notification that your project is locked, you should contact a site administrator immediately for further information. Project locking means that site administrators have temporarily disabled your project. This may be due to site policy matters, technical issues, or other reasons.</p>
d124 6
a129 11
  <p>When you load your <b>Project Home</b> or <b>Project Edit</b> page, you encounter the "Locked" flag in red at the top. All site-related project activity is suspended in locked projects. Your project pages can still be accessed and all existing project data is intact, however <b><i>you and your project members temporarily have read-only access</i></b> to the source code repository, email archives, issue database, project files, and documents. No one -- including you -- can commit source code, enter issues, upload or download files and documents, change web content, or subscribe to or modify mailing lists. If your locked project is a public project, other site users can still view your project's home page but the project is flagged as "locked."</p>

  <p>A site administrator must unlock your project to reactivate it. You will receive email notification when this action is taken also.</p>

  
  
 <div class="courtesylinks"> <a href="ProjectOwnerAdmin.html">Back to Help for project owner administration</a><br />
<a href="/servlets/HelpTOC">Back to main Help index</a></div> 
 </div>
</body>
</html>
@


1.14
log
@changed doc subheading about using index.html option to reflect changed wording in template to 'Use the Project Home Page'
@
text
@d1 2
d4 8
a11 1
<head>
d13 55
a67 1
<title>Project Help for Project Owner Administration</title>
a68 7
</head>
<body>
<p>
    <span class="Header" nowrap>Editing and maintaining the Project Home page</span> 
<p>
<span class="PlainText"><b>Project help for project owner administration: Index</b>
<p>
d70 13
a82 113
<dl>
<dt><a href="ProjectOwnerAdmin.html">Project owner administration</a>
	<dd><strong>You are here: Editing and maintaining the 
    Project Home page          
		<ul>
		<li><a href="#updatehome">Maintaining project information</a>
		<li><a href="#useindex">About the 'Use Project Home Page' option</a>
		<li><a href="#ownersmessage">Updating the owner's message</a>
		<li><a href="#aboutlists">About configuring project mailing lists</a></li>
		<li><a href="#aboutlocking">About project locking</a>
		</ul></strong>
	<dd><a href="ProjectOwnerNews.html">Managing project site news</a>
	<dd><a href="ProjectOwnerFiles.html">Managing project files</a>
	<dd><a href="ProjectOwnerMembers.html">Adding project members and approving roles</a>
	<dd><a href="ProjectOwnerMailingLists.html">Configuring and managing project mailing lists</a>
	<dd><a href="ProjectOwnerDocuments.html">Managing project documentation</a>
	<dd><a href="ProjectOwnerSource.html">Managing project source code</a>
	<dd><a href="ProjectOwnerIssues.html">Tracking project issues</a>
<dt><a href="/servlets/HelpTOC">Back to the main Help index</a></dt>
</dl>
</ul>

<p>

<hr noshade size=1>
<a name="updatehome"></a><span class="InputHeader">Maintaining project information</span>
<p>                         The <strong>Project Home </strong>page is the entry 
point for all project users, members as well as potential contributors.&nbsp;The 
primary role of the <strong>Project Home </strong>                                                page is&nbsp;to highlight the project's mission, primary goals, current status, and ongoing needs.
<p><strong>NOTE</strong>: 
For a good example of summarizing project goals and status, see the open source <a href="http://subversion.tigris.org/" target="_new">Subversion project home page</a>.
<p>
        Project information can be modified through the <b>Administer Projects</b> page, accessed by one of the following methods:&nbsp;
<p>
<ul>
<li>At first login, the&nbsp;home page has 
  a&nbsp;<strong>My Projects</strong> link as well as 
  an&nbsp;<strong>Admin</strong> link to the <strong>Project Edit 
  </strong>      page.
<p></p>
<li>Once you are on your <strong>Project Home 
  </strong>page or other project pages, use the <strong>Admin </strong> link in the Project 
  Resources tool bar at the top of every screen.</li>              
</ul>
<p>
The <strong>Project Home </strong>page has the following 
fields which are also part of the project creation process: 
<ul><p><li>Project Name 
  <li>Summary 
  <li>Description 
  <li>License 
  <li>Project Category.
</li></ul>
By clicking on the 
<strong>Edit this Project </strong>link you can modify the information in each of these fields. Because the description field accommodates html formatting and graphics, you can use this to customize and add information to your project home page.

<p>There are several additional fields in the <b>Administer Projects</b> page that do not appear during the project creation process: </p>
<p><ul><li>Message From the Owner(s)
  <li>Edit this Project
  <li>Request New Project Role
  <p></p></li></ul>
<p>


<hr noshade size=1>
<a name="useindex"></a><span class="InputHeader">About the 'Use Project Home Page' option</span>
<p>

Your <b>Project Home</b>               page by default displays the content that you entered in the Description field in the <b>Administer Project</b> page.
<p>
Because some projects require more complex home pages, however, you have the option to store and display special home page content from a different file. The "Use Index" flag in the <b>Administer Project</b> page indicates that your project home page should display the contents of the "index.html" file instead of displaying description field information from the database. This file is located in:
<blockquote>
<b>http://yourprojectname.this domain/www/index.html</b>
</blockquote>This 
file is part of&nbsp; the project's source code repository under CVS version control. If you check the "Use Index" flag, this means you must update your home page content by editing the index.html file, saving it, and then committing it into CVS to display the newest file revision in your project's home page.  When you use the index.html file, you can include HTML formatting, graphics, and other more complex elements for your project's home page.
<p>

<hr noshade size=1>
<a name="ownersmessage"></a><span class="InputHeader"><b>Updating the owner's message</b></span>

<p>            Initially you use the field&nbsp;to identify&nbsp;yourself as the project owner and convey project goals. As the project progresses, use the Owner's Message&nbsp;to&nbsp;highlight project milestones, list changing requirements, and identify particular resource needs. For example,&nbsp;you&nbsp;may advertise the types&nbsp;of development expertise currently being sought:
<blockquote>
  <p>
<i>"Desperately seeking experienced Java servlet developers with a passion for creating apps that will change the world."</i> 
  </p></blockquote>
  <p>Or, you can give updates about the current status of development and what's 
  coming up next. </p>       

               
<p>
           However you use this field, your Owner's Message should be updated frequently:&nbsp;usually once a week, but&nbsp;no less than monthly. Fresh messages convey a sense of excitement and momentum; critical perceptions to the growth of development projects.
<p>

<hr noshade size=1>
<a name="aboutlists"></a><span class="InputHeader"><b>About configuring  project mailing lists</b></span>
<p>
The <strong>Project Edit </strong>
    page is also the place to administer your project's mailing list. To find out more about this, see <a href="ProjectOwnerMailingLists.html">Configuring and managing project mailing lists</a>.
<p>

<hr noshade size=1>
<a name="aboutlocking"></a><span class="InputHeader">About project locking</span>
<p>
If you have received email notification that your project is locked, you should contact a site administrator immediately for further information. Project locking means that site administrators have temporarily disabled your project. This may be due to site policy matters, technical issues, or other reasons.
<p>
When you load your <b>Project Home</b> or <b>Project Edit</b> page, you encounter the "Locked" flag in red at the top. All site-related project activity is suspended in locked projects. Your project pages can still be accessed and all existing project data is intact, however <b><i>you and your project members temporarily have read-only access</i></b> to the source code repository, email archives, issue database, project files, and documents.  No one -- including you -- can commit source code, enter issues, upload or download files and documents, change web content, or subscribe to or modify mailing lists. If your locked project is a public project, other site users can still view your project's home page but the project is flagged as "locked."
<p>
A site administrator must unlock your project to reactivate it. You will receive email notification when this action is taken also.
<p>

<hr noshade size=1>
<a href="ProjectOwnerAdmin.html">Back to Help for project owner administration</a><br>
<a href="/servlets/HelpTOC">Back to main Help index</a>
d84 66
a149 1
</span>
d152 2
@


1.13
log
@minor html edits
@
text
@d20 1
a20 1
		<li><a href="#useindex">About the 'Use Index'</a>
d79 1
a79 1
<a name="useindex"></a><span class="InputHeader">About the 'Use Index'</span>
@


1.13.6.1
log
@updating branch with latest help files
@
text
@d20 1
a20 1
		<li><a href="#useindex">About the 'Use Project Home Page' option</a>
d79 1
a79 1
<a name="useindex"></a><span class="InputHeader">About the 'Use Project Home Page' option</span>
@


1.12
log
@added info to project locking section about automatic email notification
@
text
@d44 1
a44 1
For a good example of summarizing project goals and status, see the open source <a href="http://subversion.tigris.org/" target="_new">subversion project home page</a>.
d125 1
a125 1
<a href="ProjectOwnerAdmin.html">Back to project owner administration help</a><br>
@


1.11
log
@added project locking content
@
text
@d117 1
a117 1
If you load your <b>Project Home</b> or <b>Project Edit</b> page and encounter the "Locked" flag in red at the top, this means site administrators have temporarily disabled your project. This may be due to site policy matters, technical issues, or other reasons. <b>When your project is locked, you should contact a site administrator immediately for further information.</b>
d119 3
a121 1
All site-related project activity is suspended in locked projects. The project home page and other pages can still be accessed and all existing project data is intact, however <b><i>you and your project members temporarily have read-only access</i></b> to the source code repository, email archives, issue database, project files, and documents.  No one -- including you -- can commit source code, enter issues, upload or download files and documents, change web content, or subscribe to or modify mailing lists. If your locked project is a public project, other site users can still view your project's home page but the project is flagged as "locked."
@


1.10
log
@fixed index; added link for ProjectOwnerDocuments.html
@
text
@d1 128
a128 119
<HTML>
<HEAD>

<TITLE>Project Help for Project Owner Administration</TITLE>

</HEAD>
<BODY>
<P>
    <SPAN CLASS="Header" NOWRAP>Editing and maintaining the Project Home page</SPAN> 
<P>
<SPAN CLASS="PlainText"><B>Project help for project owner administration: Index</B>
<P>
  <UL>
<DL>
<DT><A href="ProjectOwnerAdmin.html">Project owner administration</A>
	<DD><STRONG>You are here: Editing and maintaining the 
    Project Home page          
		<UL>
		<LI><A href="#updatehome">Maintaining project information</A>
		<LI><A href="#useindex">About the 'Use Index'</A>
		<LI><A href="#ownersmessage">Updating the owner's message</A>
		<LI><A href="#aboutlists">About configuring project mailing lists</A></LI>
		</UL></strong>
	<DD><A href="ProjectOwnerNews.html">Managing project site news</A>
	<DD><A href="ProjectOwnerFiles.html">Managing project files</A>
	<DD><A href="ProjectOwnerMembers.html">Adding project members and approving roles</A>
	<DD><A href="ProjectOwnerMailingLists.html">Configuring and managing project mailing lists</A>
	<dd><a href="ProjectOwnerDocuments.html">Managing project documentation</a>
	<DD><A href="ProjectOwnerSource.html">Managing project source code</A>
	<DD><A href="ProjectOwnerIssues.html">Tracking project issues</A>
<DT><A href="/servlets/HelpTOC">Back to the main Help index</A></DT>
</DL>
</UL>

<P>

<HR NOSHADE SIZE=1>
<A NAME="updatehome"></A><SPAN CLASS="InputHeader">Maintaining project information</SPAN>
<P>                         The <STRONG>Project Home </STRONG>page is the entry 
point for all project users, members as well as potential contributers.&nbsp;The 
primary role of the <STRONG>Project Home </STRONG>                                                page is&nbsp;to highlight the project's mission, primary goals, current status, and ongoing needs.
<P><STRONG>NOTE</STRONG>: 
For a good example of summarizing project goals and status, see the open source <A HREF="http://subversion.tigris.org/" TARGET="_new">subversion project home page</A>.
<P>
        Project information can be modified through the <B>Administer Projects</B> page, accessed by one of the following methods:&nbsp;
<P>
<UL>
<LI>At first login, the&nbsp;home page has 
  a&nbsp;<STRONG>My Projects</STRONG> link as well as 
  an&nbsp;<STRONG>Admin</STRONG> link to the <STRONG>Project Edit 
  </STRONG>      page.
<P></P>
<LI>Once you are on your <STRONG>Project Home 
  </STRONG>page or other project pages, use the <STRONG>Admin </STRONG> link in the Project 
  Resources tool bar at the top of every screen.</LI>              
</UL>
<P>
The <STRONG>Project Home </STRONG>page has the following 
fields which are also part of the project creation process: 
<ul><P><li>Project Name 
  <LI>Summary 
  <LI>Description 
  <LI>License 
  <LI>Project Category.
</LI></ul>
By clicking on the 
<STRONG>Edit this Project </STRONG>link you can modify the information in each of these fields. Because the description field accommodates html formatting and graphics, you can use this to customize and add information to your project home page.

<P>There are several additional fields in the <B>Administer Projects</B> page that do not appear during the project creation process: </P>
<P><ul><li>Message From the Owner(s)
  <LI>Edit this Project
  <LI>Request New Project Role
  <P></P></LI></ul>
<P>


<HR NOSHADE SIZE=1>
<A NAME="useindex"></A><SPAN CLASS="InputHeader">About the 'Use Index'</SPAN>
<P>

Your <B>Project Home</B>               page by default displays the content that you entered in the Description field in the <B>Administer Project</B> page.
<P>
Because some projects require more complex home pages, however, you have the option to store and display special home page content from a different file. The "Use Index" flag in the <B>Administer Project</B> page indicates that your project home page should display the contents of the "index.html" file instead of displaying description field information from the database. This file is located in:
<BLOCKQUOTE>
<B>http://yourprojectname.this domain/www/index.html</B>
</BLOCKQUOTE>This 
file is part of&nbsp; the project's source code repository under CVS version control. If you check the "Use Index" flag, this means you must update your home page content by editing the index.html file, saving it, and then committing it into CVS to display the newest file revision in your project's home page.  When you use the index.html file, you can include HTML formatting, graphics, and other more complex elements for your project's home page.
<P>

<HR NOSHADE SIZE=1>
<A NAME="ownersmessage"></A><SPAN CLASS="InputHeader"><B>Updating the owner's message</B></SPAN>

<P>            Initially you use the field&nbsp;to identify&nbsp;yourself as the project owner and convey project goals. As the project progresses, use the Owner's Message&nbsp;to&nbsp;highlight project milestones, list changing requirements, and identify particular resource needs. For example,&nbsp;you&nbsp;may advertise the types&nbsp;of development expertise currently being sought:
<BLOCKQUOTE>
  <P>
<I>"Desperately seeking experienced Java servlet developers with a passion for creating apps that will change the world."</I> 
  </P></BLOCKQUOTE>
  <P>Or, you can give updates about the current status of development and what's 
  coming up next. </P>       

               
<P>
           However you use this field, your Owner's Message should be updated frequently:&nbsp;usually once a week, but&nbsp;no less than monthly. Fresh messages convey a sense of excitement and momentum; critical perceptions to the growth of development projects.
<P>

<HR NOSHADE SIZE=1>
<A NAME="aboutlists"></A><SPAN CLASS="InputHeader"><B>About configuring  project mailing lists</B></SPAN>
<P>
The <STRONG>Project Edit </STRONG>
    page is also the place to administe your project's mailing list. To find out more about this, see <A href="ProjectOwnerMailingLists.html">Configuring and managing project mailing lists</A>.


<HR NOSHADE SIZE=1>
<A href="ProjectOwnerAdmin.html">Back to project owner administration help</A><BR>
<A href="/servlets/HelpTOC">Back to main Help index</A>

</SPAN>
</BODY>
</HTML>
@


1.9
log
@Edited by Thena
PR:
Obtained from:
Submitted by:
Reviewed by:
@
text
@d17 1
a17 1
    Project Home page </STRONG>         
d23 1
a23 1
		</UL>
d28 1
@


1.8
log
@added info about use index flag
@
text
@d1 118
a118 94
<HTML>
<HEAD>

<TITLE>Project Help for Project Owner Administration</TITLE>

</HEAD>
<BODY>
<P>
    <SPAN CLASS="Header" NOWRAP>Editing and maintaining the Project Home page</SPAN> 
<P>
<SPAN CLASS="PlainText"><B>Project help for project owner administration: Index</B>
<P>
  <UL>
<DL>
<DT><A HREF="ProjectOwnerAdmin.html">Project owner administration</A>
	<DD><B>You are here: Editing and maintaining the Project Home page
		<UL>
		<LI><A HREF="#updatehome">Maintaining project information</A>
		<LI><A HREF="#useindex">About the 'Use Index'</A>
		<LI><A HREF="#ownersmessage">Updating the owner's message</A>
		<LI><A HREF="#aboutlists">About configuring project mailing lists</A>
		</UL></B>
	<DD><A HREF="ProjectOwnerNews.html">Managing project site news</A>
	<DD><A HREF="ProjectOwnerFiles.html">Managing project files</A>
	<DD><A HREF="ProjectOwnerMembers.html">Adding project members and approving roles</A>
	<DD><A HREF="ProjectOwnerMailingLists.html">Configuring and managing project mailing lists</A>
	<DD><A HREF="ProjectOwnerSource.html">Managing project source code</A>
	<DD><A HREF="ProjectOwnerIssues.html">Tracking project issues</A>
<DT><A HREF="/servlets/HelpTOC">Back to the main Help index</A>
</DL>
</UL>

<P>

<HR NOSHADE SIZE=1>
<A NAME="updatehome"></A><SPAN CLASS="InputHeader">Maintaining project information</SPAN>
<P>
Your <B>Project Home</B> page is the focal point for project information. This page makes the project's first impression to potential contributors because all users on this site who want to learn about your project come this page first. Current project members begin here, too. As such, this is the key place to highlight the project's mission, primary goals, current status, and ongoing needs.
<P>
For a good example of summarizing project goals and status, see the open source <A HREF="http://subversion.tigris.org/" TARGET="_new">subversion project home page</A>.
<P>
Project information you originally entered when you created your project may be modified through the <B>Administrate Project</B> page. There are two ways to access this page:
<P>
<UL>
<LI>When you first log in to this site, your project appears in the &quot;My Projects&quot section as a link to your home page, along with an <I>Admin</I> link to the Project Edit page.
<P>
<LI>Once you are on your Project Home page or other project pages, use the <I>Admin</I> link in the Project Resources tool bar at the top of every screen. 
</UL>
<P>
Most of the fields in the <B>Administrate Project</B> page mirror the input fields you encounter in the project creation process: Project Name, Summary, Description, License, and Project Category. This page allows you to edit those fields as necessary, although your basic project information should remain fairly constant. Because the description field accommodates html formatting and graphics, you can use this to customize and add information to your project home page.

<P>There are several additional fields in the <B>Administrate Project</B> page that do not appear during the project creation process: </P>
<P>


<HR NOSHADE SIZE=1>
<A NAME="useindex"></A><SPAN CLASS="InputHeader">About the 'Use Index'</SPAN>
<P>

Your <B>Project Home</B> page by default displays the content that you entered in the "Description" field when you created your project, or as you have most recently edited this field in the <B>Administrate Project</B> page.
<P>
Because some projects require more complex home pages, however, you have the option to store and display special home page content from a different file. The "Use Index" flag in the <B>Administrate Project</B> page indicates that your project home page should display the contents of the "index.html" file instead of displaying description field information from the database. This file is located in:
<BLOCKQUOTE>
<B>http://yourprojectname.this domain/www/index.html</B>
</BLOCKQUOTE>
This file is part of project's source code repository under CVS version control. If you check the "Use Index" flag, this means you must update your home page content by editing the index.html file, saving it, and then committing it into CVS to display the newest file revision in your project's home page.  When you use the index.html file, you can include HTML formatting, graphics, and other more complex elements for your project's home page.
<P>

<HR NOSHADE SIZE=1>
<A NAME="ownersmessage"></A><SPAN CLASS="InputHeader"><B>Updating the owner's message</B></SPAN>

<P>Initially you use the Owner's Message field perhaps to identifying yourself as the project owner and convey project goals. As the project progresses, this is the place to briefly highlight project milestones, changing requirements, and particular resource needs. For example, sometimes you can advertise the kinds of development expertise currently being sought, for example:
<BLOCKQUOTE>
<I>"Desperately seeking experienced Java servlet developers with a passion for creating apps that will change the world."</I> (Lame, perhaps, but you get the point.)
</BLOCKQUOTE>
<P>
Or, you can give updates about the current status of development and what's coming up next.
<P>
However you use this field, your Owner's Message should be updated frequently, as much as once a week, and certainly no less than once a month. Fresh messages convey a sense of excitement and momentum, critical perceptions to the growth of development projects, particularly open source projects.
<P>

<HR NOSHADE SIZE=1>
<A NAME="aboutlists"></A><SPAN CLASS="InputHeader"><B>About configuring  project mailing lists</B></SPAN>
<P>
The Project Edit page is also the place to access your project's mailing list administration. To find out more about this, see <A HREF="ProjectOwnerMailingLists.html">Configuring and managing project mailing lists</A>.


<HR NOSHADE SIZE=1>
<A HREF="ProjectOwnerAdmin.html">Back to project owner administration help</A><BR>
<A HREF="/servlets/HelpTOC">Back to main Help index</A>

</SPAN>
</BODY>
</HTML>
@


1.7
log
@revising document index and links
@
text
@a7 2
<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
  <TR>
d19 1
d38 1
a38 1
Your Project Home page is the focal point for project information. This page makes the project's first impression to potential contributors because all users on this site who want to learn about your project come this page first. Current project members begin here, too. As such, this is the key place to highlight the project's mission, primary goals, current status, and ongoing needs.
d40 1
a40 1
(For a good example of summarizing project goals and status, see the open source <A HREF="http://subversion.tigris.org/" TARGET="_new">subversion project home page</A>.)
d42 1
a42 1
Project information you originally entered when you created your project may be modified through the Project Edit page. There are two ways to access this page:
d50 1
a50 1
Most of the fields in the Project Edit page mirror the fields in the project creation process: Project Name, Summary, Description, URL Alias, License, and Project Category. This page allows you to edit these fields as necessary, although your basic project information should remain fairly constant. Because the description field accommodates html formatting and graphics, you can use this to customize and add information to your project home page.
d52 15
a66 1
<P>There are several additional fields in the Project Edit page that do not appear during the project creation process: </P>
d70 1
a70 1
<A NAME="ownersmessage"></A><SPAN CLASS="InputHeader"><B>Updating the owner's message</B></SPAN><BR>
d83 1
a83 1
<A NAME="aboutlists"></A><SPAN CLASS="InputHeader"><B>About configuring  project mailing lists</B></SPAN><BR>
a92 2
</TR>
</TABLE>
@


1.6
log
@fixed heading tags
@
text
@d18 1
a18 1
	<DD><B>You are here: Editing and maintaining the Project Home page</B>
d23 1
a23 1
		</UL>
@


1.5
log
@html edits; revised doc index
@
text
@d57 1
a57 1
<A NAME="ownersmessage"></A><SPAN CLASS="HelptextHeader"><B>Updating the owner's message</B></SPAN><BR>
d70 1
a70 1
<A NAME="aboutlists"></A><SPAN CLASS="HelptextHeader"><B>About configuring  project mailing lists</B></SPAN><BR>
@


1.4
log
@added <title> tags to all files
@
text
@a9 1
<SPAN CLASS="PlainText">Project help for project owner administration</SPAN>
d12 3
a14 2

<SPAN CLASS="PlainText">
@


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


1.2
log
@updated for new help format
@
text
@d1 74
a74 74
<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
  <TR>
<SPAN CLASS="PlainText">Project help for project owner administration</SPAN>
<P>
    <SPAN CLASS="Header" NOWRAP>Editing and maintaining the Project Home page</SPAN> 

<SPAN CLASS="PlainText">
  <UL>
<DL>
<DT><A HREF="ProjectOwnerAdmin.html">Project owner administration</A>
	<DD><B>You are here: Editing and maintaining the Project Home page</B>
		<UL>
		<LI><A HREF="#updatehome">Maintaining project information</A>
		<LI><A HREF="#ownersmessage">Updating the owner's message</A>
		<LI><A HREF="#aboutlists">About configuring project mailing lists</A>
		</UL>
	<DD><A HREF="ProjectOwnerNews.html">Managing project site news</A>
	<DD><A HREF="ProjectOwnerFiles.html">Managing project files</A>
	<DD><A HREF="ProjectOwnerMembers.html">Adding project members and approving roles</A>
	<DD><A HREF="ProjectOwnerMailingLists.html">Configuring and managing project mailing lists</A>
	<DD><A HREF="ProjectOwnerSource.html">Managing project source code</A>
	<DD><A HREF="ProjectOwnerIssues.html">Tracking project issues</A>
<DT><A HREF="/servlets/HelpTOC">Back to the main Help index</A>
</DL>
</UL>

<P>

<HR NOSHADE SIZE=1>
<A NAME="updatehome"></A><SPAN CLASS="InputHeader">Maintaining project information</SPAN>
<P>
Your Project Home page is the focal point for project information. This page makes the project's first impression to potential contributors because all users on this site who want to learn about your project come this page first. Current project members begin here, too. As such, this is the key place to highlight the project's mission, primary goals, current status, and ongoing needs.
<P>
(For a good example of summarizing project goals and status, see the open source <A HREF="http://subversion.tigris.org/" TARGET="_new">subversion project home page</A>.)
<P>
Project information you originally entered when you created your project may be modified through the Project Edit page. There are two ways to access this page:
<P>
<UL>
<LI>When you first log in to this site, your project appears in the &quot;My Projects&quot section as a link to your home page, along with an <I>Admin</I> link to the Project Edit page.
<P>
<LI>Once you are on your Project Home page or other project pages, use the <I>Admin</I> link in the Project Resources tool bar at the top of every screen. 
</UL>
<P>
Most of the fields in the Project Edit page mirror the fields in the project creation process: Project Name, Summary, Description, URL Alias, License, and Project Category. This page allows you to edit these fields as necessary, although your basic project information should remain fairly constant. Because the description field accommodates html formatting and graphics, you can use this to customize and add information to your project home page.

<P>There are several additional fields in the Project Edit page that do not appear during the project creation process: </P>
<P>

<HR NOSHADE SIZE=1>
<A NAME="ownersmessage"></A><SPAN CLASS="HelptextHeader"><B>Updating the owner's message</B></SPAN><BR>

<P>Initially you use the Owner's Message field perhaps to identifying yourself as the project owner and convey project goals. As the project progresses, this is the place to briefly highlight project milestones, changing requirements, and particular resource needs. For example, sometimes you can advertise the kinds of development expertise currently being sought, for example:
<BLOCKQUOTE>
<I>"Desperately seeking experienced Java servlet developers with a passion for creating apps that will change the world."</I> (Lame, perhaps, but you get the point.)
</BLOCKQUOTE>
<P>
Or, you can give updates about the current status of development and what's coming up next.
<P>
However you use this field, your Owner's Message should be updated frequently, as much as once a week, and certainly no less than once a month. Fresh messages convey a sense of excitement and momentum, critical perceptions to the growth of development projects, particularly open source projects.
<P>

<HR NOSHADE SIZE=1>
<A NAME="aboutlists"></A><SPAN CLASS="HelptextHeader"><B>About configuring  project mailing lists</B></SPAN><BR>
<P>
The Project Edit page is also the place to access your project's mailing list administration. To find out more about this, see <A HREF="ProjectOwnerMailingLists.html">Configuring and managing project mailing lists</A>.


<HR NOSHADE SIZE=1>
<A HREF="ProjectOwnerAdmin.html">Back to project owner administration help</A><BR>
<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 23
a25 3
    <TD CLASS="Header" NOWRAP>Editing and maintaining the Project Home page</TD> 
  </TR>
</TABLE>
a26 2
<TABLE BORDER="0" CELLSPACING="2" CELLPADDING="2" BORDER="0" WIDTH="100%">
  <TR>
a27 1
<SPAN CLASS="PlainText">
d29 2
a30 1
<span class="InputHeader">Updating your Project Home page</SPAN>
d33 2
a34 2
<p>
(For a good example of summarizing project goals and status, see the open source <A HREF="http://subversion.tigris.org/" target="_new">subversion project home page</A>.)
d39 1
a39 1
<LI>When you first log in to this site, your project appears in the &quotMy Projects&quot section as a link to your home page, along with an <I>Admin</I> link to the Project Edit page.
d47 1
d49 2
a50 1
<P><BR><BR><A NAME="ownersmessage"></A><SPAN CLASS="HelptextHeader"><B>Owner's Message</B></SPAN><BR>
d52 1
a52 1
<P>Intitially you use the Owner's Message field perhaps to identifying yourself as the project owner and convey project goals. As the project progresses, this is the place to briefly highlight project milestones, changing requirements, and particular resource needs. For example, sometimes you can advertise the kinds of development expertise currently being sought, for example:
d59 1
a59 1
However you use this field, your Owner's Message should be updated frequently, as much as once a week, and certianly no less than once a month. Fresh messages convey a sense of excitement and momentum, critical perceptions to the growth of development projects, particularly open source projects.
d61 3
a63 1
<P><BR><BR><A NAME="ownersmessage"></A><SPAN CLASS="HelptextHeader"><B>About configuring  project mailing lists</B></SPAN><BR>
d65 2
a66 1
The Project Edit page is also the place to access mailing list configurations. To find out more about this, see <A HREF="ProjectOwnerMailingLists.html">Configuring and managing project mailing lists</A>.
d68 3
a70 2
<HR noShade SIZE=1>
<a href="Help.html">Back to main Help index</a></p></span>
a72 1
</TD>
@

