Google Summer of Code 2014 Ideas
Existing bugs marked "helpwanted" are a good source of project ideas.
- Be creative
- Be specific: what do you want to be implemented
- If you are willing to mentor those ideas, add your name and email to the idea.
- GSoC project ideas should align with an existing Eclipse project
- If you're an interested student, add your name and email next to the idea. It is ok to have several students interested in one idea.
- Aspiring students and mentors need to register and submit their proposals on the SoC app
If you were a mentor last year then you are automatically in the list this year (the GSoC site may require that you re-register, but we think of you as "in").
Note that we only accept as mentors people who are known to us. This includes Eclipse committers. If you would like to be a mentor, please either introduce yourself to the group using the soc-dev mailing list, or send a note to EMO.
Idea proposal should contain the following information:
- project title, like "WTP - Improve auto-complete in xml editor"
- description with links to bug reports, project wiki pages, etc
- Reporter: who submitted idea (optional e-mail)
- Possible Mentors: who would like to mentor the students
- More info: other links or e-mail
- Eclipse Project: link to main eclipse project that improvement is targeting
- Potential students: who is interested (with optional e-mail). This one completely informal, to actually be interested you need to submit the proposal. Contact the idea owner or possible mentor to get some details before submitting it.
These are some ideas. Students feel free to base your GSoC proposals on these ideas (note that you are more likely to find a mentor for an idea that has been proposed by a mentor). Some of these ideas can be factored into multiple projects; a GSoC project proposal can work on parts of these ideas (i.e. you don't necessarily have to do it all).
There are other sources of ideas. There are numerous bugs in the Eclipse Bugzilla issue tracking system marked as "helpwanted" that may give you ideas.
Eclipse Code Recommenders: Snippet Sharing Infrastructure
Eclipse Code Recommenders comes with a code-snippet search called Snipmatch (developed during previous Google Summer of Codes). Snipmatch allows users to search for and insert code snippets right in their Java editor; all it takes is Ctrl+Enter and a full-text search springs to life.
Under the hood, Snipmatch searches a single snippet repository which is currently backed by a Git repo, to which users can upload new snippets using EGit. Doing so is not supported by Snipmatch's UI yet. Moreover, only a single snippet repository is supported, which makes it impossible to use multiple sources for your snippets.
The goal of this project is to create the necessary infrastructure to manage multiple snippet repositories, possibly with different backing implementations (Git repo, filesystem, Eclipse's built-in templates). Moreover, this project should develop a uniform UI for sharing snippets with other developers.
Additional Resources: Bug 427905
Possible Mentors: Andreas Sewe, Marcel Bruch (contact us on the mailing list)
Interested Student: Olav Lenz
Eclipse Code Recommenders: Livedoc XXL
With version 2.0, Eclipse Code Recommenders made the jump from the Eclipse IDE into the Web: With Livedoc (developed during the Google Summer of Code 2013) it became possible to enrich your good ol' Javadoc with intelligent recommendations on how to use an API.
Livedoc, a stand-alone command-line application makes it very easy to generate enriched Javadoc for your JARs. At the moment, however, it works one JAR at a time.
The goal of this project thus is to create to enhance Livedoc such that it becomes possible to create a large, interconnected web of documentation for different APIs (and in different versions) that can be deployed to download.eclipse.org as a showcase for Eclipse Code Recommenders and Livedoc. Who knows, it may even become the defaultJavadoc for other Eclipse projects.
Possible Mentors: Andreas Sewe (contact me on the mailing list)