head	1.12;
access;
symbols
	TIGRIS_1_1_0RC2:1.7.6.1
	TIGRIS_1_1_0RC1:1.7.6.1
	TIGRIS_1_1:1.7.6.1.0.2
	TIGRIS_1_0_8:1.7.6.1
	TIGRIS_1_0_8RC3:1.7.6.1
	TIGRIS_1_0_8RC2:1.7.6.1
	TIGRIS_1_0_8RC1:1.7.6.1
	TIGRIS_1_0_7:1.7.6.1
	TIGRIS_1_0_7RC3:1.7.6.1
	TIGRIS_1_0_7RC2:1.7.6.1
	TIGRIS_1_0_7RC1:1.7.6.1
	TIGRIS_1_0_6:1.7.6.1
	TIGRIS_1_0_6RC5:1.7.6.1
	TIGRIS_1_0_6RC4:1.7.6.1
	TIGRIS_1_0_6RC3:1.7.6.1
	TIGRIS_1_0_6RC2:1.7.6.1
	TIGRIS_1_0_6RC1:1.7.6.1
	TIGRIS_1_0_5:1.7
	TIGRIS_1_0_5RC6:1.7
	TIGRIS_1_0_5RC5:1.7
	TIGRIS_1_0_5RC4:1.7
	TIGRIS_1_0_5RC3:1.7
	TIGRIS_1_0_5RC2:1.7
	TIGRIS_1_0_5RC1:1.7
	TIGRIS_1_0_4:1.7
	TIGRIS_1_0_3:1.7
	TIGRIS_1_0_2:1.7
	TIGRIS_1_0_1:1.7
	TIGRIS_1_0:1.7.0.6
	TIGRIS_1_0_0:1.7
	TIGRIS_1_0_0_RC1:1.7.0.2;
locks; strict;
comment	@# @;


1.12
date	2001.07.25.20.40.35;	author tberry;	state dead;
branches;
next	1.11;

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

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

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

1.8
date	2001.06.04.04.25.51;	author dlr;	state Exp;
branches;
next	1.7;

1.7
date	2001.03.27.02.23.48;	author jrobbins;	state Exp;
branches
	1.7.6.1;
next	1.6;

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

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

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

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

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

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

1.7.6.1
date	2001.06.04.04.26.24;	author dlr;	state Exp;
branches;
next	;


desc
@@


1.12
log
@removed doc cause it's no longer needed.  Replaced with ProjectAdd.html
Issue number:
Obtained from:
Submitted by:
Reviewed by:
@
text
@ 
<div class="docs" id="projectadddstep1"> 
  <h2><a id="ProjectAddFields1" name="ProjectAddFields1">Create a New Project 
    (Step 1): Defining Your Project</a></h2>
  <div class="toc"> 
    <ul>
      <li> <a href="ProjectAdd.html">Creating a New Project: Index</a> 
        <ul>
          <li><strong>You are here:</strong> Create a New Project (Step One): 
            "Project Add" fields explained</li>
          <li><a href="ProjectAddStep2.html">Create a New Project (Step Two): 
            Choosing your project's license and profile</a></li>
          <li><a href="ProjectAddStep3.html">Create a new project (Step Three): 
            Inviting people to join your project</a></li>
          <li><a href="ProjectAddConfirm.html">Project Creation Confirmation</a></li>
        </ul>
      </li>
    </ul>
  </div>
  <p>Creating a project is a three step process. In each step, you are given the 
    opportunity to configure your project. This document explains the configuration 
    items of step one in the project creation process.</p>
  <dl> 
    <dt><a id="ProjectNameField" name="ProjectNameField"><strong>Project Name</strong></a></dt>
    <dd> The project name is appears on all pages relating to the project. Choose 
      a name that will help project members and potential members to quickly identify 
      your project. Any name you select must comply with the naming conventions 
      listed below:</dd>
  </dl>
</div>
<ul>
  <ul>
    <li>project name can only be one word </li>
    <li>characters a-z (mixed case okay), 
        0-9, and dash (though not as first or last character) can be used    </li>
    <li>no punctuation, spaces, underscoring 
        or capitalization
    </li>
  </ul>
