head	1.9;
access;
symbols
	TIGRIS_1_1_0RC2:1.5.6.1
	TIGRIS_1_1_0RC1:1.5.6.1
	TIGRIS_1_1:1.5.6.1.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.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.03.20.55.56;	author lori;	state Exp;
branches;
next	1.6;

1.6
date	2001.04.17.23.24.09;	author tberry;	state Exp;
branches;
next	1.5;

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

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

1.3
date	2001.03.10.02.22.24;	author lori;	state Exp;
branches;
next	1.2;

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

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

1.5.6.1
date	2001.06.13.00.31.04;	author lori;	state Exp;
branches;
next	;


desc
@@


1.9
log
@html usage revision
@
text
@  <div class="docs" id="domadminprojectapproval">
   <h2>Approving, deferring, or disapproving projects</h2>

   <div class="toc">
    <h3>Help for domain administration: Index</h3>

    <ul>
     <li>
      <a href="DomAdminOverview.html">Domain administration overview</a> 

      <ul>
       <li><a href="DomAdminAddUsers.html">Adding and editing user accounts</a></li>

       <li><a href="DomAdminRoles.html">Administering roles and permissions</a></li>

       <li><a href="DomAdminUserGroups.html">Creating and editing user groups</a></li>

       <li><a href="DomAdminProjectGroups.html">You are here: Creating and editing project groups</a></li>

       <li>
        <strong>You are here:</strong> Approving, disapproving, or deferring projects 

        <ul>
         <li><a href="#aboutapproval">About the project approval process</a></li>

         <li><a href="#deferdisapprove">Deferring and disapproving projects</a></li>

         <li><a href="#other">Locking, unlocking, and deleting projects</a></li>
        </ul>
       </li>

       <li><a href="DomAdminAuditLogs.html">Using domain administration tools</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="aboutapproval" name="aboutapproval">About the project approval process</a></h3>

   <p>When a project is proposed on this site, it appears in the <i>Proposed Projects</i> link in the "Pending Actions" section of the Domain Administrator's <b>Start Page</b>. The next time you log in, this count indicates how many projects are awaiting your action. Taking no action has the same result as deferring a project; they remain effectively in limbo as pending actions.</p>

   <p>Click the <i>Proposed Projects</i> link in the "Pending Actions" section to display the <b>Project Approval</b> page. An alphabetical listing of all pending projects appears with the proposer's name and a project summary included. Project titles link to each project's home page. The proposer's name links to the <b>Edit User</b> screen containing this user's account information.</p>

   <p>As the Domain Administrator, you disperse with pending projects in one of three ways: approve, defer, or disapprove them by placing checkmarks in the appropriate boxes. All of these actions are tracked in an administrative audit log, along with other administrative actions. See <a href="DomAdminAuditLogs.html">Using administrative audit logs</a> for further information.</p>

   <p>The criteria for approving or disapproving proposed projects falls within your judgment as the Domain Administrator. Factors to consider might include:</p>

   <ul>
    <li>Does the project fall within your site's overall mission and general goals?</li>

    <li>Is the project well scoped out?</li>

    <li>Are project objectives clearly stated?</li>
   </ul>

   <p>When you approve a project, an email message is automatically generated notifying the Project Owner. The project appears in the site's hosted project listings, including the <b>Hosted Projects</b> page and the appropriate category home page(s). The Project Owner can now approve members and grant roles to them.</p>

   <h3><a id="deferdisapprove" name="deferdisapprove">Deferring or disapproving projects</a></h3>

   <p>While your approval of a project is pending, or when you defer approval, the project simply remains in your list of pending projects awaiting approval. It does not appear within any project listings in public pages or to any other users. The proposer, however, continues to see a link to this project in her/his <b>Start Page</b> under the "My Projects" section, and can conduct most project related activities including:</p>

   <ul>
    <li>accessing and updating their project's home page</li>

    <li>inviting participants</li>

    <li>uploading and downloading project files and documents</li>

    <li>adding and editing news items</li>

    <li>checking source code into the project's CVS repository</li>

    <li>assigning and tracking project issues.</li>
   </ul>

   <p>None of this project information on pending projects is visible to other site users, however. And until you approve a pending project, the Project Owner <i>cannot</i> approve project members or grant roles to them.</p>

   <p>When you disapprove a project, an email message is automatically generated to notify the proposer. This message is brief; the proposer is encouraged to contact you for further discussion about the specific reasons for disapproval.</p>

   <h3><a id="other" name="other">Locking, unlocking, and deleting projects</a></h3>

   <p>The Project Lock feature enables you to stop all activity on a project if circumstances arise to necessitate this. Whether this is due to site policy matters, technical issues, or other reasons, project locking lets you essentially turn off all site-related project activity. The locked project's home page and other pages can still be accessed and all existing project data is intact, however the Project Owner and members have read-only access to the source code repository, email archives, issue database, project files, and documents. No one -- including the project owner -- can commit source code, enter issues, upload or download files and documents, change web content, or subscribe to or modify mailing lists. If the locked project is a public project, other site users can still view the project's home page but the project is flagged as "locked."</p>

   <p>To lock a currently active project, navigate to the project's home page and click on the <i>Admin</i> link in the Project Resources tool bar to display the <b>Project Edit</b> page. Use the <i>Project Lock</i> link at the bottom to display a screen where you can set the lock. This action automatically generates an email notice to the project owner, telling him/her to contact a site administrator immediately.</p>

   <p>To unlock a project, your view of the locked project's home page displays the red "Locked" flag and an <i>Unlock</i> link next to it you can use to enable the project again. Alternatively, you can use the <b>Project Edit</b> page where there an <b>Unlock Project</b> link appears at the bottom of the page. When you unlock a project to reactivate it, another email notice is automatically sent to the project owner.</p>

   <p>Projects may also be deleted from this site when they either don't pan out or reach the end of their development life cycle. The <b>Project Edit</b> page includes a <i>Project Delete</i> link at the bottom of the page. If you click this link, you are asked to confirm the action. <b><i>Use the project delete feature with caution!</i> Deleting the project not only removes it from site project listings, but also completely erases the project's cvs repository files, all project files and documents, issues database, and mailing list archives.</b></p>

   <div class="courtesylinks">
    <a href="DomAdminOverview.html">Back to help for domain administration</a><br />
    <a href="/servlets/HelpTOC">Back to main Help index</a>
   </div>
  </div>
 


