dev_process/review-mechanisms.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 		= "Review Mechanisms";
$pageKeywords	= "development process";
$pageAuthor		= "Bjorn Freeman-Benson Nov 20/05";

ob_start();
?>
    <div id="maincontent">
	<div id="midcolumn">
		
<h1>Review Mechanisms</h1>
<p><i>version 014 - July 26, 2005</i></p>
<p><a href="index.php">[This is one page of the larger document.]</a></p>
<h2>Creation, Checkpoint, and Release Reviews</h2>
<p>Phases end with Reviews. For each Review, the project leadership makes a presentation to the review committee as well as any interested Eclipse
members. Their are a number of guidelines/requirements for the presentation
slides:</p>
<ul>
  <li>The presentation slides must be posted to the project website at least one
    week, preferably two weeks, in advance. For proposals, the slides must be
    provided to the EMO for posting with the proposal.
    <ul>
      <li>If the project posts the slides, the URL is to be emailed to the EMO
        for reference from other eclipse.org pages.</li>
      <li>If the project posted the slides, a copy of the current version is to
        be emailed to the EMO after the review for archiving.</li>
    </ul>
  </li>
  <li>The presentation slides must be available on the website in a format that
    anyone in the membership can review. For example, PowerPoint is not an
    acceptable single format - it can be one of the formats available, but not
    the only one. For a single format, please use PDF.&nbsp;</li>
  <li>The presentation slides should have page numbers to allow the attendees to
    follow along.</li>
  <li>The slides are not authored by the Eclipse Foundation - they are authored
    by a project lead, or a project lead employed by a company - and thus the
    footer of the slides should make the authorship clear.</li>
  <li>The slides must be licensed under the EPL.</li>
</ul>
<p>All Reviews are announced by the EMO on <a href="/projects/">the Eclipse
website</a>.</p>
<p>Unless otherwise specified, Reviews are held as conference calls -
the EMO will provide a call-in number. The project team can utilize other
mechanisms (e.g., web conferencing) at its own expense as long as those
mechanisms are available to all the attendees without additional costs to the
attendees.</p>

<h3>Archival Quality</h3>
<p>The Review presentations are archived on the Eclipse website (Creation
Reviews are <a href="/proposals/">archived with their proposal</a>,
Checkpoint and Release Reviews <a href="/projects/previous-release-reviews.php">are
archived</a>). Eclipse members may not be able to attend the Review conference
calls for a variety of reasons including that the member did not become a member
until after the Review occurred - in spite of this, the members still need to
have access to the Review presentations. Thus the presentation slide decks need
to be more than just slide decks: they need to be archival quality documents
that are comprehensible and complete on their own.</p>
<p>What this means to presentation authors is that the slide deck needs to have
more detail than a normal face-to-face meeting presentation would usually have.
Specific facts, numbers, dates, etc.</p>
</div>
</div>
<?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);
?>