Google Summer of Code 2010

Process

Subpages

/Organisation Application

Timeline

February 8:	Program announced. Life is good.
March 8:~12 noon PST / 19:00 UTC	Mentoring organizations can begin submitting applications to Google.
March 12:4 PM PDT / 23:00 UTC	Mentoring organization application deadline.
March 13-17:	Google program administrators review organization applications.
March 18:~12 noon PDT / 19:00 UTC	List of accepted mentoring organizations published on the Google Summer of Code 2010 site.
March 18-29:	Would-be student participants discuss application ideas with mentoring organizations.
March 29:~12 noon PDT / 19:00 UTC	Student application period opens.
April 9:12 noon PDT / 19:00 UTC	Student application deadline.
Interim Period:	Mentoring organizations review and rank student proposals; where necessary, mentoring organizations may request further proposal detail from the student applicant.
April 21:	All mentors must be signed up and all student proposals matched with a mentor - 07:00 UTCStudent ranking/scoring deadline. Please do not add private comments with a nonzero score or mark students as ineligible (unless doing so as part of resolving duplicate accepted students) after this deadline - 17:00 UTCIRC meeting to resolve any outstanding duplicate accepted students - timing TBD, will be announced well in advance
April 26:~12 noon PDT / 19:00 UTC	Accepted student proposals announced on the Google Summer of Code 2010 site.
Community Bonding Period:	Students get to know mentors, read documentation, get up to speed to begin working on their projects.
May 24:	Students begin coding for their GSoC projects;Google begins issuing initial student payments provided tax forms are on file and students are in good standing with their communities.
Interim Period:	Mentors give students a helping hand and guidance on their projects.
July 12:~12 noon PDT / 19:00 UTC	Mentors and students can begin submitting mid-term evaluations.
July 16:12 noon PDT / 19:00 UTC	Mid-term evaluations deadline;Google begins issuing mid-term student payments provided passing student survey is on file.
Interim Period:	Mentors give students a helping hand and guidance on their projects.
August 9:	Suggested 'pencils down' date. Take a week to scrub code, write tests, improve documentation, etc.
August 16:~12 noon PDT / 19:00 UTC	Firm 'pencils down' date. Mentors, students and organization administrators can begin submitting final evaluations to Google.
August 20:12 noon PDT / 19:00 UTC	Final evaluation deadlineGoogle begins issuing student and mentoring organization payments provided forms and evaluations are on file.
August 23:	Final results of GSoC 2010 announced
August 30:	Students can begin submitting required code samples to Google
October (date TBD):	Mentor Summit at Google: Representatives from each successfully participating organization are invited to Google to greet, collaborate and code. Our mission for the weekend: make the program even better, have fun and make new friends.

Mentors

We will do the mentoring in a team. As we are all working on this project during our free time and all have real jobs during the day, we spread the tasks involved in mentoring so we can back up each other.

Tommi Mäkitalo (tntnet) - main openZIM developer, will take care for technical questions
Manuel Schneider (x80686) - openZIM project leader, will take care for all the paper stuff, evaluation etc., is available through IRC during the day

For coordination there will be regular IRC and Mumble meetings with the students and mentors. The schedule of this meetings should be at least twice a week and will be fixed as soon as the participants are fixed.

Ideas

openZIM GSoC Ideas in the context of Wikimedia Strategy

openZIM provides a solution - or at least a part of it - to most of the Wikimedia Offline proposals in the Wikimedia Strategy.

WMF Strategy: Outline for Recommendation #1 - content reuse from WMF projects

this is our target goal. With ZIM we provide a very efficient format which works for a variety of data types (hypertext, images and other files, categories...) and on a broad variety on platforms and devices (eg. it's optimized for very limited devices like handhelds). As an open documented standard and by the availability of GPLed libraries it can be easily be integrated in any reader application (severals are already available). ZIM files of all sources can be exchanged with any reader application and thus enables easy reuse of Wikimedia content.

The Foundation has decided to include ZIM as a regular dump file format. Other works have to be done before this can happen - namely fixing static dumps, Tomasz Finc is already working on that on Wikimedia's side.

Currently creating ZIM files involves a lot of manual work. Several publishers use different tools like Perl scripts to gather the content from MediaWiki and put it into a database. The libzim currently has an interface to read these contents from a database or other ZIM files to create new ZIM files. So automated ZIM file creation is still a missing gap.

Idea: MediaWiki extension to create ZIM files

Having a "one-click function" to export selected articles from MediaWiki was one of the first ideas the Wikimedia Foundation had when they decided to adopt ZIM. So this idea will become reality, enabling all users of MediaWiki to easily produce ZIM files, spreading the file format more widely and making it more usable outside Wikimedia.
While the static dumps are being fixed we can prepare the next step in the automated ZIM file creation. The libzim interface for the MediaWiki extension can be simply reused.

WMF Strategy: Outline of offline recommendation #2: Use of cellphones

As described in #1 the file format is very efficient and has been optimized for usage on devices with limited ressources.

Idea: zimreader for mobile phones

We don't have specific knowledge on how to write code for cell phones, but we have all the components - file format, free implementation, library - in place. So we had the idea of finding somebody to write sample application for the cell phone of his / her choice as a start.

WMF Strategy: Outline for Recommendation #3 - Schools

ZIM is already used at schools, mainly the Kiwix project (an user of openZIM) is very active in that area. Having a standardized format as described in #1 helps to provide schools with a large variety of compatible content which is updated frequently.

Beside that openZIM is working with Linux4Africa as they are about to adopt the ZIM file format using the openZIM zimreader application as a local webserver on their school servers.

Idea 1: MediaWiki extension to create ZIM files

content selection by user:
- add a selector to each article "include this article"
- provide a method to include categories / all articles with selected categories
- choose if images should be included as well or not
- choose if selected articles / category should be exported or the whole wiki
content selection by extension:
- make a list of all selected articles
- make a list of all categories needed
- make a list of all involved images / files
- gather a list of involved MIME types
ZIM header:
- send the list of content to zimlib
- create meta data for zimlib
- send MIME type list
ZIM content:
- provide an interface for zimlib where it can fetch article content
- retrieve HTML content of an article - only content section

Idea 2: zimreader for mobile phones

make a HTML viewer that uses zimlib to show contents on a mobile phone

can be

Symbian
J2ME

Student can decide which platform he / she likes better.