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


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

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

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

1.10
date	2001.03.16.21.22.05;	author lori;	state Exp;
branches
	1.10.6.1;
next	1.9;

1.9
date	2001.03.12.08.31.37;	author lori;	state Exp;
branches;
next	1.8;

1.8
date	2001.03.10.01.31.50;	author tberry;	state Exp;
branches;
next	1.7;

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

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

1.5
date	2001.02.15.21.43.22;	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.27;	author lori;	state Exp;
branches;
next	1.1;

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

1.10.6.1
date	2001.06.13.00.35.08;	author lori;	state Exp;
branches;
next	;


desc
@@


1.13
log
@html usage revision
@
text
@  <div class="docs" id="projectowneradmin">
   <h2>Project owner administration</h2>

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

    <ul>
     <li>
      <strong>You are here:</strong> Project owner administration 

      <ul>
       <li><a href="#aboutprojadmin">About project administration on this site</a></li>

       <li><a href="#projmgmtguidelines">Project management and leadership guidelines</a></li>
      </ul>

      <ul>
       <li><a href="ProjectOwnerEdit.html">Editing and maintaining the Project Home page</a></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="aboutprojadmin" name="aboutprojadmin">About project administration on this site</a></h3>

   <p>As a Project Owner with one or more development projects hosted on this site, your administrative tasks are organized around the same project pages viewed by other project members or registered users. You access these same project pages as any project member or registered user, however, your page view may include additional administrative links and options. Your Project Resources toolbar also includes an additional <i>Admin</i> link enabling you to edit your project home page and appearance throughout the site.</p>

   <p>If your project's approval is pending, you still have access to most features and tools to help you get established and set up. Because the hosted tools for projects are automatically configured upon project creation, you may:</p>

   <ul>
    <li>invite additional developer participants</li>

    <li>update your project's home page</li>

    <li>publish project news</li>

    <li>upload project files and documents</li>

    <li>post to your project's mailing lists</li>

    <li>create subdirectories in your project's CVS repository</li>

    <li>check in source code</li>

    <li>use the issue tracker to enter and search project issues.</li>
   </ul>

   <p>While still in a pending approval status you cannot perform the following tasks:</p>

   <ul>
    <li>add project members</li>

    <li>approve project membership requests</li>

    <li>grant project roles.</li>
   </ul>

   <h3><a id="projmgmtguidelines" name="projmgmtguidelines">Project management and leadership guidelines</a></h3>

   <p>The help documents in this section cover this site's administrative functions available to you as a Project Owner. How you use this functionality to structure and lead your project toward achieving particular goals remains largely in your purview. Whenever possible, these help documents suggest the implications of administrative options with respect to project leadership and management.</p>

   <p>Project type will strongly influence the method in which you manage projects. If your project is a proprietary endeavor with commercial licensing, project governance may be largely determined by external factors, for example: corporate strategy, fiscal priorities, organizational structure, and established development methods. While many collaborative development practices can be successfully adopted within this framework, final decision making authority rests with the license holder and influences the development schedule and project goals to a high degree.</p>

   <p>If your project is under open source licensing, the development culture is intrinsically different and far more self determinant. The Project owner -- equipped with some knowledge and understanding of open source practices -- is responsible for establishing and communicating the project's parameters up front. As the project progresses, the project owner will need to nurture project participants toward an increasing sense of community and ownership.</p>

   <p>A third possibility is a combination of the above, that is, you are leading an open source project with the involvement and support of a corporate entity embracing open source to achieve certain business goals. In these circumstances, as the project owner you essentially function as the liaison between two cultures.</p>

   <p>Whichever scenario applies, answering the questions below will help you to communicate the fundamental purpose and structure of the project to members and potential participants. While these questions are geared towards open source projects, most can be applied to collaborative and proprietary projects as well. Consider the following:</p>

   <ul>
    <li>What is the ultimate mission of the project?</li>

    <li>What decision making and conflict resolution methodology will be used for the project(for example, voting, consensus building, or final authority)?</li>

    <li>What coding standards will be used for the project (for example, adherence to certain conventions and/or emphasis on particular architectural characteristics)?</li>

    <li>What methods will be used to help project members gain responsibility and ownership within the project (for example, how can developers' roles evolve to earn more privileges such as becoming module leaders)?</li>

    <li>What are the terms for accepting contributions (for example, as defined by the licensing, but also how are non-member ideas or bug-fixes dealt with)?</li>
   </ul>

   <p>To learn more about managing collaborative development in commercial development, see the following <a href="http://navigation.helper.realnames.com/framer/1/1/default.asp?realname=Information+Week&amp;url=http%3A%2F%2Fwww%2Einformationweek%2Ecom&amp;frameid=1&amp;providerid=1&amp;uid=30013699">"The Customer as Co-Developer"</a>, by Christopher Locke in InformationWeek (PDF).</p>

   <p>To learn more about leading open source development efforts see<a href="http://sern.ucalgary.ca/%7Emaurer/ICSE99WS/Submissions/Cubranic/Cubranic.html">"Open-Source Software Development"</a>, by Davor Cubranic, University of British Columbia.</p>

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


@


1.12
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 Owner Administration</title>
<style type="text/css">
 div.c2 {margin-left: 2em}
 dt.c1 {font-weight: bold}
</style>
 </head>
d4 2
a5 3
 <body>
  <div class="docs" id="docid">
<h2>Project owner administration</h2> 
d7 3
a9 1
  <p><b>Project help for project owner administration: Index</b></p>
d11 2
a12 1
  
d14 2
a15 3
  <div class="c2">
   <dl>
    <dt>You are here: Project owner administration</dt>
d17 2
a18 3
    <dd>
     <ul>
      <li><a href="#aboutprojadmin"><b>About project administration on this site</b></a></li>
d20 1
a20 3
      <li><a href="#projmgmtguidelines"><b>Project management and leadership guidelines</b></a></li>
     </ul>
    </dd>
d22 1
a22 1
    <dd><a href="ProjectOwnerEdit.html">Editing and maintaining the Project Home page</a></dd>
d24 1
a24 1
    <dd><a href="ProjectOwnerNews.html">Managing project site news</a></dd>
d26 1
a26 1
    <dd><a href="ProjectOwnerFiles.html">Managing project files</a></dd>
d28 1
a28 1
    <dd><a href="ProjectOwnerMembers.html">Adding project members and approving roles</a></dd>
d30 1
a30 1
    <dd><a href="ProjectOwnerMailingLists.html">Configuring and managing project mailing lists</a></dd>
d32 5
a36 1
    <dd><a href="ProjectOwnerDocuments.html">Managing project documentation</a></dd>
d38 3
a40 1
    <dd><a href="ProjectOwnerSource.html">Managing project source code</a></dd>
d42 1
a42 1
    <dd><a href="ProjectOwnerIssues.html">Tracking project issues</a></dd>
d44 1
a44 5
    <dt><a href="/servlets/HelpTOC">Back to the main Help index</a></dt>
   </dl>
  </div>
  
  <h3><a id="aboutprojadmin" name="aboutprojadmin">About project administration on this site</a></h3>
d46 1
a46 1
  <p>As a Project Owner with one or more development projects hosted on this site, your administrative tasks are organized around the same project pages viewed by other project members or registered users. You access these same project pages as any project member or registered user, however,&#160;your page view may include additional administrative links and options.&#160; Your Project Resources toolbar also includes an additional <i>Admin</i> link enabling you to edit your project home page and appearance throughout the site.</p>
d48 2
a49 1
  <p>If your project's approval is pending, you still have access to most features and tools to help you get established and set up. Because the hosted tools for projects are automatically configured upon project creation, you may:</p>
d51 1
a51 2
  <ul>
   <li>invite additional developer participants</li>
d53 1
a53 1
   <li>update your project's home page</li>
d55 1
a55 1
   <li>publish project news</li>
d57 1
a57 1
   <li>upload project files and documents</li>
d59 1
a59 1
   <li>post to your project's mailing lists</li>
d61 1
a61 1
   <li>create subdirectories in your project's CVS repository</li>
d63 2
a64 1
   <li>check in source code</li>
d66 1
a66 2
   <li>use the issue tracker to enter and search project issues.</li>
  </ul>
d68 2
a69 1
  <p>While still in a pending approval status you cannot perform the following tasks:</p>
d71 1
a71 2
  <ul>
   <li>add project members</li>
d73 2
a74 1
   <li>approve project membership requests</li>
d76 1
a76 4
   <li>grant project roles.</li>
  </ul>
  
  <h3><a id="projmgmtguidelines" name="projmgmtguidelines">Project management and leadership guidelines</a></h3>
d78 1
a78 1
  <p>The help documents in this section cover this site's administrative functions available to you as a Project Owner. How you use this functionality to structure and lead your project toward achieving particular goals remains largely in your purview. Whenever possible, these help documents suggest the implications of administrative options with respect to project leadership and management.</p>
d80 1
a80 1
  <p>Project type will strongly influence the method in which you manage projects.&#160; If your project is a proprietary endeavor with commercial licensing, project governance may be largely determined by external factors, for example: corporate strategy, fiscal priorities, organizational structure, and established development methods. While many collaborative development practices can be successfully adopted within this framework, final decision making authority rests with the license holder and influences the development schedule and project goals to a high degree.</p>
d82 1
a82 1
  <p>If your project is under open source licensing, the development culture is intrinsically different and far more self determinant. The Project owner -- equipped with some knowledge and understanding of open source practices -- is responsible for&#160;establishing and communicating&#160;the project's parameters up front. As the project progresses, the project owner will need to&#160;nurture project participants toward an increasing sense of community and ownership.</p>
d84 1
a84 1
  <p>A third possibility is a combination of the above, that is, you are leading an open source project with the involvement and support of a corporate entity embracing open source to achieve certain business goals. In these circumstances, as the project owner you essentially function as the liaison between two cultures.</p>
d86 1
a86 1
  <p>Whichever scenario applies,&#160;answering&#160;the questions below will help you to communicate&#160;the&#160;fundamental purpose and structure of the project to members and potential participants. While these questions are geared towards open source projects,&#160;most can be applied&#160;to collaborative and proprietary projects as well. Consider the following:</p>
d88 2
a89 2
  <ul>
   <li>What is the ultimate mission of the project?</li>
d91 1
a91 1
   <li>What decision making and conflict resolution methodology&#160;will be used for the project(for example, voting, consensus building, or final authority)?&#160;</li>
d93 1
a93 1
   <li>What coding standards will be used&#160; for the project (for example, adherence to certain conventions and/or emphasis on particular architectural characteristics)?</li>
d95 1
a95 1
   <li>What methods will be used to help project members&#160;gain&#160;responsibility and&#160;ownership within the project (for example, how can developers' roles evolve to earn more privileges such as becoming module leaders)?</li>
d97 2
a98 2
   <li>What are the terms for accepting contributions (for example, as defined by the licensing, but also how are non-member ideas or bug-fixes dealt with)?</li>
  </ul>
d100 1
a100 1
  <p>To learn more about managing collaborative development in commercial development, see the following <a href="http://navigation.helper.realnames.com/framer/1/1/default.asp?realname=Information+Week&amp;url=http%3A%2F%2Fwww%2Einformationweek%2Ecom&amp;frameid=1&amp;providerid=1&amp;uid=30013699">"The Customer as Co-Developer"</a>, by Christopher Locke in InformationWeek (PDF).</p>
d102 1
a102 2
  <p>To learn more about leading open source development efforts see<a href="http://sern.ucalgary.ca/%7Emaurer/ICSE99WS/Submissions/Cubranic/Cubranic.html">"Open-Source Software Development"</a>, by Davor Cubranic, University of British Columbia.
  </p>
d104 5
a108 8
  
  
<div class="courtesylinks"><a href="/servlets/HelpTOC">Back to main Help index</a></div>

   
 </div>
</body>
</html>
@


1.11
log
@added doc section heads to doc index
@
text
@d1 2
d4 7
a10 1
<head>
d12 3
a14 1
<title>Project Owner Administration</title>
d16 1
a16 2
</head>
<body>
d18 66
a83 51
<span class="Header" nowrap>Project owner administration</span> 
<p> 
<span class="PLAINTEXT"><b>Project help for project owner administration: Index</b>
<p>

<ul>
<dl>
<dt><b>You are here: Project owner administration</b>
<ul>
<li><a href="#aboutprojadmin"><b>About project administration on this site</b></a></li>
<li><a href="#projmgmtguidelines"><b>Project management and leadership guidelines</b></a></li>
</ul>
<dd><a href="ProjectOwnerEdit.html">Editing and maintaining the Project Home page</a>
<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>
</dl>
</ul>

<hr noshade size=1>
<a name="aboutprojadmin"><span class="InputHeader">About project administration on this site</span>
<p>
As a Project Owner with one or more development projects 
hosted on this site, your administrative tasks are organized around the same 
project pages viewed by other project members or registered users. You access 
these same project pages as any project member or registered user, 
however,&nbsp;your page view may include additional administrative links and 
options.&nbsp; Your Project Resources toolbar also includes an additional 
<i>Admin </i>     link enabling you to edit your project home page and appearance throughout the site.
<p>
              If your project's approval is pending, you still have access to most features and tools to help you get established and set up. Because the hosted tools for projects are automatically configured upon project creation, you may:
<ul>
<li>invite additional developer participants
<li>update your project's home page
<li>publish project news
<li>upload project files and documents
<li>post to your project's mailing lists
<li>create subdirectories in your project's CVS repository
<li>check in source code
<li>use the issue tracker to enter and search project 
  issues.</li>          
</ul>
<p>While still in a pending approval status you cannot perform the following tasks:</p>
<ul><p><li>add project members
<li>approve project membership requests
  <li>grant project roles. </li>     
d85 12
a96 1
<p></p>
d98 2
a99 45
<hr noshade size=1>
<a name="projmgmtguidelines"><span class="InputHeader">Project management and leadership guidelines</span>
<p>
The help documents in this section cover this site's administrative functions available to you as a Project Owner. How you use this functionality to structure and lead your project toward achieving particular goals remains largely in your purview. Whenever possible, these help documents suggest the implications of administrative options with respect to project leadership and management.
<p>
Project type will strongly influence the method in which you manage projects.&nbsp; If your project is a proprietary endeavor with commercial licensing, project  governance may be largely determined by external factors, for example: corporate strategy, fiscal priorities, organizational structure, and established development methods. While many collaborative development practices can be successfully adopted within this framework, final decision making authority rests with the license holder and influences the development schedule and project goals to a high degree.
<p>
If your project is under open source licensing, the development culture is intrinsically different and far more self determinant. The Project owner -- equipped with some knowledge and understanding of open source practices -- is responsible for&nbsp;establishing and communicating&nbsp;the project's parameters up front. As the project progresses, the project owner will need to&nbsp;nurture project participants toward an increasing sense of community and ownership.
<p>
A third possibility is a combination of the above, that is, you are leading an open source project with the involvement and support of a corporate entity embracing open source to achieve certain business goals. In these circumstances, as the project owner you essentially function as the liaison between two cultures.
<p>
Whichever scenario applies,&nbsp;answering&nbsp;the 
questions below will help you to communicate&nbsp;the&nbsp;fundamental purpose and structure of the project to members and potential participants. While these questions are geared towards open source projects,&nbsp;most can be applied&nbsp;to collaborative and proprietary projects as well. Consider the following:
<p>
<ul>
<li>What is the ultimate mission of the project?
<p></p>
<li>What decision making and conflict resolution methodology&nbsp;will be used for the project(for example, voting, consensus building, or final authority)?&nbsp;
<p></p>
<li>What coding standards will be used&nbsp; for the project (for example, adherence to certain conventions and/or emphasis on particular architectural characteristics)?
<p></p>
<li>What methods will be used to help project 
  members&nbsp;gain&nbsp;responsibility and&nbsp;ownership within the project (for example, how can developers' roles evolve to earn more privileges such as becoming module leaders)?
<p></p>
<li>What are the terms for accepting contributions (for 
  example, as defined by the licensing, but also how are non-member ideas or 
  bug-fixes dealt with)?</li>                       
</ul>
<p>
To learn more about managing collaborative development in 
commercial development, see the following 
<a href="http://navigation.helper.realnames.com/framer/1/1/default.asp?realname=Information+Week&amp;url=http%3A%2F%2Fwww%2Einformationweek%2Ecom&amp;frameid=1&amp;providerid=1&amp;uid=30013699" target="_new">"The Customer as Co-Developer"</a>, by Christopher Locke in 
InformationWeek (PDF).</p><a 
href="http://navigation.helper.realnames.com/framer/1/1/default.asp?realname=Information+Week&amp;url=http%3A%2F%2Fwww%2Einformationweek%2Ecom&amp;frameid=1&amp;providerid=1&amp;uid=30013699" target="_new"></a>
<p>
To learn more about leading open source development 
efforts see<a 
href="http://sern.ucalgary.ca/%7Emaurer/ICSE99WS/Submissions/Cubranic/Cubranic.html" target="_new">"Open-Source 
Software Development"</a>, by Davor Cubranic, University of British 
Columbia.<br>
<p>

<hr noshade size=1>
<a href="/servlets/HelpTOC">Back to main Help index</a></p>
</span>
d101 20
d123 2
@


1.10
log
@incorporated tberry edits and other minor html changes
@
text
@d17 4
d34 1
a34 1
<span class="InputHeader">About project administration on this site</span>
d64 1
a64 1
<span class="InputHeader">Project management and leadership guidelines</span>
@


1.10.6.1
log
@updating branch with latest help files
@
text
@a16 4
<ul>
<li><a href="#aboutprojadmin"><b>About project administration on this site</b></a></li>
<li><a href="#projmgmtguidelines"><b>Project management and leadership guidelines</b></a></li>
</ul>
d30 1
a30 1
<a name="aboutprojadmin"><span class="InputHeader">About project administration on this site</span>
d60 1
a60 1
<a name="projmgmtguidelines"><span class="InputHeader">Project management and leadership guidelines</span>
@


1.9
log
@fixed index; added link for ProjectOwnerDocuments.html
@
text
@d1 2
a2 2
<HTML>
<HEAD>
d4 1
a4 1
<TITLE>Project Owner Administration</TITLE>
d6 2
a7 2
</HEAD>
<BODY>
d9 13
a21 13
<SPAN CLASS="Header" NOWRAP>Project owner administration</SPAN> 
<P> 
<SPAN CLASS="PLAINTEXT"><B>Project help for project owner administration: Index</B>
<P>

<UL>
<DL>
<DT><B>You are here: Project owner administration</B>
<DD><A HREF="ProjectOwnerEdit.html">Editing and maintaining the Project Home page</A>
<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>
d23 39
a61 28
<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>

<HR noShade SIZE=1>
<SPAN CLASS="InputHeader">About project administration on this site</SPAN>
<P>
As a Project Owner with one or more development projects hosted on this site, your administrative tasks are organized around the same project pages viewed by other project members or registered users. You access these same project pages as any project member or registered user, however your page view includes additional administrative links and options (in most, but not all, pages). Your Project Resources toolbar also includes an additional <I>Admin</I> link enabling you to edit your project home page and how your project information appears throughout the site.
<P>
If your project's approval by this site's administrators is pending, you still have access to most of this site's features and tools to get established and set up your project pages. Because the hosted tools for projects are automatically configured for your project as soon as you create it, you may:
<UL>
<LI>invite additional developer participants
<LI>update your project's home page
<LI>publish project news
<LI>upload project files and documents
<LI>post to your project's mailing lists
<LI>create subdirectories in your project's CVS repository
<LI>check in source code
<LI>and use the issue tracker to enter and search project issues.
</UL>
Really the only activities you are barred from until you receive project approval are adding project members, approving project membership requests, and granting roles.
<P>

<HR noShade SIZE=1>
<span class="InputHeader">A word about project management and leadership</SPAN>
<P>
d63 5
a67 5
<P>
One of the significant factors in such considerations is whether you are managing a proprietary or open source project. If your project is a proprietary endeavor with commercial licensing, project  governance may be largely determined by external factors, for example: corporate strategy, fiscal priorities, organizational structure, and established development methods. While many collaborative development practices can be successfully adopted within this framework, final decision making authority rests with the license holder and influences the development schedule and project goals to a high degree.
<P>
If your project is under open source licensing, the development culture is intrinsically different and far more determinant in how your project progresses. More of the burden fall upon you as the project owner -- equipped with some knowledge and understanding of open source practices -- to establish and communicate your project's parameters up front, yet strike a balance as the project evolves to nurture project participants toward an increasing sense of community and ownership.
<P>
d69 31
a99 19
<P>
Whichever scenario applies to your project, consider the following questions in communicating your project's fundamental purpose and structure to members and potential participants. These are geared to open source projects, but most apply to collaborative proprietary projects also:
<P>
<UL>
<li>What is the clear definition of your project's ultimate mission?
<P>
<li>How does your project handle decision-making, debates, and conflicts (for example, through voting, consensus building, or final authority)?
<P>
<li>What are your project's coding standards (for example, adherence to certain conventions and/or emphasis on particular architectural characteristics)?
<P>
<li>How can project members' gain more responsibility and greater ownership (for example, how can developers' roles evolve to earn more privileges such as becoming module leaders)?
<P>
<li>What are the terms for accepting contributions (for example, as defined by the licensing, but also how are non-member ideas or bug-fixes dealt with)?
</UL>
<P>
To learn more about managing collaborative development in commercial development, ... <b>[SUGGESTIONS FOR LINKS?]</b>
<P>
To learn more leading open source development efforts , ... <b>[SUGGESTIONS FOR LINKS?]</b>
<P>
d101 1
a101 1
<HR noShade SIZE=1>
d103 1
a103 1
</SPAN>
d105 2
a106 2
</BODY>
</HTML>
@


1.8
log
@Edited by Thena
PR:
Obtained from:
Submitted by:
Reviewed by:
@
text
@d1 83
a83 73
<HTML>
<HEAD>

<TITLE>Create New Project (Step 3)</TITLE>

</HEAD>
<BODY>
<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" WIDTH="100%" >
  <TR>

<span class="PlainText"> 
<p> <a name="ProjectAddStep3"></a><span class="Header"><b>Create New Project 
  (Step 3): Inviting people to join your project</b></span><br>
<ul>
  
  <dl> 
    <dt><b>Creating a New Project: Index</b>
    <dd> 
      <li><A href="ProjectAddStep1.html">Create a New Project (Step One): "Project Add" fields explained</A> </li>
    <dd> 
      <li><A href="ProjectAddStep2.html">Create a New Project 
        (Step Two): Choosing your project's license and profile </A></li>
    <dd> 
      <li><b>Create a New project 
        (Step Three): Inviting people to join your project</b></li>
    <dd> 
      <li><A href="ProjectAddConfirm.html">Project Creation Confirmation</A></li></dd>
  </dl>
</ul>

<P>Invite as many people as you wish by listing their email addresses, one email 
  address per line, or multiple addresses if each address is separated by a comma, 
  colon, or semicolon. Automatically generated invitations to each invitee will 
  be sent; you can use the field below to include a personal message, perhaps 
  a brief explanation of your project's purpose, why you think he or she might 
  find it worthwhile to join in, and a link providing direct access to your project 
  home page.</P>
<p>Recipients of your invitation who are already registered Motorola iDevelopers 
  log in to Motorola's developer site to view your My WebSpace project home page. 
  To join your project, they click the "Join This Project" link.</p>
<p>If the person you're inviting is <i>not</i> a registered Motorola iDeveloper, 
  the email invitation asks her to register first as a Motorola iDeveloper to 
  obtain a login and password by email. Then this person is able to log in and 
  view your My WebSpace project home page.</p>
<p>Recipients of your invitation who are already registered Motorola iDeveloper's 
  must log in to Motorola's developer site before they can view your My WebSpace 
  project home page. If they wish to join your project, they can click the "Join 
  This Project" link. 
<p> If the person you're inviting is <I>not</I> a registered Motorola iDeveloper, 
  he/she is instructed by the email invitation to register first as a Motorola 
  iDeveloper to obtain a login and password by email. Then this person is able 
  to log in and view your My WebSpace project home page. 
<P> 
<blockquote><a name="InvitationMessageField"></a><B>Invitation Message</B><BR>
  <span class="PlainText"> 
  <P>This message should be brief, but clear and informative. You can include 
    hyperlinks, and any other information that you think would promote your project. 
    Formatting and HTML are not, however, supported--the message, that is, stands 
    on what it says not on how it looks. Hint: write out what you want to say 
    beforehand. That way, you won't be lost for words. Finally, all the other 
    project information is automatically generated, so you don't have to worry 
    about including it again.</P>
  </span> </blockquote>
<p></p>

The next step in the process is rather simple: it entails little more than acknowledging the project's creation.  We explain the process in <A href="ProjectAddStep4.html">Project Creation Confirmation.</A>
<HR noShade SIZE=1>
<p><A href="Help.html">Back to main Help index</A></p>
<p>&nbsp; 
</span></P>
</TR>
</TABLE></BODY>
</HTML>
@


1.7
log
@fixing stupid little html things; this doc still needs some resource links added at bottom or those lines commented out until a future minor release
@
text
@d1 73
a73 82
<HTML>
<HEAD>

<TITLE>Project Owner Administration</TITLE>

</HEAD>
<BODY>

<SPAN CLASS="Header" NOWRAP>Project owner administration</SPAN> 
<P> 
<SPAN CLASS="PLAINTEXT"><B>Project help for project owner administration: Index</B>
<P>

<UL>
<DL>
<DT><B>You are here: Project owner administration</B>
<DD><A HREF="ProjectOwnerEdit.html">Editing and maintaining the Project Home page</A>
<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>

<HR noShade SIZE=1>
<SPAN CLASS="InputHeader">About project administration on this site</SPAN>
<P>
As a Project Owner with one or more development projects hosted on this site, your administrative tasks are organized around the same project pages viewed by other project members or registered users. You access these same project pages as any project member or registered user, however your page view includes additional administrative links and options (in most, but not all, pages). Your Project Resources toolbar also includes an additional <I>Admin</I> link enabling you to edit your project home page and how your project information appears throughout the site.
<P>
If your project's approval by this site's administrators is pending, you still have access to most of this site's features and tools to get established and set up your project pages. Because the hosted tools for projects are automatically configured for your project as soon as you create it, you may:
<UL>
<LI>invite additional developer participants
<LI>update your project's home page
<LI>publish project news
<LI>upload project files and documents
<LI>post to your project's mailing lists
<LI>create subdirectories in your project's CVS repository
<LI>check in source code
<LI>and use the issue tracker to enter and search project issues.
</UL>
Really the only activities you are barred from until you receive project approval are adding project members, approving project membership requests, and granting roles.
<P>

<HR noShade SIZE=1>
<span class="InputHeader">A word about project management and leadership</SPAN>
<P>
The help documents in this section cover this site's administrative functions available to you as a Project Owner. How you use this functionality to structure and lead your project toward achieving particular goals remains largely in your purview. Whenever possible, these help documents suggest the implications of administrative options with respect to project leadership and management.
<P>
One of the significant factors in such considerations is whether you are managing a proprietary or open source project. If your project is a proprietary endeavor with commercial licensing, project  governance may be largely determined by external factors, for example: corporate strategy, fiscal priorities, organizational structure, and established development methods. While many collaborative development practices can be successfully adopted within this framework, final decision making authority rests with the license holder and influences the development schedule and project goals to a high degree.
<P>
If your project is under open source licensing, the development culture is intrinsically different and far more determinant in how your project progresses. More of the burden fall upon you as the project owner -- equipped with some knowledge and understanding of open source practices -- to establish and communicate your project's parameters up front, yet strike a balance as the project evolves to nurture project participants toward an increasing sense of community and ownership.
<P>
A third possibility is a combination of the above, that is, you are leading an open source project with the involvement and support of a corporate entity embracing open source to achieve certain business goals. In these circumstances, as the project owner you essentially function as the liaison between two cultures.
<P>
Whichever scenario applies to your project, consider the following questions in communicating your project's fundamental purpose and structure to members and potential participants. These are geared to open source projects, but most apply to collaborative proprietary projects also:
<P>
<UL>
<li>What is the clear definition of your project's ultimate mission?
<P>
<li>How does your project handle decision-making, debates, and conflicts (for example, through voting, consensus building, or final authority)?
<P>
<li>What are your project's coding standards (for example, adherence to certain conventions and/or emphasis on particular architectural characteristics)?
<P>
<li>How can project members' gain more responsibility and greater ownership (for example, how can developers' roles evolve to earn more privileges such as becoming module leaders)?
<P>
<li>What are the terms for accepting contributions (for example, as defined by the licensing, but also how are non-member ideas or bug-fixes dealt with)?
</UL>
<P>
To learn more about managing collaborative development in commercial development, ... <b>[SUGGESTIONS FOR LINKS?]</b>
<P>
To learn more leading open source development efforts , ... <b>[SUGGESTIONS FOR LINKS?]</b>
<P>

