Google Summer Of Code 2006

Eclipse is participating in Google's Summer of Code 2006.

Thank you for your interest in Eclipse. Eclipse 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.

Students, please sign up here. We will take great care to review your application which is important for us, and will provide you with feedback along the way.

Thanks for submitting a proposal!

Below you will find many resources when choosing a Summer of Code organization, writing your application, and choosing a project to work on.

Student requirements

Here is a short list of requirements that you must be able to meet in order to get accepted as a student participant in Google's Summer of Code program.

Working on your Eclipse project should be your primary activity for the summer.
You must be willing to provide weekly status reports.
You will be expected to learn how to use CVS or SVN and maintain your project in a public CVS or SVN repository. (more details to come using a SourceForge project later)
You need to have decent Java coding skills and basic knowledge of the Eclipse framework and API.

It is important that you can allocated a decent amount of time to your project. You may have a lot to learn before you will get to the point where you can begin coding your project, and the projects are all non-trivial. We will provide you with support from the mentors and community, but it is up to you to make sure that you can focus on your Eclipse project.

Writing a Summer of Code application

We are likely to receive more than 100 proposals. Competition will be fierce, so what can you do to help make sure your application gets serious consideration? Here are some tips.

Sell your idea. Describe your idea in detail. What is its ultimate goal? What components will it have? What benefits does it have for Eclipse itself and its community? How do you plan to achieve completion of your project? If a specification already exists, what will you do that will go above and beyond expectations?

Sell yourself. Get across your enthusiasm for the project. Tell us what makes you stand out from the rest of the crowd. Talk about your past experiences, what makes you tick. Why are you interested in open source software, and Eclipse in particular? What interests do you have, and how do these interests relate to the project for which you're applying? There is a basic assumption that people applying for Summer of Code will have at least some programming skills already. So rather than spend a lot of time elaborating on these (though by all means, do tell us what you know), spend time talking about you.

Show enthusiasm. Summer of Code is an exciting opportunity, and Eclipse is an interesting project to work on. We're not just looking for people who want a summer job to pass the time, we're looking for devoted people who have an intrinsic passion for open source, and are (or will become) Eclipse experts and could make long lasting contributions to the community.

Tailor your application to the project. It was painfully obvious last year that certain people copied/pasted parts ( or even the entirety) of their applications to multiple projects. This can be seen from a mile away, and it is a sure-fire way for your application to not be taken seriously. Each application you send should be targeted and tailored for the specific mentoring organization and project to which you are applying.

Get feedback on your idea from the community. Discussing your idea with some established Eclipse folks is important. If your idea duplicates existing efforts or code (and does not provide a very convincing reason for doing so), it will be rejected. Try to have your application reviewed by someone before you submit it, whether that be the mentor for a particular project itself (in the case of already generated ideas below), or a person with expertise in a certain area. Don't be afraid to ask the community for help; we want you to succeed just as much as you do. :)
Good sources for help and feedback are the Eclipse Newsgroups and the IRC channels .

Don't be afraid to go out on a limb. Have a brilliant idea that's not covered by the proposals on the following pages? Great! Don't be scared to try and think "outside the box" and come up with a fantastic idea of your own. This is a wiki. You can just edit this page!

Note : 'Writing a Summer of Code Application ' is copyright by Angie Byron and Karoly Negyesi and available under a CC Attribution Share-Alike 2.0'
This page was also shamelessly borrowed and derived from http://dev.joomla.org/content/view/1360/85/

Some Eclipse Project Ideas

