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


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

1.11
date	2001.07.12.21.54.06;	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.04.05.22.19.19;	author dlr;	state Exp;
branches;
next	1.7;

1.7
date	2001.03.13.07.06.19;	author lori;	state Exp;
branches
	1.7.2.1;
next	1.6;

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

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

1.4
date	2001.02.21.00.47.41;	author susank;	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.45.15;	author lori;	state Exp;
branches;
next	;

1.7.2.1
date	2001.04.05.22.19.43;	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="projectaddstep2">
   
  <h2><a id="ProjectAddStep2" name="ProjectAddStep2">Create a New Project (Step 
    2): Configuring Your Project</a></h2>

   <div class="toc">
    <ul>
     <li>
      <a href="ProjectAdd.html">Creating a New Project: Index</a> 

      <ul>
       <li><a href="ProjectAddStep1.html">Create a New Project (Step One): "Project Add" fields explained</a></li>

       <li><strong>You are here:</strong>Create a New Project (Step Two): Choosing your project's license and profile</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>
  <dl> 
    <dt><a id="LicenseField" name="LicenseField"><strong>License</strong></a></dt>
    <dd> 
      <p>Choose the license you wish to apply to the project. While there is a 
        core set of licenses available to select from, you may find that your 
        administrator has added licenses created specifically for the needs of 
        project owners on this site. Once your project is approved, you can switch 
        licenses as you find necessary. To edit this feature of your project, 
        you need to click on<em> Edit Project</em> link, once you have finished 
        the process of creating the project. If you wish more information on the 
        default set of licenses, please see the "<a href="TypicalLicenses.html">Licenses</a>" 
        section.</p>
    </dd>
    <dt><a id="PublicProject" name="PublicProject"><strong>Public Project</strong></a></dt>
    <dd>If you would like to have your project viewable by anyone in your domain, 
      check this box. Leaving the box empty will require you to send invitations 
      to potential members.</dd>
    <dt>&nbsp;</dt>
    <dt><strong>Project Owner</strong></dt>
    <dd><strong></strong></dd>
    <dd> 
      <p>While this field defaults to your username, you can add or edit project 
        owners based on your needs.</p>
    </dd>
    
  </dl>

   <p>In <a href="ProjectAddStep3.html">Create a new project (Step Three): Inviting people to join your project</a>, we go through the page fields for inviting people to your project.</p>

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


@


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


1.10
log
@html usage revision
@
text
@d2 3
a4 1
   <h2><a id="ProjectAddStep2" name="ProjectAddStep2">Create a New Project (Step 2): Choosing your project's license and profile</a></h2>
d23 12
a34 6

   <dl>
    <dt><a id="LicenseField" name="LicenseField">License</a></dt>

    <dd>
     <p>Choose the license you wish to apply to the project. Licenses can range from the open source GPL to proprietary. Once your project is approved, you cannot switch from an open-source model to a proprietary one. However, proprietary projects can choose to go open source. To edit this feature of your project, you need to click on "Edit Project" link, once you have finished the process of creating the project. If you wish more information on your licensing options, please see the "<a href="TypicalLicenses.html">Licenses</a>" section.</p>
d36 10
a45 11

    <dt><a id="ProjectCategoryField" name="ProjectCategoryField">Project Category</a></dt>

    <dd>
     <p>Select the category appropriate for your project. Because projects are listed by category in both the Start Page and Project Home pages, the choice of category is critical for giving developers a sense of the kind of work available. A developer who specializes in games, for example, will not necessarily want to view projects in the productivity category. As you can see, there are many possible options, and if you end up preferring another category, you can change your project category at any time. To edit this features of your project, click on "Edit Project" once you have finished creating the project.</p>
    </dd>

    <dt><a id="ProjectProfileField" name="ProjectProfileField">Project Profile</a></dt>

    <dd>
     <p>The Project Profile buttons are configured to automatically create mailing lists for your particular project. Perhaps you have a project idea that will require much discussion and input from other developers well before getting to the point of actual source code; this would be a "Discussion project." If your project, on the other hand, involves reworking existing source code, choose "Standard development project." Selecting a content project generates one general mailing list; you would not have access to the issue-tracking system because it would not be necessary. Selecting the standard project profile generates five mailing lists, and gives you access to all of the other resources of the site, including issue tracking. It is important to stress that no matter what profile you choose, you can change it later.</p>
d47 2
a48 1
   </dl>
@


1.9
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>Create a New Project (Step 2)</title>
<style type="text/css">
 div.c1 {margin-left: 2em}
</style>
 </head>
d4 4
a7 3
 <body>
  <div class="docs" id="docid">
<h2><a id="ProjectAddStep2" name="ProjectAddStep2">Create a New Project (Step 2): Choosing your project's license and profile</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><a href="ProjectAddStep1.html">Create a New Project (Step One): "Project Add" fields explained</a></li>
d14 1
a14 1
     <li><b>You are here: Create a New Project (Step Two): Choosing your project's license and profile</b></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 2