</ul>
<blockquote> 
  Once a project has been created, the 
    name cannot be changed. An example of an appropriate name for a project involving 
    porting a sophisticated chess game to the telephone is "chessphone&quot;.
</blockquote>

  <dl> 
    <dt><a id="SummaryField" name="SummaryField"><strong>Summary</strong></a></dt>
    <dd> 
      <p>Enter a one-line description of your project, no longer than 60 characters. 
        The description should be in plain text; HTML and formatted text are not 
        supported. The description will be adjacent to the name of the project 
        and be what registered users see first when they view the list of available 
        projects. It should therefore be descriptive and concise. For instance, 
        in the case of the chess game, you might write: "Porting an advanced chess 
        game to the phone". Unlike the project name, you can edit this field at 
        any time.</p>
    </dd>
    <dt><strong>Description</strong></dt>
    <dd> 
      <p>Making up the bulk of your project's home page, the description.should 
        present the project in as interesting a light as possible. You can include 
        HTML, and formatted text, though you may find simple, unformatted text 
        to have a faster loading time, and, therefore, to be of more interest 
        to your potential members. Good information to include in this section 
        include your project's mission, background, methodology, tasks available, 
        and other information that a developer might need to begin working on 
        your project. This field can be edited at any time by clicking on the 
        "Edit Project" link once you have finished creating the project.</p>
    </dd>
    <dt><strong><a id="DescriptionField" name="DescriptionField"><strong></strong></a>Use 
      Project Home</strong></dt>
    <dd>Check this box to use your project's www/index.html file as the project's 
      description. This is useful if you plan to have a complex home page. This 
      setting can be changed at any time.</dd>
    
  </dl>

<strong>NOTE:</strong> The <strong>Description</strong> 
  field and the<strong> Use Project Home</strong> checkbox perform the same function; 
  both are designed to build an informative home page for your project. The <strong>Description</strong> 
  field allows you to use the same look and feel as all other pages on the domain 
  while the <strong>Use Project Home</strong> checkbox will use a preconfigured 
  html page as the project home page.
  <dl> 
      <dd>In <a href="ProjectAddStep2.html">&quot;Create a New Project (Step 2): 
      Choosing your project's license and profile&quot;</a>, we examine the licenses 
      and profiles by which you can characterize your project.</dd>
  </dl>
  <div class="courtesylinks"> 
    <p><a href="/servlets/HelpTOC">Back to main Help index</a></p>
  </div>

 


@


1.11
log
@edited content to cover changes to the public feature.
Issue number:
Obtained from:
Submitted by:
Reviewed by:
@
text
@@


1.10
log
@html usage revision
@
text
@d1 5
a5 4
  <div class="docs" id="projectadddstep1">
   <h2><a id="ProjectAddFields1" name="ProjectAddFields1">Project Add Page Fields Explained</a></h2>

   <div class="toc">
d7 11
a17 13
     <li>
      <a href="ProjectAdd.html">Creating a New Project: Index</a> 

      <ul>
       <li><strong>You are here:</strong> Create a New Project (Step One): "Project Add" fields explained</li>

       <li><a href="ProjectAddStep2.html">Create a New Project (Step Two): Choosing your project's license and profile</a></li>

       <li><a href="ProjectAddStep3.html">Create a new project (Step Three): Inviting people to join your project</a></li>

       <li><a href="ProjectAddConfirm.html">Project Creation Confirmation</a></li>
      </ul>
     </li>
d19 39
a57 9
   </div>

   <p>The fields available on the "Start a Project" page allow you to configure your project. Below, we have explained each of the fields and their function.</p>

   <dl>
    <dt><a id="ProjectNameField" name="ProjectNameField">Project Name</a></dt>

    <dd>
     <p>Enter what you wish to call your project. Choose a name that both describes the project and conforms to the naming conventions. That is, use characters a-z (mixed case okay), 0-9, and dash (though not as first or last character); no spaces, underscoring, capitalization, or other punctuation. Keep in mind that the project name cannot be changed. An example of a name for a project dealing with porting a sophisticated chess game to the telephone might be "chessphone." Unimaginative, to be sure, but descriptive.</p>