@


1.8
log
@extensive markup rework - first pass toward house xhtmlification
@
text
@d1 2
a2 9
<!DOCTYPE html PUBLIC "-//CollabNet//DTD XHTML 1.0 Transitional//EN"
"http://collabnet.com/dtds/collabnet_transitional_10.dtd">
<html>
 <head>
  <title>Approving projects</title>
<style type="text/css">
 div.c1 {margin-left: 2em}
</style>
 </head>
d4 2
a5 3
 <body>
<div class="docs" id="docid">
<h2>Approving, deferring, or disapproving projects</h2>
d7 3
a9 1
  <p><b>Help for domain administration: Index</b></p>
d11 2
a12 3
  <div>
   <dl>
    <dt><a href="DomAdminOverview.html">Domain administration overview</a></dt>
d14 1
a14 1
    <dd><a href="DomAdminAddUsers.html">Adding and editing user accounts</a></dd>
d16 1
a16 1
    <dd><a href="DomAdminRoles.html">Administering roles and permissions</a></dd>
d18 1
a18 1
    <dd><a href="DomAdminUserGroups.html">Creating and editing user groups</a></dd>
d20 2
a21 1
    <dd><a href="DomAdminProjectGroups.html">You are here: Creating and editing project groups</a></dd>
d23 2
a24 2
    <dd>
     <b>You are here: Approving, disapproving, or deferring projects</b>
d26 1
a26 2
     <ul>
      <li><b><a href="#aboutapproval">About the project approval process</a></b></li>
d28 3
a30 1
      <li><b><a href="#deferdisapprove">Deferring and disapproving projects</a></b></li>
d32 5
a36 3
      <li><b><a href="#other">Locking, unlocking, and deleting projects</a></b></li>
     </ul>
    </dd>
d38 3
a40 1
    <dd><a href="DomAdminAuditLogs.html">Using domain administration tools</a></dd>
d42 1
a42 3
    <dt><a href="/servlets/HelpTOC">Back to main Help index</a></dt>
   </dl>
  </div>
d44 1
a44 3
  
  
  <h3><a id="aboutapproval" name="aboutapproval">About the project approval process</a></h3> 
d46 1
a46 1
  <p>When a project is proposed on this site, it appears in the <i>Proposed Projects</i> link in the "Pending Actions" section of the Domain Administrator's <b>Start Page</b>. The next time you log in, this count indicates how many projects are awaiting your action. Taking no action has the same result as deferring a project; they remain effectively in limbo as pending actions.</p>
