OSGeo - User contributions [en]

FOSS4G 2011 Code Sprint

2011-07-21T18:25:07Z

Wiki-Kstreith: /* Workgroups */

== Code Sprint - what's that? ==

A code sprint is about getting a group together to work on Open Source software, sitting around a table and sharing ideas. It's not just about writing code, as you know a project has many needs including documentation, testing, and providing feedback. What a better way to give feedback and give back to the project that you love than to spend a day with the project's developers. There are roles needed to be filled, no matter what your expertise.

With such a short timeframe (one day) you should probably use this page to set a specific goal for your project. But don't worry, if all you get done is actually sitting at the same table with the project's developers and talking about the next release, that is also great :)

== Venue ==

For map and more details see

*Date: '''Saturday September 17th, 2011''' (the day after the conference).
*Time: '''9am-5pm'''  ([http://www.timeanddate.com/worldclock/fixedtime.html?year=2011&month=9&day=17&hour=15&min=0&sec=0 timeandate]) 
*'''Where:''' [http://www.tivoli.org/tivoli/ Tivoli Student Union building] (a former brewery), Auraria Campus
[[Image:Tivoli-logo.jpg|150px]]

Tivoli Student Union
900 Auraria Parkway
Denver, CO
'''[http://www.openstreetmap.org/?lat=39.745249&lon=-105.005806&zoom=18&layers=M OSM map]'''

*'''Rooms: (each room has a 60-70 person capacity)'''
** room 440/540 (bilevel)
** room 640

== What to Bring ==

* power bars (only outlets for 30 computers exist)

== How to get there from the Sheraton ==

* it seems to be 2 miles away...committee is discussing this...or, write you recommended method here.

== Sponsor ==

Please! contact organizers: Rafael Moreno, or [[Jeff McKenna]]

== Questions/Comments/Ideas ==

* ask on the foss4g2011 mailing list ([http://lists.osgeo.org/mailman/listinfo/foss4g2011 subscribe])

== Additional Interested People ==

The following people are potentially interested in participating in sprinting activities though have not yet established a Workgroup.

* name:project

= Workgroups =

To participate, copy a project skeleton and start a section below for your project.

== Project-name ==

'''Attending:'''

* user
* user

'''Goals:'''

* your goals

== MapQuery ==

'''Attending:'''

* [[User:Vmische|Volker Mische]]
* user

'''Goals:'''

* Making MapQUery more awesome
* Talk to OpenLayers 3 people about the future

== PostGIS ==

'''Attending:'''

* Paul Ramsey
* you?

'''Goals:'''

* Close bugs and triage for 2.0 release

== Opticks ==

'''Attending:'''

* Kip Streithorst
* Trevor Clarke
* Michael Considine

'''Goals:'''

* TBD

[[Category:FOSS4G2011]] [[Category:FOSS4G]] [[Category:Code_Sprints]]

Mailing Lists

2011-03-10T21:06:10Z

Wiki-Kstreith:

This is a selection of public OSGeo discussion lists. As of January 2007 all mailing lists managed by OSGeo have been transitioned to Mailman. The list of lists can be found at http://lists.osgeo.org/mailman/listinfo

''' Main announce list'''

* announce@lists.osgeo.org ([http://lists.osgeo.org/mailman/listinfo/announce Subscribe] / [http://lists.osgeo.org/pipermail/announce Archive] )

''' Main discuss list'''

* discuss@lists.osgeo.org ([http://lists.osgeo.org/mailman/listinfo/discuss Subscribe] / [http://lists.osgeo.org/pipermail/discuss Archive] )

''' [[Board of Directors]] list'''

* board@lists.osgeo.org ([http://lists.osgeo.org/mailman/listinfo/board Subscribe] / [http://lists.osgeo.org/pipermail/board Archive] )

'''[[Incubation Committee]] list'''

* incubator@lists.osgeo.org ([http://lists.osgeo.org/mailman/listinfo/incubator Subscribe] / [http://lists.osgeo.org/pipermail/incubator Archive] )

'''[[Marketing Committee]] list'''

* marketing@lists.osgeo.org ([http://lists.osgeo.org/mailman/listinfo/marketing Subscribe] / [http://lists.osgeo.org/pipermail/marketing Archive] )

'''[[Website Committee]] list'''

* webcom@lists.osgeo.org ([http://lists.osgeo.org/mailman/listinfo/webcom Subscribe] / [http://lists.osgeo.org/pipermail/webcom Archive] )

'''[[Public Geospatial Data Committee|Geodata]] list'''

* geodata@lists.osgeo.org ([http://lists.osgeo.org/mailman/listinfo/geodata Subscribe] / [http://lists.osgeo.org/pipermail/geodata Archive] )

'''[[Software Standards|Standards]] list'''

* standards@lists.osgeo.org ([http://lists.osgeo.org/mailman/listinfo/standards Subscribe] / [http://lists.osgeo.org/pipermail/standards Archive] )

'''[[Education and Curriculum Committee]] list'''

* edu_discuss@lists.osgeo.org ([http://lists.osgeo.org/mailman/listinfo/edu_discuss Subscribe] / [http://lists.osgeo.org/pipermail/edu_discuss Archive] )

'''[[Conference Committee|Conferences and Events]]'''

* conference@lists.osgeo.org ([http://lists.osgeo.org/mailman/listinfo/conference_dev Subscribe] / [http://lists.osgeo.org/pipermail/conference_dev Archive] )

'''[[Google Summer of Code]] discussion list'''
* soc@lists.osgeo.org ( [http://lists.osgeo.org/mailman/listinfo/soc Subscribe] / [http://lists.osgeo.org/pipermail/soc Archive] )

'''Project development lists'''

* GeoServer - geoserver-devel@lists.sourceforge.net ( [http://lists.sourceforge.net/lists/listinfo/geoserver-devel Subscribe] / [http://sourceforge.net/mailarchive/forum.php?forum_name=geoserver-devel Archive] )
* GeoTools - geotools-devel@lists.sourceforge.net ( [http://lists.sourceforge.net/lists/listinfo/geotools-devel Subscribe] / [http://sourceforge.net/mailarchive/forum.php?forum_name=geotools-devel Archive] )
* uDig - udig-devel@lists.refractions.net ( [http://lists.refractions.net/mailman/listinfo/udig-devel Subscribe] / [http://lists.refractions.net/pipermail/udig-devel/ Archive] )
* MapGuide - mapguide-internals@lists.osgeo.org ( [http://lists.osgeo.org/mailman/listinfo/mapguide-internals Subscribe] / [http://lists.osgeo.org/pipermail/mapguide-internals Archive] )
* OpenJUMP - jump-pilot-devel@lists.sourceforge.net ( [http://lists.sourceforge.net/lists/listinfo/jump-pilot-devel Subscribe] / [http://sourceforge.net/mailarchive/forum.php?forum_name=jump-pilot-devel Archive] )
* MapServer - mapserver-dev@lists.osgeo.org ( [http://lists.osgeo.org/mailman/listinfo/mapserver-dev Subscribe] / [http://lists.osgeo.org/pipermail/mapserver-dev Archive] )
* GDAL - gdal-dev@lists.osgeo.org ( [http://lists.osgeo.org/mailman/listinfo/gdal-dev Subscribe] / [http://lists.osgeo.org/pipermail/geotools-devel Archive] )
* PostGIS - postgis-users@postgis.refractions.net ( [http://postgis.refractions.net/mailman/listinfo/postgis-users Subscribe] / [http://lists.osgeo.org/pipermail/grass-dev Archive] )
* GRASS - grass-dev@lists.osgeo.org ( [http://lists.osgeo.org/mailman/listinfo/grass-dev Subscribe] / [http://lists.osgeo.org/pipermail/geotools-devel Archive] )
* Quantum GIS - qgis-developer@lists.osgeo.org ( [http://lists.osgeo.org/mailman/listinfo/qgis-developer Subscribe] / [http://lists.osgeo.org/pipermail/qgis-developer Archive] )
* Mapbender - mapbender_dev@lists.osgeo.org ( [http://lists.osgeo.org/mailman/listinfo/mapbender_dev Subscribe] / [http://lists.osgeo.org/pipermail/mapbender_dev Archive] )
* deegree - deegree-devel@lists.sourceforge.net ( [https://lists.sourceforge.net/lists/listinfo/deegree-devel Subscribe] / [http://sourceforge.net/mailarchive/forum.php?forum_name=deegree-devel Archive] )
* OpenLayers - dev@openlayers.org ( [http://openlayers.org/mailman/listinfo/dev Subscribe] / [http://openlayers.org/pipermail/dev/ Archive] )
* gvSIG - gvsig_internacional@listserv.gva.es ( [http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional Subscribe] / [http://listserv.gva.es/pipermail/gvsig_internacional/ Archive] / [http://n2.nabble.com/gvSIG-f2000051.html Nabble archive])
* Opticks Devs - opticks-devs@lists.sourceforge.net ( [http://lists.sourceforge.net/lists/listinfo/opticks-devs Subscribe] / [http://sourceforge.net/mailarchive/forum.php?forum_name=opticks-devs Archive] / [http://opticks-devs.2021163.n4.nabble.com/ Nabble Archive] )
* Opticks Users - opticks-users@lists.sourceforge.net ( [http://lists.sourceforge.net/lists/listinfo/opticks-users Subscribe] / [http://sourceforge.net/mailarchive/forum.php?forum_name=opticks-users Archive] / [http://opticks-users.980204.n3.nabble.com/ Nabble Archive])

[[Category:Board]]
[[Category:Education]]
[[Category:Infrastructure]]

Mailing Lists

2011-03-10T21:04:09Z

Wiki-Kstreith:

This is a selection of public OSGeo discussion lists. As of January 2007 all mailing lists managed by OSGeo have been transitioned to Mailman. The list of lists can be found at http://lists.osgeo.org/mailman/listinfo

''' Main announce list'''

* announce@lists.osgeo.org ([http://lists.osgeo.org/mailman/listinfo/announce Subscribe] / [http://lists.osgeo.org/pipermail/announce Archive] )

''' Main discuss list'''

* discuss@lists.osgeo.org ([http://lists.osgeo.org/mailman/listinfo/discuss Subscribe] / [http://lists.osgeo.org/pipermail/discuss Archive] )

''' [[Board of Directors]] list'''

* board@lists.osgeo.org ([http://lists.osgeo.org/mailman/listinfo/board Subscribe] / [http://lists.osgeo.org/pipermail/board Archive] )

'''[[Incubation Committee]] list'''

* incubator@lists.osgeo.org ([http://lists.osgeo.org/mailman/listinfo/incubator Subscribe] / [http://lists.osgeo.org/pipermail/incubator Archive] )

'''[[Marketing Committee]] list'''

* marketing@lists.osgeo.org ([http://lists.osgeo.org/mailman/listinfo/marketing Subscribe] / [http://lists.osgeo.org/pipermail/marketing Archive] )

'''[[Website Committee]] list'''

* webcom@lists.osgeo.org ([http://lists.osgeo.org/mailman/listinfo/webcom Subscribe] / [http://lists.osgeo.org/pipermail/webcom Archive] )

'''[[Public Geospatial Data Committee|Geodata]] list'''

* geodata@lists.osgeo.org ([http://lists.osgeo.org/mailman/listinfo/geodata Subscribe] / [http://lists.osgeo.org/pipermail/geodata Archive] )

'''[[Software Standards|Standards]] list'''

* standards@lists.osgeo.org ([http://lists.osgeo.org/mailman/listinfo/standards Subscribe] / [http://lists.osgeo.org/pipermail/standards Archive] )

'''[[Education and Curriculum Committee]] list'''

* edu_discuss@lists.osgeo.org ([http://lists.osgeo.org/mailman/listinfo/edu_discuss Subscribe] / [http://lists.osgeo.org/pipermail/edu_discuss Archive] )

'''[[Conference Committee|Conferences and Events]]'''

* conference@lists.osgeo.org ([http://lists.osgeo.org/mailman/listinfo/conference_dev Subscribe] / [http://lists.osgeo.org/pipermail/conference_dev Archive] )

'''[[Google Summer of Code]] discussion list'''
* soc@lists.osgeo.org ( [http://lists.osgeo.org/mailman/listinfo/soc Subscribe] / [http://lists.osgeo.org/pipermail/soc Archive] )

'''Project development lists'''

* GeoServer - geoserver-devel@lists.sourceforge.net ( [http://lists.sourceforge.net/lists/listinfo/geoserver-devel Subscribe] / [http://sourceforge.net/mailarchive/forum.php?forum_name=geoserver-devel Archive] )
* GeoTools - geotools-devel@lists.sourceforge.net ( [http://lists.sourceforge.net/lists/listinfo/geotools-devel Subscribe] / [http://sourceforge.net/mailarchive/forum.php?forum_name=geotools-devel Archive] )
* uDig - udig-devel@lists.refractions.net ( [http://lists.refractions.net/mailman/listinfo/udig-devel Subscribe] / [http://lists.refractions.net/pipermail/udig-devel/ Archive] )
* MapGuide - mapguide-internals@lists.osgeo.org ( [http://lists.osgeo.org/mailman/listinfo/mapguide-internals Subscribe] / [http://lists.osgeo.org/pipermail/mapguide-internals Archive] )
* OpenJUMP - jump-pilot-devel@lists.sourceforge.net ( [http://lists.sourceforge.net/lists/listinfo/jump-pilot-devel Subscribe] / [http://sourceforge.net/mailarchive/forum.php?forum_name=jump-pilot-devel Archive] )
* MapServer - mapserver-dev@lists.osgeo.org ( [http://lists.osgeo.org/mailman/listinfo/mapserver-dev Subscribe] / [http://lists.osgeo.org/pipermail/mapserver-dev Archive] )
* GDAL - gdal-dev@lists.osgeo.org ( [http://lists.osgeo.org/mailman/listinfo/gdal-dev Subscribe] / [http://lists.osgeo.org/pipermail/geotools-devel Archive] )
* PostGIS - postgis-users@postgis.refractions.net ( [http://postgis.refractions.net/mailman/listinfo/postgis-users Subscribe] / [http://lists.osgeo.org/pipermail/grass-dev Archive] )
* GRASS - grass-dev@lists.osgeo.org ( [http://lists.osgeo.org/mailman/listinfo/grass-dev Subscribe] / [http://lists.osgeo.org/pipermail/geotools-devel Archive] )
* Quantum GIS - qgis-developer@lists.osgeo.org ( [http://lists.osgeo.org/mailman/listinfo/qgis-developer Subscribe] / [http://lists.osgeo.org/pipermail/qgis-developer Archive] )
* Mapbender - mapbender_dev@lists.osgeo.org ( [http://lists.osgeo.org/mailman/listinfo/mapbender_dev Subscribe] / [http://lists.osgeo.org/pipermail/mapbender_dev Archive] )
* deegree - deegree-devel@lists.sourceforge.net ( [https://lists.sourceforge.net/lists/listinfo/deegree-devel Subscribe] / [http://sourceforge.net/mailarchive/forum.php?forum_name=deegree-devel Archive] )
* OpenLayers - dev@openlayers.org ( [http://openlayers.org/mailman/listinfo/dev Subscribe] / [http://openlayers.org/pipermail/dev/ Archive] )
* gvSIG - gvsig_internacional@listserv.gva.es ( [http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional Subscribe] / [http://listserv.gva.es/pipermail/gvsig_internacional/ Archive] / [http://n2.nabble.com/gvSIG-f2000051.html Nabble archive])
* Opticks Devs - opticks-devs@lists.sourceforge.net ( [http://lists.sourceforge.net/lists/listinfo/opticks-devs Subscribe] / [http://sourceforge.net/mailarchive/forum.php?forum_name=opticks-devs Archive] )
* Opticks Users - opticks-users@lists.sourceforge.net ( [http://lists.sourceforge.net/lists/listinfo/opticks-users Subscribe] / [http://sourceforge.net/mailarchive/forum.php?forum_name=opticks-users Archive] )

[[Category:Board]]
[[Category:Education]]
[[Category:Infrastructure]]

Google Summer of Code 2011 Ideas

2011-03-10T21:01:00Z

Wiki-Kstreith: /* What is the main IRC channel for your organization? */

[[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=
==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/#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-10T21:00:00Z

Wiki-Kstreith: /* 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=
==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 2011 Ideas

2011-03-10T20:59:23Z

Wiki-Kstreith: /* 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++ as well. 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=
==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]]