Skip to main content
Jump to: navigation, search

Difference between revisions of "Hackathon ECE 2013"

m (recategorized)
 
(34 intermediate revisions by 14 users not shown)
Line 1: Line 1:
 
= When and Where =  
 
= 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.
+
We are planning to hold a Hackathon at EclipseCon Europe 2013 in Ludwigsburg, Germany. The event will be held in the Wilhelm-Kramer-Zimmer (WKZ) room of the [http://www.eclipsecon.org/europe2013/venue Forum am Schlosspark].
 +
 
 +
We have the room reserved on Tuesday, 29th October from 20:30 to 22:30. See schedule [http://www.eclipsecon.org/europe2013/node/5315 part 1] and [http://www.eclipsecon.org/europe2013/node/5613 part 2].
  
 
= What is a Hackathon? =
 
= What is a Hackathon? =
Line 9: Line 11:
 
= Hackathon Theme =
 
= 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 <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 to 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.
  
 
= What to Bring =
 
= What to Bring =
Line 15: Line 17:
  
 
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.
 
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.
 +
 +
It is also a good idea to have an up to date [http://wiki.eclipse.org/Category:How_to_Contribute How to Contribute] page for your project. This gives contributors a useful starting place, and a summary of all the things they need to know as a reference for after the Hackathon ends. To give a concrete example, look at the [[Platform UI/How to Contribute]] page.
  
 
== Contributors ==
 
== 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.
+
All attendees should bring a laptop with Eclipse Kepler or newer installed. Please try to clone the Git repository in advance for the project you want to work on. You can likely find a link on the project's wiki page, or find it at [http://git.eclipse.org/c git.eclipse.org]. If you have trouble finding it, don't worry! A committer can help you get that setup during the event.
 +
 
 +
It is also a good idea to make sure you have an eclipse.org (bugzilla) account already created (see [http://projects.eclipse.org/user/login/sso projects.eclipse.org] to make sure). Also it is a good idea to sign the Eclipse [http://www.eclipse.org/legal/clafaq.php Contributor License Agreement], which is done from your profile page on [http://projects.eclipse.org projects.eclipse.org].
  
 
= Participating Projects =
 
= Participating Projects =
Line 24: Line 30:
 
The following Eclipse projects will have committers attending the Hackathon, ready to help you make your first contribution.
 
The following Eclipse projects will have committers attending the Hackathon, ready to help you make your first contribution.
  
* Eclipse Platform (John Arthorne)
+
* [http://eclipse.org/ecf Eclipse Communication Framework (ECF)] (Markus A. Kuppe)
* Equinox p2 (John Arthorne)
+
** [https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&classification=RT&keywords=helpwanted%2C%20&keywords_type=allwords&list_id=7300016&product=ECF&query_format=advanced&order=bug_id%20DESC&query_based_on= Help Wanted Bugs]
* Orion (John Arthorne, Anton McConville, Szymon Brandys)
+
* e4 tools (Lars Vogel)
 
* EMF-IncQuery (Istvan Rath)
 
* EMF-IncQuery (Istvan Rath)
 +
* [http://eclipse.org/emfclient EMF Client Platform] (Jonas Helming)
 +
* [http://eclipse.org/emfstore EMFStore] (Maximilian Koegel)
 +
* [http://www.eclipse.org/jgit/ JGit], [http://www.eclipse.org/egit/ EGit] (Matthias Sohn, [https://twitter.com/niborst Robin Stocker]) --- ([[EGit/Contributor_Guide|Contributor Guide]])
 +
* JBoss Tools [http://github.com/jbosstools GitHub] (Max Rydahl Andersen)
 +
* [http://eclipse.org/jubula/ Jubula Functional Testing Tool] (Markus Tiede) --- ([[Jubula/JubulaContribGuid|Contributor Guide]]) --- please [https://dev.eclipse.org/mailman/listinfo/jubula-dev contact us] beforehand
 +
* [http://eclipse.org/mylyn Mylyn] (Steffen Pingel, Benjamin Muskalla)
 +
* [http://eclipse.org/nebula Nebula (Custom UI Widgets)] (Wim Jongman) --- ([[Nebula/New Contributions|Contribution Guide]])
 +
* [[Orion]] (John Arthorne, Anton McConville, Szymon Brandys)
 +
* [[p2]] (John Arthorne)
 +
* [http://scala-ide.org/ Scala IDE] (Mirco Dotta) --- ([https://github.com/scala-ide/scala-ide/blob/master/CONTRIBUTING.md  Contributor Guide] and [http://scala-ide.org/docs/dev/index.html Developer Documentation]) --- please [https://groups.google.com/forum/#!forum/scala-ide-dev contact us] beforehand
 +
* Eclipse Platform (John Arthorne)
 +
* [[SWTBot/Contributing|SWTBot]] Lorenzo Bettini (?), easy getting started topics
 +
** Contributing keyboad layout: [[SWTBot/Keyboard_Layouts#Creating_keyboard_layouts]]
 +
** Contributing Recorder rules: [[SWTBot/Generator#Extending_it]]
 +
** Fix FindBugs issues: https://dev.eclipse.org/sonar/drilldown/issues/org.eclipse.swtbot:parent?severity=CRITICAL
 +
 +
= Resources =
 +
 +
* [http://www.vogella.com/articles/Gerrit/article.html#eclipsegerritcontribution Guide to contributing to Eclipse via Gerrit]
 +
 +
[[Category:Hackathons]]

Latest revision as of 03:09, 30 April 2014

When and Where

We are planning to hold a Hackathon at EclipseCon Europe 2013 in Ludwigsburg, Germany. The event will be held in the Wilhelm-Kramer-Zimmer (WKZ) room of the Forum am Schlosspark.

We have the room reserved on Tuesday, 29th October from 20:30 to 22:30. See schedule part 1 and part 2.

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

It is also a good idea to have an up to date How to Contribute page for your project. This gives contributors a useful starting place, and a summary of all the things they need to know as a reference for after the Hackathon ends. To give a concrete example, look at the Platform UI/How to Contribute page.

Contributors

All attendees should bring a laptop with Eclipse Kepler or newer installed. Please try to clone the Git repository in advance for the project you want to work on. You can likely find a link on the project's wiki page, or find it at git.eclipse.org. If you have trouble finding it, don't worry! A committer can help you get that setup during the event.

It is also a good idea to make sure you have an eclipse.org (bugzilla) account already created (see projects.eclipse.org to make sure). Also it is a good idea to sign the Eclipse Contributor License Agreement, which is done from your profile page on projects.eclipse.org.

Participating Projects

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

Resources

Back to the top