d48 1
a48 1
  <p>Click the <i>Proposed Projects</i> link in the "Pending Actions" section to display the <b>Project Approval</b> page. An alphabetical listing of all pending projects appears with the proposer's name and a project summary included. Project titles link to each project's home page. The proposer's name links to the <b>Edit User</b> screen containing this user's account information.</p>
d50 1
a50 1
  <p>As the Domain Administrator, you disperse with pending projects in one of three ways: approve, defer, or disapprove them by placing checkmarks in the appropriate boxes. All of these actions are tracked in an administrative audit log, along with other administrative actions. See <a href="DomAdminAuditLogs.html">Using administrative audit logs</a> for further information.</p>
d52 2
a53 1
  <p>The criteria for approving or disapproving proposed projects falls within your judgment as the Domain Administrator. Factors to consider might include:</p>
d55 1
a55 2
  <ul>
   <li>Does the project fall within your site's overall mission and general goals?</li>
d57 2
a58 1
   <li>Is the project well scoped out?</li>
d60 1
a60 2
   <li>Are project objectives clearly stated?</li>
  </ul>
d62 1
a62 1
  <p>When you approve a project, an email message is automatically generated notifying the Project Owner. The project appears in the site's hosted project listings, including the <b>Hosted Projects</b> page and the appropriate category home page(s). The Project Owner can now approve members and grant roles to them.</p>
d64 1
a64 3
  
  
  <h3><a id="deferdisapprove" name="deferdisapprove">Deferring or disapproving projects</a></h3> 
d66 2
a67 1
  <p>While your approval of a project is pending, or when you defer approval, the project simply remains in your list of pending projects awaiting approval. It does not appear within any project listings in public pages or to any other users. The proposer, however, continues to see a link to this project in her/his <b>Start Page</b> under the "My Projects" section, and can conduct most project related activities including:</p>
d69 1
a69 2
  <ul>
   <li>accessing and updating their project's home page</li>
d71 1
a71 1
   <li>inviting participants</li>
d73 1
a73 1
   <li>uploading and downloading project files and documents</li>
d75 1
a75 1
   <li>adding and editing news items</li>
d77 2
a78 1
   <li>checking source code into the project's CVS repository</li>
d80 1
a80 2
   <li>assigning and tracking project issues.</li>
  </ul>
d82 1
a82 1
  <p>None of this project information on pending projects is visible to other site users, however. And until you approve a pending project, the Project Owner <i>cannot</i> approve project members or grant roles to them.</p>
d84 1
a84 1
  <p>When you disapprove a project, an email message is automatically generated to notify the proposer. This message is brief; the proposer is encouraged to contact you for further discussion about the specific reasons for disapproval.</p>
d86 1
a86 3
  
  
  <h3><a id="other" name="other">Locking, unlocking, and deleting projects</a></h3> 
d88 1
a88 1
  <p>The Project Lock feature enables you to stop all activity on a project if circumstances arise to necessitate this. Whether this is due to site policy matters, technical issues, or other reasons, project locking lets you essentially turn off all site-related project activity. The locked project's home page and other pages can still be accessed and all existing project data is intact, however the Project Owner and members have read-only access to the source code repository, email archives, issue database, project files, and documents. No one -- including the project owner -- can commit source code, enter issues, upload or download files and documents, change web content, or subscribe to or modify mailing lists. If the locked project is a public project, other site users can still view the project's home page but the project is flagged as "locked."</p>
d90 1
a90 1
  <p>To lock a currently active project, navigate to the project's home page and click on the <i>Admin</i> link in the Project Resources tool bar to display the <b>Project Edit</b> page. Use the <i>Project Lock</i> link at the bottom to display a screen where you can set the lock. This action automatically generates an email notice to the project owner, telling him/her to contact a site administrator immediately.</p>
d92 1
a92 1
  <p>To unlock a project, your view of the locked project's home page displays the red "Locked" flag and an <i>Unlock</i> link next to it you can use to enable the project again. Alternatively, you can use the <b>Project Edit</b> page where there an <b>Unlock Project</b> link appears at the bottom of the page. When you unlock a project to reactivate it, another email notice is automatically sent to the project owner.</p>
