dev_process/project-log.php

<?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'

$pageTitle 		= "Project Intellectual Property (IP) Log";

include( '../_commonLeftNav.php' );

ob_start();
?>
    <div id="maincontent">
	<div id="midcolumn">
		
<h1>Project IP Log</h1>
<div style="float: right; border: 1px dashed black; 
background-color: #FFFFDD;"><table><tr><td width="150px">See 
"<a href="/org/documents/Eclipse_IP_Policy.pdf?page=2">Section IV</a>"
of the Eclipse IP Policy.</td>
</tr></table></div><blockquote><em>...the applicable
Committer, with the assistance of the EMO, shall conduct the following activities prior to
uploading any Content into the repository or otherwise making the Content available for
distribution: ... (2)The Committer(s) shall document all information gathered pursuant to (1)
above in a form to be provided by the Eclipse Foundation and provide such
completed form to the EMO.</em></blockquote>

The <a href="/org/documents/Eclipse_IP_Policy.pdf">Eclipse IP Policy</a> requires
    <a href="/legal/committerguidelines.php">certain due
    diligence and record keeping</a>.
    Small contributions in the form of Bugzilla patches and the like can be
    committed directly to the code base (after the appropriate contributor
    information is recorded). Medium, large, and all third-party (non-EPL
    licensed) contributions require the <a href="/legal/ContributionQuestionnairePart1-v1.0.htm">Code Contribution
    Questionnaire</a> and additional record keeping. Maintaining a current and accurate Project Log is
    the best way to keep this information up-to-date.

<p>The Project Log is a file containing the following sections. The file can be
in these formats: (The goal is to have the log in a universally readable file format, thus 
proprietary formats, such as Microsoft Word or Excel, are not allowed.)
<ul>
<li>HTML
<li>CSV (a spreadsheet saved in the open Comma Separated Value file format)
<li>text
</ul>
The Project Log
must be available via a public URL on the Project's website, and a static copy
must be included in the <a href="release-review.php">Release Review</a>
materials for each release.

<h2>Section 1 (Committers)</h2>
<p>A list of all the Committers, past and present, whose contribution is still
active in the repository. A Committer whose code has been entirely removed from
the active branches does not need to be listed. The columns for this section
are:</p>
<ul>
  <li>dev.eclipse.org unix login name</li>
</ul>

<h2>Section 2 (Developers)</h2>

<p>A list of all the non-Committers whose contribution is still active in the
repository. The columns for this section are:</p>
<ul>
  <li>component (CVS directory)</li>
  <li>bug #</li>
  <li>contributor's name (see Additional Information below)</li>
  <li>contribution size (LOC or &quot;small&quot; where small is defined as
    &quot;less than 100 LOC&quot;)</li>
  <li>committer who committed this contribution</li>
  <li>description if there is no bug # or if there are multiple bug #s</li>
</ul>
<p>Note that it behooves the Project to use the full capabilities of Bugzilla to
assist with generating this report. If the Project uses the following features,
then simple queries will generate most of section 2:</p>
<ol>
  <li>All code changes (100% of them) refer to a Bugzilla entry</li>
  <li>All commit messages include the corresponding bug numbers.</li>
  <li>VERIFY and CLOSE all RESOLVED bugs when closing out a release.</li>
  <li>Target milestones for &quot;fixed in version&quot;</li>
</ol>

<h2>Section 3 (Third Party Software)</h2>
<p>A list of the non-Eclipse third party software included in the Project. The
columns for this section are:</p>
<ul>
  <li>name including version</li>
  <li>IPzilla # of entry providing legal clearance for inclusion</li>
  <li>directory location or jar file</li>
  <li>license name and version (including any licenses related to embedded third
    party software)</li>
  <li>usage (e.g. modified/unmodified, source, object, derivative work, entire
    package or which subset)</li>
</ul>

<h2>Additional Information</h2>
<p align="left">The Foundation needs to maintain contact information for all
Contributors; however, the Foundation also needs to abide by its <a href="/legal/privacy.php">Privacy
Policy</a>. The Project handles these two requirements by maintaining an internal, non-public
database (list) of contact information for all Project Contributors, including 
the Contributor's name, email address, mailing address, and phone number. Committers
are stored in the Foundation database under their dev.eclipse.org unix login name, thus the only
requirement for section 1 is that login name. Contributors are stored by
the Project in private, in a text file, a spreadsheet, an HTML table, a small
database, or whatever the Project chooses. Section 2 uses the Contributor names
as keys into that information to avoid having to list Contributors' email addresses 
or mailing addresses in the Project IP log. The
Project sends the contact information to the Foundation as part of the process
of a <a href="release-review.php">Release Review</a>.</p>

<p>All of this is a long way of saying that the Project leadership
and/or PMC must keep track of the Contributors' contact information in private
and send that private list to the EMO at the Release Review.</p>

<?php include( '../_commonFooter.php' ); ?>
</div><!-- midcolumn -->
</div><!-- maincontent -->
<?php
	# Paste your HTML content between the EOHTML markers!	
	$html = ob_get_contents();
	ob_end_clean();

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