<HR noShade SIZE=1>
<a href="/servlets/HelpTOC">Back to main Help index</a></p>
</SPAN>

</BODY>
</HTML>
@


1.6
log
@added info about possible actions while project approval pending
@
text
@d61 2
a62 2
<li>What's the clear definition of your project's ultimate mission?

d72 1
a72 1
To learn more about managing collaborative development in commercial development, ... ADD LINKS
d74 1
a74 1
To learn more leading open source development efforts , ... ADD LINKS
@


1.5
log
@html edits; revised doc index
@
text
@d8 2
a9 3
<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
  <TR>
    <SPAN CLASS="Header" NOWRAP>Project owner administration</SPAN> 
d33 13
d50 1
a50 1
These project administration help documents cover this site's administrative functions available to you as a Project Owner. How you use this functionality to structure and lead your project toward achieving particular goals remains largely in your purview. Whenever possible, these help documents suggest the implications of administrative options with respect to project leadership and management. A significant factor in such considerations is whether you are managing a proprietary or open source project.
d52 1
a52 1
If your project is a proprietary endeavor with commercial licensing, project  governance may be largely determined by external factors, for example: corporate strategy, fiscal priorities, organizational structure, and established development methods. While many collaborative development practices can be successfully adopted within this framework, final decision making authority rests with the license holder and influences the development schedule and project goals to a high degree.
a78 2