d94 6
a99 9
  <p>Projects may also be deleted from this site when they either don't pan out or reach the end of their development life cycle. The <b>Project Edit</b> page includes a <i>Project Delete</i> link at the bottom of the page. If you click this link, you are asked to confirm the action. <b><i>Use the project delete feature with caution!</i> Deleting the project not only removes it from site project listings, but also completely erases the project's cvs repository files, all project files and documents, issues database, and mailing list archives.</b></p>

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


1.7
log
@removed referenced links to project quotas and hosted db help docs in index; changed reference to title of DomAdminAuditLogs.html doc
@
text
@d1 2
d4 6
a9 1
<head>
d11 3
a13 1
<title>Approving projects</title>
d15 1
a15 80
</head>
<body>
   
<p>
<span class="Header">Approving, deferring, or disapproving projects</span>
<p>
<span class="PlainText"> 
<b>Help for domain administration: Index</b>
<p>
<ul>
	<dl>
	<dt><a href="DomAdminOverview.html">Domain administration overview</a>
		<dd><a href="DomAdminAddUsers.html">Adding and editing user accounts</a>
		<dd><a href="DomAdminRoles.html">Administering roles and permissions</a>
		<dd><a href="DomAdminUserGroups.html">Creating and editing user groups</a>
		<dd><a href="DomAdminProjectGroups.html">You are here: Creating and editing project groups</a>
		<dd><b>You are here: Approving, disapproving, or deferring projects
		<ul>
		<li><a href="#aboutapproval">About the project approval process</a>
		<li><a href="#deferdisapprove">Deferring and disapproving projects</a>
		<li><a href="#other">Locking, unlocking, and deleting projects</a>
		</ul></b>
		<dd><a href="DomAdminAuditLogs.html">Using domain administration tools</a>
    	<dt><a href="/servlets/HelpTOC">Back to main Help index</a>
	</dl>
</ul>
<p>

<hr noshade size=1>
<a name="aboutapproval"></a><span class="InputHeader">About the project approval process</span>
<p>
When a project is proposed on this site, it appears in the <i>Proposed Projects</i> link in the "Pending Actions" section of the Domain Administrator's <b>Start Page</b>. The next time you log in, this count indicates how many projects are awaiting your action. Taking no action has the same result as deferring a project; they remain effectively in limbo as pending actions.
<p>
Click the <i>Proposed Projects</i> link in the "Pending Actions" section to display the <b>Project Approval</b> page. An alphabetical listing of all pending projects appears with the proposer's name and a project summary included. Project titles link to each project's home page. The proposer's name links to the <b>Edit User</b> screen containing this user's account information.
<p>
As the Domain Administrator, you disperse with pending projects in one of three ways: approve, defer, or disapprove them by placing checkmarks in the appropriate boxes. All of these actions are tracked in an administrative audit log, along with other administrative actions. See <a href="DomAdminAuditLogs.html">Using administrative audit logs</a> for further information.
<p>
The criteria for approving or disapproving proposed projects falls within your judgment as the Domain Administrator. Factors to consider might include:
<ul>
<li>Does the project fall within your site's overall mission and general goals?
<li>Is the project well scoped out? 
<li>Are project objectives clearly stated?
</ul>
<p>
When you approve a project, an email message is automatically generated notifying the Project Owner. The project appears in the site's hosted project listings, including the <b>Hosted Projects</b> page and the appropriate category home page(s). The Project Owner can now approve members and grant roles to them.
<p>

<hr noshade size=1>
<a name="deferdisapprove"></a><span class="InputHeader">Deferring or disapproving projects</span>
<p>
While your approval of a project is pending, or when you defer approval, the project simply remains in your list of pending projects awaiting approval. It does not appear within any project listings in public pages or to any other users. The proposer, however, continues to see a link to this project in her/his <b>Start Page</b> under the "My Projects" section, and can conduct most project related activities including:
<ul>
<li>accessing and updating their project's home page
<li>inviting participants
<li>uploading and downloading project files and documents
<li>adding and editing news items
<li>checking source code into the project's CVS repository
<li>assigning and tracking project issues.
</ul>
None of this project information on pending projects is visible to other site users, however. And until you approve a pending project, the Project Owner <i>cannot</i> approve project members or grant roles to them.
<p>
When you disapprove a project, an email message is automatically generated to notify the proposer. This message is brief; the proposer is encouraged to contact you for further discussion about the specific reasons for disapproval. 
<p>

