links to this page:    
View this PageEdit this PageUploads to this PageHistory of this PageTop of the SwikiRecent ChangesSearch the SwikiHelp Guide
Google Summer of Code 2009 Organization Application
Last updated at 6:32 pm UTC on 18 March 2009

Squeak's Summer of Code 2009 application


Submission of mentoring organizations' applications: March 9th-13th
Submission of students' applications: March 23th - April 3rd
Google's timeline

Mailing list

The mailing list for this project is available at http://lists.squeakfoundation.org/mailman/listinfo/soc.


Google Summer of Code 2009 Project Ideas

Participants (w/ Google/Gmail account login)

Application questions

Link ID: squeak
Group Name: Squeak Smalltalk
Home Page URL: http://squeak.org
Public Email: askoh@askoh.com

Squeak Smalltalk is an organization dedicated to open source development of Squeak. Squeak is a programming environment for Smalltalk, written in Smalltalk by many of the original authors of Smalltalk. Its first edition was released in 1996, and it's currently at version 3.10, with a 3.11 version under development. It has spawned many related projects, both open source (AIDA/Web, Squeakland/Etoys, Croquet/Cobalt, Comikit, Scratch, Seaside, Sophie) and commercial (Plopp, DabbleDB, CMSBox). 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. The Squeak Foundation will be joining the Software Freedom Conservancy in the near future.

Why is your group applying to participate? What do you hope to gain by participating?
Squeak Smalltalk have been in the open source world for a long time. Participating in the Google Summer of Code 2007, 2008 programs has helped us gain more visibility. GSOC has also brought new blood to the group to develop new software that have become very useful. We would be foolish not to participate.

What is the main public mailing list for your group?

Where is the main IRC channel for your group?

#squeak at freenode

What criteria do you use to select the members of your group? Please be as specific as possible.
Requests for GSOC 2009 mentors were announced in squeak-dev@lists.squeakfoundation.org croquet-dev@duke.edu cobalt-dev@duke.edu emails to past mentors. Mentors sign up voluntarily. Mentors will be peer review once we get accepted for GSOC 2009. Most are long time contributors to Squeak Smalltalk.

Has your group participated previously? If so, please summarize your involvement and any past successes and failures.
We have participated in 2007 and 2008. GSOC 2008 was very successful for Squeak. All five projects delivered useful code at the end and are continuing. Safarŕ: an Extensible Code Editor for Squeak http://blog.summer.squeak.org/2008/10/safara-project-results-personal.html Squeak IRC bot framework http://wiki.squeak.org/squeak/579
Squeak GTK Support
freeCAD: 3D CAD with Motion Simulation Port to Croquet
OpenNARS port to Squeak using Seaside http://groups.google.com/group/open-nars/browse_thread/thread/744a3f84028cb69e
If your group has not previously participated, have you applied in the past? If so, for what sort of participation?

What license does your organization use?
MIT license

What is the URL to the ideas list of your organization?

What is the main development mailing list for your group?

What is the application template you would like contributors to your organization to use.

Student Name:

Student email:

Mentor Name:

Mentor email:

Project Title:

Project Description:

Why is project useful:

Why is student suited for project:

Project timeline:

How many hours can student commit to GSOC per week:

What is your plan for dealing with disappearing contributors?
We'll try to prevent student disappearing as follows:
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.

What is your plan for dealing with disappearing members?
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 contributors to interact with your community before, during, and after the program?
Squeak related mailing lists, newsgroups, forums, IRCs have always been pretty friendly and helpful to everyone from novices to experts. Mentors will shows students how helpful those community forums are and encourage students to post their problems to get help. One of the criterion for selecting students is the history of their online presence.

What will you do to ensure that your accepted contributors stick with the project after the program concludes?
First we will select projects that have longevity and value to the Squeak community and beyond. We will impress upon the students that their work can have global impact and/or have commercial value. Finally, Squeak Smalltalk is such a fun and productive programming environment that the students will not hesitate to use it whenever they can throughout their careers.

I Agree to the Admin Agreement:

Please select your backup group administrator.