a79 2
</TR>
</TABLE>
@


1.4
log
@added <title> tags to all files
@
text
@d12 1
a12 1
<SPAN CLASS="PLAINTEXT">Project help for project owner administration: Index
@


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


1.2
log
@updated for new help format
@
text
@d1 65
a65 65
<TABLE BORDER="0" CELLSPACING="1" CELLPADDING="3" BORDER="0" WIDTH="100%">
  <TR>
    <SPAN CLASS="Header" NOWRAP>Project owner administration</SPAN> 
<P> 
<SPAN CLASS="PLAINTEXT">Project help for project owner administration: Index
<P>

<UL>
<DL>
<DT><B>You are here: Project owner administration</B>
<DD><A HREF="ProjectOwnerEdit.html">Editing and maintaining the Project Home page</A>
<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>

<HR noShade SIZE=1>
<SPAN CLASS="InputHeader">About project administration on this site</SPAN>
<P>
As a Project Owner with one or more development projects hosted on this site, your administrative tasks are organized around the same project pages viewed by other project members or registered users. You access these same project pages as any project member or registered user, however your page view includes additional administrative links and options (in most, but not all, pages). Your Project Resources toolbar also includes an additional <I>Admin</I> link enabling you to edit your project home page and how your project information appears throughout the site.
<P>

