Skip to main content

Great Fixes for Eclipse Neon

Great Fixes for Eclipse Neon is a skills competition. Flex your Eclipse development skills for an opportunity to win great prizes!

A Great Fix is a contribution provides a significant improvement in one or more projects participating in the Eclipse Neon Simultaneous Release in general, and in the Desktop IDE experience in particular.

Who Can participate?

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.

A Great Fix 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).

Void where prohibited by law.

Winners

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

Evaluation

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.

To qualify for consideration as a Great Fix, a contribution must:

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

Fixes may be considered individually or in groups.

Priority will be given to fixes that address the issues identified as high-value by the Architecture Council or otherwise improve the desktop IDE experience (more details below).

Prizes

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

Timing

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).

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

Where do I start?

Step One: Pick an issue

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

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

You may find other interesting projects to contribute to on the Eclipse Neon Simultaneous Release page.

Many projects annotate bug reports with the bugday and/or helpwanted 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:

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.

Step Two: Sort out how to contribute

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:

Use the Eclipse Oomph Installer to build your development environment and provision your workspace with the exact source code and workbench configuration you need to get started immediately.

Step Three: Connect with the team

Discuss the bug via comments on the bug report and project "dev" list.

Step Four: Contribute!

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

Please review Contributing via Gerrit/Git.

Step Five: Reap the Rewards

Bask in the glory.

Back to the top