Google Summer of Code/2009

Google Summer of Code for detailed information.

Mentors needed
The last couple of years we’ve had limited success with the SoC, in part because we’ve been so shorthanded on mentors that we can’t support more than one or two students. I’m looking for a few MediaWiki hackers who’d like to help out this time around…

You’ll need to be reasonably available by e-mail and IRC, and able to help answer the student’s questions and review their progress.

Part of the fun of Summer of Code projects is that we can get somebody excited and involved by working on something that’s big enough that it hasn’t got done yet, but small enough that they can make real progress and hopefully get something in production over the course of a couple months.

The real important part is making sure they feel welcome, and are excited about continuing their involvement in MediaWiki development after they’re done… so let’s make everybody feel at home!

Mentor signup

 * Catrope
 * this could be you!

Student info
Student applications are not yet open; see the timeline on Google's FAQ.

If you want to get started early prepping your application, here's our /Application template.

Projects ideas!
'''This list needs some lovin'! Add, update and tweak...'''

MediaWiki core and new extensions

 * Support for Chemical Markup Language and Jmol viewer . See 16491. Also more general 17598
 * Special pages improvements. See 6220, 10049, 12925, 12942, 12984, etc.
 * Upload log improvements. See 14171, 14417.
 * Tiff file format support.
 * Bot for automation interwikis adding for categories by countries, albums by artist, interwikis for categories based on interwikis for articles. See http://lists.wikimedia.org/pipermail/wikibots-l/2008-July/thread.html.
 * Special page to change wiki configuration variables via the web with built in validation before changes are made permanent.
 * Isn't this partially done with Configure?


 * Special page to automatically upgrade/downgrade the database between versions of MediaWiki (which could be hooked into by extensions).
 * Upgrade the installer to allow for automatic download, installation, and configuration of extensions. Include a special page to do live updates of extensions
 * Image rendering and resizing daemon
 * Particularly automate collection of identical messages when original English message changed/updated. Also automate draft translation of untranslated messages for particular language.
 * Proper geocoding extension for Wikipedia. This extension would include the coordinates into the articles, have keywords and formatting functions for coordinate output, have a coordinates editor/viewer, allow queries, and possibly generate geotags and geo (microformat). There is already much code for this (e. g. Category:GIS_extensions, map extensions), but the idea would be to combine everything into an extension that would be suitable for deployment on Wikipedia.
 * Coordinate entry interface (optional)
 * Simple coordinate entry format in wikitext
 * Coordinate handling, validation, conversion and display formatting without the use of templates such as en:Template:Coord
 * Support for links to external services by using a wiki-editable page with extension specific magic words on the coordinates and their metadata, offering various conversions. Currently done with GeoHack and en:Template:GeoTemplate.
 * Separate database table for coordinates to allow quick queries
 * API integration to allow replacing tools currently hacked over database dumps or the externallinks table, such as bounding box based queries as a list or map type, list of coordinates failing validation criteria, exporting coordinates from a page or category as used on en:Template:GeoGroupTemplate. That is, coordinate queries based on their content and/or source, and output formatting in API or some external tool that could then use the API. This could possibly replace some of the coordinate database functionality in WikiMiniAtlas.
 * Share geo information for multiple wikis in single wiki to avoid jobs duplication across all Wikipedias/Commons/other projects. See m:Talk:A newer look at the interlanguage link.


 * User-configurable cookie-ified date format—even for anonymous users—to properly support an international audience.
 * User-configurable cookie-ified image thumbnail size preference for anonymous users—to support a variety of browsing and communications technology from iPhones to Crays, high speed to pathetic link speeds. Other means of reducing/optimizing bandwidth like a "more" function, or preferred article sections by user preference (lead only, first image only, omit see also, references, etc.)
 * Easy integration of OpenStreetMap maps in articles, preferably by only using coordinates and of course, no images but fully usable Javascript-enabled maps, pref. based on something like OpenLayers - Husky 12:06, 11 March 2009 (UTC)
 * Making Wikiportrait into an extension that supports automatic uploads to Commons and easy OTRS integration. - Husky 12:06, 11 March 2009 (UTC)
 * Improve Visual Diff, a GSoC 2008 project
 * MediaWiki to slideshow --Currently at an exploratory stage of development. Uncertain of mentor organisation.
 * Watchlist upgrade, i.e. multiple watchlists on the same project, a global watchlist for SUL, etc. See w:Wikipedia:PERSISTENT, etc.

Existing extensions

 * MetavidWiki ! summer of code page here
 * Add support for additional mapping services, such as OpenLayers and Google Earth, to Semantic MediaWiki (currently only Google Maps is fully supported and OpenLayers partially supported) Yaron Koren 16:12, 11 March 2009 (UTC)

Services and other outside technology

 * Make Translation platform more efficient in terms of speed and tools for translators and administrators
 * Wikipedia widget for easy inclusion on other websites that display articles and images based on the content of that page - Husky 12:06, 11 March 2009 (UTC)

Previous Years

 * Summer of Code: 2006, 2007 and 2008 notes.