<HR noShade SIZE=1>
<span class="InputHeader">A word about project management and leadership</SPAN>
<P>
These project administration help documents cover this site's administrative functions available to you as a Project Owner. How you use this functionality to structure and lead your project toward achieving particular goals remains largely in your purview. Whenever possible, these help documents suggest the implications of administrative options with respect to project leadership and management. A significant factor in such considerations is whether you are managing a proprietary or open source project.
<P>
If your project is a proprietary endeavor with commercial licensing, project  governance may be largely determined by external factors, for example: corporate strategy, fiscal priorities, organizational structure, and established development methods. While many collaborative development practices can be successfully adopted within this framework, final decision making authority rests with the license holder and influences the development schedule and project goals to a high degree.
<P>
If your project is under open source licensing, the development culture is intrinsically different and far more determinant in how your project progresses. More of the burden fall upon you as the project owner -- equipped with some knowledge and understanding of open source practices -- to establish and communicate your project's parameters up front, yet strike a balance as the project evolves to nurture project participants toward an increasing sense of community and ownership.
<P>
A third possibility is a combination of the above, that is, you are leading an open source project with the involvement and support of a corporate entity embracing open source to achieve certain business goals. In these circumstances, as the project owner you essentially function as the liaison between two cultures.
<P>
Whichever scenario applies to your project, consider the following questions in communicating your project's fundamental purpose and structure to members and potential participants. These are geared to open source projects, but most apply to collaborative proprietary projects also:
<P>
<UL>
<li>What's the clear definition of your project's ultimate mission?