d59 11
a69 11

    <dt><a id="SummaryField" name="SummaryField">Summary</a></dt>

    <dd>
     <p>Enter a one-line description of your project, no longer than the field length. The description should be in plain text; HTML and formatted text are not supported. The description will be adjacent to the name of the project and be what registered users see first when they view the list of available projects. It should therefore be descriptive and concise. For instance, in the case of the chess game, you might write: "Porting an advanced chess game to the phone." Unlike the project name, you can edit this field at any time.</p>
    </dd>

    <dt><a id="DescriptionField" name="DescriptionField">Description</a></dt>

    <dd>
     <p>This description makes up the bulk of your project's home page. It is where you can present the project in as interesting a light as possible. You can include HTML, formatted text, and so on, but keep in mind that most developers prefer simple and fast over complicated and slow (and confusing). State here your project's mission, background, methodology, tasks available, and other information that a developer might need to begin working on your project. This field can be edited at any time by clicking on the "Edit Project" link once you have finished creating a project, but the information should remain consistent.</p>
d71 20
a90 5
   </dl>

   <p>In <a href="ProjectAddStep2.html">"Create a New Project (Step 2): Choosing your project's license and profile"</a>, we examine the licenses and profiles by which you can characterize your project.</p>

   <div class="courtesylinks">
a91 1
   </div>
d93 1
@


1.9
log
@extensive markup rework - first pass toward house xhtmlification
@
text
@d1 2
a2 10
<!DOCTYPE html PUBLIC "-//CollabNet//DTD XHTML 1.0 Transitional//EN"
"http://collabnet.com/dtds/collabnet_transitional_10.dtd">
<html>
 <head>
  <title>Project Add Page Fields Explained</title>
<style type="text/css">
 div.c2 {margin-left: 2em}
 li.c1 {list-style: none}
</style>
 </head>
d4 4
a7 3
 <body>
  <div class="docs" id="docid">
<h2><a id="ProjectAddFields1" name="ProjectAddFields1">Project Add Page Fields Explained</a></h2>
d9 2
a10 2
  <dl>
   <dt><a href="ProjectAdd.html">Creating a New Project: Index</a></dt>
d12 1
a12 3
   <dd>
    <ol>
     <li><b>You are here: Create a New Project (Step One): "Project Add" fields explained</b></li>
d14 1
a14 1
     <li><a href="ProjectAddStep2.html">Create a New Project (Step Two): Choosing your project's license and profile</a></li>
d16 5
a20 1
     <li><a href="ProjectAddStep3.html">Create a new project (Step Three): Inviting people to join your project</a></li>
d22 1
a22 4
     <li><a href="ProjectAddConfirm.html">Project Creation Confirmation</a></li>
    </ol>
   </dd>
  </dl>
d24 2
a25 1
  <p>The fields available on the "Start a Project" page allow you to configure your project. Below, we have explained each of the fields and their function.</p>
d27 3
a29 2
  <dl>
   <dt><a id="ProjectNameField" name="ProjectNameField"></a><b>Project Name</b></dt>
d31 1
a31 3
   <dd>
    <p>Enter what you wish to call your project. Choose a name that both describes the project and conforms to the naming conventions. That is, use characters a-z (mixed case okay), 0-9, and dash (though not as first or last character); no spaces, underscoring, capitalization, or other punctuation. Keep in mind that the project name cannot be changed. An example of a name for a project dealing with porting a sophisticated chess game to the telephone might be "chessphone." Unimaginative, to be sure, but descriptive.</p>
   </dd>
d33 3
a35 1
   <dt><a id="SummaryField" name="SummaryField"></a><b>Summary</b></dt>
d37 1
a37 3
   <dd>
    <p>Enter a one-line description of your project, no longer than the field length. The description should be in plain text; HTML and formatted text are not supported. The description will be adjacent to the name of the project and be what registered users see first when they view the list of available projects. It should therefore be descriptive and concise. For instance, in the case of the chess game, you might write: "Porting an advanced chess game to the phone." Unlike the project name, you can edit this field at any time.</p>
   </dd>
