Difference between revisions of "Google Summer of Code 2010"

From openZIM
Jump to: navigation, search
(Students Application Template)
(No difference)

Revision as of 14:55, 10 March 2010

Process

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.

Ideas

see also http://strategy.wikimedia.org/wiki/Task_force/Recommendations/Offline

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

zimreader for mobile phones

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

can be

  • Symbian
  • J2ME

Organisation Application

  • Organization Name: openZIM
  • Description:
    The openZIM project has two different targets:
    • the ZIM file format, an open, standardized file format to store Wiki content efficiently for offline usage
    • an open source implementation of the ZIM file format consisting of the zimlib, zimwriter and zimreader
    The openZIM project is sponsored by Wikimedia CH and supported by the Wikimedia Foundation.
    Currently we support MediaWiki and are working on having creation of ZIM files for all Wikimedia projects.
  • Home page: http://openzim.org/
  • Main Organization License: GNU General Public License (GPL)
  • Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating?
  • Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.
    no
  • If your organization participated in past GSoCs, please let us know the ratio of students passing to students allocated, e.g. 2006: 3/6 for 3 out of 6 students passed in 2006.
    n/a
  • If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?
    no
  • What is the URL for your ideas page? http://openzim.org/Google_Sommer_of_Code_2010
  • What is the main development mailing list for your organization? This question will be shown to students who would like to get more information about applying to your organization for GSoC 2010. If your organization uses more than one list, please make sure to include a description of the list so students know which to use.
    dev-l@openzim.org
  • What is the main IRC channel for your organization? irc://irc.freenode.net/openzim
  • Does your organization have an application template you would like to see students use? If so, please provide it now. Please note that it is a very good idea to ask students to provide you with their contact information as part of your template. Their contact details will not be shared with you automatically via the GSoC 2010 site.
    • name
    • location (city, country)
    • age
    • personal website
    • mail address
    • IRC nickname
    • Wikipedia username
    • your experience with mediawiki (usage, coding)
    • why did you choose this project for GSoC (motivation, expectations)?
    • would you be able to present your project at Wikimania Conference, June 9 - 11 2010?
  • What criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible:
    • technical competence in order to support the students to get their job done
    • time left to be available for the students to answer their questions
    • willingness to deal with students and provide the above
  • What is your plan for dealing with disappearing students?
    • trying to maintain contact
    • informing them about consequences of their absence
    • if possible discuss if they come back or if we cancel the project
    • if the above gives no results note the situation in the evaluation
  • What is your plan for dealing with disappearing mentors?
    very unlikely case as the main developer is part of the mentoring team
    • trying to maintain contact
    • if neccessary there is at least one fall-back available that will take over the responsibility
  • What steps will you take to encourage students to interact with your project's community before, during and after the program?
    they will be a full member of the development team, so they are involved in all processes with the project at least through the mailinglist
    they are free to participate on any developers meeting or other event of the openZIM such as ehibitions which are all sponsored by the project team (at least accommodation)
  • What will you do to ensure that your accepted students stick with the project after GSoC concludes?
    as written above they are a full member of the project team and have all rights and privileges within that. If they like the project - which we hope, but cannot influence - we think that they will stick with it.
  • Is there anything else you would like to tell the Google Summer of Code program administration team?
    We like the idea of GSoC and thank you very much for this opportunity for us to find skilled developers!
  • Backup Admin (Link ID):