| |
| |
| <head> |
| </head> |
| |
| <?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 = "Eclipse Project Status Infrastructure"; |
| $pageKeywords = "development process"; |
| $pageAuthor = "Bjorn Freeman-Benson Jan 2006"; |
| |
| ob_start(); |
| ?> |
| <div id="maincontent"> |
| <div id="midcolumn"> |
| |
| <h2>Project Status Reporting</h2> |
| |
| <div class="homeitem3col"> |
| <h3><a name="Why"></a>Why is project status information important?</h3> |
| <p> |
| Eclipse projects belong to a larger community - Eclipse - which is comprised |
| of a not only the committers and developers on the project, but also the |
| developers on other projects, plug-in developers outside the Eclipse projects, |
| and the entire ecosystem surrounding Eclipse. In order to keep all these people |
| up-to-date on the direction and status of the Eclipse projects, each project |
| needs to provide timely and accurate descriptive and status information.</p> |
| <p>The project status information (files) drive a number of the |
| eclipse.org web pages including <a href="/projects/dashboard/">the |
| dashboard</a>, <a href="/projects/timeline/">the timeline</a>, <a href="/technology/">lists |
| of projects</a>, lists of <a href="/mail/">mailing lists</a> and <a href="/newsgroups/">newsgroups</a>, |
| <a href="/projects/callisto.php">status pages</a>, and more.</p> |
| </div> |
| |
| <div class="homeitem3col"> |
| <h3><a name="What"></a>What is project status information?</h3> |
| <p>The project status information encompasses three kinds of |
| information:</p> |
| <ol> |
| <li>Relatively static structural information such as the names of the |
| project's mailing lists and newsgroups, the bugzilla products and |
| CVS repository, etc.</li> |
| <li>Historical information such as previous release downloads, release |
| review slides and IP logs, etc.</li> |
| <li>Status and future looking information such as the project and |
| milestone plans, the features scheduled for the current release, |
| release dates, etc.</li> |
| </ol> |
| </div> |
| |
| <div class="homeitem3col"> |
| <h3><a name="Where"></a>Where is the project status information stored?</h3> |
| |
| <p>The descriptive and status information is stored and used in a number of places:</p> |
| |
| <ol> |
| <li>The Eclipse Foundation's internal database of projects. (<a href="project-status-infrastructure-page1.php">see |
| "how to" page 1</a>)</li> |
| <li>The project's own <code>project-info/</code> directory. (<a href="project-status-infrastructure-page2.php">see |
| "how to" page 2</a>)</li> |
| <li>The project's own <code> index.php</code> home page. (<a href="project-status-infrastructure-page3.php">see |
| "how to" page 3</a>)</li> |
| <li>Other project pages (<a href="project-status-infrastructure-page4.php">see |
| "how to" page 4</a>)</li> |
| </ol> |
| </div> |
| |
| <div class="homeitem3col"> |
| <h3><a name="Who"></a>Who is responsible for maintaining the project status information?</h3> |
| <p>Each Eclipse project's project lead is responsible for maintaining |
| that project's status information. This information is an important part |
| of being an Eclipse project and thus while we acknowledge that it is |
| possible to write code without status information, it is not possible to |
| be an <i>Eclipse project</i> without providing status to the rest of the |
| community.</p> |
| </div> |
| |
| <div class="homeitem3col"> |
| <h3><a name="When"></a>When is project status information considered out-of-date?</h3> |
| <p>Different kinds of information go out of date at different rates and |
| times, but here's an easy checklist:</p> |
| <ul> |
| <li>All structural status information is out-of-date if it does not |
| match the infrastructure. For example, if the project has added a |
| new project-announce@ mailing list, but the project status files do |
| not list that mailing list, then they are out of date.</li> |
| <li>Status summaries must be updated at least once a quarter. It's |
| better to update them once a month.</li> |
| <li>Historical information (downloads, release information, and so on) |
| and status summaries need updating with each release (obviously).</li> |
| </ul> |
| </div> |
| |
| <div class="homeitem3col"> |
| <h3><a name="How"></a>How do I create and maintain the project status information?</h3> |
| <p>To create the project status information, just follow <a href="project-status-infrastructure-page1.php">these |
| easy instructions</a> starting at page 1.</p> |
| |
| <p>For modifying your existing project status information, you may want |
| to jump directly to the relevant section:</p> |
| |
| <ol> |
| <li>The Eclipse Foundation's internal database of projects. (<a href="project-status-infrastructure-page1.php">see |
| "how to" page 1</a>)</li> |
| <li>The project's own <code>project-info/</code> directory. (<a href="project-status-infrastructure-page2.php">see |
| "how to" page 2</a>)</li> |
| <li>The project's own <code> index.php</code> home page. (<a href="project-status-infrastructure-page3.php">see |
| "how to" page 3</a>)</li> |
| <li>Other project pages (<a href="project-status-infrastructure-page4.php">see |
| "how to" page 4</a>)</li> |
| </ol> |
| </div> |
| |
| </div> |
| </div> |
| |
| <div id="rightcolumn"> |
| |
| <div class="sideitem"> |
| <h6>Five Questions</h6> |
| <ul> |
| <li><a href="#Who">Who?</a></li> |
| <li><a href="#What">What?</a></li> |
| <li><a href="#Where">Where?</a></li> |
| <li><a href="#When">When?</a></li> |
| <li><a href="#How">How?</a></li> |
| </ul> |
| </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); |
| ?> |
