Google Summer of Code 2009 Ideas




 * Back to the main OSGeo Google Summer of Code 2009 wiki page.

=OSGeo Google Summer of Code 2009= The Open Source Geospatial Foundation would like to extend a welcome to all SoC students. On this page you will find links to a host of ideas organized by project. You will find ideas ranging from the depths of computer science graph theory to the heights of visualization. One thing all these ideas have in common is lots and lots of spatial data.

These ideas are *only* to motivate you, and serve as example of the kind of hills we want to charge up. Your own ideas are more than welcomed - they are encouraged. We view you as the next wave of open source leaders; show us what you've got.

If you need more information on how to apply you can contact all the mentoring organisations via soc at lists.osgeo.org


 * There is a Google SoC flyer to look at and post in appropriate places.

=What to expect during the summer?=

Be prepared to be in constant communication with your mentors and project
You and your mentors will decide on the specifics, but we will expect you and your mentor to communicate *a lot*. Part of the idea of SoC is to intergrate you into the developer community, so you should get involved from the start. The more you communicate the easier it will be. Don't be afraid that the mentors will request your phone number. It is only to make sure that we can reach you, in case of problems.

Weekly reports
Yes, every week we expect to see a report that at least answers the following questions:
 * 1) What did you get done this week?
 * 2) What do you plan on doing next week?
 * 3) Are you blocked on anything?

If you want, feel free to write *more*. But three sentences is the bare minimum. *IT IS VERY IMPORTANT THAT YOU SEND YOUR PROGRESS REPORTS ON TIME*, if you don't send this email your mentors will start to get twitchy, and *especially* if they don't get any responses to their emails / don't see you in IRC. Twitchy mentors is not what we want. If you are blocked by finals, that's cool. We have all studied at some point, just tell us about it, be honest. If you don't know how to proceed and your mentor isn't answering *definitely* tell about it. The SoC project admins will always be available. Basically the point is that you open up the communication channels, and keep them open. That way you will have a super summer, and get paid ;)

Last year this weekly report proved to be very popular among the students and mentors alike, so we will keep it up.

Wiki page
In addition to weekly reports we ask you to maintain a wiki page for your project. You should store your weekly reports there and add other information, like how to compile and test your program. If applicable add screenshots and other nice info.

=Timeline= http://socghop.appspot.com/document/show/program/google/gsoc2009/faqs#timeline


 * March 18th 2009: Google announces accepted organisations. If OSGeo is accepted as an organization for Google Summer of Code, start talking to us earlier rather than later.
 * April 3rd 2009: Student application deadline. The earlier you start the more probable it is that you will be accepted!
 * April 20th 2009: Accepted student proposals are announced.
 * May 23rd 2009: Coding begins!
 * July 6th - July 13th: Mid-term evaluation.
 * Agust 10th: Pencils down!

= What is the URL for your ideas page? = Each participating project's list of ideas is here, with a short description of the project and what type of students would be interested in it.


 * OpenLayers: OpenLayers is a Javascript based mapping client, similar to the Javascript used to power Google Maps and other similar mapping websites. Ideas run the full range of math-oriented vector operations to full scale browser-based GIS application development. Good place to look if you're interested in Javascript.
 * GDAL SoC Ideas: GDAL is the Geographic Data Abstraction Library, a library which provides access to spatial data in all kinds of formats via a uniform API.
 * GRASS SoC Ideas: GRASS GIS is an open source GIS focusing mainly on analysis. It is written as a collection of stand-alone C programs and has a new GUI written in Python. If you know Python, or want to implement algorithms in C take a look!
 * Mapbender SoC ideas 2009: Mapbender is a server and client side geographic data management tool, programmed in PHP and JavaScript, using the jQuery library.
 * Quantum GIS SoC Ideas Quantum GIS (QGIS) is a user friendly Open Source Geographic Information System (GIS) that runs on Linux, Unix, Mac OSX, and Windows. QGIS supports vector, raster, and database formats.
 * MapServer 2009 SOC Ideas
 * Laval University 2009 SoC ideas: Based on OpenLayers and other relevant software from OSGeo, this project aims at designing and developing a tool to produce rich and interactive geo-analytical dashboards. Such dashboards will serve as a front end for a range of Spatial OLAP technologies to better support decision makers, managers, etc. in making informed decisions.
 * GeoServer SoC 2009: GeoServer supports Web Map Server, Web Feature Server and Web Coverage Service protocols. It makes spatial information available in a range of formats from GeoTIFF to KML. The application is Java EE based, making use of Spring to wire everything up. The application supports a plug-in system so student contributions can me distributed as they are ready.
 * GeoTools SoC 2009: GeoTools is a Java toolkit for working with spatial data, it covers everything from bits on disk to rendering. It provides client code for WFS, WMS and supports a range of data sources like shapefile and PostGIS. The library is used by a lot of the Java applications on this page. The library has a plug-in system so students work can be distributed via maven as they are ready.
 * uDig SoC 2009: User-friendly Desktop GIS is a Java application written with the Eclipse RCP framework. The project has a community svn area to host student plug-ins, tutorials cover how to package up a custom application to show off your work.
 * OpenJUMP/deegree Ideas List: deegree and OpenJUMP share code derived from the original JUMP. Both programs maintain separate development lists and source code repositories but look for opportunities to collaborate.
 * OSGeo Cartographic Library: A cross-project effort to define a cartography output specification, and ideally, to create an example engine or set of scripts to produce high quality printable output. Then other projects can export to this standard and share in the benefit of a common engine.