a23 4
     <li><a href="ProjectAddConfirm.html">Project Creation Confirmation</a></li>
    </ol>
   </dd>
  </dl>
d25 3
a27 2
  <dl>
   <dt><a id="LicenseField" name="LicenseField"></a><b>License</b></dt>
d29 1
a29 3
   <dd>
    <p>Choose the license you wish to apply to the project. Licenses can range from the open source GPL to proprietary. Once your project is approved, you cannot switch from an open-source model to a proprietary one. However, proprietary projects can choose to go open source. To edit this feature of your project, you need to click on "Edit Project" link, once you have finished the process of creating the project. If you wish more information on your licensing options, please see the "<a href="TypicalLicenses.html">Licenses</a>" section.</p>
   </dd>
d31 3
a33 1
   <dt><a id="ProjectCategoryField" name="ProjectCategoryField"></a><b>Project Category</b></dt>
d35 1
a35 3
   <dd>
    <p>Select the category appropriate for your project. Because projects are listed by category in both the Start Page and Project Home pages, the choice of category is critical for giving developers a sense of the kind of work available. A developer who specializes in games, for example, will not necessarily want to view projects in the productivity category. As you can see, there are many possible options, and if you end up preferring another category, you can change your project category at any time. To edit this features of your project, click on "Edit Project" once you have finished creating the project.</p>
   </dd>
d37 4
a40 1
   <dt><a id="ProjectProfileField" name="ProjectProfileField"></a><b>Project Profile</b></dt>
d42 1
a42 4
   <dd>
    <p>The Project Profile buttons are configured to automatically create mailing lists for your particular project. Perhaps you have a project idea that will require much discussion and input from other developers well before getting to the point of actual source code; this would be a "Discussion project." If your project, on the other hand, involves reworking existing source code, choose "Standard development project." Selecting a content project generates one general mailing list; you would not have access to the issue-tracking system because it would not be necessary. Selecting the standard project profile generates five mailing lists, and gives you access to all of the other resources of the site, including issue tracking. It is important to stress that no matter what profile you choose, you can change it later.</p>
   </dd>
  </dl>
d44 3
a46 4
  <p>In <a href="ProjectAddStep3.html">Create a new project (Step Three): Inviting people to join your project</a>, we go through the page fields for inviting people to your project.</p>

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


1.8
log
@Corrected broken link (thanks Kat).
@
text
@d1 2
d4 6
a9 1
<head>
d11 3
a13 2
<title>Create a New Project (Step 2)</title>
<!-- Changed by: , 05-Apr-2001 -->
d15 2
a16 2
</head>
<body>
d18 31
a48 21
<span class="PlainText">
 <a name="ProjectAddStep2"></a>
 <p><span class="Header"><b>Create a New Project (Step 2): Choosing your project's license and profile</b></span>
<ul>
  
  <dl> 
    <dt><a href="ProjectAdd.html">Creating a New Project: Index</a></dt>
    <dd> 
      <li><a href="ProjectAddStep1.html">Create a New Project (Step One): &quot;Project Add&quot; fields explained</a> </li>
    </dd>
    <dd> 
      <li><b>You are here: Create a New Project 
        (Step Two): Choosing your project's license and profile</b> </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>
d50 7
a56 39
</ul>
<blockquote> 
  <P><a name="LicenseField"></A><B>License</B><BR>
    Choose the license you wish to apply to the project. Licenses can range from 
    the open source GPL to proprietary. Once your project is approved, you cannot 
    switch from an open-source model to a proprietary one. However, proprietary 
    projects can choose to go open source. To edit this feature of your project, 
    you need to click on &quot;Edit Project&quot; link, once you have finished 
    the process of creating the project. If you wish more information on your 
    licensing options, please see the &quot;<a href="TypicalLicenses.html">Licenses</a>&quot; 
    section.</p>
  <P><a name="ProjectCategoryField"></A><B>Project Category</B><BR>
    Select the category appropriate for your project. Because projects are listed 
    by category in both the Start Page and Project Home pages, the choice of category 
    is critical for giving developers a sense of the kind of work available. A 
    developer who specializes in games, for example, will not necessarily want 
    to view projects in the productivity category. As you can see, there are many 
    possible options, and if you end up preferring another category, you can change 
    your project category at any time. To edit this features of your project, 
    click on &quot;Edit Project&quot; once you have finished creating the project.</p>
  <P><a name="ProjectProfileField"></A><B>Project Profile</B><BR>
    The Project Profile buttons are configured to automatically create mailing 
    lists for your particular project. Perhaps you have a project idea that will 
    require much discussion and input from other developers well before getting 
    to the point of actual source code; this would be a "Discussion project." 
    If your project, on the other hand, involves reworking existing source code, 
    choose "Standard development project." Selecting a content project generates 
    one general mailing list; you would not have access to the issue-tracking 
    system because it would not be necessary. Selecting the standard project profile 
    generates five mailing lists, and gives you access to all of the other resources 
    of the site, including issue tracking. It is important to stress that no matter 
    what profile you choose, you can change it later.</p>
