Summer of Code 2008 Application
Last updated at 7:27 pm UTC on 31 March 2008
Squeak's Summer of Code 2008 application
This is the working page for Squeak's application to Google's Summer of Code 2008 program.
Submission of mentoring organizations' applications: March 5th-12th
Submission of students' applications: March 24th-?
The mailing list for this project is available at http://lists.squeakfoundation.org/mailman/listinfo/soc.
Project Ideas for Google Summer of Code 2008
Participants (w/ Google/Gmail account)
- Giovanni Corriga (gcorriga)
- Possible Mentors
- Aik-Siong Koh (email@example.com)
- Andreas Raab (andreas.raab)
- Esteban Lorenzano (estebanlm)
- Lukas Renggli (renggli)
- Janko Mivšek (janko.mivsek)
- Mathieu Suen (firstname.lastname@example.org)
- Stephane Ducasse (email@example.com)
- Pei Wang, OpenNars project (NARS.Wang)
- Klaus D. Witzel (firstname.lastname@example.org)
- Ken Causey (klcausey)
- Brian Rice (email@example.com)
- Matthew Fulmer (firstname.lastname@example.org)
- Tansel Ersavas (email@example.com)
- Ralph Johnson (firstname.lastname@example.org)
- Adrian Kuhn (email@example.com)
- Toon Verwaest (firstname.lastname@example.org)
- Possible Students
- Cédrick Béler (cdrick65), OpenNars port to Squeak using Seaside, full time not before June
- Ya Wen Chai (email@example.com), freeCAD port to Croquet
- Khai Fong Phua (firstname.lastname@example.org), freeCAD port to Croquet
- Keng Fai Wong (email@example.com), freeCAD port to Croquet
- Mariano Martinez Peck (firstname.lastname@example.org), plugin OpenDBX for Squeak
- Hilaire Fernandes (email@example.com), DrGeo II
- François Stephany (firstname.lastname@example.org), Squeak IRC Bot
- Fernando Olivero (email@example.com), Maze Resolution Browser
- Nicolas Petton (firstname.lastname@example.org), Squeak code on the Web
There's a list of questions that will be asked by Google as part of the application project. Here's a copy of the questions, along with answers.
All these questions must have answers before March 10th.
We are aware that Smalltalk has a peculiar approach to computing and to development, and that getting your head around it and becoming part of the community may not be as easy as with some other languages. Participanting in the Google Summer of Code program will help the mentors, and the community at large, to better bring people into the community and make them feel welcome.
- Describe your organization.
The Squeak Project is a small organization dedicated to support Squeak's development. Squeak is a Smalltalk dialect and a programming environment created by many of the original Smalltalk authors. Its first edition was released in 1996, and it's currently at version 3.9, with a 3.10 version under development. It has spawned many related projects, both non-commercial (such as Squeakland, Croquet, Scratch, Sophie) and commercial (Plopp, DabbleDB, CMSBox). It's also the main developer platform for the Seaside web framework.
The Squeak Foundation takes care of all the bureaucratic tasks for the Squeak community (providing funding for server and connectivity costs, etc.); all the other tasks and problems, including technical ones, are handled by the community.
By partecipating as the Squeak Foundation, instead of simply Squeak as in the 2007 edition of the GSoC, we aim to muster a larger involvement from the various communities related to Squeak.
The Squeak Foundation will be joining the Software Freedom Conservancy in the near future.
- Why is your organization applying to participate in GSoC 2008? What do you hope to gain by participating?
Smalltalk and Squeak have remained on the corner of the open source world for a long time. Participating in the Google Summer of Code 2007 program has helped us gain some more visibility, so we're hoping to be able to repeat the experience this year.
Finally, having developers who are paid to work on our software will give us an opportunity to improve our programming environment and tools to make them more uniform and accessible.
- Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and failures of your student projects.
The Squeak Project participated as Squeak in the 2007 edition of the GSoC with five students. One of them was a complete newcomer to the language and the community, and is now a stable member of our group. All the students completed their 2007 projects; of these projects, one will be included in the next release of Squeak, one is still under active development, while the other three have produced add-ons to other projects and are available on our package repository (This past three projects haven't seen much development after the end of GSoC2007, unfortunately). We're particularly happy with the fact that one of last year's student has volunteered to be a mentor for this year's edition.
- If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?
- Who will your organization administrator be? Please include Google Account information.
The administrator for the SoC 2008 program will be Giovanni Corriga (Google Account: gcorriga).
- What license does your project use?
Squeak 1.1 is triple licensed: Squeak License, APSL2, ASL. All new code is produced under the MIT license. The Squeak Foundation is undergoing an effort in order to relicense all produced code under the MIT License; this effort is now near completion.
- What is the URL for your ideas page?
Project Ideas for Google Summer of Code 2008 - http://wiki.squeak.org/squeak/6032
- What is the main development mailing list for your organization?
- What is the main IRC channel for your organization?
#squeak on the Freenode network.
- Does your organization have an application template you would like to see students use? If so, please provide it now.
- Who will be your backup organization administrator? Please include Google Account information.
email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, NARS.Wang@gmail.com, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org
- Who will your mentors be? Please include Google Account Information.
- What criteria did you use to select these individuals as mentors? Please be as specific as possible.
The mentors has been selected amongst those who volunteered for the job. All the selected volunteers are longstanding members of the Squeak and Smalltalk communities; most of them already had mentoring experiences (as university professors and researchers).
- What is your plan for dealing with disappearing students?
We'll try to prevent student disappearing:
Before the project starts, we'll collect their contact info, both online and offline (IM contacts, skype contacts, phone numbers). In case this doesn't work, we'll call the A-Team.
- the students will be involved in defining the details of their projects.
- Mentors will offer regular online meetings in addition to the email support.
- The projects will also be advertised in the community early in the process (early April), and we'll ask the community for feedback to show to the students that their work is valued.
- What is your plan for dealing with disappearing mentors?
Before the project starts, we'll collect all the mentors' contact info. Students will have the info for their mentors.
We'll assign two mentors per student, so that in case one of them disappears, the other one will still be there. We'll have a couple of backup mentors ready to step up in case of mentor disappearances.
- What steps will you take to encourage students to interact with your project's community before, during and after the program?
We'll try to have periodic (weekly or bi-weekly) IM/IRC meetings with them. We'll ask them to subscribe to the development lists. We'll encourage them to join our blog (syndicated on Planet Squeak and Planet Smalltalk) and to hang around on the IRC channel.
- What will you do to ensure that your accepted students stick with the project after GSoC concludes?
First of all, we trust that the accepted students won't be "in it for the money", so they will be interested in sticking with the project even after the conclusion of GSoC.
Also, the ideas that we'd like to propose will be fun enough to keep the students' interest piqued.
Finally, the students' work will possibly be included in the main Squeak or related distributions (either in the main codelines or as add-on packages)