d39 4
a42 1
   <dt><a id="DescriptionField" name="DescriptionField"></a><b>Description</b></dt>
d44 1
a44 4
   <dd>
    <p>This description makes up the bulk of your project's home page. It is where you can present the project in as interesting a light as possible. You can include HTML, formatted text, and so on, but keep in mind that most developers prefer simple and fast over complicated and slow (and confusing). State here your project's mission, background, methodology, tasks available, and other information that a developer might need to begin working on your project. This field can be edited at any time by clicking on the "Edit Project" link once you have finished creating a project, but the information should remain consistent.</p>
   </dd>
  </dl>
d46 3
a48 4
  <p>In <a href="ProjectAddStep2.html">"Create a New Project (Step 2): Choosing your project's license and profile"</a>, we examine the licenses and profiles by which you can characterize your project.</p>

  <div class="courtesylinks">
   <a href="/servlets/HelpTOC">Back to main Help index</a>
d50 1
a50 3
 </div>
</body>
</html>
@


1.8
log
@Dashes can no longer be used as the last character in a project name.
@
text
@d1 2
d4 7
a10 1
<head>
d12 3
a14 2
<title>Project Add Page Fields Explained</title>
<!-- Changed by: , 03-Jun-2001 -->
d16 2
a17 2
</head>
<body>
d19 11
a29 20
<span class="PlainText"><a name="ProjectAddFields1"></a> <span class="Header"><b>Project 
Add Page Fields Explained</b></span> 
<ul>
  
  <dl> 
    <dt><a href="ProjectAdd.html">Creating a New Project: Index</a></dt>
    <dd> 
      <li><b>You are here: Create a New Project (Step One): &quot;Project Add&quot; fields explained </b></li>
n    </dd>
    <dd> 
      <li><a href="ProjectAddStep2.html">Create a New Project 
        (Step Two): Choosing your project's license and profile </a></li>
    </dd>
    <dd> 
      <li><a href="ProjectAddStep3.html">Create a new project 
        (Step Three): Inviting people to join your project</a></li>
    </dd>
    <dd> 
      <li><a href="ProjectAddConfirm.html">Project Creation 
        Confirmation</a></li></dd>
d31 29
a59 42
</ul>
<p>The fields available on the &quot;Start a Project&quot; page allow you 
  to configure your project. Below, we have explained each of the fields and their 
  function. </p>
<P> 
<P> 
<blockquote><a name="ProjectNameField"></A><B>Project Name</B>
  Enter what you wish to call your project. Choose a name that both describes 
  the project and conforms to the naming conventions. That is, use
  characters a-z (mixed case okay), 0-9, and dash (though not as first
  or last character); no spaces, underscoring, capitalization, or
  other punctuation. Keep in mind that the project name cannot be
  changed.  An example of a name for a project dealing with porting a
  sophisticated chess game to the telephone might be
  &quot;chessphone.&quot; Unimaginative, to be sure, but descriptive.
  <p></P>
  <P><a name="SummaryField"></A><B>Summary</B><BR>
    Enter a one-line description of your project, no longer than the field length. 
    The description should be in plain text; HTML and formatted text are not supported. 
    The description will be adjacent to the name of the project and be what registered 
    users see first when they view the list of available projects. It should therefore 
    be descriptive and concise. For instance, in the case of the chess game, you 
    might write: &quot;Porting an advanced chess game to the phone.&quot; Unlike 
    the project name, you can edit this field at any time.</P>
  <P><a name="DescriptionField"></A><B>Description</B><BR>
    This description makes up the bulk of your project's home page. It is where 
    you can present the project in as interesting a light as possible. You can 
    include HTML, formatted text, and so on, but keep in mind that most developers 
    prefer simple and fast over complicated and slow (and confusing). State here 
    your project's mission, background, methodology, tasks available, and other 
    information that a developer might need to begin working on your project. 
    This field can be edited at any time by clicking on the &quot;Edit Project&quot; 
    link once you have finished creating a project, but the information should 
    remain consistent. 
</blockquote>
<p>In <a href="ProjectAddStep2.html">&quot;Create a New Project (Step 2): Choosing your project's 
license and profile&quot;</a>, we examine the licenses and profiles by which you can characterize your project.
<p>

