callisto-files/callisto-bug-contest.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 		= "Callisto Simultaneous Release Bug Finding Contest";
$pageKeywords	= "projects callisto";
$pageAuthor		= "Bjorn Freeman-Benson Mar 2006";

ob_start();
?>
<style type="text/css">
h2 {
border-bottom: solid
}
h3 {
border-bottom: thin dotted
}
</style>

    <div id="maincontent">
	<div id="midcolumn">
        <h1><?= $pageTitle ?></h1>
        
        <h2>Prizes</h2>
        <ul><li>Both the reporter of, and the triager of, each and every great bug report receives an <a href="callisto-shirt.png">"I Helped Callisto" T-Shirt</a>. (That's an eclipse
        of the Sun by Jupiter as seen from the surface of the moon Callisto.)
        <center><img src="callisto-shirt-crop.png"></center>
        </li>
        <li><img src="ipod.gif"  align="right" hspace="3" vspace="3">At every milestone and release candidate, a random drawing 
        amongst all the reporters of great bugs submitted in 
        that milestone/release candidate will receive an iPod.
        </li>
        <li>Upon the final Callisto Simultaneous Release, two random drawings (one for reporters
        and one for triagers) from all the great bugs submitted will
        receive an Eclipse mountain bike.
        </li>
        </ul>
        
                <p align="center" style="border: thin dotted;">
	<a href="/projects/callisto.php#Installing">How to install Callisto</a></p>
        
              
        <h2>iPod Winners</h2>
        <ul>
        <li>The RC1a iPod winner is Olivier Nouguier for <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=121235">bug 121235</a>.
        </li>
        <li>The RC2 iPod winner is Joan Haggarty for <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=136388">bug 136388</a>.
        </li>
        <li>The RC3 iPod winner is Randy Smith for <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=138244">bug 138244</a>.
        </li>
        <li>The RC4 iPod winner is Anton Leherbauer for <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=142170">bug 142170</a>.
        </li>
        <li>The RC5 iPod winner is Raj Mandayam for <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=136400">bug 136400</a>.
        </li>
        </ul>
        
       <h2>Eclipse Mountain Bike Winners</h2>
       <ul>
       <li>The winner of the custom mountain bike from among the great bug reporters is
        Channing Walton, for  
        <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=136907">bug 136097</a>.
        </li>
        <li>The winner of the custom mountain bike from among the great bug triagers is
        John Arthorne, for  
        <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=140843">bug 140843</a>.
        </li>
        </ul>
        
        <h2>The Callisto Guide to Great Bug Reports</h2>
<p>We are having a contest for great <a href="/projects/callisto.php">Callisto</a> bug reports. That means that we  need to say a few 
words about what we are looking for. We will keep  this simple so that it is easy to apply. We'll 
also point to a few  other resources about filing good reports because we know it is not a  simple subject.
<p>
Here are the two things to think about when filing a great Callisto  bug report:
<ul><li>Action.
    <li>Value.
</ul>
<h3>Action</h3>
<img src="ladybug_flying_70x70.gif"  align="left" hspace="5" vspace="3">
Of course we want action when we find a bug. Much about reporting has  to do with getting the right thing done 
without a lot of wasted work  on your part or anyone else. This division of work is a deal. If you  
want action, take action. Do what you think others should do and see  if your report will guide them there.
<p>
The ultimate is to find the bug, write the test, fix the bug and pass  the test. That's action, but 
not the only valued action. Since so  much about Callisto is about integration. Try reproducing the bug in  
various configurations. This can take time, of course. But you have  one failing configuration already and 
that is one more than anyone else.
<p>
<h3>Value</h3>
<img src="value_70x70.gif"  align="left" hspace="5" vspace="3">
We also want our actions to be valuable. A fixed bug is always  valuable, but is it the best value 
for everyone's time, even yours?  The trick to finding valuable bugs is to look efficiently. Now I'm  
going to assume that we're actually looking, not just stumbling  across a bug and reporting it, not that there 
is anything wrong with  that.
<p>
But when looking for bugs you have to choose to use Callisto like  someone other 
than yourself. You must observe what that person sees  and you have to judge what problems are 
important to them. A label  alignment problem might indicate careless design to this user, but  
having that fixed is not a valuable as correcting wrong answers to  possibly foolish operations that most of us 
have already learned not  to do. Keep a notepad handy and keep track of paths or operations  that you 
haven't tried, or areas that look suspicious but maybe not  high value and therefore lower priority in your search.
<p>
<h3>A Big Win</h3>
So that's the formula: action + value. We're looking for great bugs  that move smothly through triage 
and lead developers to action that  proves valuable. We're asking developers to think about each bug 
in  terms of action and value and to bring the best of  them to the  attention of the Foundation (see "How It Works" below). 
We'll do something nice for these bug  authors and include them in a drawing for something even nicer. 
But  the big win for all of us is a really nice system in the end.
</p>        
        
        <h2>How It Works</h2>
        <ol>
        <li>Any developer who sees a great <a href="/projects/callisto.php">Callisto</a> bug marks that bug with 
        the <b><code>greatbug</code></b> keyword.</li>
        <li>If a project lead / PMC lead finds a bug report
        that is great - i.e., a bug report that provides both <b>action</b> and <b>value</b> 
        - then he or she
        sends the bug to emo@eclipse.org.</li>
        <li>The EMO regularly queries for, and acts upon, <code>greatbug</code>
        marked bugs. This is in addition to any bugs the PMC/PLs find.</li>
        <li>The EMO handles the operational side of mailing T-shirts, 
        iPods, and (at the end) the bicycles.</li>
        </ol>
		</p>
<br/>
  </div></div>
<?php
	$html = ob_get_contents();
	ob_end_clean();

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