<li>How does your project handle decision-making, debates, and conflicts (for example, through voting, consensus building, or final authority)?
<P>
<li>What are your project's coding standards (for example, adherence to certain conventions and/or emphasis on particular architectural characteristics)?
<P>
<li>How can project members' gain more responsibility and greater ownership (for example, how can developers' roles evolve to earn more privileges such as becoming module leaders)?
<P>
<li>What are the terms for accepting contributions (for example, as defined by the licensing, but also how are non-member ideas or bug-fixes dealt with)?
</UL>
<P>
To learn more about managing collaborative development in commercial development, ... ADD LINKS
<P>
To learn more leading open source development efforts , ... ADD LINKS
<P>

<HR noShade SIZE=1>
<a href="/servlets/HelpTOC">Back to main Help index</a></p>


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

@


1.1
log
@new and revised help documentation for v1.0
@
text
@d3 4
a6 3
    <SPAN CLASS="Header" NOWRAP>Project Owner Administration</SPAN> 
 
<SPAN CLASS="PlainText">
d10 9
a18 7
<DT><A HREF="ProjectOwnerEdit.html">Editing and maintaining your Project Home page</A>
<DT><A HREF="ProjectOwnerNews.html">Managing project site news</A>
<DT><A HREF="ProjectOwnerFiles.html">Managing project files</A>
<DT><A HREF="ProjectOwnerMembers.html">Adding project members and approving roles</A>
<DT><A HREF="ProjectOwnerMailingLists.html">Configuring and managing project mailing lists</A>
<DT><A HREF="ProjectOwnerSource.html">Administering project source code</A>
<DT><A HREF="ProjectOwnerIssues.html">Managing project issues and generating reports</A>
d43 1
a43 1
<P>
d59 1
a59 1
<a href="Help.html">Back to main Help index</a></p></span>
a62 1
</TD>
@