</blockquote>
<p>In <a href="ProjectAddStep3.html">Create a new project (Step Three): Inviting people to join your project</a>, we go through the page fields for inviting people to your project.
<p>

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


1.7
log
@fixing index and formatting to conform with rest of 1.0 help docs
@
text
@d5 1
d41 1
a41 1
    licensing options, please see the &quot;<a href="#TypicalLicenses.html">Licenses</a>&quot; 
@


1.7.2.1
log
@Corrected broken link (thanks Kat).
@
text
@a4 1
<!-- Changed by: , 05-Apr-2001 -->
d40 1
a40 1
    licensing options, please see the &quot;<a href="TypicalLicenses.html">Licenses</a>&quot; 
@


1.6
log
@updated index, help toc links
@
text
@d1 2
a2 2
<HTML>
<HEAD>
d4 1
a4 1
<TITLE>Create a New Project (Step 2)</TITLE>
d6 2
a7 2
</HEAD>
<BODY>
a29 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>
d32 1
a32 1
<BLOCKQUOTE> 
d63 1
a63 1
</BLOCKQUOTE>
d65 2
d68 1
a68 1
<p><a href="/servlets/HelpTOC">Back to main Help index</a></p>
d70 2
a71 2
</BODY>
</HTML>
@


1.5
log
@revising document index and links
@
text
@a7 2
<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
  <TR>
d11 1
a11 2
 <p><span class="Header"><b>Create a New Project (Step 2): Choosing your project's 
license and profile</b></span><br>
d15 1
a15 1
    <dt><b>Creating a New Project: Index</b></dt>
d20 1
a20 1
      <li><b>Create a New Project 
d73 1
a73 1
<p><a href="Help.html">Back to main Help index</a></p>
a74 2
</TR>
</TABLE>
@


1.4
log
@removed link around ProjectAddStep2 link, within its own page
PR:
Obtained from:
Submitted by:
Reviewed by:
@
text
@d18 1
a18 1
    <dt>Creating a New Project Index</dt>
d23 2
a24 2
      <li>Create a New Project 
        (Step Two): Choosing your project's license and profile </li>
d31 1
a31 1
      <li><a href="#ProjectAddStep4.html">Project Creation 
@


1.3
log
@added <title> tags to all files
@
text
@d23 2
a24 2
      <li><a href="#LicenseField">Create a New Project 
        (Step Two): Choosing your project's license and profile</a> </li>
@


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
d80 2
@


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

<span class="PlainText">
 <a name="ProjectAddStep2"></a>
 <p><span class="Header"><b>Create a New Project (Step 2): Choosing your project's 
license and profile</b></span><br>
<ul>
  
  <dl> 
    <dt>Creating a New Project Index</dt>
    <dd> 
      <li><a href="ProjectAddStep1.html">Create a New Project (Step One): &quot;Project Add&quot; fields explained</a> </li>
    </dd>
    <dd> 
      <li><a href="#LicenseField">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>
<BLOCKQUOTE> 
  <P><a name="LicenseField"></A><B>License</B><BR>
    Choose the license you wish to apply to the project. Licenses can range from 
    the open source GPL to proprietary. Once your project is approved, you cannot 
    switch from an open-source model to a proprietary one. However, proprietary 
    projects can choose to go open source. To edit this feature of your project, 
    you need to click on &quot;Edit Project&quot; link, once you have finished 
    the process of creating the project. If you wish more information on your 
    licensing options, please see the &quot;<a href="#TypicalLicenses.html">Licenses</a>&quot; 
    section.</p>
  <P><a name="ProjectCategoryField"></A><B>Project Category</B><BR>
    Select the category appropriate for your project. Because projects are listed 
    by category in both the Start Page and Project Home pages, the choice of category 
    is critical for giving developers a sense of the kind of work available. A 
    developer who specializes in games, for example, will not necessarily want 
    to view projects in the productivity category. As you can see, there are many 
    possible options, and if you end up preferring another category, you can change 
    your project category at any time. To edit this features of your project, 
    click on &quot;Edit Project&quot; once you have finished creating the project.</p>
  <P><a name="ProjectProfileField"></A><B>Project Profile</B><BR>
    The Project Profile buttons are configured to automatically create mailing 
    lists for your particular project. Perhaps you have a project idea that will 
    require much discussion and input from other developers well before getting 
    to the point of actual source code; this would be a "Discussion project." 
    If your project, on the other hand, involves reworking existing source code, 
    choose "Standard development project." Selecting a content project generates 
    one general mailing list; you would not have access to the issue-tracking 
    system because it would not be necessary. Selecting the standard project profile 
    generates five mailing lists, and gives you access to all of the other resources 
    of the site, including issue tracking. It is important to stress that no matter 
    what profile you choose, you can change it later.</p>
</BLOCKQUOTE>
<p>In <a href="ProjectAddStep3.html">Create a new project (Step Three): Inviting people to join your project</a>, we go through the page fields for inviting people to your project.
<HR noShade SIZE=1>
<p><a href="Help.html">Back to main Help index</a></p>
</span>
</TR>
</TABLE>
@

