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.
Hackathon EclipseCon 2015
When and Where
We are planning to hold a Hackathon at EclipseCon 2015 in San Francisco. The event will be held at the Hyatt Regency San Francisco Airport. We have the room reserved for Tuesday, March 10, 7:00pm (19:00).
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.
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
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.
Please note that your project doesn't need to be hosted at Eclipse in order to participate.
We recommend that all contributors do the following before attending:
- Install Eclipse Luna or newer on your laptop.
- Try to clone the Git repository 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 set it up during the event.
- Ensure you have an eclipse.org (Bugzilla) account created (see projects.eclipse.org to make sure).
- Sign the Eclipse Contributor License Agreement, which is done from your profile page on projects.eclipse.org.
Again, don't worry if you have trouble with any of this. We can help during the Hackathon.
The following Eclipse projects will have committers attending the Hackathon, ready to help you make your first contribution.
- Mylyn Docs
- Mylyn Builds
- JGit and EGit
- Eclipse e4/Platform UI
- Easier & smarter import of projects
- C/C++ Development Toolkit (CDT)
- ...add your project here...
In case you wish to contribute that is not listed here, come anyway. It is almost sure one person in the room will be able to give you some help.