<?php  																														require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/app.class.php");	require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/nav.class.php"); 	require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/menu.class.php"); 	$App 	= new App();	$Nav	= new Nav();	$Menu 	= new Menu();		include($App->getProjectCommon());    # All on the same line to unclutter the user's desktop'

//See http://www.eclipse.org/projects/dev_process/new-committer.php for the new page.

	$pageTitle 		= "New Committer / Bug Triager Process";
	$pageKeywords	= "foundation, committer, process, guidelines";
	$pageAuthor		= "Mike Milinkovich, Nov. 29, 2005";
	
	# Paste your HTML content between the EOHTML markers!	
	$html = <<<EOHTML

<style type="text/css">
#bigfirstchar
{
float:left;
padding-right: 4px;
font-size:300%;
line-height:80%;
}
</style>
<div id="maincontent">
	<div id="midcolumn">
		<h1>$pageTitle</h1>
		<h3>Purpose</h3>

		<p>
  	    The Eclipse Foundation needs to ensure that all committers to the code and/or the 
  	    website and/or the bug system understand their role in safeguarding 
  	    the intellectual property of Eclipse. 
  	    The Foundation also needs to ensure that we have accurate records of the people who 
  	    are acting as change agents on the projects.</p>
  	  	<p>The process the Foundation has chosen to ensure these goals (committers/bug triagers
      	understand their role; Foundation has accurate records) is to have  committers/bug triagers
      	sign that they have read, understood, and will follow the 
      	<a href="committerguidelines.php">Committer Guidelines</a> and to have their 
      	employer sign that they agree that the new committer/bug triager can participate at Eclipse and 
      	can contribute under the terms of the <a href="../org/documents/epl-v10.php">Eclipse 
      	Public License</a>. This document describes this process that must be followed by all 
      	Eclipse Project Management Committees (PMC&rsquo;s) for the identification and 
      	provisioning of new Committers/Bug Triagers for the projects managed by the PMC. </p>
      	
  	  	<blockquote>A Committer is an individual who is to have write access to the Eclipse 
  	  	CVS repositories for code or web pages. </blockquote>
  	  	<blockquote>A Bug Triager is an individual who is to extended write access to the Eclipse 
  	  	bug tracking system. (In the text below, the word "Committer" refers to both 
  	  	Committers and Bug Triagers.</blockquote>
  	  	
      	<p>If you have any questions, please send them to the 
      	<a href="mailto:emo@eclipse.org">EMO</a>.
      	</p>

		<h3>Process</h3>
		<p>
		<span id="bigfirstchar">1</span>
		    The PMC follows the process described in their
      		top-level project charter for selecting, vetting, and electing a new
      		Committer. Most top-level project charters are based on 
      		<a href="../projects/dev_process/Eclipse_Standard_TopLevel_Charter_v1.0.php">the
      		generic top-level charter (see the section titled &quot;Committers&quot;)</a>.
      		(Note: for Technology projects, the project lead follows this process and
      		then confirms the results with the PMC via technology-pmc@eclipse.org.)
      	</p>
		<p><span id="bigfirstchar">2</span>
		   The PMC educates the new Committer on their
      		responsibilities for safeguarding the intellectual property of Eclipse and
      		that they have read, understood, and agree to follow the 
      		<a href="committerguidelines.php">Committer Guidelines</a>.
      		Being a Committer at Eclipse is more than just having write-access to the
      		CVS repository and/or website - there are specific IP due diligence and
      		record keeping activities that Committers must follow. The PMC is
      		responsible for ensuring that their committers understand and follow these
      		responsibilities.</p>
		<p>
		<span id="bigfirstchar">3</span>
		    Then...the PMC fills out the on-line <a href="committer_process/committer_request.html">new
      		committer request form</a><br/><br/></p>
      	<p>
      	   Then one of these four choices...
      		<table>
      		  <TR>
   				<TD width="50%" valign="top"><span id="bigfirstchar">4a</span> If the new committer 
   				is already a Committer on an existing Eclipse project then no additional paperwork 
   				is needed.
    			</TD>
    			<td>&nbsp;</td>
    			<TD width="50%" valign="top"><span id="bigfirstchar">4b</span> If the new committer (i) works&nbsp;for a
      			Member company and (ii) that Member company has signed and submitted a <a href="EclipseMemberCommitterAgreementFinal.pdf">Member Committer Agreement</a>
      			covering all of its employees who contribute to Eclipse, then:
      			<ol>
        			<li>The new Committer fills out the online <a href="committer_process/member_committer_questionnaire.php">Member Committer
          			Questionnaire</a></li>
      			</ol>
    			</TD>
     			</tr><tr><td>&nbsp;</td></tr>
     			<TD width="50%" valign="top"><span id="bigfirstchar">4c</span> If the new committer (i) works for a Member
      			company but (ii) that Member company has <b><i>NOT </i></b>signed a 
      			<a href="EclipseMemberCommitterAgreementFinal.pdf">Member Committer Agreement</a>,
      			then:
      			<ol>
        			<li>The new Committer fills out the online <a href="committer_process/individual_committer_questionnaire.php">Individual Committer Questionnaire</a> </li>
        			<li>The new Committer prints and signs and faxes or postal mails
          			an&nbsp;<a href="committer_process/EclipseIndividualCommitterAgreementFinal.pdf">Individual Committer Agreement</a>.
          			<em>If you find the signature block of this form confusing, we've
          			prepared <a href="example-individual-committer-agreement-signature-block.gif">an example for you to emulate</a>.</em></li>
        			<li>The new Committer prints and has his/her employer sign and then
          			faxes or postal mails an <a href="committer_process/employer_consent.pdf">Eclipse Committer Employer Consent Form</a>.</li>
      			</ol>
    			</TD>
    			<td>&nbsp;</td>
    			<TD width="50%" valign="top"><span id="bigfirstchar">4d</span> If the new committer
      			does NOT work for a Member company, then:
      			<ol>
        			<li>The new Committer fills out the online <a href="committer_process/individual_committer_questionnaire.php">Individual Committer Questionnaire</a> </li>
        			<li>The new Committer prints and signs and faxes or postal mails
          			an&nbsp;<a href="EclipseIndividualCommitterAgreementFinal.pdf">Individual Committer Agreement</a>.
          			<em>If you find the signature block of this form confusing, we've
          			prepared <a href="example-individual-committer-agreement-signature-block.gif">an example for you to emulate</a>.</em></li>
        			<li>The new Committer prints and has his/her employer sign and then
          			faxes or postal mails an <a href="employer_consent.pdf">Eclipse Committer Employer Consent Form</a>.</li>
      			</ol>
    			</TD>
  			</TR>
  			</table>
		<p>
		<span id="bigfirstchar">5</span>
		    Then...after the EMO has received the online form from (3) and
      		the appropriate online and paper forms from (4), the EMO will cause the
      		Webmaster to create and provision the committer&rsquo;s unix account
      		appropriately.</p>
      	<p>
      	<span id="bigfirstchar">6</span>
      	    The Webmaster will notify both the new Committer, and the PMC
      		member who filled out form (3), via email that the new account is ready to go. 
      	</p>
	</div>
	</div>
	<!-- remove the entire <div> tag to omit the right column!  -->
	<div id="rightcolumn">
		<div class="sideitem">
			<h6>Related Links</h6>
			<ul>
				<li><a href="index.php">Legal Resources</a></li>
				<li><a href="committerguidelines.php">Committer Guidelines</a></li>
				<li><a href="ContributionQuestionnairePart1-v1.0.php">Contribution Questionnaire</a></li>
				<li><a href="EclipseIndividualCommitterAgreementFinal.pdf">Individual Committer Agreement</a></li>
				<li><a href="EclipseMemberCommitterAgreementFinal.pdf">Member Committer Agreement</a></li>				
			</ul>
		</div>
	</div>

EOHTML;


	# Generate the web page
	$App->generatePage($theme, $Menu, $Nav, $pageAuthor, $pageKeywords, $pageTitle, $html);
?>