<hr noshade size=1>
<a name="other"></a><span class="InputHeader">Locking, unlocking, and deleting projects</span>
<p>
The Project Lock feature enables you to stop all activity on a project if circumstances arise to necessitate this. Whether this is due to site policy matters, technical issues, or other reasons, project locking lets you essentially turn off all site-related project activity. The locked project's home page and other pages can still be accessed and all existing project data is intact, however the Project Owner and members have read-only access to the source code repository, email archives, issue database, project files, and documents.  No one -- including the project owner -- can commit source code, enter issues, upload or download files and documents, change web content, or subscribe to or modify mailing lists. If the locked project is a public project, other site users can still view the project's home page but the project is flagged as "locked."
<p>
To lock a currently active project, navigate to the project's home page and click on the <i>Admin</i> link in the Project Resources tool bar to display the <b>Project Edit</b> page. Use the <i>Project Lock</i> link at the bottom to display a screen where you can set the lock. This action automatically generates an email notice to the project owner, telling him/her to contact a site administrator immediately. 
<p>
To unlock a project, your view of the locked project's home page displays the red "Locked" flag and an <i>Unlock</i> link next to it you can use to enable the project again. Alternatively, you can use the <b>Project Edit</b> page where there an <b>Unlock Project</b> link appears at the bottom of the page. When you unlock a project to reactivate it, another email notice is automatically sent to the project owner.
<p>
Projects may also be deleted from this site when they either don't pan out or reach the end of their development life cycle. The <b>Project Edit</b> page includes a <i>Project Delete</i> link at the bottom of the page. If you click this link, you are asked to confirm the action. <b><i>Use the project delete feature with caution!</i> Deleting the project not only removes it from site project listings, but also completely erases the project's cvs repository files, all project files and documents, issues database, and mailing list archives.</b>
<p>

<hr noshade size=1>
<a href="DomAdminOverview.html">Back to help for domain administration</a><br>
<a href="/servlets/HelpTOC">Back to main Help index</a>
</span>
d17 3
d21 89
d112 2
@


1.6
log
@added info to the top toc
PR:
Obtained from:
Submitted by:
Reviewed by:
@
text
@d28 2
a29 6
		<dd><a href="DomAdminSource.html">Administering domain source code repositories</a> 
		<dd><a href="DomAdminAuditLogs.html">Using administrative audit logs</a>
 <dd> <a href="/project/www/docs/ProjectQuotas.html" >Administering project 
      quotas</a> </dd>
    <dd> <a href="/project/www/docs/DomAdminAuditLogs.html" >Using a project database</a> 
    </dd>	<dt><a href="/servlets/HelpTOC">Back to main Help index</a>
@


1.5
log
@added info to project locking section about automatic email notification
@
text
@d30 4
a33 1
	<dt><a href="/servlets/HelpTOC">Back to main Help index</a>
d90 2
a91 2
</tr>
</table>
@


1.5.6.1
log
@updating branch with latest help files
@
text
@d28 3
a30 2
		<dd><a href="DomAdminAuditLogs.html">Using domain administration tools</a>
    	<dt><a href="/servlets/HelpTOC">Back to main Help index</a>
d87 2
a88 2


@


1.4
log
@minor edits to project locking section
@
text
@d76 1
a76 1
To lock a currently active project, navigate to the project's home page and click on the <i>Admin</i> link in the Project Resources tool bar to display the <b>Project Edit</b> page. Use the <i>Project Lock</i> link at the bottom to display a screen where you can set the lock.
d78 1
a78 1
To unlock a project, your view of the locked project's home page displays the red "Locked" flag and an <i>Unlock</i> link next to it you can use to enable the project again. Alternatively, you can use the <b>Project Edit</b> page where there an <b>Unlock Project</b> link appears at the bottom of the page.
@


1.3
log
@added project locking info
@
text
@d74 1
a74 1
The Project Lock feature enables you to stop all activity on a project if circumstances arise to necessitate this. Whether this is due to site policy matters, technical issues, or other reasons, project locking lets you essentially turn off all site-related project activity. The locked project's home page and other pages can still be accessed and all existing project data is intact, however the Project Owner and members have read-only access to the source code repository, email archives, issue database, project files, and documents.  No one can commit source code, enter issues, upload or download file and documents, or subscribe to or modify mailing lists. If the locked project is a public project, other site users can still view the project's home page but the project is flagged as "locked."
@


