OSGeo - User contributions [en]

File:Neo4j-spatial 256.png

2014-02-28T11:34:46Z

Wiki-Craig.taverner: 256x256 image of Neo4j Spatial logo

256x256 image of Neo4j Spatial logo

File:Neo4j-64.png

2014-02-28T11:34:00Z

Wiki-Craig.taverner: 64x64 image of Neo4j logo

64x64 image of Neo4j logo

File:Neo4j-spatial 64.png

2014-02-28T11:33:09Z

Wiki-Craig.taverner: 64x64 image of Neo4j Spatial logo

64x64 image of Neo4j Spatial logo

Google Summer of Code 2014 Ideas

2014-02-28T11:31:29Z

Wiki-Craig.taverner: spacing

[[Image:GoogleSummer_2014logo.jpg|300px|link=http://code.google.com/soc/]] @ [[Image:OSGeo_300_127_pixel.png|link=http://www.osgeo.org]]

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

* See also ideas from [[2007_SoC_Merged_Ideas|2007]], [[2008_SoC_Merged_Ideas|2008]], [[Google_Summer_of_Code_2009_Ideas|2009]], [[Google Summer of Code 2010 Ideas|2010]], [[Google Summer of Code 2011 Ideas|2011]], [[Google Summer of Code 2012 Ideas|2012]], and [[Google Summer of Code 2013 Ideas|2013]].
-----

== OSGeo Google Summer of Code 2014 ==

The [http://www.osgeo.org 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.

* '''Students: If you need more information on how to apply you can contact all the mentoring organisations via the OSGeo-SoC mailing list''' ([[#How to get in contact via mailing lists|see below]])

* 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 and [http://svn.osgeo.org/osgeo/marketing/flyer/google_summer_of_code/OSGeo_GSoC_2014.pdf an OSGeo flavoured one as well].

* Ok, [[OSGeo]] is involved in working with maps and things, but what kind of projects does it really do? Have a look at the [http://planet.osgeo.org/ live blog feed] to see what people are working on right now.

* Mentors, there's an additional link providing some tips and specifying your responsibilities on the main OSGeo [[Google Summer of Code 2014]] wiki page.

== Important dates ==

* [http://www.google-melange.com/gsoc/events/google/gsoc2014 '''The official timeline''']


* February 24: Google announces accepted organizations. {{done}}

: Please start talking to the dev communities you are interested in ''now''.
* March 10: Student applications open.
: 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 the final deadline. The better your involvement with your potential mentors during this period, the better your chances of being selected.''
* March 21: Student application deadline.
* April 21: '''Accepted student proposals are announced and Community Bonding Period begins.'''
* May 19: '''Coding begins!'''
: (''you may unofficially start a week or two earlier if you know you'll have to take a week or two off during The Summer or you'll be sitting finals in the first week(s) of the program. This must be reflected in your application timeline'')
* June 23: Mid-term evaluation begins
* August 11-18: '''Pencils down!'''
* August 18-22: Final evaluations
* August 22: Students begin submitting required code samples to Google
* August 25: Final results announced

== The ideas pages ==
'''''[Check back often, it's a work in progress]'''''

Each participating project's list of ideas is on the respective projects' wikis, with a short description of the project and what type of students would be interested in it:

=== OSGeo Foundation member projects ===

* ''More coming soon: Get started talking to your favorite project's development team today!''

[[Image:logo-grass.png|60px|right]]
* [https://trac.osgeo.org/grass/wiki/GSoC/2014 '''GRASS GIS''' SoC Ideas]: [http://grass.osgeo.org GRASS GIS] is an open source GIS focusing on analysis, modeling and visualization. It is a collection of modules written in C and Python and has a GUI written in wxPython. If you know Python, or want to implement algorithms in C, take a look!

[[Image:logo-qgis.png|60px|right]]
* [http://hub.qgis.org/wiki/quantum-gis/Google_Summer_of_Code_2014 '''QGIS''' SoC Ideas]: [http://www.qgis.org 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. It is written in C++ and Python.

[[Image:logo-gdal.png|60px|right]]

* [http://trac.osgeo.org/gdal/wiki/SummerOfCode '''GDAL''' Ideas]: [http://www.gdal.org GDAL] is a C++ library for reading and writing geospatial data raster and vector formats.



[[Image:logo-gvSIG.png|60px|right]]
* [[GvSIG_GSoC_2014_Ideas|'''gvSIG''' Ideas]]: gvSIG is a free GIS project 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]. The gvSIG project looks for students with Java skills that want to develop new ideas on any of these products.

[[Image:logo-opticks.png|right]]
* [http://opticks.org/confluence/display/opticksDev/Google+Summer+of+Code '''Opticks''' Ideas]: [http://opticks.org/ 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.

[[Image:Osgeolive_60px.png|right]]
* [http://wiki.osgeo.org/wiki/Live_GIS_GSoC_2014 '''OSGeo-Live''' Ideas]: [http://live.osgeo.org OSGeo-Live] packages over 50 of the best geospatial open source projects, preconfigured with data, quickstarts and project overviews. We have packaging and automated build projects. ([[#Which_project_do_I_choose.3F|See below]])

[[Image:logo-postgis.png|60px|right]]
* [http://trac.osgeo.org/postgis/wiki/GoogleSummerCode '''PostGIS''' Ideas]: [http://postgis.net PostGIS] spatially enables the popular PostgreSQL object-relational database, allowing it to be used as a back-end database for geographic information systems (GIS) and web-mapping applications.

[[Image:logo-ossim.png|90px|right]]
* [https://trac.osgeo.org/ossim/wiki/GSoC_2014 '''OSSIM''' SoC Ideas]: [http://trac.osgeo.org/ossim/wiki OSSIM] Open Source Software Image Map (OSSIM) is a high performance engine for remote sensing, image processing, geographical information systems and photogrammetry. The software has been under active development since 1996 and is deployed across a number of private, federal and civilian agencies. It is written in C++.

[[Image:Logo_OTB.png|60px|right]]
* [http://wiki.orfeo-toolbox.org/index.php/GSOC_2014 '''OTB''' SoC Ideas]: [http://www.orfeo-toolbox.org ORFEO ToolBox] (OTB) is an open source library for remote sensing image processing.Targeted algorithms for high resolution optical images (Pleiades, SPOT, QuickBird, WorldView, Landsat, Ikonos), hyperspectral sensors (Hyperion) or SAR (TerraSarX, ERS, Palsar) are available. The software has been under active development since 2006 and is written in C++ and it includes also side projects also open source with GUI like Monteverdi. OTB has recently started the incubation process into OSGeo.

  



=== Guest projects ===

Like-minded geospatial projects to take part under OSGeo umbrella. If you wish your software project to be listed here, please contact Hamish, Anne and Dustan.

[[Image:Logo-osm6.png|60px|right]]
* [http://wiki.openstreetmap.org/wiki/Google_Summer_of_Code/2014/Project_Ideas '''OpenStreetMap''' Ideas]: [http://osm.org/ OSM] is a project aimed squarely at creating and providing free geographic data such as street maps to anyone who wants them. The project was started because most maps you think of as free actually have legal or technical restrictions on their use, holding back people from using them in creative, productive or unexpected ways.
:* ''This year OpenStreetMap students will again be hosted under OSGeo's GSoC umbrella. Talk to OSM, but apply with us. Begin your proposal description with "OSM: " so we know which way to direct it.''

[[Image:Pgrouting-logo.png|60px|right]]

* [https://github.com/pgrouting/pgrouting/wiki/GSOC-Ideas '''pgRouting''' Ideas]: [http://pgrouting.org pgRouting] extends the PostGIS / PostgreSQL geospatial database to provide geospatial routing functionality and more.

[[Image:Pywps-logo.png|60px|right]]

* [https://github.com/jachym/pywps-4/wiki/GSOC-2014-ideas '''PyWPS''' Ideas]: [http://pywps.wald.intevation.org PyWPS] is server implementation of OGC WPS standard on server side using Python programming language. Currently, [http://github.com/jachym/pywps-4/ new version of PyWPS] is being done, were we would like to implement several new attractive features.

* [https://sourceforge.net/p/istsos/wiki/GSoC_ideas_2014/ '''istSOS''' Ideas]: [http://sourceforge.net/projects/istsos/ istSOS] [[Image:Logo-istSOS.png|100px|right]] (Istituto Scienze della Terra Sensor Observation Service) is an implementation of the Sensor Observation Service (SOS) standard from the Open Geospatial Consortium (OGC). The development of istSOS was started in 2009 in order to provide a simple implementation of the SOS standard for the management, provision and integration of hydro-meteorological data collected in Canton Ticino (Switzerland). istSOS is entirely written in Python.

[[Image:logo-uDig.png|60px|right]]
* [https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-Ideas-2014 '''JGrasstools''' and '''uDig''' SoC Ideas]: User-friendly Desktop GIS ([http://udig.github.io/ uDig]) 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.



[[Image:Logo-cartaro.png|60px|right]]
* [https://groups.drupal.org/node/407408 '''Cartaro''' Ideas]: [http://cartaro.org Cartaro] provides geospatial functionality and web services within the Drupal Content Management System (CMS). It is builds upon robust Open Source components: the PostGIS database, GeoServer and GeoWebCache web services, OpenLayers maps in the browser, all managed from within the powerful Drupal CMS.

[[Image:Geonode logo.png|60px|right]]
* [https://github.com/GeoNode/geonode/wiki/Google-Summer-of-Code-Ideas-2014 '''GeoNode''' Ideas]: [http://geonode.org/ GeoNode] is an Open Source Geospatial Content Management System: a web-based application and platform for developing Geospatial Information Systems (GIS) and for deploying spatial data infrastructures (SDI). It is designed to be easily extended and modified, and can be integrated into existing platforms. Written with the Python Django web application, it is based on other great Open Source components such as PostGIS, GeoServer, OpenLayers and GeoExplorer.

[[Image:neo4j-spatial_64.png|right]]
* [https://github.com/neo4j/GSoC/wiki '''Neo4j Spatial''' Ideas]: [https://github.com/neo4j/spatial Neo4j Spatial] is an Open Source library extending the popular [http://neo4j.org Neo4j Graph Database] with a number of features for GIS enabling your data model. It embeds and relies on JTS and GeoTools, and provides the ability to store your domain model in many internal formats, and has utilities for import and export of Shapefiles and OpenStreetMap data. We've received contributions from GSoC projects in 2010, 2011 and 2012.





== Which project do I choose? ==

Most of the software projects are available pre-built on our Live demo { DVD | USB stick | VirtualMachine } with project overviews and short tutorials where you can try everything out.
: View the documents and download the ISO from http://live.osgeo.org
[[File:Osgeolive wordle.png|400px|center]]

== How to get in contact via mailing lists ==

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, as well as the longer list at http://lists.osgeo.org.

== How to get in contact via IRC ==

Primary channel:

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

GSoC @ OSGeo inter-project discussions:

* irc://irc.freenode.net/#osgeo-soc

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/#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/#osgeolive
* irc://irc.freenode.net/#ossimplanet
* irc://irc.freenode.net/#pgrouting-project
* irc://irc.freenode.net/#postgis
* irc://irc.freenode.net/#qgis
* irc://irc.freenode.net/#udig
* irc://irc.oftc.net/#osm-dev

== Application questions we'll ask you ==
'''''[Provisional]'''''

* All questions must be answered, ''no exceptions''. Treat this as something between a formal job application and a scholarship application, because that's exactly what it is.

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 ('''detailed timeline''': 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?

Do you have any known time conflicts during the official coding
period? (May 19 to August 18)

== What to expect during the summer ==

* A group of past GSoC students, mentors, and Googlers have prepared this short book just for you:
: [http://google-opensource.blogspot.com/2011/02/flip-bits-not-burgers-student-guide.html Flip bits not Burgers: The Student's Guide to the Summer of Code] -- READ THIS eBOOK

=== 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 integrate you into the developer community, so you should get involved with them 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, like making sure you get paid.

University exams and semester terms vary widely, if we know ''in advance'' that you need a week off to study, or that you've already scheduled a short vacation to somewhere off the grid, that's fine and won't count against you. But you need to ''communicate'' this up front so we can make a plan to work around it.

=== 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 up front, be honest, and we'll work around it. 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 require 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.

We plan to link all of the students' blogs to the [http://planet.osgeo.org OSGeo Planet] blog aggregator for maximum community exposure and hopefully early feedback from the experts who read it, which may save you a lot of time and trouble if, for example, some obscure wheel has already been invented by another partner project.

Final reports from those blogs and wiki pages will be collected into a OSGeoofcode posting about what everyone did during the summer, ensuring you long lasting fame and fortune. (''Or failing that, a bit of public press, a bit of cash from Google, and a lot of gratitude and kudos from us, your peers.'')

[Back to [[Google Summer of Code 2014]] @ OSGeo]
[[Category: Google Summer of Code]]

Google Summer of Code 2014 Ideas

2014-02-28T11:25:20Z

Wiki-Craig.taverner: Added Neo4j Spatial text

[[Image:GoogleSummer_2014logo.jpg|300px|link=http://code.google.com/soc/]] @ [[Image:OSGeo_300_127_pixel.png|link=http://www.osgeo.org]]

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

* See also ideas from [[2007_SoC_Merged_Ideas|2007]], [[2008_SoC_Merged_Ideas|2008]], [[Google_Summer_of_Code_2009_Ideas|2009]], [[Google Summer of Code 2010 Ideas|2010]], [[Google Summer of Code 2011 Ideas|2011]], [[Google Summer of Code 2012 Ideas|2012]], and [[Google Summer of Code 2013 Ideas|2013]].
-----

== OSGeo Google Summer of Code 2014 ==

The [http://www.osgeo.org 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.

* '''Students: If you need more information on how to apply you can contact all the mentoring organisations via the OSGeo-SoC mailing list''' ([[#How to get in contact via mailing lists|see below]])

* 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 and [http://svn.osgeo.org/osgeo/marketing/flyer/google_summer_of_code/OSGeo_GSoC_2014.pdf an OSGeo flavoured one as well].

* Ok, [[OSGeo]] is involved in working with maps and things, but what kind of projects does it really do? Have a look at the [http://planet.osgeo.org/ live blog feed] to see what people are working on right now.

* Mentors, there's an additional link providing some tips and specifying your responsibilities on the main OSGeo [[Google Summer of Code 2014]] wiki page.

== Important dates ==

* [http://www.google-melange.com/gsoc/events/google/gsoc2014 '''The official timeline''']


* February 24: Google announces accepted organizations. {{done}}

: Please start talking to the dev communities you are interested in ''now''.
* March 10: Student applications open.
: 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 the final deadline. The better your involvement with your potential mentors during this period, the better your chances of being selected.''
* March 21: Student application deadline.
* April 21: '''Accepted student proposals are announced and Community Bonding Period begins.'''
* May 19: '''Coding begins!'''
: (''you may unofficially start a week or two earlier if you know you'll have to take a week or two off during The Summer or you'll be sitting finals in the first week(s) of the program. This must be reflected in your application timeline'')
* June 23: Mid-term evaluation begins
* August 11-18: '''Pencils down!'''
* August 18-22: Final evaluations
* August 22: Students begin submitting required code samples to Google
* August 25: Final results announced

== The ideas pages ==
'''''[Check back often, it's a work in progress]'''''

Each participating project's list of ideas is on the respective projects' wikis, with a short description of the project and what type of students would be interested in it:

=== OSGeo Foundation member projects ===

* ''More coming soon: Get started talking to your favorite project's development team today!''

[[Image:logo-grass.png|60px|right]]
* [https://trac.osgeo.org/grass/wiki/GSoC/2014 '''GRASS GIS''' SoC Ideas]: [http://grass.osgeo.org GRASS GIS] is an open source GIS focusing on analysis, modeling and visualization. It is a collection of modules written in C and Python and has a GUI written in wxPython. If you know Python, or want to implement algorithms in C, take a look!

[[Image:logo-qgis.png|60px|right]]
* [http://hub.qgis.org/wiki/quantum-gis/Google_Summer_of_Code_2014 '''QGIS''' SoC Ideas]: [http://www.qgis.org 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. It is written in C++ and Python.

[[Image:logo-gdal.png|60px|right]]

* [http://trac.osgeo.org/gdal/wiki/SummerOfCode '''GDAL''' Ideas]: [http://www.gdal.org GDAL] is a C++ library for reading and writing geospatial data raster and vector formats.



[[Image:logo-gvSIG.png|60px|right]]
* [[GvSIG_GSoC_2014_Ideas|'''gvSIG''' Ideas]]: gvSIG is a free GIS project 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]. The gvSIG project looks for students with Java skills that want to develop new ideas on any of these products.

[[Image:logo-opticks.png|right]]
* [http://opticks.org/confluence/display/opticksDev/Google+Summer+of+Code '''Opticks''' Ideas]: [http://opticks.org/ 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.

[[Image:Osgeolive_60px.png|right]]
* [http://wiki.osgeo.org/wiki/Live_GIS_GSoC_2014 '''OSGeo-Live''' Ideas]: [http://live.osgeo.org OSGeo-Live] packages over 50 of the best geospatial open source projects, preconfigured with data, quickstarts and project overviews. We have packaging and automated build projects. ([[#Which_project_do_I_choose.3F|See below]])

[[Image:logo-postgis.png|60px|right]]
* [http://trac.osgeo.org/postgis/wiki/GoogleSummerCode '''PostGIS''' Ideas]: [http://postgis.net PostGIS] spatially enables the popular PostgreSQL object-relational database, allowing it to be used as a back-end database for geographic information systems (GIS) and web-mapping applications.

[[Image:logo-ossim.png|90px|right]]
* [https://trac.osgeo.org/ossim/wiki/GSoC_2014 '''OSSIM''' SoC Ideas]: [http://trac.osgeo.org/ossim/wiki OSSIM] Open Source Software Image Map (OSSIM) is a high performance engine for remote sensing, image processing, geographical information systems and photogrammetry. The software has been under active development since 1996 and is deployed across a number of private, federal and civilian agencies. It is written in C++.

[[Image:Logo_OTB.png|60px|right]]
* [http://wiki.orfeo-toolbox.org/index.php/GSOC_2014 '''OTB''' SoC Ideas]: [http://www.orfeo-toolbox.org ORFEO ToolBox] (OTB) is an open source library for remote sensing image processing.Targeted algorithms for high resolution optical images (Pleiades, SPOT, QuickBird, WorldView, Landsat, Ikonos), hyperspectral sensors (Hyperion) or SAR (TerraSarX, ERS, Palsar) are available. The software has been under active development since 2006 and is written in C++ and it includes also side projects also open source with GUI like Monteverdi. OTB has recently started the incubation process into OSGeo.

  



=== Guest projects ===

Like-minded geospatial projects to take part under OSGeo umbrella. If you wish your software project to be listed here, please contact Hamish, Anne and Dustan.

[[Image:Logo-osm6.png|60px|right]]
* [http://wiki.openstreetmap.org/wiki/Google_Summer_of_Code/2014/Project_Ideas '''OpenStreetMap''' Ideas]: [http://osm.org/ OSM] is a project aimed squarely at creating and providing free geographic data such as street maps to anyone who wants them. The project was started because most maps you think of as free actually have legal or technical restrictions on their use, holding back people from using them in creative, productive or unexpected ways.
:* ''This year OpenStreetMap students will again be hosted under OSGeo's GSoC umbrella. Talk to OSM, but apply with us. Begin your proposal description with "OSM: " so we know which way to direct it.''

[[Image:Pgrouting-logo.png|60px|right]]

* [https://github.com/pgrouting/pgrouting/wiki/GSOC-Ideas '''pgRouting''' Ideas]: [http://pgrouting.org pgRouting] extends the PostGIS / PostgreSQL geospatial database to provide geospatial routing functionality and more.

[[Image:Pywps-logo.png|60px|right]]

* [https://github.com/jachym/pywps-4/wiki/GSOC-2014-ideas '''PyWPS''' Ideas]: [http://pywps.wald.intevation.org PyWPS] is server implementation of OGC WPS standard on server side using Python programming language. Currently, [http://github.com/jachym/pywps-4/ new version of PyWPS] is being done, were we would like to implement several new attractive features.

* [https://sourceforge.net/p/istsos/wiki/GSoC_ideas_2014/ '''istSOS''' Ideas]: [http://sourceforge.net/projects/istsos/ istSOS] [[Image:Logo-istSOS.png|100px|right]] (Istituto Scienze della Terra Sensor Observation Service) is an implementation of the Sensor Observation Service (SOS) standard from the Open Geospatial Consortium (OGC). The development of istSOS was started in 2009 in order to provide a simple implementation of the SOS standard for the management, provision and integration of hydro-meteorological data collected in Canton Ticino (Switzerland). istSOS is entirely written in Python.

[[Image:logo-uDig.png|60px|right]]
* [https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-Ideas-2014 '''JGrasstools''' and '''uDig''' SoC Ideas]: User-friendly Desktop GIS ([http://udig.github.io/ uDig]) 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.



[[Image:Logo-cartaro.png|60px|right]]
* [https://groups.drupal.org/node/407408 '''Cartaro''' Ideas]: [http://cartaro.org Cartaro] provides geospatial functionality and web services within the Drupal Content Management System (CMS). It is builds upon robust Open Source components: the PostGIS database, GeoServer and GeoWebCache web services, OpenLayers maps in the browser, all managed from within the powerful Drupal CMS.

[[Image:Geonode logo.png|60px|right]]
* [https://github.com/GeoNode/geonode/wiki/Google-Summer-of-Code-Ideas-2014 '''GeoNode''' Ideas]: [http://geonode.org/ GeoNode] is an Open Source Geospatial Content Management System: a web-based application and platform for developing Geospatial Information Systems (GIS) and for deploying spatial data infrastructures (SDI). It is designed to be easily extended and modified, and can be integrated into existing platforms. Written with the Python Django web application, it is based on other great Open Source components such as PostGIS, GeoServer, OpenLayers and GeoExplorer.

[[Image:neo4j-spatial_64.png|64px|right]]
* [https://github.com/neo4j/GSoC/wiki '''Neo4j Spatial''' Ideas]: [https://github.com/neo4j/spatial Neo4j Spatial] is an Open Source library extending the popular [http://neo4j.org Neo4j Graph Database] with a number of features for GIS enabling your data model. It embeds and relies on JTS and GeoTools, and provides the ability to store your domain model in many internal formats, and has utilities for import and export of Shapefiles and OpenStreetMap data. We've received contributions from GSoC projects in 2010, 2011 and 2012.





== Which project do I choose? ==

Most of the software projects are available pre-built on our Live demo { DVD | USB stick | VirtualMachine } with project overviews and short tutorials where you can try everything out.
: View the documents and download the ISO from http://live.osgeo.org
[[File:Osgeolive wordle.png|400px|center]]

== How to get in contact via mailing lists ==

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, as well as the longer list at http://lists.osgeo.org.

== How to get in contact via IRC ==

Primary channel:

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

GSoC @ OSGeo inter-project discussions:

* irc://irc.freenode.net/#osgeo-soc

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/#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/#osgeolive
* irc://irc.freenode.net/#ossimplanet
* irc://irc.freenode.net/#pgrouting-project
* irc://irc.freenode.net/#postgis
* irc://irc.freenode.net/#qgis
* irc://irc.freenode.net/#udig
* irc://irc.oftc.net/#osm-dev

== Application questions we'll ask you ==
'''''[Provisional]'''''

* All questions must be answered, ''no exceptions''. Treat this as something between a formal job application and a scholarship application, because that's exactly what it is.

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 ('''detailed timeline''': 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?

Do you have any known time conflicts during the official coding
period? (May 19 to August 18)

== What to expect during the summer ==

* A group of past GSoC students, mentors, and Googlers have prepared this short book just for you:
: [http://google-opensource.blogspot.com/2011/02/flip-bits-not-burgers-student-guide.html Flip bits not Burgers: The Student's Guide to the Summer of Code] -- READ THIS eBOOK

=== 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 integrate you into the developer community, so you should get involved with them 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, like making sure you get paid.

University exams and semester terms vary widely, if we know ''in advance'' that you need a week off to study, or that you've already scheduled a short vacation to somewhere off the grid, that's fine and won't count against you. But you need to ''communicate'' this up front so we can make a plan to work around it.

=== 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 up front, be honest, and we'll work around it. 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 require 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.

We plan to link all of the students' blogs to the [http://planet.osgeo.org OSGeo Planet] blog aggregator for maximum community exposure and hopefully early feedback from the experts who read it, which may save you a lot of time and trouble if, for example, some obscure wheel has already been invented by another partner project.

Final reports from those blogs and wiki pages will be collected into a OSGeoofcode posting about what everyone did during the summer, ensuring you long lasting fame and fortune. (''Or failing that, a bit of public press, a bit of cash from Google, and a lot of gratitude and kudos from us, your peers.'')

[Back to [[Google Summer of Code 2014]] @ OSGeo]
[[Category: Google Summer of Code]]

Google Summer of Code 2011 Administrative

2011-03-28T08:51:40Z

Wiki-Craig.taverner: /* 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 ==

* [[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] (seems to have moved to [http://www.google-melange.com/gsoc/request/google/gsoc2011/osgeo])
#* 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 2010 Ideas

2010-03-25T10:26:34Z

Wiki-Craig.taverner: removed 2009 from uDIG link

[[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 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], [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]]

Udig the 10 minutes bug sprint

2009-03-11T15:42:25Z

Wiki-Craig.taverner: Anthony and Frankline are just starting with uDIG, working with Craig Taverner

== Introduction ==

Dear community of udig developers and users (and all osgeo supporters).

We are delighted to propose you '''the 10 minutes bug sprint'''!!

== What is the 10 minutes code sprint? ==

A code sprint in which bugs and feature requests will be fixed that are supposed to take only 10 minutes to the involved developer (in a perfect world).

== What will it gain? ==

* Many small bugs fixed that make users very happy.
* Lots of satisfaction for the developers that are involved that will smash lots of bugs.
* A nice and clean JIRA list.
* All in all a happy community.

== When will it be? ==

The sprint will cover Saturday and Sunday the 14th and 15th of March 2009.
As usual for uDig sprints if not defined else, it will take place in all-around-the-world IRC sessions, with Sydney giving the good start push. :)

== Further informations ==

A cleanup of the JIRA issues list has been started and should be finished in one day or so.

A first result we gained can be seen in [http://jira.codehaus.org/browse/UDIG?report=com.atlassian.jira.plugin.system.project:components-panel the list of components], which has passed from users unreadable format of more than 30 categories to a more content based set of 14 categories.

=== for developers ===

The aim is to isolate a list of bugs with that only caracteristic: it should be solvable in more or less 10 minutes.

Those bugs are going to be marked with '''fix version UDIG 1.2.M3''' and will be available to the developers during the code sprint at [http://jira.codehaus.org/browse/UDIG/fixforversion/14979 this link].

=== for users ===

The aim is that to make it easier for users to report bugs and assigning them to a category. The above linked page shows the list of categories and a funny description through which Jody helps us to decide.

=== for testers ===

We are incurring in many bugs of which we are not sure if they are still bugs. So this time testers will be even more important, in order to go through the bugs list and help to decide if the issue is still a bug or if it can be closed. So please testers, come and help!

== roadmap page ==

Also, a [http://udig.refractions.net/confluence/display/HACK/Road+Map roadmap wiki page] has been setup (still in progress) to keep under control the bugs list and their evolution.

== attending people ==

Please add yourself here in order to know on who we can count on. Any time and any time interval will be of help to the community, so jump by even if you have just a couple of hours!

* Andrea Antonello - devel
* Silvia Franceschi - testing
* Jody - devel
* Emily - devel
* Jesse Eichar - devel
* Craig Taverner - testing (+devel?)
* Anthony Wachira - testing
* Frankline Ogongi - testing
* ...add yourself here

[[Category:FOSS4G]]
[[Category:Code Sprints]]
[[Category:FOSS4G2008]]

Udig the 10 minutes bug sprint

2009-03-09T14:05:09Z

Wiki-Craig.taverner: /* attending people */

== Introduction ==

Dear community of udig developers and users (and all osgeo supporters).

We are delighted to propose you '''the 10 minutes bug sprint'''!!

== What is the 10 minutes code sprint? ==

A code sprint in which bugs and feature requests will be fixed that are supposed to take only 10 minutes to the involved developer (in a perfect world).

== What will it gain? ==

* Many small bugs fixed that make users very happy.
* Lots of satisfaction for the developers that are involved that will smash lots of bugs.
* A nice and clean JIRA list.
* All in all a happy community.

== When will it be? ==

The sprint will cover Saturday and Sunday the 14th and 15th of March 2009.
As usual for uDig sprints if not defined else, it will take place in all-around-the-world IRC sessions, with Sydney giving the good start push. :)

== Further informations ==

A cleanup of the JIRA issues list has been started and should be finished in one day or so.

A first result we gained can be seen in [http://jira.codehaus.org/browse/UDIG?report=com.atlassian.jira.plugin.system.project:components-panel the list of components], which has passed from users unreadable format of more than 30 categories to a more content based set of 14 categories.

=== for developers ===

The aim is to isolate a list of bugs with that only caracteristic: it should be solvable in more or less 10 minutes.

Those bugs are going to be marked with '''fix version UDIG 1.2.M3''' and will be available to the developers during the code sprint at [http://jira.codehaus.org/browse/UDIG/fixforversion/14979 this link].

=== for users ===

The aim is that to make it easier for users to report bugs and assigning them to a category. The above linked page shows the list of categories and a funny description through which Jody helps us to decide.

=== for testers ===

We are incurring in many bugs of which we are not sure if they are still bugs. So this time testers will be even more important, in order to go through the bugs list and help to decide if the issue is still a bug or if it can be closed. So please testers, come and help!

== roadmap page ==

Also, a [http://udig.refractions.net/confluence/display/HACK/Road+Map roadmap wiki page] has been setup (still in progress) to keep under control the bugs list and their evolution.

== attending people ==

Please add yourself here in order to know on who we can count on. Any time and any time interval will be of help to the community, so jump by even if you have just a couple of hours!

* Andrea Antonello - devel
* Silvia Franceschi - testing
* Jody - devel
* Emily - devel
* Jesse Eichar - devel
* Craig Taverner - testing (+devel?)
* ...add yourself here

[[Category:FOSS4G]]
[[Category:Code Sprints]]
[[Category:FOSS4G2008]]