<HR noShade SIZE=1>
<a href="/servlets/HelpTOC">Back to main Help index</a>
</span>
d62 2
@


1.7
log
@removed extra closing span, now the "back" link shuld show in the correct font
@
text
@d5 1
d39 7
a45 6
  the project and conforms to the naming conventions. That is, use the a-z, 0-9, 
  and dash (but not as the first character); no spaces, underscoring, capitalization, 
  or other punctuation. Keep in mind that the project name cannot be changed. 
  An example of a name for a project dealing with porting a sophisticated chess 
  game to the telephone might be &quot;chessphone.&quot; Unimaginative, to be 
  sure, but descriptive. 
@


1.7.6.1
log
@Dashes can no longer be used as the last character in a project name.
@
text
@a4 1
<!-- Changed by: , 03-Jun-2001 -->
d38 6
a43 6
  the project and conforms to the naming conventions. That is, use characters
  a-z (mixed case okay), 0-9, and dash (though not as first or last character);
  no spaces, underscoring, capitalization, or other punctuation. Keep in mind
  that the project name cannot be changed.  An example of a name for a project
  dealing with porting a sophisticated chess game to the telephone might be
  &quot;chessphone.&quot; Unimaginative, to be sure, but descriptive. 
@


1.6
log
@fixing index and formatting to conform with rest of 1.0 help docs
@
text
@d17 1
a17 1
    </dd>
a65 1
</span> 
@


1.5
log
@updated index, help toc links
@
text
@d1 2
a2 2
<HTML>
<HEAD>
d4 1
a4 1
<TITLE>Project Add Page Fields Explained</TITLE>
d6 2
a7 2
</HEAD>
<BODY>
a28 7
 <dt><SPAN class=HelptextHeader>Licenses</SPAN>
        <dt><a href="TypicalLicenses.html#Public">Public</a></dt>
	<dd><li><A href="TypicalLicenses.html#Apache">Apache</A> </li></dd>
	<dd><li><A href="TypicalLicenses.html#BSDStyleLicenses">BSD</A></li></dd>
	<dd><li><A href="TypicalLicenses.html#GPL">GNU General Public License (GPL)</A></li></dd>
    <dt><a href="#Proprietary">Private</a></dt>
	<dd><li><A href="TypicalLicenses.html#Proprietary">Proprietary</A></li></dd>
d36 1
a36 1
<BLOCKQUOTE><a name="ProjectNameField"></A><B>Project Name</B>
d63 1
a63 9
  <p><a name="URLAliasField"></A><B>URL Alias</B><BR>
    You can choose either to have your project URL hosted through the this site's domain, a third party customer's domain, or to direct your own domain name 
    (if you own one) to this site. In the latter two cases, you can direct the DNS entry to 
    this site's domain as a virtual host, so your project's page requests are handled 
    by this site's servers. Otherwise, you may leave this field blank. All projects 
    are assigned a URL as: projectname.domain.com (or net). This feature can be 
    edited later by clicking on the &quot;Edit Project&quot; link once you have 
    finished.</P>
</BLOCKQUOTE>
d67 2
d70 1
a70 2
<p>
<p><a href="/servlets/HelpTOC">Back to main Help index</a></p>
d72 2
a73 2
</BODY>
</HTML>
@


1.4
log
@revising document index and links
@
text
@a7 2
<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
  <TR>
d14 1
a14 1
    <dt><b>Creating a New Project: Index</b></dt>
d16 1
a16 1
      <li><b>Create a New Project (Step One): &quot;Project Add&quot; fields explained </b></li>
d84 1
a84 1
<p><a href="Help.html">Back to main Help index</a></p>
a85 2
</TR>
</TABLE>
@


1.3
log
@added <title> tags to all files
@
text
@d16 1
a16 1
    <dt>Creating a New Project Index</dt>
d29 1
a29 1
      <li><a href="#ProjectAddStep4.html">Project Creation 
@


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


1.1
log
@new and revised help documentation for v1.0
@
text
@d1 82
a82 82
<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
  <TR>

