Google Summer of Code
The Eclipse Foundation participates in Google's Summer of Code. Thank you for your interest in open source software development at the Eclipse Foundation. The Eclipse community is a great place to spend a summer learning, coding, participating and contributing. We are an exciting open source project with a vibrant community, and we look forward to your application and your project ideas.
A good way to meet those involved with the program is to participate in the soc-dev mailing list, or visit the #eclipse-soc and #eclipse IRC channels on Freenode, or the Eclipse SoC mattermost channel.
The program is administered by the Eclipse Management Organization. It's best if you use the public communication channel whenever possible; however, if you need to communicate in private, please feel free to send a note (please use the public channels for any project-related discussion).
You'll find a ideas page for the current year below.
Or you can look through our "helpwanted" bugs. There are a lot of potential projects in there. Have a look.
Search through our many open source projects to find something interesting. Note that you can find links to the Git repositories by clicking the "Developer Resources" tab on a page. All repositories should include a CONTRIBUTING file with project-specific contribution guidance.
Feel free to make your own suggestions. But do note that we give strong preference to student proposals that result in contribution to existing Eclipse open source projects.
Sign up for the soc-dev list to connect with our mentors and other members of the Eclipse GSoC community.
Sign the Eclipse Contributor Agreement to ensure that you are ready to make contributions.
Some Useful Stuff
There's help regarding how we expect Git Commits to be structured in the Eclipse Project Handbook (please don't feel like you have to read the entire handbook; treat it like a resource).
The Eclipse Foundation values rigorous Intellectual Property management. We care deeply about honoring software licenses and copyright. By signing the ECA (see above), you attest that all contributions that you make are authored 100% by you and that you have the necessary rights to contribute to our open source projects. Please work with a committer if you need to include third-party content with your contributions (we do have a due diligence process for handing third-party content).
After we've been accepted as a mentoring organization, we will have the opportunity to add mentors to the Eclipse Foundation's Google Summer of Code team. Google's process requires that mentors be invited to join the mentoring organization's team. The EMO will send a note to email@example.com when we're ready to start inviting mentors (that is, we'll tell you when it's time to ask to be invited).
Anybody who is a committer on an open source project hosted by the Eclipse Foundation can be a mentor. When the time comes, we'll ask you to send firstname.lastname@example.org a note with your name, the email address for your Google account, and the names of the projects for which you have committer status, and we'll set up an invitation. Non committers may be mentors, only if they have a project lead who can vouch for them. Project leads should expect to be asked why the individual is not a committer.
Mentoring takes a couple of different forms. First, as a mentor, you will be invited to help the team review and select student proposals. Student proposals will be accessible via the interface provided by Google. While reviewing proposals, mentors may opt select a proposal and offer to mentor a student. At that point, a mentor commits to working with the student for the term if that student proposal is ultimately selected.
Mentors should familiarize themselves with the Google Summer of Code Mentoring Guide.
In the lead up to the start of the programme in any given year, we need to assemble an "ideas" page for students. All Eclipse Committers can add project ideas before being formally invited as a mentor. Add your ideas to the current year "ideas" page (see below). Mark bugs you care about with the "helpwanted" keyword.
Sign up for the soc-dev list to connect with students and other members of the Eclipse GSoC community.
Please keep in mind that--for this to work--you will be required to invest some time looking at student proposals for projects that you might not necessarily have a direct interested in. We still value your input on these proposals.
- Google Summer of Code 2020 Ideas
- Google Summer of Code 2019 Ideas
- Google Summer of Code 2018 Ideas
- Google Summer of Code 2017 Ideas
- Google Summer of Code 2016
- Google Summer of Code 2016 Ideas
- Google Summer of Code 2015
- Google Summer of Code 2015 Ideas
- Google Summer of Code 2014
- Google Summer of Code 2014 Ideas
- Google Summer of Code 2013
- Google Summer of Code 2013 Ideas
- Google Summer of Code 2012
- Google Summer of Code 2012 Ideas
- Google Summer of Code 2011
- Google Summer of Code 2011 Ideas
- Google Summer of Code 2010
- Google Summer of Code 2010 Ideas
- Google Summer of Code 2009
- Google Summer of Code 2009 Ideas
- Google Summer of Code 2008
- Google Summer of Code 2008 Ideas
- Google Summer of Code 2008 improvements
- Google Summer of Code 2007
- Google Summer of Code 2007 Ideas
- Google Summer of Code 2006