greatfix/index.php - gerrit/www.eclipse.org/projects - Git at Google

 <?php
 /*******************************************************************************
  * Copyright (c) 2015, 2016 Eclipse Foundation and others.
  * All rights reserved. This program and the accompanying materials
  * are made available under the terms of the Eclipse Public License v1.0
  * which accompanies this distribution, and is available at
  * http://www.eclipse.org/legal/epl-v10.html
  *
  * Contributors:
  *   Wayne Beaton - initial API and implementation
  *******************************************************************************/
 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();

 ob_start();

 $pageKeywords = "";
 $pageTitle = "Great Fixes for Eclipse Neon";
 $pageAuthor = "Wayne Beaton";
 ?>

 <div id="midcolumn">
 	<div class="homeitem">
 		<h1><?= $pageTitle ?></h1>
 		<p>
 			<b><?= $pageTitle ?></b> is a skills competition. Flex your
 			Eclipse development skills for an opportunity to win great prizes!
 		</p>
 		<p>
 			A <b>Great Fix</b> is a contribution provides a significant
 			improvement in one or more projects participating in the
 			<a href="http://projects.eclipse.org/releases/neon">Eclipse Neon Simultaneous Release</a>
 			in general, and in the <b>Desktop IDE experience</b> in particular.
 		</p>

 		<h2>Who Can participate?</h2>

 		<p>To qualify, you must be a contributor who is not a committer on the
 			project that accepts the contribution. So, you can be an Eclipse
 			committer on a different Eclipse project and qualify. Contributors
 			must have signed the Eclipse Foundation's Contributor License
 			Agreement (CLA). Members of the Eclipse Architecture Council are
 			ineligible.
 		</p>

 		<p>
 			A <b>Great Fix</b> must be fixed by the contributor on their own
 			qualifications (i.e. if your starting point is "I want to fix bug
 			xyz, but don't know much about the code. Please explain how I should
 			start", then&mdash;respectfully&mdash;this isn't for you).
 		</p>

 		<p>
 			<b>Void where prohibited by law.</b>
 		</p>

 		<h2 id="winners">Winners</h2>

 		<p>
 			We've started selecting winners and awarding prizes. There's still
 			time to join!
 		</p>

 		<ul>
 		<li><a href="https://waynebeaton.wordpress.com/2016/04/20/great-fixes-from-eric-williams/">Eric Williams</a></li>
 		</ul>

 		<h2 id="evaluation">Evaluation</h2>

 		<p>
 			To enter, all you need to do is a submit one or more patches.
 			All contributions that are accepted by the corresponding project
 			team and merged qualify.
 		</p>

 		<p>
 			To qualify for consideration as a <b>Great Fix</b>, a contribution must:
 		</p>

 		<ul>
 			<li>Be for a project that is participating in the Eclipse Neon Simultaneous Release;</li>
 			<li>Be submitted between June 24/2015 and May 26/2016;</li>
 			<li>Be submitted by a non-committer;</li>
 			<li>Be accepted by a project committer and merged into the
 				corresponding source code repository; and</li>
 			<li>Be deemed &quot;significant&quot; by the Architecture Council.</li>
 		</ul>

 		<p>
 			Fixes may be considered individually or in groups.
 		</p>

 		<p>
 			Priority will be given to fixes that address the issues
 			<a href="https://dev.eclipse.org/mhonarc/lists/eclipse.org-architecture-council/msg02789.html">identified as high-value</a>
 			by the Architecture Council or otherwise improve the desktop IDE experience (more details below).
 		</p>

 		<h2 id="prizes">Prizes</h2>

 		<p>
 			Winners will receive an Android tablet or Android Cell phone (details pending).
 			We will announce ten winners.
 		</p>

 		<h2 id="timing">Timing</h2>

 		<p>
 			This is the best part: this competition has been in progress since June 2015.
 			If you've submitted a patch that's been accepted, then you're already on the pool
 			of potential winners.
 			It's not too late to join. The final deadline to have your patches accepted is
 			May 26/2016, but the effective deadline for many projects is the Eclipse Neon M7 milestone
 			date (after M7, most projects will only accept critical fixes; check with the project team).
 		</p>

 		<p>
 			The Architecture Council will start picking weekly winners out of the pool on April 15th.
 		</p>


 		<h2 id="start">Where do I start?</h2>

 		<h3>Step One: Pick an issue</h3>

 		<p>
 			There are lots of issues to choose from. Start by reviewing the Architecture
 			Council's list of priority work areas:
 		</p>


 		<ul>
 			<li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=479686">Improve SWT/GTK 3.0+ integration</a>;</li>
 			<li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=480176">Allow user to discover plug-ins to edit a specific type of file</a>;</li>
 			<li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=482409">Improve SWT/MacOS integration</a>;</li>
 			<li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=482236">JVM selection UI in the launcher</a>;</li>
 			<li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=482034">p2 improvements</a>;</li>
 			<li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=480547">Prompt user to install additional plug-ins</a>;</li>
 			<li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=480177">WTP XML editor technology face-lift</a>;</li>
 			<li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=479536">Improve Tooling Support for <code>null</code> pointer analysis</a>;</li>
 			<li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=480551">Enable "refresh using native hooks"</a>;</li>
 			<li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=481227">Improve Dark Theme</a>; and</li>
 			<li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=480550">Tips &amp; tricks dialog</a>.</li>
 		</ul>

 		<p>
 			You will find pointers to the repositories and issue trackers for
 			projects specifically concerned with <b>Desktop IDE</b> functionality on
 			the corresponding project pages:
 		</p>

 		<ul>
 			<li><a href="http://projects.eclipse.org/projects/eclipse.platform">Eclipse Platform</a>;</li>
 			<li><a href="http://projects.eclipse.org/projects/eclipse.jdt">Eclipse Java development tools</a> (JDT);</li>
 			<li><a href="http://projects.eclipse.org/projects/tools.cdt">Eclipse C/C++ Development Tools</a> (CDT);</li>
 			<li><a href="http://projects.eclipse.org/projects/tools.pdt">Eclipse PHP Development Tools</a> (PDT);</li>
 			<li><a href="http://projects.eclipse.org/projects/webtools">Eclipse Web Tools</a>;</li>
 			<li><a href="http://projects.eclipse.org/projects/technology.egit">Eclipse Git Integration</a>;</li>
 			<li><a href="http://projects.eclipse.org/projects/technology.recommenders">Eclipse Code Recommenders</a>;</li>
 			<li><a href="http://projects.eclipse.org/projects/tools.andmore">Eclipse Andmore</a> (Eclipse Tools for Android Development);</li>
 			<li><a href="http://projects.eclipse.org/projects/technology.m2e">m2Eclipse</a> (Maven Integration);</li>
 			<li><a href="http://projects.eclipse.org/projects/tools.buildship">Eclipse Buildship</a> (Gradle Integration);</li>
             <li><a href="http://projects.eclipse.org/projects/rt.equinox">Eclipse Equinox</a>;</li>
             <li><a href="http://projects.eclipse.org/projects/tools.oomph">Eclipse Oomph</a>; and</li>
             <li><a href="http://projects.eclipse.org/projects/technology.subversive">Eclipse Subversive</a> (SVN Integration)</li>
 		</ul>

 		<p>
 			You may find other interesting projects to contribute to on the
 			<a href="https://projects.eclipse.org/releases/neon/details">Eclipse Neon Simultaneous Release</a> page.
 		</p>

 		<p>
 			Many projects annotate bug reports with the <code>bugday</code> and/or <code>helpwanted</code> keywords.
 			This is a good way to find specific features that are of interest to the corresponding project team
 			(thereby improving your odds of having your contribution accepted by the team).
 			For example:
 		</p>
 		<ul>

 			<li><a rel="nofollow" class="external text"
 				href="https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&classification=Eclipse&keywords=bugday&keywords_type=allwords&list_id=11139814&product=JDT&product=PDE&product=Platform&query_format=advanced">"Bug
 					Day" bugs for the Platform, JDT, and PDE</a>; and</li>
 			<li><a rel="nofollow" class="external text"
 				href="https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&classification=WebTools&list_id=11100076&query_format=advanced&status_whiteboard=greatfix_candidate&status_whiteboard_type=allwordssubstr ">Great
 					Fix candidates for the Web Tools project</a>;</li>
 		</ul>

 		<p>
 			When you've selected a bug, be sure to review the contribution guide for the project
 			(which should be in the root of the Git repository). If you're having trouble locating
 			the code, ask the project team for help either in their mailing list or on a bug.
 		</p>

 		<h3>Step Two: Sort out how to contribute</h3>

 		<p>
 			All projects provide a contribution guide that can help you know
 			what you need to do to ensure that your contribution is accepted.
 			For example:
 		</p>

 		<ul>
 			<li><a href="http://wiki.eclipse.org/Platform_UI/How_to_Contribute"
 				title="Platform UI/How to Contribute">How to Contribute to the
 					Platform UI Project</a>; or</li>
 			<li>You should find a contribution guide in the root of the Git
 				repository</li>
 		</ul>

 		<p>
 			Use the <a href="http://wiki.eclipse.org/Eclipse_Oomph_Installer"
 				title="Eclipse Oomph Installer">Eclipse Oomph Installer</a> to build
 			your development environment and provision your workspace with the
 			exact source code and workbench configuration you need to get started
 			immediately.
 		</p>

 		<h3>Step Three: Connect with the team</h3>

 		<p>
 			Discuss the bug via comments on the bug report and project
 			&quot;dev&quot; list.
 		</p>

 		<h3>Step Four: Contribute!</h3>

 		<p>
 			Push your fixes to the project's Gerrit/Git repository (be sure to
 			check the project's contribution guidelines).
 		</p>

 		<p>
 			Please review <a
 				href="https://wiki.eclipse.org/Development_Resources/Contributing_via_Git">Contributing
 				via Gerrit/Git</a>.
 		</p>

 		<h3>Step Five: Reap the Rewards</h3>

 		<p>
 			Bask in the glory.
 		</p>
 	</div>
 </div>


 <?php

 $html = ob_get_contents();
 ob_end_clean();
 $App->generatePage($theme, $Menu, $Nav, $pageAuthor, $pageKeywords, $pageTitle, $html );
 ?>
	<?php
	/*******************************************************************************
	* Copyright (c) 2015, 2016 Eclipse Foundation and others.
	* All rights reserved. This program and the accompanying materials
	* are made available under the terms of the Eclipse Public License v1.0
	* which accompanies this distribution, and is available at
	* http://www.eclipse.org/legal/epl-v10.html
	*
	* Contributors:
	* Wayne Beaton - initial API and implementation
	*******************************************************************************/
	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();

	ob_start();

	$pageKeywords = "";
	$pageTitle = "Great Fixes for Eclipse Neon";
	$pageAuthor = "Wayne Beaton";
	?>

	<div id="midcolumn">
	<div class="homeitem">
	<h1><?= $pageTitle ?></h1>
	<p>
	<b><?= $pageTitle ?></b> is a skills competition. Flex your
	Eclipse development skills for an opportunity to win great prizes!
	</p>
	<p>
	A <b>Great Fix</b> is a contribution provides a significant
	improvement in one or more projects participating in the
	<a href="http://projects.eclipse.org/releases/neon">Eclipse Neon Simultaneous Release</a>
	in general, and in the <b>Desktop IDE experience</b> in particular.
	</p>

	<h2>Who Can participate?</h2>

	<p>To qualify, you must be a contributor who is not a committer on the
	project that accepts the contribution. So, you can be an Eclipse
	committer on a different Eclipse project and qualify. Contributors
	must have signed the Eclipse Foundation's Contributor License
	Agreement (CLA). Members of the Eclipse Architecture Council are
	ineligible.
	</p>

	<p>
	A <b>Great Fix</b> must be fixed by the contributor on their own
	qualifications (i.e. if your starting point is "I want to fix bug
	xyz, but don't know much about the code. Please explain how I should
	start", then—respectfully—this isn't for you).
	</p>

	<p>
	<b>Void where prohibited by law.</b>
	</p>

	<h2 id="winners">Winners</h2>

	<p>
	We've started selecting winners and awarding prizes. There's still
	time to join!
	</p>

	<ul>
	<li><a href="https://waynebeaton.wordpress.com/2016/04/20/great-fixes-from-eric-williams/">Eric Williams</a></li>
	</ul>

	<h2 id="evaluation">Evaluation</h2>

	<p>
	To enter, all you need to do is a submit one or more patches.
	All contributions that are accepted by the corresponding project
	team and merged qualify.
	</p>

	<p>
	To qualify for consideration as a <b>Great Fix</b>, a contribution must:
	</p>

	<ul>
	<li>Be for a project that is participating in the Eclipse Neon Simultaneous Release;</li>
	<li>Be submitted between June 24/2015 and May 26/2016;</li>
	<li>Be submitted by a non-committer;</li>
	<li>Be accepted by a project committer and merged into the
	corresponding source code repository; and</li>
	<li>Be deemed "significant" by the Architecture Council.</li>
	</ul>

	<p>
	Fixes may be considered individually or in groups.
	</p>

	<p>
	Priority will be given to fixes that address the issues
	<a href="https://dev.eclipse.org/mhonarc/lists/eclipse.org-architecture-council/msg02789.html">identified as high-value</a>
	by the Architecture Council or otherwise improve the desktop IDE experience (more details below).
	</p>

	<h2 id="prizes">Prizes</h2>

	<p>
	Winners will receive an Android tablet or Android Cell phone (details pending).
	We will announce ten winners.
	</p>

	<h2 id="timing">Timing</h2>

	<p>
	This is the best part: this competition has been in progress since June 2015.
	If you've submitted a patch that's been accepted, then you're already on the pool
	of potential winners.
	It's not too late to join. The final deadline to have your patches accepted is
	May 26/2016, but the effective deadline for many projects is the Eclipse Neon M7 milestone
	date (after M7, most projects will only accept critical fixes; check with the project team).
	</p>

	<p>
	The Architecture Council will start picking weekly winners out of the pool on April 15th.
	</p>


	<h2 id="start">Where do I start?</h2>

	<h3>Step One: Pick an issue</h3>

	<p>
	There are lots of issues to choose from. Start by reviewing the Architecture
	Council's list of priority work areas:
	</p>


	<ul>
	<li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=479686">Improve SWT/GTK 3.0+ integration</a>;</li>
	<li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=480176">Allow user to discover plug-ins to edit a specific type of file</a>;</li>
	<li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=482409">Improve SWT/MacOS integration</a>;</li>
	<li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=482236">JVM selection UI in the launcher</a>;</li>
	<li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=482034">p2 improvements</a>;</li>
	<li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=480547">Prompt user to install additional plug-ins</a>;</li>
	<li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=480177">WTP XML editor technology face-lift</a>;</li>
	<li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=479536">Improve Tooling Support for <code>null</code> pointer analysis</a>;</li>
	<li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=480551">Enable "refresh using native hooks"</a>;</li>
	<li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=481227">Improve Dark Theme</a>; and</li>
	<li><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=480550">Tips & tricks dialog</a>.</li>
	</ul>

	<p>
	You will find pointers to the repositories and issue trackers for
	projects specifically concerned with <b>Desktop IDE</b> functionality on
	the corresponding project pages:
	</p>

	<ul>
	<li><a href="http://projects.eclipse.org/projects/eclipse.platform">Eclipse Platform</a>;</li>
	<li><a href="http://projects.eclipse.org/projects/eclipse.jdt">Eclipse Java development tools</a> (JDT);</li>
	<li><a href="http://projects.eclipse.org/projects/tools.cdt">Eclipse C/C++ Development Tools</a> (CDT);</li>
	<li><a href="http://projects.eclipse.org/projects/tools.pdt">Eclipse PHP Development Tools</a> (PDT);</li>
	<li><a href="http://projects.eclipse.org/projects/webtools">Eclipse Web Tools</a>;</li>
	<li><a href="http://projects.eclipse.org/projects/technology.egit">Eclipse Git Integration</a>;</li>
	<li><a href="http://projects.eclipse.org/projects/technology.recommenders">Eclipse Code Recommenders</a>;</li>
	<li><a href="http://projects.eclipse.org/projects/tools.andmore">Eclipse Andmore</a> (Eclipse Tools for Android Development);</li>
	<li><a href="http://projects.eclipse.org/projects/technology.m2e">m2Eclipse</a> (Maven Integration);</li>
	<li><a href="http://projects.eclipse.org/projects/tools.buildship">Eclipse Buildship</a> (Gradle Integration);</li>
	<li><a href="http://projects.eclipse.org/projects/rt.equinox">Eclipse Equinox</a>;</li>
	<li><a href="http://projects.eclipse.org/projects/tools.oomph">Eclipse Oomph</a>; and</li>
	<li><a href="http://projects.eclipse.org/projects/technology.subversive">Eclipse Subversive</a> (SVN Integration)</li>
	</ul>

	<p>
	You may find other interesting projects to contribute to on the
	<a href="https://projects.eclipse.org/releases/neon/details">Eclipse Neon Simultaneous Release</a> page.
	</p>

	<p>
	Many projects annotate bug reports with the <code>bugday</code> and/or <code>helpwanted</code> keywords.
	This is a good way to find specific features that are of interest to the corresponding project team
	(thereby improving your odds of having your contribution accepted by the team).
	For example:
	</p>
	<ul>

	<li><a rel="nofollow" class="external text"
	href="https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&classification=Eclipse&keywords=bugday&keywords_type=allwords&list_id=11139814&product=JDT&product=PDE&product=Platform&query_format=advanced">"Bug
	Day" bugs for the Platform, JDT, and PDE</a>; and</li>
	<li><a rel="nofollow" class="external text"
	href="https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&classification=WebTools&list_id=11100076&query_format=advanced&status_whiteboard=greatfix_candidate&status_whiteboard_type=allwordssubstr ">Great
	Fix candidates for the Web Tools project</a>;</li>
	</ul>

	<p>
	When you've selected a bug, be sure to review the contribution guide for the project
	(which should be in the root of the Git repository). If you're having trouble locating
	the code, ask the project team for help either in their mailing list or on a bug.
	</p>

	<h3>Step Two: Sort out how to contribute</h3>

	<p>
	All projects provide a contribution guide that can help you know
	what you need to do to ensure that your contribution is accepted.
	For example:
	</p>

	<ul>
	<li><a href="http://wiki.eclipse.org/Platform_UI/How_to_Contribute"
	title="Platform UI/How to Contribute">How to Contribute to the
	Platform UI Project</a>; or</li>
	<li>You should find a contribution guide in the root of the Git
	repository</li>
	</ul>

	<p>
	Use the <a href="http://wiki.eclipse.org/Eclipse_Oomph_Installer"
	title="Eclipse Oomph Installer">Eclipse Oomph Installer</a> to build
	your development environment and provision your workspace with the
	exact source code and workbench configuration you need to get started
	immediately.
	</p>

	<h3>Step Three: Connect with the team</h3>

	<p>
	Discuss the bug via comments on the bug report and project
	"dev" list.
	</p>

	<h3>Step Four: Contribute!</h3>

	<p>
	Push your fixes to the project's Gerrit/Git repository (be sure to
	check the project's contribution guidelines).
	</p>

	<p>
	Please review <a
	href="https://wiki.eclipse.org/Development_Resources/Contributing_via_Git">Contributing
	via Gerrit/Git</a>.
	</p>

	<h3>Step Five: Reap the Rewards</h3>

	<p>
	Bask in the glory.
	</p>
	</div>
	</div>


	<?php

	$html = ob_get_contents();
	ob_end_clean();
	$App->generatePage($theme, $Menu, $Nav, $pageAuthor, $pageKeywords, $pageTitle, $html );
	?>