OSGeo - User contributions [en]

User:Wolf

2013-03-31T11:30:37Z

Wiki-Wolf: /* Location */

'''Name:''' Wolf Bergenheim

'''IRC nick:''' _wolf_

I'm a OS geoinformatics enthusiast and student and GRASS developer from Finland. I can do GRASS commission work on request.

= Areas of interest =
* [http://grass.osgeo.org/ GRASS GIS]
* [[Google Summer of Code]] - GRASS Mentor 2007, OSGeo Administrator & GRASS Mentor 2008, OSGeo Administrator & GRASS Mentor 2009, OSGeo Administrator 2010
* [[OSGeo Cartographic Library]]
* Generalization
* WPS
* Label placement

= Location =
* (Europe, Finland, Helsinki)
* ''Europe, Switzerland, Zürich''

{{#umSetParam: 8.55|47.367|Zürich, Switzerland|Wolf|Wolf Bergenheim}}
{{#umUserMap: Wolf}}

User:Wolf

2013-03-31T11:25:30Z

Wiki-Wolf: /* Areas of interest */

'''Name:''' Wolf Bergenheim

'''IRC nick:''' _wolf_

I'm a OS geoinformatics enthusiast and student and GRASS developer from Finland. I can do GRASS commission work on request.

= Areas of interest =
* [http://grass.osgeo.org/ GRASS GIS]
* [[Google Summer of Code]] - GRASS Mentor 2007, OSGeo Administrator & GRASS Mentor 2008, OSGeo Administrator & GRASS Mentor 2009, OSGeo Administrator 2010
* [[OSGeo Cartographic Library]]
* Generalization
* WPS
* Label placement

= Location =
Europe, Finland, Helsinki
{{#umSetParam: 24.960|60.185|Helsinki, Finland|Wolf|Wolf Bergenheim}}
{{#umUserMap: Wolf}}

Google Summer of Code 2011 Administrative

2011-03-29T08:21:13Z

Wiki-Wolf: /* How to register as a mentor */ Fixed mentor application URL

[[Image:GSOC_2011_URL.png|250px|right]]

* Back to main OSGeo [[Google Summer of Code]] wiki page.

Central page for administering OSGeo participation in Google Summer of Code 2011.

== Background ==

* [[User:Wolf|Wolf Bergenheim]] will act as Administrative contact, with support from [[User:Aghisla|Anne Ghisla]] and [[HamishBowman|Hamish Bowman]]

* Previous years' SoC involvement: [http://code.google.com/soc/2008/osgeo/about.html 2008], [http://socghop.appspot.com/org/home/google/gsoc2009/osgeo 2009], [http://socghop.appspot.com/org/home/google/gsoc2010/osgeo 2010]

* There is a 2010 version of the [http://svn.osgeo.org/osgeo/marketing/flyer/ OSGeo SoC flyer] to look at and post in appropriate places.

* Last year(s) OSGeo GSoC wiki pages: [[Google Summer of Code 2008|2008]], [[Google Summer of Code 2009|2009]], [[Google Summer of Code 2010|2010]]

== Timeline ==

[http://www.google-melange.com/document/show/gsoc_program/google/gsoc2011/timeline The official timeline]

== Links ==

* The official [http://www.google-melange.com/ Google Summer of Code 2011 program site]
* [http://people.gnome.org/~federico/docs/summer-of-code-mentoring-howto/ Mentoring HOWTO]
* [http://code.google.com/p/google-summer-of-code/wiki/AdviceforMentors Advice for Mentors from the Google Wiki]
* [http://www.google-melange.com/document/show/gsoc_program/google/gsoc2011/faqs Google's FAQ on the program]
* There is also a [http://code.google.com/p/google-summer-of-code/wiki/WikiStart Google Wiki page about the program]
* [http://www.google-melange.com/document/show/gsoc_program/google/gsoc2011/userguide Melange User's Guide]
* [http://www.google-melange.com/document/show/gsoc_program/google/gsoc2011/userguide#depth_orgapp Melange guide for organization administrators]
* [http://code.google.com/p/soc/issues/list Melange issue tracker]

== Documents ==

* OSGeo [[Google Summer of Code Application 2011]] (see also [[Google SoC Application 2009|2009]], [[Google SoC Application 2010|2010]])

* [[SoC Application Rankings by Project]]

* The "Student Landing Page" is [[Google Summer of Code 2011 Ideas]].

* The 2011 OSGeo home at melange is (http://www.google-melange.com/gsoc/org/show/google/gsoc2011/osgeo)

== How to register as a mentor ==

Please apply to become a mentor today! Just follow these steps:

# Sign up to the [http://lists.osgeo.org/mailman/listinfo/soc OSGeo SoC mailinglist].
# Present yourself on soc@lists.osgeo.org Here are some suggested topics:
#* Project you want to/can mentor for
#* Area(s) of interest
#* Feel free to tell more about yourself
# Register yourself [http://www.google-melange.com/ at the Melange site] (if you haven't done so already).
# Fill in the [https://spreadsheets.google.com/viewform?formkey=dEpKRDUzZEU4dXRxdHd5MVhCRWlSZXc6MA Mentor form]
# [http://www.google-melange.com/gsoc/request/google/gsoc2011/osgeo Apply to become a mentor]
#* Accept the invitation that you receive, and fill in your Mentor information
# Go [http://www.google-melange.com/org/list_proposals/google/gsoc2011/osgeo read and comment on student applications] (Opens March 29th)







[[Category: Google Summer of Code]]

Google Summer of Code 2011 Ideas

2011-03-18T19:56:09Z

Wiki-Wolf: /* The ideas pages */

[[Image:GSOC_2011_URL.png|400px|center]]

see also [[Google Summer of Code 2010 Ideas]]

* Back to the main OSGeo [[Google Summer of Code 2011]] wiki page.

=OSGeo Google Summer of Code 2011=

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 [http://code.google.com/p/google-summer-of-code/wiki/GsocFlyers 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 posted to the soc@osgeo mailing list that at least answers the following questions:
# What did you get done this week?
# What do you plan on doing next week?
# Are you blocked on anything?
These questions BTW are the same as are used in real-work, when developing with the
[http://en.wikipedia.org/wiki/Scrum_(development) Scrum] [http://en.wikipedia.org/wiki/Agile_software_development development process]. ;)

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 and blogs==
In addition to weekly reports we ask you to maintain a wiki or blog 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.

Wiki and/or blog space can and will be provided by OSGeo if your project doesn't have anything already set up for this.

=Timeline=
http://www.google-melange.com/document/show/gsoc_program/google/gsoc2011/timeline

* March 18: Google announces accepted organizations. If OSGeo is accepted as an organization for Google Summer of Code, start talking to us earlier rather than later.
* April 8: Student application deadline. The earlier you start the more probable it is that you will be accepted! There is two way feedback during the application process which really helps you improve and clarify your application before this final deadline.
* April 25: Accepted student proposals are announced.
* May 23: Coding begins!
* July 11: Mid-term evaluation.
* August 22: Pencils down!

= The ideas pages =
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:

* [http://trac.osgeo.org/gdal/wiki/SummerOfCode 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.
* [http://grass.osgeo.org/wiki/GRASS_SoC_Ideas 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!
* [http://www.mapbender.org/GSoC_2010 Mapbender SoC ideas 2010]: Mapbender is a server and client side geographic data management tool, programmed in '''PHP''' and '''JavaScript''', using the '''jQuery''' library.
* [http://www.qgis.org/wiki/Google_Summer_of_Code_2010 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.
* [http://udig.refractions.net/confluence/display/HACK/Summer+of+Code uDig Summer of Code]: 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.
* [http://sourceforge.net/apps/mediawiki/jump-pilot/index.php?title=OpenJUMP_Google_Summer_Of_Code 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.
* [http://wiki.osgeo.org/wiki/OpenRouter_2010_SOC_Ideas OpenRouter 2010 SOC Ideas]: OpenRouter is a couple of projects that are building routing and driving direction libraries and applications that can be integrated with other applications.
* OSSIM [http://web.me.com/epiesasha/PlanetSasha/2010Project.html Py-OSSIM]: - ossim-swig-python to generate code to call ossim from python
* [[OSGeo_Cartographic_Engine#Ideas_for_Summer_of_Code_2010_Project | Cartographic Engine project ideas built on Mapnik]]: Refining much needed high quality hardcopy output tools that encourage collaboration. Built on Mapnik, applications like QGIS, GRASS, MapServer, etc. can output using these features. Focused initially on building specs that support Mapnik as the engine, but that could be applied generally across OSGeo projects as well.
* [http://www.spatialytics.org/google-summer-of-code-2010-ideas/ Spatialytics.org GSoC 2010 Ideas]: Spatialytics.org is the new home of the three open source Geospatial BI projects (GeoKettle, GeoMondrian and SOLAPLayers). Geospatial Business Intelligence (BI) tools, such as spatial ETL (Extract, Transform and Load), geo-analytical dashboards and Spatial On-Line Analytical Processing (SOLAP) allow decision-makers to rapidly analyze large amount of data at different levels of time, geography and detail in order to make better decisions.
* [http://www.mapwindow.org/wiki/index.php/Google_Summer_of_Code MapWindow GIS SoC Ideas]: MapWindow is a free, extensible, geographic information system (GIS) that can be used as an alternative desktop GIS, to distribute data to others, to develop and distribute custom spatial data analyses, written in .NET (C++, C#, VB.NET). If you're a talented VB.Net, C#, or C++ programmer, you could be the perfect fit to work on this project. We have a couple of ideas that could be done over the summer; feel free to suggest your own ideas or plug-ins as well.
* [[MapServer_2010_SOC_Ideas | MapServer GSoC Ideas]]: MapServer is a Web Mapping Engine; an Open Source platform for publishing spatial data and interactive mapping applications to the web.
* [[Live_GIS_Disc_GSoC_2010 | OSGeo Live]] is a stack of 35+ of the best GeoSpatial Open Source packages bundled as a LiveDVD and Virtual Machine on top an Xubuntu linux ditribution. There are opportunities to address packaging and cross project quality control through application of systematic testing processes. Through this project, developers will gain a broad understanding of the full GeoSpatial Open Source stack.
* [[gvSIG GSoC 2010 Ideas|gvSIG]] is the free GIS project developed by the Regional Department of Infrastructures and Transport of the Valencian Government (Spain). gvSIG is at this time a group of software developments for [http://www.gvsig.org/web/projects/gvsig-desktop/description2/view?set_language=en Desktop],[http://www.gvsig.org/web/projects/gvsig-mobile/description-2/view?set_language=en PDAs] and [http://gvsigmini.org mobile phones].
* [http://geoserver.org/display/GEOS/Summer+of+Code+2010 GeoServer] is an open source software server written in Java that allows users to share and edit geospatial data. Designed for interoperability, it publishes data from any major spatial data source using open standards.
* [http://opticks.org/confluence/display/opticksDev/Google+Summer+of+Code Opticks Ideas]: Opticks is an extensible [http://en.wikipedia.org/wiki/Remote_sensing remote sensing] and imagery analysis desktop application. It provides a framework to process remote sensing data such as [http://en.wikipedia.org/wiki/Hyperspectral_imaging Hyperspectral] (HSI), [http://en.wikipedia.org/wiki/Multi-spectral_image Multispectral] (MSI), and [http://en.wikipedia.org/wiki/Synthetic_aperture_radar Synthetic aperture radar] (SAR) imagery and video. The application is written in C++ and licensed under LGPL v2.1. Extensions are written using C++ or Python. You can review the [http://opticks.org/confluence/display/opticksExt/All+Opticks+Extensions available extensions] and [http://opticks.org/confluence/display/opticks/Feature+Tour+-+Your+Data feature tour] to get a better idea of what Opticks can do.

= Application Template =
Name:

Country:

School and degree:

Email:

Phone:

OSGeo project(s):

Title:
(please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS")

Describe your idea
1. Introduction
2. Background
3. The idea
4. Project plan (how do you plan to spend your summer?)
5. Future ideas / How can your idea be expanded?

Explain how your SoC task would benefit the OSGeo member project and more generally the OSGeo Foundation as a whole:

Please provide details of general computing experience:
(operating systems you use on a day-to-day basis, languages you could write a program in, hardware, networking experience, etc.)

Please provide details of previous GIS experience:

Please provide details of any previous involvement with GIS programming and other software programming:

Please tell us why you are interested in GIS and open source software:

Please tell us why you are interested in working for OSGeo and the software project you have selected:

Please tell us why you are interested in your specific coding project:

Would your application contribute to your ongoing studies/degree? If so, how?

Please explain how you intend to continue being an active member of your project and/or OSGeo AFTER the summer is over:

Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?

= 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 for project specific lists.

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

irc://irc.freenode.net/#osgeo (Web based [http://irc.telascience.org/cgi-bin/irc.cgi IRC client], [http://webchat.freenode.net alternative)

Project irc channels:

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

[[Category: Google Summer of Code]]

Google Summer of Code 2011 Ideas

2011-03-18T19:55:10Z

Wiki-Wolf: /* Application Template */

[[Image:GSOC_2011_URL.png|400px|center]]

see also [[Google Summer of Code 2010 Ideas]]

* Back to the main OSGeo [[Google Summer of Code 2011]] wiki page.

=OSGeo Google Summer of Code 2011=

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 [http://code.google.com/p/google-summer-of-code/wiki/GsocFlyers 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 posted to the soc@osgeo mailing list that at least answers the following questions:
# What did you get done this week?
# What do you plan on doing next week?
# Are you blocked on anything?
These questions BTW are the same as are used in real-work, when developing with the
[http://en.wikipedia.org/wiki/Scrum_(development) Scrum] [http://en.wikipedia.org/wiki/Agile_software_development development process]. ;)

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 and blogs==
In addition to weekly reports we ask you to maintain a wiki or blog 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.

Wiki and/or blog space can and will be provided by OSGeo if your project doesn't have anything already set up for this.

=Timeline=
http://www.google-melange.com/document/show/gsoc_program/google/gsoc2011/timeline

* March 18: Google announces accepted organizations. If OSGeo is accepted as an organization for Google Summer of Code, start talking to us earlier rather than later.
* April 8: Student application deadline. The earlier you start the more probable it is that you will be accepted! There is two way feedback during the application process which really helps you improve and clarify your application before this final deadline.
* April 25: Accepted student proposals are announced.
* May 23: Coding begins!
* July 11: Mid-term evaluation.
* August 22: Pencils down!

= The ideas pages =
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:

* [http://trac.osgeo.org/gdal/wiki/SummerOfCode 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.
* [http://grass.osgeo.org/wiki/GRASS_SoC_Ideas 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!
* [http://www.mapbender.org/GSoC_2010 Mapbender SoC ideas 2010]: Mapbender is a server and client side geographic data management tool, programmed in '''PHP''' and '''JavaScript''', using the '''jQuery''' library.
* [http://www.qgis.org/wiki/Google_Summer_of_Code_2010 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.
* [http://udig.refractions.net/confluence/display/HACK/Summer+of+Code uDig Summer of Code]: 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.
* [http://sourceforge.net/apps/mediawiki/jump-pilot/index.php?title=OpenJUMP_Google_Summer_Of_Code 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.
* [http://wiki.osgeo.org/wiki/OpenRouter_2010_SOC_Ideas OpenRouter 2010 SOC Ideas]: OpenRouter is a couple of projects that are building routing and driving direction libraries and applications that can be integrated with other applications.
* OSSIM [http://web.me.com/epiesasha/PlanetSasha/2010Project.html Py-OSSIM]: - ossim-swig-python to generate code to call ossim from python
* [[OSGeo_Cartographic_Engine#Ideas_for_Summer_of_Code_2010_Project | Cartographic Engine project ideas built on Mapnik]]: Refining much needed high quality hardcopy output tools that encourage collaboration. Built on Mapnik, applications like QGIS, GRASS, MapServer, etc. can output using these features. Focused initially on building specs that support Mapnik as the engine, but that could be applied generally across OSGeo projects as well.
* [http://www.spatialytics.org/google-summer-of-code-2010-ideas/ Spatialytics.org GSoC 2010 Ideas]: Spatialytics.org is the new home of the three open source Geospatial BI projects (GeoKettle, GeoMondrian and SOLAPLayers). Geospatial Business Intelligence (BI) tools, such as spatial ETL (Extract, Transform and Load), geo-analytical dashboards and Spatial On-Line Analytical Processing (SOLAP) allow decision-makers to rapidly analyze large amount of data at different levels of time, geography and detail in order to make better decisions.
* [http://www.mapwindow.org/wiki/index.php/Google_Summer_of_Code MapWindow GIS SoC Ideas]: MapWindow is a free, extensible, geographic information system (GIS) that can be used as an alternative desktop GIS, to distribute data to others, to develop and distribute custom spatial data analyses, written in .NET (C++, C#, VB.NET). If you're a talented VB.Net, C#, or C++ programmer, you could be the perfect fit to work on this project. We have a couple of ideas that could be done over the summer; feel free to suggest your own ideas or plug-ins as well.
* [[MapServer_2010_SOC_Ideas | MapServer GSoC Ideas]]: MapServer is a Web Mapping Engine; an Open Source platform for publishing spatial data and interactive mapping applications to the web.
* [[Live_GIS_Disc_GSoC_2010 | OSGeo Live]] is a stack of 35+ of the best GeoSpatial Open Source packages bundled as a LiveDVD and Virtual Machine on top an Xubuntu linux ditribution. There are opportunities to address packaging and cross project quality control through application of systematic testing processes. Through this project, developers will gain a broad understanding of the full GeoSpatial Open Source stack.
* [[gvSIG GSoC 2010 Ideas|gvSIG]] is the free GIS project developed by the Regional Department of Infrastructures and Transport of the Valencian Government (Spain). gvSIG is at this time a group of software developments for [http://www.gvsig.org/web/projects/gvsig-desktop/description2/view?set_language=en Desktop],[http://www.gvsig.org/web/projects/gvsig-mobile/description-2/view?set_language=en PDAs] and [http://gvsigmini.org mobile phones].
* [http://geoserver.org/display/GEOS/Summer+of+Code+2010 GeoServer] is an open source software server written in Java that allows users to share and edit geospatial data. Designed for interoperability, it publishes data from any major spatial data source using open standards.
* [http://opticks.org/confluence/display/opticksDev/Google+Summer+of+Code Opticks Ideas]: Opticks is an extensible [http://en.wikipedia.org/wiki/Remote_sensing remote sensing] and imagery analysis desktop application. It provides a framework to process remote sensing data such as [http://en.wikipedia.org/wiki/Hyperspectral_imaging Hyperspectral] (HSI), [http://en.wikipedia.org/wiki/Multi-spectral_image Multispectral] (MSI), and [http://en.wikipedia.org/wiki/Synthetic_aperture_radar Synthetic aperture radar] (SAR) imagery and video. The application is written in C++ and licensed under LGPL v2.1. Extensions are written using C++ or Python. You can review the [http://opticks.org/confluence/display/opticksExt/All+Opticks+Extensions available extensions] and [http://opticks.org/confluence/display/opticks/Feature+Tour+-+Your+Data feature tour] to get a better idea of what Opticks can do.

Name:

Country:

School and degree:

Email:

Phone:

OSGeo project(s):

Title:
(please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS")

Describe your idea
1. Introduction
2. Background
3. The idea
4. Project plan (how do you plan to spend your summer?)
5. Future ideas / How can your idea be expanded?

Explain how your SoC task would benefit the OSGeo member project and more generally the OSGeo Foundation as a whole:

Please provide details of general computing experience:
(operating systems you use on a day-to-day basis, languages you could write a program in, hardware, networking experience, etc.)

Please provide details of previous GIS experience:

Please provide details of any previous involvement with GIS programming and other software programming:

Please tell us why you are interested in GIS and open source software:

Please tell us why you are interested in working for OSGeo and the software project you have selected:

Please tell us why you are interested in your specific coding project:

Would your application contribute to your ongoing studies/degree? If so, how?

Please explain how you intend to continue being an active member of your project and/or OSGeo AFTER the summer is over:

Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?

= 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 for project specific lists.

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

irc://irc.freenode.net/#osgeo (Web based [http://irc.telascience.org/cgi-bin/irc.cgi IRC client], [http://webchat.freenode.net alternative)

Project irc channels:

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

[[Category: Google Summer of Code]]

Google Summer of Code Application 2011

2011-03-11T20:05:25Z

Wiki-Wolf: /* What is your plan for dealing with disappearing students? */

[[Image:GSOC_2011_URL.png|175px|right]]
: http://www.google-melange.com
== Application Deadline ==

Status: ''Applied, but still editable''

: http://www.google-melange.com/document/show/gsoc_program/google/gsoc2011/timeline

* '''February 28''': 19:00 UTC
: Mentoring organizations can begin submitting applications to Google.

* '''March 11''': 23:00 UTC
: Mentoring organization application deadline.

== Old ==

* Base on [[2007 Google SoC Application|2007]], [[2008 Google SoC Application|2008]], [[Google Summer of Code Application 2009|2009]] and [[Google Summer of Code Application 2010]]

== Pending ==

* Verify if the application rules have changed in any way since we last looked at them. - Done (Hamish)
* Apply

== New ==

* Anne!

=== For discussion ===
==== Possible additions to last year's ====

* Title: (''please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS"'')
** Anne: +1 for me.
** Wolf: accepted.

proposed additional question for the application:

* ''Would your application contribute to your ongoing studies/degree? If so, how?''
: (logic: If they will use the software for their degree they will care more about functional and absolutely correct outcomes. Also if they have a local univ. supervisor it's like a built-in co-mentor)

** Anne: Agreed. We can also ask if the supervisor is willing to participate more officially to the application, as co-mentor, for example discussing with the student and the official mentor about goals and timeline.
** Wolf: Accepted and +1 to Anne's comment.

* ''Please explain how you intend to continue being an active member of your project and/or OSGeo AFTER the summer is over''

==== Possible removals vs. last year's ====

* too many "why are you interested in this?" questions? combine some? (or not)
** Anne: They are OK for me. Maybe we can invert the order, starting from more general questions (generic computing > programming > GIS). I also think that these two questions are overlapping, the first can be dropped, if not at least swapped so that first we ask about interest in OSGeo, the in the OSGeo project, then in the specific proposal.
** Wolf: I agree with Anne. It doesn't hurt to have these questions.

Please tell us why you are interested in your specific coding project:
Please tell us why you are interested in working for OSGeo and the software project you have selected:

== The Application ==

=== Organization Name ===
OSGeo - Open Source Geospatial Foundation

=== Description ===

OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and 20 (to 26) code projects in particular:

Web Mapping: '''deegree''', '''geomajas''', '''GeoServer''', '''Mapbender''', '''MapBuilder''', '''MapFish''', '''MapGuide Open Source''', '''MapServer''', '''OpenLayers'''

Desktop Applications: '''GRASS GIS''', '''OSSIM''', '''Quantum GIS''', '''gvSIG'''

Geospatial Libraries: '''FDO''', '''GDAL/OGR''', '''GEOS''', '''GeoTools''', '''MetaCRS''', '''PostGIS'''
: ''The following are sub-projects of MetaCRS'':
:* '''CS-Map''', '''GeoTIFF/libgeotiff''', '''PROJ.4''', '''Proj4J''', '''Proj4js''', '''SpatialReference.org'''

Metadata Catalog: '''GeoNetwork'''

Other (non-code) Projects: '''Public Geospatial Data''', '''Education and Curriculum''', '''Live Handout DVD'''

=== Home page ===
http://www.osgeo.org

=== Main Organization License ===

Each member project uses their own, but all OSGeo projects are required to use an OSI approved license. (see http://www.osgeo.org/incubator/process/evaluation.html)

* Member projects specifically use: GPL >=2, LGPL, MIT/X, ...

GSoC program requires an OSI approved license, but the dropdown only lets you select one.
We go with GPL 2 since it seems to be the one most commonly used.

=== Why is your organization applying to participate in GSoC 2011? What do you hope to gain by participating? ===
(required)

We hope to get more students excited about open source geospatial development. This will help to grow the development community and of course tangibly advance particular projects. Additionally by way of the level of exposure that SoC provides we aim to further extend the use, development, and teaching & training of open source GIS at universities worldwide. This will help to prepare a new generation of developers for industry and government agencies capable of introducing and implementing viable open source geospatial technology, to the benefit of all.

Last but not least we hope to use this opportunity to bring more open source geospatial projects closer and to communicate more. We are encouraging students to come up with ideas that cross project boundaries, and to find new ways to connect the separate efforts in order to bring out new and perhaps improved wholes. In 2008 we also saw the birth of a new project, Spatialytics, which is a novel combination of several geospatial technologies. This is, as stated above, one of our goals, which SGoC helps us achieve in a way which cannot be matched in any other regular effort.

Additionally it has been a great opportunity to mingle code with and get to know other like-minded FOSS projects in our app domain. (such as OSM, Mapnik, Sahana, Ushahidi, ...)

=== If accepted, would this be your first year participating in GSoC? ===

* No

=== Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation. ===

OSgeo participated in 2010, and in many ways it was a tough year, but we like to think that we managed to come out victorious. It was challenging because our slot count was cut to about half of what we have had the previous year, while still having the same number, if not more projects participate under our umbrella. We also had some surprising student dropouts (one who is still MIA, as far as we know), maybe the aliens targeted OSGeo, because of our knowledge of the earth? ;) But despite these challenges we managed to put out some great projects and were in general very happy with the year.

OSGeo sent 2 delegates to the Mentor summit who participated in many geospatial sessions and also chaired one session. We made new friends among the FLOSS geo-related projects and re-connected with old friends.

OSGeo participated in GSoC in 2009. Twelve OSGeo member projects participated and were very successful. The applications were of better quality so we had fewer dropouts than the previous year. We also had further cross-project co-operation projects, which went very well indeed. OSGeo Sent two delegates to the Mentor Summit.

OSGeo participated in GSoC in 2008. Eleven OSGeo member projects participated and were in general very successful. OSGeo didn't send delegates to the Mentor Summit due to the busy schedules of the mentors.

See http://wiki.osgeo.org/wiki/SoC_Report_2008 for a full report.

OSGeo participated in GSoC in 2007. Six OSGeo projects participated and were generally very successful. OSGeo also sent one delegate to the Mentor Summit in 2007. See http://wiki.osgeo.org/wiki/SoC_Report_2007 for a full report. We also opened up a demo theatre track highlighting SoC work at our foss4g conference that year.

OSGeo was formed in early 2006 and did not participate in GSoC prior to 2007. However, Refractions Research did participate in 2006 on behalf of the GeoTools, uDig, and PostGIS projects which now participate through OSGeo. Most of the the previously participating mentors and administrators continue to be involved in this years OSGeo GSoC effort.

=== 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.''

2007: 13/19 2008: 15/19 2009: 17/20 2010: 7/10

the breakdown of the failures is interesting-
Were failures all from first-time-SOC / outside-of-osgeo projects?
* MapGuide - OSGeo - student who failed was a last minute replacement for Sergei who we gave to another SOC org during the conflict resolution swap-meet.
* MapWindow - non-member OSGeo
* GeoKettle - non-member OSGeo
*
2c thoughts: So we could do better helping our "outsider" projects in? Or perhaps projects already accepted into OSGeo have a long history and established already-integrated teams, thus correlation with success in an OSGeo-led endeavour is not entirely surprising. (aka we can twist our friends arms with greater force than we can our guests).

2009 app comment: "''As the numbers indicate each year we have received better and better applications, and thus have had a better success ratio. Also we have learned to mentor better, and to spot the good applications.''"
* Last year was special in may ways... Projects had to pick between 2 very good students, and then we were also hit by bad luck. Also we had the same number of dropouts, which gives a higher percentage, but the absolute number is still the same. ([[User:Wolf]])

=== What is the URL for your ideas page? ===

http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2011_Ideas

=== 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 2011. If your organization uses more than one list, please make sure to include a description of the list so students know which to use.''
(required)

soc@lists.osgeo.org - For questions about applying and other GSoC questions

See http://wiki.osgeo.org/wiki/Mailing_Lists for a full list and
descriptions of the OSGeo project mailing lists.

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

The primary OSGeo channel is #osgeo on the irc.freenode.net network.
member projects maintain their own IRC channels:
http://wiki.osgeo.org/wiki/IRC

=== 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 2011 site.''

Name:

Country:

School and degree:

Email:

Phone:

OSGeo project(s):

Title:
(please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS")

Describe your idea
1. Introduction
2. Background
3. The idea
4. Project plan (how do you plan to spend your summer?)
5. Future ideas / How can your idea be expanded?

Explain how your SoC task would benefit the OSGeo member project and more generally the OSGeo Foundation as a whole:

Please provide details of general computing experience:
(operating systems you use on a day-to-day basis, languages you could write a program in, hardware, networking experience, etc.)

Please provide details of previous GIS experience:

Please provide details of any previous involvement with GIS programming and other software programming:

Please tell us why you are interested in GIS and open source software:

Please tell us why you are interested in working for OSGeo and the software project you have selected:

Please tell us why you are interested in your specific coding project:

Would your application contribute to your ongoing studies/degree? If so, how?

Please explain how you intend to continue being an active member of your project and/or OSGeo AFTER the summer is over:

Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?

=== What criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible. ===
(required)

The project administrator is appointed by the OSGeo board at the beginning of the year. The project administrator asks for one or two people he trusts to be the backup administrators. Mentors are selected by project steering committees and development teams based on their reputation as skilled developers, domain experience, previously demonstrated ability to support new project developers, and stated willingness to devote time to the mentoring process. We also try very hard to match up the student working on a specific module or tool with a developer with the best expertise in the relevant area. We have in the past not voted up an otherwise good student project if there was no mentor capable of overseeing the project from a technical standpoint. Fortunately we have had a strong response from the developer pool so this has not been a major problem.

=== What is your plan for dealing with disappearing students? ===
(required)

In order to minimize the chance of disappearing students we will ensure that the OSGeo administrative contact and the mentors have full contact information (email, home phone, etc) so that we can keep in touch with them at all times. We also stress to our students that this is a Job, as opposed to a school project.

In addition, we will make our reporting requirements clear up front. Letting the students know that we will require a weekly progress report to be posted to OSGeo's SoC mailing list (cc the member project's development mailing list), participation in public IRC channels and project mailing lists will all help ensure ongoing commitment to the work. Mentors are required to make sure that happens and that the lines of communication are kept open from beginning to end.

Other possibilities include:

# Having potential students work with their potential mentor to prepare a plan for the implementation of their project.
# Setting milestones that need to be reached by the student. These milestones would be defined before the student's work begins. A student would subsequently write a brief e-mail informing the OSGeo SoC mailing list (cc project-specific mailing list) when they have reached each milestone, giving a brief description of the work completed to that date. This is in addition to the weekly progress reports which are intended to be more casual and actively soliciting feedback.
# Selecting students that have shown previous interest in the geospatial field and free software. A student who already has a (reviewable) FOSS track record has a much higher chance of success.

=== What is your plan for dealing with disappearing mentors? ===
(required)

Project steering committees will appoint replacement mentors if existing mentors become unavailable or unresponsive during the project period. We also plan to have backup mentors for all projects so the backup mentor can fill in for, or replace the primary mentor in case of changing circumstances. Our administrators take an active role communicating with students and mentors, and so will be able to help out early if there is a problem somewhere.

Among all the OSGeo mailing lists there are 14,000 subscribers, indicating a good pool of people to draw from if required. Due to relatively high member project code and personnel cross-over, in a pinch a mentor from another OSGeo project could usefully help out. Additionally this year we plan on communicating with mentors even more closely thus if something happens with the mentor it should not come as a surprise and additionally there is a backup mentor to continue the mentoring.

=== What steps will you take to encourage students to interact with your project's community before, during and after the program? ===
(required)

The steps taken depend on the individual projects. As an example, last year we required weekly reports and encouraged the students to interact with us on the project mailing lists and IRC channels. We also encourage the developers and users who are not mentors to provide additional advice and feedback to the participating student and help with testing the students contributions during and after the program. In general other developers have not been shy about sharing their opinions, guidance, and advice on the member project development lists.

Furthermore the mentors are encouraged to actively involve the students in the community by having the student interact with the mentor through the community (public) channels rather then one-on-one. This also assists with student integration into the project and alleviates the disappearing-mentor problem.

This year we are also asking the student to think about the time after the summer already in the application.

=== If you are a small or new organization applying to GSoC, please list a larger, established GSoC organization or a Googler that can vouch for you here. ===

n/a

=== If you are a large organization who is vouching for a small organization applying to GSoC for their first time this year, please list their name and why you think they'd be good candidates for GSoC here ===

As an umbrella organization we are fundamentally a conglomerate of small(er) organizations and so are well experienced in helping smaller mentoring teams. We have been happy to mentor-mentor small orgs in the past when they've approached us, each year taking in a few in-the-same-field projects who were not technically members of our Foundation but who otherwise would have missed out.

This year we are vouching for Neo4j graph database. Neo4j worked with us last year as one of the many projects under the OSGeo Umbrella. This year they have chosen to go on for them selves and we OSGeo vouch for them as an organization.

This year there is also the Opticks project, but they are participating under the OSGeo umbrella, since they have started the OSGeo incubation process.

So I guess what we're saying is that we have already been performing this role for some time.

=== Anything else you'd like to tell us? ===

GSoC is a very important project for OSGeo. We are investing more and more to it every year. This year we have a second full-time administrator in order to improve on the quality of mentoring the mentors. For OSGeo GSoC is not only a means to increase the size of the community, but also an important event to grow awareness of our project in academia, and other open source communities.

=== Backup Admin (Link ID) ===

Backup administrators:
* Anne Ghisla (melange: anne_ghisla)
* Hamish Bowman (melange: hamish)

[[Category: Google Summer of Code]]

Google Summer of Code Application 2011

2011-03-11T20:04:45Z

Wiki-Wolf: /* What criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible. */

[[Image:GSOC_2011_URL.png|175px|right]]
: http://www.google-melange.com
== Application Deadline ==

Status: ''Applied, but still editable''

: http://www.google-melange.com/document/show/gsoc_program/google/gsoc2011/timeline

* '''February 28''': 19:00 UTC
: Mentoring organizations can begin submitting applications to Google.

* '''March 11''': 23:00 UTC
: Mentoring organization application deadline.

== Old ==

* Base on [[2007 Google SoC Application|2007]], [[2008 Google SoC Application|2008]], [[Google Summer of Code Application 2009|2009]] and [[Google Summer of Code Application 2010]]

== Pending ==

* Verify if the application rules have changed in any way since we last looked at them. - Done (Hamish)
* Apply

== New ==

* Anne!

=== For discussion ===
==== Possible additions to last year's ====

* Title: (''please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS"'')
** Anne: +1 for me.
** Wolf: accepted.

proposed additional question for the application:

* ''Would your application contribute to your ongoing studies/degree? If so, how?''
: (logic: If they will use the software for their degree they will care more about functional and absolutely correct outcomes. Also if they have a local univ. supervisor it's like a built-in co-mentor)

** Anne: Agreed. We can also ask if the supervisor is willing to participate more officially to the application, as co-mentor, for example discussing with the student and the official mentor about goals and timeline.
** Wolf: Accepted and +1 to Anne's comment.

* ''Please explain how you intend to continue being an active member of your project and/or OSGeo AFTER the summer is over''

==== Possible removals vs. last year's ====

* too many "why are you interested in this?" questions? combine some? (or not)
** Anne: They are OK for me. Maybe we can invert the order, starting from more general questions (generic computing > programming > GIS). I also think that these two questions are overlapping, the first can be dropped, if not at least swapped so that first we ask about interest in OSGeo, the in the OSGeo project, then in the specific proposal.
** Wolf: I agree with Anne. It doesn't hurt to have these questions.

Please tell us why you are interested in your specific coding project:
Please tell us why you are interested in working for OSGeo and the software project you have selected:

== The Application ==

=== Organization Name ===
OSGeo - Open Source Geospatial Foundation

=== Description ===

OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and 20 (to 26) code projects in particular:

Web Mapping: '''deegree''', '''geomajas''', '''GeoServer''', '''Mapbender''', '''MapBuilder''', '''MapFish''', '''MapGuide Open Source''', '''MapServer''', '''OpenLayers'''

Desktop Applications: '''GRASS GIS''', '''OSSIM''', '''Quantum GIS''', '''gvSIG'''

Geospatial Libraries: '''FDO''', '''GDAL/OGR''', '''GEOS''', '''GeoTools''', '''MetaCRS''', '''PostGIS'''
: ''The following are sub-projects of MetaCRS'':
:* '''CS-Map''', '''GeoTIFF/libgeotiff''', '''PROJ.4''', '''Proj4J''', '''Proj4js''', '''SpatialReference.org'''

Metadata Catalog: '''GeoNetwork'''

Other (non-code) Projects: '''Public Geospatial Data''', '''Education and Curriculum''', '''Live Handout DVD'''

=== Home page ===
http://www.osgeo.org

=== Main Organization License ===

Each member project uses their own, but all OSGeo projects are required to use an OSI approved license. (see http://www.osgeo.org/incubator/process/evaluation.html)

* Member projects specifically use: GPL >=2, LGPL, MIT/X, ...

GSoC program requires an OSI approved license, but the dropdown only lets you select one.
We go with GPL 2 since it seems to be the one most commonly used.

=== Why is your organization applying to participate in GSoC 2011? What do you hope to gain by participating? ===
(required)

We hope to get more students excited about open source geospatial development. This will help to grow the development community and of course tangibly advance particular projects. Additionally by way of the level of exposure that SoC provides we aim to further extend the use, development, and teaching & training of open source GIS at universities worldwide. This will help to prepare a new generation of developers for industry and government agencies capable of introducing and implementing viable open source geospatial technology, to the benefit of all.

Last but not least we hope to use this opportunity to bring more open source geospatial projects closer and to communicate more. We are encouraging students to come up with ideas that cross project boundaries, and to find new ways to connect the separate efforts in order to bring out new and perhaps improved wholes. In 2008 we also saw the birth of a new project, Spatialytics, which is a novel combination of several geospatial technologies. This is, as stated above, one of our goals, which SGoC helps us achieve in a way which cannot be matched in any other regular effort.

Additionally it has been a great opportunity to mingle code with and get to know other like-minded FOSS projects in our app domain. (such as OSM, Mapnik, Sahana, Ushahidi, ...)

=== If accepted, would this be your first year participating in GSoC? ===

* No

=== Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation. ===

OSgeo participated in 2010, and in many ways it was a tough year, but we like to think that we managed to come out victorious. It was challenging because our slot count was cut to about half of what we have had the previous year, while still having the same number, if not more projects participate under our umbrella. We also had some surprising student dropouts (one who is still MIA, as far as we know), maybe the aliens targeted OSGeo, because of our knowledge of the earth? ;) But despite these challenges we managed to put out some great projects and were in general very happy with the year.

OSGeo sent 2 delegates to the Mentor summit who participated in many geospatial sessions and also chaired one session. We made new friends among the FLOSS geo-related projects and re-connected with old friends.

OSGeo participated in GSoC in 2009. Twelve OSGeo member projects participated and were very successful. The applications were of better quality so we had fewer dropouts than the previous year. We also had further cross-project co-operation projects, which went very well indeed. OSGeo Sent two delegates to the Mentor Summit.

OSGeo participated in GSoC in 2008. Eleven OSGeo member projects participated and were in general very successful. OSGeo didn't send delegates to the Mentor Summit due to the busy schedules of the mentors.

See http://wiki.osgeo.org/wiki/SoC_Report_2008 for a full report.

OSGeo participated in GSoC in 2007. Six OSGeo projects participated and were generally very successful. OSGeo also sent one delegate to the Mentor Summit in 2007. See http://wiki.osgeo.org/wiki/SoC_Report_2007 for a full report. We also opened up a demo theatre track highlighting SoC work at our foss4g conference that year.

OSGeo was formed in early 2006 and did not participate in GSoC prior to 2007. However, Refractions Research did participate in 2006 on behalf of the GeoTools, uDig, and PostGIS projects which now participate through OSGeo. Most of the the previously participating mentors and administrators continue to be involved in this years OSGeo GSoC effort.

=== 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.''

2007: 13/19 2008: 15/19 2009: 17/20 2010: 7/10

the breakdown of the failures is interesting-
Were failures all from first-time-SOC / outside-of-osgeo projects?
* MapGuide - OSGeo - student who failed was a last minute replacement for Sergei who we gave to another SOC org during the conflict resolution swap-meet.
* MapWindow - non-member OSGeo
* GeoKettle - non-member OSGeo
*
2c thoughts: So we could do better helping our "outsider" projects in? Or perhaps projects already accepted into OSGeo have a long history and established already-integrated teams, thus correlation with success in an OSGeo-led endeavour is not entirely surprising. (aka we can twist our friends arms with greater force than we can our guests).

2009 app comment: "''As the numbers indicate each year we have received better and better applications, and thus have had a better success ratio. Also we have learned to mentor better, and to spot the good applications.''"
* Last year was special in may ways... Projects had to pick between 2 very good students, and then we were also hit by bad luck. Also we had the same number of dropouts, which gives a higher percentage, but the absolute number is still the same. ([[User:Wolf]])

=== What is the URL for your ideas page? ===

http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2011_Ideas

=== 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 2011. If your organization uses more than one list, please make sure to include a description of the list so students know which to use.''
(required)

soc@lists.osgeo.org - For questions about applying and other GSoC questions

See http://wiki.osgeo.org/wiki/Mailing_Lists for a full list and
descriptions of the OSGeo project mailing lists.

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

The primary OSGeo channel is #osgeo on the irc.freenode.net network.
member projects maintain their own IRC channels:
http://wiki.osgeo.org/wiki/IRC

=== 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 2011 site.''

Name:

Country:

School and degree:

Email:

Phone:

OSGeo project(s):

Title:
(please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS")

Describe your idea
1. Introduction
2. Background
3. The idea
4. Project plan (how do you plan to spend your summer?)
5. Future ideas / How can your idea be expanded?

Explain how your SoC task would benefit the OSGeo member project and more generally the OSGeo Foundation as a whole:

Please provide details of general computing experience:
(operating systems you use on a day-to-day basis, languages you could write a program in, hardware, networking experience, etc.)

Please provide details of previous GIS experience:

Please provide details of any previous involvement with GIS programming and other software programming:

Please tell us why you are interested in GIS and open source software:

Please tell us why you are interested in working for OSGeo and the software project you have selected:

Please tell us why you are interested in your specific coding project:

Would your application contribute to your ongoing studies/degree? If so, how?

Please explain how you intend to continue being an active member of your project and/or OSGeo AFTER the summer is over:

Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?

=== What criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible. ===
(required)

The project administrator is appointed by the OSGeo board at the beginning of the year. The project administrator asks for one or two people he trusts to be the backup administrators. Mentors are selected by project steering committees and development teams based on their reputation as skilled developers, domain experience, previously demonstrated ability to support new project developers, and stated willingness to devote time to the mentoring process. We also try very hard to match up the student working on a specific module or tool with a developer with the best expertise in the relevant area. We have in the past not voted up an otherwise good student project if there was no mentor capable of overseeing the project from a technical standpoint. Fortunately we have had a strong response from the developer pool so this has not been a major problem.

=== What is your plan for dealing with disappearing students? ===
(required)
In order to minimize the chance of disappearing students we will ensure that the OSGeo administrative contact and the mentors have full contact information (email, home phone, etc) so that we can keep in touch with them at all times. We also stress to our students that this is a Job, as opposed to a school project.

In addition, we will make our reporting requirements clear up front. Letting the students know that we will require a weekly progress report to be posted to OSGeo's SoC mailing list (cc the member project's development mailing list), participation in public IRC channels and project mailing lists will all help ensure ongoing commitment to the work. Mentors are required to make sure that happens and that the lines of communication are kept open from beginning to end.

Other possibilities include:

# Having potential students work with their potential mentor to prepare a plan for the implementation of their project.
# Setting milestones that need to be reached by the student. These milestones would be defined before the student's work begins. A student would subsequently write a brief e-mail informing the OSGeo SoC mailing list (cc project-specific mailing list) when they have reached each milestone, giving a brief description of the work completed to that date. This is in addition to the weekly progress reports which are intended to be more casual and actively soliciting feedback.
# Selecting students that have shown previous interest in the geospatial field and free software. A student who already has a (reviewable) FOSS track record has a much higher chance of success.

=== What is your plan for dealing with disappearing mentors? ===
(required)

Project steering committees will appoint replacement mentors if existing mentors become unavailable or unresponsive during the project period. We also plan to have backup mentors for all projects so the backup mentor can fill in for, or replace the primary mentor in case of changing circumstances. Our administrators take an active role communicating with students and mentors, and so will be able to help out early if there is a problem somewhere.

Among all the OSGeo mailing lists there are 14,000 subscribers, indicating a good pool of people to draw from if required. Due to relatively high member project code and personnel cross-over, in a pinch a mentor from another OSGeo project could usefully help out. Additionally this year we plan on communicating with mentors even more closely thus if something happens with the mentor it should not come as a surprise and additionally there is a backup mentor to continue the mentoring.

=== What steps will you take to encourage students to interact with your project's community before, during and after the program? ===
(required)

The steps taken depend on the individual projects. As an example, last year we required weekly reports and encouraged the students to interact with us on the project mailing lists and IRC channels. We also encourage the developers and users who are not mentors to provide additional advice and feedback to the participating student and help with testing the students contributions during and after the program. In general other developers have not been shy about sharing their opinions, guidance, and advice on the member project development lists.

Furthermore the mentors are encouraged to actively involve the students in the community by having the student interact with the mentor through the community (public) channels rather then one-on-one. This also assists with student integration into the project and alleviates the disappearing-mentor problem.

This year we are also asking the student to think about the time after the summer already in the application.

=== If you are a small or new organization applying to GSoC, please list a larger, established GSoC organization or a Googler that can vouch for you here. ===

n/a

=== If you are a large organization who is vouching for a small organization applying to GSoC for their first time this year, please list their name and why you think they'd be good candidates for GSoC here ===

As an umbrella organization we are fundamentally a conglomerate of small(er) organizations and so are well experienced in helping smaller mentoring teams. We have been happy to mentor-mentor small orgs in the past when they've approached us, each year taking in a few in-the-same-field projects who were not technically members of our Foundation but who otherwise would have missed out.

This year we are vouching for Neo4j graph database. Neo4j worked with us last year as one of the many projects under the OSGeo Umbrella. This year they have chosen to go on for them selves and we OSGeo vouch for them as an organization.

This year there is also the Opticks project, but they are participating under the OSGeo umbrella, since they have started the OSGeo incubation process.

So I guess what we're saying is that we have already been performing this role for some time.

=== Anything else you'd like to tell us? ===

GSoC is a very important project for OSGeo. We are investing more and more to it every year. This year we have a second full-time administrator in order to improve on the quality of mentoring the mentors. For OSGeo GSoC is not only a means to increase the size of the community, but also an important event to grow awareness of our project in academia, and other open source communities.

=== Backup Admin (Link ID) ===

Backup administrators:
* Anne Ghisla (melange: anne_ghisla)
* Hamish Bowman (melange: hamish)

[[Category: Google Summer of Code]]

Google Summer of Code Application 2011

2011-03-11T19:58:18Z

Wiki-Wolf: Protected "Google Summer of Code Application 2011": Freezing page to match final submission ([edit=sysop] (indefinite))

[[Image:GSOC_2011_URL.png|175px|right]]
: http://www.google-melange.com
== Application Deadline ==

Status: ''Applied, but still editable''

: http://www.google-melange.com/document/show/gsoc_program/google/gsoc2011/timeline

* '''February 28''': 19:00 UTC
: Mentoring organizations can begin submitting applications to Google.

* '''March 11''': 23:00 UTC
: Mentoring organization application deadline.

== Old ==

* Base on [[2007 Google SoC Application|2007]], [[2008 Google SoC Application|2008]], [[Google Summer of Code Application 2009|2009]] and [[Google Summer of Code Application 2010]]

== Pending ==

* Verify if the application rules have changed in any way since we last looked at them. - Done (Hamish)
* Apply

== New ==

* Anne!

=== For discussion ===
==== Possible additions to last year's ====

* Title: (''please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS"'')
** Anne: +1 for me.
** Wolf: accepted.

proposed additional question for the application:

* ''Would your application contribute to your ongoing studies/degree? If so, how?''
: (logic: If they will use the software for their degree they will care more about functional and absolutely correct outcomes. Also if they have a local univ. supervisor it's like a built-in co-mentor)

** Anne: Agreed. We can also ask if the supervisor is willing to participate more officially to the application, as co-mentor, for example discussing with the student and the official mentor about goals and timeline.
** Wolf: Accepted and +1 to Anne's comment.

* ''Please explain how you intend to continue being an active member of your project and/or OSGeo AFTER the summer is over''

==== Possible removals vs. last year's ====

* too many "why are you interested in this?" questions? combine some? (or not)
** Anne: They are OK for me. Maybe we can invert the order, starting from more general questions (generic computing > programming > GIS). I also think that these two questions are overlapping, the first can be dropped, if not at least swapped so that first we ask about interest in OSGeo, the in the OSGeo project, then in the specific proposal.
** Wolf: I agree with Anne. It doesn't hurt to have these questions.

Please tell us why you are interested in your specific coding project:
Please tell us why you are interested in working for OSGeo and the software project you have selected:

== The Application ==

=== Organization Name ===
OSGeo - Open Source Geospatial Foundation

=== Description ===

OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and 20 (to 26) code projects in particular:

Web Mapping: '''deegree''', '''geomajas''', '''GeoServer''', '''Mapbender''', '''MapBuilder''', '''MapFish''', '''MapGuide Open Source''', '''MapServer''', '''OpenLayers'''

Desktop Applications: '''GRASS GIS''', '''OSSIM''', '''Quantum GIS''', '''gvSIG'''

Geospatial Libraries: '''FDO''', '''GDAL/OGR''', '''GEOS''', '''GeoTools''', '''MetaCRS''', '''PostGIS'''
: ''The following are sub-projects of MetaCRS'':
:* '''CS-Map''', '''GeoTIFF/libgeotiff''', '''PROJ.4''', '''Proj4J''', '''Proj4js''', '''SpatialReference.org'''

Metadata Catalog: '''GeoNetwork'''

Other (non-code) Projects: '''Public Geospatial Data''', '''Education and Curriculum''', '''Live Handout DVD'''

=== Home page ===
http://www.osgeo.org

=== Main Organization License ===

Each member project uses their own, but all OSGeo projects are required to use an OSI approved license. (see http://www.osgeo.org/incubator/process/evaluation.html)

* Member projects specifically use: GPL >=2, LGPL, MIT/X, ...

GSoC program requires an OSI approved license, but the dropdown only lets you select one.
We go with GPL 2 since it seems to be the one most commonly used.

=== Why is your organization applying to participate in GSoC 2011? What do you hope to gain by participating? ===
(required)

We hope to get more students excited about open source geospatial development. This will help to grow the development community and of course tangibly advance particular projects. Additionally by way of the level of exposure that SoC provides we aim to further extend the use, development, and teaching & training of open source GIS at universities worldwide. This will help to prepare a new generation of developers for industry and government agencies capable of introducing and implementing viable open source geospatial technology, to the benefit of all.

Last but not least we hope to use this opportunity to bring more open source geospatial projects closer and to communicate more. We are encouraging students to come up with ideas that cross project boundaries, and to find new ways to connect the separate efforts in order to bring out new and perhaps improved wholes. In 2008 we also saw the birth of a new project, Spatialytics, which is a novel combination of several geospatial technologies. This is, as stated above, one of our goals, which SGoC helps us achieve in a way which cannot be matched in any other regular effort.

Additionally it has been a great opportunity to mingle code with and get to know other like-minded FOSS projects in our app domain. (such as OSM, Mapnik, Sahana, Ushahidi, ...)

=== If accepted, would this be your first year participating in GSoC? ===

* No

=== Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation. ===

OSgeo participated in 2010, and in many ways it was a tough year, but we like to think that we managed to come out victorious. It was challenging because our slot count was cut to about half of what we have had the previous year, while still having the same number, if not more projects participate under our umbrella. We also had some surprising student dropouts (one who is still MIA, as far as we know), maybe the aliens targeted OSGeo, because of our knowledge of the earth? ;) But despite these challenges we managed to put out some great projects and were in general very happy with the year.

OSGeo sent 2 delegates to the Mentor summit who participated in many geospatial sessions and also chaired one session. We made new friends among the FLOSS geo-related projects and re-connected with old friends.

OSGeo participated in GSoC in 2009. Twelve OSGeo member projects participated and were very successful. The applications were of better quality so we had fewer dropouts than the previous year. We also had further cross-project co-operation projects, which went very well indeed. OSGeo Sent two delegates to the Mentor Summit.

OSGeo participated in GSoC in 2008. Eleven OSGeo member projects participated and were in general very successful. OSGeo didn't send delegates to the Mentor Summit due to the busy schedules of the mentors.

See http://wiki.osgeo.org/wiki/SoC_Report_2008 for a full report.

OSGeo participated in GSoC in 2007. Six OSGeo projects participated and were generally very successful. OSGeo also sent one delegate to the Mentor Summit in 2007. See http://wiki.osgeo.org/wiki/SoC_Report_2007 for a full report. We also opened up a demo theatre track highlighting SoC work at our foss4g conference that year.

OSGeo was formed in early 2006 and did not participate in GSoC prior to 2007. However, Refractions Research did participate in 2006 on behalf of the GeoTools, uDig, and PostGIS projects which now participate through OSGeo. Most of the the previously participating mentors and administrators continue to be involved in this years OSGeo GSoC effort.

=== 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.''

2007: 13/19 2008: 15/19 2009: 17/20 2010: 7/10

the breakdown of the failures is interesting-
Were failures all from first-time-SOC / outside-of-osgeo projects?
* MapGuide - OSGeo - student who failed was a last minute replacement for Sergei who we gave to another SOC org during the conflict resolution swap-meet.
* MapWindow - non-member OSGeo
* GeoKettle - non-member OSGeo
*
2c thoughts: So we could do better helping our "outsider" projects in? Or perhaps projects already accepted into OSGeo have a long history and established already-integrated teams, thus correlation with success in an OSGeo-led endeavour is not entirely surprising. (aka we can twist our friends arms with greater force than we can our guests).

2009 app comment: "''As the numbers indicate each year we have received better and better applications, and thus have had a better success ratio. Also we have learned to mentor better, and to spot the good applications.''"
* Last year was special in may ways... Projects had to pick between 2 very good students, and then we were also hit by bad luck. Also we had the same number of dropouts, which gives a higher percentage, but the absolute number is still the same. ([[User:Wolf]])

=== What is the URL for your ideas page? ===

http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2011_Ideas

=== 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 2011. If your organization uses more than one list, please make sure to include a description of the list so students know which to use.''
(required)

soc@lists.osgeo.org - For questions about applying and other GSoC questions

See http://wiki.osgeo.org/wiki/Mailing_Lists for a full list and
descriptions of the OSGeo project mailing lists.

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

The primary OSGeo channel is #osgeo on the irc.freenode.net network.
member projects maintain their own IRC channels:
http://wiki.osgeo.org/wiki/IRC

=== 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 2011 site.''

Name:

Country:

School and degree:

Email:

Phone:

OSGeo project(s):

Title:
(please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS")

Describe your idea
1. Introduction
2. Background
3. The idea
4. Project plan (how do you plan to spend your summer?)
5. Future ideas / How can your idea be expanded?

Explain how your SoC task would benefit the OSGeo member project and more generally the OSGeo Foundation as a whole:

Please provide details of general computing experience:
(operating systems you use on a day-to-day basis, languages you could write a program in, hardware, networking experience, etc.)

Please provide details of previous GIS experience:

Please provide details of any previous involvement with GIS programming and other software programming:

Please tell us why you are interested in GIS and open source software:

Please tell us why you are interested in working for OSGeo and the software project you have selected:

Please tell us why you are interested in your specific coding project:

Would your application contribute to your ongoing studies/degree? If so, how?

Please explain how you intend to continue being an active member of your project and/or OSGeo AFTER the summer is over:

Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?

=== What criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible. ===
(required)
The project administrator is appointed by the OSGeo board at the beginning of the year. The project administrator asks for one or two people he trusts to be the backup administrators. Mentors are selected by project steering committees and development teams based on their reputation as skilled developers, domain experience, previously demonstrated ability to support new project developers, and stated willingness to devote time to the mentoring process. We also try very hard to match up the student working on a specific module or tool with a developer with the best expertise in the relevant area. We have in the past not voted up an otherwise good student project if there was no mentor capable of overseeing the project from a technical standpoint. Fortunately we have had a strong response from the developer pool so this has not been a major problem.

=== What is your plan for dealing with disappearing students? ===
(required)
In order to minimize the chance of disappearing students we will ensure that the OSGeo administrative contact and the mentors have full contact information (email, home phone, etc) so that we can keep in touch with them at all times. We also stress to our students that this is a Job, as opposed to a school project.

In addition, we will make our reporting requirements clear up front. Letting the students know that we will require a weekly progress report to be posted to OSGeo's SoC mailing list (cc the member project's development mailing list), participation in public IRC channels and project mailing lists will all help ensure ongoing commitment to the work. Mentors are required to make sure that happens and that the lines of communication are kept open from beginning to end.

Other possibilities include:

# Having potential students work with their potential mentor to prepare a plan for the implementation of their project.
# Setting milestones that need to be reached by the student. These milestones would be defined before the student's work begins. A student would subsequently write a brief e-mail informing the OSGeo SoC mailing list (cc project-specific mailing list) when they have reached each milestone, giving a brief description of the work completed to that date. This is in addition to the weekly progress reports which are intended to be more casual and actively soliciting feedback.
# Selecting students that have shown previous interest in the geospatial field and free software. A student who already has a (reviewable) FOSS track record has a much higher chance of success.

=== What is your plan for dealing with disappearing mentors? ===
(required)

Project steering committees will appoint replacement mentors if existing mentors become unavailable or unresponsive during the project period. We also plan to have backup mentors for all projects so the backup mentor can fill in for, or replace the primary mentor in case of changing circumstances. Our administrators take an active role communicating with students and mentors, and so will be able to help out early if there is a problem somewhere.

Among all the OSGeo mailing lists there are 14,000 subscribers, indicating a good pool of people to draw from if required. Due to relatively high member project code and personnel cross-over, in a pinch a mentor from another OSGeo project could usefully help out. Additionally this year we plan on communicating with mentors even more closely thus if something happens with the mentor it should not come as a surprise and additionally there is a backup mentor to continue the mentoring.

=== What steps will you take to encourage students to interact with your project's community before, during and after the program? ===
(required)

The steps taken depend on the individual projects. As an example, last year we required weekly reports and encouraged the students to interact with us on the project mailing lists and IRC channels. We also encourage the developers and users who are not mentors to provide additional advice and feedback to the participating student and help with testing the students contributions during and after the program. In general other developers have not been shy about sharing their opinions, guidance, and advice on the member project development lists.

Furthermore the mentors are encouraged to actively involve the students in the community by having the student interact with the mentor through the community (public) channels rather then one-on-one. This also assists with student integration into the project and alleviates the disappearing-mentor problem.

This year we are also asking the student to think about the time after the summer already in the application.

=== If you are a small or new organization applying to GSoC, please list a larger, established GSoC organization or a Googler that can vouch for you here. ===

n/a

=== If you are a large organization who is vouching for a small organization applying to GSoC for their first time this year, please list their name and why you think they'd be good candidates for GSoC here ===

As an umbrella organization we are fundamentally a conglomerate of small(er) organizations and so are well experienced in helping smaller mentoring teams. We have been happy to mentor-mentor small orgs in the past when they've approached us, each year taking in a few in-the-same-field projects who were not technically members of our Foundation but who otherwise would have missed out.

This year we are vouching for Neo4j graph database. Neo4j worked with us last year as one of the many projects under the OSGeo Umbrella. This year they have chosen to go on for them selves and we OSGeo vouch for them as an organization.

This year there is also the Opticks project, but they are participating under the OSGeo umbrella, since they have started the OSGeo incubation process.

So I guess what we're saying is that we have already been performing this role for some time.

=== Anything else you'd like to tell us? ===

GSoC is a very important project for OSGeo. We are investing more and more to it every year. This year we have a second full-time administrator in order to improve on the quality of mentoring the mentors. For OSGeo GSoC is not only a means to increase the size of the community, but also an important event to grow awareness of our project in academia, and other open source communities.

=== Backup Admin (Link ID) ===

Backup administrators:
* Anne Ghisla (melange: anne_ghisla)
* Hamish Bowman (melange: hamish)

[[Category: Google Summer of Code]]

Google Summer of Code 2011 Administrative

2011-03-10T23:27:30Z

Wiki-Wolf:

[[Image:GSOC_2011_URL.png|250px|right]]

* Back to main OSGeo [[Google Summer of Code]] wiki page.

Central page for administering OSGeo participation in Google Summer of Code 2011.

== Background ==

* [[User:Wolf|Wolf Bergenheim]] will act as Administrative contact, with support from [[User:Aghisla|Anne Ghisla]] and [[HamishBowman|Hamish Bowman]]

* Previous years' SoC involvement: [http://code.google.com/soc/2008/osgeo/about.html 2008], [http://socghop.appspot.com/org/home/google/gsoc2009/osgeo 2009], [http://socghop.appspot.com/org/home/google/gsoc2010/osgeo 2010]

* There is a 2010 version of the [http://svn.osgeo.org/osgeo/marketing/flyer/ OSGeo SoC flyer] to look at and post in appropriate places.

* Last year(s) OSGeo GSoC wiki pages: [[Google Summer of Code 2008|2008]], [[Google Summer of Code 2009|2009]], [[Google Summer of Code 2010|2010]]

== Timeline ==

[http://www.google-melange.com/document/show/gsoc_program/google/gsoc2011/timeline The official timeline]

== Links ==

* The official [http://www.google-melange.com/ Google Summer of Code 2011 program site]
* [http://primates.ximian.com/~federico/docs/summer-of-code-mentoring-howto/index.html Mentoring HOWTO]
* [http://code.google.com/p/google-summer-of-code/wiki/AdviceforMentors Advice for Mentors from the Google Wiki]
* [http://www.google-melange.com/document/show/gsoc_program/google/gsoc2011/faqs Google's FAQ on the program]
* There is also a [http://code.google.com/p/google-summer-of-code/wiki/WikiStart Google Wiki page about the program]
* [http://www.google-melange.com/document/show/gsoc_program/google/gsoc2011/userguide Melange User's Guide]
* [http://www.google-melange.com/document/show/gsoc_program/google/gsoc2011/userguide#depth_orgapp Melange guide for organization administrators]
* [http://code.google.com/p/soc/issues/list Melange issue tracker]

== Documents ==

* OSGeo [[Google Summer of Code Application 2011]] (see also [[Google SoC Application 2009|2009]], [[Google SoC Application 2010|2010]])

* [[SoC Application Rankings by Project]]

* The "Student Landing Page" is [[Google Summer of Code 2011 Ideas]].

* The 2010 OSGeo home at melange is (http://socghop.appspot.com/org/home/google/gsoc2010/osgeo)

== How to register as a mentor ==

Please apply to become a mentor today! Just follow these steps:

# Sign up to the [http://lists.osgeo.org/mailman/listinfo/soc OSGeo SoC mailinglist].
# Present yourself on soc@lists.osgeo.org Here are some suggested topics:
#* Project you want to/can mentor for
#* Area(s) of interest
#* Feel free to tell more about yourself
# Register yourself [http://www.google-melange.com/ at the Melange site] (if you haven't done so already).
# Fill in the [https://spreadsheets.google.com/viewform?formkey=dEpKRDUzZEU4dXRxdHd5MVhCRWlSZXc6MA Mentor form]
# [http://www.google-melange.com/gsoc/mentor/request/google/gsoc2011/osgeo Apply to become a mentor]
#* Accept the invitation that you receive, and fill in your Mentor information
# Go [http://www.google-melange.com/org/list_proposals/google/gsoc2011/osgeo read and comment on student applications] (Opens March 29th)







[[Category: Google Summer of Code]]

Google Summer of Code Application 2011

2011-03-10T22:15:59Z

Wiki-Wolf: /* Application Deadline */

[[Image:GSOC_2011_URL.png|175px|right]]
: http://www.google-melange.com
== Application Deadline ==

Status: ''Applied, but still editable''

: http://www.google-melange.com/document/show/gsoc_program/google/gsoc2011/timeline

* '''February 28''': 19:00 UTC
: Mentoring organizations can begin submitting applications to Google.

* '''March 11''': 23:00 UTC
: Mentoring organization application deadline.

== Old ==

* Base on [[2007 Google SoC Application|2007]], [[2008 Google SoC Application|2008]], [[Google Summer of Code Application 2009|2009]] and [[Google Summer of Code Application 2010]]

== Pending ==

* Verify if the application rules have changed in any way since we last looked at them. - Done (Hamish)
* Apply

== New ==

* Anne!

=== For discussion ===
==== Possible additions to last year's ====

* Title: (''please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS"'')
** Anne: +1 for me.
** Wolf: accepted.

proposed additional question for the application:

* ''Would your application contribute to your ongoing studies/degree? If so, how?''
: (logic: If they will use the software for their degree they will care more about functional and absolutely correct outcomes. Also if they have a local univ. supervisor it's like a built-in co-mentor)

** Anne: Agreed. We can also ask if the supervisor is willing to participate more officially to the application, as co-mentor, for example discussing with the student and the official mentor about goals and timeline.
** Wolf: Accepted and +1 to Anne's comment.

* ''Please explain how you intend to continue being an active member of your project and/or OSGeo AFTER the summer is over''

==== Possible removals vs. last year's ====

* too many "why are you interested in this?" questions? combine some? (or not)
** Anne: They are OK for me. Maybe we can invert the order, starting from more general questions (generic computing > programming > GIS). I also think that these two questions are overlapping, the first can be dropped, if not at least swapped so that first we ask about interest in OSGeo, the in the OSGeo project, then in the specific proposal.
** Wolf: I agree with Anne. It doesn't hurt to have these questions.

Please tell us why you are interested in your specific coding project:
Please tell us why you are interested in working for OSGeo and the software project you have selected:

== The Application ==

=== Organization Name ===
OSGeo - Open Source Geospatial Foundation

=== Description ===

OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and 20 (to 26) code projects in particular:

Web Mapping: '''deegree''', '''geomajas''', '''GeoServer''', '''Mapbender''', '''MapBuilder''', '''MapFish''', '''MapGuide Open Source''', '''MapServer''', '''OpenLayers'''

Desktop Applications: '''GRASS GIS''', '''OSSIM''', '''Quantum GIS''', '''gvSIG'''

Geospatial Libraries: '''FDO''', '''GDAL/OGR''', '''GEOS''', '''GeoTools''', '''MetaCRS''', '''PostGIS'''
: ''The following are sub-projects of MetaCRS'':
:* '''CS-Map''', '''GeoTIFF/libgeotiff''', '''PROJ.4''', '''Proj4J''', '''Proj4js''', '''SpatialReference.org'''

Metadata Catalog: '''GeoNetwork'''

Other (non-code) Projects: '''Public Geospatial Data''', '''Education and Curriculum''', '''Live Handout DVD'''

=== Home page ===
http://www.osgeo.org

=== Main Organization License ===

Each member project uses their own, but all OSGeo projects are required to use an OSI approved license. (see http://www.osgeo.org/incubator/process/evaluation.html)

* Member projects specifically use: GPL >=2, LGPL, MIT/X, ...

GSoC program requires an OSI approved license, but the dropdown only lets you select one.
We go with GPL 2 since it seems to be the one most commonly used.

=== Why is your organization applying to participate in GSoC 2011? What do you hope to gain by participating? ===
(required)

We hope to get more students excited about open source geospatial development. This will help to grow the development community and of course tangibly advance particular projects. Additionally by way of the level of exposure that SoC provides we aim to further extend the use, development, and teaching & training of open source GIS at universities worldwide. This will help to prepare a new generation of developers for industry and government agencies capable of introducing and implementing viable open source geospatial technology, to the benefit of all.

Last but not least we hope to use this opportunity to bring more open source geospatial projects closer and to communicate more. We are encouraging students to come up with ideas that cross project boundaries, and to find new ways to connect the separate efforts in order to bring out new and perhaps improved wholes. In 2008 we also saw the birth of a new project, Spatialytics, which is a novel combination of several geospatial technologies. This is, as stated above, one of our goals, which SGoC helps us achieve in a way which cannot be matched in any other regular effort.

Additionally it has been a great opportunity to mingle code with and get to know other likeminded FOSS projects in our app domain. (such as OSM, Mapnik, Sahana, Ushahidi, ...)

=== If accepted, would this be your first year participating in GSoC? ===

* No

=== Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation. ===

OSgeo participated in 2010, and in many ways it was a tough year, but we like to think that we managed to come out victorious. It was challenging because our slot count was cut to about half of what we have had the previous year, while still having the same number, if not more projects participate under our umbrella. We also had some surprising student dropouts (one who is still MIA, as far as we know), maybe the aliens targeted OSGeo, because of our knowledge of the earth? ;) But despite these challenges we managed to put out some great projects and were in general very happy with the year.

OSGeo sent 2 delegates to the Mentor summit who participated in many geospatial sessions and also chaired one session. We made new friends among the FLOSS geo-related projects and re-connected with old friends.

OSGeo participated in GSoC in 2009. Twelve OSGeo member projects participated and were very successful. The applications were of better quality so we had fewer dropouts than the previous year. We also had further cross-project co-operation projects, which went very well indeed. OSGeo Sent two delegates to the Mentor Summit.

OSGeo participated in GSoC in 2008. Eleven OSGeo member projects participated and were in general very successful. OSGeo didn't send delegates to the Mentor Summit due to the busy schedules of the mentors.

See http://wiki.osgeo.org/wiki/SoC_Report_2008 for a full report.

OSGeo participated in GSoC in 2007. Six OSGeo projects participated and were generally very successful. OSGeo also sent one delegate to the Mentor Summit in 2007. See http://wiki.osgeo.org/wiki/SoC_Report_2007 for a full report. We also opened up a demo theatre track highlighting SoC work at our foss4g conference that year.

OSGeo was formed in early 2006 and did not participate in GSoC prior to 2007. However, Refractions Research did participate in 2006 on behalf of the GeoTools, uDig, and PostGIS projects which now participate through OSGeo. Most of the the previously participating mentors and administrators continue to be involved in this years OSGeo GSoC effort.

=== 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.''

2007: 13/19 2008: 15/19 2009: 17/20 2010: 7/10

the breakdown of the failures is interesting-
Were failures all from first-time-SOC / outside-of-osgeo projects?
* MapGuide - OSGeo - student who failed was a last minute replacement for Sergei who we gave to another SOC org during the conflict resolution swap-meet.
* MapWindow - non-member OSGeo
* GeoKettle - non-member OSGeo
*
2c thoughts: So we could do better helping our "outsider" projects in? Or perhaps projects already accepted into OSGeo have a long history and established already-integrated teams, thus correlation with success in an OSGeo-led endeavour is not entirely surprising. (aka we can twist our friends arms with greater force than we can our guests).

2009 app comment: "''As the numbers indicate each year we have received better and better applications, and thus have had a better success ratio. Also we have learned to mentor better, and to spot the good applications.''"
* Last year was special in may ways... Projects had to pick between 2 very good students, and then we were also hit by bad luck. Also we had the same number of dropouts, which gives a higher percentage, but the absolute number is still the same. ([[User:Wolf]])

=== What is the URL for your ideas page? ===

http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2011_Ideas

=== 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 2011. If your organization uses more than one list, please make sure to include a description of the list so students know which to use.''
(required)

soc@lists.osgeo.org - For questions about applying and other GSoC questions

See http://wiki.osgeo.org/wiki/Mailing_Lists for a full list and
descriptions of the OSGeo project mailing lists.

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

The primary OSGeo channel is #osgeo on the irc.freenode.net network.
member projects maintain their own IRC channels:
http://wiki.osgeo.org/wiki/IRC

=== 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 2011 site.''

Name:

Country:

School and degree:

Email:

Phone:

OSGeo project(s):

Title:
(please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS")

Describe your idea
1. Introduction
2. Background
3. The idea
4. Project plan (how do you plan to spend your summer?)
5. Future ideas / How can your idea be expanded?

Explain how your SoC task would benefit the OSGeo member project and more generally the OSGeo Foundation as a whole:

Please provide details of previous GIS experience:

Please provide details of any previous involvement with GIS programming and other software programming:

Please provide details of general computing experience:
(operating systems you use on a day-to-day basis, languages you could write a program in, hardware, networking experience, etc.)

Please tell us why you are interested in GIS and open source software:

Please tell us why you are interested in your specific coding project:

Please tell us why you are interested in working for OSGeo and the software project you have selected:

Would your application contribute to your ongoing studies/degree? If so, how?

Please explain how you intend to continue being an active member of your project and/or OSGeo AFTER the summer is over:

Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?

=== What criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible. ===
(required)
The project administrator is appointed by the OSGeo board at the beginning of the year. The project administrator asks for one or two people he trusts to be the backup administrators. Mentors are selected by project steering committees and development teams based on their reputation as skilled developers, domain experience, previously demonstrated ability to support new project developers, and stated willingness to devote time to the mentoring process. We also try very hard to match up the student working on a specific module or tool with a developer with the best expertise in the relevant area. We have in the past not voted up an otherwise good student project if there was no mentor capable of overseeing the project from a technical standpoint. Fortunately we have had a strong response from the developer pool so this has not been a major problem.

=== What is your plan for dealing with disappearing students? ===
(required)
In order to minimize the chance of disappearing students we will ensure that the OSGeo administrative contact and the mentors have full contact information (email, home phone, etc) so that we can keep in touch with them at all times. We also stress to our students that this is a Job, as opposed to a school project.

In addition, we will make our reporting requirements clear up front. Letting the students know that we will require a weekly progress report to be posted to OSGeo's SoC mailing list (cc the member project's development mailing list), participation in public IRC channels and project mailing lists will all help ensure ongoing commitment to the work. Mentors are required to make sure that happens and that the lines of communication are kept open from beginning to end.

Other possibilities include:

# Having potential students work with their potential mentor to prepare a plan for the implementation of their project.
# Setting milestones that need to be reached by the student. These milestones would be defined before the student's work begins. A student would subsequently write a brief e-mail informing the OSGeo SoC mailing list (cc project-specific mailing list) when they have reached each milestone, giving a brief description of the work completed to that date. This is in addition to the weekly progress reports which are intended to be more casual and actively soliciting feedback.
# Selecting students that have shown previous interest in the geospatial field and free software. A student who already has a (reviewable) FOSS track record has a much higher chance of success.

=== What is your plan for dealing with disappearing mentors? ===
(required)

Project steering committees will appoint replacement mentors if existing mentors become unavailable or unresponsive during the project period. We also plan to have backup mentors for projects so the backup mentor can fill in for, or replace the primary mentor in case of changing circumstances. Our administrators take an active role communicating with students and mentors, and so will be able to help out early if there is a problem somewhere.

Among all the OSGeo mailing lists there are 14,000 subscribers, indicating a good pool of people to draw from if required. Due to relatively high member project code and personnel cross-over, in a pinch a mentor from another OSGeo project could usefully help out. Additionally this year we plan on communicating with mentors even more closely thus if something happens with the mentor it should not come as a surprise and additionally there is a backup mentor to continue the mentoring.

=== What steps will you take to encourage students to interact with your project's community before, during and after the program? ===
(required)

The steps taken depend on the individual projects. As an example, last year we required weekly reports and encouraged the students to interact with us on the project mailing lists and IRC channels. We also encourage the developers and users who are not mentors to provide additional advice and feedback to the participating student and help with testing the students contributions during and after the program. In general other developers have not been shy about sharing their opinions, guidance, and advice on the member project development lists.

Furthermore the mentors are encouraged to actively involve the students in the community by having the student interact with the mentor through the community (public) channels rather then one-on-one. This also assists with student integration into the project and alleviates the disappearing-mentor problem.

This year we are also asking the student to think about the time after the summer already in the application.

=== If you are a small or new organization applying to GSoC, please list a larger, established GSoC organization or a Googler that can vouch for you here. ===

n/a

=== If you are a large organization who is vouching for a small organization applying to GSoC for their first time this year, please list their name and why you think they'd be good candidates for GSoC here ===

As an umbrella organization we are fundamentally a conglomerate of small(er) organizations and so are well experienced in helping smaller mentoring teams. We have been happy to mentor-mentor small orgs in the past when they've approached us, each year taking in a few in-the-same-field projects who were not technically members of our Foundation but who'd otherwise would have missed out.

This year we are vouching for Neo4j graph database. Neo4j worked with us last year as one of the many projects under the OSGeo Umbrella. This year they have chosen to go on for them selves and we OSGeo vouch for them as an organization.

This year there is also the Opticks project, but they are participating under the OSGeo umbrealla, since they have started the OSGeo incubation process.

So I guess what we're saying is that we have already been performing this role for some time.

=== Anything else you'd like to tell us? ===

GSoC is a very important project for OSGeo. We are investing more and more to it every year. This year we have a second full-time administrator in order to improve on the quality of mentoring the mentors. For OSGeo GSoC is not only a means to increase the size of the community, but also an important event to grow awareness of our project in academia, and other open source communities.

=== Backup Admin (Link ID) ===

Backup administrators:
* Anne Ghisla (melange: anne_ghisla)
* Hamish Bowman (melange: hamish)

[[Category: Google Summer of Code]]

Google Summer of Code 2011 Administrative

2011-03-10T22:07:49Z

Wiki-Wolf: /* Links */

[[Image:GSOC_2011_URL.png|250px|right]]

* Back to main OSGeo [[Google Summer of Code]] wiki page.

Central page for administering OSGeo participation in Google Summer of Code 2011.

== Background ==

* [[User:Wolf|Wolf Bergenheim]] will act as Administrative contact, with support from [[User:Aghisla|Anne Ghisla]] and [[HamishBowman|Hamish Bowman]]

* Previous years' SoC involvement: [http://code.google.com/soc/2008/osgeo/about.html 2008], [http://socghop.appspot.com/org/home/google/gsoc2009/osgeo 2009], [http://socghop.appspot.com/org/home/google/gsoc2010/osgeo 2010]

* There is a 2010 version of the [http://svn.osgeo.org/osgeo/marketing/flyer/ OSGeo SoC flyer] to look at and post in appropriate places.

* Last year(s) OSGeo GSoC wiki pages: [[Google Summer of Code 2008|2008]], [[Google Summer of Code 2009|2009]], [[Google Summer of Code 2010|2010]]

== Timeline ==

[http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2011/timeline The official timeline]

== Links ==

* The official [http://socghop.appspot.com/ Google Summer of Code 2011 program site]
* [http://primates.ximian.com/~federico/docs/summer-of-code-mentoring-howto/index.html Mentoring HOWTO]
* [http://code.google.com/p/google-summer-of-code/wiki/AdviceforMentors Advice for Mentors from the Google Wiki]
* [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2011/faqs Google's FAQ on the program]
* There is also a [http://code.google.com/p/google-summer-of-code/wiki/WikiStart Google Wiki page about the program]
* [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2011/userguide Melange User's Guide]
* [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2011/userguide#depth_orgapp Melange guide for organization administrators]
* [http://code.google.com/p/soc/issues/list Melange issue tracker]

== Documents ==

* OSGeo [[Google Summer of Code Application 2011]] (see also [[Google SoC Application 2009|2009]], [[Google SoC Application 2010|2010]])

* [[SoC Application Rankings by Project]]

* The "Student Landing Page" is [[Google Summer of Code 2011 Ideas]].

* The 2010 OSGeo home at melange is (http://socghop.appspot.com/org/home/google/gsoc2010/osgeo)

== How to register as a mentor ==

Please apply to become a mentor today! Just follow these steps:

# Sign up to the [http://lists.osgeo.org/mailman/listinfo/soc OSGeo SoC mailinglist].
# Present yourself on soc@lists.osgeo.org Here are some suggested topics:
#* Project you want to/can mentor for
#* Area(s) of interest
#* Feel free to tell more about yourself
# Register yourself [http://socghop.appspot.com/ at the Melange site] (if you haven't done so already).
# Fill in the [https://spreadsheets.google.com/viewform?formkey=dEpKRDUzZEU4dXRxdHd5MVhCRWlSZXc6MA Mentor form]
# [http://socghop.appspot.com/gsoc/mentor/request/google/gsoc2011/osgeo Apply to become a mentor]
#* Accept the invitation that you receive, and fill in your Mentor information
# Go [http://socghop.appspot.com/org/list_proposals/google/gsoc2011/osgeo read and comment on student applications] (Opens March 29th)







[[Category: Google Summer of Code]]

Google Summer of Code 2011 Administrative

2011-03-10T22:07:17Z

Wiki-Wolf:

[[Image:GSOC_2011_URL.png|250px|right]]

* Back to main OSGeo [[Google Summer of Code]] wiki page.

Central page for administering OSGeo participation in Google Summer of Code 2011.

== Background ==

* [[User:Wolf|Wolf Bergenheim]] will act as Administrative contact, with support from [[User:Aghisla|Anne Ghisla]] and [[HamishBowman|Hamish Bowman]]

* Previous years' SoC involvement: [http://code.google.com/soc/2008/osgeo/about.html 2008], [http://socghop.appspot.com/org/home/google/gsoc2009/osgeo 2009], [http://socghop.appspot.com/org/home/google/gsoc2010/osgeo 2010]

* There is a 2010 version of the [http://svn.osgeo.org/osgeo/marketing/flyer/ OSGeo SoC flyer] to look at and post in appropriate places.

* Last year(s) OSGeo GSoC wiki pages: [[Google Summer of Code 2008|2008]], [[Google Summer of Code 2009|2009]], [[Google Summer of Code 2010|2010]]

== Timeline ==

[http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2011/timeline The official timeline]

== Links ==
=== General ===
* The official [http://socghop.appspot.com/ Google Summer of Code 2011 program site]
* [http://primates.ximian.com/~federico/docs/summer-of-code-mentoring-howto/index.html Mentoring HOWTO]
* [http://code.google.com/p/google-summer-of-code/wiki/AdviceforMentors Advice for Mentors from the Google Wiki]
* [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2011/faqs Google's FAQ on the program]
* There is also a [http://code.google.com/p/google-summer-of-code/wiki/WikiStart Google Wiki page about the program]

=== Administering ===
* [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2011/userguide Melange User's Guide]
* [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2011/userguide#depth_orgapp Melange guide for organization administrators]
* [http://code.google.com/p/soc/issues/list Melange issue tracker]

== Documents ==

* OSGeo [[Google Summer of Code Application 2011]] (see also [[Google SoC Application 2009|2009]], [[Google SoC Application 2010|2010]])

* [[SoC Application Rankings by Project]]

* The "Student Landing Page" is [[Google Summer of Code 2011 Ideas]].

* The 2010 OSGeo home at melange is (http://socghop.appspot.com/org/home/google/gsoc2010/osgeo)

== How to register as a mentor ==

Please apply to become a mentor today! Just follow these steps:

# Sign up to the [http://lists.osgeo.org/mailman/listinfo/soc OSGeo SoC mailinglist].
# Present yourself on soc@lists.osgeo.org Here are some suggested topics:
#* Project you want to/can mentor for
#* Area(s) of interest
#* Feel free to tell more about yourself
# Register yourself [http://socghop.appspot.com/ at the Melange site] (if you haven't done so already).
# Fill in the [https://spreadsheets.google.com/viewform?formkey=dEpKRDUzZEU4dXRxdHd5MVhCRWlSZXc6MA Mentor form]
# [http://socghop.appspot.com/gsoc/mentor/request/google/gsoc2011/osgeo Apply to become a mentor]
#* Accept the invitation that you receive, and fill in your Mentor information
# Go [http://socghop.appspot.com/org/list_proposals/google/gsoc2011/osgeo read and comment on student applications] (Opens March 29th)







[[Category: Google Summer of Code]]

Google Summer of Code 2011 Administrative

2011-03-10T21:57:46Z

Wiki-Wolf: Added Administrative Links

[[Image:GSOC_2011_URL.png|250px|right]]

* Back to main OSGeo [[Google Summer of Code]] wiki page.

Central page for administering OSGeo participation in Google Summer of Code 2011.

== Background ==

* Wolf Bergenheim will act as Administrative contact, with support from [[User:Aghisla|Anne Ghisla]] and [[HamishBowman|Hamish Bowman]]

* [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2011/faqs Google's FAQ on the program]

* There is also a [http://code.google.com/p/google-summer-of-code/wiki/WikiStart Google Wiki page about the program]

* Previous years' SoC involvement: [http://code.google.com/soc/2008/osgeo/about.html 2008], [http://socghop.appspot.com/org/home/google/gsoc2009/osgeo 2009], [http://socghop.appspot.com/org/home/google/gsoc2010/osgeo 2010]

* Last year(s) OSGeo GSoC wiki pages: [[Google Summer of Code 2008|2008]], [[Google Summer of Code 2009|2009]], [[Google Summer of Code 2010|2010]]

* [http://primates.ximian.com/~federico/docs/summer-of-code-mentoring-howto/index.html Mentoring HOWTO]

* [http://code.google.com/p/google-summer-of-code/wiki/AdviceforMentors Advice for Mentors from the Google Wiki]

* The official [http://socghop.appspot.com/ Google Summer of Code 2011 program site]

* There is a 2010 version of the [http://svn.osgeo.org/osgeo/marketing/flyer/ OSGeo SoC flyer] to look at and post in appropriate places.

== Timeline ==

[http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2011/timeline The official timeline]

== Links ==
* [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2011/userguide Melange User's Guide]
* [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2011/userguide#depth_orgapp Melange guide for organization administrators]
* [http://code.google.com/p/soc/issues/list Melange issue tracker]

== Documents ==

* OSGeo [[Google Summer of Code Application 2011]] (see also [[Google SoC Application 2009|2009]], [[Google SoC Application 2010|2010]])

* [[SoC Application Rankings by Project]]

* The "Student Landing Page" is [[Google Summer of Code 2011 Ideas]].

* The 2010 OSGeo home at melange is (http://socghop.appspot.com/org/home/google/gsoc2010/osgeo)

== How to register as a mentor ==

Please apply to become a mentor today! Just follow these steps:

# Sign up to the [http://lists.osgeo.org/mailman/listinfo/soc OSGeo SoC mailinglist].
# Present yourself on soc@lists.osgeo.org Here are some suggested topics:
#* Project you want to/can mentor for
#* Area(s) of interest
#* Feel free to tell more about yourself
# Register yourself [http://socghop.appspot.com/ at the Melange site] (if you haven't done so already).
# Fill in the [https://spreadsheets.google.com/viewform?formkey=dEpKRDUzZEU4dXRxdHd5MVhCRWlSZXc6MA Mentor form]
# [http://socghop.appspot.com/gsoc/mentor/request/google/gsoc2011/osgeo Apply to become a mentor]
#* Accept the invitation that you receive, and fill in your Mentor information
# Go [http://socghop.appspot.com/org/list_proposals/google/gsoc2011/osgeo read and comment on student applications] (Opens March 29th)







[[Category: Google Summer of Code]]

Google Summer of Code Application 2011

2011-03-10T21:50:18Z

Wiki-Wolf: /* Anything else you'd like to tell us? */

[[Image:GSOC_2011_URL.png|175px|right]]
: http://www.google-melange.com
== Application Deadline ==

: http://www.google-melange.com/document/show/gsoc_program/google/gsoc2011/timeline

* '''February 28''': 19:00 UTC
: Mentoring organizations can begin submitting applications to Google.

* '''March 11''': 23:00 UTC
: Mentoring organization application deadline.

== Old ==

* Base on [[2007 Google SoC Application|2007]], [[2008 Google SoC Application|2008]], [[Google Summer of Code Application 2009|2009]] and [[Google Summer of Code Application 2010]]

== Pending ==

* Verify if the application rules have changed in any way since we last looked at them. - Done (Hamish)
* Apply

== New ==

* Anne!

=== For discussion ===
==== Possible additions to last year's ====

* Title: (''please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS"'')
** Anne: +1 for me.
** Wolf: accepted.

proposed additional question for the application:

* ''Would your application contribute to your ongoing studies/degree? If so, how?''
: (logic: If they will use the software for their degree they will care more about functional and absolutely correct outcomes. Also if they have a local univ. supervisor it's like a built-in co-mentor)

** Anne: Agreed. We can also ask if the supervisor is willing to participate more officially to the application, as co-mentor, for example discussing with the student and the official mentor about goals and timeline.
** Wolf: Accepted and +1 to Anne's comment.

* ''Please explain how you intend to continue being an active member of your project and/or OSGeo AFTER the summer is over''

==== Possible removals vs. last year's ====

* too many "why are you interested in this?" questions? combine some? (or not)
** Anne: They are OK for me. Maybe we can invert the order, starting from more general questions (generic computing > programming > GIS). I also think that these two questions are overlapping, the first can be dropped, if not at least swapped so that first we ask about interest in OSGeo, the in the OSGeo project, then in the specific proposal.
** Wolf: I agree with Anne. It doesn't hurt to have these questions.

Please tell us why you are interested in your specific coding project:
Please tell us why you are interested in working for OSGeo and the software project you have selected:

== The Application ==

=== Organization Name ===
OSGeo - Open Source Geospatial Foundation

=== Description ===

OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and 20 (to 26) code projects in particular:

Web Mapping: '''deegree''', '''geomajas''', '''GeoServer''', '''Mapbender''', '''MapBuilder''', '''MapFish''', '''MapGuide Open Source''', '''MapServer''', '''OpenLayers'''

Desktop Applications: '''GRASS GIS''', '''OSSIM''', '''Quantum GIS''', '''gvSIG'''

Geospatial Libraries: '''FDO''', '''GDAL/OGR''', '''GEOS''', '''GeoTools''', '''MetaCRS''', '''PostGIS'''
: ''The following are sub-projects of MetaCRS'':
:* '''CS-Map''', '''GeoTIFF/libgeotiff''', '''PROJ.4''', '''Proj4J''', '''Proj4js''', '''SpatialReference.org'''

Metadata Catalog: '''GeoNetwork'''

Other (non-code) Projects: '''Public Geospatial Data''', '''Education and Curriculum''', '''Live Handout DVD'''

=== Home page ===
http://www.osgeo.org

=== Main Organization License ===

Each member project uses their own, but all OSGeo projects are required to use an OSI approved license. (see http://www.osgeo.org/incubator/process/evaluation.html)

* Member projects specifically use: GPL >=2, LGPL, MIT/X, ...

GSoC program requires an OSI approved license, but the dropdown only lets you select one.
We go with GPL 2 since it seems to be the one most commonly used.

=== Why is your organization applying to participate in GSoC 2011? What do you hope to gain by participating? ===
(required)

We hope to get more students excited about open source geospatial development. This will help to grow the development community and of course tangibly advance particular projects. Additionally by way of the level of exposure that SoC provides we aim to further extend the use, development, and teaching & training of open source GIS at universities worldwide. This will help to prepare a new generation of developers for industry and government agencies capable of introducing and implementing viable open source geospatial technology, to the benefit of all.

Last but not least we hope to use this opportunity to bring more open source geospatial projects closer and to communicate more. We are encouraging students to come up with ideas that cross project boundaries, and to find new ways to connect the separate efforts in order to bring out new and perhaps improved wholes. In 2008 we also saw the birth of a new project, Spatialytics, which is a novel combination of several geospatial technologies. This is, as stated above, one of our goals, which SGoC helps us achieve in a way which cannot be matched in any other regular effort.

Additionally it has been a great opportunity to mingle code with and get to know other likeminded FOSS projects in our app domain. (such as OSM, Mapnik, Sahana, Ushahidi, ...)

=== If accepted, would this be your first year participating in GSoC? ===

* No

=== Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation. ===

OSgeo participated in 2010, and in many ways it was a tough year, but we like to think that we managed to come out victorious. It was challenging because our slot count was cut to about half of what we have had the previous year, while still having the same number, if not more projects participate under our umbrella. We also had some surprising student dropouts (one who is still MIA, as far as we know), maybe the aliens targeted OSGeo, because of our knowledge of the earth? ;) But despite these challenges we managed to put out some great projects and were in general very happy with the year.

OSGeo sent 2 delegates to the Mentor summit who participated in many geospatial sessions and also chaired one session. We made new friends among the FLOSS geo-related projects and re-connected with old friends.

OSGeo participated in GSoC in 2009. Twelve OSGeo member projects participated and were very successful. The applications were of better quality so we had fewer dropouts than the previous year. We also had further cross-project co-operation projects, which went very well indeed. OSGeo Sent two delegates to the Mentor Summit.

OSGeo participated in GSoC in 2008. Eleven OSGeo member projects participated and were in general very successful. OSGeo didn't send delegates to the Mentor Summit due to the busy schedules of the mentors.

See http://wiki.osgeo.org/wiki/SoC_Report_2008 for a full report.

OSGeo participated in GSoC in 2007. Six OSGeo projects participated and were generally very successful. OSGeo also sent one delegate to the Mentor Summit in 2007. See http://wiki.osgeo.org/wiki/SoC_Report_2007 for a full report. We also opened up a demo theatre track highlighting SoC work at our foss4g conference that year.

OSGeo was formed in early 2006 and did not participate in GSoC prior to 2007. However, Refractions Research did participate in 2006 on behalf of the GeoTools, uDig, and PostGIS projects which now participate through OSGeo. Most of the the previously participating mentors and administrators continue to be involved in this years OSGeo GSoC effort.

=== 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.''

2007: 13/19 2008: 15/19 2009: 17/20 2010: 7/10

the breakdown of the failures is interesting-
Were failures all from first-time-SOC / outside-of-osgeo projects?
* MapGuide - OSGeo - student who failed was a last minute replacement for Sergei who we gave to another SOC org during the conflict resolution swap-meet.
* MapWindow - non-member OSGeo
* GeoKettle - non-member OSGeo
*
2c thoughts: So we could do better helping our "outsider" projects in? Or perhaps projects already accepted into OSGeo have a long history and established already-integrated teams, thus correlation with success in an OSGeo-led endeavour is not entirely surprising. (aka we can twist our friends arms with greater force than we can our guests).

2009 app comment: "''As the numbers indicate each year we have received better and better applications, and thus have had a better success ratio. Also we have learned to mentor better, and to spot the good applications.''"
* Last year was special in may ways... Projects had to pick between 2 very good students, and then we were also hit by bad luck. Also we had the same number of dropouts, which gives a higher percentage, but the absolute number is still the same. ([[User:Wolf]])

=== What is the URL for your ideas page? ===

http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2011_Ideas

=== 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 2011. If your organization uses more than one list, please make sure to include a description of the list so students know which to use.''
(required)

soc@lists.osgeo.org - For questions about applying and other GSoC questions

See http://wiki.osgeo.org/wiki/Mailing_Lists for a full list and
descriptions of the OSGeo project mailing lists.

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

The primary OSGeo channel is #osgeo on the irc.freenode.net network.
member projects maintain their own IRC channels:
http://wiki.osgeo.org/wiki/IRC

=== 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 2011 site.''

Name:

Country:

School and degree:

Email:

Phone:

OSGeo project(s):

Title:
(please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS")

Describe your idea
1. Introduction
2. Background
3. The idea
4. Project plan (how do you plan to spend your summer?)
5. Future ideas / How can your idea be expanded?

Explain how your SoC task would benefit the OSGeo member project and more generally the OSGeo Foundation as a whole:

Please provide details of previous GIS experience:

Please provide details of any previous involvement with GIS programming and other software programming:

Please provide details of general computing experience:
(operating systems you use on a day-to-day basis, languages you could write a program in, hardware, networking experience, etc.)

Please tell us why you are interested in GIS and open source software:

Please tell us why you are interested in your specific coding project:

Please tell us why you are interested in working for OSGeo and the software project you have selected:

Would your application contribute to your ongoing studies/degree? If so, how?

Please explain how you intend to continue being an active member of your project and/or OSGeo AFTER the summer is over:

Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?

=== What criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible. ===
(required)
The project administrator is appointed by the OSGeo board at the beginning of the year. The project administrator asks for one or two people he trusts to be the backup administrators. Mentors are selected by project steering committees and development teams based on their reputation as skilled developers, domain experience, previously demonstrated ability to support new project developers, and stated willingness to devote time to the mentoring process. We also try very hard to match up the student working on a specific module or tool with a developer with the best expertise in the relevant area. We have in the past not voted up an otherwise good student project if there was no mentor capable of overseeing the project from a technical standpoint. Fortunately we have had a strong response from the developer pool so this has not been a major problem.

=== What is your plan for dealing with disappearing students? ===
(required)
In order to minimize the chance of disappearing students we will ensure that the OSGeo administrative contact and the mentors have full contact information (email, home phone, etc) so that we can keep in touch with them at all times. We also stress to our students that this is a Job, as opposed to a school project.

In addition, we will make our reporting requirements clear up front. Letting the students know that we will require a weekly progress report to be posted to OSGeo's SoC mailing list (cc the member project's development mailing list), participation in public IRC channels and project mailing lists will all help ensure ongoing commitment to the work. Mentors are required to make sure that happens and that the lines of communication are kept open from beginning to end.

Other possibilities include:

# Having potential students work with their potential mentor to prepare a plan for the implementation of their project.
# Setting milestones that need to be reached by the student. These milestones would be defined before the student's work begins. A student would subsequently write a brief e-mail informing the OSGeo SoC mailing list (cc project-specific mailing list) when they have reached each milestone, giving a brief description of the work completed to that date. This is in addition to the weekly progress reports which are intended to be more casual and actively soliciting feedback.
# Selecting students that have shown previous interest in the geospatial field and free software. A student who already has a (reviewable) FOSS track record has a much higher chance of success.

=== What is your plan for dealing with disappearing mentors? ===
(required)

Project steering committees will appoint replacement mentors if existing mentors become unavailable or unresponsive during the project period. We also plan to have backup mentors for projects so the backup mentor can fill in for, or replace the primary mentor in case of changing circumstances. Our administrators take an active role communicating with students and mentors, and so will be able to help out early if there is a problem somewhere.

Among all the OSGeo mailing lists there are 14,000 subscribers, indicating a good pool of people to draw from if required. Due to relatively high member project code and personnel cross-over, in a pinch a mentor from another OSGeo project could usefully help out. Additionally this year we plan on communicating with mentors even more closely thus if something happens with the mentor it should not come as a surprise and additionally there is a backup mentor to continue the mentoring.

=== What steps will you take to encourage students to interact with your project's community before, during and after the program? ===
(required)

The steps taken depend on the individual projects. As an example, last year we required weekly reports and encouraged the students to interact with us on the project mailing lists and IRC channels. We also encourage the developers and users who are not mentors to provide additional advice and feedback to the participating student and help with testing the students contributions during and after the program. In general other developers have not been shy about sharing their opinions, guidance, and advice on the member project development lists.

Furthermore the mentors are encouraged to actively involve the students in the community by having the student interact with the mentor through the community (public) channels rather then one-on-one. This also assists with student integration into the project and alleviates the disappearing-mentor problem.

This year we are also asking the student to think about the time after the summer already in the application.

=== If you are a small or new organization applying to GSoC, please list a larger, established GSoC organization or a Googler that can vouch for you here. ===

n/a

=== If you are a large organization who is vouching for a small organization applying to GSoC for their first time this year, please list their name and why you think they'd be good candidates for GSoC here ===

As an umbrella organization we are fundamentally a conglomerate of small(er) organizations and so are well experienced in helping smaller mentoring teams. We have been happy to mentor-mentor small orgs in the past when they've approached us, each year taking in a few in-the-same-field projects who were not technically members of our Foundation but who'd otherwise would have missed out.

This year we are vouching for Neo4j graph database. Neo4j worked with us last year as one of the many projects under the OSGeo Umbrella. This year they have chosen to go on for them selves and we OSGeo vouch for them as an organization.

This year there is also the Opticks project, but they are participating under the OSGeo umbrealla, since they have started the OSGeo incubation process.

So I guess what we're saying is that we have already been performing this role for some time.

=== Anything else you'd like to tell us? ===

GSoC is a very important project for OSGeo. We are investing more and more to it every year. This year we have a second full-time administrator in order to improve on the quality of mentoring the mentors. For OSGeo GSoC is not only a means to increase the size of the community, but also an important event to grow awareness of our project in academia, and other open source communities.

=== Backup Admin (Link ID) ===

Backup administrators:
* Anne Ghisla (melange: anne_ghisla)
* Hamish Bowman (melange: hamish)

[[Category: Google Summer of Code]]

Google Summer of Code Application 2011

2011-03-10T21:49:41Z

Wiki-Wolf: /* If you are a large organization who is vouching for a small organization applying to GSoC for their first time this year, please list their name and why you think they'd be good candidates for GSoC here */

[[Image:GSOC_2011_URL.png|175px|right]]
: http://www.google-melange.com
== Application Deadline ==

: http://www.google-melange.com/document/show/gsoc_program/google/gsoc2011/timeline

* '''February 28''': 19:00 UTC
: Mentoring organizations can begin submitting applications to Google.

* '''March 11''': 23:00 UTC
: Mentoring organization application deadline.

== Old ==

* Base on [[2007 Google SoC Application|2007]], [[2008 Google SoC Application|2008]], [[Google Summer of Code Application 2009|2009]] and [[Google Summer of Code Application 2010]]

== Pending ==

* Verify if the application rules have changed in any way since we last looked at them. - Done (Hamish)
* Apply

== New ==

* Anne!

=== For discussion ===
==== Possible additions to last year's ====

* Title: (''please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS"'')
** Anne: +1 for me.
** Wolf: accepted.

proposed additional question for the application:

* ''Would your application contribute to your ongoing studies/degree? If so, how?''
: (logic: If they will use the software for their degree they will care more about functional and absolutely correct outcomes. Also if they have a local univ. supervisor it's like a built-in co-mentor)

** Anne: Agreed. We can also ask if the supervisor is willing to participate more officially to the application, as co-mentor, for example discussing with the student and the official mentor about goals and timeline.
** Wolf: Accepted and +1 to Anne's comment.

* ''Please explain how you intend to continue being an active member of your project and/or OSGeo AFTER the summer is over''

==== Possible removals vs. last year's ====

* too many "why are you interested in this?" questions? combine some? (or not)
** Anne: They are OK for me. Maybe we can invert the order, starting from more general questions (generic computing > programming > GIS). I also think that these two questions are overlapping, the first can be dropped, if not at least swapped so that first we ask about interest in OSGeo, the in the OSGeo project, then in the specific proposal.
** Wolf: I agree with Anne. It doesn't hurt to have these questions.

Please tell us why you are interested in your specific coding project:
Please tell us why you are interested in working for OSGeo and the software project you have selected:

== The Application ==

=== Organization Name ===
OSGeo - Open Source Geospatial Foundation

=== Description ===

OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and 20 (to 26) code projects in particular:

Web Mapping: '''deegree''', '''geomajas''', '''GeoServer''', '''Mapbender''', '''MapBuilder''', '''MapFish''', '''MapGuide Open Source''', '''MapServer''', '''OpenLayers'''

Desktop Applications: '''GRASS GIS''', '''OSSIM''', '''Quantum GIS''', '''gvSIG'''

Geospatial Libraries: '''FDO''', '''GDAL/OGR''', '''GEOS''', '''GeoTools''', '''MetaCRS''', '''PostGIS'''
: ''The following are sub-projects of MetaCRS'':
:* '''CS-Map''', '''GeoTIFF/libgeotiff''', '''PROJ.4''', '''Proj4J''', '''Proj4js''', '''SpatialReference.org'''

Metadata Catalog: '''GeoNetwork'''

Other (non-code) Projects: '''Public Geospatial Data''', '''Education and Curriculum''', '''Live Handout DVD'''

=== Home page ===
http://www.osgeo.org

=== Main Organization License ===

Each member project uses their own, but all OSGeo projects are required to use an OSI approved license. (see http://www.osgeo.org/incubator/process/evaluation.html)

* Member projects specifically use: GPL >=2, LGPL, MIT/X, ...

GSoC program requires an OSI approved license, but the dropdown only lets you select one.
We go with GPL 2 since it seems to be the one most commonly used.

=== Why is your organization applying to participate in GSoC 2011? What do you hope to gain by participating? ===
(required)

We hope to get more students excited about open source geospatial development. This will help to grow the development community and of course tangibly advance particular projects. Additionally by way of the level of exposure that SoC provides we aim to further extend the use, development, and teaching & training of open source GIS at universities worldwide. This will help to prepare a new generation of developers for industry and government agencies capable of introducing and implementing viable open source geospatial technology, to the benefit of all.

Last but not least we hope to use this opportunity to bring more open source geospatial projects closer and to communicate more. We are encouraging students to come up with ideas that cross project boundaries, and to find new ways to connect the separate efforts in order to bring out new and perhaps improved wholes. In 2008 we also saw the birth of a new project, Spatialytics, which is a novel combination of several geospatial technologies. This is, as stated above, one of our goals, which SGoC helps us achieve in a way which cannot be matched in any other regular effort.

Additionally it has been a great opportunity to mingle code with and get to know other likeminded FOSS projects in our app domain. (such as OSM, Mapnik, Sahana, Ushahidi, ...)

=== If accepted, would this be your first year participating in GSoC? ===

* No

=== Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation. ===

OSgeo participated in 2010, and in many ways it was a tough year, but we like to think that we managed to come out victorious. It was challenging because our slot count was cut to about half of what we have had the previous year, while still having the same number, if not more projects participate under our umbrella. We also had some surprising student dropouts (one who is still MIA, as far as we know), maybe the aliens targeted OSGeo, because of our knowledge of the earth? ;) But despite these challenges we managed to put out some great projects and were in general very happy with the year.

OSGeo sent 2 delegates to the Mentor summit who participated in many geospatial sessions and also chaired one session. We made new friends among the FLOSS geo-related projects and re-connected with old friends.

OSGeo participated in GSoC in 2009. Twelve OSGeo member projects participated and were very successful. The applications were of better quality so we had fewer dropouts than the previous year. We also had further cross-project co-operation projects, which went very well indeed. OSGeo Sent two delegates to the Mentor Summit.

OSGeo participated in GSoC in 2008. Eleven OSGeo member projects participated and were in general very successful. OSGeo didn't send delegates to the Mentor Summit due to the busy schedules of the mentors.

See http://wiki.osgeo.org/wiki/SoC_Report_2008 for a full report.

OSGeo participated in GSoC in 2007. Six OSGeo projects participated and were generally very successful. OSGeo also sent one delegate to the Mentor Summit in 2007. See http://wiki.osgeo.org/wiki/SoC_Report_2007 for a full report. We also opened up a demo theatre track highlighting SoC work at our foss4g conference that year.

OSGeo was formed in early 2006 and did not participate in GSoC prior to 2007. However, Refractions Research did participate in 2006 on behalf of the GeoTools, uDig, and PostGIS projects which now participate through OSGeo. Most of the the previously participating mentors and administrators continue to be involved in this years OSGeo GSoC effort.

=== 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.''

2007: 13/19 2008: 15/19 2009: 17/20 2010: 7/10

the breakdown of the failures is interesting-
Were failures all from first-time-SOC / outside-of-osgeo projects?
* MapGuide - OSGeo - student who failed was a last minute replacement for Sergei who we gave to another SOC org during the conflict resolution swap-meet.
* MapWindow - non-member OSGeo
* GeoKettle - non-member OSGeo
*
2c thoughts: So we could do better helping our "outsider" projects in? Or perhaps projects already accepted into OSGeo have a long history and established already-integrated teams, thus correlation with success in an OSGeo-led endeavour is not entirely surprising. (aka we can twist our friends arms with greater force than we can our guests).

2009 app comment: "''As the numbers indicate each year we have received better and better applications, and thus have had a better success ratio. Also we have learned to mentor better, and to spot the good applications.''"
* Last year was special in may ways... Projects had to pick between 2 very good students, and then we were also hit by bad luck. Also we had the same number of dropouts, which gives a higher percentage, but the absolute number is still the same. ([[User:Wolf]])

=== What is the URL for your ideas page? ===

http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2011_Ideas

=== 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 2011. If your organization uses more than one list, please make sure to include a description of the list so students know which to use.''
(required)

soc@lists.osgeo.org - For questions about applying and other GSoC questions

See http://wiki.osgeo.org/wiki/Mailing_Lists for a full list and
descriptions of the OSGeo project mailing lists.

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

The primary OSGeo channel is #osgeo on the irc.freenode.net network.
member projects maintain their own IRC channels:
http://wiki.osgeo.org/wiki/IRC

=== 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 2011 site.''

Name:

Country:

School and degree:

Email:

Phone:

OSGeo project(s):

Title:
(please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS")

Describe your idea
1. Introduction
2. Background
3. The idea
4. Project plan (how do you plan to spend your summer?)
5. Future ideas / How can your idea be expanded?

Explain how your SoC task would benefit the OSGeo member project and more generally the OSGeo Foundation as a whole:

Please provide details of previous GIS experience:

Please provide details of any previous involvement with GIS programming and other software programming:

Please provide details of general computing experience:
(operating systems you use on a day-to-day basis, languages you could write a program in, hardware, networking experience, etc.)

Please tell us why you are interested in GIS and open source software:

Please tell us why you are interested in your specific coding project:

Please tell us why you are interested in working for OSGeo and the software project you have selected:

Would your application contribute to your ongoing studies/degree? If so, how?

Please explain how you intend to continue being an active member of your project and/or OSGeo AFTER the summer is over:

Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?

=== What criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible. ===
(required)
The project administrator is appointed by the OSGeo board at the beginning of the year. The project administrator asks for one or two people he trusts to be the backup administrators. Mentors are selected by project steering committees and development teams based on their reputation as skilled developers, domain experience, previously demonstrated ability to support new project developers, and stated willingness to devote time to the mentoring process. We also try very hard to match up the student working on a specific module or tool with a developer with the best expertise in the relevant area. We have in the past not voted up an otherwise good student project if there was no mentor capable of overseeing the project from a technical standpoint. Fortunately we have had a strong response from the developer pool so this has not been a major problem.

=== What is your plan for dealing with disappearing students? ===
(required)
In order to minimize the chance of disappearing students we will ensure that the OSGeo administrative contact and the mentors have full contact information (email, home phone, etc) so that we can keep in touch with them at all times. We also stress to our students that this is a Job, as opposed to a school project.

In addition, we will make our reporting requirements clear up front. Letting the students know that we will require a weekly progress report to be posted to OSGeo's SoC mailing list (cc the member project's development mailing list), participation in public IRC channels and project mailing lists will all help ensure ongoing commitment to the work. Mentors are required to make sure that happens and that the lines of communication are kept open from beginning to end.

Other possibilities include:

# Having potential students work with their potential mentor to prepare a plan for the implementation of their project.
# Setting milestones that need to be reached by the student. These milestones would be defined before the student's work begins. A student would subsequently write a brief e-mail informing the OSGeo SoC mailing list (cc project-specific mailing list) when they have reached each milestone, giving a brief description of the work completed to that date. This is in addition to the weekly progress reports which are intended to be more casual and actively soliciting feedback.
# Selecting students that have shown previous interest in the geospatial field and free software. A student who already has a (reviewable) FOSS track record has a much higher chance of success.

=== What is your plan for dealing with disappearing mentors? ===
(required)

Project steering committees will appoint replacement mentors if existing mentors become unavailable or unresponsive during the project period. We also plan to have backup mentors for projects so the backup mentor can fill in for, or replace the primary mentor in case of changing circumstances. Our administrators take an active role communicating with students and mentors, and so will be able to help out early if there is a problem somewhere.

Among all the OSGeo mailing lists there are 14,000 subscribers, indicating a good pool of people to draw from if required. Due to relatively high member project code and personnel cross-over, in a pinch a mentor from another OSGeo project could usefully help out. Additionally this year we plan on communicating with mentors even more closely thus if something happens with the mentor it should not come as a surprise and additionally there is a backup mentor to continue the mentoring.

=== What steps will you take to encourage students to interact with your project's community before, during and after the program? ===
(required)

The steps taken depend on the individual projects. As an example, last year we required weekly reports and encouraged the students to interact with us on the project mailing lists and IRC channels. We also encourage the developers and users who are not mentors to provide additional advice and feedback to the participating student and help with testing the students contributions during and after the program. In general other developers have not been shy about sharing their opinions, guidance, and advice on the member project development lists.

Furthermore the mentors are encouraged to actively involve the students in the community by having the student interact with the mentor through the community (public) channels rather then one-on-one. This also assists with student integration into the project and alleviates the disappearing-mentor problem.

This year we are also asking the student to think about the time after the summer already in the application.

=== If you are a small or new organization applying to GSoC, please list a larger, established GSoC organization or a Googler that can vouch for you here. ===

n/a

=== If you are a large organization who is vouching for a small organization applying to GSoC for their first time this year, please list their name and why you think they'd be good candidates for GSoC here ===

As an umbrella organization we are fundamentally a conglomerate of small(er) organizations and so are well experienced in helping smaller mentoring teams. We have been happy to mentor-mentor small orgs in the past when they've approached us, each year taking in a few in-the-same-field projects who were not technically members of our Foundation but who'd otherwise would have missed out.

This year we are vouching for Neo4j graph database. Neo4j worked with us last year as one of the many projects under the OSGeo Umbrella. This year they have chosen to go on for them selves and we OSGeo vouch for them as an organization.

This year there is also the Opticks project, but they are participating under the OSGeo umbrealla, since they have started the OSGeo incubation process.

So I guess what we're saying is that we have already been performing this role for some time.

=== Anything else you'd like to tell us? ===

GSoC is a very important project for OSGeo. We are investing more and more to it
every year. This year we have a second full-time administrator in order to improve
on the quality of mentoring the mentors. For OSGeo GSoC is not only a means to
increase the size of the community, but also an important event to grow awareness
of our project in academia, and other open source communities.

=== Backup Admin (Link ID) ===

Backup administrators:
* Anne Ghisla (melange: anne_ghisla)
* Hamish Bowman (melange: hamish)

[[Category: Google Summer of Code]]

Google Summer of Code Application 2011

2011-03-10T21:46:40Z

Wiki-Wolf: /* What steps will you take to encourage students to interact with your project's community before, during and after the program? */

[[Image:GSOC_2011_URL.png|175px|right]]
: http://www.google-melange.com
== Application Deadline ==

: http://www.google-melange.com/document/show/gsoc_program/google/gsoc2011/timeline

* '''February 28''': 19:00 UTC
: Mentoring organizations can begin submitting applications to Google.

* '''March 11''': 23:00 UTC
: Mentoring organization application deadline.

== Old ==

* Base on [[2007 Google SoC Application|2007]], [[2008 Google SoC Application|2008]], [[Google Summer of Code Application 2009|2009]] and [[Google Summer of Code Application 2010]]

== Pending ==

* Verify if the application rules have changed in any way since we last looked at them. - Done (Hamish)
* Apply

== New ==

* Anne!

=== For discussion ===
==== Possible additions to last year's ====

* Title: (''please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS"'')
** Anne: +1 for me.
** Wolf: accepted.

proposed additional question for the application:

* ''Would your application contribute to your ongoing studies/degree? If so, how?''
: (logic: If they will use the software for their degree they will care more about functional and absolutely correct outcomes. Also if they have a local univ. supervisor it's like a built-in co-mentor)

** Anne: Agreed. We can also ask if the supervisor is willing to participate more officially to the application, as co-mentor, for example discussing with the student and the official mentor about goals and timeline.
** Wolf: Accepted and +1 to Anne's comment.

* ''Please explain how you intend to continue being an active member of your project and/or OSGeo AFTER the summer is over''

==== Possible removals vs. last year's ====

* too many "why are you interested in this?" questions? combine some? (or not)
** Anne: They are OK for me. Maybe we can invert the order, starting from more general questions (generic computing > programming > GIS). I also think that these two questions are overlapping, the first can be dropped, if not at least swapped so that first we ask about interest in OSGeo, the in the OSGeo project, then in the specific proposal.
** Wolf: I agree with Anne. It doesn't hurt to have these questions.

Please tell us why you are interested in your specific coding project:
Please tell us why you are interested in working for OSGeo and the software project you have selected:

== The Application ==

=== Organization Name ===
OSGeo - Open Source Geospatial Foundation

=== Description ===

OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and 20 (to 26) code projects in particular:

Web Mapping: '''deegree''', '''geomajas''', '''GeoServer''', '''Mapbender''', '''MapBuilder''', '''MapFish''', '''MapGuide Open Source''', '''MapServer''', '''OpenLayers'''

Desktop Applications: '''GRASS GIS''', '''OSSIM''', '''Quantum GIS''', '''gvSIG'''

Geospatial Libraries: '''FDO''', '''GDAL/OGR''', '''GEOS''', '''GeoTools''', '''MetaCRS''', '''PostGIS'''
: ''The following are sub-projects of MetaCRS'':
:* '''CS-Map''', '''GeoTIFF/libgeotiff''', '''PROJ.4''', '''Proj4J''', '''Proj4js''', '''SpatialReference.org'''

Metadata Catalog: '''GeoNetwork'''

Other (non-code) Projects: '''Public Geospatial Data''', '''Education and Curriculum''', '''Live Handout DVD'''

=== Home page ===
http://www.osgeo.org

=== Main Organization License ===

Each member project uses their own, but all OSGeo projects are required to use an OSI approved license. (see http://www.osgeo.org/incubator/process/evaluation.html)

* Member projects specifically use: GPL >=2, LGPL, MIT/X, ...

GSoC program requires an OSI approved license, but the dropdown only lets you select one.
We go with GPL 2 since it seems to be the one most commonly used.

=== Why is your organization applying to participate in GSoC 2011? What do you hope to gain by participating? ===
(required)

We hope to get more students excited about open source geospatial development. This will help to grow the development community and of course tangibly advance particular projects. Additionally by way of the level of exposure that SoC provides we aim to further extend the use, development, and teaching & training of open source GIS at universities worldwide. This will help to prepare a new generation of developers for industry and government agencies capable of introducing and implementing viable open source geospatial technology, to the benefit of all.

Last but not least we hope to use this opportunity to bring more open source geospatial projects closer and to communicate more. We are encouraging students to come up with ideas that cross project boundaries, and to find new ways to connect the separate efforts in order to bring out new and perhaps improved wholes. In 2008 we also saw the birth of a new project, Spatialytics, which is a novel combination of several geospatial technologies. This is, as stated above, one of our goals, which SGoC helps us achieve in a way which cannot be matched in any other regular effort.

Additionally it has been a great opportunity to mingle code with and get to know other likeminded FOSS projects in our app domain. (such as OSM, Mapnik, Sahana, Ushahidi, ...)

=== If accepted, would this be your first year participating in GSoC? ===

* No

=== Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation. ===

OSgeo participated in 2010, and in many ways it was a tough year, but we like to think that we managed to come out victorious. It was challenging because our slot count was cut to about half of what we have had the previous year, while still having the same number, if not more projects participate under our umbrella. We also had some surprising student dropouts (one who is still MIA, as far as we know), maybe the aliens targeted OSGeo, because of our knowledge of the earth? ;) But despite these challenges we managed to put out some great projects and were in general very happy with the year.

OSGeo sent 2 delegates to the Mentor summit who participated in many geospatial sessions and also chaired one session. We made new friends among the FLOSS geo-related projects and re-connected with old friends.

OSGeo participated in GSoC in 2009. Twelve OSGeo member projects participated and were very successful. The applications were of better quality so we had fewer dropouts than the previous year. We also had further cross-project co-operation projects, which went very well indeed. OSGeo Sent two delegates to the Mentor Summit.

OSGeo participated in GSoC in 2008. Eleven OSGeo member projects participated and were in general very successful. OSGeo didn't send delegates to the Mentor Summit due to the busy schedules of the mentors.

See http://wiki.osgeo.org/wiki/SoC_Report_2008 for a full report.

OSGeo participated in GSoC in 2007. Six OSGeo projects participated and were generally very successful. OSGeo also sent one delegate to the Mentor Summit in 2007. See http://wiki.osgeo.org/wiki/SoC_Report_2007 for a full report. We also opened up a demo theatre track highlighting SoC work at our foss4g conference that year.

OSGeo was formed in early 2006 and did not participate in GSoC prior to 2007. However, Refractions Research did participate in 2006 on behalf of the GeoTools, uDig, and PostGIS projects which now participate through OSGeo. Most of the the previously participating mentors and administrators continue to be involved in this years OSGeo GSoC effort.

=== 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.''

2007: 13/19 2008: 15/19 2009: 17/20 2010: 7/10

the breakdown of the failures is interesting-
Were failures all from first-time-SOC / outside-of-osgeo projects?
* MapGuide - OSGeo - student who failed was a last minute replacement for Sergei who we gave to another SOC org during the conflict resolution swap-meet.
* MapWindow - non-member OSGeo
* GeoKettle - non-member OSGeo
*
2c thoughts: So we could do better helping our "outsider" projects in? Or perhaps projects already accepted into OSGeo have a long history and established already-integrated teams, thus correlation with success in an OSGeo-led endeavour is not entirely surprising. (aka we can twist our friends arms with greater force than we can our guests).

2009 app comment: "''As the numbers indicate each year we have received better and better applications, and thus have had a better success ratio. Also we have learned to mentor better, and to spot the good applications.''"
* Last year was special in may ways... Projects had to pick between 2 very good students, and then we were also hit by bad luck. Also we had the same number of dropouts, which gives a higher percentage, but the absolute number is still the same. ([[User:Wolf]])

=== What is the URL for your ideas page? ===

http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2011_Ideas

=== 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 2011. If your organization uses more than one list, please make sure to include a description of the list so students know which to use.''
(required)

soc@lists.osgeo.org - For questions about applying and other GSoC questions

See http://wiki.osgeo.org/wiki/Mailing_Lists for a full list and
descriptions of the OSGeo project mailing lists.

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

The primary OSGeo channel is #osgeo on the irc.freenode.net network.
member projects maintain their own IRC channels:
http://wiki.osgeo.org/wiki/IRC

=== 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 2011 site.''

Name:

Country:

School and degree:

Email:

Phone:

OSGeo project(s):

Title:
(please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS")

Describe your idea
1. Introduction
2. Background
3. The idea
4. Project plan (how do you plan to spend your summer?)
5. Future ideas / How can your idea be expanded?

Explain how your SoC task would benefit the OSGeo member project and more generally the OSGeo Foundation as a whole:

Please provide details of previous GIS experience:

Please provide details of any previous involvement with GIS programming and other software programming:

Please provide details of general computing experience:
(operating systems you use on a day-to-day basis, languages you could write a program in, hardware, networking experience, etc.)

Please tell us why you are interested in GIS and open source software:

Please tell us why you are interested in your specific coding project:

Please tell us why you are interested in working for OSGeo and the software project you have selected:

Would your application contribute to your ongoing studies/degree? If so, how?

Please explain how you intend to continue being an active member of your project and/or OSGeo AFTER the summer is over:

Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?

=== What criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible. ===
(required)
The project administrator is appointed by the OSGeo board at the beginning of the year. The project administrator asks for one or two people he trusts to be the backup administrators. Mentors are selected by project steering committees and development teams based on their reputation as skilled developers, domain experience, previously demonstrated ability to support new project developers, and stated willingness to devote time to the mentoring process. We also try very hard to match up the student working on a specific module or tool with a developer with the best expertise in the relevant area. We have in the past not voted up an otherwise good student project if there was no mentor capable of overseeing the project from a technical standpoint. Fortunately we have had a strong response from the developer pool so this has not been a major problem.

=== What is your plan for dealing with disappearing students? ===
(required)
In order to minimize the chance of disappearing students we will ensure that the OSGeo administrative contact and the mentors have full contact information (email, home phone, etc) so that we can keep in touch with them at all times. We also stress to our students that this is a Job, as opposed to a school project.

In addition, we will make our reporting requirements clear up front. Letting the students know that we will require a weekly progress report to be posted to OSGeo's SoC mailing list (cc the member project's development mailing list), participation in public IRC channels and project mailing lists will all help ensure ongoing commitment to the work. Mentors are required to make sure that happens and that the lines of communication are kept open from beginning to end.

Other possibilities include:

# Having potential students work with their potential mentor to prepare a plan for the implementation of their project.
# Setting milestones that need to be reached by the student. These milestones would be defined before the student's work begins. A student would subsequently write a brief e-mail informing the OSGeo SoC mailing list (cc project-specific mailing list) when they have reached each milestone, giving a brief description of the work completed to that date. This is in addition to the weekly progress reports which are intended to be more casual and actively soliciting feedback.
# Selecting students that have shown previous interest in the geospatial field and free software. A student who already has a (reviewable) FOSS track record has a much higher chance of success.

=== What is your plan for dealing with disappearing mentors? ===
(required)

Project steering committees will appoint replacement mentors if existing mentors become unavailable or unresponsive during the project period. We also plan to have backup mentors for projects so the backup mentor can fill in for, or replace the primary mentor in case of changing circumstances. Our administrators take an active role communicating with students and mentors, and so will be able to help out early if there is a problem somewhere.

Among all the OSGeo mailing lists there are 14,000 subscribers, indicating a good pool of people to draw from if required. Due to relatively high member project code and personnel cross-over, in a pinch a mentor from another OSGeo project could usefully help out. Additionally this year we plan on communicating with mentors even more closely thus if something happens with the mentor it should not come as a surprise and additionally there is a backup mentor to continue the mentoring.

=== What steps will you take to encourage students to interact with your project's community before, during and after the program? ===
(required)

The steps taken depend on the individual projects. As an example, last year we required weekly reports and encouraged the students to interact with us on the project mailing lists and IRC channels. We also encourage the developers and users who are not mentors to provide additional advice and feedback to the participating student and help with testing the students contributions during and after the program. In general other developers have not been shy about sharing their opinions, guidance, and advice on the member project development lists.

Furthermore the mentors are encouraged to actively involve the students in the community by having the student interact with the mentor through the community (public) channels rather then one-on-one. This also assists with student integration into the project and alleviates the disappearing-mentor problem.

This year we are also asking the student to think about the time after the summer already in the application.

=== If you are a small or new organization applying to GSoC, please list a larger, established GSoC organization or a Googler that can vouch for you here. ===

n/a

=== If you are a large organization who is vouching for a small organization applying to GSoC for their first time this year, please list their name and why you think they'd be good candidates for GSoC here ===

As an umbrella organization we are fundamentally a conglomerate of small(er)
organizations and so are well experienced in helping smaller mentoring teams.
We have been happy to mentor-mentor small orgs in the past when they've
approached us, each year taking in a few in-the-same-field projects who were
not technically members of our Foundation but who'd otherwise would have missed
out.

This year we are vouching for Neo4j graph database. Neo4j worked with us last
year as one of the many projects under the OSGeo Umbrella. This year they have
chosen to go on for them selves and we OSGeo vouch for them as an organization.

This year there is also the Opticks project, but they are participating under the
OSGeo umbrealla, since they have started the OSGeo incubation process.

So I guess what we're saying is that we are already performing this role.

=== Anything else you'd like to tell us? ===

GSoC is a very important project for OSGeo. We are investing more and more to it
every year. This year we have a second full-time administrator in order to improve
on the quality of mentoring the mentors. For OSGeo GSoC is not only a means to
increase the size of the community, but also an important event to grow awareness
of our project in academia, and other open source communities.

=== Backup Admin (Link ID) ===

Backup administrators:
* Anne Ghisla (melange: anne_ghisla)
* Hamish Bowman (melange: hamish)

[[Category: Google Summer of Code]]

Google Summer of Code Application 2011

2011-03-10T21:45:09Z

Wiki-Wolf: /* What is your plan for dealing with disappearing mentors? */

[[Image:GSOC_2011_URL.png|175px|right]]
: http://www.google-melange.com
== Application Deadline ==

: http://www.google-melange.com/document/show/gsoc_program/google/gsoc2011/timeline

* '''February 28''': 19:00 UTC
: Mentoring organizations can begin submitting applications to Google.

* '''March 11''': 23:00 UTC
: Mentoring organization application deadline.

== Old ==

* Base on [[2007 Google SoC Application|2007]], [[2008 Google SoC Application|2008]], [[Google Summer of Code Application 2009|2009]] and [[Google Summer of Code Application 2010]]

== Pending ==

* Verify if the application rules have changed in any way since we last looked at them. - Done (Hamish)
* Apply

== New ==

* Anne!

=== For discussion ===
==== Possible additions to last year's ====

* Title: (''please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS"'')
** Anne: +1 for me.
** Wolf: accepted.

proposed additional question for the application:

* ''Would your application contribute to your ongoing studies/degree? If so, how?''
: (logic: If they will use the software for their degree they will care more about functional and absolutely correct outcomes. Also if they have a local univ. supervisor it's like a built-in co-mentor)

** Anne: Agreed. We can also ask if the supervisor is willing to participate more officially to the application, as co-mentor, for example discussing with the student and the official mentor about goals and timeline.
** Wolf: Accepted and +1 to Anne's comment.

* ''Please explain how you intend to continue being an active member of your project and/or OSGeo AFTER the summer is over''

==== Possible removals vs. last year's ====

* too many "why are you interested in this?" questions? combine some? (or not)
** Anne: They are OK for me. Maybe we can invert the order, starting from more general questions (generic computing > programming > GIS). I also think that these two questions are overlapping, the first can be dropped, if not at least swapped so that first we ask about interest in OSGeo, the in the OSGeo project, then in the specific proposal.
** Wolf: I agree with Anne. It doesn't hurt to have these questions.

Please tell us why you are interested in your specific coding project:
Please tell us why you are interested in working for OSGeo and the software project you have selected:

== The Application ==

=== Organization Name ===
OSGeo - Open Source Geospatial Foundation

=== Description ===

OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and 20 (to 26) code projects in particular:

Web Mapping: '''deegree''', '''geomajas''', '''GeoServer''', '''Mapbender''', '''MapBuilder''', '''MapFish''', '''MapGuide Open Source''', '''MapServer''', '''OpenLayers'''

Desktop Applications: '''GRASS GIS''', '''OSSIM''', '''Quantum GIS''', '''gvSIG'''

Geospatial Libraries: '''FDO''', '''GDAL/OGR''', '''GEOS''', '''GeoTools''', '''MetaCRS''', '''PostGIS'''
: ''The following are sub-projects of MetaCRS'':
:* '''CS-Map''', '''GeoTIFF/libgeotiff''', '''PROJ.4''', '''Proj4J''', '''Proj4js''', '''SpatialReference.org'''

Metadata Catalog: '''GeoNetwork'''

Other (non-code) Projects: '''Public Geospatial Data''', '''Education and Curriculum''', '''Live Handout DVD'''

=== Home page ===
http://www.osgeo.org

=== Main Organization License ===

Each member project uses their own, but all OSGeo projects are required to use an OSI approved license. (see http://www.osgeo.org/incubator/process/evaluation.html)

* Member projects specifically use: GPL >=2, LGPL, MIT/X, ...

GSoC program requires an OSI approved license, but the dropdown only lets you select one.
We go with GPL 2 since it seems to be the one most commonly used.

=== Why is your organization applying to participate in GSoC 2011? What do you hope to gain by participating? ===
(required)

We hope to get more students excited about open source geospatial development. This will help to grow the development community and of course tangibly advance particular projects. Additionally by way of the level of exposure that SoC provides we aim to further extend the use, development, and teaching & training of open source GIS at universities worldwide. This will help to prepare a new generation of developers for industry and government agencies capable of introducing and implementing viable open source geospatial technology, to the benefit of all.

Last but not least we hope to use this opportunity to bring more open source geospatial projects closer and to communicate more. We are encouraging students to come up with ideas that cross project boundaries, and to find new ways to connect the separate efforts in order to bring out new and perhaps improved wholes. In 2008 we also saw the birth of a new project, Spatialytics, which is a novel combination of several geospatial technologies. This is, as stated above, one of our goals, which SGoC helps us achieve in a way which cannot be matched in any other regular effort.

Additionally it has been a great opportunity to mingle code with and get to know other likeminded FOSS projects in our app domain. (such as OSM, Mapnik, Sahana, Ushahidi, ...)

=== If accepted, would this be your first year participating in GSoC? ===

* No

=== Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation. ===

OSgeo participated in 2010, and in many ways it was a tough year, but we like to think that we managed to come out victorious. It was challenging because our slot count was cut to about half of what we have had the previous year, while still having the same number, if not more projects participate under our umbrella. We also had some surprising student dropouts (one who is still MIA, as far as we know), maybe the aliens targeted OSGeo, because of our knowledge of the earth? ;) But despite these challenges we managed to put out some great projects and were in general very happy with the year.

OSGeo sent 2 delegates to the Mentor summit who participated in many geospatial sessions and also chaired one session. We made new friends among the FLOSS geo-related projects and re-connected with old friends.

OSGeo participated in GSoC in 2009. Twelve OSGeo member projects participated and were very successful. The applications were of better quality so we had fewer dropouts than the previous year. We also had further cross-project co-operation projects, which went very well indeed. OSGeo Sent two delegates to the Mentor Summit.

OSGeo participated in GSoC in 2008. Eleven OSGeo member projects participated and were in general very successful. OSGeo didn't send delegates to the Mentor Summit due to the busy schedules of the mentors.

See http://wiki.osgeo.org/wiki/SoC_Report_2008 for a full report.

OSGeo participated in GSoC in 2007. Six OSGeo projects participated and were generally very successful. OSGeo also sent one delegate to the Mentor Summit in 2007. See http://wiki.osgeo.org/wiki/SoC_Report_2007 for a full report. We also opened up a demo theatre track highlighting SoC work at our foss4g conference that year.

OSGeo was formed in early 2006 and did not participate in GSoC prior to 2007. However, Refractions Research did participate in 2006 on behalf of the GeoTools, uDig, and PostGIS projects which now participate through OSGeo. Most of the the previously participating mentors and administrators continue to be involved in this years OSGeo GSoC effort.

=== 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.''

2007: 13/19 2008: 15/19 2009: 17/20 2010: 7/10

the breakdown of the failures is interesting-
Were failures all from first-time-SOC / outside-of-osgeo projects?
* MapGuide - OSGeo - student who failed was a last minute replacement for Sergei who we gave to another SOC org during the conflict resolution swap-meet.
* MapWindow - non-member OSGeo
* GeoKettle - non-member OSGeo
*
2c thoughts: So we could do better helping our "outsider" projects in? Or perhaps projects already accepted into OSGeo have a long history and established already-integrated teams, thus correlation with success in an OSGeo-led endeavour is not entirely surprising. (aka we can twist our friends arms with greater force than we can our guests).

2009 app comment: "''As the numbers indicate each year we have received better and better applications, and thus have had a better success ratio. Also we have learned to mentor better, and to spot the good applications.''"
* Last year was special in may ways... Projects had to pick between 2 very good students, and then we were also hit by bad luck. Also we had the same number of dropouts, which gives a higher percentage, but the absolute number is still the same. ([[User:Wolf]])

=== What is the URL for your ideas page? ===

http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2011_Ideas

=== 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 2011. If your organization uses more than one list, please make sure to include a description of the list so students know which to use.''
(required)

soc@lists.osgeo.org - For questions about applying and other GSoC questions

See http://wiki.osgeo.org/wiki/Mailing_Lists for a full list and
descriptions of the OSGeo project mailing lists.

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

The primary OSGeo channel is #osgeo on the irc.freenode.net network.
member projects maintain their own IRC channels:
http://wiki.osgeo.org/wiki/IRC

=== 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 2011 site.''

Name:

Country:

School and degree:

Email:

Phone:

OSGeo project(s):

Title:
(please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS")

Describe your idea
1. Introduction
2. Background
3. The idea
4. Project plan (how do you plan to spend your summer?)
5. Future ideas / How can your idea be expanded?

Explain how your SoC task would benefit the OSGeo member project and more generally the OSGeo Foundation as a whole:

Please provide details of previous GIS experience:

Please provide details of any previous involvement with GIS programming and other software programming:

Please provide details of general computing experience:
(operating systems you use on a day-to-day basis, languages you could write a program in, hardware, networking experience, etc.)

Please tell us why you are interested in GIS and open source software:

Please tell us why you are interested in your specific coding project:

Please tell us why you are interested in working for OSGeo and the software project you have selected:

Would your application contribute to your ongoing studies/degree? If so, how?

Please explain how you intend to continue being an active member of your project and/or OSGeo AFTER the summer is over:

Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?

=== What criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible. ===
(required)
The project administrator is appointed by the OSGeo board at the beginning of the year. The project administrator asks for one or two people he trusts to be the backup administrators. Mentors are selected by project steering committees and development teams based on their reputation as skilled developers, domain experience, previously demonstrated ability to support new project developers, and stated willingness to devote time to the mentoring process. We also try very hard to match up the student working on a specific module or tool with a developer with the best expertise in the relevant area. We have in the past not voted up an otherwise good student project if there was no mentor capable of overseeing the project from a technical standpoint. Fortunately we have had a strong response from the developer pool so this has not been a major problem.

=== What is your plan for dealing with disappearing students? ===
(required)
In order to minimize the chance of disappearing students we will ensure that the OSGeo administrative contact and the mentors have full contact information (email, home phone, etc) so that we can keep in touch with them at all times. We also stress to our students that this is a Job, as opposed to a school project.

In addition, we will make our reporting requirements clear up front. Letting the students know that we will require a weekly progress report to be posted to OSGeo's SoC mailing list (cc the member project's development mailing list), participation in public IRC channels and project mailing lists will all help ensure ongoing commitment to the work. Mentors are required to make sure that happens and that the lines of communication are kept open from beginning to end.

Other possibilities include:

# Having potential students work with their potential mentor to prepare a plan for the implementation of their project.
# Setting milestones that need to be reached by the student. These milestones would be defined before the student's work begins. A student would subsequently write a brief e-mail informing the OSGeo SoC mailing list (cc project-specific mailing list) when they have reached each milestone, giving a brief description of the work completed to that date. This is in addition to the weekly progress reports which are intended to be more casual and actively soliciting feedback.
# Selecting students that have shown previous interest in the geospatial field and free software. A student who already has a (reviewable) FOSS track record has a much higher chance of success.

=== What is your plan for dealing with disappearing mentors? ===
(required)

Project steering committees will appoint replacement mentors if existing mentors become unavailable or unresponsive during the project period. We also plan to have backup mentors for projects so the backup mentor can fill in for, or replace the primary mentor in case of changing circumstances. Our administrators take an active role communicating with students and mentors, and so will be able to help out early if there is a problem somewhere.

Among all the OSGeo mailing lists there are 14,000 subscribers, indicating a good pool of people to draw from if required. Due to relatively high member project code and personnel cross-over, in a pinch a mentor from another OSGeo project could usefully help out. Additionally this year we plan on communicating with mentors even more closely thus if something happens with the mentor it should not come as a surprise and additionally there is a backup mentor to continue the mentoring.

=== What steps will you take to encourage students to interact with your project's community before, during and after the program? ===
(required)
=== If you are a small or new organization applying to GSoC, please list a larger, established GSoC organization or a Googler that can vouch for you here. ===

n/a

=== If you are a large organization who is vouching for a small organization applying to GSoC for their first time this year, please list their name and why you think they'd be good candidates for GSoC here ===

As an umbrella organization we are fundamentally a conglomerate of small(er)
organizations and so are well experienced in helping smaller mentoring teams.
We have been happy to mentor-mentor small orgs in the past when they've
approached us, each year taking in a few in-the-same-field projects who were
not technically members of our Foundation but who'd otherwise would have missed
out.

This year we are vouching for Neo4j graph database. Neo4j worked with us last
year as one of the many projects under the OSGeo Umbrella. This year they have
chosen to go on for them selves and we OSGeo vouch for them as an organization.

This year there is also the Opticks project, but they are participating under the
OSGeo umbrealla, since they have started the OSGeo incubation process.

So I guess what we're saying is that we are already performing this role.

=== Anything else you'd like to tell us? ===

GSoC is a very important project for OSGeo. We are investing more and more to it
every year. This year we have a second full-time administrator in order to improve
on the quality of mentoring the mentors. For OSGeo GSoC is not only a means to
increase the size of the community, but also an important event to grow awareness
of our project in academia, and other open source communities.

=== Backup Admin (Link ID) ===

Backup administrators:
* Anne Ghisla (melange: anne_ghisla)
* Hamish Bowman (melange: hamish)

[[Category: Google Summer of Code]]

Google Summer of Code Application 2011

2011-03-10T21:42:38Z

Wiki-Wolf: /* What is your plan for dealing with disappearing students? */

[[Image:GSOC_2011_URL.png|175px|right]]
: http://www.google-melange.com
== Application Deadline ==

: http://www.google-melange.com/document/show/gsoc_program/google/gsoc2011/timeline

* '''February 28''': 19:00 UTC
: Mentoring organizations can begin submitting applications to Google.

* '''March 11''': 23:00 UTC
: Mentoring organization application deadline.

== Old ==

* Base on [[2007 Google SoC Application|2007]], [[2008 Google SoC Application|2008]], [[Google Summer of Code Application 2009|2009]] and [[Google Summer of Code Application 2010]]

== Pending ==

* Verify if the application rules have changed in any way since we last looked at them. - Done (Hamish)
* Apply

== New ==

* Anne!

=== For discussion ===
==== Possible additions to last year's ====

* Title: (''please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS"'')
** Anne: +1 for me.
** Wolf: accepted.

proposed additional question for the application:

* ''Would your application contribute to your ongoing studies/degree? If so, how?''
: (logic: If they will use the software for their degree they will care more about functional and absolutely correct outcomes. Also if they have a local univ. supervisor it's like a built-in co-mentor)

** Anne: Agreed. We can also ask if the supervisor is willing to participate more officially to the application, as co-mentor, for example discussing with the student and the official mentor about goals and timeline.
** Wolf: Accepted and +1 to Anne's comment.

* ''Please explain how you intend to continue being an active member of your project and/or OSGeo AFTER the summer is over''

==== Possible removals vs. last year's ====

* too many "why are you interested in this?" questions? combine some? (or not)
** Anne: They are OK for me. Maybe we can invert the order, starting from more general questions (generic computing > programming > GIS). I also think that these two questions are overlapping, the first can be dropped, if not at least swapped so that first we ask about interest in OSGeo, the in the OSGeo project, then in the specific proposal.
** Wolf: I agree with Anne. It doesn't hurt to have these questions.

Please tell us why you are interested in your specific coding project:
Please tell us why you are interested in working for OSGeo and the software project you have selected:

== The Application ==

=== Organization Name ===
OSGeo - Open Source Geospatial Foundation

=== Description ===

OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and 20 (to 26) code projects in particular:

Web Mapping: '''deegree''', '''geomajas''', '''GeoServer''', '''Mapbender''', '''MapBuilder''', '''MapFish''', '''MapGuide Open Source''', '''MapServer''', '''OpenLayers'''

Desktop Applications: '''GRASS GIS''', '''OSSIM''', '''Quantum GIS''', '''gvSIG'''

Geospatial Libraries: '''FDO''', '''GDAL/OGR''', '''GEOS''', '''GeoTools''', '''MetaCRS''', '''PostGIS'''
: ''The following are sub-projects of MetaCRS'':
:* '''CS-Map''', '''GeoTIFF/libgeotiff''', '''PROJ.4''', '''Proj4J''', '''Proj4js''', '''SpatialReference.org'''

Metadata Catalog: '''GeoNetwork'''

Other (non-code) Projects: '''Public Geospatial Data''', '''Education and Curriculum''', '''Live Handout DVD'''

=== Home page ===
http://www.osgeo.org

=== Main Organization License ===

Each member project uses their own, but all OSGeo projects are required to use an OSI approved license. (see http://www.osgeo.org/incubator/process/evaluation.html)

* Member projects specifically use: GPL >=2, LGPL, MIT/X, ...

GSoC program requires an OSI approved license, but the dropdown only lets you select one.
We go with GPL 2 since it seems to be the one most commonly used.

=== Why is your organization applying to participate in GSoC 2011? What do you hope to gain by participating? ===
(required)

We hope to get more students excited about open source geospatial development. This will help to grow the development community and of course tangibly advance particular projects. Additionally by way of the level of exposure that SoC provides we aim to further extend the use, development, and teaching & training of open source GIS at universities worldwide. This will help to prepare a new generation of developers for industry and government agencies capable of introducing and implementing viable open source geospatial technology, to the benefit of all.

Last but not least we hope to use this opportunity to bring more open source geospatial projects closer and to communicate more. We are encouraging students to come up with ideas that cross project boundaries, and to find new ways to connect the separate efforts in order to bring out new and perhaps improved wholes. In 2008 we also saw the birth of a new project, Spatialytics, which is a novel combination of several geospatial technologies. This is, as stated above, one of our goals, which SGoC helps us achieve in a way which cannot be matched in any other regular effort.

Additionally it has been a great opportunity to mingle code with and get to know other likeminded FOSS projects in our app domain. (such as OSM, Mapnik, Sahana, Ushahidi, ...)

=== If accepted, would this be your first year participating in GSoC? ===

* No

=== Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation. ===

OSgeo participated in 2010, and in many ways it was a tough year, but we like to think that we managed to come out victorious. It was challenging because our slot count was cut to about half of what we have had the previous year, while still having the same number, if not more projects participate under our umbrella. We also had some surprising student dropouts (one who is still MIA, as far as we know), maybe the aliens targeted OSGeo, because of our knowledge of the earth? ;) But despite these challenges we managed to put out some great projects and were in general very happy with the year.

OSGeo sent 2 delegates to the Mentor summit who participated in many geospatial sessions and also chaired one session. We made new friends among the FLOSS geo-related projects and re-connected with old friends.

OSGeo participated in GSoC in 2009. Twelve OSGeo member projects participated and were very successful. The applications were of better quality so we had fewer dropouts than the previous year. We also had further cross-project co-operation projects, which went very well indeed. OSGeo Sent two delegates to the Mentor Summit.

OSGeo participated in GSoC in 2008. Eleven OSGeo member projects participated and were in general very successful. OSGeo didn't send delegates to the Mentor Summit due to the busy schedules of the mentors.

See http://wiki.osgeo.org/wiki/SoC_Report_2008 for a full report.

OSGeo participated in GSoC in 2007. Six OSGeo projects participated and were generally very successful. OSGeo also sent one delegate to the Mentor Summit in 2007. See http://wiki.osgeo.org/wiki/SoC_Report_2007 for a full report. We also opened up a demo theatre track highlighting SoC work at our foss4g conference that year.

OSGeo was formed in early 2006 and did not participate in GSoC prior to 2007. However, Refractions Research did participate in 2006 on behalf of the GeoTools, uDig, and PostGIS projects which now participate through OSGeo. Most of the the previously participating mentors and administrators continue to be involved in this years OSGeo GSoC effort.

=== 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.''

2007: 13/19 2008: 15/19 2009: 17/20 2010: 7/10

the breakdown of the failures is interesting-
Were failures all from first-time-SOC / outside-of-osgeo projects?
* MapGuide - OSGeo - student who failed was a last minute replacement for Sergei who we gave to another SOC org during the conflict resolution swap-meet.
* MapWindow - non-member OSGeo
* GeoKettle - non-member OSGeo
*
2c thoughts: So we could do better helping our "outsider" projects in? Or perhaps projects already accepted into OSGeo have a long history and established already-integrated teams, thus correlation with success in an OSGeo-led endeavour is not entirely surprising. (aka we can twist our friends arms with greater force than we can our guests).

2009 app comment: "''As the numbers indicate each year we have received better and better applications, and thus have had a better success ratio. Also we have learned to mentor better, and to spot the good applications.''"
* Last year was special in may ways... Projects had to pick between 2 very good students, and then we were also hit by bad luck. Also we had the same number of dropouts, which gives a higher percentage, but the absolute number is still the same. ([[User:Wolf]])

=== What is the URL for your ideas page? ===

http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2011_Ideas

=== 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 2011. If your organization uses more than one list, please make sure to include a description of the list so students know which to use.''
(required)

soc@lists.osgeo.org - For questions about applying and other GSoC questions

See http://wiki.osgeo.org/wiki/Mailing_Lists for a full list and
descriptions of the OSGeo project mailing lists.

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

The primary OSGeo channel is #osgeo on the irc.freenode.net network.
member projects maintain their own IRC channels:
http://wiki.osgeo.org/wiki/IRC

=== 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 2011 site.''

Name:

Country:

School and degree:

Email:

Phone:

OSGeo project(s):

Title:
(please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS")

Describe your idea
1. Introduction
2. Background
3. The idea
4. Project plan (how do you plan to spend your summer?)
5. Future ideas / How can your idea be expanded?

Explain how your SoC task would benefit the OSGeo member project and more generally the OSGeo Foundation as a whole:

Please provide details of previous GIS experience:

Please provide details of any previous involvement with GIS programming and other software programming:

Please provide details of general computing experience:
(operating systems you use on a day-to-day basis, languages you could write a program in, hardware, networking experience, etc.)

Please tell us why you are interested in GIS and open source software:

Please tell us why you are interested in your specific coding project:

Please tell us why you are interested in working for OSGeo and the software project you have selected:

Would your application contribute to your ongoing studies/degree? If so, how?

Please explain how you intend to continue being an active member of your project and/or OSGeo AFTER the summer is over:

Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?

=== What criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible. ===
(required)
The project administrator is appointed by the OSGeo board at the beginning of the year. The project administrator asks for one or two people he trusts to be the backup administrators. Mentors are selected by project steering committees and development teams based on their reputation as skilled developers, domain experience, previously demonstrated ability to support new project developers, and stated willingness to devote time to the mentoring process. We also try very hard to match up the student working on a specific module or tool with a developer with the best expertise in the relevant area. We have in the past not voted up an otherwise good student project if there was no mentor capable of overseeing the project from a technical standpoint. Fortunately we have had a strong response from the developer pool so this has not been a major problem.

=== What is your plan for dealing with disappearing students? ===
(required)
In order to minimize the chance of disappearing students we will ensure that the OSGeo administrative contact and the mentors have full contact information (email, home phone, etc) so that we can keep in touch with them at all times. We also stress to our students that this is a Job, as opposed to a school project.

In addition, we will make our reporting requirements clear up front. Letting the students know that we will require a weekly progress report to be posted to OSGeo's SoC mailing list (cc the member project's development mailing list), participation in public IRC channels and project mailing lists will all help ensure ongoing commitment to the work. Mentors are required to make sure that happens and that the lines of communication are kept open from beginning to end.

Other possibilities include:

# Having potential students work with their potential mentor to prepare a plan for the implementation of their project.
# Setting milestones that need to be reached by the student. These milestones would be defined before the student's work begins. A student would subsequently write a brief e-mail informing the OSGeo SoC mailing list (cc project-specific mailing list) when they have reached each milestone, giving a brief description of the work completed to that date. This is in addition to the weekly progress reports which are intended to be more casual and actively soliciting feedback.
# Selecting students that have shown previous interest in the geospatial field and free software. A student who already has a (reviewable) FOSS track record has a much higher chance of success.

=== What is your plan for dealing with disappearing mentors? ===
(required)
=== What steps will you take to encourage students to interact with your project's community before, during and after the program? ===
(required)
=== If you are a small or new organization applying to GSoC, please list a larger, established GSoC organization or a Googler that can vouch for you here. ===

n/a

=== If you are a large organization who is vouching for a small organization applying to GSoC for their first time this year, please list their name and why you think they'd be good candidates for GSoC here ===

As an umbrella organization we are fundamentally a conglomerate of small(er)
organizations and so are well experienced in helping smaller mentoring teams.
We have been happy to mentor-mentor small orgs in the past when they've
approached us, each year taking in a few in-the-same-field projects who were
not technically members of our Foundation but who'd otherwise would have missed
out.

This year we are vouching for Neo4j graph database. Neo4j worked with us last
year as one of the many projects under the OSGeo Umbrella. This year they have
chosen to go on for them selves and we OSGeo vouch for them as an organization.

This year there is also the Opticks project, but they are participating under the
OSGeo umbrealla, since they have started the OSGeo incubation process.

So I guess what we're saying is that we are already performing this role.

=== Anything else you'd like to tell us? ===

GSoC is a very important project for OSGeo. We are investing more and more to it
every year. This year we have a second full-time administrator in order to improve
on the quality of mentoring the mentors. For OSGeo GSoC is not only a means to
increase the size of the community, but also an important event to grow awareness
of our project in academia, and other open source communities.

=== Backup Admin (Link ID) ===

Backup administrators:
* Anne Ghisla (melange: anne_ghisla)
* Hamish Bowman (melange: hamish)

[[Category: Google Summer of Code]]

Google Summer of Code Application 2011

2011-03-10T21:39:56Z

Wiki-Wolf: /* What criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible. */

[[Image:GSOC_2011_URL.png|175px|right]]
: http://www.google-melange.com
== Application Deadline ==

: http://www.google-melange.com/document/show/gsoc_program/google/gsoc2011/timeline

* '''February 28''': 19:00 UTC
: Mentoring organizations can begin submitting applications to Google.

* '''March 11''': 23:00 UTC
: Mentoring organization application deadline.

== Old ==

* Base on [[2007 Google SoC Application|2007]], [[2008 Google SoC Application|2008]], [[Google Summer of Code Application 2009|2009]] and [[Google Summer of Code Application 2010]]

== Pending ==

* Verify if the application rules have changed in any way since we last looked at them. - Done (Hamish)
* Apply

== New ==

* Anne!

=== For discussion ===
==== Possible additions to last year's ====

* Title: (''please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS"'')
** Anne: +1 for me.
** Wolf: accepted.

proposed additional question for the application:

* ''Would your application contribute to your ongoing studies/degree? If so, how?''
: (logic: If they will use the software for their degree they will care more about functional and absolutely correct outcomes. Also if they have a local univ. supervisor it's like a built-in co-mentor)

** Anne: Agreed. We can also ask if the supervisor is willing to participate more officially to the application, as co-mentor, for example discussing with the student and the official mentor about goals and timeline.
** Wolf: Accepted and +1 to Anne's comment.

* ''Please explain how you intend to continue being an active member of your project and/or OSGeo AFTER the summer is over''

==== Possible removals vs. last year's ====

* too many "why are you interested in this?" questions? combine some? (or not)
** Anne: They are OK for me. Maybe we can invert the order, starting from more general questions (generic computing > programming > GIS). I also think that these two questions are overlapping, the first can be dropped, if not at least swapped so that first we ask about interest in OSGeo, the in the OSGeo project, then in the specific proposal.
** Wolf: I agree with Anne. It doesn't hurt to have these questions.

Please tell us why you are interested in your specific coding project:
Please tell us why you are interested in working for OSGeo and the software project you have selected:

== The Application ==

=== Organization Name ===
OSGeo - Open Source Geospatial Foundation

=== Description ===

OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and 20 (to 26) code projects in particular:

Web Mapping: '''deegree''', '''geomajas''', '''GeoServer''', '''Mapbender''', '''MapBuilder''', '''MapFish''', '''MapGuide Open Source''', '''MapServer''', '''OpenLayers'''

Desktop Applications: '''GRASS GIS''', '''OSSIM''', '''Quantum GIS''', '''gvSIG'''

Geospatial Libraries: '''FDO''', '''GDAL/OGR''', '''GEOS''', '''GeoTools''', '''MetaCRS''', '''PostGIS'''
: ''The following are sub-projects of MetaCRS'':
:* '''CS-Map''', '''GeoTIFF/libgeotiff''', '''PROJ.4''', '''Proj4J''', '''Proj4js''', '''SpatialReference.org'''

Metadata Catalog: '''GeoNetwork'''

Other (non-code) Projects: '''Public Geospatial Data''', '''Education and Curriculum''', '''Live Handout DVD'''

=== Home page ===
http://www.osgeo.org

=== Main Organization License ===

Each member project uses their own, but all OSGeo projects are required to use an OSI approved license. (see http://www.osgeo.org/incubator/process/evaluation.html)

* Member projects specifically use: GPL >=2, LGPL, MIT/X, ...

GSoC program requires an OSI approved license, but the dropdown only lets you select one.
We go with GPL 2 since it seems to be the one most commonly used.

=== Why is your organization applying to participate in GSoC 2011? What do you hope to gain by participating? ===
(required)

We hope to get more students excited about open source geospatial development. This will help to grow the development community and of course tangibly advance particular projects. Additionally by way of the level of exposure that SoC provides we aim to further extend the use, development, and teaching & training of open source GIS at universities worldwide. This will help to prepare a new generation of developers for industry and government agencies capable of introducing and implementing viable open source geospatial technology, to the benefit of all.

Last but not least we hope to use this opportunity to bring more open source geospatial projects closer and to communicate more. We are encouraging students to come up with ideas that cross project boundaries, and to find new ways to connect the separate efforts in order to bring out new and perhaps improved wholes. In 2008 we also saw the birth of a new project, Spatialytics, which is a novel combination of several geospatial technologies. This is, as stated above, one of our goals, which SGoC helps us achieve in a way which cannot be matched in any other regular effort.

Additionally it has been a great opportunity to mingle code with and get to know other likeminded FOSS projects in our app domain. (such as OSM, Mapnik, Sahana, Ushahidi, ...)

=== If accepted, would this be your first year participating in GSoC? ===

* No

=== Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation. ===

OSgeo participated in 2010, and in many ways it was a tough year, but we like to think that we managed to come out victorious. It was challenging because our slot count was cut to about half of what we have had the previous year, while still having the same number, if not more projects participate under our umbrella. We also had some surprising student dropouts (one who is still MIA, as far as we know), maybe the aliens targeted OSGeo, because of our knowledge of the earth? ;) But despite these challenges we managed to put out some great projects and were in general very happy with the year.

OSGeo sent 2 delegates to the Mentor summit who participated in many geospatial sessions and also chaired one session. We made new friends among the FLOSS geo-related projects and re-connected with old friends.

OSGeo participated in GSoC in 2009. Twelve OSGeo member projects participated and were very successful. The applications were of better quality so we had fewer dropouts than the previous year. We also had further cross-project co-operation projects, which went very well indeed. OSGeo Sent two delegates to the Mentor Summit.

OSGeo participated in GSoC in 2008. Eleven OSGeo member projects participated and were in general very successful. OSGeo didn't send delegates to the Mentor Summit due to the busy schedules of the mentors.

See http://wiki.osgeo.org/wiki/SoC_Report_2008 for a full report.

OSGeo participated in GSoC in 2007. Six OSGeo projects participated and were generally very successful. OSGeo also sent one delegate to the Mentor Summit in 2007. See http://wiki.osgeo.org/wiki/SoC_Report_2007 for a full report. We also opened up a demo theatre track highlighting SoC work at our foss4g conference that year.

OSGeo was formed in early 2006 and did not participate in GSoC prior to 2007. However, Refractions Research did participate in 2006 on behalf of the GeoTools, uDig, and PostGIS projects which now participate through OSGeo. Most of the the previously participating mentors and administrators continue to be involved in this years OSGeo GSoC effort.

=== 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.''

2007: 13/19 2008: 15/19 2009: 17/20 2010: 7/10

the breakdown of the failures is interesting-
Were failures all from first-time-SOC / outside-of-osgeo projects?
* MapGuide - OSGeo - student who failed was a last minute replacement for Sergei who we gave to another SOC org during the conflict resolution swap-meet.
* MapWindow - non-member OSGeo
* GeoKettle - non-member OSGeo
*
2c thoughts: So we could do better helping our "outsider" projects in? Or perhaps projects already accepted into OSGeo have a long history and established already-integrated teams, thus correlation with success in an OSGeo-led endeavour is not entirely surprising. (aka we can twist our friends arms with greater force than we can our guests).

2009 app comment: "''As the numbers indicate each year we have received better and better applications, and thus have had a better success ratio. Also we have learned to mentor better, and to spot the good applications.''"
* Last year was special in may ways... Projects had to pick between 2 very good students, and then we were also hit by bad luck. Also we had the same number of dropouts, which gives a higher percentage, but the absolute number is still the same. ([[User:Wolf]])

=== What is the URL for your ideas page? ===

http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2011_Ideas

=== 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 2011. If your organization uses more than one list, please make sure to include a description of the list so students know which to use.''
(required)

soc@lists.osgeo.org - For questions about applying and other GSoC questions

See http://wiki.osgeo.org/wiki/Mailing_Lists for a full list and
descriptions of the OSGeo project mailing lists.

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

The primary OSGeo channel is #osgeo on the irc.freenode.net network.
member projects maintain their own IRC channels:
http://wiki.osgeo.org/wiki/IRC

=== 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 2011 site.''

Name:

Country:

School and degree:

Email:

Phone:

OSGeo project(s):

Title:
(please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS")

Describe your idea
1. Introduction
2. Background
3. The idea
4. Project plan (how do you plan to spend your summer?)
5. Future ideas / How can your idea be expanded?

Explain how your SoC task would benefit the OSGeo member project and more generally the OSGeo Foundation as a whole:

Please provide details of previous GIS experience:

Please provide details of any previous involvement with GIS programming and other software programming:

Please provide details of general computing experience:
(operating systems you use on a day-to-day basis, languages you could write a program in, hardware, networking experience, etc.)

Please tell us why you are interested in GIS and open source software:

Please tell us why you are interested in your specific coding project:

Please tell us why you are interested in working for OSGeo and the software project you have selected:

Would your application contribute to your ongoing studies/degree? If so, how?

Please explain how you intend to continue being an active member of your project and/or OSGeo AFTER the summer is over:

Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?

=== What criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible. ===
(required)
The project administrator is appointed by the OSGeo board at the beginning of the year. The project administrator asks for one or two people he trusts to be the backup administrators. Mentors are selected by project steering committees and development teams based on their reputation as skilled developers, domain experience, previously demonstrated ability to support new project developers, and stated willingness to devote time to the mentoring process. We also try very hard to match up the student working on a specific module or tool with a developer with the best expertise in the relevant area. We have in the past not voted up an otherwise good student project if there was no mentor capable of overseeing the project from a technical standpoint. Fortunately we have had a strong response from the developer pool so this has not been a major problem.

=== What is your plan for dealing with disappearing students? ===
(required)
=== What is your plan for dealing with disappearing mentors? ===
(required)
=== What steps will you take to encourage students to interact with your project's community before, during and after the program? ===
(required)
=== If you are a small or new organization applying to GSoC, please list a larger, established GSoC organization or a Googler that can vouch for you here. ===

n/a

=== If you are a large organization who is vouching for a small organization applying to GSoC for their first time this year, please list their name and why you think they'd be good candidates for GSoC here ===

As an umbrella organization we are fundamentally a conglomerate of small(er)
organizations and so are well experienced in helping smaller mentoring teams.
We have been happy to mentor-mentor small orgs in the past when they've
approached us, each year taking in a few in-the-same-field projects who were
not technically members of our Foundation but who'd otherwise would have missed
out.

This year we are vouching for Neo4j graph database. Neo4j worked with us last
year as one of the many projects under the OSGeo Umbrella. This year they have
chosen to go on for them selves and we OSGeo vouch for them as an organization.

This year there is also the Opticks project, but they are participating under the
OSGeo umbrealla, since they have started the OSGeo incubation process.

So I guess what we're saying is that we are already performing this role.

=== Anything else you'd like to tell us? ===

GSoC is a very important project for OSGeo. We are investing more and more to it
every year. This year we have a second full-time administrator in order to improve
on the quality of mentoring the mentors. For OSGeo GSoC is not only a means to
increase the size of the community, but also an important event to grow awareness
of our project in academia, and other open source communities.

=== Backup Admin (Link ID) ===

Backup administrators:
* Anne Ghisla (melange: anne_ghisla)
* Hamish Bowman (melange: hamish)

[[Category: Google Summer of Code]]

Google Summer of Code Application 2011

2011-03-10T21:38:39Z

Wiki-Wolf: /* Does your organization have an application template you would like to see students use? */

[[Image:GSOC_2011_URL.png|175px|right]]
: http://www.google-melange.com
== Application Deadline ==

: http://www.google-melange.com/document/show/gsoc_program/google/gsoc2011/timeline

* '''February 28''': 19:00 UTC
: Mentoring organizations can begin submitting applications to Google.

* '''March 11''': 23:00 UTC
: Mentoring organization application deadline.

== Old ==

* Base on [[2007 Google SoC Application|2007]], [[2008 Google SoC Application|2008]], [[Google Summer of Code Application 2009|2009]] and [[Google Summer of Code Application 2010]]

== Pending ==

* Verify if the application rules have changed in any way since we last looked at them. - Done (Hamish)
* Apply

== New ==

* Anne!

=== For discussion ===
==== Possible additions to last year's ====

* Title: (''please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS"'')
** Anne: +1 for me.
** Wolf: accepted.

proposed additional question for the application:

* ''Would your application contribute to your ongoing studies/degree? If so, how?''
: (logic: If they will use the software for their degree they will care more about functional and absolutely correct outcomes. Also if they have a local univ. supervisor it's like a built-in co-mentor)

** Anne: Agreed. We can also ask if the supervisor is willing to participate more officially to the application, as co-mentor, for example discussing with the student and the official mentor about goals and timeline.
** Wolf: Accepted and +1 to Anne's comment.

* ''Please explain how you intend to continue being an active member of your project and/or OSGeo AFTER the summer is over''

==== Possible removals vs. last year's ====

* too many "why are you interested in this?" questions? combine some? (or not)
** Anne: They are OK for me. Maybe we can invert the order, starting from more general questions (generic computing > programming > GIS). I also think that these two questions are overlapping, the first can be dropped, if not at least swapped so that first we ask about interest in OSGeo, the in the OSGeo project, then in the specific proposal.
** Wolf: I agree with Anne. It doesn't hurt to have these questions.

Please tell us why you are interested in your specific coding project:
Please tell us why you are interested in working for OSGeo and the software project you have selected:

== The Application ==

=== Organization Name ===
OSGeo - Open Source Geospatial Foundation

=== Description ===

OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and 20 (to 26) code projects in particular:

Web Mapping: '''deegree''', '''geomajas''', '''GeoServer''', '''Mapbender''', '''MapBuilder''', '''MapFish''', '''MapGuide Open Source''', '''MapServer''', '''OpenLayers'''

Desktop Applications: '''GRASS GIS''', '''OSSIM''', '''Quantum GIS''', '''gvSIG'''

Geospatial Libraries: '''FDO''', '''GDAL/OGR''', '''GEOS''', '''GeoTools''', '''MetaCRS''', '''PostGIS'''
: ''The following are sub-projects of MetaCRS'':
:* '''CS-Map''', '''GeoTIFF/libgeotiff''', '''PROJ.4''', '''Proj4J''', '''Proj4js''', '''SpatialReference.org'''

Metadata Catalog: '''GeoNetwork'''

Other (non-code) Projects: '''Public Geospatial Data''', '''Education and Curriculum''', '''Live Handout DVD'''

=== Home page ===
http://www.osgeo.org

=== Main Organization License ===

Each member project uses their own, but all OSGeo projects are required to use an OSI approved license. (see http://www.osgeo.org/incubator/process/evaluation.html)

* Member projects specifically use: GPL >=2, LGPL, MIT/X, ...

GSoC program requires an OSI approved license, but the dropdown only lets you select one.
We go with GPL 2 since it seems to be the one most commonly used.

=== Why is your organization applying to participate in GSoC 2011? What do you hope to gain by participating? ===
(required)

We hope to get more students excited about open source geospatial development. This will help to grow the development community and of course tangibly advance particular projects. Additionally by way of the level of exposure that SoC provides we aim to further extend the use, development, and teaching & training of open source GIS at universities worldwide. This will help to prepare a new generation of developers for industry and government agencies capable of introducing and implementing viable open source geospatial technology, to the benefit of all.

Last but not least we hope to use this opportunity to bring more open source geospatial projects closer and to communicate more. We are encouraging students to come up with ideas that cross project boundaries, and to find new ways to connect the separate efforts in order to bring out new and perhaps improved wholes. In 2008 we also saw the birth of a new project, Spatialytics, which is a novel combination of several geospatial technologies. This is, as stated above, one of our goals, which SGoC helps us achieve in a way which cannot be matched in any other regular effort.

Additionally it has been a great opportunity to mingle code with and get to know other likeminded FOSS projects in our app domain. (such as OSM, Mapnik, Sahana, Ushahidi, ...)

=== If accepted, would this be your first year participating in GSoC? ===

* No

=== Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation. ===

OSgeo participated in 2010, and in many ways it was a tough year, but we like to think that we managed to come out victorious. It was challenging because our slot count was cut to about half of what we have had the previous year, while still having the same number, if not more projects participate under our umbrella. We also had some surprising student dropouts (one who is still MIA, as far as we know), maybe the aliens targeted OSGeo, because of our knowledge of the earth? ;) But despite these challenges we managed to put out some great projects and were in general very happy with the year.

OSGeo sent 2 delegates to the Mentor summit who participated in many geospatial sessions and also chaired one session. We made new friends among the FLOSS geo-related projects and re-connected with old friends.

OSGeo participated in GSoC in 2009. Twelve OSGeo member projects participated and were very successful. The applications were of better quality so we had fewer dropouts than the previous year. We also had further cross-project co-operation projects, which went very well indeed. OSGeo Sent two delegates to the Mentor Summit.

OSGeo participated in GSoC in 2008. Eleven OSGeo member projects participated and were in general very successful. OSGeo didn't send delegates to the Mentor Summit due to the busy schedules of the mentors.

See http://wiki.osgeo.org/wiki/SoC_Report_2008 for a full report.

OSGeo participated in GSoC in 2007. Six OSGeo projects participated and were generally very successful. OSGeo also sent one delegate to the Mentor Summit in 2007. See http://wiki.osgeo.org/wiki/SoC_Report_2007 for a full report. We also opened up a demo theatre track highlighting SoC work at our foss4g conference that year.

OSGeo was formed in early 2006 and did not participate in GSoC prior to 2007. However, Refractions Research did participate in 2006 on behalf of the GeoTools, uDig, and PostGIS projects which now participate through OSGeo. Most of the the previously participating mentors and administrators continue to be involved in this years OSGeo GSoC effort.

=== 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.''

2007: 13/19 2008: 15/19 2009: 17/20 2010: 7/10

the breakdown of the failures is interesting-
Were failures all from first-time-SOC / outside-of-osgeo projects?
* MapGuide - OSGeo - student who failed was a last minute replacement for Sergei who we gave to another SOC org during the conflict resolution swap-meet.
* MapWindow - non-member OSGeo
* GeoKettle - non-member OSGeo
*
2c thoughts: So we could do better helping our "outsider" projects in? Or perhaps projects already accepted into OSGeo have a long history and established already-integrated teams, thus correlation with success in an OSGeo-led endeavour is not entirely surprising. (aka we can twist our friends arms with greater force than we can our guests).

2009 app comment: "''As the numbers indicate each year we have received better and better applications, and thus have had a better success ratio. Also we have learned to mentor better, and to spot the good applications.''"
* Last year was special in may ways... Projects had to pick between 2 very good students, and then we were also hit by bad luck. Also we had the same number of dropouts, which gives a higher percentage, but the absolute number is still the same. ([[User:Wolf]])

=== What is the URL for your ideas page? ===

http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2011_Ideas

=== 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 2011. If your organization uses more than one list, please make sure to include a description of the list so students know which to use.''
(required)

soc@lists.osgeo.org - For questions about applying and other GSoC questions

See http://wiki.osgeo.org/wiki/Mailing_Lists for a full list and
descriptions of the OSGeo project mailing lists.

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

The primary OSGeo channel is #osgeo on the irc.freenode.net network.
member projects maintain their own IRC channels:
http://wiki.osgeo.org/wiki/IRC

=== 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 2011 site.''

Name:

Country:

School and degree:

Email:

Phone:

OSGeo project(s):

Title:
(please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS")

Describe your idea
1. Introduction
2. Background
3. The idea
4. Project plan (how do you plan to spend your summer?)
5. Future ideas / How can your idea be expanded?

Explain how your SoC task would benefit the OSGeo member project and more generally the OSGeo Foundation as a whole:

Please provide details of previous GIS experience:

Please provide details of any previous involvement with GIS programming and other software programming:

Please provide details of general computing experience:
(operating systems you use on a day-to-day basis, languages you could write a program in, hardware, networking experience, etc.)

Please tell us why you are interested in GIS and open source software:

Please tell us why you are interested in your specific coding project:

Please tell us why you are interested in working for OSGeo and the software project you have selected:

Would your application contribute to your ongoing studies/degree? If so, how?

Please explain how you intend to continue being an active member of your project and/or OSGeo AFTER the summer is over:

Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?

=== What criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible. ===
(required)
=== What is your plan for dealing with disappearing students? ===
(required)
=== What is your plan for dealing with disappearing mentors? ===
(required)
=== What steps will you take to encourage students to interact with your project's community before, during and after the program? ===
(required)
=== If you are a small or new organization applying to GSoC, please list a larger, established GSoC organization or a Googler that can vouch for you here. ===

n/a

=== If you are a large organization who is vouching for a small organization applying to GSoC for their first time this year, please list their name and why you think they'd be good candidates for GSoC here ===

As an umbrella organization we are fundamentally a conglomerate of small(er)
organizations and so are well experienced in helping smaller mentoring teams.
We have been happy to mentor-mentor small orgs in the past when they've
approached us, each year taking in a few in-the-same-field projects who were
not technically members of our Foundation but who'd otherwise would have missed
out.

This year we are vouching for Neo4j graph database. Neo4j worked with us last
year as one of the many projects under the OSGeo Umbrella. This year they have
chosen to go on for them selves and we OSGeo vouch for them as an organization.

This year there is also the Opticks project, but they are participating under the
OSGeo umbrealla, since they have started the OSGeo incubation process.

So I guess what we're saying is that we are already performing this role.

=== Anything else you'd like to tell us? ===

GSoC is a very important project for OSGeo. We are investing more and more to it
every year. This year we have a second full-time administrator in order to improve
on the quality of mentoring the mentors. For OSGeo GSoC is not only a means to
increase the size of the community, but also an important event to grow awareness
of our project in academia, and other open source communities.

=== Backup Admin (Link ID) ===

Backup administrators:
* Anne Ghisla (melange: anne_ghisla)
* Hamish Bowman (melange: hamish)

[[Category: Google Summer of Code]]

Google Summer of Code Application 2011

2011-03-10T21:26:43Z

Wiki-Wolf: /* For discussion */

Google Summer of Code Application 2011

2011-03-10T21:16:49Z

Wiki-Wolf: /* If your organization participated in past GSoCs, please let us know the ratio of students passing to students allocated */

Google Summer of Code Application 2011

2011-03-10T21:15:14Z

Wiki-Wolf: /* If your organization participated in past GSoCs, please let us know the ratio of students passing to students allocated */

Google Summer of Code Application 2011

2011-03-10T21:07:34Z

Wiki-Wolf: /* Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation. */

Google Summer of Code Application 2011

2011-03-10T20:54:32Z

Wiki-Wolf: /* Why is your organization applying to participate in GSoC 2011? What do you hope to gain by participating? */

Google Summer of Code Application 2011

2011-03-10T20:50:35Z

Wiki-Wolf: /* Anything else you'd like to tell us? */

Google Summer of Code Application 2011

2011-03-10T20:47:26Z

Wiki-Wolf: /* Backup Admin (Link ID) */

Google Summer of Code Application 2011

2011-03-10T20:43:44Z

Google Summer of Code 2011 Administrative

2011-03-10T20:28:16Z

Wiki-Wolf: /* How to register as a mentor */

[[Image:GSOC_2011_URL.png|250px|right]]

* Back to main OSGeo [[Google Summer of Code]] wiki page.

Central page for administering OSGeo participation in Google Summer of Code 2011.

== Background ==

* Wolf Bergenheim will act as Administrative contact, with support from [[User:Aghisla|Anne Ghisla]] and [[HamishBowman|Hamish Bowman]]

* [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2011/faqs Google's FAQ on the program]

* There is also a [http://code.google.com/p/google-summer-of-code/wiki/WikiStart Google Wiki page about the program]

* Previous years' SoC involvement: [http://code.google.com/soc/2008/osgeo/about.html 2008], [http://socghop.appspot.com/org/home/google/gsoc2009/osgeo 2009], [http://socghop.appspot.com/org/home/google/gsoc2010/osgeo 2010]

* Last year(s) OSGeo GSoC wiki pages: [[Google Summer of Code 2008|2008]], [[Google Summer of Code 2009|2009]], [[Google Summer of Code 2010|2010]]

* [http://primates.ximian.com/~federico/docs/summer-of-code-mentoring-howto/index.html Mentoring HOWTO]

* [http://code.google.com/p/google-summer-of-code/wiki/AdviceforMentors Advice for Mentors from the Google Wiki]

* The official [http://socghop.appspot.com/ Google Summer of Code 2011 program site]

* There is a 2010 version of the [http://svn.osgeo.org/osgeo/marketing/flyer/ OSGeo SoC flyer] to look at and post in appropriate places.

== Timeline ==

[http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2011/timeline The official timeline]

== Documents ==

* OSGeo [[Google Summer of Code Application 2011]] (see also [[Google SoC Application 2009|2009]], [[Google SoC Application 2010|2010]])

* [[SoC Application Rankings by Project]]

* The "Student Landing Page" is [[Google Summer of Code 2011 Ideas]].

* The 2010 OSGeo home at melange is (http://socghop.appspot.com/org/home/google/gsoc2010/osgeo)

== How to register as a mentor ==

Please apply to become a mentor today! Just follow these steps:

# Sign up to the [http://lists.osgeo.org/mailman/listinfo/soc OSGeo SoC mailinglist].
# Present yourself on soc@lists.osgeo.org Here are some suggested topics:
#* Project you want to/can mentor for
#* Area(s) of interest
#* Feel free to tell more about yourself
# Register yourself [http://socghop.appspot.com/ at the Melange site] (if you haven't done so already).
# Fill in the [https://spreadsheets.google.com/viewform?formkey=dEpKRDUzZEU4dXRxdHd5MVhCRWlSZXc6MA Mentor form]
# [http://socghop.appspot.com/gsoc/mentor/request/google/gsoc2011/osgeo Apply to become a mentor]
#* Accept the invitation that you receive, and fill in your Mentor information
# Go [http://socghop.appspot.com/org/list_proposals/google/gsoc2011/osgeo read and comment on student applications] (Opens March 29th)







[[Category: Google Summer of Code]]

New Member Nominations 2010

2010-10-23T23:03:26Z

Wiki-Wolf: Added Anne Ghisla

{| class="wikitable"
|-
!Name
!Notes
|-
|Steve Woodbridge
|
* Steve has long been a strong advocate and user of the open geospatial world of products. It would be hard to find someone who is more helpful and willing to help on any topic than Steve. From his early help on Mapserver until now, Steve has been a very active member and contributor in the geospatial community.
|-
|Jesse Eichar
|
* Jesse Eichar has been a long-time developer on the uDig open source desktop GIS, and has contributed important work to the GeoTools library. He is a constant presence on the uDig community list, helping new users and developers. He has participated in the FOSS4G conference over the years, giving talks and teaching workshops. He knows the open source geospatial world, and is a part of the larger community.
|-
|Alex Mandel
|
* Alex is an excessively active contributor to the numerous facets of OSGeo. You have likely seen him on one of the many OSGeo IRC channel he haunts, regularly offering advice to newbies, contributing to conversations and volunteering to take on tasks. I've seen him contribute significantly over the last couple of years to the core development of the OSGeo-Live project and the marketing committee. He also helps out of the System Administration Committee, acts as a representative at numerous trade fairs, helped found the Californian OSGeo chapter, helped develop numerous Geography academic courses which use a variety of FOSS applications and he has contributed directly to QGIS. Alex brings a valuable "user perspective" with him, as he has a degree in Wildlife Biology and field experience with State and Federal agencies.
|-
|Hirofumi Hayashi
|
* He is one of the most active member of OSGeo-Japan Local Chapter and is deeply involved in promoting OSGeo in Japan and elsewhere. He is a great team player and also contributed significantly to Internationalization of OSGeo software, localization of documentation, enhancement to OSGeo4W package and organization of FOSS4G events in Japan. He is the Vice-Representative of OSGeo Japan Local Chapter and PSC member in the ZOO project. He bears all the positive attributes desired of a OSGeo Charter Member
|-
|Gavin Fleming
|
* Gavin is the chief organizer of FOSS4G 2008. I attended the FOSS4G2008 conference, which Gavin was instrumental in organising. He and his team attracted delegates from some 50 countries, and subsequently produced a hugely successful conference. This is a tribute to Gavin's exceptional hard work and dedication to the task at hand. In so doing, he managed to put South Africa firmly onto the FOSS4G map. I particularly appreciated his kind manner, for regardless of the pressures on him, he always treated people with dignity and respect.
|-
|Suchith Anand
|
* Suchith is the chief organizer of OSGIS UK 2009 and 2010, as an OSGeo charter member. Suchith has done a major service to the interests of our foundation by organizing OSGIS UK conferences and by setting up an open source geospatial lab at University of Nottingham and negotiating a MoU with OSGeo, I think he definitely should be a charter member.
|-
|Dr. Xianfeng Song
|
* Dr. Xianfeng Song, Associate Professor, Graduate University of Chinese Academy of Sciences, for his contributions to the FOSS4G2010 as a academic chair and also his great activities in OSGeo China and Japan chapters to involve international collaborations.
|-
|Milena Nowotarska
|
* [[Milena_Nowotarska]] is very active member of Poland OSGeo Chapter. She is the key person in localization of Quantum GIS, GRASS, gvSIG and author of first polish QGIS manual. Milena has been involved in translations of GUI, manuals, brochures and promotional materials. Co-founder of polish forum and wiki for mentioned projects and GRASS-wiki manager. Trainer and teacher of FOSS4G at university and during several workshops. Milena plays important role in popularization of FOSS in local governmental agencies in Poland. Co-organizer of upcoming QGIS Hackfest in Wroclaw 2010.
|-
|Hirofumi Hayashi
|
* Mr. Hayashi is one of the most active member of OSGeo-Japan Local Chapter and is deeply involved in promoting OSGeo in Japan and elsewhere. He is a great team player and also contributed significantly to Internationalization of OSGeo software, localization of documentation, enhancement to OSGeo4W package and organization of FOSS4G events in Japan. He is the Vice-Representative of OSGeo Japan Local Chapter and PSC member in the ZOO project. He bears all the positive attributes desired of a OSGeo Charter Member.
|-
|Bruce Bannerman
|
* Bruce has been very hard working toward the OSGeo cause and often provides valuable insights to OSGeo discussions from a government purchasing perspective. He currently works as the key a GeoSpatial Architect at the Australian Bureau of Meteorology, where he plays a key role in international programs such as the Global Earth Observation System of Systems http://www.earthobservations.org/ . Bruce was incredibly hard working on the FOSS4G 2009 organising committee, and was key in fostering OSGeo/OGC relationships by coordination and sourcing substantial sponsorship for the Climate Change Integration Plugfest. He has done a lot of local OSGeo evangelism, manning OSGeo booths at conferences, writing papers for Government committees on behalf of OSGeo and helping found and run the Australian/New Zealand local chapter of OSGeo.
|-
|Nicolas Bozon
|
* Nicolas Bozon is specialized in design and GUIs for FOSS4G based applications, he has contributed to various FOSS4G projects and used OSGeo tools for scientific research projects. He actively promoted OSGeo during many trainings and workshops in France and participates actively in national and international conferences (OSGeo fr + jp + th, ...), giving talks and teaching workshops. Nicolas co-founded the ZOO Project (http://zoo-project.org/), is ZOO PSC member and important contributor.
|-
|Jo Cook
|
* Jo Cook is the patient leader of the UK OSGeo community. For years she has stuck with it, waiting for the world around her to catch up. Now she is providing a guiding hand to the flourishing OSGeo:UK chapter as its members put on conferences, masterclasses, training. Jo's notable FOSS4G presentations include "[http://2007.foss4g.org/presentations/view.php?abstract_id=81| Portable GIS - GIS on a USB stick]" in 2007 and "[http://2010.foss4g.org/presentations_show.php?id=3595| Open source archaeology - two years later]" in 2010. One reason i am nominating Jo is that i think she'd make a good board member for the OSGeo foundation. I was surprised to learn that Jo's not already an OSGeo charter member.
|-
|Daniel Ames
|
* Dan is instrumental in the .NET side of the open source geo ecosystem, heading up both the MapWindow (http://www.mapwindow.org/) and the DotSpatial (http://dotspatial.codeplex.com/) projects.
|-
|Karsten Vennemann
|
* Karsten is an active and well-known OSGeo champion in the Seattle area, running his own OS-based consulting shop and regularly promoting the OSGeo agenda by running training classes and workshops on free and open source GIS tools.
|-
| Simon Mercier
|
* Simon is indeed an active member of the geospatial free and open source community in the Quebec Province. As an employee of the Quebec Ministry of Public Security (MSP), he has contributed to the implementation of several innovative and effective geospatial systems based on free and open source technologies, such as G.O.LOC (http://geomsp.msp.gouv.qc.ca/portail_geo/goloc.htm) and SAG 911 (http://www.quebecgeographique.gouv.qc.ca/approfondir/bibliotheque/geoinfo/geoinfo-mars-2010.asp). He is to my mind one the person responsible for the successful transition initiated by the MSP for the use in its every day missions of geospatial free and open source technologies. Based on these successful initiatives, the geomatics department of the MSP acts now as a pioneer among the different public organisations in the adoption of open source technologies in the Quebec Province. In 2009, Simon has also been elected as a board member of the steering committee of the OSGeo Quebec local chapter. He has been one of the co-organisers of the 1st rendez-vous OSGeo-Quebec (http://rendez-vous-osgeo-qc.org/2010/) which have gathered about 100 attendees from different organisations and offered the Quebec community to meet and discuss with different members of the OSGeo international (see http://rendez-vous-osgeo-qc.org/2010/conferenciers/). Recently, Simon has joined Spatialytics (http://www.spatialytics.com), a new startup in Quebec city which at developing a commercial open source Geospatial BI (Business Intelligence) Suite.
|-
|Pedro-Juan Ferrer
|
* Pedro-Juan has been an active member of OSGeo-ES since the LC started. He has presented the OSGeo Foundation in several events doing a hard job on advocacy on free software blogging, at mailing lists, etc. He's doing a lot of work in other fronts like translations, documenting, advocacy, support at mailing lists and so on. Finally he is part of the Board of Directors of the Local Chapter and also the Liason Officer.
|-
| Miguel García Coya (Micho)
|
* Micho has been an active member of OSGeo-ES for more than two years and nowadays he is part of the Board of Directors of the Local Chapter. He is a FOSS4G expert and apart from working on GIS projects is also doing a hard job at OSGeo-es advocacy tasks. Now he's living at North Spain (Galicia) and he is promoting a microchapter with a recently succesful first meeting.
|-
| [[Anne Ghisla]]
|
* Anne is an active member of OSGeo and a FOSS evangelist. In 2008 she first participated in Google Summer of Code as a student She contributed the Home-range analyses in QGIS using R through Python and in 2009 she developed v.krige, a GUI for Kriging analysis for GRASS GIS. This summer (2010) she was a mentor in the Google Summer of Code program and helped the administration team by presenting GSoC at FOSS4G in Barcelona. Anne has also shown interest in helping out as an administrator for GSoC in 2011. She is also spearheading the still relatively fresh OSGeo Women Chapter, and is a member in the Web Committee. Anne also participates on the OSGeo IRC channels and mailing lists. She is very eager to be more involved with OSGeo!
|}
[[Category:Elections]]
[[Category:Election 2010]]

SAC Meeting 2010-06-07

2010-06-11T15:04:01Z

Wiki-Wolf: /* Minutes */

= SAC OSL Transition Meeting =

Tentatively planned for June 10th at 11am EST:
http://www.timeanddate.com/worldclock/fixedtime.html?year=2010&month=06&day=10&hour=15&min=0&sec=0

Place: #osgeo IRC channel on freenode.

== Supporting Documents ==
* [[Infrastructure Transition Plan 2010]]
* [[SAC Service Status]]

== Agenda ==

* Alex: Brief summary of the VM creation status at OSL.
** Created: Web,Secure,Wiki,QGIS,Webextra,Tracsvn,Backup
* Assign primary responsibility for transition of various key services (wiki, backup, mailman, trac/svn, ldap)
** Backup strategy - [[Infrastructure Transition Plan 2010#Questions_to_ask_OSL.2FOurselves |Staggered Backup times]], Sync to telescience?
* Refine timeline for migration.
* Refine role of the less obvious VMs like "webextra", and "projects".
* Discuss access control strategy (sac, telescience and qgis shell groups for instance)
* Discuss service documentation strategy
* Discuss how we interact with OSL, and how we get access "under the VMs".
** In the works, access to the host machines will be granted via ssh keys, the same keys used for root on the VMs.
* Support for SSL logins to our services.

== Minutes ==

Attending:FrankW, Wolf, CRSchmidt, nhv, strk, wildintellect, TylerM, Arnulf

Log: http://logs.qgis.org/osgeo/%23osgeo.2010-06-10.log

* Chris reported on current progress, notably with the trac/svn transition.
* Porting services off osgeo2:
** planet.osgeo.org: Chris, to webextra VM
** qgis.org: macho, otto, to qgis VM
** community.osgeo.org: Tyler needs to harvest some info to Web VM
** Plan to shutdown osgeo2 by end of June.
* webextra vs. projects:
** webextra is SAC administered "foundation" services, shell group "sac"
** wildintellect migrating live.osgeo.org to webextra.
** projects is user/project administered services, shell group "telescience".
** Project VM sized at 250GB disk, 8GB RAM, 4 CPUs: wildintellect to request creation from OSUOSL
** metadata, grass and mapbender services will be establish on Projects VM until a compelling reason is found to establish project specific VMs.
* osgeo1:
** Plan to shutdown osgeo1 no later than the end of September.
** Web VM will have all the Drupal sites (osgeo.org, fdo, mapguide) and the port will be done by Wolf, Tyler and (Anne Ghisla)aghisla
** Mail VM (mailman, postfix): FrankW for Mailman, someone yet to be named to do the email/postfix configuration.
** ldap.osgeo.org: Martin to migrate this to the secure VM.
* we expect bare iron access to the two physical servers in the next week or two from OSU OSL.

Drupal Upgrade Plan 2010

2010-05-14T21:15:54Z

Wiki-Wolf: updated server tasks

Previous upgrade notes: [[Drupal Upgrade Plan]]
* These notes are mostly just a copy of the previous upgrade, but are being modified still :)
------

Upgrading the OSGeo Drupal CMS is a complicated task further complicated by the use of multi-site configuration. To upgrade from current 5.3 ('''??''') to the newest 6.x ('''??''') version the following steps should be taken (doubles as a check list):

= Time estimation =
I estimate that the total read-only time for the OSGeo sites will be around 1 day if everything goes according to plan, this does not include the preliminary tasks which have to be completed prior to doing the upgrade.

= Preliminary tasks =
== DNS Changes ==
Redirect any *test* instances?

== Debian Package Installation ==
osgeo3/4 run debian linux OS. The server has no apache, drupal or any other packages already installed. Here is the list of packages to be installed to get support for our Drupal sites up and running:
* apache2

== Review Module Availability ==
* Which modules needed - check that all are available in 6.x
=== Current modules ===
...

== Theme upgrade ==
Wave a magic wand to complete this step.

== web.osgeo.org server tasks ==
# install packages
# setup webroot like this:
#* /var/www/drupal -> drupal-version
#* /var/www/site.osgeo.org (most of /var/www/drupal stuff symlinked here)
#* This way all sites have their own files directory for uploads and images)
# install drupal (old version)
# copy all sites over
# upgrade to Drupal 6 (more details later)

== osgeo2 server tasks ==
# download Drupal 4.7.8
# Download Drupal 5.3 and modules:
#* captcha
#* content (CCK)
#** date
#** imagefield
#** number (comes with CCK)
#** link (comes with CCK)
#** optionwidgets (comes with CCK)
#** text (comes with CCK)
#* diff
#* event
#** basicevent
#* feedback
#* image
#** image_gallery (part of image)
#* insert_block
#* LDAP Integration consists of:
#** ldapauth
#** ldapdata
#** ldapgroups
#* locale
#** localizer
#*** localizerblock
#*** localizermenu
#*** localizernode
#*** localizertaxonomy
#*** localizeruser
#*** localizerviews
#* path_image
#* pearwiki_filter
#* recent_changes
#* syndication
#* tinymce
#** imce
#* views
#** views_rss
#** views_theme_wizard
#** views_ui
#* webfm
# Build a new osgeo theme, visually the same as the old theme. Based on 5.3 bluemarine

'''These items still need doing'''

# create new directory structure
#* /var/www/drupal-5.3 (extracted from the tarball)
#* /var/www/drupal (symlnk to above)
#* /var/www/osgeo (symlink contents of drupal here)
#** /var/www/osgeo/files
#* /var/www/fdo (like osgeo)
#* /var/www/mapguide
#* /var/www/mapbender

= Actual Upgrade sequence =
== osgeo1 ==
# Make a Backup of all 4 Drupal databases and the files.
# Make all Drupal sites read-only by taking away write access
#* http://osgeo.org/
#* http://fdo.osgeo.org/
#* http://mapguide.osgeo.org/
#* http://mapbender.osgeo.org/

== osgeo2 ==
# Extract osgeo1 files to /var/www/drupal
# Create a new databases for the sites
#* drupal_osgeo
#* drupal_fdo
#* drupal_mapguide
#* drupal_mapbender
# Move old drupal test.osgeo.net to run on dev.osgeo.net
## Add dev.osgeo.conf to Apache
## Point osgeo.conf to /var/www/drupal
## Point fdo.conf to /var/www/drupal
## Point mapguide.conf to /var/www/drupal
## Point mapbender.conf to /var/www/drupal
# Upgrade Drupal to 4.7.8
## Untar drupal-4.7.8 to /var/www/drupal-4.7.8
## Log in as 'admin' to osgeo site
## Log in as 'admin' to fdo site
## Log in as 'admin' to mapguide site
## Log in as 'admin' to mapbender site
## Disable all non-core modules on osgeo (with mysql update) [see below]
## Disable all non-core modules on fdo (with mysql update) [see below]
## Disable all non-core modules on mapguide (with mysql update) [see below]
## Disable all non-core modules on mapbender (with mysql update) [see below]
## Switch to bluemarine theme (Drupal standard) on osgeo (with mysql update) [see below]
## Switch to bluemarine theme (Drupal standard) on fdo (with mysql update) [see below]
## Switch to bluemarine theme (Drupal standard) on mapguide (with mysql update) [see below]
## Switch to bluemarine theme (Drupal standard) on mapbender (with mysql update) [see below]
## <code>mv /var/www/drupal /var/www/drupal-old</code>
## <code>ln -s /var/www/drupal-4.7.8 /var/www/drupal</code>
## <code>rm -rf /var/www/drupal-4.7.8/sites</code>
## <code>mv /var/www/drupal-old/sites /var/www/drupal-4.7.8</code>
## point browser to test.drupal.org/update.php
## point browser to fdo-test.drupal.org/update.php
## point browser to mapguide-test.drupal.org/update.php
## point browser to mapbender-test.drupal.org/update.php
# Upgrade to 5.3
## log in as admin
## Untar drupal-5.3 to /var/www/drupal-5.3
## <code>ln -s /var/www/drupal-5.3 /var/www/drupal</code>
## <code>rm -rf /var/www/drupal-5.3/sites</code>
## <code>mv /var/www/drupal-4.7.8/sites /var/www/drupal-5.3</code>
## point browser to test.drupal.org/update.php
## point browser to fdo-test.drupal.org/update.php
## point browser to mapguide-test.drupal.org/update.php
## point browser to mapbender-test.drupal.org/update.php
# install missing modules
# enable required modules
# enable the osgeo theme on osgeo
# enable the osgeo theme on fdo
# enable the osgeo theme on mapguide
# enable the osgeo theme on mapbender
# dump databases and tar files and move the new site over to osgeo1

== osgeo1 ==
# load the new site files and databases
# edit apache config files to point to new sites.
#* www.drupal.org
## Point osgeo.conf to /var/www/drupal
## Point fdo.conf to /var/www/drupal
## Point mapguide.conf to /var/www/drupal
## Point mapbender.conf to /var/www/drupal

== dev.osgeo.conf ==
<pre>
<VirtualHost 66.223.95.243:80>
ServerName dev.osgeo.net
DocumentRoot /var/www/html
ErrorLog /var/log/httpd/osgeo-error_log
CustomLog /var/log/httpd/osgeo-access_log common
<Directory "/var/www/html">
Options Indexes FollowSymLinks
AllowOverride all
Order allow,deny
Allow from all
</Directory>
</VirtualHost>
</pre>

== edu.osgeo.conf ==
<pre>
<VirtualHost 66.223.95.243:80>
ServerName edu.osgeo.net
DocumentRoot /var/www/moodle
ErrorLog /var/log/httpd/osgeo-error_log
CustomLog /var/log/httpd/osgeo-access_log common
<Directory "/var/www/moodle">
Options Indexes FollowSymLinks
AllowOverride all
Order allow,deny
Allow from all
</Directory>
</VirtualHost>
</pre>

== fdo-test.osgeo.conf ==
<pre>
<VirtualHost 66.223.95.243:80>
ServerName fdo-test.osgeo.net
DocumentRoot /var/www/fdo
ErrorLog /var/log/httpd/osgeo-error_log
CustomLog /var/log/httpd/osgeo-access_log common
<Directory "/var/www/fdo">
Options Indexes FollowSymLinks
AllowOverride all
Order allow,deny
Allow from all
</Directory>
</VirtualHost>
</pre>

== mapbender.osgeo.conf ==
<pre>
<VirtualHost 66.223.95.243:80>
ServerName mapbender-test.osgeo.net
DocumentRoot /var/www/mapbender
ErrorLog /var/log/httpd/osgeo-error_log
CustomLog /var/log/httpd/osgeo-access_log common
<Directory "/var/www/mapbender">
Options Indexes FollowSymLinks
AllowOverride all
Order allow,deny
Allow from all
</Directory>
</VirtualHost>
</pre>

== mapguide.osgeo.conf ==
<pre>
<VirtualHost 66.223.95.243:80>
ServerName mapguide-test.osgeo.net
DocumentRoot /var/www/mapguide
ErrorLog /var/log/httpd/osgeo-error_log
CustomLog /var/log/httpd/osgeo-access_log common
<Directory "/var/www/mapguide">
Options Indexes FollowSymLinks
AllowOverride all
Order allow,deny
Allow from all
</Directory>
</VirtualHost>
</pre>

== SQL to disable all non-core modules ==
<pre>
alter table system set status=0 where where name != 'aggregator' and
name != 'block' and name != 'blog' and name != 'blogapi' and
name != 'book' and name != 'comment' and name != 'contact' and
name != 'drupal' and name != 'filter' and name != 'forum' and
name != 'help' and name != 'legacy' and name != 'locale' and
name != 'menu' and name != 'node' and name != 'path' and
name != 'ping' and name != 'poll' and name != 'profile' and
name != 'search' and name != 'statistics' and name != 'taxonomy' and
name != 'throttle' and name != 'tracker' and name != 'upload' and
name != 'user' and name != 'watchdog' and name != 'bluemarine';
</pre>

== SQL to set bluemarine as the default theme ==
<pre>
alter table variable set value='s:10:"bluemarine";' where name='theme_default';
delete from cache;
</pre>

[[Category:Web Site Committee]]

Google Summer of Code Application 2010

2010-04-06T16:00:25Z

Wiki-Wolf: /* Description (required) */ Fixed correctly

==Link ID==
osgeo

==Organization Name (required)==
OSGeo - Open Source Geospatial Foundation

==Description (required)==
OSGeo is a non-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and 19 (to 24) code projects in particular:

Web Mapping: '''deegree''', '''GeoServer''', '''Mapbender''', '''MapBuilder''', '''MapFish''', '''MapGuide Open Source''', '''MapServer''', '''OpenLayers'''

Desktop Applications: '''GRASS GIS''', '''OSSIM''', '''Quantum GIS''', '''gvSIG'''

Geospatial Libraries: '''FDO''', '''GDAL/OGR''', '''GEOS''', '''GeoTools''', '''MetaCRS''', '''PostGIS'''
: ''The following are sub-projects of MetaCRS'':
:* '''CS-Map''', '''GeoTIFF/libgeotiff''', '''PROJ.4''', '''Proj4J''', '''Proj4js''', '''SpatialReference.org'''

Metadata Catalog: '''GeoNetwork'''

Other (non-code) Projects: '''Public Geospatial Data''', '''Education and Curriculum'''

==Home Page (required)==
http://www.osgeo.org/

==What license does your organization use? (required)==

Each member project uses their own, but all OSGeo projects are required to use an OSI approved license. (see http://www.osgeo.org/incubator/process/evaluation.html)

* Member projects specifically use: GPL >=2, LGPL, MIT/X, ...

GSoC program requires an OSI approved license, but the dropdown only lets you select one. We go with GPL 2 since it seems to be the one most commonly used.

==Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating? (required)==

We hope to get more students excited about open source geospatial development. This will help to grow the development community and of course tangibly advance particular projects. Additionally by way of the level of exposure that SoC provides we aim to further extend the use, development, and teaching & training of open source GIS at universities worldwide. This will help to prepare a new generation of developers for industry and government agencies capable of introducing and implementing viable open source geospatial technology, to the benefit of all.

Last but not least we hope to use this opportunity to bring more open source geospatial projects closer and to communicate more. We are encouraging students to come up with ideas that cross project boundaries, and to find new ways to connect the separate efforts in order to bring out new and perhaps improved wholes. In 2008 we also saw the birth of a new project, Spatialytics, which is a novel combination of several geospatial technologies. This is, as stated above, one of our goals, which SGoC helps us achieve in a way which cannot be matched in any other regular effort.

==Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.==

OSGeo participated in GSoC in 2009. Twelve OSGeo member projects participated and were very successful. The applications were of better quality so we had fewer dropouts than the previous year. We also had further cross-project co-operation projects, which went very well indeed. OSGeo Sent two delegates to the Mentor Summit.

OSGeo participated in GSoC in 2008. Eleven OSGeo member projects participated and were in general very successful. OSGeo didn't send delegates to the Mentor Summit due to the busy schedules of the mentors.

See http://wiki.osgeo.org/wiki/SoC_Report_2008 for a full report.

OSGeo participated in GSoC in 2007. Six OSGeo projects participated and were generally very successful. OSGeo also sent one delegate to the Mentor Summit in 2007. See http://wiki.osgeo.org/wiki/SoC_Report_2007 for a full report. We also opened up a demo theatre track highlighting SoC work at our [http://www.foss4g2007.org/ foss4g] conference that year.

OSGeo was formed in early 2006 and did not participate in GSoC prior to 2007. However, Refractions Research did participate in 2006 on behalf of the GeoTools, uDig, and PostGIS projects which now participate through OSGeo. Most of the the previously participating mentors and administrators continue to be involved in this years OSGeo GSoC effort.

==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.==
2007: 13/19

2008: 15/19

2009: 17/20

==Add a Comment (optional):==
As the numbers indicate each year we have received better and better applications, and thus have had a better success ratio. Also we have learned to mentor better, and to spot the good applications.

==What is the URL for your ideas page? (required)==
http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2010_Ideas

==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. (required)==
soc@lists.osgeo.org - For questions about applying and other GSoC questions

See http://wiki.osgeo.org/wiki/Mailing_Lists for a full list and descriptions of the OSGeo project mailing lists.

==What is the main IRC channel for your organization? (required)==

The primary OSGeo channel is #osgeo on the irc.freenode.net network.

==Add a Comment (optional)==
member projects maintain their own IRC channels:
: http://wiki.osgeo.org/wiki/IRC

==Does your organization have an application template you would like to see students use? (required)==
'''Name:'''

'''Country:'''

'''School and degree:'''

'''Email:'''

'''Phone:'''

'''OSGeo project(s):'''

'''Title:'''

'''Describe your idea'''
# Introduction
# Background
# The idea
# Project plan (how do you plan to spend your summer?)
# Future ideas / How can your idea be expanded?

'''Explain how your SoC task would benefit the OSGeo member project and more generally the OSGeo Foundation as a whole:'''

'''Please provide details of previous GIS experience:'''

'''Please provide details of any previous involvement with GIS programming and other software programming:'''

'''Please provide details of general computing experience: (operating systems you use on a day-to-day basis, languages you could write a program in, hardware, networking experience, etc.)'''

'''Please tell us why you are interested in GIS and open source software:'''

'''Please tell us why you are interested in your specific coding project:'''

'''Please tell us why you are interested in working for OSGeo and the software project you have selected:'''

'''Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?'''

==What criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible==
The project administrator is appointed by the OSGeo board at the beginning of the year. The project administrator asks for one or two people he trusts to be the backup administrators. Mentors are selected by project steering committees and development teams based on their reputation as skilled developers, domain experience, previously demonstrated ability to support new project developers, and stated willingness to devote time to the mentoring process. We also try very hard to match up the student working on a specific module or tool with a developer with the best expertise in the relevant area. We have in the past not voted up an otherwise good student project if there was no mentor capable of overseeing the project from a technical standpoint. Fortunately we have had a strong response from the developer pool so this has not been a major problem.

==What is your plan for dealing with disappearing students? (required)==
In order to minimize the chance of disappearing students we will ensure that the OSGeo administrative contact and the mentors have full contact information (email, home phone, etc) so that we can keep in touch with them at all times. We also stress to our students that this is a Job, as opposed to a school project.

In addition, we will make our reporting requirements clear up front. Letting the students know that we will require a weekly progress report to be posted to OSGeo's SoC mailing list (cc the member project's development mailing list), participation in public IRC channels and project mailing lists will all help ensure ongoing commitment to the work. Mentors are required to make sure that happens and that the lines of communication are kept open from beginning to end.

Other possibilities include:
# Having potential students work with their potential mentor to prepare a plan for the implementation of their project.
# Setting milestones that need to be reached by the student. These milestones would be defined before the student's work begins. A student would subsequently write a brief e-mail informing the OSGeo SoC mailing list (cc project-specific mailing list) when they have reached each milestone, giving a brief description of the work completed to that date. This is in addition to the weekly progress reports which are intended to be more casual and actively soliciting feedback.
# Selecting students that have shown previous interest in the geospatial field and free software. A student who already has a (reviewable) FOSS track record has a much higher chance of success.

==What is your plan for dealing with disappearing mentors? (required)==

Project steering committees will appoint replacement mentors if existing mentors become unavailable or unresponsive during the project period. We also plan to have backup mentors for projects so the backup mentor can fill in for, or replace the primary mentor in case of changing circumstances. Our administrators take an active role communicating with students and mentors, and so will be able to help out early if there is a problem somewhere.

Among all the OSGeo mailing lists there are 14,000 subscribers, indicating a good pool of people to draw from if required. Due to relatively high member project code and personnel cross-over, in a pinch a mentor from another OSGeo project could usefully help out.

==What steps will you take to encourage students to interact with your community before, during, and after the program? (required)==

The steps taken depend on the individual projects. As an example, last year we required weekly reports and encouraged the students to interact with us on the project mailing lists and IRC channels. We also encourage the developers and users who are not mentors to provide additional advice and feedback to the participating student and help with testing the students contributions during and after the program. In general other developers have not been shy about sharing their opinions, guidance, and advice on the member project development lists.

Furthermore the mentors are encouraged to actively involve the students in the community by having the student interact with the mentor through the community (public) channels rather then one-on-one. This also assists with student integration into the project and alleviates the disappearing-mentor problem.

==What will you do to ensure that your accepted students stick with the project after GSoC concludes? (required)==
The steps taken depend on the individual projects, as example last year many projects asked that students act as a "module maintainer" for their work. This role has an expected level of support associated with it.

Apart from that, we are relying on the open development process and the appreciation that students will receive for implementing these needed features to provide positive feedback for the students. The projects will be encouraging the students to take ownership of their work, and to contribute in other areas they may be interested in. In some cases students may also have opportunities for future contract work if they make a good impression on community members.

==Is there anything else you would like to tell the Google Summer of Code program administration team? (required)==
Thank you for your great work and the great chance to spread Open Source GIS.

==Please select your backup group administrator.==

Backup administrators:
* Hamish Bowman (melange: hamish)
* Landon Blake (melange: sunburned_surveyor)

[[Category: Google Summer of Code]]

Google Summer of Code Application 2010

2010-04-06T15:55:24Z

Wiki-Wolf: /* Description (required) */ non-profit as per Arnulf's instructions

==Link ID==
osgeo

==Organization Name (required)==
OSGeo - Open Source Geospatial Foundation

==Description (required)==
OSGeo is an incorporated non-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and 19 (to 24) code projects in particular:

Web Mapping: '''deegree''', '''GeoServer''', '''Mapbender''', '''MapBuilder''', '''MapFish''', '''MapGuide Open Source''', '''MapServer''', '''OpenLayers'''

Desktop Applications: '''GRASS GIS''', '''OSSIM''', '''Quantum GIS''', '''gvSIG'''

Geospatial Libraries: '''FDO''', '''GDAL/OGR''', '''GEOS''', '''GeoTools''', '''MetaCRS''', '''PostGIS'''
: ''The following are sub-projects of MetaCRS'':
:* '''CS-Map''', '''GeoTIFF/libgeotiff''', '''PROJ.4''', '''Proj4J''', '''Proj4js''', '''SpatialReference.org'''

Metadata Catalog: '''GeoNetwork'''

Other (non-code) Projects: '''Public Geospatial Data''', '''Education and Curriculum'''

==Home Page (required)==
http://www.osgeo.org/

==What license does your organization use? (required)==

Each member project uses their own, but all OSGeo projects are required to use an OSI approved license. (see http://www.osgeo.org/incubator/process/evaluation.html)

* Member projects specifically use: GPL >=2, LGPL, MIT/X, ...

GSoC program requires an OSI approved license, but the dropdown only lets you select one. We go with GPL 2 since it seems to be the one most commonly used.

==Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating? (required)==

We hope to get more students excited about open source geospatial development. This will help to grow the development community and of course tangibly advance particular projects. Additionally by way of the level of exposure that SoC provides we aim to further extend the use, development, and teaching & training of open source GIS at universities worldwide. This will help to prepare a new generation of developers for industry and government agencies capable of introducing and implementing viable open source geospatial technology, to the benefit of all.

Last but not least we hope to use this opportunity to bring more open source geospatial projects closer and to communicate more. We are encouraging students to come up with ideas that cross project boundaries, and to find new ways to connect the separate efforts in order to bring out new and perhaps improved wholes. In 2008 we also saw the birth of a new project, Spatialytics, which is a novel combination of several geospatial technologies. This is, as stated above, one of our goals, which SGoC helps us achieve in a way which cannot be matched in any other regular effort.

==Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.==

OSGeo participated in GSoC in 2009. Twelve OSGeo member projects participated and were very successful. The applications were of better quality so we had fewer dropouts than the previous year. We also had further cross-project co-operation projects, which went very well indeed. OSGeo Sent two delegates to the Mentor Summit.

OSGeo participated in GSoC in 2008. Eleven OSGeo member projects participated and were in general very successful. OSGeo didn't send delegates to the Mentor Summit due to the busy schedules of the mentors.

See http://wiki.osgeo.org/wiki/SoC_Report_2008 for a full report.

OSGeo participated in GSoC in 2007. Six OSGeo projects participated and were generally very successful. OSGeo also sent one delegate to the Mentor Summit in 2007. See http://wiki.osgeo.org/wiki/SoC_Report_2007 for a full report. We also opened up a demo theatre track highlighting SoC work at our [http://www.foss4g2007.org/ foss4g] conference that year.

OSGeo was formed in early 2006 and did not participate in GSoC prior to 2007. However, Refractions Research did participate in 2006 on behalf of the GeoTools, uDig, and PostGIS projects which now participate through OSGeo. Most of the the previously participating mentors and administrators continue to be involved in this years OSGeo GSoC effort.

==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.==
2007: 13/19

2008: 15/19

2009: 17/20

==Add a Comment (optional):==
As the numbers indicate each year we have received better and better applications, and thus have had a better success ratio. Also we have learned to mentor better, and to spot the good applications.

==What is the URL for your ideas page? (required)==
http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2010_Ideas

==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. (required)==
soc@lists.osgeo.org - For questions about applying and other GSoC questions

See http://wiki.osgeo.org/wiki/Mailing_Lists for a full list and descriptions of the OSGeo project mailing lists.

==What is the main IRC channel for your organization? (required)==

The primary OSGeo channel is #osgeo on the irc.freenode.net network.

==Add a Comment (optional)==
member projects maintain their own IRC channels:
: http://wiki.osgeo.org/wiki/IRC

==Does your organization have an application template you would like to see students use? (required)==
'''Name:'''

'''Country:'''

'''School and degree:'''

'''Email:'''

'''Phone:'''

'''OSGeo project(s):'''

'''Title:'''

'''Describe your idea'''
# Introduction
# Background
# The idea
# Project plan (how do you plan to spend your summer?)
# Future ideas / How can your idea be expanded?

'''Explain how your SoC task would benefit the OSGeo member project and more generally the OSGeo Foundation as a whole:'''

'''Please provide details of previous GIS experience:'''

'''Please provide details of any previous involvement with GIS programming and other software programming:'''

'''Please provide details of general computing experience: (operating systems you use on a day-to-day basis, languages you could write a program in, hardware, networking experience, etc.)'''

'''Please tell us why you are interested in GIS and open source software:'''

'''Please tell us why you are interested in your specific coding project:'''

'''Please tell us why you are interested in working for OSGeo and the software project you have selected:'''

'''Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?'''

==What criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible==
The project administrator is appointed by the OSGeo board at the beginning of the year. The project administrator asks for one or two people he trusts to be the backup administrators. Mentors are selected by project steering committees and development teams based on their reputation as skilled developers, domain experience, previously demonstrated ability to support new project developers, and stated willingness to devote time to the mentoring process. We also try very hard to match up the student working on a specific module or tool with a developer with the best expertise in the relevant area. We have in the past not voted up an otherwise good student project if there was no mentor capable of overseeing the project from a technical standpoint. Fortunately we have had a strong response from the developer pool so this has not been a major problem.

==What is your plan for dealing with disappearing students? (required)==
In order to minimize the chance of disappearing students we will ensure that the OSGeo administrative contact and the mentors have full contact information (email, home phone, etc) so that we can keep in touch with them at all times. We also stress to our students that this is a Job, as opposed to a school project.

In addition, we will make our reporting requirements clear up front. Letting the students know that we will require a weekly progress report to be posted to OSGeo's SoC mailing list (cc the member project's development mailing list), participation in public IRC channels and project mailing lists will all help ensure ongoing commitment to the work. Mentors are required to make sure that happens and that the lines of communication are kept open from beginning to end.

Other possibilities include:
# Having potential students work with their potential mentor to prepare a plan for the implementation of their project.
# Setting milestones that need to be reached by the student. These milestones would be defined before the student's work begins. A student would subsequently write a brief e-mail informing the OSGeo SoC mailing list (cc project-specific mailing list) when they have reached each milestone, giving a brief description of the work completed to that date. This is in addition to the weekly progress reports which are intended to be more casual and actively soliciting feedback.
# Selecting students that have shown previous interest in the geospatial field and free software. A student who already has a (reviewable) FOSS track record has a much higher chance of success.

==What is your plan for dealing with disappearing mentors? (required)==

Project steering committees will appoint replacement mentors if existing mentors become unavailable or unresponsive during the project period. We also plan to have backup mentors for projects so the backup mentor can fill in for, or replace the primary mentor in case of changing circumstances. Our administrators take an active role communicating with students and mentors, and so will be able to help out early if there is a problem somewhere.

Among all the OSGeo mailing lists there are 14,000 subscribers, indicating a good pool of people to draw from if required. Due to relatively high member project code and personnel cross-over, in a pinch a mentor from another OSGeo project could usefully help out.

==What steps will you take to encourage students to interact with your community before, during, and after the program? (required)==

The steps taken depend on the individual projects. As an example, last year we required weekly reports and encouraged the students to interact with us on the project mailing lists and IRC channels. We also encourage the developers and users who are not mentors to provide additional advice and feedback to the participating student and help with testing the students contributions during and after the program. In general other developers have not been shy about sharing their opinions, guidance, and advice on the member project development lists.

Furthermore the mentors are encouraged to actively involve the students in the community by having the student interact with the mentor through the community (public) channels rather then one-on-one. This also assists with student integration into the project and alleviates the disappearing-mentor problem.

==What will you do to ensure that your accepted students stick with the project after GSoC concludes? (required)==
The steps taken depend on the individual projects, as example last year many projects asked that students act as a "module maintainer" for their work. This role has an expected level of support associated with it.

Apart from that, we are relying on the open development process and the appreciation that students will receive for implementing these needed features to provide positive feedback for the students. The projects will be encouraging the students to take ownership of their work, and to contribute in other areas they may be interested in. In some cases students may also have opportunities for future contract work if they make a good impression on community members.

==Is there anything else you would like to tell the Google Summer of Code program administration team? (required)==
Thank you for your great work and the great chance to spread Open Source GIS.

==Please select your backup group administrator.==

Backup administrators:
* Hamish Bowman (melange: hamish)
* Landon Blake (melange: sunburned_surveyor)

[[Category: Google Summer of Code]]

Google Summer of Code 2010 Ideas

2010-04-03T15:09:57Z

Wiki-Wolf: /* How does your SoC task would benefit the OSGeo member project, and more generally the OSGeo Foundation as a whole? */

[[Image:Google_soc_2010_logo.jpg|center|250px]]

* Back to the main OSGeo [[Google Summer of Code 2010]] wiki page.

=OSGeo Google Summer of Code 2010=

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 [http://code.google.com/p/google-summer-of-code/wiki/GsocFlyers 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 posted to the soc@osgeo mailing list that at least answers the following questions:
# What did you get done this week?
# What do you plan on doing next week?
# Are you blocked on anything?
These questions BTW are the same as are used in real-work, when developing with the
[http://en.wikipedia.org/wiki/Scrum_(development) Scrum] [http://en.wikipedia.org/wiki/Agile_software_development development process]. ;)

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 and blogs==
In addition to weekly reports we ask you to maintain a wiki or blog 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.

Wiki and/or blog space can and will be provided by OSGeo if your project doesn't have anything already set up for this.

=Timeline=
http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/timeline

* March 18th 2010: Google announces accepted organizations. If OSGeo is accepted as an organization for Google Summer of Code, start talking to us earlier rather than later.
* April 9th 2010: Student application deadline. The earlier you start the more probable it is that you will be accepted! There is two way feedback during the application process which really helps you improve and clarify your application before this final deadline.
* April 26th 2010: Accepted student proposals are announced.
* May 24th 2010: Coding begins!
* July 12-16th: Mid-term evaluation.
* August 9th: Pencils down!

= The ideas pages =
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:

* [http://trac.osgeo.org/gdal/wiki/SummerOfCode 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.
* [http://grass.osgeo.org/wiki/GRASS_SoC_Ideas 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!
* [http://www.mapbender.org/GSoC_2010 Mapbender SoC ideas 2010]: Mapbender is a server and client side geographic data management tool, programmed in '''PHP''' and '''JavaScript''', using the '''jQuery''' library.
* [http://www.qgis.org/wiki/Google_Summer_of_Code_2010 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.
* [http://udig.refractions.net/confluence/display/HACK/Summer+of+Code uDig Summer of Code]: 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.
* [http://sourceforge.net/apps/mediawiki/jump-pilot/index.php?title=OpenJUMP_Google_Summer_Of_Code 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.
* [http://wiki.osgeo.org/wiki/OpenRouter_2010_SOC_Ideas OpenRouter 2010 SOC Ideas]: OpenRouter is a couple of projects that are building routing and driving direction libraries and applications that can be integrated with other applications.
* OSSIM [http://web.me.com/epiesasha/PlanetSasha/2010Project.html Py-OSSIM]: - ossim-swig-python to generate code to call ossim from python
* [[OSGeo_Cartographic_Engine#Ideas_for_Summer_of_Code_2010_Project | Cartographic Engine project ideas built on Mapnik]]: Refining much needed high quality hardcopy output tools that encourage collaboration. Built on Mapnik, applications like QGIS, GRASS, MapServer, etc. can output using these features. Focused initially on building specs that support Mapnik as the engine, but that could be applied generally across OSGeo projects as well.
* [http://www.spatialytics.org/google-summer-of-code-2010-ideas/ Spatialytics.org GSoC 2010 Ideas]: Spatialytics.org is the new home of the three open source Geospatial BI projects (GeoKettle, GeoMondrian and SOLAPLayers). Geospatial Business Intelligence (BI) tools, such as spatial ETL (Extract, Transform and Load), geo-analytical dashboards and Spatial On-Line Analytical Processing (SOLAP) allow decision-makers to rapidly analyze large amount of data at different levels of time, geography and detail in order to make better decisions.
* [http://www.mapwindow.org/wiki/index.php/Google_Summer_of_Code MapWindow GIS SoC Ideas]: MapWindow is a free, extensible, geographic information system (GIS) that can be used as an alternative desktop GIS, to distribute data to others, to develop and distribute custom spatial data analyses, written in .NET (C++, C#, VB.NET). If you're a talented VB.Net, C#, or C++ programmer, you could be the perfect fit to work on this project. We have a couple of ideas that could be done over the summer; feel free to suggest your own ideas or plug-ins as well.
* [[MapServer_2010_SOC_Ideas | MapServer GSoC Ideas]]: MapServer is a Web Mapping Engine; an Open Source platform for publishing spatial data and interactive mapping applications to the web.
* [[Live_GIS_Disc_GSoC_2010 | OSGeo Live]] is a stack of 35+ of the best GeoSpatial Open Source packages bundled as a LiveDVD and Virtual Machine on top an Xubuntu linux ditribution. There are opportunities to address packaging and cross project quality control through application of systematic testing processes. Through this project, developers will gain a broad understanding of the full GeoSpatial Open Source stack.
* [[gvSIG GSoC 2010 Ideas|gvSIG]] is the free GIS project developed by the Regional Department of Infrastructures and Transport of the Valencian Government (Spain). gvSIG is at this time a group of software developments for [http://www.gvsig.org/web/projects/gvsig-desktop/description2/view?set_language=en Desktop],[http://www.gvsig.org/web/projects/gvsig-mobile/description-2/view?set_language=en PDAs] and [http://gvsigmini.org mobile phones].

=Application Template=
==Contact Information==
* '''Name:'''
* '''Country:'''
* '''School and degree:'''
* '''Email:'''
* '''Phone:'''
* '''OSGeo project(s):'''

==Application==
===Title===
===Introduction===
A summary of your idea. About 300 words is a suitable length
===Background===
Describe how your project relates to your project and OSGeo. Also describe how you came to think of the idea.
===The idea===
Describe your detail in as much detail as you can. Explain what algorithms you intend to use/study (if any). Also describe the business benefit, that is how your idea improves the program it is intended for. Who is your intended target audience (end users?, administrators?, developers?)
===Project plan===
How do you plan to spend your summer? Please include a preliminary week-by-week plan on how you think you can fulfill your project in the time allocated.
===Future ideas / How can your idea be expanded?===
Describe how your idea can be improved and extended, and what the benefits of this extension would be. Perhaps your idea can be used in some other project, or for something else?

==Answer the following questions briefly (about 300 words max)==
===How does your SoC task benefit the OSGeo member project, and more generally the OSGeo Foundation as a whole?===

===Please provide details of previous GIS experience===

===Do you have any previous GIS programming and other software programming experience?===
If you do explain what and when.

===Please provide details of general computing experience===
We are looking for things like operating systems you use on a day-to-day basis, programming languages you could write a program in, hardware, networking experience, etc.

===Please tell us why you are interested in GIS and open source software===

===Please tell us why you are interested in your specific coding project===

===Please tell us why you are interested in working for OSGeo and the software project(s) you have selected===

===Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?===

= 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 for project specific lists.

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

irc://irc.freenode.net/#osgeo (Web based [http://irc.telascience.org/cgi-bin/irc.cgi IRC client], [http://webchat.freenode.net alternative)

Project irc channels:

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

[[Category:Google Summer of Code]]

Google Summer of Code 2010 Ideas

2010-03-22T17:21:09Z

Wiki-Wolf: /* The ideas pages */

[[Image:Google_soc_2010_logo.jpg|center|250px]]

* Back to the main OSGeo [[Google Summer of Code 2010]] wiki page.

=OSGeo Google Summer of Code 2010=

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 [http://code.google.com/p/google-summer-of-code/wiki/GsocFlyers 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 posted to the soc@osgeo mailing list that at least answers the following questions:
# What did you get done this week?
# What do you plan on doing next week?
# Are you blocked on anything?
These questions BTW are the same as are used in real-work, when developing with the
[http://en.wikipedia.org/wiki/Scrum_(development) Scrum] [http://en.wikipedia.org/wiki/Agile_software_development development process]. ;)

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 and blogs==
In addition to weekly reports we ask you to maintain a wiki or blog 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.

Wiki and/or blog space can and will be provided by OSGeo if your project doesn't have anything already set up for this.

=Timeline=
http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/timeline

* March 18th 2010: Google announces accepted organizations. If OSGeo is accepted as an organization for Google Summer of Code, start talking to us earlier rather than later.
* April 9th 2010: Student application deadline. The earlier you start the more probable it is that you will be accepted! There is two way feedback during the application process which really helps you improve and clarify your application before this final deadline.
* April 26th 2010: Accepted student proposals are announced.
* May 24th 2010: Coding begins!
* July 12-16th: Mid-term evaluation.
* August 9th: Pencils down!

= The ideas pages =
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:

* [http://trac.osgeo.org/gdal/wiki/SummerOfCode 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.
* [http://grass.osgeo.org/wiki/GRASS_SoC_Ideas 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!
* [http://www.mapbender.org/GSoC_2010 Mapbender SoC ideas 2010]: Mapbender is a server and client side geographic data management tool, programmed in '''PHP''' and '''JavaScript''', using the '''jQuery''' library.
* [http://www.qgis.org/wiki/Google_Summer_of_Code_2010 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.
* [http://udig.refractions.net/confluence/display/HACK/Summer+of+Code 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.
* [http://sourceforge.net/apps/mediawiki/jump-pilot/index.php?title=OpenJUMP_Google_Summer_Of_Code 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.
* [http://wiki.osgeo.org/wiki/OpenRouter_2010_SOC_Ideas OpenRouter 2010 SOC Ideas]: OpenRouter is a couple of projects that are building routing and driving direction libraries and applications that can be integrated with other applications.
* OSSIM [http://web.me.com/epiesasha/PlanetSasha/2010Project.html Py-OSSIM]: - ossim-swig-python to generate code to call ossim from python
* [[OSGeo_Cartographic_Engine#Ideas_for_Summer_of_Code_2010_Project | Cartographic Engine project ideas built on Mapnik]]: Refining much needed high quality hardcopy output tools that encourage collaboration. Built on Mapnik, applications like QGIS, GRASS, MapServer, etc. can output using these features. Focused initially on building specs that support Mapnik as the engine, but that could be applied generally across OSGeo projects as well.
* [http://www.spatialytics.org/google-summer-of-code-2010-ideas/ Spatialytics.org GSoC 2010 Ideas]: Spatialytics.org is the new home of the three open source Geospatial BI projects (GeoKettle, GeoMondrian and SOLAPLayers). Geospatial Business Intelligence (BI) tools, such as spatial ETL (Extract, Transform and Load), geo-analytical dashboards and Spatial On-Line Analytical Processing (SOLAP) allow decision-makers to rapidly analyze large amount of data at different levels of time, geography and detail in order to make better decisions.
* [http://www.mapwindow.org/wiki/index.php/Google_Summer_of_Code MapWindow GIS SoC Ideas]: MapWindow is a free, extensible, geographic information system (GIS) that can be used as an alternative desktop GIS, to distribute data to others, to develop and distribute custom spatial data analyses, written in .NET (C++, C#, VB.NET). If you're a talented VB.Net, C#, or C++ programmer, you could be the perfect fit to work on this project. We have a couple of ideas that could be done over the summer; feel free to suggest your own ideas or plug-ins as well.
* [[MapServer_2010_SOC_Ideas | MapServer GSoC Ideas]]: MapServer is a Web Mapping Engine; an Open Source platform for publishing spatial data and interactive mapping applications to the web.

=Application Template=
==Contact Information==
* '''Name:'''
* '''Country:'''
* '''School and degree:'''
* '''Email:'''
* '''Phone:'''
* '''OSGeo project(s):'''

==Application==
===Title===
===Introduction===
A summary of your idea. About 300 words is a suitable length
===Background===
Describe how your project relates to your project and OSGeo. Also describe how you came to think of the idea.
===The idea===
Describe your detail in as much detail as you can. Explain what algorithms you intend to use/study (if any). Also describe the business benefit, that is how your idea improves the program it is intended for. Who is your intended target audience (end users?, administrators?, developers?)
===Project plan===
How do you plan to spend your summer? Please include a preliminary week-by-week plan on how you think you can fulfill your project in the time allocated.
===Future ideas / How can your idea be expanded?===
Describe how your idea can be improved and extended, and what the benefits of this extension would be. Perhaps your idea can be used in some other project, or for something else?

==Answer the following questions briefly (about 300 words max)==
===How does your SoC task would benefit the OSGeo member project, and more generally the OSGeo Foundation as a whole?===

===Please provide details of previous GIS experience===

===Do you have any previous GIS programming and other software programming experience?===
If you do explain what and when.

===Please provide details of general computing experience===
We are looking for things like operating systems you use on a day-to-day basis, programming languages you could write a program in, hardware, networking experience, etc.

===Please tell us why you are interested in GIS and open source software===

===Please tell us why you are interested in your specific coding project===

===Please tell us why you are interested in working for OSGeo and the software project(s) you have selected===

===Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?===

= 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 for project specific lists.

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

irc://irc.freenode.net/#osgeo (Web based [http://irc.telascience.org/cgi-bin/irc.cgi IRC client])

Project irc channels:

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

[[Category:Google Summer of Code]]

Google Summer of Code 2010 Ideas

2010-03-22T16:42:55Z

Wiki-Wolf: /* What to expect during the summer? */

[[Image:Google_soc_2010_logo.jpg|center|250px]]

* Back to the main OSGeo [[Google Summer of Code 2010]] wiki page.

=OSGeo Google Summer of Code 2010=

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 [http://code.google.com/p/google-summer-of-code/wiki/GsocFlyers 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 posted to the soc@osgeo mailing list that at least answers the following questions:
# What did you get done this week?
# What do you plan on doing next week?
# Are you blocked on anything?
These questions BTW are the same as are used in real-work, when developing with the
[http://en.wikipedia.org/wiki/Scrum_(development) Scrum] [http://en.wikipedia.org/wiki/Agile_software_development development process]. ;)

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 and blogs==
In addition to weekly reports we ask you to maintain a wiki or blog 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.

Wiki and/or blog space can and will be provided by OSGeo if your project doesn't have anything already set up for this.

=Timeline=
http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/timeline

* March 18th 2010: Google announces accepted organizations. If OSGeo is accepted as an organization for Google Summer of Code, start talking to us earlier rather than later.
* April 9th 2010: Student application deadline. The earlier you start the more probable it is that you will be accepted! There is two way feedback during the application process which really helps you improve and clarify your application before this final deadline.
* April 26th 2010: Accepted student proposals are announced.
* May 24th 2010: Coding begins!
* July 12-16th: Mid-term evaluation.
* August 9th: Pencils down!

= The ideas pages =
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:

* [http://trac.osgeo.org/gdal/wiki/SummerOfCode 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.
* [http://grass.osgeo.org/wiki/GRASS_SoC_Ideas 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!
* [http://www.mapbender.org/GSoC_2010 Mapbender SoC ideas 2010]: Mapbender is a server and client side geographic data management tool, programmed in '''PHP''' and '''JavaScript''', using the '''jQuery''' library.
* [http://www.qgis.org/wiki/Google_Summer_of_Code_2010 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.
* [http://udig.refractions.net/confluence/display/HACK/Summer+of+Code 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.
* [http://sourceforge.net/apps/mediawiki/jump-pilot/index.php?title=OpenJUMP_Google_Summer_Of_Code 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.
* [http://wiki.osgeo.org/wiki/OpenRouter_2010_SOC_Ideas OpenRouter 2010 SOC Ideas]: OpenRouter is a couple of projects that are building routing and driving direction libraries and applications that can be integrated with other applications.
* OSSIM [http://web.me.com/epiesasha/PlanetSasha/2010Project.html Py-OSSIM]: - ossim-swig-python to generate code to call ossim from python
* [[OSGeo_Cartographic_Engine#Ideas_for_Summer_of_Code_2010_Project | Cartographic Engine project ideas built on Mapnik]]: Refining much needed high quality hardcopy output tools that encourage collaboration. Built on Mapnik, applications like QGIS, GRASS, MapServer, etc. can output using these features. Focused initially on building specs that support Mapnik as the engine, but that could be applied generally across OSGeo projects as well.
* [http://www.spatialytics.org/google-summer-of-code-2010-ideas/ Spatialytics.org GSoC 2010 Ideas]: Spatialytics.org is the new home of the three open source Geospatial BI projects (GeoKettle, GeoMondrian and SOLAPLayers). Geospatial Business Intelligence (BI) tools, such as spatial ETL (Extract, Transform and Load), geo-analytical dashboards and Spatial On-Line Analytical Processing (SOLAP) allow decision-makers to rapidly analyze large amount of data at different levels of time, geography and detail in order to make better decisions.
* [http://www.mapwindow.org/wiki/index.php/Google_Summer_of_Code MapWindow GIS SoC Ideas]: MapWindow is a free, extensible, geographic information system (GIS) that can be used as an alternative desktop GIS, to distribute data to others, to develop and distribute custom spatial data analyses, written in .NET (C++, C#, VB.NET). If you're a talented VB.Net, C#, or C++ programmer, you could be the perfect fit to work on this project. We have a couple of ideas that could be done over the summer; feel free to suggest your own ideas or plug-ins as well.
* [[MapServer_2010_SOC_Ideas | MapServer GSoC Ideas]]: MapServer is a Web Mapping Engine; an Open Source platform for publishing spatial data and interactive mapping applications to the web.

= 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 for project specific lists.

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

irc://irc.freenode.net/#osgeo (Web based [http://irc.telascience.org/cgi-bin/irc.cgi IRC client])

Project irc channels:

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

[[Category:Google Summer of Code]]

Google Summer of Code Application 2010

2010-03-19T05:54:02Z

Wiki-Wolf: /* Please select your backup group administrator. */

==Link ID==
osgeo

==Organization Name (required)==
OSGeo - Open Source Geospatial Foundation

==Description (required)==
OSGeo is an incorporated not-for-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and 19 (to 24) code projects in particular:

Web Mapping: '''deegree''', '''GeoServer''', '''Mapbender''', '''MapBuilder''', '''MapFish''', '''MapGuide Open Source''', '''MapServer''', '''OpenLayers'''

Desktop Applications: '''GRASS GIS''', '''OSSIM''', '''Quantum GIS''', '''gvSIG'''

Geospatial Libraries: '''FDO''', '''GDAL/OGR''', '''GEOS''', '''GeoTools''', '''MetaCRS''', '''PostGIS'''
: ''The following are sub-projects of MetaCRS'':
:* '''CS-Map''', '''GeoTIFF/libgeotiff''', '''PROJ.4''', '''Proj4J''', '''Proj4js''', '''SpatialReference.org'''

Metadata Catalog: '''GeoNetwork'''

Other (non-code) Projects: '''Public Geospatial Data''', '''Education and Curriculum'''

==Home Page (required)==
http://www.osgeo.org/

==What license does your organization use? (required)==

Each member project uses their own, but all OSGeo projects are required to use an OSI approved license. (see http://www.osgeo.org/incubator/process/evaluation.html)

* Member projects specifically use: GPL >=2, LGPL, MIT/X, ...

GSoC program requires an OSI approved license, but the dropdown only lets you select one. We go with GPL 2 since it seems to be the one most commonly used.

==Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating? (required)==

We hope to get more students excited about open source geospatial development. This will help to grow the development community and of course tangibly advance particular projects. Additionally by way of the level of exposure that SoC provides we aim to further extend the use, development, and teaching & training of open source GIS at universities worldwide. This will help to prepare a new generation of developers for industry and government agencies capable of introducing and implementing viable open source geospatial technology, to the benefit of all.

Last but not least we hope to use this opportunity to bring more open source geospatial projects closer and to communicate more. We are encouraging students to come up with ideas that cross project boundaries, and to find new ways to connect the separate efforts in order to bring out new and perhaps improved wholes. In 2008 we also saw the birth of a new project, Spatialytics, which is a novel combination of several geospatial technologies. This is, as stated above, one of our goals, which SGoC helps us achieve in a way which cannot be matched in any other regular effort.

==Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.==

OSGeo participated in GSoC in 2009. Twelve OSGeo member projects participated and were very successful. The applications were of better quality so we had fewer dropouts than the previous year. We also had further cross-project co-operation projects, which went very well indeed. OSGeo Sent two delegates to the Mentor Summit.

OSGeo participated in GSoC in 2008. Eleven OSGeo member projects participated and were in general very successful. OSGeo didn't send delegates to the Mentor Summit due to the busy schedules of the mentors.

See http://wiki.osgeo.org/wiki/SoC_Report_2008 for a full report.

OSGeo participated in GSoC in 2007. Six OSGeo projects participated and were generally very successful. OSGeo also sent one delegate to the Mentor Summit in 2007. See http://wiki.osgeo.org/wiki/SoC_Report_2007 for a full report. We also opened up a demo theatre track highlighting SoC work at our [http://www.foss4g2007.org/ foss4g] conference that year.

OSGeo was formed in early 2006 and did not participate in GSoC prior to 2007. However, Refractions Research did participate in 2006 on behalf of the GeoTools, uDig, and PostGIS projects which now participate through OSGeo. Most of the the previously participating mentors and administrators continue to be involved in this years OSGeo GSoC effort.

==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.==
2007: 13/19

2008: 15/19

2009: 17/20

==Add a Comment (optional):==
As the numbers indicate each year we have received better and better applications, and thus have had a better success ratio. Also we have learned to mentor better, and to spot the good applications.

==What is the URL for your ideas page? (required)==
http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2010_Ideas

==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. (required)==
soc@lists.osgeo.org - For questions about applying and other GSoC questions

See http://wiki.osgeo.org/wiki/Mailing_Lists for a full list and descriptions of the OSGeo project mailing lists.

==What is the main IRC channel for your organization? (required)==

The primary OSGeo channel is #osgeo on the irc.freenode.net network.

==Add a Comment (optional)==
member projects maintain their own IRC channels:
: http://wiki.osgeo.org/wiki/IRC

==Does your organization have an application template you would like to see students use? (required)==
'''Name:'''

'''Country:'''

'''School and degree:'''

'''Email:'''

'''Phone:'''

'''OSGeo project(s):'''

'''Title:'''

'''Describe your idea'''
# Introduction
# Background
# The idea
# Project plan (how do you plan to spend your summer?)
# Future ideas / How can your idea be expanded?

'''Explain how your SoC task would benefit the OSGeo member project and more generally the OSGeo Foundation as a whole:'''

'''Please provide details of previous GIS experience:'''

'''Please provide details of any previous involvement with GIS programming and other software programming:'''

'''Please provide details of general computing experience: (operating systems you use on a day-to-day basis, languages you could write a program in, hardware, networking experience, etc.)'''

'''Please tell us why you are interested in GIS and open source software:'''

'''Please tell us why you are interested in your specific coding project:'''

'''Please tell us why you are interested in working for OSGeo and the software project you have selected:'''

'''Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?'''

==What criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible==
The project administrator is appointed by the OSGeo board at the beginning of the year. The project administrator asks for one or two people he trusts to be the backup administrators. Mentors are selected by project steering committees and development teams based on their reputation as skilled developers, domain experience, previously demonstrated ability to support new project developers, and stated willingness to devote time to the mentoring process. We also try very hard to match up the student working on a specific module or tool with a developer with the best expertise in the relevant area. We have in the past not voted up an otherwise good student project if there was no mentor capable of overseeing the project from a technical standpoint. Fortunately we have had a strong response from the developer pool so this has not been a major problem.

==What is your plan for dealing with disappearing students? (required)==
In order to minimize the chance of disappearing students we will ensure that the OSGeo administrative contact and the mentors have full contact information (email, home phone, etc) so that we can keep in touch with them at all times. We also stress to our students that this is a Job, as opposed to a school project.

In addition, we will make our reporting requirements clear up front. Letting the students know that we will require a weekly progress report to be posted to OSGeo's SoC mailing list (cc the member project's development mailing list), participation in public IRC channels and project mailing lists will all help ensure ongoing commitment to the work. Mentors are required to make sure that happens and that the lines of communication are kept open from beginning to end.

Other possibilities include:
# Having potential students work with their potential mentor to prepare a plan for the implementation of their project.
# Setting milestones that need to be reached by the student. These milestones would be defined before the student's work begins. A student would subsequently write a brief e-mail informing the OSGeo SoC mailing list (cc project-specific mailing list) when they have reached each milestone, giving a brief description of the work completed to that date. This is in addition to the weekly progress reports which are intended to be more casual and actively soliciting feedback.
# Selecting students that have shown previous interest in the geospatial field and free software. A student who already has a (reviewable) FOSS track record has a much higher chance of success.

==What is your plan for dealing with disappearing mentors? (required)==

Project steering committees will appoint replacement mentors if existing mentors become unavailable or unresponsive during the project period. We also plan to have backup mentors for projects so the backup mentor can fill in for, or replace the primary mentor in case of changing circumstances. Our administrators take an active role communicating with students and mentors, and so will be able to help out early if there is a problem somewhere.

Among all the OSGeo mailing lists there are 14,000 subscribers, indicating a good pool of people to draw from if required. Due to relatively high member project code and personnel cross-over, in a pinch a mentor from another OSGeo project could usefully help out.

==What steps will you take to encourage students to interact with your community before, during, and after the program? (required)==

The steps taken depend on the individual projects. As an example, last year we required weekly reports and encouraged the students to interact with us on the project mailing lists and IRC channels. We also encourage the developers and users who are not mentors to provide additional advice and feedback to the participating student and help with testing the students contributions during and after the program. In general other developers have not been shy about sharing their opinions, guidance, and advice on the member project development lists.

Furthermore the mentors are encouraged to actively involve the students in the community by having the student interact with the mentor through the community (public) channels rather then one-on-one. This also assists with student integration into the project and alleviates the disappearing-mentor problem.

==What will you do to ensure that your accepted students stick with the project after GSoC concludes? (required)==
The steps taken depend on the individual projects, as example last year many projects asked that students act as a "module maintainer" for their work. This role has an expected level of support associated with it.

Apart from that, we are relying on the open development process and the appreciation that students will receive for implementing these needed features to provide positive feedback for the students. The projects will be encouraging the students to take ownership of their work, and to contribute in other areas they may be interested in. In some cases students may also have opportunities for future contract work if they make a good impression on community members.

==Is there anything else you would like to tell the Google Summer of Code program administration team? (required)==
Thank you for your great work and the great chance to spread Open Source GIS.

==Please select your backup group administrator.==

Backup administrators:
* Hamish Bowman (melange: hamish)
* Landon Blake (melange: sunburned_surveyor)

[[Category: Google Summer of Code]]

Google Summer of Code 2010 Ideas

2010-03-18T22:04:58Z

Wiki-Wolf: /* OSGeo Google Summer of Code 2010 */

[[Image:Google_soc_2010_logo.jpg|center|250px]]

* Back to the main OSGeo [[Google Summer of Code 2010]] wiki page.

=OSGeo Google Summer of Code 2010=

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 [http://code.google.com/p/google-summer-of-code/wiki/GsocFlyers 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 posted to the soc@osgeo mailing list that at least answers the following questions:
# What did you get done this week?
# What do you plan on doing next week?
# 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 and blogs==
In addition to weekly reports we ask you to maintain a wiki or blog 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.
Wiki or blog space can be provided by OSGeo if your project doesn't have anything already set up for this.

=Timeline=
http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/timeline

* March 18th 2010: Google announces accepted organizations. If OSGeo is accepted as an organization for Google Summer of Code, start talking to us earlier rather than later.
* April 9th 2010: Student application deadline. The earlier you start the more probable it is that you will be accepted! There is two way feedback during the application process which really helps you improve and clarify your application before this final deadline.
* April 26th 2010: Accepted student proposals are announced.
* May 24th 2010: Coding begins!
* July 12-16th: Mid-term evaluation.
* August 9th: Pencils down!

= The ideas pages =
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:

* [http://trac.osgeo.org/gdal/wiki/SummerOfCode 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.
* [http://grass.osgeo.org/wiki/GRASS_SoC_Ideas 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!
* [http://www.mapbender.org/GSoC_2010 Mapbender SoC ideas 2010]: Mapbender is a server and client side geographic data management tool, programmed in '''PHP''' and '''JavaScript''', using the '''jQuery''' library.
* [http://www.qgis.org/wiki/Google_Summer_of_Code_2010 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.
* [http://udig.refractions.net/confluence/display/HACK/Summer+of+Code 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.
* [http://sourceforge.net/apps/mediawiki/jump-pilot/index.php?title=OpenJUMP_Google_Summer_Of_Code 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.
* [http://wiki.osgeo.org/wiki/OpenRouter_2010_SOC_Ideas OpenRouter 2010 SOC Ideas]: OpenRouter is a couple of projects that are building routing and driving direction libraries and applications that can be integrated with other applications.
* [[OSGeo_Cartographic_Engine#Ideas_for_Summer_of_Code_2010_Project | Cartographic Engine project ideas built on Mapnik]]: Refining much needed high quality hardcopy output tools that encourage collaboration. Built on Mapnik, applications like QGIS, GRASS, MapServer, etc. can output using these features. Focused initially on building specs that support Mapnik as the engine, but that could be applied generally across OSGeo projects as well.
* [http://www.spatialytics.org/google-summer-of-code-2010-ideas/ Spatialytics.org GSoC 2010 Ideas]: Spatialytics.org is the new home of the three open source Geospatial BI projects (GeoKettle, GeoMondrian and SOLAPLayers). Geospatial Business Intelligence (BI) tools, such as spatial ETL (Extract, Transform and Load), geo-analytical dashboards and Spatial On-Line Analytical Processing (SOLAP) allow decision-makers to rapidly analyze large amount of data at different levels of time, geography and detail in order to make better decisions.
* [http://www.mapwindow.org/wiki/index.php/Google_Summer_of_Code MapWindow GIS SoC Ideas]: MapWindow is a free, extensible, geographic information system (GIS) that can be used as an alternative desktop GIS, to distribute data to others, to develop and distribute custom spatial data analyses, written in .NET (C++, C#, VB.NET). If you're a talented VB.Net, C#, or C++ programmer, you could be the perfect fit to work on this project. We have a couple of ideas that could be done over the summer; feel free to suggest your own ideas or plug-ins as well.

= 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 for project specific lists.

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

irc://irc.freenode.net/#osgeo (Web based [http://irc.telascience.org/cgi-bin/irc.cgi IRC client])

Project irc channels:

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

[[Category:Google Summer of Code]]

Google Summer of Code 2010 Administrative

2010-03-18T21:49:21Z

Wiki-Wolf: /* How to register as a mentor */

[[Image:Google_soc_2010_logo.jpg|center]]

* Back to main OSGeo [[Google Summer of Code]] wiki page.

Central page for administering OSGeo participation in Google Summer of Code 2010.

= Background =

* Wolf Bergenheim will act as Administrative contact, with support from Landon Blake and [[HamishBowman|Hamish Bowman]]

* [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs Google's FAQ on the program]

* There is also a [http://code.google.com/p/google-summer-of-code/wiki/WikiStart Google Wiki page about the program]

* Last year(s) SoC submissions: [http://code.google.com/soc/2008/osgeo/about.html 2008], [http://socghop.appspot.com/org/home/google/gsoc2009/osgeo 2009]

* Last year(s) OSGeo GSoC wiki pages: [[Google Summer of Code 2008|2008]], [[Google Summer of Code 2009|2009]]

* [http://primates.ximian.com/~federico/docs/summer-of-code-mentoring-howto/index.html Mentoring HOWTO]

* [http://code.google.com/p/google-summer-of-code/wiki/AdviceforMentors Advice for Mentors from the Google Wiki]

* The official [http://socghop.appspot.com/ Google Summer of Code 2010 program site]

* There is a 2010 version of the [http://svn.osgeo.org/osgeo/marketing/flyer/ OSGeo SoC flyer] to look at and post in appropriate places.

= Timeline =

[http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/timeline The official timeline]



= Documents =

* OSGeo [[Google SoC Application 2010]] (see also [[Google SoC Application 2009]])

* [[SoC Application Rankings by Project]]

* The "Student Landing Page" is [[Google Summer of Code 2010 Ideas]].

* The OSGeo home at melange is (http://socghop.appspot.com/org/home/google/gsoc2009/osgeo)

== How to register as a mentor ==

Please apply to become a mentor today! Just follow these steps:

# Sign up to the [http://lists.osgeo.org/mailman/listinfo/soc OSGeo SoC mailinglist].
# Present yourself on soc@lists.osgeo.org Here are some suggested topics:
#* Project you want to/can mentor for
#* Area(s) of interest
#* Feel free to tell more about yourself
# Register yourself [http://socghop.appspot.com/ at the Melange site] (if you haven't done so already).
# Fill in the [https://spreadsheets.google.com/viewform?formkey=dEpKRDUzZEU4dXRxdHd5MVhCRWlSZXc6MA Mentor form]
# Apply to become a mentor (link will be posted later, once/if we get accepted)
# [http://socghop.appspot.com/gsoc/mentor/request/google/gsoc2010/osgeo Apply to become a mentor]
#* Accept the invitation that you receive, and fill in your Mentor information
# Go [http://socghop.appspot.com/org/list_proposals/google/gsoc2010/osgeo read and comment on student applications] (Opens March 29th)

= Project Mentors =

{| class="wikitable sortable" border="1" style="margin: 1em auto 1em auto; text-align:left"
| align="center" style="background:#f0f0f0;"|'''Mentor'''
| align="center" style="background:#f0f0f0;"|'''Project'''
|-
| --||GDAL
|-
| --||GeoServer
|-
| --||GRASS
|-
| --||gvSIG
|-
| --||Laval University
|-
| --||Mapbender
|-
| --||Mapserver
|-
| --||OpenJUMP/deegree
|-
| --||[[OpenRouter]]
|-
| --||OSSIM
|-
| --||QGIS
|-
| --||uDig
|}

= Project Milestones =
[[Google SoC Project Milestones 2010]] - todo

= Project Pages =
Each accepted Soc Project should be listed here, and the page should be updated with information about the progress of the project.

<strike>The list of proposals can be found here: [[Google Summer of Code 2010 Ranking]]</strike>

[[Category:Google Summer of Code]]

Google Summer of Code Application 2010

2010-03-11T16:14:37Z

Wiki-Wolf: /* 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

==Link ID==
osgeo

==Organization Name (required)==
OSGeo - Open Source Geospatial Foundation

==Description (required)==
OSGeo is an incorporated not-for-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and 19 (to 24) code projects in particular:

Web Mapping: '''deegree''', '''GeoServer''', '''Mapbender''', '''MapBuilder''', '''MapFish''', '''MapGuide Open Source''', '''MapServer''', '''OpenLayers'''

Desktop Applications: '''GRASS GIS''', '''OSSIM''', '''Quantum GIS''', '''gvSIG'''

Geospatial Libraries: '''FDO''', '''GDAL/OGR''', '''GEOS''', '''GeoTools''', '''MetaCRS''', '''PostGIS'''
: ''The following are sub-projects of MetaCRS'':
:* '''CS-Map''', '''GeoTIFF/libgeotiff''', '''PROJ.4''', '''Proj4J''', '''Proj4js''', '''SpatialReference.org'''

Metadata Catalog: '''GeoNetwork'''

Other (non-code) Projects: '''Public Geospatial Data''', '''Education and Curriculum'''

==Home Page (required)==
http://www.osgeo.org/

==What license does your organization use? (required)==

Each member project uses their own, but all OSGeo projects are required to use an OSI approved license. (see http://www.osgeo.org/incubator/process/evaluation.html)

* Member projects specifically use: GPL >=2, LGPL, MIT/X, ...

GSoC program requires an OSI approved license, but the dropdown only lets you select one. We go with GPL 2 since it seems to be the one most commonly used.

==Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating? (required)==

We hope to get more students excited about open source geospatial development. This will help to grow the development community and of course tangibly advance particular projects. Additionally by way of the level of exposure that SoC provides we aim to further extend the use, development, and teaching & training of open source GIS at universities worldwide. This will help to prepare a new generation of developers for industry and government agencies capable of introducing and implementing viable open source geospatial technology, to the benefit of all.

Last but not least we hope to use this opportunity to bring more open source geospatial projects closer and to communicate more. We are encouraging students to come up with ideas that cross project boundaries, and to find new ways to connect the separate efforts in order to bring out new and perhaps improved wholes. In 2008 we also saw the birth of a new project, Spatialytics, which is a novel combination of several geospatial technologies. This is, as stated above, one of our goals, which SGoC helps us achieve in a way which cannot be matched in any other regular effort.

==Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.==

OSGeo participated in GSoC in 2009. Twelve OSGeo member projects participated and were very successful. The applications were of better quality so we had fewer dropouts than the previous year. We also had further cross-project co-operation projects, which went very well indeed. OSGeo Sent two delegates to the Mentor Summit.

OSGeo participated in GSoC in 2008. Eleven OSGeo member projects participated and were in general very successful. OSGeo didn't send delegates to the Mentor Summit due to the busy schedules of the mentors.

See http://wiki.osgeo.org/wiki/SoC_Report_2008 for a full report.

OSGeo participated in GSoC in 2007. Six OSGeo projects participated and were generally very successful. OSGeo also sent one delegate to the Mentor Summit in 2007. See http://wiki.osgeo.org/wiki/SoC_Report_2007 for a full report. We also opened up a demo theatre track highlighting SoC work at our [http://www.foss4g2007.org/ foss4g] conference that year.

OSGeo was formed in early 2006 and did not participate in GSoC prior to 2007. However, Refractions Research did participate in 2006 on behalf of the GeoTools, uDig, and PostGIS projects which now participate through OSGeo. Most of the the previously participating mentors and administrators continue to be involved in this years OSGeo GSoC effort.

==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.==
2007: 13/19

2008: 15/19

2009: 17/20

==Add a Comment (optional):==
As the numbers indicate each year we have received better and better applications, and thus have had a better success ratio. Also we have learned to mentor better, and to spot the good applications.

==What is the URL for your ideas page? (required)==
http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2010_Ideas

==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. (required)==
soc@lists.osgeo.org - For questions about applying and other GSoC questions

See http://wiki.osgeo.org/wiki/Mailing_Lists for a full list and descriptions of the OSGeo project mailing lists.

==What is the main IRC channel for your organization? (required)==

The primary OSGeo channel is #osgeo on the irc.freenode.net network.

==Add a Comment (optional)==
member projects maintain their own IRC channels:
: http://wiki.osgeo.org/wiki/IRC

==Does your organization have an application template you would like to see students use? (required)==
'''Name:'''

'''Country:'''

'''School and degree:'''

'''Email:'''

'''Phone:'''

'''OSGeo project(s):'''

'''Title:'''

'''Describe your idea'''
# Introduction
# Background
# The idea
# Project plan (how do you plan to spend your summer?)
# Future ideas / How can your idea be expanded?

'''Explain how your SoC task would benefit the OSGeo member project and more generally the OSGeo Foundation as a whole:'''

'''Please provide details of previous GIS experience:'''

'''Please provide details of any previous involvement with GIS programming and other software programming:'''

'''Please provide details of general computing experience: (operating systems you use on a day-to-day basis, languages you could write a program in, hardware, networking experience, etc.)'''

'''Please tell us why you are interested in GIS and open source software:'''

'''Please tell us why you are interested in your specific coding project:'''

'''Please tell us why you are interested in working for OSGeo and the software project you have selected:'''

'''Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?'''

==What criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible==
The project administrator is appointed by the OSGeo board at the beginning of the year. The project administrator asks for one or two people he trusts to be the backup administrators. Mentors are selected by project steering committees and development teams based on their reputation as skilled developers, domain experience, previously demonstrated ability to support new project developers, and stated willingness to devote time to the mentoring process. We also try very hard to match up the student working on a specific module or tool with a developer with the best expertise in the relevant area. We have in the past not voted up an otherwise good student project if there was no mentor capable of overseeing the project from a technical standpoint. Fortunately we have had a strong response from the developer pool so this has not been a major problem.

==What is your plan for dealing with disappearing students? (required)==
In order to minimize the chance of disappearing students we will ensure that the OSGeo administrative contact and the mentors have full contact information (email, home phone, etc) so that we can keep in touch with them at all times. We also stress to our students that this is a Job, as opposed to a school project.

In addition, we will make our reporting requirements clear up front. Letting the students know that we will require a weekly progress report to be posted to OSGeo's SoC mailing list (cc the member project's development mailing list), participation in public IRC channels and project mailing lists will all help ensure ongoing commitment to the work. Mentors are required to make sure that happens and that the lines of communication are kept open from beginning to end.

Other possibilities include:
# Having potential students work with their potential mentor to prepare a plan for the implementation of their project.
# Setting milestones that need to be reached by the student. These milestones would be defined before the student's work begins. A student would subsequently write a brief e-mail informing the OSGeo SoC mailing list (cc project-specific mailing list) when they have reached each milestone, giving a brief description of the work completed to that date. This is in addition to the weekly progress reports which are intended to be more casual and actively soliciting feedback.
# Selecting students that have shown previous interest in the geospatial field and free software. A student who already has a (reviewable) FOSS track record has a much higher chance of success.

==What is your plan for dealing with disappearing mentors? (required)==

Project steering committees will appoint replacement mentors if existing mentors become unavailable or unresponsive during the project period. We also plan to have backup mentors for projects so the backup mentor can fill in for, or replace the primary mentor in case of changing circumstances. Our administrators take an active role communicating with students and mentors, and so will be able to help out early if there is a problem somewhere.

Among all the OSGeo mailing lists there are 14,000 subscribers, indicating a good pool of people to draw from if required. Due to relatively high member project code and personnel cross-over, in a pinch a mentor from another OSGeo project could usefully help out.

==What steps will you take to encourage students to interact with your community before, during, and after the program? (required)==

The steps taken depend on the individual projects. As an example, last year we required weekly reports and encouraged the students to interact with us on the project mailing lists and IRC channels. We also encourage the developers and users who are not mentors to provide additional advice and feedback to the participating student and help with testing the students contributions during and after the program. In general other developers have not been shy about sharing their opinions, guidance, and advice on the member project development lists.

Furthermore the mentors are encouraged to actively involve the students in the community by having the student interact with the mentor through the community (public) channels rather then one-on-one. This also assists with student integration into the project and alleviates the disappearing-mentor problem.

==What will you do to ensure that your accepted students stick with the project after GSoC concludes? (required)==
The steps taken depend on the individual projects, as example last year many projects asked that students act as a "module maintainer" for their work. This role has an expected level of support associated with it.

Apart from that, we are relying on the open development process and the appreciation that students will receive for implementing these needed features to provide positive feedback for the students. The projects will be encouraging the students to take ownership of their work, and to contribute in other areas they may be interested in. In some cases students may also have opportunities for future contract work if they make a good impression on community members.

==Is there anything else you would like to tell the Google Summer of Code program administration team? (required)==
Thank you for your great work and the great chance to spread Open Source GIS.

==Please select your backup group administrator.==

Backup administrators:
* Hamish Bowman (melange: hamish.bowman)
* Landon Blake (melange: sunburned_surveyor)

[[Category: Google Summer of Code]]

Google Summer of Code Application 2010

2010-03-10T22:53:00Z

Wiki-Wolf: /* Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating? (required) */

==Link ID==
osgeo

==Organization Name (required)==
OSGeo - Open Source Geospatial Foundation

==Description (required)==
OSGeo is an incorporated not-for-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and 19 (to 24) code projects in particular:

Web Mapping: '''deegree''', '''GeoServer''', '''Mapbender''', '''MapBuilder''', '''MapFish''', '''MapGuide Open Source''', '''MapServer''', '''OpenLayers'''

Desktop Applications: '''GRASS GIS''', '''OSSIM''', '''Quantum GIS''', '''gvSIG'''

Geospatial Libraries: '''FDO''', '''GDAL/OGR''', '''GEOS''', '''GeoTools''', '''MetaCRS''', '''PostGIS'''
: ''The following are sub-projects of MetaCRS'':
:* '''CS-Map''', '''GeoTIFF/libgeotiff''', '''PROJ.4''', '''Proj4J''', '''Proj4js''', '''SpatialReference.org'''

Metadata Catalog: '''GeoNetwork'''

Other (non-code) Projects: '''Public Geospatial Data''', '''Education and Curriculum'''

==Home Page (required)==
http://www.osgeo.org/

==What license does your organization use? (required)==

Each member project uses their own, but all OSGeo projects are required to use an OSI approved license. (see http://www.osgeo.org/incubator/process/evaluation.html)

* Member projects specifically use: GPL >=2, LGPL, MIT/X, ...

GSoC program requires an OSI approved license, but the dropdown only lets you select one. We go with GPL 2 since it seems to be the one most commonly used.

==Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating? (required)==

We hope to get more students excited about open source geospatial development. This will help to grow the development community and of course tangibly advance particular projects. Additionally by way of the level of exposure that SoC provides we aim to further extend the use, development, and teaching & training of open source GIS at universities worldwide. This will help to prepare a new generation of developers for industry and government agencies capable of introducing and implementing viable open source geospatial technology, to the benefit of all.

Last but not least we hope to use this opportunity to bring more open source geospatial projects closer and to communicate more. We are encouraging students to come up with ideas that cross project boundaries, and to find new ways to connect the separate efforts in order to bring out new and perhaps improved wholes. In 2008 we also saw the birth of a new project, Spatialytics, which is a novel combination of several geospatial technologies. This is, as stated above, one of our goals, which SGoC helps us achieve in a way which cannot be matched in any other regular effort.

==Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.==

OSGeo participated in GSoC in 2009. Twelve OSGeo member projects participated and were very successful. The applications were of better quality so we had fewer dropouts than the previous year. We also had further cross-project co-operation projects, which went very well indeed. OSGeo Sent two delegates to the Mentor Summit.

OSGeo participated in GSoC in 2008. Eleven OSGeo member projects participated and were in general very successful. OSGeo didn't send delegates to the Mentor Summit due to the busy schedules of the mentors.

See http://wiki.osgeo.org/wiki/SoC_Report_2008 for a full report.

OSGeo participated in GSoC in 2007. Six OSGeo projects participated and were generally very successful. OSGeo also sent one delegate to the Mentor Summit in 2007. See http://wiki.osgeo.org/wiki/SoC_Report_2007 for a full report. We also opened up a demo theatre track highlighting SoC work at our [http://www.foss4g2007.org/ foss4g] conference that year.

OSGeo was formed in early 2006 and did not participate in GSoC prior to 2007. However, Refractions Research did participate in 2006 on behalf of the GeoTools, uDig, and PostGIS projects which now participate through OSGeo. Most of the the previously participating mentors and administrators continue to be involved in this years OSGeo GSoC effort.

==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.==
2007: 13/19

2008: 15/19

2009: 17/20

==Add a Comment (optional):==
As the numbers indicate each year we have received better and better applications, and thus have had a better success ratio. Also we have learned to mentor better, and to spot the good applications.

==What is the URL for your ideas page? (required)==
http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2010_Ideas

==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. (required)==
soc@lists.osgeo.org - For questions about applying and other GSoC questions
See http://wiki.osgeo.org/wiki/Mailing_Lists for a full list and descriptions of the OSGeo project mailing lists.

==What is the main IRC channel for your organization? (required)==

The primary OSGeo channel is #osgeo on the irc.freenode.net network.

==Add a Comment (optional)==
member projects maintain their own IRC channels:
: http://wiki.osgeo.org/wiki/IRC

==Does your organization have an application template you would like to see students use? (required)==
'''Name:'''

'''Country:'''

'''School and degree:'''

'''Email:'''

'''Phone:'''

'''OSGeo project(s):'''

'''Title:'''

'''Describe your idea'''
# Introduction
# Background
# The idea
# Project plan (how do you plan to spend your summer?)
# Future ideas / How can your idea be expanded?

'''Explain how your SoC task would benefit the OSGeo member project and more generally the OSGeo Foundation as a whole:'''

'''Please provide details of previous GIS experience:'''

'''Please provide details of any previous involvement with GIS programming and other software programming:'''

'''Please provide details of general computing experience: (operating systems you use on a day-to-day basis, languages you could write a program in, hardware, networking experience, etc.)'''

'''Please tell us why you are interested in GIS and open source software:'''

'''Please tell us why you are interested in your specific coding project:'''

'''Please tell us why you are interested in working for OSGeo and the software project you have selected:'''

'''Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?'''

==What criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible==
The project administrator is appointed by the OSGeo board at the beginning of the year. The project administrator asks for one or two people he trusts to be the backup administrators. Mentors are selected by project steering committees and development teams based on their reputation as skilled developers, domain experience, previously demonstrated ability to support new project developers, and stated willingness to devote time to the mentoring process. We also try very hard to match up the student working on a specific module or tool with a developer with the best expertise in the relevant area. We have in the past not voted up an otherwise good student project if there was no mentor capable of overseeing the project from a technical standpoint. Fortunately we have had a strong response from the developer pool so this has not been a major problem.

==What is your plan for dealing with disappearing students? (required)==
In order to minimize the chance of disappearing students we will ensure that the OSGeo administrative contact and the mentors have full contact information (email, home phone, etc) so that we can keep in touch with them at all times. We also stress to our students that this is a Job, as opposed to a school project.

In addition, we will make our reporting requirements clear up front. Letting the students know that we will require a weekly progress report to be posted to OSGeo's SoC mailing list (cc the member project's development mailing list), participation in public IRC channels and project mailing lists will all help ensure ongoing commitment to the work. Mentors are required to make sure that happens and that the lines of communication are kept open from beginning to end.

Other possibilities include:
# Having potential students work with their potential mentor to prepare a plan for the implementation of their project.
# Setting milestones that need to be reached by the student. These milestones would be defined before the student's work begins. A student would subsequently write a brief e-mail informing the OSGeo SoC mailing list (cc project-specific mailing list) when they have reached each milestone, giving a brief description of the work completed to that date. This is in addition to the weekly progress reports which are intended to be more casual and actively soliciting feedback.
# Selecting students that have shown previous interest in the geospatial field and free software. A student who already has a (reviewable) FOSS track record has a much higher chance of success.

==What is your plan for dealing with disappearing mentors? (required)==

Project steering committees will appoint replacement mentors if existing mentors become unavailable or unresponsive during the project period. We also plan to have backup mentors for projects so the backup mentor can fill in for, or replace the primary mentor in case of changing circumstances. Our administrators take an active role communicating with students and mentors, and so will be able to help out early if there is a problem somewhere.

Among all the OSGeo mailing lists there are 14,000 subscribers, indicating a good pool of people to draw from if required. Due to relatively high member project code and personnel cross-over, in a pinch a mentor from another OSGeo project could usefully help out.

==What steps will you take to encourage students to interact with your community before, during, and after the program? (required)==

The steps taken depend on the individual projects. As an example, last year we required weekly reports and encouraged the students to interact with us on the project mailing lists and IRC channels. We also encourage the developers and users who are not mentors to provide additional advice and feedback to the participating student and help with testing the students contributions during and after the program. In general other developers have not been shy about sharing their opinions, guidance, and advice on the member project development lists.

Furthermore the mentors are encouraged to actively involve the students in the community by having the student interact with the mentor through the community (public) channels rather then one-on-one. This also assists with student integration into the project and alleviates the disappearing-mentor problem.

==What will you do to ensure that your accepted students stick with the project after GSoC concludes? (required)==
The steps taken depend on the individual projects, as example last year many projects asked that students act as a "module maintainer" for their work. This role has an expected level of support associated with it.

Apart from that, we are relying on the open development process and the appreciation that students will receive for implementing these needed features to provide positive feedback for the students. The projects will be encouraging the students to take ownership of their work, and to contribute in other areas they may be interested in. In some cases students may also have opportunities for future contract work if they make a good impression on community members.

==Is there anything else you would like to tell the Google Summer of Code program administration team? (required)==
Thank you for your great work and the great chance to spread Open Source GIS.

==Please select your backup group administrator.==

Backup administrators:
* Hamish Bowman (melange: hamish.bowman)
* Landon Blake (melange: sunburned_surveyor)

[[Category: Google Summer of Code]]

Google Summer of Code Application 2010

2010-03-10T22:39:51Z

Wiki-Wolf: /* Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating? (required) */

==Link ID==
osgeo

==Organization Name (required)==
OSGeo - Open Source Geospatial Foundation

==Description (required)==
OSGeo is an incorporated not-for-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and 19 (to 24) code projects in particular:

Web Mapping: '''deegree''', '''GeoServer''', '''Mapbender''', '''MapBuilder''', '''MapFish''', '''MapGuide Open Source''', '''MapServer''', '''OpenLayers'''

Desktop Applications: '''GRASS GIS''', '''OSSIM''', '''Quantum GIS''', '''gvSIG'''

Geospatial Libraries: '''FDO''', '''GDAL/OGR''', '''GEOS''', '''GeoTools''', '''MetaCRS''', '''PostGIS'''
: ''The following are sub-projects of MetaCRS'':
:* '''CS-Map''', '''GeoTIFF/libgeotiff''', '''PROJ.4''', '''Proj4J''', '''Proj4js''', '''SpatialReference.org'''

Metadata Catalog: '''GeoNetwork'''

Other (non-code) Projects: '''Public Geospatial Data''', '''Education and Curriculum'''

==Home Page (required)==
http://www.osgeo.org/

==What license does your organization use? (required)==

Each member project uses their own, but all OSGeo projects are required to use an OSI approved license. (see http://www.osgeo.org/incubator/process/evaluation.html)

* Member projects specifically use: GPL >=2, LGPL, MIT/X, ...

GSoC program requires an OSI approved license, but the dropdown only lets you select one. We go with GPL 2 since it seems to be the one most commonly used.

==Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating? (required)==

We hope to get more students excited about open source geospatial development. This will help to grow the development community and of course tangibly advance particular projects. Additionally by way of the level of exposure that SoC provides we aim to further extend the use, development, and teaching & training of open source GIS at universities worldwide. This will help to prepare a new generation of developers for industry and government agencies capable of introducing and implementing viable open source geospatial technology, to the benefit of all. Last but not least we hope to use this opportunity to bring more open source geospatial projects closer and to communicate more. We are encouraging students to come up with ideas that cross project boundaries, and to find new ways to connect the separate efforts in order to bring out new and perhaps improved wholes.

==Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.==

OSGeo participated in GSoC in 2009. Twelve OSGeo member projects participated and were very successful. The applications were of better quality so we had fewer dropouts than the previous year. We also had further cross-project co-operation projects, which went very well indeed. OSGeo Sent two delegates to the Mentor Summit.

OSGeo participated in GSoC in 2008. Eleven OSGeo member projects participated and were in general very successful. OSGeo didn't send delegates to the Mentor Summit due to the busy schedules of the mentors.

See http://wiki.osgeo.org/wiki/SoC_Report_2008 for a full report.

OSGeo participated in GSoC in 2007. Six OSGeo projects participated and were generally very successful. OSGeo also sent one delegate to the Mentor Summit in 2007. See http://wiki.osgeo.org/wiki/SoC_Report_2007 for a full report. We also opened up a demo theatre track highlighting SoC work at our [http://www.foss4g2007.org/ foss4g] conference that year.

OSGeo was formed in early 2006 and did not participate in GSoC prior to 2007. However, Refractions Research did participate in 2006 on behalf of the GeoTools, uDig, and PostGIS projects which now participate through OSGeo. Most of the the previously participating mentors and administrators continue to be involved in this years OSGeo GSoC effort.

==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.==
2007: 13/19

2008: 15/19

2009: 17/20

==Add a Comment (optional):==
As the numbers indicate each year we have received better and better applications, and thus have had a better success ratio. Also we have learned to mentor better, and to spot the good applications.

==What is the URL for your ideas page? (required)==
http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2010_Ideas

==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. (required)==
soc@lists.osgeo.org - For questions about applying and other GSoC questions
See http://wiki.osgeo.org/wiki/Mailing_Lists for a full list and descriptions of the OSGeo project mailing lists.

==What is the main IRC channel for your organization? (required)==

The primary OSGeo channel is #osgeo on the irc.freenode.net network.

==Add a Comment (optional)==
member projects maintain their own IRC channels:
: http://wiki.osgeo.org/wiki/IRC

==Does your organization have an application template you would like to see students use? (required)==
'''Name:'''

'''Country:'''

'''School and degree:'''

'''Email:'''

'''Phone:'''

'''OSGeo project(s):'''

'''Title:'''

'''Describe your idea'''
# Introduction
# Background
# The idea
# Project plan (how do you plan to spend your summer?)
# Future ideas / How can your idea be expanded?

'''Explain how your SoC task would benefit the OSGeo member project and more generally the OSGeo Foundation as a whole:'''

'''Please provide details of previous GIS experience:'''

'''Please provide details of any previous involvement with GIS programming and other software programming:'''

'''Please provide details of general computing experience: (operating systems you use on a day-to-day basis, languages you could write a program in, hardware, networking experience, etc.)'''

'''Please tell us why you are interested in GIS and open source software:'''

'''Please tell us why you are interested in your specific coding project:'''

'''Please tell us why you are interested in working for OSGeo and the software project you have selected:'''

'''Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?'''

==What criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible==
The project administrator is appointed by the OSGeo board at the beginning of the year. The project administrator asks for one or two people he trusts to be the backup administrators. Mentors are selected by project steering committees and development teams based on their reputation as skilled developers, domain experience, previously demonstrated ability to support new project developers, and stated willingness to devote time to the mentoring process. We also try very hard to match up the student working on a specific module or tool with a developer with the best expertise in the relevant area. We have in the past not voted up an otherwise good student project if there was no mentor capable of overseeing the project from a technical standpoint. Fortunately we have had a strong response from the developer pool so this has not been a major problem.

==What is your plan for dealing with disappearing students? (required)==
In order to minimize the chance of disappearing students we will ensure that the OSGeo administrative contact and the mentors have full contact information (email, home phone, etc) so that we can keep in touch with them at all times. We also stress to our students that this is a Job, as opposed to a school project.

In addition, we will make our reporting requirements clear up front. Letting the students know that we will require a weekly progress report to be posted to OSGeo's SoC mailing list (cc the member project's development mailing list), participation in public IRC channels and project mailing lists will all help ensure ongoing commitment to the work. Mentors are required to make sure that happens and that the lines of communication are kept open from beginning to end.

Other possibilities include:
# Having potential students work with their potential mentor to prepare a plan for the implementation of their project.
# Setting milestones that need to be reached by the student. These milestones would be defined before the student's work begins. A student would subsequently write a brief e-mail informing the OSGeo SoC mailing list (cc project-specific mailing list) when they have reached each milestone, giving a brief description of the work completed to that date. This is in addition to the weekly progress reports which are intended to be more casual and actively soliciting feedback.
# Selecting students that have shown previous interest in the geospatial field and free software. A student who already has a (reviewable) FOSS track record has a much higher chance of success.

==What is your plan for dealing with disappearing mentors? (required)==

Project steering committees will appoint replacement mentors if existing mentors become unavailable or unresponsive during the project period. We also plan to have backup mentors for projects so the backup mentor can fill in for, or replace the primary mentor in case of changing circumstances. Our administrators take an active role communicating with students and mentors, and so will be able to help out early if there is a problem somewhere.

Among all the OSGeo mailing lists there are 14,000 subscribers, indicating a good pool of people to draw from if required. Due to relatively high member project code and personnel cross-over, in a pinch a mentor from another OSGeo project could usefully help out.

==What steps will you take to encourage students to interact with your community before, during, and after the program? (required)==

The steps taken depend on the individual projects. As an example, last year we required weekly reports and encouraged the students to interact with us on the project mailing lists and IRC channels. We also encourage the developers and users who are not mentors to provide additional advice and feedback to the participating student and help with testing the students contributions during and after the program. In general other developers have not been shy about sharing their opinions, guidance, and advice on the member project development lists.

Furthermore the mentors are encouraged to actively involve the students in the community by having the student interact with the mentor through the community (public) channels rather then one-on-one. This also assists with student integration into the project and alleviates the disappearing-mentor problem.

==What will you do to ensure that your accepted students stick with the project after GSoC concludes? (required)==
The steps taken depend on the individual projects, as example last year many projects asked that students act as a "module maintainer" for their work. This role has an expected level of support associated with it.

Apart from that, we are relying on the open development process and the appreciation that students will receive for implementing these needed features to provide positive feedback for the students. The projects will be encouraging the students to take ownership of their work, and to contribute in other areas they may be interested in. In some cases students may also have opportunities for future contract work if they make a good impression on community members.

==Is there anything else you would like to tell the Google Summer of Code program administration team? (required)==
Thank you for your great work and the great chance to spread Open Source GIS.

==Please select your backup group administrator.==

Backup administrators:
* Hamish Bowman (melange: hamish.bowman)
* Landon Blake (melange: sunburned_surveyor)

[[Category: Google Summer of Code]]

Google Summer of Code 2010 Administrative

2010-03-08T23:10:36Z

Wiki-Wolf: /* How to register as a mentor */

[[Image:Google_soc_2010_logo.jpg|center]]

* Back to main OSGeo [[Google Summer of Code]] wiki page.

Central page for administering OSGeo participation in Google Summer of Code 2010.

= Background =

* Wolf Bergenheim will act as Administrative contact, with support from Landon Blake and [[HamishBowman|Hamish Bowman]]

* [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs Google's FAQ on the program]

* There is also a [http://code.google.com/p/google-summer-of-code/wiki/WikiStart Google Wiki page about the program]

* Last year(s) SoC submissions: [http://code.google.com/soc/2008/osgeo/about.html 2008], [http://socghop.appspot.com/org/home/google/gsoc2009/osgeo 2009]

* Last year(s) OSGeo GSoC wiki pages: [[Google Summer of Code 2008|2008]], [[Google Summer of Code 2009|2009]]

* [http://primates.ximian.com/~federico/docs/summer-of-code-mentoring-howto/index.html Mentoring HOWTO]

* [http://code.google.com/p/google-summer-of-code/wiki/AdviceforMentors Advice for Mentors from the Google Wiki]

* The official [http://socghop.appspot.com/ Google Summer of Code 2010 program site]

* There is a 2010 version of the [http://svn.osgeo.org/osgeo/marketing/flyer/ OSGeo SoC flyer] to look at and post in appropriate places.

= Timeline =

[http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/timeline The official timeline]



= Documents =

* OSGeo [[Google SoC Application 2010]] (see also [[Google SoC Application 2009]])

* [[SoC Application Rankings by Project]]

* The "Student Landing Page" is [[Google Summer of Code 2010 Ideas]].

* The OSGeo home at melange is (http://socghop.appspot.com/org/home/google/gsoc2009/osgeo)

== How to register as a mentor ==

* '''''As we have not yet even applied to the program yet, for now just say hello on the OSGeo SoC mailing list.'''''

Please apply to become a mentor today! Just follow these steps:

# Sign up to the [http://lists.osgeo.org/mailman/listinfo/soc OSGeo SoC mailinglist].
# Present yourself on soc@lists.osgeo.org Here are some suggested topics:
#* Project you want to/can mentor for
#* Area(s) of interest
#* Feel free to tell more about yourself
# Register yourself [http://socghop.appspot.com/ at the Melange site] (if you haven't done so already).
# Fill in the [https://spreadsheets.google.com/viewform?formkey=dEpKRDUzZEU4dXRxdHd5MVhCRWlSZXc6MA Mentor form]
# Apply to become a mentor (link will be posted later, once/if we get accepted)

<strike>
After you have applied you will get an invitation notification in the melange system. You need to accept the invitation, and fill in the form to become a registered mentor.
# [http://socghop.appspot.com/org/apply_mentor/google/gsoc2010 Apply to become a mentor]
## Accept the invitation that you receive, and fill in your Mentor information
# Go [http://socghop.appspot.com/org/list_proposals/google/gsoc2010/osgeo read and comment on student applications]
</strike>

= Project Mentors =

{| class="wikitable sortable" border="1" style="margin: 1em auto 1em auto; text-align:left"
| align="center" style="background:#f0f0f0;"|'''Mentor'''
| align="center" style="background:#f0f0f0;"|'''Project'''
|-
| --||GDAL
|-
| --||GeoServer
|-
| --||GRASS
|-
| --||gvSIG
|-
| --||Laval University
|-
| --||Mapbender
|-
| --||Mapserver
|-
| --||OpenJUMP/deegree
|-
| --||[[OpenRouter]]
|-
| --||OSSIM
|-
| --||QGIS
|-
| --||uDig
|}

= Project Milestones =
[[Google SoC Project Milestones 2010]] - todo

= Project Pages =
Each accepted Soc Project should be listed here, and the page should be updated with information about the progress of the project.

<strike>The list of proposals can be found here: [[Google Summer of Code 2010 Ranking]]</strike>

[[Category:Google Summer of Code]]

Google Summer of Code 2010 Administrative

2010-03-08T20:47:01Z

Wiki-Wolf: /* How to register as a mentor */

[[Image:Google_soc_2010_logo.jpg|center]]

* Back to main OSGeo [[Google Summer of Code]] wiki page.

Central page for administering OSGeo participation in Google Summer of Code 2010.

= Background =

* Wolf Bergenheim will act as Administrative contact, with support from Landon Blake and [[HamishBowman|Hamish Bowman]]

* [http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs Google's FAQ on the program]

* There is also a [http://code.google.com/p/google-summer-of-code/wiki/WikiStart Google Wiki page about the program]

* Last year(s) SoC submissions: [http://code.google.com/soc/2008/osgeo/about.html 2008], [http://socghop.appspot.com/org/home/google/gsoc2009/osgeo 2009]

* Last year(s) OSGeo GSoC wiki pages: [[Google Summer of Code 2008|2008]], [[Google Summer of Code 2009|2009]]

* [http://primates.ximian.com/~federico/docs/summer-of-code-mentoring-howto/index.html Mentoring HOWTO]

* [http://code.google.com/p/google-summer-of-code/wiki/AdviceforMentors Advice for Mentors from the Google Wiki]

* The official [http://socghop.appspot.com/ Google Summer of Code 2010 program site]

* There is a 2010 version of the [http://svn.osgeo.org/osgeo/marketing/flyer/ OSGeo SoC flyer] to look at and post in appropriate places.

= Timeline =

[http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/timeline The official timeline]



= Documents =

* OSGeo [[Google SoC Application 2010]] (see also [[Google SoC Application 2009]])

* [[SoC Application Rankings by Project]]

* The "Student Landing Page" is [[Google Summer of Code 2010 Ideas]].

* The OSGeo home at melange is (http://socghop.appspot.com/org/home/google/gsoc2009/osgeo)

== How to register as a mentor ==

* '''''As we have not yet even applied to the program yet, for now just say hello on the OSGeo SoC mailing list.'''''

Please apply to become a mentor today! Just follow these steps:

# Sign up to the [http://lists.osgeo.org/mailman/listinfo/soc OSGeo SoC mailinglist].
# Present yourself on soc@lists.osgeo.org Here are some suggested topics:
#* Project you want to/can mentor for
#* Area(s) of interest
#* Feel free to tell more about yourself
# Register yourself [http://socghop.appspot.com/ at the Melange site]
# Fill in the [https://spreadsheets.google.com/viewform?formkey=dEpKRDUzZEU4dXRxdHd5MVhCRWlSZXc6MA Mentor form]
# Apply to become a mentor (link will be posted later, once/if we get accepted)

<strike>
After you have applied you will get an invitation notification in the melange system. You need to accept the invitation, and fill in the form to become a registered mentor.
# [http://socghop.appspot.com/org/apply_mentor/google/gsoc2010 Apply to become a mentor]
## Accept the invitation that you receive, and fill in your Mentor information
# Go [http://socghop.appspot.com/org/list_proposals/google/gsoc2010/osgeo read and comment on student applications]
</strike>

= Project Mentors =

{| class="wikitable sortable" border="1" style="margin: 1em auto 1em auto; text-align:left"
| align="center" style="background:#f0f0f0;"|'''Mentor'''
| align="center" style="background:#f0f0f0;"|'''Project'''
|-
| --||GDAL
|-
| --||GeoServer
|-
| --||GRASS
|-
| --||gvSIG
|-
| --||Laval University
|-
| --||Mapbender
|-
| --||Mapserver
|-
| --||OpenJUMP/deegree
|-
| --||[[OpenRouter]]
|-
| --||OSSIM
|-
| --||QGIS
|-
| --||uDig
|}

= Project Milestones =
[[Google SoC Project Milestones 2010]] - todo

= Project Pages =
Each accepted Soc Project should be listed here, and the page should be updated with information about the progress of the project.

<strike>The list of proposals can be found here: [[Google Summer of Code 2010 Ranking]]</strike>

[[Category:Google Summer of Code]]

Google Summer of Code Application 2010

2010-03-08T20:28:23Z

Wiki-Wolf: /* 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. */

==Link ID==
osgeo

==Organization Name (required)==
OSGeo - Open Source Geospatial Foundation

==Description (required)==
OSGeo is an incorporated not-for-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and 19 (to 24) code projects in particular:

Web Mapping: '''deegree''', '''GeoServer''', '''Mapbender''', '''MapBuilder''', '''MapFish''', '''MapGuide Open Source''', '''MapServer''', '''OpenLayers'''

Desktop Applications: '''GRASS GIS''', '''OSSIM''', '''Quantum GIS''', '''gvSIG'''

Geospatial Libraries: '''FDO''', '''GDAL/OGR''', '''GEOS''', '''GeoTools''', '''MetaCRS''', '''PostGIS'''
: ''The following are sub-projects of MetaCRS'':
:* '''CS-Map''', '''GeoTIFF/libgeotiff''', '''PROJ.4''', '''Proj4J''', '''Proj4js''', '''SpatialReference.org'''

Metadata Catalog: '''GeoNetwork'''

Other (non-code) Projects: '''Public Geospatial Data''', '''Education and Curriculum'''

Each member project uses their own, but all OSGeo projects are required to use an OSI approved license. (see http://www.osgeo.org/incubator/process/evaluation.html)

==Home Page (required)==
http://www.osgeo.org/

==What license does your organization use? (required)==

Each member project uses their own, but all OSGeo projects are required to use an OSI approved license. (see http://www.osgeo.org/incubator/process/evaluation.html)

* Member projects specifically use: GPL >=2, LGPL, MIT/X, ...

GSoC program requires an OSI approved license, but the dropdown only lets you select one. We go with GPL 2 since it seems to be the one mostly used.

==Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating? (required)==

We hope to get more students excited about open source geospatial development. This will help to grow the development community and of course tangibly advance particular projects. Additionally by way of the level of exposure that SoC provides we aim to further extend the use, development, and teaching & training of open source GIS at universities worldwide. This will help to prepare a new generation of developers for industry and government agencies capable of introducing and implementing viable open source geospatial technology, to the benefit of all.

==Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.==

OSGeo participated in GSoC in 2009. Twelve OSGeo member projects participated and were very successful. The applications were of better quality so we had fewer dropouts than the previous year. We also had further cross-project co-operation projects, which went very well indeed. OSGeo Sent two delegates to the Mentor Summit.

OSGeo participated in GSoC in 2008. Eleven OSGeo member projects participated and were in general very successful. OSGeo didn't send delegates to the Mentor Summit due to the busy schedules of the mentors.

See http://wiki.osgeo.org/wiki/SoC_Report_2008 for a full report.

OSGeo participated in GSoC in 2007. Six OSGeo projects participated and were generally very successful. OSGeo also sent one delegate to the Mentor Summit in 2007. See http://wiki.osgeo.org/wiki/SoC_Report_2007 for a full report. We also opened up a demo theatre track highlighting SoC work at our [http://www.foss4g2007.org/ foss4g] conference that year.

OSGeo was formed in early 2006 and did not participate in GSoC prior to 2007. However, Refractions Research did participate in 2006 on behalf of the GeoTools, uDig, and PostGIS projects which now participate through OSGeo. Most of the the previously participating mentors and administrators continue to be involved in this years OSGeo GSoC effort.

==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.==
2007: 13/19

2008: 15/19

2009: 17/20

==Add a Comment (optional):==
As the numbers indicate each year we have received better and better applications, and thus have had a better success ratio. Also we have learned to mentor better, and to spot the good applications.

==What is the URL for your ideas page? (required)==
http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2010_Ideas

==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. (required)==
soc@lists.osgeo.org - For questions about applying and other GSoC questions
See http://wiki.osgeo.org/wiki/Mailing_Lists for a full list and descriptions of the OSGeo project mailing lists.

==What is the main IRC channel for your organization? (required)==

The primary OSGeo channel is #osgeo on the irc.freenode.net network.

==Add a Comment (optional)==
member projects maintain their own IRC channels:
: http://wiki.osgeo.org/wiki/IRC

==Does your organization have an application template you would like to see students use? (required)==
'''Name:'''

'''Country:'''

'''School and degree:'''

'''Email:'''

'''Phone:'''

'''OSGeo project(s):'''

'''Title:'''

'''Describe your idea'''
# Introduction
# Background
# The idea
# Project plan (how do you plan to spend your summer?)
# Future ideas / How can your idea be expanded?

'''Explain how your SoC task would benefit the OSGeo member project and more generally the OSGeo Foundation as a whole:'''

'''Please provide details of previous GIS experience:'''

'''Please provide details of any previous involvement with GIS programming and other software programming:'''

'''Please provide details of general computing experience: (operating systems you use on a day-to-day basis, languages you could write a program in, hardware, networking experience, etc.)'''

'''Please tell us why you are interested in GIS and open source software:'''

'''Please tell us why you are interested in your specific coding project:'''

'''Please tell us why you are interested in working for OSGeo and the software project you have selected:'''

'''Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?'''

==What criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible==
The project administrator is appointed by the OSGeo board at the beginning of the year. The project administrator asks for one or two people he trusts to be the backup administrators. Mentors are selected by project steering committees and development teams based on their reputation as skilled developers, domain experience, previously demonstrated ability to support new project developers, and stated willingness to devote time to the mentoring process. We also try very hard to match up the student working on a specific module or tool with a developer with the best expertise in the relevant area. We have in the past not voted up an otherwise good student project if there was no mentor capable of overseeing the project from a technical standpoint. Fortunately we have had a strong response from the developer pool so this has not been a major problem.

==What is your plan for dealing with disappearing students? (required)==
In order to minimize the chance of disappearing students we will ensure that the OSGeo administrative contact and the mentors have full contact information (email, home phone, etc) so that we can keep in touch with them at all times. We also stress to our students that this is a Job, as opposed to a school project.

In addition, we will make our reporting requirements clear up front. Letting the students know that we will require a weekly progress report to be posted to OSGeo's SoC mailing list (cc the member project's development mailing list), participation in public IRC channels and project mailing lists will all help ensure ongoing commitment to the work. Mentors are required to make sure that happens and that the lines of communication are kept open from beginning to end.

Other possibilities include:
# Having potential students work with their potential mentor to prepare a plan for the implementation of their project.
# Setting milestones that need to be reached by the student. These milestones would be defined before the student's work begins. A student would subsequently write a brief e-mail informing the OSGeo SoC mailing list (cc project-specific mailing list) when they have reached each milestone, giving a brief description of the work completed to that date. This is in addition to the weekly progress reports which are intended to be more casual and actively soliciting feedback.
# Selecting students that have shown previous interest in the geospatial field and free software. A student who already has a (reviewable) FOSS track record has a much higher chance of success.

==What is your plan for dealing with disappearing mentors? (required)==

Project steering committees will appoint replacement mentors if existing mentors become unavailable or unresponsive during the project period. Where possible, we also plan to have backup mentors for projects so the backup mentor can fill in for, or replace the mentor in case of changing circumstances. We also have active administrators who will communicate with students and mentros to be able to help out if there is a problem somewhere.

Among all the OSGeo mailing lists there are 14,000 subscribers, indicating a good pool of people to draw from if required. Due to relatively high member project code and personnel cross-over, in a pinch a mentor from another OSGeo project could usefully help out.

==What steps will you take to encourage students to interact with your community before, during, and after the program? (required)==

The steps taken depend on the individual projects. As an example, last year we required weekly reports and encouraged the students to interact with us on the project mailing lists and IRC channels. We also encourage the developers and users who are not mentors to provide additional advice and feedback to the participating student and help with testing the students contributions during and after the program. In general other developers have not been shy about sharing their opinions, guidance, and advice on the member project development lists.

Furthermore the mentors are encouraged to actively involve the students in the community by having the student interact with the mentor through the community (public) channels rather then one-on-one. This also assists with student integration into the project and alleviates the disappearing-mentor problem.

==What will you do to ensure that your accepted students stick with the project after GSoC concludes? (required)==
The steps taken depend on the individual projects, as example last year many projects asked that students act as a "module maintainer" for their work. This role has an expected level of support associated with it.

Apart from that, we are relying on the open development process and the appreciation that students will receive for implementing these needed features to provide positive feedback for the students. The projects will be encouraging the students to take ownership of their work, and to contribute in other areas they may be interested in. In some cases students may also have opportunities for future contract work if they make a good impression on community members.

==Is there anything else you would like to tell the Google Summer of Code program administration team? (required)==
Thank you for your great work and the great chance to spread Open Source GIS.

==Please select your backup group administrator.==

Backup administrators:
* Hamish Bowman (melange: hamish.bowman)
* Landon Blake (melange: sunburned_surveyor)

[[Category: Google Summer of Code]]

Google Summer of Code Application 2010

2010-03-08T20:27:43Z

Wiki-Wolf:

==Link ID==
osgeo

==Organization Name (required)==
OSGeo - Open Source Geospatial Foundation

==Description (required)==
OSGeo is an incorporated not-for-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and 19 (to 24) code projects in particular:

Web Mapping: '''deegree''', '''GeoServer''', '''Mapbender''', '''MapBuilder''', '''MapFish''', '''MapGuide Open Source''', '''MapServer''', '''OpenLayers'''

Desktop Applications: '''GRASS GIS''', '''OSSIM''', '''Quantum GIS''', '''gvSIG'''

Geospatial Libraries: '''FDO''', '''GDAL/OGR''', '''GEOS''', '''GeoTools''', '''MetaCRS''', '''PostGIS'''
: ''The following are sub-projects of MetaCRS'':
:* '''CS-Map''', '''GeoTIFF/libgeotiff''', '''PROJ.4''', '''Proj4J''', '''Proj4js''', '''SpatialReference.org'''

Metadata Catalog: '''GeoNetwork'''

Other (non-code) Projects: '''Public Geospatial Data''', '''Education and Curriculum'''

Each member project uses their own, but all OSGeo projects are required to use an OSI approved license. (see http://www.osgeo.org/incubator/process/evaluation.html)

==Home Page (required)==
http://www.osgeo.org/

==What license does your organization use? (required)==

Each member project uses their own, but all OSGeo projects are required to use an OSI approved license. (see http://www.osgeo.org/incubator/process/evaluation.html)

* Member projects specifically use: GPL >=2, LGPL, MIT/X, ...

GSoC program requires an OSI approved license, but the dropdown only lets you select one. We go with GPL 2 since it seems to be the one mostly used.

==Why is your organization applying to participate in GSoC 2010? What do you hope to gain by participating? (required)==

We hope to get more students excited about open source geospatial development. This will help to grow the development community and of course tangibly advance particular projects. Additionally by way of the level of exposure that SoC provides we aim to further extend the use, development, and teaching & training of open source GIS at universities worldwide. This will help to prepare a new generation of developers for industry and government agencies capable of introducing and implementing viable open source geospatial technology, to the benefit of all.

==Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.==

OSGeo participated in GSoC in 2009. Twelve OSGeo member projects participated and were very successful. The applications were of better quality so we had fewer dropouts than the previous year. We also had further cross-project co-operation projects, which went very well indeed. OSGeo Sent two delegates to the Mentor Summit.

OSGeo participated in GSoC in 2008. Eleven OSGeo member projects participated and were in general very successful. OSGeo didn't send delegates to the Mentor Summit due to the busy schedules of the mentors.

See http://wiki.osgeo.org/wiki/SoC_Report_2008 for a full report.

OSGeo participated in GSoC in 2007. Six OSGeo projects participated and were generally very successful. OSGeo also sent one delegate to the Mentor Summit in 2007. See http://wiki.osgeo.org/wiki/SoC_Report_2007 for a full report. We also opened up a demo theatre track highlighting SoC work at our [http://www.foss4g2007.org/ foss4g] conference that year.

OSGeo was formed in early 2006 and did not participate in GSoC prior to 2007. However, Refractions Research did participate in 2006 on behalf of the GeoTools, uDig, and PostGIS projects which now participate through OSGeo. Most of the the previously participating mentors and administrators continue to be involved in this years OSGeo GSoC effort.

==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.==
2007: 13/19
2008: 15/19
2009: 17/20

==Add a Comment (optional):==
As the numbers indicate each year we have received better and better applications, and thus have had a better success ratio. Also we have learned to mentor better, and to spot the good applications.

==What is the URL for your ideas page? (required)==
http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2010_Ideas

==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. (required)==
soc@lists.osgeo.org - For questions about applying and other GSoC questions
See http://wiki.osgeo.org/wiki/Mailing_Lists for a full list and descriptions of the OSGeo project mailing lists.

==What is the main IRC channel for your organization? (required)==

The primary OSGeo channel is #osgeo on the irc.freenode.net network.

==Add a Comment (optional)==
member projects maintain their own IRC channels:
: http://wiki.osgeo.org/wiki/IRC

==Does your organization have an application template you would like to see students use? (required)==
'''Name:'''

'''Country:'''

'''School and degree:'''

'''Email:'''

'''Phone:'''

'''OSGeo project(s):'''

'''Title:'''

'''Describe your idea'''
# Introduction
# Background
# The idea
# Project plan (how do you plan to spend your summer?)
# Future ideas / How can your idea be expanded?

'''Explain how your SoC task would benefit the OSGeo member project and more generally the OSGeo Foundation as a whole:'''

'''Please provide details of previous GIS experience:'''

'''Please provide details of any previous involvement with GIS programming and other software programming:'''

'''Please provide details of general computing experience: (operating systems you use on a day-to-day basis, languages you could write a program in, hardware, networking experience, etc.)'''

'''Please tell us why you are interested in GIS and open source software:'''

'''Please tell us why you are interested in your specific coding project:'''

'''Please tell us why you are interested in working for OSGeo and the software project you have selected:'''

'''Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?'''

==What criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible==
The project administrator is appointed by the OSGeo board at the beginning of the year. The project administrator asks for one or two people he trusts to be the backup administrators. Mentors are selected by project steering committees and development teams based on their reputation as skilled developers, domain experience, previously demonstrated ability to support new project developers, and stated willingness to devote time to the mentoring process. We also try very hard to match up the student working on a specific module or tool with a developer with the best expertise in the relevant area. We have in the past not voted up an otherwise good student project if there was no mentor capable of overseeing the project from a technical standpoint. Fortunately we have had a strong response from the developer pool so this has not been a major problem.

==What is your plan for dealing with disappearing students? (required)==
In order to minimize the chance of disappearing students we will ensure that the OSGeo administrative contact and the mentors have full contact information (email, home phone, etc) so that we can keep in touch with them at all times. We also stress to our students that this is a Job, as opposed to a school project.

In addition, we will make our reporting requirements clear up front. Letting the students know that we will require a weekly progress report to be posted to OSGeo's SoC mailing list (cc the member project's development mailing list), participation in public IRC channels and project mailing lists will all help ensure ongoing commitment to the work. Mentors are required to make sure that happens and that the lines of communication are kept open from beginning to end.

Other possibilities include:
# Having potential students work with their potential mentor to prepare a plan for the implementation of their project.
# Setting milestones that need to be reached by the student. These milestones would be defined before the student's work begins. A student would subsequently write a brief e-mail informing the OSGeo SoC mailing list (cc project-specific mailing list) when they have reached each milestone, giving a brief description of the work completed to that date. This is in addition to the weekly progress reports which are intended to be more casual and actively soliciting feedback.
# Selecting students that have shown previous interest in the geospatial field and free software. A student who already has a (reviewable) FOSS track record has a much higher chance of success.

==What is your plan for dealing with disappearing mentors? (required)==

Project steering committees will appoint replacement mentors if existing mentors become unavailable or unresponsive during the project period. Where possible, we also plan to have backup mentors for projects so the backup mentor can fill in for, or replace the mentor in case of changing circumstances. We also have active administrators who will communicate with students and mentros to be able to help out if there is a problem somewhere.

Among all the OSGeo mailing lists there are 14,000 subscribers, indicating a good pool of people to draw from if required. Due to relatively high member project code and personnel cross-over, in a pinch a mentor from another OSGeo project could usefully help out.

==What steps will you take to encourage students to interact with your community before, during, and after the program? (required)==

The steps taken depend on the individual projects. As an example, last year we required weekly reports and encouraged the students to interact with us on the project mailing lists and IRC channels. We also encourage the developers and users who are not mentors to provide additional advice and feedback to the participating student and help with testing the students contributions during and after the program. In general other developers have not been shy about sharing their opinions, guidance, and advice on the member project development lists.

Furthermore the mentors are encouraged to actively involve the students in the community by having the student interact with the mentor through the community (public) channels rather then one-on-one. This also assists with student integration into the project and alleviates the disappearing-mentor problem.

==What will you do to ensure that your accepted students stick with the project after GSoC concludes? (required)==
The steps taken depend on the individual projects, as example last year many projects asked that students act as a "module maintainer" for their work. This role has an expected level of support associated with it.

Apart from that, we are relying on the open development process and the appreciation that students will receive for implementing these needed features to provide positive feedback for the students. The projects will be encouraging the students to take ownership of their work, and to contribute in other areas they may be interested in. In some cases students may also have opportunities for future contract work if they make a good impression on community members.

==Is there anything else you would like to tell the Google Summer of Code program administration team? (required)==
Thank you for your great work and the great chance to spread Open Source GIS.

==Please select your backup group administrator.==

Backup administrators:
* Hamish Bowman (melange: hamish.bowman)
* Landon Blake (melange: sunburned_surveyor)

[[Category: Google Summer of Code]]

Google Summer of Code 2010 Ideas

2010-03-07T21:45:09Z

Wiki-Wolf: /* The ideas pages */ Removed all projects with no GSoC 2010 Ideas page

[[Image:Google_soc_2010_logo.jpg|center|250px]]

* Back to the main OSGeo [[Google Summer of Code 2010]] wiki page.

=OSGeo Google Summer of Code 2010=

* '''''PRELIMINARY - WE HAVEN'T EVEN APPLIED TO BE IN THE PROGRAM YET THIS YEAR'''''

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 [http://code.google.com/p/google-summer-of-code/wiki/GsocFlyers 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 posted to the soc@osgeo mailing list that at least answers the following questions:
# What did you get done this week?
# What do you plan on doing next week?
# 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 and blogs==
In addition to weekly reports we ask you to maintain a wiki or blog 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.
Wiki or blog space can be provided by OSGeo if your project doesn't have anything already set up for this.

=Timeline=
http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/timeline

* March 18th 2010: Google announces accepted organizations. If OSGeo is accepted as an organization for Google Summer of Code, start talking to us earlier rather than later.
* April 9th 2010: Student application deadline. The earlier you start the more probable it is that you will be accepted! There is two way feedback during the application process which really helps you improve and clarify your application before this final deadline.
* April 26th 2010: Accepted student proposals are announced.
* May 24th 2010: Coding begins!
* July 12-16th: Mid-term evaluation.
* August 9th: Pencils down!

= The ideas pages =
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:

* [http://trac.osgeo.org/gdal/wiki/SummerOfCode 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.
* [http://grass.osgeo.org/wiki/GRASS_SoC_Ideas 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!
* [http://www.mapbender.org/GSoC_2010 Mapbender SoC ideas 2010]: Mapbender is a server and client side geographic data management tool, programmed in '''PHP''' and '''JavaScript''', using the '''jQuery''' library.
* [http://www.qgis.org/wiki/Google_Summer_of_Code_2010 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.
* [http://udig.refractions.net/confluence/display/HACK/Summer+of+Code 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.
* [http://sourceforge.net/apps/mediawiki/jump-pilot/index.php?title=OpenJUMP_Google_Summer_Of_Code 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.

= 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 for project specific lists.

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

irc://irc.freenode.net/#osgeo (Web based [http://irc.telascience.org/cgi-bin/irc.cgi IRC client])

Project irc channels:

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

[[Category:Google Summer of Code]]

Google Summer of Code Application 2010

2010-03-07T20:53:27Z

Wiki-Wolf:

==Link ID==
osgeo

==Group Name (required)==
OSGeo - Open Source Geospatial Foundation

==Home Page URL (required)==
http://www.osgeo.org/

==Public Email (required)==
soc@lists.osgeo.org

==Description (required)==
OSGeo is an incorporated not-for-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and 16 projects in particular:

Web Mapping: '''deegree''', '''Mapbender''', '''MapBuilder''', '''MapGuide Open Source''', '''MapServer''', '''OpenLayers'''

Desktop Applications: '''GRASS GIS''', '''OSSIM''', '''Quantum GIS''', '''gvSIG'''

Geospatial Libraries: '''FDO''', '''GDAL/OGR''', '''GEOS''', '''GeoTools''', '''MetaCRS'''

Metadata Catalog: '''GeoNetwork'''

Other Projects: '''Public Geospatial Data''', '''Education and Curriculum'''

==Why is your group applying to participate? What do you hope to gain by participating? (required)==

We hope to get more students excited about open source geospatial development. This will help to grow the development community and of course tangibly advance particular projects. Additionally by way of the level of exposure that SoC provides we aim to further extend the use, development, and teaching & training of open source GIS at universities worldwide. This will help to prepare a new generation of developers for industry and government agencies capable of introducing and implementing viable open source geospatial technology, to the benefit of all.

==What is the main public mailing list for your group? (required)==
http://wiki.osgeo.org/wiki/Mailing_Lists

==Where is the main IRC channel for your group? (required)==

The primary OSGeo channel is #osgeo on the irc.freenode.net network.

member projects maintain their own IRC channels:
: http://wiki.osgeo.org/wiki/IRC

==What criteria do you use to select the members of your group? Please be as specific as possible. (required)==

The project administrator is appointed by the OSGeo board at the beginning of the year. The project administrator asks for one or two people he trusts to be the backup administrators. Mentors are selected by project steering committees and development teams based on their reputation as skilled developers, domain experience, previously demonstrated ability to support new project developers, and stated willingness to devote time to the mentoring process. We also try very hard to match up the student working on a specific module or tool with a developer with the best expertise in the relevant area. We have in the past not voted up an otherwise good student project if there was no mentor capable of overseeing the project from a technical standpoint. Fortunately we have had a strong response from the developer pool so this has not been a major problem.

==Has your group participated previously? If so, please summarize your involvement and any past successes and failures.==

OSGeo participated in GSoC in 2009. Twelve OSGeo projects participated and were very successful. The applications were of better quality so we had fewer dropouts than the previous year. OSGeo Sent two delegates to the Mentor Summit.

OSGeo participated in GSoC in 2008. Eleven OSGeo projects participated and were in general very successful. OSGeo didn't send delegates to the Mentor Summit due to the busy schedules of the mentors.

See [[SoC Report 2008]] for a full report.

OSGeo participated in GSoC in 2007. Six OSGeo projects participated and were generally very successful. OSGeo also sent one delegate to the Mentor Summit in 2007. See http://wiki.osgeo.org/wiki/SoC_Report_2007 for a full report. We also opened up a demo theatre track highlighting SoC work at our [http://www.foss4g2007.org/ foss4g] conference that year.

OSGeo was formed in early 2006 and did not participate in GSoC prior to 2007. However, Refractions Research did participate in 2006 on behalf of the GeoTools, uDig, and PostGIS projects which now participate through OSGeo. Most of the the previously participating mentors and administrators continue to be involved in this years OSGeo GSoC effort.

==What license does your organization use? (required)==

Each member project uses their own, but all OSGeo projects are required to use an OSI approved license. (see http://www.osgeo.org/incubator/process/evaluation.html)

* Member projects specifically use: GPL >=2, LGPL, MIT/X, ...

==What is the URL to the ideas list of your organization? (required)==
http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2010_Ideas

==What is the main development mailing list for your group? (required)==
http://wiki.osgeo.org/wiki/Mailing_Lists

==What is the application template you would like contributors to your organization to use. (required)==
'''Name:'''

'''Country:'''

'''School and degree:'''

'''Email:'''

'''Phone:'''

'''OSGeo project(s):'''

'''Title:'''

'''Describe your idea'''
# Introduction
# Background
# The idea
# Project plan (how do you plan to spend your summer?)
# Future ideas / How can your idea be expanded?

'''Explain how your SoC task would benefit the OSGeo member project and more generally the OSGeo Foundation as a whole:'''

'''Please provide details of previous GIS experience:'''

'''Please provide details of any previous involvement with GIS programming and other software programming:'''

'''Please provide details of general computing experience: (operating systems you use on a day-to-day basis, languages you could write a program in, hardware, networking experience, etc.)'''

'''Please tell us why you are interested in GIS and open source software:'''

'''Please tell us why you are interested in your specific coding project:'''

'''Please tell us why you are interested in working for OSGeo and the software project you have selected:'''

'''Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?'''

==What is your plan for dealing with disappearing contributors? (required)==
In order to minimize the chance of disappearing students we will ensure that the OSGeo administrative contact and the mentors have full contact information (email, home phone, etc) so that we can keep in touch with them at all times. We also stress to our students that this is a Job, as opposed to a school project.

In addition, we will make our reporting requirements clear up front. Letting the students know that we will require a weekly progress report to be posted to OSGeo's SoC mailing list (cc the member project's development mailing list), participation in public IRC channels and project mailing lists will all help ensure ongoing commitment to the work. Mentors are required to make sure that happens and that the lines of communication are kept open from beginning to end.

Other possibilities include:
# Having potential students work with their potential mentor to prepare a plan for the implementation of their project.
# Setting milestones that need to be reached by the student. These milestones would be defined before the student's work begins. A student would subsequently write a brief e-mail informing the OSGeo SoC mailing list (cc project-specific mailing list) when they have reached each milestone, giving a brief description of the work completed to that date. This is in addition to the weekly progress reports which are intended to be more casual and actively soliciting feedback.
# Selecting students that have shown previous interest in the geospatial field and free software. A student who already has a (reviewable) FOSS track record has a much higher chance of success.

==What is your plan for dealing with disappearing members? (required)==

Project steering committees will appoint replacement mentors if existing mentors become unavailable or unresponsive during the project period. Where possible, we also plan to have backup mentors for projects so the backup mentor can fill in for, or replace the mentor in case of changing circumstances. We also have active administrators who will communicate with students and mentros to be able to help out if there is a problem somewhere.

Among all the OSGeo mailing lists there are 14,000 subscribers, indicating a good pool of people to draw from if required. Due to relatively high member project code and personnel cross-over, in a pinch a mentor from another OSGeo project could usefully help out.

==What steps will you take to encourage contributors to interact with your community before, during, and after the program? (required)==

The steps taken depend on the individual projects. As an example, last year we required weekly reports and encouraged the students to interact with us on the project mailing lists and IRC channels. We also encourage the developers and users who are not mentors to provide additional advice and feedback to the participating student and help with testing the students contributions during and after the program. In general other developers have not been shy about sharing their opinions, guidance, and advice on the member project development lists.

Furthermore the mentors are encouraged to actively involve the students in the community by having the student interact with the mentor through the community (public) channels rather then one-on-one. This also assists with student integration into the project and alleviates the disappearing-mentor problem.

==What will you do to ensure that your accepted contributors stick with the project after the program concludes? (required)==
The steps taken depend on the individual projects, as example last year many projects asked that students act as a "module maintainer" for their work. This role has an expected level of support associated with it.

Apart from that, we are relying on the open development process and the appreciation that students will receive for implementing these needed features to provide positive feedback for the students. The projects will be encouraging the students to take ownership of their work, and to contribute in other areas they may be interested in. In some cases students may also have opportunities for future contract work if they make a good impression on community members.

==Please select your backup group administrator.==

Backup administrators:
* Hamish Bowman (melange: hamish.bowman)
* Landon Blake (melange: sunburned_surveyor)

[[Category: Google Summer of Code]]

Google Summer of Code Application 2010

2010-03-07T20:34:14Z

Wiki-Wolf: /* Has your group participated previously? If so, please summarize your involvement and any past successes and failures. */

==Link ID==
osgeo

==Group Name (required)==
OSGeo - Open Source Geospatial Foundation

==Home Page URL (required)==
http://www.osgeo.org/

==Public Email (required)==
soc@lists.osgeo.org

==Description (required)==
OSGeo is an incorporated not-for-profit organization serving as an umbrella organization for the Open Source Geospatial community in general and 16 projects in particular:

Web Mapping: '''deegree''', '''Mapbender''', '''MapBuilder''', '''MapGuide Open Source''', '''MapServer''', '''OpenLayers'''

Desktop Applications: '''GRASS GIS''', '''OSSIM''', '''Quantum GIS''', '''gvSIG'''

Geospatial Libraries: '''FDO''', '''GDAL/OGR''', '''GEOS''', '''GeoTools''', '''MetaCRS'''

Metadata Catalog: '''GeoNetwork'''

Other Projects: '''Public Geospatial Data''', '''Education and Curriculum'''

==Why is your group applying to participate? What do you hope to gain by participating? (required)==

We hope to get more students excited about open source geospatial development. This will help to grow the development community and of course tangibly advance particular projects. Additionally by way of the level of exposure that SoC provides we aim to further extend the use, development, and teaching & training of open source GIS at universities worldwide. This will help to prepare a new generation of developers for industry and government agencies capable of introducing and implementing viable open source geospatial technology, to the benefit of all.

==What is the main public mailing list for your group? (required)==
http://wiki.osgeo.org/wiki/Mailing_Lists

==Where is the main IRC channel for your group? (required)==

The primary OSGeo channel is #osgeo on the irc.freenode.net network.

member projects maintain their own IRC channels:
: http://wiki.osgeo.org/wiki/IRC

==What criteria do you use to select the members of your group? Please be as specific as possible. (required)==

The project administrator is appointed by the OSGeo board at the beginning of the year. The project administrator asks for one or two people he trusts to be the backup administrators. Mentors are selected by project steering committees and development teams based on their reputation as skilled developers, domain experience, previously demonstrated ability to support new project developers, and stated willingness to devote time to the mentoring process. We also try very hard to match up the student working on a specific module or tool with a developer with the best expertise in the relevant area. We have in the past not voted up an otherwise good student project if there was no mentor capable of overseeing the project from a technical standpoint. Fortunately we have had a strong response from the developer pool so this has not been a major problem.

==Has your group participated previously? If so, please summarize your involvement and any past successes and failures.==

OSGeo participated in GSoC in 2009. Twelve OSGeo projects participated and were very successful. The applications were of better quality so we had fewer dropouts than the previous year. OSGeo Sent two delegates to the Mentor Summit.

OSGeo participated in GSoC in 2008. Eleven OSGeo projects participated and were in general very successful. OSGeo didn't send delegates to the Mentor Summit due to the busy schedules of the mentors.

See [[SoC Report 2008]] for a full report.

OSGeo participated in GSoC in 2007. Six OSGeo projects participated and were generally very successful. OSGeo also sent one delegate to the Mentor Summit in 2007. See http://wiki.osgeo.org/wiki/SoC_Report_2007 for a full report. We also opened up a demo theatre track highlighting SoC work at our [http://www.foss4g2007.org/ foss4g] conference that year.

OSGeo was formed in early 2006 and did not participate in GSoC prior to 2007. However, Refractions Research did participate in 2006 on behalf of the GeoTools, uDig, and PostGIS projects which now participate through OSGeo. Most of the the previously participating mentors and administrators continue to be involved in this years OSGeo GSoC effort.

==What license does your organization use? (required)==

Each member project uses their own, but all OSGeo projects are required to use an OSI approved license. (see http://www.osgeo.org/incubator/process/evaluation.html)

* Member projects specifically use: GPL >=2, LGPL, MIT/X, ...

==What is the URL to the ideas list of your organization? (required)==
http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2009_Ideas

==What is the main development mailing list for your group? (required)==
http://wiki.osgeo.org/wiki/Mailing_Lists

==What is the application template you would like contributors to your organization to use. (required)==
'''Name:'''

'''Country:'''

'''School and degree:'''

'''Email:'''

'''Phone:'''

'''OSGeo project(s):'''

'''Title:'''

'''Describe your idea'''
# Introduction
# Background
# The idea
# Project plan (how do you plan to spend your summer?)
# Future ideas

'''Explain how your SoC task would benefit the OSGeo member project and more generally the OSGeo Foundation as a whole:'''

'''Please provide details of previous GIS experience:'''

'''Please provide details of any previous involvement with GIS programming and other software programming:'''

'''Please provide details of general computing experience: (operating systems you use on a day-to-day basis, languages you could write a program in, hardware, networking experience, etc.)'''

'''Please tell us why you are interested in GIS and open source software:'''

'''Please tell us why you are interested in your specific coding project:'''

'''Please tell us why you are interested in the specific software project that you wish to work with:'''

'''Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?'''

==What is your plan for dealing with disappearing contributors? (required)==
In order to minimize the chance of disappearing students we will ensure that the OSGeo administrative contact and the mentors have full contact information (email, home phone, etc) so that we can keep in touch with them at all times. We also stress to our students that this is a Job, as opposed to a school project.

In addition, we will make our reporting requirements clear up front. Letting the students know that we will require a weekly progress report to be posted to OSGeo's SoC mailing list (cc the member project's development mailing list), participation in public IRC channels and project mailing lists will all help ensure ongoing commitment to the work. Mentors are required to make sure that happens and that the lines of communication are kept open from beginning to end.

Other possibilities include:
# Having potential students work with their potential mentor to prepare a brief plan for the implementation of their project.
# Setting milestones that need to be reached by the student. These milestones would be defined before the student's work begins. A student would subsequently write a brief e-mail informing the OSGeo SoC mailing list (cc project-specific mailing list) when they have reached each milestone, giving a brief description of the work completed to that date. This is in addition to the weekly progress reports which are intended to be more casual and actively soliciting feedback.
# Selecting students that have shown previous interest in the geospatial field and free software. A student who already has a (reviewable) FOSS track record has a much higher chance of success.

==What is your plan for dealing with disappearing members? (required)==

Project steering committees will appoint replacement mentors if existing mentors become unavailable or unresponsive during the project period. Where possible, we also plan to have backup mentors for projects so the backup mentor can fill in for, or replace the mentor in case of changing circumstances.

Among all the OSGeo mailing lists there are 14,000 subscribers, indicating a good pool of people to draw from if required. Due to relatively high member project code and personnel cross-over, in a pinch a mentor from another OSGeo project could usefully help out.

==What steps will you take to encourage contributors to interact with your community before, during, and after the program? (required)==

The steps taken depend on the individual projects. As an example, last year we required weekly reports and encouraged the students to interact with us on the project mailing lists and IRC channels. We also encourage the developers and users who are not mentors to provide additional advice and feedback to the participating student and help with testing the students contributions during and after the program. In general other developers have not been shy about sharing their opinions, guidance, and advice on the member project development lists.

Furthermore the mentors are encouraged to actively involve the students in the community by having the student interact with the mentor through the community (public) channels rather then one-on-one. This also assists with student integration into the project and alleviates the disappearing-mentor problem.

==What will you do to ensure that your accepted contributors stick with the project after the program concludes? (required)==
The steps taken depend on the individual projects, as example last year many projects asked that students act as a "module maintainer" for their work. This role has an expected level of support associated with it.

Apart from that, we are relying on the open development process and the appreciation that students will receive for implementing these needed features to provide positive feedback for the students. The projects will be encouraging the students to take ownership of their work, and to contribute in other areas they may be interested in. In some cases students may also have opportunities for future contract work if they make a good impression on community members.

==Please select your backup group administrator.==

Backup administrators:
* Hamish Bowman (melange: hamish.bowman)
* Landon Blake (melange: sunburned_surveyor)

[[Category: Google Summer of Code]]