1.2
log
@changed page index; other minor edits
@
text
@d1 2
a2 2
<HTML>
<HEAD>
d4 1
a4 1
<TITLE>Approving projects</TITLE>
d6 2
a7 2
</HEAD>
<BODY>
d9 35
a43 34
<P>
<SPAN CLASS="Header">Approving, deferring, or disapproving projects</SPAN>
<P>
<SPAN CLASS="PlainText"> 
<B>Help for domain administration: Index</B>
<P>
<UL>
	<DL>
	<DT><A HREF="DomAdminOverview.html">Domain administration overview</A>
		<DD><A HREF="DomAdminAddUsers.html">Adding and editing user accounts</A>
		<DD><A HREF="DomAdminRoles.html">Administering roles and permissions</A>
		<DD><A HREF="DomAdminUserGroups.html">Creating and editing user groups</A>
		<DD><A HREF="DomAdminProjectGroups.html">You are here: Creating and editing project groups</A>
		<DD><B>You are here: Approving, disapproving, or deferring projects
		<UL>
		<LI><A HREF="#aboutapproval">About the project approval process</A>
		<LI><A HREF="#deferdisapprove">Deferring and disapproving projects</A>
		</UL></B>
		<DD><A HREF="DomAdminSource.html">Administering domain source code repositories</A> 
		<DD><A HREF="DomAdminAuditLogs.html">Using administrative audit logs</A>
	<DT><A HREF="/servlets/HelpTOC">Back to main Help index</A>
	</DL>
</UL>
<P>

<HR NOSHADE SIZE=1>
<A NAME="aboutapproval"></A><SPAN CLASS="InputHeader">About the project approval process</SPAN>
<P>
When a project is proposed on this site, it appears in the <I>Proposed Projects</I> link in the "Pending Actions" section of the Domain Administrator's <B>Start Page</B>. The next time you log in, this count indicates how many projects are awaiting your action. Taking no action has the same result as deferring a project; they remain effectively in limbo as pending actions.
<P>
Click the <I>Proposed Projects</I> link in the "Pending Actions" section to display the <B>Project Approval</B> page. An alphabetical listing of all pending projects appears with the proposer's name and a project summary included. Project titles link to each project's home page. The proposer's name links to the <B>Edit User</B> screen containing this user's account information.
<P>
As the Domain Administrator, you disperse with pending projects in one of three ways: approve, defer, or disapprove them by placing checkmarks in the appropriate boxes. All of these actions are tracked in an administrative audit log, along with other administrative actions. See <A HREF="DomAdminAuditLogs.html">Using administrative audit logs</A> for further information.
<P>
d45 23
a67 23
<UL>
<LI>Does the project fall within your site's overall mission and general goals?
<LI>Is the project well scoped out? 
<LI>Are project objectives clearly stated?
</UL>
<P>
When you approve a project, an email message is automatically generated notifying the Project Owner. The project appears in the site's hosted project listings, including the <B>Hosted Projects</B> page and the appropriate category home page(s). The Project Owner can now approve members and grant roles to them.
<P>

<HR NOSHADE SIZE=1>
<A NAME="deferdisapprove"></A><SPAN CLASS="InputHeader">Deferring or disapproving projects</SPAN>
<P>
While your approval of a project is pending, or when you defer approval, the project simply remains in your list of pending projects awaiting approval. It does not appear within any project listings in public pages or to any other users. The proposer, however, continues to see a link to this project in her/his <B>Start Page</B> under the "My Projects" section, and can conduct most project related activities including:
<UL>
<LI>accessing and updating their project's home page
<LI>inviting participants
<LI>uploading and downloading project files and documents
<LI>adding and editing news items
<LI>checking source code into the project's CVS repository
<LI>assigning and tracking project issues.
</UL>
None of this project information on pending projects is visible to other site users, however. And until you approve a pending project, the Project Owner <I>cannot</I> approve project members or grant roles to them.
<P>
d69 13
a81 1
<P>
d83 8
a90 8
<HR NOSHADE SIZE=1>
<A HREF="DomAdminOverview.html">Back to help for domain administration</A><BR>
<A HREF="/servlets/HelpTOC">Back to main Help index</A>
</SPAN>
</TR>
</TABLE>
</BODY>
</HTML>
@


1.1
log
@initial revision
@
text
@a7 2
<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
  <TR>
d9 3
d13 1
a13 3
<B>Help for domain administration</B>
<P>
<SPAN CLASS="Header">Approving, disapproving, or deferring projects</SPAN></BR>
a14 1

d19 1
@

