Skip to main content
Jump to: navigation, search

Difference between revisions of "Google Summer of Code 2011 Ideas"

(Sequoyah - Add multi-language support to Eclipse plugin projects using the Sequoyah Localization Editor)
(Ideas)
Line 25: Line 25:
  
 
=Ideas=
 
=Ideas=
 +
 +
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 "[https://bugs.eclipse.org/bugs/buglist.cgi?keywords=helpwanted;query_format=advanced;keywords_type=allwords;bug_status=NEW;bug_status=REOPENED helpwanted]" that may give you ideas.
  
 
==EGit / JGit - git-blame support==
 
==EGit / JGit - git-blame support==

Revision as of 22:44, 9 March 2011

Rules

  • 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

Mentors info

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.

Ideas submission

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.

Ideas

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.

EGit / JGit - git-blame support

It's about adding support for "git blame" in JGit (git library in Java) and EGit (Eclipse integration and UI). There is an early proposed draft for the jgit part by Benjamin Muskalla which is based on prior work from Manuel Woelker but there wasn't much progress on that in the last months.

If you are interested to have a closer look refer to the EGit Contributor Guide to find out how to setup your environment for contributing and maybe try to fix some low hanging fruit from our bug list to get a feeling what these projects are all about.

  • Reporter: Chris Aniszczyk
  • Possible Mentors: Chris Aniszczyk, Matthias Sohn
  • More info: EGit mailing list
  • Eclipse Project: EGit
  • Potential students: ???

Acceleo - Export profiling data to gprof

Acceleo has a nice profiling model, so it could be nice to be able to export this data to gprof files so that the user can leverage other more sophisticated tools to analyse the trace. See bug 293304. If you want to know more about the profiling in Acceleo see the user guide.

If you are interested to have a closer look refer to our Contributor Guide to find out how to setup your environment for contributing.

  • Reporter: Mariot Chauvin
  • Possible Mentors: Mariot Chauvin, Laurent Goubet, Cédric Brun
  • More info: M2T mailing list
  • Eclipse Project: Acceleo
  • Potential students: ?

EEF - Enhance the end user experience

EEF provides a three steps process to generate eye-candy user interface for your models. This process could be simplified by doing automatically several steps instead of asking the user to do it. See bug 338939 and bug 338942 for instance.


If you are interested to have a closer look refer to our Developer Guide to find out how to setup your environment for contributing.

  • Reporter: Mariot Chauvin
  • Possible Mentors: Mariot Chauvin, Goulwen Lefur
  • More info: EMFT mailing list
  • Eclipse Project: EEF
  • Potential students: ?

CDT - Build UI Improvements

Currently the CDT build UI is hidden away in Project Properties. We'd like to add nodes in the Project Explorer under each project to list the build configurations. Actions would be added to open up a build configuration editor to change the settings. Actions would be added for invoking build and clean, and for setting the default build and indexer configuration.

CDT - CMake and/or Qt qmake Builder Integration

CDT has it's own managed build system, but we are seeing more and more use of external managed builders such as CMake and Qt's qmake. We need to make sure the infrastructure is in place to allow for integration of these builders into the CDT builds. Then we need to implement them. CMake is a priority because there already exists a qmake builder. But then the qmake builder isn't very standard and could be redone.

Sequoyah - Add multi-language support to Eclipse plugin projects using the Sequoyah Localization Editor

The Sequoyah project is focused on Mobile application development tools. One of the components of Sequoyah is the Localization Files Editor (LFE), which is a visual editor for handling parallel resources for multi-language projects. The LFE has a reference implementation for Android, although it was written in a way so that the model is abstracted from the underlying implementation.

We are proposing a feature for the Sequoyah Localization Framework, which will extend support to Eclipse plugin projects. In order to do that, the framework must be changed to handle PDE projects, which contain strings files in the Java .properties format. The result will be a new set of editors that will allow Eclipse projects to localize themselves more easily.

The Eclipse Babel project has expressed interest in participating in this work.

  • Reporter: Marcel Gorri
  • Possible mentors: Marcel Gorri, Werner Keil (Babel)
  • More info: Sequoyah mailing list
  • Eclipse Project: Sequoyah
  • Potential students: TBD

Eclipse Project - My project title (THIS IS A SAMPLE)

Description with links and other information.

Back to the top