Fix the most popular bugs and feature requests: provide patches or fixes for any open bugzilla with at least 20 votes .
Cross platform Eclipse SWT embedded Firefox browser widget. This is one of the longest standing and most asked for Eclipse feature. This can be tricky though.
Eclipse JavaScript debugger: develop a working JavaScript debugging environment relying on an integration with the major browsers and available debuggers, possibly adding support for MacOS to complement the Ajax Toolkit Framework.
Eclipse IDE generator: building on some previous research work (Chris Laffra), provide an Eclipse IDE generation environment derived from a language grammar. This project would allow the creation of basic support of new or existing languages in Eclipse rapidly.
Add support for printing in Eclipse on Linux. yes! It does not have proper support yet.
Eclipse Mono Development Environment: a feature rich .Net development platform for Eclipse. The Java development tool may provide a great starting point. As this may be a big project, providing a project that accomplishes some significant contributions towards that goal is fine.
New Eclipse update manager: Eclipse current update manager is four years old and ridden with significant problems. This project would provide with a modern and original design for an automated software update for plugins and natives, if possible generic for OSGi based runtimes and could provide original inputs for a revamp of update in 3.3 to the platform team.
Eclipse key macros: this is one of the most requested and oldest pending feature on Eclipse. Think something like emacs style macros done right.
Eclipse key bindings manager: add support to Eclipse to create arbitrary bindings between keys and actions, even when not planned ahead by a plugin developer.
Eclipse multiple fast view bars: add support for multiple fast view bars in Eclipse (Only one is supported for now.)... and earn Erich Gamma gratitude for doing so as a bonus.
NetBeans in Eclipse: netclipse: the plugins models for Eclipse and NetBeans are very similar yet different. This project would provide the ability to run and embed a minimal NetBeans environment within Eclipse -- as Eclipse plugins-- , and support running NetBeans plugins like Matisse (Swing UI painter) or Coyote (dynamic languages toolkit).
Eclipse plugin search plugin: provide an Eclipse search function that makes searching navigation and browsing in the plugin code easier.
Eclipse RCP installer wizards: create Eclipse wizards to generate native graphical installers and packages for the major platforms: Windows , MacOSX, and Linux is, deb, emerge, rpms for an Eclipse Rich Client Platform application.
Eclipse Open Office Integration: provide OpenOffice as a set of minimal Eclipse plugins for each platforms integrated in Eclipse and packaged for RCP deployment
Eclipse install based manager: provide application and support for managing a large deployment of Eclipse based RCP clients, including pushed updates and client configurations.
Mylar Wiki integration, enabling context and embedded authoring for Wiki pages and tasks.
Mylar and ECF integration, enabling task contexts to be shared synchronously between developers. Possibly using XMPP and Google Talk messaging service
Voice-over-IP client implemented as RCP app using ECF call API and Google Talk call setup protocol (Jingle)
RCP real-time collaboration based upon ECF and Google Talk XMPP-based messaging service
Implementation of System-Tray API for Mac, allowing to control the Dock (See Bug 56116)
Embedding Editors and Views (See Bug 71125)
API for the Browser widget to set content from a Stream. Currently you can only call setText() or open an URL.
A way of communication from the Browser widget to the Java Application. It would be nice to have a method that returns the result of a JavaScript call (similiar to Browser#execute(), which currently only returns if the operation failed or not).
DOM support for the Browser via Java-API, avoiding to directly use JavaScript
An Eclipse Plug-in for Distributed Debugging. Currently, Eclipse has very little support for debugging distributed applications. There is an ongoing effort in developing an Eclipse framework for distributed debugging ; at the moment, it is targeting at applications based on Java/CORBA but it could be extended to other middleware platforms such as Java RMI and Web Services.
An Eclipse plugin for discovering run-time components that other plugins may need. For instance on MacOS, all the installed Java runtimes are automatically added to the list of installed Java runtimes. Having a similar feature to flexibly discover Java runtimes on Windows and Linux would be very helpful, looking for well-known installations locations, marker files, registries, or using file system scans. It could be even more generic and provide extensions points to contribute discovered runtimes in other areas: a Ruby, PHP, Python, Perl or C++ language runtime for the available open source plugins, or the discovery of installed servers or database runtimes for MySQl, Apache, Tomcat and so on. Third party plugins could subscribe to those services and provide auto-configuration of their own preferences.

Mentors

Currently, we have Wayne Beaton, Philippe Ombredanne, Mik Kersten and Gunnar Wagenknecht and few others (to be listed soon) as potential mentors.
For more information, please see The Eclipse SOC Landing Page.

Eclipse mentors, please sign up here (an administrator -- Wayne or Philippe -- will have to accept your application). After you've signed up (and have been accepted), visit the Mentor home page.

Last Modified 5/5/06 8:52 AM

Hide Tools

Site
Changes
Index
Search

User
Log In
Register