<span class="PlainText"><a name="ProjectAddFields1"></a> <span class="Header"><b>Project 
Add Page Fields Explained</b></span> 
<ul>
  
  <dl> 
    <dt>Creating a New Project Index</dt>
    <dd> 
      <li><b>Create a New Project (Step One): &quot;Project Add&quot; fields explained </b></li>
    </dd>
    <dd> 
      <li><a href="ProjectAddStep2.html">Create a New Project 
        (Step Two): Choosing your project's license and profile </a></li>
    </dd>
    <dd> 
      <li><a href="ProjectAddStep3.html">Create a new project 
        (Step Three): Inviting people to join your project</a></li>
    </dd>
    <dd> 
      <li><a href="#ProjectAddStep4.html">Project Creation 
        Confirmation</a></li></dd>
 <dt><SPAN class=HelptextHeader>Licenses</SPAN>
        <dt><a href="TypicalLicenses.html#Public">Public</a></dt>
	<dd><li><A href="TypicalLicenses.html#Apache">Apache</A> </li></dd>
	<dd><li><A href="TypicalLicenses.html#BSDStyleLicenses">BSD</A></li></dd>
	<dd><li><A href="TypicalLicenses.html#GPL">GNU General Public License (GPL)</A></li></dd>
    <dt><a href="#Proprietary">Private</a></dt>
	<dd><li><A href="TypicalLicenses.html#Proprietary">Proprietary</A></li></dd>
  </dl>
</ul>
<p>The fields available on the &quot;Start a Project&quot; page allow you 
  to configure your project. Below, we have explained each of the fields and their 
  function. </p>
<P> 
<P> 
<BLOCKQUOTE><a name="ProjectNameField"></A><B>Project Name</B>
  Enter what you wish to call your project. Choose a name that both describes 
  the project and conforms to the naming conventions. That is, use the a-z, 0-9, 
  and dash (but not as the first character); no spaces, underscoring, capitalization, 
  or other punctuation. Keep in mind that the project name cannot be changed. 
  An example of a name for a project dealing with porting a sophisticated chess 
  game to the telephone might be &quot;chessphone.&quot; Unimaginative, to be 
  sure, but descriptive. 
  <p></P>
  <P><a name="SummaryField"></A><B>Summary</B><BR>
    Enter a one-line description of your project, no longer than the field length. 
    The description should be in plain text; HTML and formatted text are not supported. 
    The description will be adjacent to the name of the project and be what registered 
    users see first when they view the list of available projects. It should therefore 
    be descriptive and concise. For instance, in the case of the chess game, you 
    might write: &quot;Porting an advanced chess game to the phone.&quot; Unlike 
    the project name, you can edit this field at any time.</P>
  <P><a name="DescriptionField"></A><B>Description</B><BR>
    This description makes up the bulk of your project's home page. It is where 
    you can present the project in as interesting a light as possible. You can 
    include HTML, formatted text, and so on, but keep in mind that most developers 
    prefer simple and fast over complicated and slow (and confusing). State here 
    your project's mission, background, methodology, tasks available, and other 
    information that a developer might need to begin working on your project. 
    This field can be edited at any time by clicking on the &quot;Edit Project&quot; 
    link once you have finished creating a project, but the information should 
    remain consistent. 
  <p><a name="URLAliasField"></A><B>URL Alias</B><BR>
    You can choose either to have your project URL hosted through the this site's domain, a third party customer's domain, or to direct your own domain name 
    (if you own one) to this site. In the latter two cases, you can direct the DNS entry to 
    this site's domain as a virtual host, so your project's page requests are handled 
    by this site's servers. Otherwise, you may leave this field blank. All projects 
    are assigned a URL as: projectname.domain.com (or net). This feature can be 
    edited later by clicking on the &quot;Edit Project&quot; link once you have 
    finished.</P>
</BLOCKQUOTE>
<p>In <a href="ProjectAddStep2.html">&quot;Create a New Project (Step 2): Choosing your project's 
license and profile&quot;</a>, we examine the licenses and profiles by which you can characterize your project.
</span> 
<HR noShade SIZE=1>
<p>
<p><a href="Help.html">Back to main Help index</a></p>
</span>
</TR>
</TABLE>
@

