Project Proposal Guidelines

This document describes a list of guidelines that can help you in preparing your application form for the Summer of Code 2012. We really suggest you to give a look to the following resource also:

http://summer.cs.pdx.edu/propose http://www.google-melange.com/document/show/gsoc_program/google/gsoc2012/faqs http://code.google.com/soc/

Requirements

Please, follow all the guidelines and rules defined by Google, as these are the most important requirements. A program like the Summer of Code can be very difficult to manage, especially for students in the European Community whose summer schedule is usually later than that in the United States, this is why we recommends that students do not work on other projects outside the GSoC, or limit the time spent on these project to a maximum of 10 hours per week, depending on the task being proposed.

All applicants must be reasonably fluent in the Java and C programming languages, and have strong knowledge of build tools like make. The GSoC is a mean of learning and gaining experience, and our mentors will do everything to help the student, but a student must start from a solid basis already to have a chance to successfully complete the program.

Proposal Outline

The guidelines offered by the GSoC FAQ page are generally enough for us, the FAQ provides two example, also linked here for reference: http://www.booki.cc/gsocstudentguide/_v/1.0/proposal-example-2/ and http://www.booki.cc/gsocstudentguide/_v/1.0/proposal-examples/

Ideas

* Contribute to the Caciocavallo Project.

Caciocavallo is a Toolkit written in order to easy the portability of Java to new platforms for the OpenJDK Challenge Contest. We have few ideas to chose from (but please, feel free to propose more):

1. We are interested in students that can help us fix bugs and write test cases. 2. One project that is particularly challenging is to rewrite the focus handling code. 3. We are also interested in running JavaFX on top of Cacio. 4. Another taks would be to adapt the rendering manager in the JDK in order to use different look and feel for Caciocavallo widgets and for Swing ones. 5. Finally, and most interestingly for us, we would love someone to keep the work we started last year about WebJDK. The task will be to improve CacioWeb and to integrate and improve and hopefully integrate WebJDK patches into the OpenJDK8 forest.

GoogleSoC2012 (last edited 2012-02-26 20:57:23 by neugens)