Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Hackathon ECE 2013"

(Hackathon Theme)
(Who is Attending)
Line 11: Line 11:
 
The theme for this Hackathon will be creating your first commit to an Eclipse project. Contributing your first commit to an open source project is always the hardest one, because there is so much to learn. You're a smart developer so you know how to implement a fix or enhancement on a chunk of code once it is sitting in front of you. But first you need to learn where to get the source code, how to enter a bug, how to run the tests, how to follow the IP process, how to submit a patch for review, and how flag down a committer to get them to review and release it. At this Hackathon, seasoned committers from various Eclipse projects will be on hand to take you through all these steps. The goal will be to have a <b>real commit pushed to master</b> from new contributors. Armed with this knowledge you will be able to go home after the conference and continue contributing to the project, confident in understanding how the lifecycle of a change works on that project.
 
The theme for this Hackathon will be creating your first commit to an Eclipse project. Contributing your first commit to an open source project is always the hardest one, because there is so much to learn. You're a smart developer so you know how to implement a fix or enhancement on a chunk of code once it is sitting in front of you. But first you need to learn where to get the source code, how to enter a bug, how to run the tests, how to follow the IP process, how to submit a patch for review, and how flag down a committer to get them to review and release it. At this Hackathon, seasoned committers from various Eclipse projects will be on hand to take you through all these steps. The goal will be to have a <b>real commit pushed to master</b> from new contributors. Armed with this knowledge you will be able to go home after the conference and continue contributing to the project, confident in understanding how the lifecycle of a change works on that project.
  
= Who is Attending =
+
= What to Bring =
 +
== Committers ==
 +
 
 +
Committer volunteers should arrive with a list of known <b>simple</b> bugs that first time contributors can fix. Since the goal here is helping contributors understand the dev process, the nature of the bug isn't very important. For example it could be fixing typos, adding documentation, writing a test, etc. Bugs with one line fixes are fine. Maybe resist the temptation to fix this kind of bug yourself for the next month and save it for the Hackathon.
 +
 
 +
== Contributors ==
 +
 
 +
Contributors should bring a laptop with Eclipse Kepler or newer installed. It would be helpful to first clone the git repository of the project you want to contribute to, but if you don't know where that is, we can do it during the event.
 +
 
 +
= Participating Projects =
 +
 
 +
The following Eclipse projects will have committers attending the Hackathon, ready to help you make your first contribution.
 +
 
 +
* Eclipse Platform (John Arthorne)
 +
* Equinox p2 (John Arthorne)
 +
* Orion (John Arthorne, Anton McConville, Szymon Brandys)

Revision as of 16:45, 27 August 2013

When and Where

We are planning to hold a Hackathon at EclipseCon Europe 2013 in Ludwigsburg, Germany. Exact date and location to be determined, but the conference runs October 29-31, so it will be one of those days.

What is a Hackathon?

Hackathon is when a group of developers code together. We invite you to come and code with us. Learn new stuff, get code contributed to your favorite Eclipse projects, win prizes, meet new people and have some geek fun.

Hackathon Theme

The theme for this Hackathon will be creating your first commit to an Eclipse project. Contributing your first commit to an open source project is always the hardest one, because there is so much to learn. You're a smart developer so you know how to implement a fix or enhancement on a chunk of code once it is sitting in front of you. But first you need to learn where to get the source code, how to enter a bug, how to run the tests, how to follow the IP process, how to submit a patch for review, and how flag down a committer to get them to review and release it. At this Hackathon, seasoned committers from various Eclipse projects will be on hand to take you through all these steps. The goal will be to have a real commit pushed to master from new contributors. Armed with this knowledge you will be able to go home after the conference and continue contributing to the project, confident in understanding how the lifecycle of a change works on that project.

What to Bring

Committers

Committer volunteers should arrive with a list of known simple bugs that first time contributors can fix. Since the goal here is helping contributors understand the dev process, the nature of the bug isn't very important. For example it could be fixing typos, adding documentation, writing a test, etc. Bugs with one line fixes are fine. Maybe resist the temptation to fix this kind of bug yourself for the next month and save it for the Hackathon.

Contributors

Contributors should bring a laptop with Eclipse Kepler or newer installed. It would be helpful to first clone the git repository of the project you want to contribute to, but if you don't know where that is, we can do it during the event.

Participating Projects

The following Eclipse projects will have committers attending the Hackathon, ready to help you make your first contribution.

  • Eclipse Platform (John Arthorne)
  • Equinox p2 (John Arthorne)
  • Orion (John Arthorne, Anton McConville, Szymon Brandys)

Back to the top