= What is the main public mailing list for your organization? = Since OSGeo is an umbrella organisation for multiple projects, each project has their own discussion and development mailing lists.

Main OSGeo mailing lists of interest to students.

Please start here, when contacting us for the first time with questions about Google Summer of Code.


 * OSGeo SoC Mentors and Students - soc@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/soc)
 * OSGeo Wide Discussion List - discuss@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/discuss)

Also see the Mailing Lists page.

Project development lists


 * GeoServer - geoserver-devel@lists.sourceforge.net ( http://lists.sourceforge.net/lists/listinfo/geoserver-devel )
 * GeoTools - geotools-devel@lists.sourceforge.net ( http://lists.sourceforge.net/lists/listinfo/geotools-devel )
 * uDig - udig-devel@lists.refractions.net ( http://lists.refractions.net/mailman/listinfo/udig-devel )
 * MapGuide - mapguide-internals@lists.osgeo.org ( http://lists.osgeo.org/mailman/listinfo/mapguide-internals )
 * OpenJUMP - jump-pilot-devel@lists.sourceforge.net ( http://lists.sourceforge.net/lists/listinfo/jump-pilot-devel )
 * MapServer - mapserver-dev@lists.osgeo.org ( http://lists.osgeo.org/mailman/listinfo/mapserver-dev )
 * GDAL - gdal-dev@lists.osgeo.org ( http://lists.osgeo.org/mailman/listinfo/gdal-dev )
 * PostGIS - postgis-users@postgis.refractions.net ( http://postgis.refractions.net/mailman/listinfo/postgis-users )
 * GRASS - grass-dev@lists.osgeo.org ( http://lists.osgeo.org/mailman/listinfo/grass-dev )
 * Quantum GIS - qgis-developer@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/qgis-developer)
 * Mapbender - mapbender_dev@lists.osgeo.org ( http://lists.osgeo.org/mailman/listinfo/mapbender_dev )
 * OpenJUMP - jump-pilot-devel@lists.sourceforge.net (https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel)
 * deegree - deegree-devel@lists.sourceforge.net (https://lists.sourceforge.net/lists/listinfo/deegree-devel)
 * OpenLayers - dev@openlayers.org (http://openlayers.org/mailman/listinfo/dev)

= What is the main IRC channel for your organization? =

irc://irc.freenode.net/#osgeo (Web based IRC client)

Project irc channels:


 * irc://irc.freenode.net/#geoserver
 * irc://irc.freenode.net/#geotools
 * irc://irc.freenode.net/#udig
 * irc://irc.freenode.net/#mapbuilder
 * irc://irc.freenode.net/#mapguide
 * irc://irc.freenode.net/#mapserver
 * irc://irc.freenode.net/#openlayers
 * irc://irc.freenode.net/#gdal
 * irc://irc.freenode.net/#postgis
 * irc://irc.freenode.net/#grass
 * irc://irc.freenode.net/#qgis
 * irc://irc.freenode.net/#mapbender