<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.osgeo.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Wiki-Adube</id>
	<title>OSGeo - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.osgeo.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Wiki-Adube"/>
	<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/wiki/Special:Contributions/Wiki-Adube"/>
	<updated>2026-04-12T15:41:15Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.35.9</generator>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=OL3-Google-Maps-GSoC_2017_Ideas&amp;diff=105602</id>
		<title>OL3-Google-Maps-GSoC 2017 Ideas</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=OL3-Google-Maps-GSoC_2017_Ideas&amp;diff=105602"/>
		<updated>2017-03-10T18:19:55Z</updated>

		<summary type="html">&lt;p&gt;Wiki-Adube: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page lists some ideas for the 2017 Google Summer of Code program with [http://mapgears.github.io/ol3-google-maps/ ol3-google-maps], i.e. OLGM.&lt;br /&gt;
&lt;br /&gt;
Your ideas are welcome as well!&lt;br /&gt;
&lt;br /&gt;
== Cleaner way to manage Google Maps layers ==&lt;br /&gt;
&lt;br /&gt;
=== Mentors ===&lt;br /&gt;
&lt;br /&gt;
* Alexandre Dubé&lt;br /&gt;
* Raphaël Gagnon&lt;br /&gt;
&lt;br /&gt;
=== Description ===&lt;br /&gt;
&lt;br /&gt;
The idea is about having a cleaner way to deal with Google Maps layers within the library.  The way it is currently done brings a lot of limitations.  Having a way to deal with those layers without any limitations would be the main goal.&lt;br /&gt;
&lt;br /&gt;
=== Technical Description ===&lt;br /&gt;
&lt;br /&gt;
Here's how the library works: The OpenLayers' map is put on top of the Google Maps map as a control that takes 100% of the map.  The navigation tools of Google Maps are all deactivated.  Those from OpenLayers are active, so zooming or panning the map comes from the navigation tools of OpenLayers.  The synchronization of the animations between Google Maps and OpenLayers is not always perfect.&lt;br /&gt;
&lt;br /&gt;
In an attempt to make the animation more &amp;quot;fluid&amp;quot;, the layers from OpenLayers are rendered by Google Maps instead.  This is a nice feature, but comes with limitations.  For example, in OpenLayers you can create clustered vector features.  This is not managed by the OLGM library, i.e. we would need to make the same thing using the Google Maps API.&lt;br /&gt;
&lt;br /&gt;
Having a cleaner way to deal with Google Maps layers would require a big turnover in the way things are currently managed within the library.  This new &amp;quot;way&amp;quot; would be the one to use from there on, but the &amp;quot;old&amp;quot; way should be kept for backward compatibility support.&lt;br /&gt;
&lt;br /&gt;
=== Expected Outcome ===&lt;br /&gt;
&lt;br /&gt;
* Be able to use OpenLayers with a Google Maps layer without any limitations and with perfect synchronization of the navigation animations.&lt;br /&gt;
* This may require features that are only available in recent browsers&lt;br /&gt;
* It is expected that some older browsers may not be able to support this new feature.&lt;br /&gt;
&lt;br /&gt;
=== Required skills ===&lt;br /&gt;
&lt;br /&gt;
* JavaScript&lt;br /&gt;
* ES6 (ECMAScript 6)&lt;br /&gt;
* OpenLayers&lt;br /&gt;
* Google Maps JavaScript API&lt;br /&gt;
&lt;br /&gt;
=== Difficulty Rating ===&lt;br /&gt;
&lt;br /&gt;
The difficulty can be categorized as &amp;quot;normal&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
=== Tasks ===&lt;br /&gt;
&lt;br /&gt;
Here's a list of tasks that should be accomplished.  Some are not directly linked with the idea, but would make the library more robust and more usable by users.&lt;br /&gt;
&lt;br /&gt;
* have a cleaner way to manage Google Maps layers within OLGM without having to create sibling components within Google Maps&lt;br /&gt;
* ensures the perfect animation synchronization of both OpenLayers and Google Maps while zooming and panning&lt;br /&gt;
* support more features within the library, such as clusters and other features mentioned under the &amp;quot;limitations&amp;quot; of the library&lt;br /&gt;
* convert the code to ES6&lt;br /&gt;
* remove all dependencies to the Closure Library&lt;br /&gt;
* support the latest version of OpenLayers&lt;br /&gt;
* various bug fixes that have been raised on GitHub by users of the library&lt;br /&gt;
* various features that have been asked on GitHub by users of the library&lt;/div&gt;</summary>
		<author><name>Wiki-Adube</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=OL3-Google-Maps-GSoC_2017_Ideas&amp;diff=105601</id>
		<title>OL3-Google-Maps-GSoC 2017 Ideas</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=OL3-Google-Maps-GSoC_2017_Ideas&amp;diff=105601"/>
		<updated>2017-03-10T18:15:57Z</updated>

		<summary type="html">&lt;p&gt;Wiki-Adube: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page lists some ideas for the 2017 Google Summer of Code program with [http://mapgears.github.io/ol3-google-maps/ ol3-google-maps], i.e. OLGM.&lt;br /&gt;
&lt;br /&gt;
Your ideas are welcome as well!&lt;br /&gt;
&lt;br /&gt;
== Cleaner way to manage Google Maps layers ==&lt;br /&gt;
&lt;br /&gt;
=== Mentors ===&lt;br /&gt;
&lt;br /&gt;
* Alexandre Dubé&lt;br /&gt;
* Raphaël Gagnon&lt;br /&gt;
&lt;br /&gt;
=== Description ===&lt;br /&gt;
&lt;br /&gt;
The idea is about having a cleaner way to deal with Google Maps layers within the library.  The way it is currently done brings a lot of limitations.  Having a way to deal with those layers without any limitations would be the main goal.&lt;br /&gt;
&lt;br /&gt;
=== Technical Description ===&lt;br /&gt;
&lt;br /&gt;
Here's how the library works: The OpenLayers' map is put on top of the Google Maps map as a control that takes 100% of the map.  The navigation tools of Google Maps are all deactivated.  Those from OpenLayers are active, so zooming or panning the map comes from the navigation tools of OpenLayers.  The synchronization of the animations between Google Maps and OpenLayers is not always perfect.&lt;br /&gt;
&lt;br /&gt;
In an attempt to make the animation more &amp;quot;fluid&amp;quot;, the layers from OpenLayers are rendered by Google Maps instead.  This is a nice feature, but comes with limitations.  For example, in OpenLayers you can create clustered vector features.  This is not managed by the OLGM library, i.e. we would need to make the same thing using the Google Maps API.&lt;br /&gt;
&lt;br /&gt;
Having a cleaner way to deal with Google Maps layers would require a big turnover in the way things are currently managed within the library.  This new &amp;quot;way&amp;quot; would be the one to use from there on, but the &amp;quot;old&amp;quot; way should be kept for backward compatibility support.&lt;br /&gt;
&lt;br /&gt;
=== Expected Outcome ===&lt;br /&gt;
&lt;br /&gt;
* Be able to use OpenLayers with a Google Maps layer without any limitations and with perfect synchronization of the navigation animations.&lt;br /&gt;
* This may require features that are only available in recent browsers&lt;br /&gt;
* It is expected that some older browsers may not be able to support this new feature.&lt;br /&gt;
&lt;br /&gt;
=== Required skills ===&lt;br /&gt;
&lt;br /&gt;
* JavaScript&lt;br /&gt;
* ES6 (Emma Script 6)&lt;br /&gt;
* OpenLayers&lt;br /&gt;
* Google Maps JavaScript API&lt;br /&gt;
&lt;br /&gt;
=== Difficulty Rating ===&lt;br /&gt;
&lt;br /&gt;
The difficulty can be categorized as &amp;quot;normal&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
=== Tasks ===&lt;br /&gt;
&lt;br /&gt;
Here's a list of tasks that should be accomplished.  Some are not directly linked with the idea, but would make the library more robust and more usable by users.&lt;br /&gt;
&lt;br /&gt;
* have a cleaner way to manage Google Maps layers within OLGM without having to create sibling components within Google Maps&lt;br /&gt;
* ensures the perfect animation synchronization of both OpenLayers and Google Maps while zooming and panning&lt;br /&gt;
* support more features within the library, such as clusters and other features mentioned under the &amp;quot;limitations&amp;quot; of the library&lt;br /&gt;
* convert the code to ES6&lt;br /&gt;
* remove all dependencies to the Closure Library&lt;br /&gt;
* support the latest version of OpenLayers&lt;br /&gt;
* various bug fixes that have been raised on GitHub by users of the library&lt;br /&gt;
* various features that have been asked on GitHub by users of the library&lt;/div&gt;</summary>
		<author><name>Wiki-Adube</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2017_Ideas&amp;diff=105600</id>
		<title>Google Summer of Code 2017 Ideas</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2017_Ideas&amp;diff=105600"/>
		<updated>2017-03-10T15:30:15Z</updated>

		<summary type="html">&lt;p&gt;Wiki-Adube: /* Guest projects */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;center&amp;gt;&lt;br /&gt;
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] &amp;lt;font size=&amp;quot;+3&amp;quot;&amp;gt; @ &amp;lt;/font&amp;gt; &lt;br /&gt;
[[Image:OSGeo_300_127_pixel.png|300px|link=http://www.osgeo.org]]&lt;br /&gt;
&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
-----&lt;br /&gt;
* Back to the main OSGeo [[Google Summer of Code 2017]] wiki page.&lt;br /&gt;
&lt;br /&gt;
* See also ideas from [[Google Summer of Code 2016 Ideas|2016]], [[Google Summer of Code 2015 Ideas|2015]], [[Google Summer of Code 2014 Ideas|2014]], [[Google Summer of Code 2013 Ideas|2013]], [[Google Summer of Code 2012 Ideas|2012]], [[Google Summer of Code 2011 Ideas|2011]], [[Google Summer of Code 2010 Ideas|2010]], [[Google_Summer_of_Code_2009_Ideas|2009]], [[2008_SoC_Merged_Ideas|2008]], [[2007_SoC_Merged_Ideas|2007]].&lt;br /&gt;
-----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== OSGeo Google Summer of Code 2017 ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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 and the future of the geospatial industry; show us what you've got!&lt;br /&gt;
&lt;br /&gt;
* '''Students: check out the [[Google Summer of Code Recommendations for Students]] page. If you need more information on how to apply you can contact all the mentors via the OSGeo-SoC mailing list''' ([[#How to get in contact via mailing lists|see below]]) And look at [https://developers.google.com/open-source/gsoc/help/responsibilities GSoC Roles and Responsibilities ] to understand a successfull teamwork and interplay of project, mentors and students. &lt;br /&gt;
&lt;br /&gt;
* There is a [https://developers.google.com/open-source/soc/resources/flyers Google SoC flyer] to look at and post in appropriate places.&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* Mentors, there's an additional link providing some tips and specifying your responsibilities on the main OSGeo [[Google_Summer_of_Code_2017_Administrative]] wiki page.&lt;br /&gt;
&lt;br /&gt;
== The ideas pages ==&lt;br /&gt;
'''''[Check back often, it's a work in progress]'''''&lt;br /&gt;
&lt;br /&gt;
If you are an OSGeo project lead about to add your page, &amp;lt;strong&amp;gt;please contact the GSoC admin team&amp;lt;/strong&amp;gt; to let them know of your ideas page, by sending an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&lt;br /&gt;
=== OSGeo Foundation member projects ===&lt;br /&gt;
&lt;br /&gt;
''More coming soon: Get started talking to your favorite project's development team today!''&lt;br /&gt;
&lt;br /&gt;
[[Image:logo-grass.png|60px|right]]&lt;br /&gt;
* [https://trac.osgeo.org/grass/wiki/GSoC/2017 '''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!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:logo-qgis.png|60px|right]]&lt;br /&gt;
* [https://hub.qgis.org/wiki/quantum-gis/Google_Summer_of_Code_2017 '''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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-gdal.png|60px|right]]&lt;br /&gt;
* [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.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
* [http://trac.osgeo.org/osgeo4w/wiki/Reports '''OSGeo4W''']: -  OSGeo4W is a binary distribution of a broad set of open source geospatial software for Win32 environments (Windows 7, XP, etc).&lt;br /&gt;
[[Image:Logo-osgeo4w-mini.png|60px|right]]&lt;br /&gt;
:* ''Idea'': We need to extend support to x64 based platforms to handle larger datasets and circumvent memory restrictions. This is a distribution and packaging project which will involve most/all of OSGeo member projects. (''ed. note: keep in mind that to fulfill GSoC requirements each project must have a majority coding component, so lots of scripting, testing, and Makefiles!'')&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Image:logo-gvSIG.png|60px|right]]&lt;br /&gt;
* [[GvSIG_GSoC_2017_Ideas|'''gvSIG''' Ideas]]: gvSIG is a free GIS project for [http://www.gvsig.com/en/web/guest/products/gvsig-desktop Desktop]. The gvSIG project looks for students with Java or Python skills that want to develop new ideas on this software. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:Pycsw-logo.png|60px|right]]&lt;br /&gt;
* [https://github.com/geopython/pycsw/wiki/OSGeo-GSoC#2017'''pycsw''' Ideas]: [http://pycsw.org pycsw] is an OGC CSW server implementation written in Python, and provides a metadata and catalogue component for spatial data infrastructures.  The pycsw project is looking for students interested in Python and search, come join us!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-opticks.png|right]]&lt;br /&gt;
* [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.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!-- &lt;br /&gt;
[[Image:logo-postgis.png|60px|right]] &lt;br /&gt;
* [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.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-ossim.png|90px|right]]&lt;br /&gt;
* [https://trac.osgeo.org/ossim/wiki/GSoC_2015 '''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++.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Logo_OTB.png|60px|right]]&lt;br /&gt;
* [http://wiki.orfeo-toolbox.org/index.php/Proposals_for_GSoC_2015 '''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.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Mapserver.png|100px|right]]&lt;br /&gt;
* [http://wiki.osgeo.org/wiki/MapServer_2015_SOC_Ideas '''Mapserver''' SoC Ideas]: MapServer is a Web Mapping Engine; an Open Source platform for publishing spatial data and interactive mapping applications to the web.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Image:Logo-istSOS.png|100px|right]]&lt;br /&gt;
* [https://sourceforge.net/p/istsos/wiki/GSoC_ideas_2017/ '''istSOS''' Ideas]: [http://sourceforge.net/projects/istsos/ istSOS] is a complete sensor data management system for acquiring, storing and dispatching time-series observations. istSOS is compliant with the Sensor Observation Service (SOS) version 1.0 and 2.0 standard from the Open Geospatial Consortium (OGC) and offers unique extended capabilities to support scientific data analyses (integrated quality assurance, RESTful API, on the fly processing with virtual procedures, remote data aggregation and time-space re-projection etc.). istSOS core libraries are written in Python while it easy to use interface is Web based.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:Pywps logo.png|80px|right]]&lt;br /&gt;
* [https://github.com/geopython/pywps/wiki/GSoC-2017-ideas '''PyWPS''' Ideas]: [http://pywps.org/ PyWPS] is an implementation of the Web Processing Service standard from the Open Geospatial Consortium. PyWPS is written in Python. PyWPS enables integration, publishing and execution of Python processes via the WPS standard.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-geos.png|60px|right]]&lt;br /&gt;
* [http://trac.osgeo.org/geos/wiki/GSoC '''GEOS''' Ideas]: GEOS (Geometry Engine - Open Source) is a C++ port of the JTS Topology Suite (JTS). It includes the OpenGIS Simple Features for SQL spatial predicate functions and spatial operators, as well as specific JTS enhanced topology functions.&lt;br /&gt;
--&amp;gt; &lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-geoserver-crop.png|50px|right]]&lt;br /&gt;
* [https://github.com/geoserver/geoserver/wiki/GSOC-Ideas GSOC Ideas]: [http://live.osgeo.org/en/overview/geoserver_overview.html '''GeoServer'''] is a web server that allows you to serve maps and data from a variety of formats to standard clients such as web browsers and desktop GIS applications.  GeoServer works with the Open Geospatial Consortium (OGC) standards Web Feature Service (WFS), Web Coverage Service (WCS), Web Processing Service (WPS) and Web Map Service (WMS) standards.&lt;br /&gt;
:* The GeoServer team asks applicants to introduce themselves on the geoserver-devel list ( Communicating in public is a key success factor to open source development )&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Geotools-logo.png|50px|right]]&lt;br /&gt;
* [http://docs.codehaus.org/display/GEOTOOLS/Google+Summer+of+Code ''GSOC'']:  [http://live.osgeo.org/en/overview/geotools_overview.html '''GeoTools'''] GeoTools is an open source Java library for working with geospatial data, including both data access, data structures, processing and a powerful rendering engine. GeoTools is a modular library used in a wide range of web service, command line tools and desktop applications.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:ZOO-Project-mini.png|right]]&lt;br /&gt;
* [http://www.zoo-project.org/trac/wiki/ZOO_GSoC_Idea '''ZOO-Project''' Ideas]: [http://www.zoo-project.org ZOO-Project] is a WPS open source project released under a MIT/X-11 style license. It provides support for WPS 1.0.0 and 2.0.0 versions  and is able to handle services implemented in various programming languages.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
We expect ideas also from [http://live.osgeo.org/en/overview/mapbender_overview.html MapBender], [http://live.osgeo.org/en/overview/geomoose_overview.html GeoMOOSE], [http://mapserver.org/ MapServer], ...&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Osgeo-live.png|150px|right]]&lt;br /&gt;
* [http://wiki.osgeo.org/wiki/Live_GIS_GSoC_2016 '''Osgeo-Live''' SoC Ideas]: [http://live.osgeo.org/en/index.html OSGeo-Live] is a self-contained bootable DVD, USB thumb drive or Virtual Machine based on Lubuntu, that allows you to try a wide variety of open source geospatial software without installing anything. It is composed entirely of free software, allowing it to be freely distributed, duplicated and passed around. It provides pre-configured applications for a range of geospatial use cases, including storage, publishing, viewing, analysis and manipulation of data. It also contains sample datasets and documentation.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Guest projects ===&lt;br /&gt;
&lt;br /&gt;
Like-minded geospatial projects to take part under OSGeo umbrella. If you wish your software project to be listed here, please contact the GSoC admin team, by sending an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:Pgrouting-logo.png|60px|right]]&lt;br /&gt;
* [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.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:Nasa meatball logo.png|60px|right]]&lt;br /&gt;
* [[NASA-ESA_WebWorldWind_GSoC_2017_Ideas | '''NASA-ESA Web World Wind''']] Ideas: [https://webworldwind.org/ NASA-ESA Web World Wind] is a 3D virtual globe API for HTML5 and JavaScript.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* [[OL3-Google-Maps-GSoC_2017_Ideas | '''OL3-Google-Maps''']] ideas, [http://mapgears.github.io/ol3-google-maps/ OL3-Google-Maps] is a library that allows the use of the Google Maps API within OpenLayers using JavaScript.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
=== See also ===&lt;br /&gt;
&lt;br /&gt;
Other like minded projects do not participate to GSoC under OSGeo umbrella, but with their own organization. You may want to visit also their page:&lt;br /&gt;
&lt;br /&gt;
[[Image:Logo-osm6.png|60px|right]] &lt;br /&gt;
* [http://wiki.openstreetmap.org/wiki/Google_Summer_of_Code/2015/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.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Don't see in the list the project you're interested in? ===&lt;br /&gt;
&lt;br /&gt;
Contact them in their developers mailing list! Feel free to propose your own idea and get feedback!&lt;br /&gt;
&lt;br /&gt;
== I want to apply as a student ==&lt;br /&gt;
&lt;br /&gt;
Before applying as a student, check out the [[Google Summer of Code Recommendations for Students]] page.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Which project do I choose? ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
: View the documents and download the ISO from http://live.osgeo.org&lt;br /&gt;
[[File:Osgeolive wordle.png|500px|center]]&lt;br /&gt;
&lt;br /&gt;
=== Important dates ===&lt;br /&gt;
&lt;br /&gt;
* [https://developers.google.com/open-source/gsoc/timeline '''The official timeline''']&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- {{done}} --&amp;gt;&lt;br /&gt;
* Feb 27: Google announces accepted organizations.&lt;br /&gt;
: Please start talking to the dev communities you are interested in ''now''.&lt;br /&gt;
* March 20:  Student applications open.&lt;br /&gt;
: The earlier you start the more probable it is that you will be accepted!&lt;br /&gt;
: ''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.''&lt;br /&gt;
* April 3:  Student application deadline.&lt;br /&gt;
* May 4: '''Accepted student proposals are announced and Community Bonding Period begins.'''&lt;br /&gt;
* May 30: '''Coding begins!'''&lt;br /&gt;
: (''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'')&lt;br /&gt;
* June 26 - 30: Phase 1 evaluation &lt;br /&gt;
* July 28: Phase 2 evaluation&lt;br /&gt;
* August 21-29: '''Pencils down!'''&lt;br /&gt;
* August 29 - September 5: Final evaluations&lt;br /&gt;
* September 6: Final results announced&lt;br /&gt;
&lt;br /&gt;
[Back to [[Google Summer of Code 2017]] @ OSGeo]&lt;br /&gt;
[[Category: Google Summer of Code]]&lt;/div&gt;</summary>
		<author><name>Wiki-Adube</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=OL3-Google-Maps-GSoC_2017_Ideas&amp;diff=105599</id>
		<title>OL3-Google-Maps-GSoC 2017 Ideas</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=OL3-Google-Maps-GSoC_2017_Ideas&amp;diff=105599"/>
		<updated>2017-03-10T15:25:19Z</updated>

		<summary type="html">&lt;p&gt;Wiki-Adube: The ideas for the GSoC 2017 with the ol3-google-maps library&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page lists some ideas for the 2017 Google Summer of Code program with OL3-Google-Maps.&lt;br /&gt;
&lt;br /&gt;
== Project Information ==&lt;br /&gt;
&lt;br /&gt;
* Project: [http://mapgears.github.io/ol3-google-maps/ ol3-google-maps]&lt;br /&gt;
* Mentors: Alexandre Dubé, Raphaël Gagnon&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Ideas ==&lt;br /&gt;
&lt;br /&gt;
* have a cleaner way to manage Google Maps layers within OLGM without having to create sibling components within Google Maps&lt;br /&gt;
* ensures the perfect animation synchronization of both OpenLayers and Google Maps while zooming and panning&lt;br /&gt;
* support more features within the library, such as clusters and other features mentioned under the &amp;quot;limitations&amp;quot; of the library&lt;br /&gt;
* convert the code to ES6&lt;br /&gt;
* remove all dependencies to the Closure Library&lt;br /&gt;
* support the latest version of OpenLayers&lt;br /&gt;
* various bug fixes that have been raised on GitHub by users of the library&lt;br /&gt;
* various features that have been asked on GitHub by users of the library&lt;br /&gt;
&lt;br /&gt;
And, of course and most importantly, '''your ideas''' are welcome as well!&lt;/div&gt;</summary>
		<author><name>Wiki-Adube</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2017_Administrative&amp;diff=105568</id>
		<title>Google Summer of Code 2017 Administrative</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2017_Administrative&amp;diff=105568"/>
		<updated>2017-03-08T13:49:37Z</updated>

		<summary type="html">&lt;p&gt;Wiki-Adube: /* Mentors */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;center&amp;gt;&lt;br /&gt;
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] &amp;lt;font size=&amp;quot;+3&amp;quot;&amp;gt; @ &amp;lt;/font&amp;gt; [[Image:OSGeo_300_127_pixel.png|300px|link=http://www.osgeo.org]]&lt;br /&gt;
&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Back to the main OSGeo [[Google Summer of Code 2017]] @ OSGeo wiki page.&lt;br /&gt;
* Visit our [[Google Summer of Code 2017 Ideas]] and our [[Google Summer of Code Recommendations for Students]] pages&lt;br /&gt;
&lt;br /&gt;
This is the central page for OSGeo administrative information in Google Summer of Code 2017.&lt;br /&gt;
&lt;br /&gt;
== GSoC general information ==&lt;br /&gt;
&lt;br /&gt;
* [https://developers.google.com/open-source/gsoc/timeline The official timeline]&lt;br /&gt;
* [https://developers.google.com/open-source/gsoc/faq Google's FAQ on the program]&lt;br /&gt;
* [https://developers.google.com/open-source/gsoc/ Official 2017 GSoC site]&lt;br /&gt;
* [https://developers.google.com/open-source/gsoc/help/responsibilities Roles and Responsibilities]&lt;br /&gt;
&lt;br /&gt;
== Contacts == &lt;br /&gt;
&lt;br /&gt;
* Would-be mentors and students: you are invited to sign up to the [http://lists.osgeo.org/mailman/listinfo/soc OSGeo SoC mailing list] right away. The list is the central communication channel for mentors, students and administrators. It is used for general GSoC announcements, specific OSGeo announcements, and for clarification about the program. As soon as you subscribe it, you are encouraged to introduce yourself and your role. We look forward to hear from you!&lt;br /&gt;
&lt;br /&gt;
* To contact OSGeo's GSoC admin team directly:&lt;br /&gt;
** send an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]&lt;br /&gt;
** join the #osgeo-gsoc channel on irc.freenode.net (connect directly in your browser via [https://webchat.freenode.net/?channels=osgeo-gsoc webchat])&lt;br /&gt;
&lt;br /&gt;
* [[User:Madi|Margherita Di Leo]] acts as chair of the Admin team, which includes [[User:Masterflorin|Florin-Daniel Cioloboc]], [[User:Aghisla|Anne Ghisla]], [[Helmut Kudrnovsky]], [[User:Macho|Werner Macho]], [[Jeff McKenna]], and Guillermo Pizarro. Feel free to email us with any questions, we're here to help mentor the mentors as much as anything else!&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Admins: please add your pictures here --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Image:Madi_BW_1.jpg|x100px|link=https://wiki.osgeo.org/wiki/User:Madi|Margherita Di Leo]][[Image:FlorinCioloboc.jpg|x100px|link=https://wiki.osgeo.org/wiki/User:Masterflorin|Florin Cioloboc]][[Image:Aghisla-profile-pic.jpg|x100px|link=https://wiki.osgeo.org/wiki/User:Aghisla|Anne Ghisla]][[Image:Hk grey.png|x100px|link=https://wiki.osgeo.org/wiki/Helmut_Kudrnovsky|Helmut Kudrnovsky]][[Image:Macho.jpg|x100px|link=https://wiki.osgeo.org/index.php?title=Werner_Macho|Werner Macho]][[Image:Jeff_McKenna.jpg|x100px|link=https://wiki.osgeo.org/index.php?title=Jeff_McKenna|Jeff McKenna]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
.&lt;br /&gt;
&lt;br /&gt;
== Mentors ==&lt;br /&gt;
&lt;br /&gt;
If you're interested in mentoring / supervising a student for one of the software participating this year under OSGeo's umbrella, please add your name, email, OSGeo/guest software and the projects you're interested in mentoring here:&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable sortable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;4&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#D7E3D1; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|width=30px|'''Number'''&lt;br /&gt;
|width=100px|'''Name'''&lt;br /&gt;
|width=100px|'''Surname'''&lt;br /&gt;
|width=100px|'''Nickname (IRC)'''&lt;br /&gt;
|width=250px|'''email'''&lt;br /&gt;
|'''Software community'''&lt;br /&gt;
|'''Idea(s) you are available to mentor''' (please write down the title of the idea, not link to ideas page!)&lt;br /&gt;
|-&lt;br /&gt;
|1&lt;br /&gt;
|Tom&lt;br /&gt;
|Kralidis&lt;br /&gt;
|tomkralidis&lt;br /&gt;
|tomkralidis at gmail.com&lt;br /&gt;
|pycsw&lt;br /&gt;
|[https://github.com/geopython/pycsw/wiki/OSGeo-GSoC#2017 pycsw filter abstraction, Elasticsearch backend, admin HTTP API] &lt;br /&gt;
|-&lt;br /&gt;
|2&lt;br /&gt;
|Gabriele&lt;br /&gt;
|Prestifilippo&lt;br /&gt;
|gabry501&lt;br /&gt;
|gabriele.prestifilippo at gmail com&lt;br /&gt;
|ESA-NASA WebWorldWind&lt;br /&gt;
|HeatMap Layer, Plug-in, Create Your Own&lt;br /&gt;
|-&lt;br /&gt;
|3&lt;br /&gt;
|Vicky&lt;br /&gt;
|Vergara&lt;br /&gt;
|cvvergara&lt;br /&gt;
|vicky at georepublic de&lt;br /&gt;
|pgRouting&lt;br /&gt;
|Develop new functionality into pgRouting&lt;br /&gt;
|-&lt;br /&gt;
|4&lt;br /&gt;
|Daniel&lt;br /&gt;
|Kastl&lt;br /&gt;
|dkastl&lt;br /&gt;
|daniel at georepublic de&lt;br /&gt;
|pgRouting&lt;br /&gt;
|Connect more boost functions to pgRouting&lt;br /&gt;
|-&lt;br /&gt;
|5&lt;br /&gt;
|Rohith&lt;br /&gt;
|Reddy&lt;br /&gt;
|sankepallyrohithreddy&lt;br /&gt;
|rohithreddy2219 at gmail com&lt;br /&gt;
|pgRouting&lt;br /&gt;
|Connect more boost functions to pgRouting&lt;br /&gt;
|-&lt;br /&gt;
|6&lt;br /&gt;
|Patrick&lt;br /&gt;
|Hogan&lt;br /&gt;
|HamletAlive&lt;br /&gt;
|patrick.hogan at nasa gov&lt;br /&gt;
|ESA-NASA WebWorldWind&lt;br /&gt;
|CitySmart Urban Infrastructure Management&lt;br /&gt;
|-&lt;br /&gt;
|7&lt;br /&gt;
|Anna&lt;br /&gt;
|Petrasova&lt;br /&gt;
|&lt;br /&gt;
|kratochanna at gmail com&lt;br /&gt;
|GRASS GIS&lt;br /&gt;
|3D rendering, 3D viewer&lt;br /&gt;
|-&lt;br /&gt;
|8&lt;br /&gt;
|Vaclav&lt;br /&gt;
|Petras&lt;br /&gt;
|&lt;br /&gt;
|wenzeslaus at gmail com&lt;br /&gt;
|GRASS GIS&lt;br /&gt;
|Jupyter Notebook, Benchmarking, Testing, ...&lt;br /&gt;
|-&lt;br /&gt;
|9&lt;br /&gt;
|Jakub&lt;br /&gt;
|Balhar&lt;br /&gt;
|&lt;br /&gt;
|jakub at balhar net&lt;br /&gt;
|ESA-NASA WebWorldWind&lt;br /&gt;
|CitySmart Urban Infrastructure Management&lt;br /&gt;
|-&lt;br /&gt;
|10&lt;br /&gt;
|Alexandre&lt;br /&gt;
|Dubé&lt;br /&gt;
|&lt;br /&gt;
|adube at mapgears com&lt;br /&gt;
|OL3-Google-Maps&lt;br /&gt;
|Develop new features in the OL3-Google-Maps library&lt;br /&gt;
|-&lt;br /&gt;
|11&lt;br /&gt;
|Raphaël&lt;br /&gt;
|Gagnon&lt;br /&gt;
|&lt;br /&gt;
|rgagnon at mapgears com&lt;br /&gt;
|OL3-Google-Maps&lt;br /&gt;
|Develop new features in the OL3-Google-Maps library&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
| &lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== A Mentor's Responsibilities ==&lt;br /&gt;
&lt;br /&gt;
Being a mentor can take anywhere from 2-10 hours a week of your time depending on the student (it really ''is'' in your best interest to take on the strongest students you can find). You must have the time to be responsive and an advocate for the student. No matter how cool the project is and how much your team needs the job done, if you can't commit to supporting it, experience shows that the best thing to do is not start it, i.e. even with the best of intentions don't set a student up to fail. Long story short, student projects simply can't go ahead without proper mentoring support.&lt;br /&gt;
&lt;br /&gt;
Every student project will also have a '''backup mentor''', this person should come from your dev community and should at minimum keep up to date with the student's weekly developments. ''' Both mentors need to appoint themselves officially'''. The best way is if the student is well integrated into your development team from the start, it lessens the workload on you and betters the buy-in from the rest of the community once you're ready for the final code merge.&lt;br /&gt;
&lt;br /&gt;
You '''must''' be available at some time during the '''evaluation periods'''. If you will be away during these time periods please arrange with the OSGeo org admins and your backup mentor so that one of us can fill in your answers for you. These are hard cutoffs -- evaluations ''must'' be filed within these dates. There are '''3 evaluation periods''' this year where mentors are required to complete an evaluation of their student. After the first 4 weeks of coding, after 8 weeks of coding and then at the end (after 12 weeks of coding). The evaluation forms are shorter than previous years so they should take less time to complete.&lt;br /&gt;
&lt;br /&gt;
== Guides for mentors ==&lt;br /&gt;
&lt;br /&gt;
* [http://write.flossmanuals.net/gsoc-mentoring/what-is-gsoc/ The GSoC Mentoring Guide] - A must. Do get all useful info and tips from many years of experience from GSoC mentors.&lt;br /&gt;
* [http://people.gnome.org/~federico/docs/summer-of-code-mentoring-howto/ GNOME GSoC Mentoring HOWTO]&lt;br /&gt;
* [http://emptysqua.re/blog/mentoring/ An excellent summary of mentoring, from A. Jesse Jiryu Davis]&lt;br /&gt;
&lt;br /&gt;
== Tips for mentors ==&lt;br /&gt;
&lt;br /&gt;
This section is for collecting suggestions on best practices, from mentors to other mentors. If you have good / bad experiences in mentoring, please share here! Remember that this is a public page, respect the privacy of the people.&lt;br /&gt;
&lt;br /&gt;
=== Good ideas ===&lt;br /&gt;
&lt;br /&gt;
* '''Test students before selection.''' Challenge them with small programming tasks or bug fixes. This will help them getting familiar with the dev environment well before GSoC starts, and helps mentors understand if they are capable. Think to a task much earlier to the timeline, and connect the task to the idea in the ideas page. &lt;br /&gt;
* Time management tip: Try not to mentor more than one project per year. In any case, '''you can be primary mentor only for one project.''' Consider carefully the time that you can allocate on GSoC.&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
=== Bad ideas ===&lt;br /&gt;
&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
== Learn more ==&lt;br /&gt;
&lt;br /&gt;
* Previous years SoC involvement: [https://summerofcode.withgoogle.com/archive/2016/organizations/6434461499523072/ 2016] [https://www.google-melange.com/archive/gsoc/2015 2015], [https://www.google-melange.com/archive/gsoc/2014 2014], [https://www.google-melange.com/archive/gsoc/2013 2013], [https://www.google-melange.com/archive/gsoc/2012 2012], [https://www.google-melange.com/archive/gsoc/2011 2011], [https://www.google-melange.com/archive/gsoc/2010 2010], [https://www.google-melange.com/archive/gsoc/2009 2009], [http://code.google.com/soc/2008/osgeo/about.html 2008]&lt;br /&gt;
&lt;br /&gt;
* OSGeo GSoC wiki pages: [[Google Summer of Code 2016|2016]],[[Google Summer of Code 2015|2015]],[[Google Summer of Code 2014|2014]],[[Google Summer of Code 2013|2013]],[[Google Summer of Code 2012|2012]],[[Google Summer of Code 2011|2011]],[[Google Summer of Code 2010|2010]],[[Google Summer of Code 2009|2009]],[[Google Summer of Code 2008|2008]]&lt;br /&gt;
&lt;br /&gt;
* OSGeo Applications: [[Google Summer of Code Application 2016|2016]],[[Google Summer of Code Application 2015|2015]],[[Google Summer of Code Application 2014|2014]],[[Google Summer of Code Application 2013|2013]],[[Google Summer of Code Application 2012|2012]],[[Google Summer of Code Application 2011|2011]],[[Google SoC Application 2010|2010]],[[Google SoC Application 2009|2009]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category: Google Summer of Code]]&lt;/div&gt;</summary>
		<author><name>Wiki-Adube</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2017_Administrative&amp;diff=105567</id>
		<title>Google Summer of Code 2017 Administrative</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2017_Administrative&amp;diff=105567"/>
		<updated>2017-03-08T13:28:13Z</updated>

		<summary type="html">&lt;p&gt;Wiki-Adube: /* Mentors */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;center&amp;gt;&lt;br /&gt;
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] &amp;lt;font size=&amp;quot;+3&amp;quot;&amp;gt; @ &amp;lt;/font&amp;gt; [[Image:OSGeo_300_127_pixel.png|300px|link=http://www.osgeo.org]]&lt;br /&gt;
&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Back to the main OSGeo [[Google Summer of Code 2017]] @ OSGeo wiki page.&lt;br /&gt;
* Visit our [[Google Summer of Code 2017 Ideas]] and our [[Google Summer of Code Recommendations for Students]] pages&lt;br /&gt;
&lt;br /&gt;
This is the central page for OSGeo administrative information in Google Summer of Code 2017.&lt;br /&gt;
&lt;br /&gt;
== GSoC general information ==&lt;br /&gt;
&lt;br /&gt;
* [https://developers.google.com/open-source/gsoc/timeline The official timeline]&lt;br /&gt;
* [https://developers.google.com/open-source/gsoc/faq Google's FAQ on the program]&lt;br /&gt;
* [https://developers.google.com/open-source/gsoc/ Official 2017 GSoC site]&lt;br /&gt;
* [https://developers.google.com/open-source/gsoc/help/responsibilities Roles and Responsibilities]&lt;br /&gt;
&lt;br /&gt;
== Contacts == &lt;br /&gt;
&lt;br /&gt;
* Would-be mentors and students: you are invited to sign up to the [http://lists.osgeo.org/mailman/listinfo/soc OSGeo SoC mailing list] right away. The list is the central communication channel for mentors, students and administrators. It is used for general GSoC announcements, specific OSGeo announcements, and for clarification about the program. As soon as you subscribe it, you are encouraged to introduce yourself and your role. We look forward to hear from you!&lt;br /&gt;
&lt;br /&gt;
* To contact OSGeo's GSoC admin team directly:&lt;br /&gt;
** send an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]&lt;br /&gt;
** join the #osgeo-gsoc channel on irc.freenode.net (connect directly in your browser via [https://webchat.freenode.net/?channels=osgeo-gsoc webchat])&lt;br /&gt;
&lt;br /&gt;
* [[User:Madi|Margherita Di Leo]] acts as chair of the Admin team, which includes [[User:Masterflorin|Florin-Daniel Cioloboc]], [[User:Aghisla|Anne Ghisla]], [[Helmut Kudrnovsky]], [[User:Macho|Werner Macho]], [[Jeff McKenna]], and Guillermo Pizarro. Feel free to email us with any questions, we're here to help mentor the mentors as much as anything else!&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Admins: please add your pictures here --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Image:Madi_BW_1.jpg|x100px|link=https://wiki.osgeo.org/wiki/User:Madi|Margherita Di Leo]][[Image:FlorinCioloboc.jpg|x100px|link=https://wiki.osgeo.org/wiki/User:Masterflorin|Florin Cioloboc]][[Image:Aghisla-profile-pic.jpg|x100px|link=https://wiki.osgeo.org/wiki/User:Aghisla|Anne Ghisla]][[Image:Hk grey.png|x100px|link=https://wiki.osgeo.org/wiki/Helmut_Kudrnovsky|Helmut Kudrnovsky]][[Image:Macho.jpg|x100px|link=https://wiki.osgeo.org/index.php?title=Werner_Macho|Werner Macho]][[Image:Jeff_McKenna.jpg|x100px|link=https://wiki.osgeo.org/index.php?title=Jeff_McKenna|Jeff McKenna]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
.&lt;br /&gt;
&lt;br /&gt;
== Mentors ==&lt;br /&gt;
&lt;br /&gt;
If you're interested in mentoring / supervising a student for one of the software participating this year under OSGeo's umbrella, please add your name, email, OSGeo/guest software and the projects you're interested in mentoring here:&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable sortable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;4&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#D7E3D1; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|width=30px|'''Number'''&lt;br /&gt;
|width=100px|'''Name'''&lt;br /&gt;
|width=100px|'''Surname'''&lt;br /&gt;
|width=100px|'''Nickname (IRC)'''&lt;br /&gt;
|width=250px|'''email'''&lt;br /&gt;
|'''Software community'''&lt;br /&gt;
|'''Idea(s) you are available to mentor''' (please write down the title of the idea, not link to ideas page!)&lt;br /&gt;
|-&lt;br /&gt;
|1&lt;br /&gt;
|Tom&lt;br /&gt;
|Kralidis&lt;br /&gt;
|tomkralidis&lt;br /&gt;
|tomkralidis at gmail.com&lt;br /&gt;
|pycsw&lt;br /&gt;
|[https://github.com/geopython/pycsw/wiki/OSGeo-GSoC#2017 pycsw filter abstraction, Elasticsearch backend, admin HTTP API] &lt;br /&gt;
|-&lt;br /&gt;
|2&lt;br /&gt;
|Gabriele&lt;br /&gt;
|Prestifilippo&lt;br /&gt;
|gabry501&lt;br /&gt;
|gabriele.prestifilippo at gmail com&lt;br /&gt;
|ESA-NASA WebWorldWind&lt;br /&gt;
|HeatMap Layer, Plug-in, Create Your Own&lt;br /&gt;
|-&lt;br /&gt;
|3&lt;br /&gt;
|Vicky&lt;br /&gt;
|Vergara&lt;br /&gt;
|cvvergara&lt;br /&gt;
|vicky at georepublic de&lt;br /&gt;
|pgRouting&lt;br /&gt;
|Develop new functionality into pgRouting&lt;br /&gt;
|-&lt;br /&gt;
|4&lt;br /&gt;
|Daniel&lt;br /&gt;
|Kastl&lt;br /&gt;
|dkastl&lt;br /&gt;
|daniel at georepublic de&lt;br /&gt;
|pgRouting&lt;br /&gt;
|Connect more boost functions to pgRouting&lt;br /&gt;
|-&lt;br /&gt;
|5&lt;br /&gt;
|Rohith&lt;br /&gt;
|Reddy&lt;br /&gt;
|sankepallyrohithreddy&lt;br /&gt;
|rohithreddy2219 at gmail com&lt;br /&gt;
|pgRouting&lt;br /&gt;
|Connect more boost functions to pgRouting&lt;br /&gt;
|-&lt;br /&gt;
|6&lt;br /&gt;
|Patrick&lt;br /&gt;
|Hogan&lt;br /&gt;
|HamletAlive&lt;br /&gt;
|patrick.hogan at nasa gov&lt;br /&gt;
|ESA-NASA WebWorldWind&lt;br /&gt;
|CitySmart Urban Infrastructure Management&lt;br /&gt;
|-&lt;br /&gt;
|7&lt;br /&gt;
|Anna&lt;br /&gt;
|Petrasova&lt;br /&gt;
|&lt;br /&gt;
|kratochanna at gmail com&lt;br /&gt;
|GRASS GIS&lt;br /&gt;
|3D rendering, 3D viewer&lt;br /&gt;
|-&lt;br /&gt;
|8&lt;br /&gt;
|Vaclav&lt;br /&gt;
|Petras&lt;br /&gt;
|&lt;br /&gt;
|wenzeslaus at gmail com&lt;br /&gt;
|GRASS GIS&lt;br /&gt;
|Jupyter Notebook, Benchmarking, Testing, ...&lt;br /&gt;
|-&lt;br /&gt;
|9&lt;br /&gt;
|Jakub&lt;br /&gt;
|Balhar&lt;br /&gt;
|&lt;br /&gt;
|jakub at balhar net&lt;br /&gt;
|ESA-NASA WebWorldWind&lt;br /&gt;
|CitySmart Urban Infrastructure Management&lt;br /&gt;
|-&lt;br /&gt;
|10&lt;br /&gt;
|Alexandre&lt;br /&gt;
|Dubé&lt;br /&gt;
|&lt;br /&gt;
|adube at mapgears com&lt;br /&gt;
|OL3-Google-Maps&lt;br /&gt;
|Develop new features in the OL3-Google-Maps library&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
| &lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== A Mentor's Responsibilities ==&lt;br /&gt;
&lt;br /&gt;
Being a mentor can take anywhere from 2-10 hours a week of your time depending on the student (it really ''is'' in your best interest to take on the strongest students you can find). You must have the time to be responsive and an advocate for the student. No matter how cool the project is and how much your team needs the job done, if you can't commit to supporting it, experience shows that the best thing to do is not start it, i.e. even with the best of intentions don't set a student up to fail. Long story short, student projects simply can't go ahead without proper mentoring support.&lt;br /&gt;
&lt;br /&gt;
Every student project will also have a '''backup mentor''', this person should come from your dev community and should at minimum keep up to date with the student's weekly developments. ''' Both mentors need to appoint themselves officially'''. The best way is if the student is well integrated into your development team from the start, it lessens the workload on you and betters the buy-in from the rest of the community once you're ready for the final code merge.&lt;br /&gt;
&lt;br /&gt;
You '''must''' be available at some time during the '''evaluation periods'''. If you will be away during these time periods please arrange with the OSGeo org admins and your backup mentor so that one of us can fill in your answers for you. These are hard cutoffs -- evaluations ''must'' be filed within these dates. There are '''3 evaluation periods''' this year where mentors are required to complete an evaluation of their student. After the first 4 weeks of coding, after 8 weeks of coding and then at the end (after 12 weeks of coding). The evaluation forms are shorter than previous years so they should take less time to complete.&lt;br /&gt;
&lt;br /&gt;
== Guides for mentors ==&lt;br /&gt;
&lt;br /&gt;
* [http://write.flossmanuals.net/gsoc-mentoring/what-is-gsoc/ The GSoC Mentoring Guide] - A must. Do get all useful info and tips from many years of experience from GSoC mentors.&lt;br /&gt;
* [http://people.gnome.org/~federico/docs/summer-of-code-mentoring-howto/ GNOME GSoC Mentoring HOWTO]&lt;br /&gt;
* [http://emptysqua.re/blog/mentoring/ An excellent summary of mentoring, from A. Jesse Jiryu Davis]&lt;br /&gt;
&lt;br /&gt;
== Tips for mentors ==&lt;br /&gt;
&lt;br /&gt;
This section is for collecting suggestions on best practices, from mentors to other mentors. If you have good / bad experiences in mentoring, please share here! Remember that this is a public page, respect the privacy of the people.&lt;br /&gt;
&lt;br /&gt;
=== Good ideas ===&lt;br /&gt;
&lt;br /&gt;
* '''Test students before selection.''' Challenge them with small programming tasks or bug fixes. This will help them getting familiar with the dev environment well before GSoC starts, and helps mentors understand if they are capable. Think to a task much earlier to the timeline, and connect the task to the idea in the ideas page. &lt;br /&gt;
* Time management tip: Try not to mentor more than one project per year. In any case, '''you can be primary mentor only for one project.''' Consider carefully the time that you can allocate on GSoC.&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
=== Bad ideas ===&lt;br /&gt;
&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
== Learn more ==&lt;br /&gt;
&lt;br /&gt;
* Previous years SoC involvement: [https://summerofcode.withgoogle.com/archive/2016/organizations/6434461499523072/ 2016] [https://www.google-melange.com/archive/gsoc/2015 2015], [https://www.google-melange.com/archive/gsoc/2014 2014], [https://www.google-melange.com/archive/gsoc/2013 2013], [https://www.google-melange.com/archive/gsoc/2012 2012], [https://www.google-melange.com/archive/gsoc/2011 2011], [https://www.google-melange.com/archive/gsoc/2010 2010], [https://www.google-melange.com/archive/gsoc/2009 2009], [http://code.google.com/soc/2008/osgeo/about.html 2008]&lt;br /&gt;
&lt;br /&gt;
* OSGeo GSoC wiki pages: [[Google Summer of Code 2016|2016]],[[Google Summer of Code 2015|2015]],[[Google Summer of Code 2014|2014]],[[Google Summer of Code 2013|2013]],[[Google Summer of Code 2012|2012]],[[Google Summer of Code 2011|2011]],[[Google Summer of Code 2010|2010]],[[Google Summer of Code 2009|2009]],[[Google Summer of Code 2008|2008]]&lt;br /&gt;
&lt;br /&gt;
* OSGeo Applications: [[Google Summer of Code Application 2016|2016]],[[Google Summer of Code Application 2015|2015]],[[Google Summer of Code Application 2014|2014]],[[Google Summer of Code Application 2013|2013]],[[Google Summer of Code Application 2012|2012]],[[Google Summer of Code Application 2011|2011]],[[Google SoC Application 2010|2010]],[[Google SoC Application 2009|2009]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category: Google Summer of Code]]&lt;/div&gt;</summary>
		<author><name>Wiki-Adube</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2016_Administrative&amp;diff=97330</id>
		<title>Google Summer of Code 2016 Administrative</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2016_Administrative&amp;diff=97330"/>
		<updated>2016-03-09T18:14:41Z</updated>

		<summary type="html">&lt;p&gt;Wiki-Adube: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;center&amp;gt;&lt;br /&gt;
[[Image:GSoC2016Logo.jpg|500px|link=https://summerofcode.withgoogle.com/]] &amp;lt;font size=&amp;quot;+3&amp;quot;&amp;gt; @ &amp;lt;/font&amp;gt; [[Image:OSGeo_300_127_pixel.png|200px|link=http://www.osgeo.org]]&lt;br /&gt;
&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Back to the main OSGeo [[Google Summer of Code 2016]] @ OSGeo wiki page.&lt;br /&gt;
&lt;br /&gt;
This is the central page for OSGeo administrative information in Google Summer of Code 2016.&lt;br /&gt;
&lt;br /&gt;
== GSoC general information ==&lt;br /&gt;
&lt;br /&gt;
* [https://developers.google.com/open-source/gsoc/timeline The official timeline]&lt;br /&gt;
* [https://developers.google.com/open-source/gsoc/resources/ Google's FAQ on the program]&lt;br /&gt;
* [https://summerofcode.withgoogle.com/ Official 2016 GSoC site]&lt;br /&gt;
&lt;br /&gt;
== Contacts == &lt;br /&gt;
&lt;br /&gt;
* [[User:Madi|Margherita Di Leo]] acts as Administrative contact, with support from [[User:Aghisla|Anne Ghisla]]. Feel free to email us with any questions, we're here to help mentor the mentors as much as anything else!&lt;br /&gt;
&lt;br /&gt;
* Would-be mentors and students: you are invited to sign up to the [http://lists.osgeo.org/mailman/listinfo/soc OSGeo SoC mailing list] right away. The list is the central communication channel for mentors, students and administrators. It is used for general GSoC announcements, specific OSGeo announcements, and for clarification about the program. As soon as you subscribe it, you are encouraged to introduce yourself and your role. We look forward to hear from you!&lt;br /&gt;
&lt;br /&gt;
== Mentors ==&lt;br /&gt;
&lt;br /&gt;
If you're interested in mentoring / supervising a student for one of the software participating this year under OSGeo's umbrella, please add your name, email, OSGeo/guest software and the projects you're interested in mentoring here:&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable sortable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;4&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#D7E3D1; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|width=30px|'''Number'''&lt;br /&gt;
|width=100px|'''Name'''&lt;br /&gt;
|width=100px|'''Surname'''&lt;br /&gt;
|width=100px|'''Nickname (IRC)'''&lt;br /&gt;
|width=250px|'''email'''&lt;br /&gt;
|'''Software'''&lt;br /&gt;
|'''Idea(s) you are available to mentor'''&lt;br /&gt;
|-&lt;br /&gt;
|1&lt;br /&gt;
|Margherita&lt;br /&gt;
|Di Leo &lt;br /&gt;
|madi&lt;br /&gt;
|diregola AT gmail DOT com &lt;br /&gt;
|admin at OSGeo&lt;br /&gt;
|Idea I would like to mentor&lt;br /&gt;
|-&lt;br /&gt;
|2&lt;br /&gt;
|Alexander&lt;br /&gt;
|Bruy &lt;br /&gt;
|alexbruy&lt;br /&gt;
|alexander.bruy AT gmail.com &lt;br /&gt;
|QGIS&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|3&lt;br /&gt;
|Victor&lt;br /&gt;
|Olaya &lt;br /&gt;
|volaya&lt;br /&gt;
|volayaf AT gmail DOT com &lt;br /&gt;
|QGIS&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|4&lt;br /&gt;
|Daniel&lt;br /&gt;
|Kastl&lt;br /&gt;
|dkastl&lt;br /&gt;
|daniel AT georepublic DOT de &lt;br /&gt;
|pgRouting&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|5&lt;br /&gt;
|Massimiliano&lt;br /&gt;
|Cannata&lt;br /&gt;
|maxi&lt;br /&gt;
|massimiliano.cannata AT gmail DOT com &lt;br /&gt;
|istSOS&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|6&lt;br /&gt;
|Milan&lt;br /&gt;
|Antonovic&lt;br /&gt;
|milan&lt;br /&gt;
|milan.antonovic AT gmail DOT com &lt;br /&gt;
|istSOS&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|7&lt;br /&gt;
|Jachym&lt;br /&gt;
|Cepicky&lt;br /&gt;
|jachym&lt;br /&gt;
|jachym.cepicky AT gmail &lt;br /&gt;
|PyWPS&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|8&lt;br /&gt;
|Andrea&lt;br /&gt;
|Antonello&lt;br /&gt;
|moovida&lt;br /&gt;
|andrea.antonello AT gmail DOT com&lt;br /&gt;
|JGrasstools, gvSIG, Geopaparazzi&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|-&lt;br /&gt;
|9&lt;br /&gt;
|Rashad&lt;br /&gt;
|Kanavath&lt;br /&gt;
|rashadkm&lt;br /&gt;
|rashadkm AT gmail DOT com&lt;br /&gt;
|GRASS GIS, OSSIM, GDAL&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|10&lt;br /&gt;
|Cameron&lt;br /&gt;
|Shorter&lt;br /&gt;
|CameronShorter&lt;br /&gt;
|cameronDOTs h o r ter AT gmail com&lt;br /&gt;
|OSGeo-Live&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|11&lt;br /&gt;
|Stephen&lt;br /&gt;
|Woodbridge&lt;br /&gt;
|woodbri&lt;br /&gt;
|woodbri AT swoodbridge DOT com&lt;br /&gt;
|pgRouting&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|12&lt;br /&gt;
|Vicky&lt;br /&gt;
|Vergara&lt;br /&gt;
|cvvergara&lt;br /&gt;
|vicky AT georepublic DOT de&lt;br /&gt;
|pgRouting&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|13&lt;br /&gt;
|Dmitry&lt;br /&gt;
|Baryshnikov&lt;br /&gt;
|bishop&lt;br /&gt;
|bishop.dev AT gmail.com &lt;br /&gt;
|GDAL&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|14&lt;br /&gt;
|Luca&lt;br /&gt;
|Delucchi&lt;br /&gt;
|lucadelu&lt;br /&gt;
|lucadeluge AT gmail.com &lt;br /&gt;
|GRASS GIS&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|15&lt;br /&gt;
|Anna&lt;br /&gt;
|Petrasova&lt;br /&gt;
|&lt;br /&gt;
|kratochanna AT gmail.com &lt;br /&gt;
|GRASS GIS&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|16&lt;br /&gt;
|Stefan&lt;br /&gt;
|Steiniger&lt;br /&gt;
|&lt;br /&gt;
|sstein AT geo.uzh.ch &lt;br /&gt;
|OneBusAway, OpenTripPlanner, OpenJUMP&lt;br /&gt;
|for OneBusAway see [http://github.com/OneBusAway/onebusaway-application-modules/wiki/Google-Summer-of-Code-2016 here]&lt;br /&gt;
|-&lt;br /&gt;
|17&lt;br /&gt;
|Sean&lt;br /&gt;
|Barbeau&lt;br /&gt;
|&lt;br /&gt;
|barbeau AT cutr.usf.edu&lt;br /&gt;
|OneBusAway, OpenTripPlanner&lt;br /&gt;
|for OneBusAway see [http://github.com/OneBusAway/onebusaway-application-modules/wiki/Google-Summer-of-Code-2016 here], also there are ideas around for OpenTripPlanner Android App, and the GTFS-RT Validator&lt;br /&gt;
|-&lt;br /&gt;
|18&lt;br /&gt;
|Riccardo&lt;br /&gt;
|Rigon&lt;br /&gt;
|abouthydrology&lt;br /&gt;
|rccrd.rgn AT gmail DOT com&lt;br /&gt;
|JGrasstools, gvSIG, Geopaparazzi&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|19&lt;br /&gt;
|Vaclav&lt;br /&gt;
|Petras&lt;br /&gt;
|&lt;br /&gt;
|wenzeslaus AT gmail.com &lt;br /&gt;
|GRASS GIS&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|20&lt;br /&gt;
|Oliver&lt;br /&gt;
|May&lt;br /&gt;
|&lt;br /&gt;
|oliver AT dfc DOT be&lt;br /&gt;
|Geomajas, leaflet, openlayers, geoserver, geotools&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|21&lt;br /&gt;
|Even&lt;br /&gt;
|Rouault&lt;br /&gt;
|&lt;br /&gt;
|even dot rouault AT spatialys dot com&lt;br /&gt;
|GDAL&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|22&lt;br /&gt;
|Alexandre&lt;br /&gt;
|Dubé&lt;br /&gt;
|&lt;br /&gt;
|adube AT mapgears dot com&lt;br /&gt;
|OL3-Google-Maps&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== A Mentor's Responsibilities ==&lt;br /&gt;
&lt;br /&gt;
Being a mentor can take anywhere from 2-10 hours a week of your time depending on the student (it really ''is'' in your best interest to take on the strongest students you can find :). You must have the time to be responsive and an advocate for the student. No matter how cool the project is and how much your team needs the job done, if you can't commit to supporting it, experience shows that the best thing to do is not start it, i.e. even with the best of intentions don't set a student up to fail. Long story short, student projects simply can't go ahead without proper mentoring support.&lt;br /&gt;
&lt;br /&gt;
Every student project will also have a '''backup mentor''', this person should come from your programming team and should at minimum keep up to date with the student's weekly developments. The best way is if the student is well integrated into your development team from the start, it lessens the workload on you and betters the buy-in from the rest of the community once you're ready for the final code merge.&lt;br /&gt;
&lt;br /&gt;
You '''must''' be available at some time during the '''midterm and final evaluation period'''. If you will be away during these time periods please arrange with the OSGeo org admins and your backup mentor so that one of us can fill in your answers for you. These are hard cutoffs -- evaluations ''must'' be filed within these dates.&lt;br /&gt;
&lt;br /&gt;
== Guides for mentors ==&lt;br /&gt;
&lt;br /&gt;
* [http://en.flossmanuals.net/GSoCMentoring/ The GSoC Mentoring Guide] - A must. Do get all useful info and tips from many years of experience from GSoC mentors.&lt;br /&gt;
* [http://people.gnome.org/~federico/docs/summer-of-code-mentoring-howto/ GNOME GSoC Mentoring HOWTO]&lt;br /&gt;
* [http://emptysqua.re/blog/mentoring/ An excellent summary of mentoring, from A. Jesse Jiryu Davis]&lt;br /&gt;
&lt;br /&gt;
== Tips for mentors ==&lt;br /&gt;
&lt;br /&gt;
This section is for collecting suggestions on best practices, from mentors to other mentors. If you have good / bad experiences in mentoring, please share here! Remember that this is a public page, respect the privacy of the people.&lt;br /&gt;
&lt;br /&gt;
=== Good ideas ===&lt;br /&gt;
&lt;br /&gt;
* Test students before selection. Challenge them with small programming tasks or bug fixes. This will help them getting familiar with the dev environment well before GSoC starts, and helps mentors understand if they are capable.&lt;br /&gt;
* Be patient.&lt;br /&gt;
&lt;br /&gt;
=== Bad ideas ===&lt;br /&gt;
&lt;br /&gt;
== Learn more ==&lt;br /&gt;
&lt;br /&gt;
* Previous years SoC involvement: [http://code.google.com/soc/2008/osgeo/about.html 2008], [http://www.google-melange.com/gsoc/org/google/gsoc2009/osgeo 2009], [http://www.google-melange.com/gsoc/org/google/gsoc2010/osgeo 2010], [http://www.google-melange.com/gsoc/org/google/gsoc2011/osgeo 2011], [http://www.google-melange.com/gsoc/org/google/gsoc2012/osgeo 2012], [http://www.google-melange.com/gsoc/org/google/gsoc2013/osgeo 2013], [https://www.google-melange.com/gsoc/org2/google/gsoc2015/osgeo 2015]&lt;br /&gt;
&lt;br /&gt;
* OSGeo GSoC wiki pages: [[Google Summer of Code 2008|2008]], [[Google Summer of Code 2009|2009]], [[Google Summer of Code 2010|2010]], [[Google Summer of Code 2011|2011]], [[Google Summer of Code 2012|2012]], [[Google Summer of Code 2013|2013]], [[Google Summer of Code 2014|2014]], [[Google Summer of Code 2015|2015]]&lt;br /&gt;
&lt;br /&gt;
* OSGeo Applications: [[Google SoC Application 2009|2009]], [[Google SoC Application 2010|2010]], [[Google Summer of Code Application 2011|2011]], [[Google Summer of Code Application 2012|2012]], [[Google Summer of Code Application 2013|2013]], [[Google Summer of Code Application 2014|2014]], [[Google Summer of Code Application 2015|2015]], [[Google Summer of Code Application 2016|2016]] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category: Google Summer of Code]]&lt;/div&gt;</summary>
		<author><name>Wiki-Adube</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Montreal_Code_Sprint_2011_Agenda&amp;diff=53898</id>
		<title>Montreal Code Sprint 2011 Agenda</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Montreal_Code_Sprint_2011_Agenda&amp;diff=53898"/>
		<updated>2011-03-17T18:21:56Z</updated>

		<summary type="html">&lt;p&gt;Wiki-Adube: /* GeoPrisma / OpenLayers / GeoExt */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Theme ==&lt;br /&gt;
&lt;br /&gt;
[[Montreal Code Sprint 2011]] : '''The Rendez-vous of the Tribes'''&lt;br /&gt;
&lt;br /&gt;
Sending out a clear message that we'd like to see members of all OSGeo tribes (C/C++, Java, JavaScript, C#, etc.) join forces for the advancement of OSGeo technologies. Last year's sprint in NYC helped foster synergies between the tribes and we want this to continue even stronger.&lt;br /&gt;
&lt;br /&gt;
== MapServer ==&lt;br /&gt;
&lt;br /&gt;
* 6.0 Release work (documentation, polishing and bug fixes)&lt;br /&gt;
* SVG Symbols (assefa, zak, thomas)&lt;br /&gt;
* rendering features with offset + leader (assefa, zak, thomas)&lt;br /&gt;
* Outputformat refactoring (don't create and initialize all default outputformats at each request) (thomas)&lt;br /&gt;
* Text rendering =&amp;gt; always use labelpathobj (thomas)&lt;br /&gt;
* rasterBufferObj: premultiplied or not? (thomas, frankw)&lt;br /&gt;
* INSPIRE View Services support for WMS (TomK, assefa, etc.)&lt;br /&gt;
* Ruby/SWIG MapScript (JimK)&lt;br /&gt;
* layer level GEOMTRANSFORM (Steve)&lt;br /&gt;
* use case snippets (see OpenLayers as an example) (Steve)&lt;br /&gt;
* profiling 6.0 ahead of benchmarking exercise  (need feedback from Jeff/Daniel on where we sucked)&lt;br /&gt;
&lt;br /&gt;
== PostGIS ==&lt;br /&gt;
&lt;br /&gt;
* 3D index issues outline support whether we'll have one or 2 types of parallel indices (prefer one type even if it means putting off til 2.1)&lt;br /&gt;
* 9.1 KNN GIST  are we going to do or punt to 2.1&lt;br /&gt;
* Left over issues with EMPTY and new more ISO compliant WKT display of geometries&lt;br /&gt;
* Make geometry_columns a view rather than table - harmonize legacy with new to cause least pain&lt;br /&gt;
* Possibility of preliminary X3D support in 2.0 instead of 2.1 (Olivier) ( http://trac.osgeo.org/postgis/ticket/854 )&lt;br /&gt;
* 3D topological serialization for PolyhedralSurface and TIN (Olivier)&lt;br /&gt;
* shp2pgsql (-gui)/pgsql2shp - (Jeff Adams)&lt;br /&gt;
    while you are at it would be really nice to investigate http://trac.osgeo.org/postgis/ticket/808 &lt;br /&gt;
     got broken in 2.0 and a real show-stopper for PostGIS 2.0 release&lt;br /&gt;
&lt;br /&gt;
  Also add more regression tests for shp2pgsql,pgsql2shp&lt;br /&gt;
* Incubation issues -- not fun stuff but needs to be addressed, get list of all contributors, decide if each file will have blanket copyright with reference to contributor file, what to do with files that have no copyright markings&lt;br /&gt;
&lt;br /&gt;
== PostGIS raster ==&lt;br /&gt;
&lt;br /&gt;
*Ticket fixes Pierre: (792 &amp;amp; 762), 825, 633, 766, 651, 490,&lt;br /&gt;
*Ticket fixes David: 582&lt;br /&gt;
*Ticket fixes Jorge: 851, 837&lt;br /&gt;
*Look at ticket 650 (GDAL Polygonize with real values) with Frank (Pierre)&lt;br /&gt;
*ST_SetRotation &amp;amp; ST_Rotation (ticket 482) (David)&lt;br /&gt;
*rt_raster_deserialize for header only in order to make get functions faster&lt;br /&gt;
*pl/pgSQL script fixes (tickets 643, 644, 645) (Pierre)&lt;br /&gt;
*ST_MapAlgebra optimization &amp;amp; neighbourhood (David)&lt;br /&gt;
*ST_Intersection optimization (David)&lt;br /&gt;
*Optional tickets 165, 301, 484&lt;br /&gt;
&lt;br /&gt;
== GDAL/OGR ==&lt;br /&gt;
&lt;br /&gt;
* SWIG/Ruby bindings? (JimK)&lt;br /&gt;
* Merge the two MrSID Drivers (Raster and Lidar) into one&lt;br /&gt;
&lt;br /&gt;
== libLAS  ==&lt;br /&gt;
&lt;br /&gt;
* Discussions&lt;br /&gt;
** hobu to talk about technologies, intents, and targeted platforms for libPC&lt;br /&gt;
** mpg to discuss/demonstrate the Stage model that libPC sets up&lt;br /&gt;
** mpg to give a small code walkthrough via projector&lt;br /&gt;
** Try to get FrankW to discuss features/failures/successes of both GDAL and OGR's driver models&lt;br /&gt;
** Investigate and discuss using boost-style traits for class description&lt;br /&gt;
** Investigate Point Cloud Library's (PCL) template-driven point classes and their applicability and/or adaptability for libPC.&lt;br /&gt;
&lt;br /&gt;
* Technical support / Infrastructure&lt;br /&gt;
** Get hg access for all sprint participants&lt;br /&gt;
** Bootstrap people building libPC on their own computers (writing docs as we go)&lt;br /&gt;
** hobu to stand up libpc.org with Trac/HG/Sphinx&lt;br /&gt;
** Add CMake detection for MG4&lt;br /&gt;
** test harness for the command line apps&lt;br /&gt;
&lt;br /&gt;
* Development&lt;br /&gt;
** Crib up the text, MG4, and BAG drivers&lt;br /&gt;
** Add MG4/L support to libPC&lt;br /&gt;
** Plan for adding octree libpc::Stage&lt;br /&gt;
** finish the native LAS driver&lt;br /&gt;
** flesh out the dump routines for each major class&lt;br /&gt;
** light up pcinfo&lt;br /&gt;
&lt;br /&gt;
== TinyOWS ==&lt;br /&gt;
&lt;br /&gt;
* MapFile parser, to allow a single configuration file for both MapServer and TinyOWS.&lt;br /&gt;
&lt;br /&gt;
== ZOO Project ==&lt;br /&gt;
&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
== GeoPrisma / OpenLayers / GeoExt ==&lt;br /&gt;
&lt;br /&gt;
'''Objectives, with (priority)'''&lt;br /&gt;
&lt;br /&gt;
* (1) GeoPrisma: WFS&lt;br /&gt;
 * Add service and proxy&lt;br /&gt;
  * Read&lt;br /&gt;
  * Create&lt;br /&gt;
  * Update&lt;br /&gt;
  * Delete&lt;br /&gt;
 * Adapt existing widgets currently using featureserver to support wfs as well (editing, shortcut, etc.)&lt;br /&gt;
&lt;br /&gt;
* (1) GeoPrisma: [http://dev8.mapgears.com/geoprisma/trunk/samples/pgsqlconfig/osgeocs/ Demo] with :&lt;br /&gt;
 * (done) GeoPrisma (trunk) using the PGSQLMapContext config driver&lt;br /&gt;
 * (done) GMap data (postgis &amp;amp; shapefiles)&lt;br /&gt;
 * (done) MapServer (trunk) - WMS&lt;br /&gt;
 * TinyOWS (trunk) - WFST (using MapServer mapfile)&lt;br /&gt;
 * (done) MapFishPrint, supporting vector printing&lt;br /&gt;
 * ZooProject - WPS&lt;br /&gt;
&lt;br /&gt;
* '''(Done)''' GeoExt ux - LayerTreeBuilder: make the display of a Legend widget configurable on a per-layer basis?? (instead of on per-layer type basis). Solution : new 'hideInLegend' layer property transported to the GeoExt.data.LayerRecord object.&lt;br /&gt;
* (1) GeoExt ux - AttributeFilterPanel: add flexibility in how the Vector features are retrieved (i.e. using a Vector layer object to query an existing layer or using a Protocol object and creating a new Vector layer on the fly). This widget has a lot of overlap with GeoExt's FormPanel (in fact it was derived from it), we should try to merge the functionality of both widgets in a single one.&lt;br /&gt;
* (1) GeoPrisma - AttributeFilterPanel widget: #175 - write a sample (we may need a PostgreSQL server on the geoprisma.org machine), documentation and merge the branch to the trunk.&lt;br /&gt;
* '''(done)''' GeoPrisma: #164 - Add Vector layer type support for MapFishPrint service.&lt;br /&gt;
* (2) GeoExt ux - [http://dev.geoext.org/sandbox/mapgears/geoext.ux/ux/LayerTreeBuilder/examples/tree-builder.html LayerTreeBuilder] officialisation&lt;br /&gt;
 * create ticket in [http://trac.geoext.org/ GeoExt TRAC]&lt;br /&gt;
 * create a patch with an example and test units (with OpenLayers 2.10 and GeoExt 1.0)&lt;br /&gt;
 * create a [http://trac.geoext.org/wiki/Community wiki page] for the ux explaining it&lt;br /&gt;
 * ask a review to a core commiter&lt;br /&gt;
* (2) GeoExt ux - [http://dev.geoext.org/sandbox/mapgears/geoext.ux/ux/WMSBrowser/examples/WMSBrowser.html WMSBrowser] officialisation&lt;br /&gt;
 * create ticket in [http://trac.geoext.org/ GeoExt TRAC]&lt;br /&gt;
 * create a patch with an example and test units (with OpenLayers 2.10 and GeoExt 1.0)&lt;br /&gt;
 * create a [http://trac.geoext.org/wiki/Community wiki page] for the ux explaining it&lt;br /&gt;
 * ask a review to a core commiter&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''If we have more time'''&lt;br /&gt;
&lt;br /&gt;
* (2) GeoPrisma - WPS service and proxy&lt;br /&gt;
* (2) GeoExt ux - LayerTreeBuilder: add support for multiple layers when calling a WMS service.&lt;br /&gt;
* (3) GeoPrisma: #168 - switch to ExtJS-style i18n for client widgets (maybe do 1 or 2 widgets as a proof-of-concept)&lt;br /&gt;
* (3) GeoPrisma: #149 - deprecate the PDFPrint widget ?&lt;br /&gt;
* (2) GeoPrisma: Try to setup and support mod-geocache&lt;br /&gt;
&lt;br /&gt;
== OpenLayers ==&lt;br /&gt;
&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category: Code Sprints]]&lt;/div&gt;</summary>
		<author><name>Wiki-Adube</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Montreal_Code_Sprint_2011_Agenda&amp;diff=53886</id>
		<title>Montreal Code Sprint 2011 Agenda</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Montreal_Code_Sprint_2011_Agenda&amp;diff=53886"/>
		<updated>2011-03-16T17:21:47Z</updated>

		<summary type="html">&lt;p&gt;Wiki-Adube: /* GeoPrisma / OpenLayers / GeoExt */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Theme ==&lt;br /&gt;
&lt;br /&gt;
[[Montreal Code Sprint 2011]] : '''The Rendez-vous of the Tribes'''&lt;br /&gt;
&lt;br /&gt;
Sending out a clear message that we'd like to see members of all OSGeo tribes (C/C++, Java, JavaScript, C#, etc.) join forces for the advancement of OSGeo technologies. Last year's sprint in NYC helped foster synergies between the tribes and we want this to continue even stronger.&lt;br /&gt;
&lt;br /&gt;
== MapServer ==&lt;br /&gt;
&lt;br /&gt;
* 6.0 Release work (documentation, polishing and bug fixes)&lt;br /&gt;
* SVG Symbols (assefa, zak, thomas)&lt;br /&gt;
* rendering features with offset + leader (assefa, zak, thomas)&lt;br /&gt;
* Outputformat refactoring (don't create and initialize all default outputformats at each request) (thomas)&lt;br /&gt;
* Text rendering =&amp;gt; always use labelpathobj (thomas)&lt;br /&gt;
* rasterBufferObj: premultiplied or not? (thomas, frankw)&lt;br /&gt;
* INSPIRE View Services support for WMS (TomK, assefa, etc.)&lt;br /&gt;
* Ruby/SWIG MapScript (JimK)&lt;br /&gt;
* layer level GEOMTRANSFORM (Steve)&lt;br /&gt;
* use case snippets (see OpenLayers as an example) (Steve)&lt;br /&gt;
* profiling 6.0 ahead of benchmarking exercise  (need feedback from Jeff/Daniel on where we sucked)&lt;br /&gt;
&lt;br /&gt;
== PostGIS ==&lt;br /&gt;
&lt;br /&gt;
* 3D index issues outline support whether we'll have one or 2 types of parallel indices (prefer one type even if it means putting off til 2.1)&lt;br /&gt;
* 9.1 KNN GIST  are we going to do or punt to 2.1&lt;br /&gt;
* Left over issues with EMPTY and new more ISO compliant WKT display of geometries&lt;br /&gt;
* Make geometry_columns a view rather than table - harmonize legacy with new to cause least pain&lt;br /&gt;
* Possibility of preliminary X3D support in 2.0 instead of 2.1 (Olivier) ( http://trac.osgeo.org/postgis/ticket/854 )&lt;br /&gt;
* 3D topological serialization for PolyhedralSurface and TIN (Olivier)&lt;br /&gt;
* shp2pgsql (-gui)/pgsql2shp - (Jeff Adams)&lt;br /&gt;
    while you are at it would be really nice to investigate http://trac.osgeo.org/postgis/ticket/808 &lt;br /&gt;
     got broken in 2.0 and a real show-stopper for PostGIS 2.0 release&lt;br /&gt;
&lt;br /&gt;
  Also add more regression tests for shp2pgsql,pgsql2shp&lt;br /&gt;
* Incubation issues -- not fun stuff but needs to be addressed, get list of all contributors, decide if each file will have blanket copyright with reference to contributor file, what to do with files that have no copyright markings&lt;br /&gt;
&lt;br /&gt;
== PostGIS raster ==&lt;br /&gt;
&lt;br /&gt;
*Ticket fixes Pierre: (792 &amp;amp; 762), 825, 633, 766, 651, 490,&lt;br /&gt;
*Ticket fixes David: 582&lt;br /&gt;
*Ticket fixes Jorge: 851, 837&lt;br /&gt;
*Look at ticket 650 (GDAL Polygonize with real values) with Frank (Pierre)&lt;br /&gt;
*ST_SetRotation &amp;amp; ST_Rotation (ticket 482) (David)&lt;br /&gt;
*rt_raster_deserialize for header only in order to make get functions faster&lt;br /&gt;
*pl/pgSQL script fixes (tickets 643, 644, 645) (Pierre)&lt;br /&gt;
*ST_MapAlgebra optimization &amp;amp; neighbourhood (David)&lt;br /&gt;
*ST_Intersection optimization (David)&lt;br /&gt;
*Optional tickets 165, 301, 484&lt;br /&gt;
&lt;br /&gt;
== GDAL/OGR ==&lt;br /&gt;
&lt;br /&gt;
* SWIG/Ruby bindings? (JimK)&lt;br /&gt;
* Merge the two MrSID Drivers (Raster and Lidar) into one&lt;br /&gt;
&lt;br /&gt;
== libLAS  ==&lt;br /&gt;
&lt;br /&gt;
* Discussions&lt;br /&gt;
** hobu to talk about technologies, intents, and targeted platforms for libPC&lt;br /&gt;
** mpg to discuss/demonstrate the Stage model that libPC sets up&lt;br /&gt;
** mpg to give a small code walkthrough via projector&lt;br /&gt;
** Try to get FrankW to discuss features/failures/successes of both GDAL and OGR's driver models&lt;br /&gt;
** Investigate and discuss using boost-style traits for class description&lt;br /&gt;
** Investigate Point Cloud Library's (PCL) template-driven point classes and their applicability and/or adaptability for libPC.&lt;br /&gt;
&lt;br /&gt;
* Technical support / Infrastructure&lt;br /&gt;
** Get hg access for all sprint participants&lt;br /&gt;
** Bootstrap people building libPC on their own computers (writing docs as we go)&lt;br /&gt;
** hobu to stand up libpc.org with Trac/HG/Sphinx&lt;br /&gt;
** Add CMake detection for MG4&lt;br /&gt;
** test harness for the command line apps&lt;br /&gt;
&lt;br /&gt;
* Development&lt;br /&gt;
** Crib up the text, MG4, and BAG drivers&lt;br /&gt;
** Add MG4/L support to libPC&lt;br /&gt;
** Plan for adding octree libpc::Stage&lt;br /&gt;
** finish the native LAS driver&lt;br /&gt;
** flesh out the dump routines for each major class&lt;br /&gt;
** light up pcinfo&lt;br /&gt;
&lt;br /&gt;
== TinyOWS ==&lt;br /&gt;
&lt;br /&gt;
* MapFile parser, to allow a single configuration file for both MapServer and TinyOWS.&lt;br /&gt;
&lt;br /&gt;
== ZOO Project ==&lt;br /&gt;
&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
== GeoPrisma / OpenLayers / GeoExt ==&lt;br /&gt;
&lt;br /&gt;
'''Objectives, with (priority)'''&lt;br /&gt;
&lt;br /&gt;
* (1) GeoPrisma: WFS&lt;br /&gt;
 * Add service and proxy&lt;br /&gt;
 * Adapt existing widgets currently using featureserver to support wfs as well (editing, shortcut, etc.)&lt;br /&gt;
&lt;br /&gt;
* (1) GeoPrisma: [http://dev8.mapgears.com/geoprisma/trunk/samples/pgsqlconfig/osgeocs/ Demo] with :&lt;br /&gt;
 * (done) GeoPrisma (trunk) using the PGSQLMapContext config driver&lt;br /&gt;
 * (done) GMap data (postgis &amp;amp; shapefiles)&lt;br /&gt;
 * (done) MapServer (trunk) - WMS&lt;br /&gt;
 * TinyOWS (trunk) - WFST (using MapServer mapfile)&lt;br /&gt;
 * MapFishPrint, supporting vector printing&lt;br /&gt;
 * ZooProject - WPS&lt;br /&gt;
&lt;br /&gt;
* '''(Done)''' GeoExt ux - LayerTreeBuilder: make the display of a Legend widget configurable on a per-layer basis?? (instead of on per-layer type basis). Solution : new 'hideInLegend' layer property transported to the GeoExt.data.LayerRecord object.&lt;br /&gt;
* (1) GeoExt ux - AttributeFilterPanel: add flexibility in how the Vector features are retrieved (i.e. using a Vector layer object to query an existing layer or using a Protocol object and creating a new Vector layer on the fly). This widget has a lot of overlap with GeoExt's FormPanel (in fact it was derived from it), we should try to merge the functionality of both widgets in a single one.&lt;br /&gt;
* (1) GeoPrisma - AttributeFilterPanel widget: #175 - write a sample (we may need a PostgreSQL server on the geoprisma.org machine), documentation and merge the branch to the trunk.&lt;br /&gt;
* (2) GeoPrisma: #164 - Add Vector layer type support for MapFishPrint service.&lt;br /&gt;
* (2) GeoExt ux - [http://dev.geoext.org/sandbox/mapgears/geoext.ux/ux/LayerTreeBuilder/examples/tree-builder.html LayerTreeBuilder] officialisation&lt;br /&gt;
 * create ticket in [http://trac.geoext.org/ GeoExt TRAC]&lt;br /&gt;
 * create a patch with an example and test units (with OpenLayers 2.10 and GeoExt 1.0)&lt;br /&gt;
 * create a [http://trac.geoext.org/wiki/Community wiki page] for the ux explaining it&lt;br /&gt;
 * ask a review to a core commiter&lt;br /&gt;
* (2) GeoExt ux - [http://dev.geoext.org/sandbox/mapgears/geoext.ux/ux/WMSBrowser/examples/WMSBrowser.html WMSBrowser] officialisation&lt;br /&gt;
 * create ticket in [http://trac.geoext.org/ GeoExt TRAC]&lt;br /&gt;
 * create a patch with an example and test units (with OpenLayers 2.10 and GeoExt 1.0)&lt;br /&gt;
 * create a [http://trac.geoext.org/wiki/Community wiki page] for the ux explaining it&lt;br /&gt;
 * ask a review to a core commiter&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''If we have more time'''&lt;br /&gt;
&lt;br /&gt;
* (2) GeoPrisma - WPS service and proxy&lt;br /&gt;
* (2) GeoExt ux - LayerTreeBuilder: add support for multiple layers when calling a WMS service.&lt;br /&gt;
* (3) GeoPrisma: #168 - switch to ExtJS-style i18n for client widgets (maybe do 1 or 2 widgets as a proof-of-concept)&lt;br /&gt;
* (3) GeoPrisma: #149 - deprecate the PDFPrint widget ?&lt;br /&gt;
* (2) GeoPrisma: Try to setup and support mod-geocache&lt;br /&gt;
&lt;br /&gt;
== OpenLayers ==&lt;br /&gt;
&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category: Code Sprints]]&lt;/div&gt;</summary>
		<author><name>Wiki-Adube</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Montreal_Code_Sprint_2011_Agenda&amp;diff=53865</id>
		<title>Montreal Code Sprint 2011 Agenda</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Montreal_Code_Sprint_2011_Agenda&amp;diff=53865"/>
		<updated>2011-03-15T19:47:04Z</updated>

		<summary type="html">&lt;p&gt;Wiki-Adube: /* GeoPrisma / OpenLayers / GeoExt */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Theme ==&lt;br /&gt;
&lt;br /&gt;
[[Montreal Code Sprint 2011]] : '''The Rendez-vous of the Tribes'''&lt;br /&gt;
&lt;br /&gt;
Sending out a clear message that we'd like to see members of all OSGeo tribes (C/C++, Java, JavaScript, C#, etc.) join forces for the advancement of OSGeo technologies. Last year's sprint in NYC helped foster synergies between the tribes and we want this to continue even stronger.&lt;br /&gt;
&lt;br /&gt;
== MapServer ==&lt;br /&gt;
&lt;br /&gt;
* 6.0 Release work (documentation, polishing and bug fixes)&lt;br /&gt;
* SVG Symbols (assefa, zak, thomas)&lt;br /&gt;
* rendering features with offset + leader (assefa, zak, thomas)&lt;br /&gt;
* Outputformat refactoring (don't create and initialize all default outputformats at each request) (thomas)&lt;br /&gt;
* Text rendering =&amp;gt; always use labelpathobj (thomas)&lt;br /&gt;
* rasterBufferObj: premultiplied or not? (thomas, frankw)&lt;br /&gt;
* INSPIRE View Services support for WMS (TomK, assefa, etc.)&lt;br /&gt;
* Ruby/SWIG MapScript (JimK)&lt;br /&gt;
* layer level GEOMTRANSFORM (Steve)&lt;br /&gt;
* use case snippets (see OpenLayers as an example) (Steve)&lt;br /&gt;
* profiling 6.0 ahead of benchmarking exercise  (need feedback from Jeff/Daniel on where we sucked)&lt;br /&gt;
&lt;br /&gt;
== PostGIS ==&lt;br /&gt;
&lt;br /&gt;
* 3D index issues outline support whether we'll have one or 2 types of parallel indices (prefer one type even if it means putting off til 2.1)&lt;br /&gt;
* 9.1 KNN GIST  are we going to do or punt to 2.1&lt;br /&gt;
* Left over issues with EMPTY and new more ISO compliant WKT display of geometries&lt;br /&gt;
* Make geometry_columns a view rather than table - harmonize legacy with new to cause least pain&lt;br /&gt;
* Possibility of preliminary X3D support in 2.0 instead of 2.1 (Olivier) ( http://trac.osgeo.org/postgis/ticket/854 )&lt;br /&gt;
* 3D topological serialization for PolyhedralSurface and TIN (Olivier)&lt;br /&gt;
* shp2pgsql (-gui)/pgsql2shp - (Jeff Adams)&lt;br /&gt;
    while you are at it would be really nice to investigate http://trac.osgeo.org/postgis/ticket/808 &lt;br /&gt;
     got broken in 2.0 and a real show-stopper for PostGIS 2.0 release&lt;br /&gt;
&lt;br /&gt;
  Also add more regression tests for shp2pgsql,pgsql2shp&lt;br /&gt;
* Incubation issues -- not fun stuff but needs to be addressed, get list of all contributors, decide if each file will have blanket copyright with reference to contributor file, what to do with files that have no copyright markings&lt;br /&gt;
&lt;br /&gt;
== PostGIS raster ==&lt;br /&gt;
&lt;br /&gt;
*Ticket fixes Pierre: (792 &amp;amp; 762), 825, 633, 766, 651, 490,&lt;br /&gt;
*Ticket fixes David: 582&lt;br /&gt;
*Ticket fixes Jorge: 851, 837&lt;br /&gt;
*Look at ticket 650 (GDAL Polygonize with real values) with Frank (Pierre)&lt;br /&gt;
*ST_SetRotation &amp;amp; ST_Rotation (ticket 482) (David)&lt;br /&gt;
*rt_raster_deserialize for header only in order to make get functions faster&lt;br /&gt;
*pl/pgSQL script fixes (tickets 643, 644, 645) (Pierre)&lt;br /&gt;
*ST_MapAlgebra optimization &amp;amp; neighbourhood (David)&lt;br /&gt;
*ST_Intersection optimization (David)&lt;br /&gt;
*Optional tickets 165, 301, 484&lt;br /&gt;
&lt;br /&gt;
== GDAL/OGR ==&lt;br /&gt;
&lt;br /&gt;
* SWIG/Ruby bindings? (JimK)&lt;br /&gt;
* Merge the two MrSID Drivers (Raster and Lidar) into one&lt;br /&gt;
&lt;br /&gt;
== libLAS  ==&lt;br /&gt;
&lt;br /&gt;
* Discussions&lt;br /&gt;
** hobu to talk about technologies, intents, and targeted platforms for libPC&lt;br /&gt;
** mpg to discuss/demonstrate the Stage model that libPC sets up&lt;br /&gt;
** mpg to give a small code walkthrough via projector&lt;br /&gt;
** Try to get FrankW to discuss features/failures/successes of both GDAL and OGR's driver models&lt;br /&gt;
** Investigate and discuss using boost-style traits for class description&lt;br /&gt;
** Investigate Point Cloud Library's (PCL) template-driven point classes and their applicability and/or adaptability for libPC.&lt;br /&gt;
&lt;br /&gt;
* Technical support / Infrastructure&lt;br /&gt;
** Get hg access for all sprint participants&lt;br /&gt;
** Bootstrap people building libPC on their own computers (writing docs as we go)&lt;br /&gt;
** hobu to stand up libpc.org with Trac/HG/Sphinx&lt;br /&gt;
** Add CMake detection for MG4&lt;br /&gt;
** test harness for the command line apps&lt;br /&gt;
&lt;br /&gt;
* Development&lt;br /&gt;
** Crib up the text, MG4, and BAG drivers&lt;br /&gt;
** Add MG4/L support to libPC&lt;br /&gt;
** Plan for adding octree libpc::Stage&lt;br /&gt;
** finish the native LAS driver&lt;br /&gt;
** flesh out the dump routines for each major class&lt;br /&gt;
** light up pcinfo&lt;br /&gt;
&lt;br /&gt;
== TinyOWS ==&lt;br /&gt;
&lt;br /&gt;
* MapFile parser, to allow a single configuration file for both MapServer and TinyOWS.&lt;br /&gt;
&lt;br /&gt;
== ZOO Project ==&lt;br /&gt;
&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
== GeoPrisma / OpenLayers / GeoExt ==&lt;br /&gt;
&lt;br /&gt;
'''Objectives, with (priority)'''&lt;br /&gt;
&lt;br /&gt;
* (1) GeoPrisma: WFS&lt;br /&gt;
 * Add service and proxy&lt;br /&gt;
 * Adapt existing widgets currently using featureserver to support wfs as well (editing, shortcut, etc.)&lt;br /&gt;
&lt;br /&gt;
* (1) GeoPrisma: Demo with :&lt;br /&gt;
 * GeoPrisma (trunk) using the PGSQLMapContext config driver&lt;br /&gt;
 * GMap data (postgis &amp;amp; shapefiles)&lt;br /&gt;
 * MapServer (trunk) - WMS&lt;br /&gt;
 * TinyOWS (trunk) - WFST (using MapServer mapfile)&lt;br /&gt;
 * MapFishPrint, supporting vector printing&lt;br /&gt;
 * ZooProject - WPS&lt;br /&gt;
&lt;br /&gt;
* '''(Done)''' GeoExt ux - LayerTreeBuilder: make the display of a Legend widget configurable on a per-layer basis?? (instead of on per-layer type basis). Solution : new 'hideInLegend' layer property transported to the GeoExt.data.LayerRecord object.&lt;br /&gt;
* (1) GeoExt ux - AttributeFilterPanel: add flexibility in how the Vector features are retrieved (i.e. using a Vector layer object to query an existing layer or using a Protocol object and creating a new Vector layer on the fly). This widget has a lot of overlap with GeoExt's FormPanel (in fact it was derived from it), we should try to merge the functionality of both widgets in a single one.&lt;br /&gt;
* (1) GeoPrisma - AttributeFilterPanel widget: #175 - write a sample (we may need a PostgreSQL server on the geoprisma.org machine), documentation and merge the branch to the trunk.&lt;br /&gt;
* (2) GeoPrisma: #164 - Add Vector layer type support for MapFishPrint service.&lt;br /&gt;
* (2) GeoExt ux - [http://dev.geoext.org/sandbox/mapgears/geoext.ux/ux/LayerTreeBuilder/examples/tree-builder.html LayerTreeBuilder] officialisation&lt;br /&gt;
 * create ticket in [http://trac.geoext.org/ GeoExt TRAC]&lt;br /&gt;
 * create a patch with an example and test units (with OpenLayers 2.10 and GeoExt 1.0)&lt;br /&gt;
 * create a [http://trac.geoext.org/wiki/Community wiki page] for the ux explaining it&lt;br /&gt;
 * ask a review to a core commiter&lt;br /&gt;
* (2) GeoExt ux - [http://dev.geoext.org/sandbox/mapgears/geoext.ux/ux/WMSBrowser/examples/WMSBrowser.html WMSBrowser] officialisation&lt;br /&gt;
 * create ticket in [http://trac.geoext.org/ GeoExt TRAC]&lt;br /&gt;
 * create a patch with an example and test units (with OpenLayers 2.10 and GeoExt 1.0)&lt;br /&gt;
 * create a [http://trac.geoext.org/wiki/Community wiki page] for the ux explaining it&lt;br /&gt;
 * ask a review to a core commiter&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''If we have more time'''&lt;br /&gt;
&lt;br /&gt;
* (2) GeoPrisma - WPS service and proxy&lt;br /&gt;
* (2) GeoExt ux - LayerTreeBuilder: add support for multiple layers when calling a WMS service.&lt;br /&gt;
* (3) GeoPrisma: #168 - switch to ExtJS-style i18n for client widgets (maybe do 1 or 2 widgets as a proof-of-concept)&lt;br /&gt;
* (3) GeoPrisma: #149 - deprecate the PDFPrint widget ?&lt;br /&gt;
* (2) GeoPrisma: Try to setup and support mod-geocache&lt;br /&gt;
&lt;br /&gt;
== OpenLayers ==&lt;br /&gt;
&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category: Code Sprints]]&lt;/div&gt;</summary>
		<author><name>Wiki-Adube</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Montreal_Code_Sprint_2011_Agenda&amp;diff=53861</id>
		<title>Montreal Code Sprint 2011 Agenda</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Montreal_Code_Sprint_2011_Agenda&amp;diff=53861"/>
		<updated>2011-03-15T19:03:39Z</updated>

		<summary type="html">&lt;p&gt;Wiki-Adube: /* GeoPrisma / OpenLayers / GeoExt */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Theme ==&lt;br /&gt;
&lt;br /&gt;
[[Montreal Code Sprint 2011]] : '''The Rendez-vous of the Tribes'''&lt;br /&gt;
&lt;br /&gt;
Sending out a clear message that we'd like to see members of all OSGeo tribes (C/C++, Java, JavaScript, C#, etc.) join forces for the advancement of OSGeo technologies. Last year's sprint in NYC helped foster synergies between the tribes and we want this to continue even stronger.&lt;br /&gt;
&lt;br /&gt;
== MapServer ==&lt;br /&gt;
&lt;br /&gt;
* 6.0 Release work (documentation, polishing and bug fixes)&lt;br /&gt;
* SVG Symbols (assefa, zak, thomas)&lt;br /&gt;
* rendering features with offset + leader (assefa, zak, thomas)&lt;br /&gt;
* Outputformat refactoring (don't create and initialize all default outputformats at each request) (thomas)&lt;br /&gt;
* Text rendering =&amp;gt; always use labelpathobj (thomas)&lt;br /&gt;
* rasterBufferObj: premultiplied or not? (thomas, frankw)&lt;br /&gt;
* INSPIRE View Services support for WMS (TomK, assefa, etc.)&lt;br /&gt;
* Ruby/SWIG MapScript (JimK)&lt;br /&gt;
* layer level GEOMTRANSFORM (Steve)&lt;br /&gt;
* use case snippets (see OpenLayers as an example) (Steve)&lt;br /&gt;
* profiling 6.0 ahead of benchmarking exercise  (need feedback from Jeff/Daniel on where we sucked)&lt;br /&gt;
&lt;br /&gt;
== PostGIS ==&lt;br /&gt;
&lt;br /&gt;
* 3D index issues outline support whether we'll have one or 2 types of parallel indices (prefer one type even if it means putting off til 2.1)&lt;br /&gt;
* 9.1 KNN GIST  are we going to do or punt to 2.1&lt;br /&gt;
* Left over issues with EMPTY and new more ISO compliant WKT display of geometries&lt;br /&gt;
* Make geometry_columns a view rather than table - harmonize legacy with new to cause least pain&lt;br /&gt;
* Possibility of preliminary X3D support in 2.0 instead of 2.1 (Olivier) ( http://trac.osgeo.org/postgis/ticket/854 )&lt;br /&gt;
* 3D topological serialization for PolyhedralSurface and TIN (Olivier)&lt;br /&gt;
* shp2pgsql (-gui)/pgsql2shp - (Jeff Adams)&lt;br /&gt;
    while you are at it would be really nice to investigate http://trac.osgeo.org/postgis/ticket/808 &lt;br /&gt;
     got broken in 2.0 and a real show-stopper for PostGIS 2.0 release&lt;br /&gt;
&lt;br /&gt;
  Also add more regression tests for shp2pgsql,pgsql2shp&lt;br /&gt;
* Incubation issues -- not fun stuff but needs to be addressed, get list of all contributors, decide if each file will have blanket copyright with reference to contributor file, what to do with files that have no copyright markings&lt;br /&gt;
&lt;br /&gt;
== PostGIS raster ==&lt;br /&gt;
&lt;br /&gt;
*Ticket fixes Pierre: (792 &amp;amp; 762), 825, 633, 766, 651, 490,&lt;br /&gt;
*Ticket fixes David: 582&lt;br /&gt;
*Ticket fixes Jorge: 851, 837&lt;br /&gt;
*Look at ticket 650 (GDAL Polygonize with real values) with Frank (Pierre)&lt;br /&gt;
*ST_SetRotation &amp;amp; ST_Rotation (ticket 482) (David)&lt;br /&gt;
*rt_raster_deserialize for header only in order to make get functions faster&lt;br /&gt;
*pl/pgSQL script fixes (tickets 643, 644, 645) (Pierre)&lt;br /&gt;
*ST_MapAlgebra optimization &amp;amp; neighbourhood (David)&lt;br /&gt;
*ST_Intersection optimization (David)&lt;br /&gt;
*Optional tickets 165, 301, 484&lt;br /&gt;
&lt;br /&gt;
== GDAL/OGR ==&lt;br /&gt;
&lt;br /&gt;
* SWIG/Ruby bindings? (JimK)&lt;br /&gt;
* Merge the two MrSID Drivers (Raster and Lidar) into one&lt;br /&gt;
&lt;br /&gt;
== libLAS  ==&lt;br /&gt;
&lt;br /&gt;
* Discussions&lt;br /&gt;
** hobu to talk about technologies, intents, and targeted platforms for libPC&lt;br /&gt;
** mpg to discuss/demonstrate the Stage model that libPC sets up&lt;br /&gt;
** mpg to give a small code walkthrough via projector&lt;br /&gt;
** Try to get FrankW to discuss features/failures/successes of both GDAL and OGR's driver models&lt;br /&gt;
** Investigate and discuss using boost-style traits for class description&lt;br /&gt;
** Investigate Point Cloud Library's (PCL) template-driven point classes and their applicability and/or adaptability for libPC.&lt;br /&gt;
&lt;br /&gt;
* Technical support / Infrastructure&lt;br /&gt;
** Get hg access for all sprint participants&lt;br /&gt;
** Bootstrap people building libPC on their own computers (writing docs as we go)&lt;br /&gt;
** hobu to stand up libpc.org with Trac/HG/Sphinx&lt;br /&gt;
** Add CMake detection for MG4&lt;br /&gt;
** test harness for the command line apps&lt;br /&gt;
&lt;br /&gt;
* Development&lt;br /&gt;
** Crib up the text, MG4, and BAG drivers&lt;br /&gt;
** Add MG4/L support to libPC&lt;br /&gt;
** Plan for adding octree libpc::Stage&lt;br /&gt;
** finish the native LAS driver&lt;br /&gt;
** flesh out the dump routines for each major class&lt;br /&gt;
** light up pcinfo&lt;br /&gt;
&lt;br /&gt;
== TinyOWS ==&lt;br /&gt;
&lt;br /&gt;
* MapFile parser, to allow a single configuration file for both MapServer and TinyOWS.&lt;br /&gt;
&lt;br /&gt;
== ZOO Project ==&lt;br /&gt;
&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
== GeoPrisma / OpenLayers / GeoExt ==&lt;br /&gt;
&lt;br /&gt;
'''Objectives, with (priority)'''&lt;br /&gt;
&lt;br /&gt;
* (1) GeoPrisma: WFS&lt;br /&gt;
 * Add service and proxy&lt;br /&gt;
 * Adapt existing widgets currently using featureserver to support wfs as well (editing, shortcut, etc.)&lt;br /&gt;
&lt;br /&gt;
* (1) GeoPrisma: Demo with :&lt;br /&gt;
 * GeoPrisma (trunk) using the PGSQLMapContext config driver&lt;br /&gt;
 * GMap data (postgis &amp;amp; shapefiles)&lt;br /&gt;
 * MapServer (trunk) - WMS&lt;br /&gt;
 * TinyOWS (trunk) - WFST (using MapServer mapfile)&lt;br /&gt;
 * MapFishPrint, supporting vector printing&lt;br /&gt;
 * ZooProject - WPS&lt;br /&gt;
&lt;br /&gt;
* (1) GeoExt ux - LayerTreeBuilder: make the display of a Legend widget configurable on a per-layer basis?? (instead of on per-layer type basis).&lt;br /&gt;
* (1) GeoExt ux - AttributeFilterPanel: add flexibility in how the Vector features are retrieved (i.e. using a Vector layer object to query an existing layer or using a Protocol object and creating a new Vector layer on the fly). This widget has a lot of overlap with GeoExt's FormPanel (in fact it was derived from it), we should try to merge the functionality of both widgets in a single one.&lt;br /&gt;
* (1) GeoPrisma - AttributeFilterPanel widget: #175 - write a sample (we may need a PostgreSQL server on the geoprisma.org machine), documentation and merge the branch to the trunk.&lt;br /&gt;
* (2) GeoPrisma: #164 - Add Vector layer type support for MapFishPrint service.&lt;br /&gt;
* (2) GeoExt ux - [http://dev.geoext.org/sandbox/mapgears/geoext.ux/ux/LayerTreeBuilder/examples/tree-builder.html LayerTreeBuilder] officialisation&lt;br /&gt;
 * create ticket in [http://trac.geoext.org/ GeoExt TRAC]&lt;br /&gt;
 * create a patch with an example and test units (with OpenLayers 2.10 and GeoExt 1.0)&lt;br /&gt;
 * create a [http://trac.geoext.org/wiki/Community wiki page] for the ux explaining it&lt;br /&gt;
 * ask a review to a core commiter&lt;br /&gt;
* (2) GeoExt ux - [http://dev.geoext.org/sandbox/mapgears/geoext.ux/ux/WMSBrowser/examples/WMSBrowser.html WMSBrowser] officialisation&lt;br /&gt;
 * create ticket in [http://trac.geoext.org/ GeoExt TRAC]&lt;br /&gt;
 * create a patch with an example and test units (with OpenLayers 2.10 and GeoExt 1.0)&lt;br /&gt;
 * create a [http://trac.geoext.org/wiki/Community wiki page] for the ux explaining it&lt;br /&gt;
 * ask a review to a core commiter&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''If we have more time'''&lt;br /&gt;
&lt;br /&gt;
* (2) GeoPrisma - WPS service and proxy&lt;br /&gt;
* (2) GeoExt ux - LayerTreeBuilder: add support for multiple layers when calling a WMS service.&lt;br /&gt;
* (3) GeoPrisma: #168 - switch to ExtJS-style i18n for client widgets (maybe do 1 or 2 widgets as a proof-of-concept)&lt;br /&gt;
* (3) GeoPrisma: #149 - deprecate the PDFPrint widget ?&lt;br /&gt;
* (2) GeoPrisma: Try to setup and support mod-geocache&lt;br /&gt;
&lt;br /&gt;
== OpenLayers ==&lt;br /&gt;
&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category: Code Sprints]]&lt;/div&gt;</summary>
		<author><name>Wiki-Adube</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Montreal_Code_Sprint_2011_Agenda&amp;diff=53858</id>
		<title>Montreal Code Sprint 2011 Agenda</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Montreal_Code_Sprint_2011_Agenda&amp;diff=53858"/>
		<updated>2011-03-15T18:55:20Z</updated>

		<summary type="html">&lt;p&gt;Wiki-Adube: /* GeoPrisma / OpenLayers / GeoExt */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Theme ==&lt;br /&gt;
&lt;br /&gt;
[[Montreal Code Sprint 2011]] : '''The Rendez-vous of the Tribes'''&lt;br /&gt;
&lt;br /&gt;
Sending out a clear message that we'd like to see members of all OSGeo tribes (C/C++, Java, JavaScript, C#, etc.) join forces for the advancement of OSGeo technologies. Last year's sprint in NYC helped foster synergies between the tribes and we want this to continue even stronger.&lt;br /&gt;
&lt;br /&gt;
== MapServer ==&lt;br /&gt;
&lt;br /&gt;
* 6.0 Release work (documentation, polishing and bug fixes)&lt;br /&gt;
* SVG Symbols (assefa, zak, thomas)&lt;br /&gt;
* rendering features with offset + leader (assefa, zak, thomas)&lt;br /&gt;
* Outputformat refactoring (don't create and initialize all default outputformats at each request) (thomas)&lt;br /&gt;
* Text rendering =&amp;gt; always use labelpathobj (thomas)&lt;br /&gt;
* rasterBufferObj: premultiplied or not? (thomas, frankw)&lt;br /&gt;
* INSPIRE View Services support for WMS (TomK, assefa, etc.)&lt;br /&gt;
* Ruby/SWIG MapScript (JimK)&lt;br /&gt;
* layer level GEOMTRANSFORM (Steve)&lt;br /&gt;
* use case snippets (see OpenLayers as an example) (Steve)&lt;br /&gt;
* profiling 6.0 ahead of benchmarking exercise  (need feedback from Jeff/Daniel on where we sucked)&lt;br /&gt;
&lt;br /&gt;
== PostGIS ==&lt;br /&gt;
&lt;br /&gt;
* 3D index issues outline support whether we'll have one or 2 types of parallel indices (prefer one type even if it means putting off til 2.1)&lt;br /&gt;
* 9.1 KNN GIST  are we going to do or punt to 2.1&lt;br /&gt;
* Left over issues with EMPTY and new more ISO compliant WKT display of geometries&lt;br /&gt;
* Make geometry_columns a view rather than table - harmonize legacy with new to cause least pain&lt;br /&gt;
* Possibility of preliminary X3D support in 2.0 instead of 2.1 (Olivier) ( http://trac.osgeo.org/postgis/ticket/854 )&lt;br /&gt;
* 3D topological serialization for PolyhedralSurface and TIN (Olivier)&lt;br /&gt;
* shp2pgsql (-gui)/pgsql2shp - (Jeff Adams)&lt;br /&gt;
    while you are at it would be really nice to investigate http://trac.osgeo.org/postgis/ticket/808 &lt;br /&gt;
     got broken in 2.0 and a real show-stopper for PostGIS 2.0 release&lt;br /&gt;
&lt;br /&gt;
  Also add more regression tests for shp2pgsql,pgsql2shp&lt;br /&gt;
* Incubation issues -- not fun stuff but needs to be addressed, get list of all contributors, decide if each file will have blanket copyright with reference to contributor file, what to do with files that have no copyright markings&lt;br /&gt;
&lt;br /&gt;
== PostGIS raster ==&lt;br /&gt;
&lt;br /&gt;
*Ticket fixes Pierre: (792 &amp;amp; 762), 825, 633, 766, 651, 490,&lt;br /&gt;
*Ticket fixes David: 582&lt;br /&gt;
*Ticket fixes Jorge: 851, 837&lt;br /&gt;
*Look at ticket 650 (GDAL Polygonize with real values) with Frank (Pierre)&lt;br /&gt;
*ST_SetRotation &amp;amp; ST_Rotation (ticket 482) (David)&lt;br /&gt;
*rt_raster_deserialize for header only in order to make get functions faster&lt;br /&gt;
*pl/pgSQL script fixes (tickets 643, 644, 645) (Pierre)&lt;br /&gt;
*ST_MapAlgebra optimization &amp;amp; neighbourhood (David)&lt;br /&gt;
*ST_Intersection optimization (David)&lt;br /&gt;
*Optional tickets 165, 301, 484&lt;br /&gt;
&lt;br /&gt;
== GDAL/OGR ==&lt;br /&gt;
&lt;br /&gt;
* SWIG/Ruby bindings? (JimK)&lt;br /&gt;
* Merge the two MrSID Drivers (Raster and Lidar) into one&lt;br /&gt;
&lt;br /&gt;
== libLAS  ==&lt;br /&gt;
&lt;br /&gt;
* Discussions&lt;br /&gt;
** hobu to talk about technologies, intents, and targeted platforms for libPC&lt;br /&gt;
** mpg to discuss/demonstrate the Stage model that libPC sets up&lt;br /&gt;
** mpg to give a small code walkthrough via projector&lt;br /&gt;
** Try to get FrankW to discuss features/failures/successes of both GDAL and OGR's driver models&lt;br /&gt;
** Investigate and discuss using boost-style traits for class description&lt;br /&gt;
** Investigate Point Cloud Library's (PCL) template-driven point classes and their applicability and/or adaptability for libPC.&lt;br /&gt;
&lt;br /&gt;
* Technical support / Infrastructure&lt;br /&gt;
** Get hg access for all sprint participants&lt;br /&gt;
** Bootstrap people building libPC on their own computers (writing docs as we go)&lt;br /&gt;
** hobu to stand up libpc.org with Trac/HG/Sphinx&lt;br /&gt;
** Add CMake detection for MG4&lt;br /&gt;
** test harness for the command line apps&lt;br /&gt;
&lt;br /&gt;
* Development&lt;br /&gt;
** Crib up the text, MG4, and BAG drivers&lt;br /&gt;
** Add MG4/L support to libPC&lt;br /&gt;
** Plan for adding octree libpc::Stage&lt;br /&gt;
** finish the native LAS driver&lt;br /&gt;
** flesh out the dump routines for each major class&lt;br /&gt;
** light up pcinfo&lt;br /&gt;
&lt;br /&gt;
== TinyOWS ==&lt;br /&gt;
&lt;br /&gt;
* MapFile parser, to allow a single configuration file for both MapServer and TinyOWS.&lt;br /&gt;
&lt;br /&gt;
== ZOO Project ==&lt;br /&gt;
&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
== GeoPrisma / OpenLayers / GeoExt ==&lt;br /&gt;
&lt;br /&gt;
'''Objectives, with (priority)'''&lt;br /&gt;
&lt;br /&gt;
* (1) GeoPrisma: WFS&lt;br /&gt;
 * Add service and proxy&lt;br /&gt;
 * Adapt existing widgets currently using featureserver to support wfs as well (editing, shortcut, etc.)&lt;br /&gt;
&lt;br /&gt;
* (1) GeoPrisma: Demo with :&lt;br /&gt;
 * GeoPrisma (trunk) using the PGSQLMapContext config driver&lt;br /&gt;
 * GMap data (postgis &amp;amp; shapefiles)&lt;br /&gt;
 * MapServer (trunk) - WMS&lt;br /&gt;
 * TinyOWS (trunk) - WFST (using MapServer mapfile)&lt;br /&gt;
 * MapFishPrint, supporting vector printing&lt;br /&gt;
 * ZooProject - WPS&lt;br /&gt;
&lt;br /&gt;
* GeoExt ux - LayerTreeBuilder: make the display of a Legend widget configurable on a per-layer basis?? (instead of on per-layer type basis).&lt;br /&gt;
* (1) GeoExt ux - AttributeFilterPanel: add flexibility in how the Vector features are retrieved (i.e. using a Vector layer object to query an existing layer or using a Protocol object and creating a new Vector layer on the fly). This widget has a lot of overlap with GeoExt's FormPanel (in fact it was derived from it), we should try to merge the functionality of both widgets in a single one.&lt;br /&gt;
* (1) GeoPrisma - AttributeFilterPanel widget: #175 - write a sample (we may need a PostgreSQL server on the geoprisma.org machine), documentation and merge the branch to the trunk.&lt;br /&gt;
* (2) GeoPrisma: #164 - Add Vector layer type support for MapFishPrint service.&lt;br /&gt;
* (2) GeoExt ux - [http://dev.geoext.org/sandbox/mapgears/geoext.ux/ux/LayerTreeBuilder/examples/tree-builder.html LayerTreeBuilder] officialisation&lt;br /&gt;
 * create ticket in [http://trac.geoext.org/ GeoExt TRAC]&lt;br /&gt;
 * create a patch with an example and test units (with OpenLayers 2.10 and GeoExt 1.0)&lt;br /&gt;
 * create a [http://trac.geoext.org/wiki/Community wiki page] for the ux explaining it&lt;br /&gt;
 * ask a review to a core commiter&lt;br /&gt;
* (2) GeoExt ux - [http://dev.geoext.org/sandbox/mapgears/geoext.ux/ux/WMSBrowser/examples/WMSBrowser.html WMSBrowser] officialisation&lt;br /&gt;
 * create ticket in [http://trac.geoext.org/ GeoExt TRAC]&lt;br /&gt;
 * create a patch with an example and test units (with OpenLayers 2.10 and GeoExt 1.0)&lt;br /&gt;
 * create a [http://trac.geoext.org/wiki/Community wiki page] for the ux explaining it&lt;br /&gt;
 * ask a review to a core commiter&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''If we have more time'''&lt;br /&gt;
&lt;br /&gt;
* (2) GeoPrisma - WPS service and proxy&lt;br /&gt;
* (2) GeoExt ux - LayerTreeBuilder: add support for multiple layers when calling a WMS service.&lt;br /&gt;
* (3) GeoPrisma: #168 - switch to ExtJS-style i18n for client widgets (maybe do 1 or 2 widgets as a proof-of-concept)&lt;br /&gt;
* (3) GeoPrisma: #149 - deprecate the PDFPrint widget ?&lt;br /&gt;
* (?) GeoPrisma: make projection configurable for measuretool widget, just like what was done with getmouseposition (using proj4js)&lt;br /&gt;
* (2) GeoPrisma: Try to setup and support mod-geocache&lt;br /&gt;
&lt;br /&gt;
== OpenLayers ==&lt;br /&gt;
&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category: Code Sprints]]&lt;/div&gt;</summary>
		<author><name>Wiki-Adube</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Montreal_Code_Sprint_2011_Agenda&amp;diff=53857</id>
		<title>Montreal Code Sprint 2011 Agenda</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Montreal_Code_Sprint_2011_Agenda&amp;diff=53857"/>
		<updated>2011-03-15T18:47:29Z</updated>

		<summary type="html">&lt;p&gt;Wiki-Adube: /* GeoPrisma / OpenLayers / GeoExt */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Theme ==&lt;br /&gt;
&lt;br /&gt;
[[Montreal Code Sprint 2011]] : '''The Rendez-vous of the Tribes'''&lt;br /&gt;
&lt;br /&gt;
Sending out a clear message that we'd like to see members of all OSGeo tribes (C/C++, Java, JavaScript, C#, etc.) join forces for the advancement of OSGeo technologies. Last year's sprint in NYC helped foster synergies between the tribes and we want this to continue even stronger.&lt;br /&gt;
&lt;br /&gt;
== MapServer ==&lt;br /&gt;
&lt;br /&gt;
* 6.0 Release work (documentation, polishing and bug fixes)&lt;br /&gt;
* SVG Symbols (assefa, zak, thomas)&lt;br /&gt;
* rendering features with offset + leader (assefa, zak, thomas)&lt;br /&gt;
* Outputformat refactoring (don't create and initialize all default outputformats at each request) (thomas)&lt;br /&gt;
* Text rendering =&amp;gt; always use labelpathobj (thomas)&lt;br /&gt;
* rasterBufferObj: premultiplied or not? (thomas, frankw)&lt;br /&gt;
* INSPIRE View Services support for WMS (TomK, assefa, etc.)&lt;br /&gt;
* Ruby/SWIG MapScript (JimK)&lt;br /&gt;
* layer level GEOMTRANSFORM (Steve)&lt;br /&gt;
* use case snippets (see OpenLayers as an example) (Steve)&lt;br /&gt;
* profiling 6.0 ahead of benchmarking exercise  (need feedback from Jeff/Daniel on where we sucked)&lt;br /&gt;
&lt;br /&gt;
== PostGIS ==&lt;br /&gt;
&lt;br /&gt;
* 3D index issues outline support whether we'll have one or 2 types of parallel indices (prefer one type even if it means putting off til 2.1)&lt;br /&gt;
* 9.1 KNN GIST  are we going to do or punt to 2.1&lt;br /&gt;
* Left over issues with EMPTY and new more ISO compliant WKT display of geometries&lt;br /&gt;
* Make geometry_columns a view rather than table - harmonize legacy with new to cause least pain&lt;br /&gt;
* Possibility of preliminary X3D support in 2.0 instead of 2.1 (Olivier) ( http://trac.osgeo.org/postgis/ticket/854 )&lt;br /&gt;
* 3D topological serialization for PolyhedralSurface and TIN (Olivier)&lt;br /&gt;
* shp2pgsql (-gui)/pgsql2shp - (Jeff Adams)&lt;br /&gt;
    while you are at it would be really nice to investigate http://trac.osgeo.org/postgis/ticket/808 &lt;br /&gt;
     got broken in 2.0 and a real show-stopper for PostGIS 2.0 release&lt;br /&gt;
&lt;br /&gt;
  Also add more regression tests for shp2pgsql,pgsql2shp&lt;br /&gt;
* Incubation issues -- not fun stuff but needs to be addressed, get list of all contributors, decide if each file will have blanket copyright with reference to contributor file, what to do with files that have no copyright markings&lt;br /&gt;
&lt;br /&gt;
== PostGIS raster ==&lt;br /&gt;
&lt;br /&gt;
*Ticket fixes Pierre: (792 &amp;amp; 762), 825, 633, 766, 651, 490,&lt;br /&gt;
*Ticket fixes David: 582&lt;br /&gt;
*Ticket fixes Jorge: 851, 837&lt;br /&gt;
*Look at ticket 650 (GDAL Polygonize with real values) with Frank (Pierre)&lt;br /&gt;
*ST_SetRotation &amp;amp; ST_Rotation (ticket 482) (David)&lt;br /&gt;
*rt_raster_deserialize for header only in order to make get functions faster&lt;br /&gt;
*pl/pgSQL script fixes (tickets 643, 644, 645) (Pierre)&lt;br /&gt;
*ST_MapAlgebra optimization &amp;amp; neighbourhood (David)&lt;br /&gt;
*ST_Intersection optimization (David)&lt;br /&gt;
*Optional tickets 165, 301, 484&lt;br /&gt;
&lt;br /&gt;
== GDAL/OGR ==&lt;br /&gt;
&lt;br /&gt;
* SWIG/Ruby bindings? (JimK)&lt;br /&gt;
* Merge the two MrSID Drivers (Raster and Lidar) into one&lt;br /&gt;
&lt;br /&gt;
== libLAS  ==&lt;br /&gt;
&lt;br /&gt;
* Discussions&lt;br /&gt;
** hobu to talk about technologies, intents, and targeted platforms for libPC&lt;br /&gt;
** mpg to discuss/demonstrate the Stage model that libPC sets up&lt;br /&gt;
** mpg to give a small code walkthrough via projector&lt;br /&gt;
** Try to get FrankW to discuss features/failures/successes of both GDAL and OGR's driver models&lt;br /&gt;
** Investigate and discuss using boost-style traits for class description&lt;br /&gt;
** Investigate Point Cloud Library's (PCL) template-driven point classes and their applicability and/or adaptability for libPC.&lt;br /&gt;
&lt;br /&gt;
* Technical support / Infrastructure&lt;br /&gt;
** Get hg access for all sprint participants&lt;br /&gt;
** Bootstrap people building libPC on their own computers (writing docs as we go)&lt;br /&gt;
** hobu to stand up libpc.org with Trac/HG/Sphinx&lt;br /&gt;
** Add CMake detection for MG4&lt;br /&gt;
** test harness for the command line apps&lt;br /&gt;
&lt;br /&gt;
* Development&lt;br /&gt;
** Crib up the text, MG4, and BAG drivers&lt;br /&gt;
** Add MG4/L support to libPC&lt;br /&gt;
** Plan for adding octree libpc::Stage&lt;br /&gt;
** finish the native LAS driver&lt;br /&gt;
** flesh out the dump routines for each major class&lt;br /&gt;
** light up pcinfo&lt;br /&gt;
&lt;br /&gt;
== TinyOWS ==&lt;br /&gt;
&lt;br /&gt;
* MapFile parser, to allow a single configuration file for both MapServer and TinyOWS.&lt;br /&gt;
&lt;br /&gt;
== ZOO Project ==&lt;br /&gt;
&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
== GeoPrisma / OpenLayers / GeoExt ==&lt;br /&gt;
&lt;br /&gt;
'''Objectives, with (priority)'''&lt;br /&gt;
&lt;br /&gt;
* (1) GeoPrisma: WFS&lt;br /&gt;
 * Add service and proxy&lt;br /&gt;
 * Adapt existing widgets currently using featureserver to support wfs as well (editing, shortcut, etc.)&lt;br /&gt;
&lt;br /&gt;
* (1) GeoPrisma: Demo with :&lt;br /&gt;
 * GeoPrisma (trunk) using the PGSQLMapContext config driver&lt;br /&gt;
 * GMap data (postgis &amp;amp; shapefiles)&lt;br /&gt;
 * MapServer (trunk) - WMS&lt;br /&gt;
 * TinyOWS (trunk) - WFST (using MapServer mapfile)&lt;br /&gt;
 * MapFishPrint, supporting vector printing&lt;br /&gt;
 * ZooProject - WPS&lt;br /&gt;
&lt;br /&gt;
* GeoExt ux - LayerTreeBuilder: make the display of a Legend widget configurable on a per-layer basis?? (instead of on per-layer type basis).&lt;br /&gt;
* (1) GeoExt ux - AttributeFilterPanel: add flexibility in how the Vector features are retrieved (i.e. using a Vector layer object to query an existing layer or using a Protocol object and creating a new Vector layer on the fly). This widget has a lot of overlap with GeoExt's FormPanel (in fact it was derived from it), we should try to merge the functionality of both widgets in a single one.&lt;br /&gt;
* (1) GeoPrisma - AttributeFilterPanel widget: #175 - write a sample (we may need a PostgreSQL server on the geoprisma.org machine), documentation and merge the branch to the trunk.&lt;br /&gt;
* (2) GeoPrisma: #164 - Add Vector layer type support for MapFishPrint service.&lt;br /&gt;
&lt;br /&gt;
'''If we have more time'''&lt;br /&gt;
&lt;br /&gt;
* (2) GeoPrisam - WPS service and proxy&lt;br /&gt;
* (2) GeoExt ux - LayerTreeBuilder: add support for multiple layers when calling a WMS service.&lt;br /&gt;
* (3) GeoPrisma: #168 - switch to ExtJS-style i18n for client widgets (maybe do 1 or 2 widgets as a proof-of-concept)&lt;br /&gt;
* (3) GeoPrisma: #149 - deprecate the PDFPrint widget ?&lt;br /&gt;
* (?) GeoPrisma: make projection configurable for measuretool widget, just like what was done with getmouseposition (using proj4js)&lt;br /&gt;
* (2) GeoPrisma: Try to setup and support mod-geocache in&lt;br /&gt;
&lt;br /&gt;
== OpenLayers ==&lt;br /&gt;
&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category: Code Sprints]]&lt;/div&gt;</summary>
		<author><name>Wiki-Adube</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Montreal_Code_Sprint_2011&amp;diff=53555</id>
		<title>Montreal Code Sprint 2011</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Montreal_Code_Sprint_2011&amp;diff=53555"/>
		<updated>2011-03-01T19:46:48Z</updated>

		<summary type="html">&lt;p&gt;Wiki-Adube: /* Participation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Purpose ==&lt;br /&gt;
&lt;br /&gt;
Get together project members to make decisions and tackle larger problems (as done in previous years at the [[New York Code Sprint 2010]] and [[Toronto Code Sprint 2009]]).&lt;br /&gt;
&lt;br /&gt;
We have started a [[Montreal Code Sprint 2011 Agenda]] page for preliminary planning of tasks.&lt;br /&gt;
&lt;br /&gt;
== Timing ==&lt;br /&gt;
&lt;br /&gt;
Dates: Tuesday-Friday, March 15-18, from approximately 9am-5pm&lt;br /&gt;
&lt;br /&gt;
== Venue ==&lt;br /&gt;
&lt;br /&gt;
Communauté Métropolitaine de Montréal (CMM)&lt;br /&gt;
[http://maps.google.ca/maps?f=q&amp;amp;source=s_q&amp;amp;hl=en&amp;amp;geocode=&amp;amp;q=1002+sherbrooke+west+montreal+qc&amp;amp;sll=45.502703,-73.575719&amp;amp;sspn=0.00943,0.014977&amp;amp;ie=UTF8&amp;amp;hq=&amp;amp;hnear=1002+Rue+Sherbrooke+Ouest,+Montr%C3%A9al,+Communaut%C3%A9-Urbaine-de-Montr%C3%A9al,+Qu%C3%A9bec+H3A+1Y1&amp;amp;z=16 1002, Sherbrooke West, suite 2400, Montreal QC]&lt;br /&gt;
&lt;br /&gt;
* 2 large adjacent conference rooms located on 24th floor of a tower with great view of the city ([[Montreal Code Sprint 2011 - Possible Venues#pictures-cmm |see pictures]])&lt;br /&gt;
* Possibility to remove the wall between the two rooms to make a single larger room&lt;br /&gt;
* RJ-45 and power plugs in the floor&lt;br /&gt;
* Larger room: 14 tables for two = 28 person capacity&lt;br /&gt;
* Smaller room: 6 tables for two = 12 person capacity&lt;br /&gt;
* Possibility to rearrange the tables to fit our needs (e.g. make tables/teams of 6-8 people for instance)&lt;br /&gt;
* Projector in each room&lt;br /&gt;
* White boards on the wall between the two rooms (become unavailable if we remove the wall)&lt;br /&gt;
&lt;br /&gt;
== Sponsors ==&lt;br /&gt;
&lt;br /&gt;
We will again be looking for sponsors ($750) to support food and fun for the sprinters as they work hard and play hard for four productive days. Each $750 sponsorship will be put towards lunch and dinner costs for the sprinters, and potentially bringing in sprinters who might otherwise be unable to attend. &lt;br /&gt;
&lt;br /&gt;
To sponsor, please contact Daniel Morissette (dmorissette at mapgears dot com) directly.&lt;br /&gt;
&lt;br /&gt;
=== 2011 Sponsors ===&lt;br /&gt;
&lt;br /&gt;
750$ Sponsors:&lt;br /&gt;
* [http://www.lizardtech.com/ LizardTech]&lt;br /&gt;
* [http://www.azavea.com/ Azavea]&lt;br /&gt;
* [http://qpublic.net/ qPublic]&lt;br /&gt;
* [http://fargeo.com/ Farallon Geographics]&lt;br /&gt;
* [http://airborne.aero/ Airborne Interactive]&lt;br /&gt;
* [http://www.boreal-is.com/ Boreal - Information Strategies (Borealis)]&lt;br /&gt;
&lt;br /&gt;
Hockey Night Sponsor:&lt;br /&gt;
* [http://gatewaygeomatics.com/ Gateway Geomatics]&lt;br /&gt;
&lt;br /&gt;
Host (Room and Internet):&lt;br /&gt;
* [http://cmm.qc.ca/ Communauté Métropolitaine de Montréal (CMM)]&lt;br /&gt;
&lt;br /&gt;
== Budget ==&lt;br /&gt;
&lt;br /&gt;
* The 2011 budget is available online [https://spreadsheets.google.com/pub?hl=en&amp;amp;hl=en&amp;amp;key=0Av9Xf1ehZXz-dG4yTzQwSTVJM0sxOVNBNFdWS2dKdHc&amp;amp;single=true&amp;amp;gid=0&amp;amp;output=html here]&lt;br /&gt;
* Any surplus at the end of the event will be turned over to [http://osgeo.org/ OSGeo] or used for a future code sprint&lt;br /&gt;
&lt;br /&gt;
== Hotel ==&lt;br /&gt;
&lt;br /&gt;
* [http://hotelcantlie.com/ Hotel Cantlie Suites], located 1-2 blocks away: Group rate starting at 99$/night + taxes&lt;br /&gt;
&lt;br /&gt;
We have a group reservation. Here's the link to reserve your room:&lt;br /&gt;
&lt;br /&gt;
* English: https://reservations.ihotelier.com/crs/g_reservation.cfm?groupID=544358&amp;amp;hotelID=12608&amp;amp;languageid=1&lt;br /&gt;
* Français: https://reservations.ihotelier.com/crs/g_reservation.cfm?groupID=544358&amp;amp;hotelID=12608&amp;amp;languageid=3&lt;br /&gt;
&lt;br /&gt;
== Costs ==&lt;br /&gt;
&lt;br /&gt;
Participants should plan for the following costs:&lt;br /&gt;
&lt;br /&gt;
* Travel to Montreal, variable depending on where you are.&lt;br /&gt;
* Accommodation for four nights, $200 to $600 depending on what room you choose and whether you room share.&lt;br /&gt;
* Breakfast, dinner and other snacks.&lt;br /&gt;
* The sponsorship moneys will be put towards: morning snacks, lunches, dinner(s), social event (?)&lt;br /&gt;
&lt;br /&gt;
== Communication ==&lt;br /&gt;
&lt;br /&gt;
* Please join the mailing list:&amp;lt;br&amp;gt;http://lists.osgeo.org/mailman/listinfo/tosprint&lt;br /&gt;
&lt;br /&gt;
* IRC chat during the event:&amp;lt;br&amp;gt;Channel: #tosprint&amp;lt;br&amp;gt;Server: irc.freenode.net&lt;br /&gt;
&lt;br /&gt;
== Participation ==&lt;br /&gt;
&lt;br /&gt;
We are planning for attendance of 20-40. Please add your name and the projects you are hoping to sprint on, if you have a strong intention to attend. &lt;br /&gt;
&lt;br /&gt;
'''Update 2011-03-01: To help with planning, please confirm your participation in each of the code sprint days and nights activities via Doodle at [http://doodle.com/n99d4fkhsid4ghap http://doodle.com/n99d4fkhsid4ghap].'''&lt;br /&gt;
 &lt;br /&gt;
# [[User:Dmorissette|Daniel Morissette]] (MapServer, GDAL/OGR)&lt;br /&gt;
# [[User:msmitherdc|Michael Smith]] (MapServer, libLAS)&lt;br /&gt;
# [[User:dzwarg|David Zwarg]] (PostGIS)&lt;br /&gt;
# [[User:jadams|Jeff Adams]] (PostGIS)&lt;br /&gt;
# Frank Warmerdam (MapServer, GDAL, ...)&lt;br /&gt;
# [[User:olivier.courtin|Olivier Courtin]] (PostGIS - TinyOWS)&lt;br /&gt;
# [[User:pwramsey3|Paul Ramsey]] (PostGIS)&lt;br /&gt;
# [[User:jmckenna|Jeff McKenna]] (MapServer)&lt;br /&gt;
# [[User:assefa|Yewondwossen Assefa]] (MapServer)&lt;br /&gt;
# [[User:aboudreault|Alan Boudreault]] (MapServer)&lt;br /&gt;
# [[User:hobu|Howard Butler]] (MapServer libLAS GDAL)&lt;br /&gt;
# [[User:tbonfort|Thomas Bonfort]] (MapServer)&lt;br /&gt;
# [[User:mpg|Michael P. Gerlek]] (libLAS, C# tribe)&lt;br /&gt;
# [[User:tomkralidis|Tom Kralidis]] (MapServer) (Wed-Fri)&lt;br /&gt;
# [[User:djay|Gérald Fenoy]] (ZOO-Project)&lt;br /&gt;
# [[User:mrosen|Michael Rosen]] (liblas, gdal)&lt;br /&gt;
# Nicolas Bozon (ZOO-Project)&lt;br /&gt;
# Steve Lime (MapServer) (Tue-Thu)&lt;br /&gt;
# [[User:pierre|Pierre Racine]] (PostGIS raster)&lt;br /&gt;
# [[User:Schpidi|Stephan Meißl]] (MapServer)&lt;br /&gt;
# [[User:zjames|Zak James]] (MapServer)&lt;br /&gt;
# [[User:kirk|Kirk McKelvey]] (mrsid, liblas, gdal)&lt;br /&gt;
# [[User:quentonc|Pete Gadomski]] (liblas)&lt;br /&gt;
# Jim Klassen (MapServer, GDAL)&lt;br /&gt;
# Alexandre Dubé (GeoPrisma, OpenLayers, GeoExt)&lt;br /&gt;
# Julien-Samuel Lacroix (MapServer, GeoPrisma, OpenLayers, GeoExt)&lt;br /&gt;
&lt;br /&gt;
Virtual participants (irc #tosprint)&lt;br /&gt;
&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
== Room Share ==&lt;br /&gt;
&lt;br /&gt;
If you would like to room share, &lt;br /&gt;
&lt;br /&gt;
# Reserve a room at the hotel, choosing a type with more than one bed.&lt;br /&gt;
# Put your name in this section, indicating the amount of space in your room.&lt;br /&gt;
&lt;br /&gt;
Put your names below:&lt;br /&gt;
&lt;br /&gt;
* example entry: B has a triple room, needs two roommates.&lt;br /&gt;
&lt;br /&gt;
Special offer: I, [[User:Aleroux|Alexandre Leroux]], can provide free lodging for the whole event with these parameters: one double bed, private access (we'll let you a key), private kitchen with fridge, private shower and toilet. Internet wifi included. It's a 2-minutes walk from the Snowdon subway station, making it easy to go to the Code Sprint. That would be on the basement of where my wife, daughter and myself live. If interested, contact me directly.&lt;br /&gt;
&lt;br /&gt;
== Individual Preparation ==&lt;br /&gt;
&lt;br /&gt;
* Bring your own computer&lt;br /&gt;
* Install subversion and the compiler tools, and come with a working development environment if possible.&lt;br /&gt;
&lt;br /&gt;
== FAQ ==&lt;br /&gt;
&lt;br /&gt;
* Is the Montreal Code Sprint just a coding event?&lt;br /&gt;
** Yes, a coding and documentation event. It is a working session for people who are already participants in open source projects.&lt;br /&gt;
* Will it be possible to present new projects during this event?&lt;br /&gt;
** No, this is not a presentation-oriented event. People will get together in small groups and work on areas of mutual interest within their projects.&lt;br /&gt;
&lt;br /&gt;
== Social Events ==&lt;br /&gt;
&lt;br /&gt;
* Monday March 14, 2011 @5pm: OSGeo-Québec 5 à 7 / Code Sprint Ice breaker. On the 2nd floor of http://www.mcleanspub.com/ 1210 Peel St, Montreal (450m South of the Cantlies Suites hotel on Peel Street)&lt;br /&gt;
* Tuesday March 15, 2011 @5:30pm: Dinner at Dundee's Bar &amp;amp; Grill (2010 Crescent Street, [http://maps.google.ca/maps/place?hl=en&amp;amp;client=firefox-a&amp;amp;hs=jUq&amp;amp;rls=org.mozilla:en-US:official&amp;amp;um=1&amp;amp;ie=UTF-8&amp;amp;q=dundees+bar+and+grill+montreal&amp;amp;fb=1&amp;amp;gl=ca&amp;amp;hq=dundees+bar+and+grill&amp;amp;hnear=Montreal,+QC&amp;amp;cid=7637348018275249337 map]) &lt;br /&gt;
* Wednesday March 16, 2011 @5:30pm: Dinner at Le Milsa http://www.lemilsa.com/lemilsa/index.html (1445-A Bishop Street, [http://maps.google.ca/maps?f=q&amp;amp;source=s_q&amp;amp;hl=en&amp;amp;geocode=&amp;amp;q=Le+Milsa+Restaurant,+Montreal,+Quebec&amp;amp;aq=0&amp;amp;gl=ca&amp;amp;g=2010+Crescent+St,+Montr%C3%A9al,+QC+H3G+2B8&amp;amp;ie=UTF8&amp;amp;hq=Le+Milsa+Restaurant,&amp;amp;hnear=Montreal,+Communaut%C3%A9-Urbaine-de-Montr%C3%A9al,+Quebec&amp;amp;ll=45.497203,-73.577242&amp;amp;spn=0.026772,0.071583&amp;amp;z=14 map])&lt;br /&gt;
** &amp;quot;Brazilian &amp;quot;Churrasco&amp;quot;: an all you can eat meat experience that you'll remember, also includes animation from Brazilian dancers.&lt;br /&gt;
* Thursday March 17, 2011 @5:30pm: watch a hockey game at Verdun Auditorium (7:05PM start) courtesy of Gateway Gemomatics (details)&lt;br /&gt;
* Friday March 18, 2011 evening: &amp;quot;networking&amp;quot; at a local establishment&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
== Eating Options ==&lt;br /&gt;
&lt;br /&gt;
Some locations recommended by locals:&lt;br /&gt;
&lt;br /&gt;
* Restaurants&lt;br /&gt;
** ...&lt;br /&gt;
* Bars&lt;br /&gt;
** &lt;br /&gt;
&lt;br /&gt;
(Please do not hesitate to add locations to this list)&lt;br /&gt;
&lt;br /&gt;
== Getting to the Sprint ==&lt;br /&gt;
&lt;br /&gt;
=== From Trudeau International Airport (YUL) ===&lt;br /&gt;
&lt;br /&gt;
Unfortunately there is no shuttle that goes straight from the airport to the hotel. &lt;br /&gt;
&lt;br /&gt;
Here are some options (See also [http://maps.google.com/maps?f=d&amp;amp;source=s_d&amp;amp;saddr=45.454231,-73.748131&amp;amp;daddr=1110+Rue+Sherbrooke+Ouest,+Montr%C3%A9al,+QC+H3A+1G6,+Canada&amp;amp;hl=en&amp;amp;geocode=%3BFRxMtgIdbU-d-ynR5QLZQBrJTDE5mLJmp5RZkQ&amp;amp;mra=dme&amp;amp;mrsp=0&amp;amp;sz=13&amp;amp;dirflg=r&amp;amp;ttype=dep&amp;amp;date=02%2F25%2F11&amp;amp;time=7:22am&amp;amp;noexp=0&amp;amp;noal=0&amp;amp;sort=def&amp;amp;sll=45.469521,-73.682384&amp;amp;sspn=0.099197,0.222301&amp;amp;ie=UTF8&amp;amp;ll=45.500813,-73.574409&amp;amp;spn=0.099141,0.222301&amp;amp;z=13&amp;amp;iwloc=statictransit:&amp;amp;start=0 Google Maps]):&lt;br /&gt;
&lt;br /&gt;
==== Option 1 - Express Bus 747 + Subway ====&lt;br /&gt;
&lt;br /&gt;
http://www.admtl.com/Passengers/AccessAndParking/STMBuses.aspx&lt;br /&gt;
&lt;br /&gt;
Take the 747 express bus from the Airport. The bus goes to Berri-UQAM, but do not go all the way to Berri-UQAM, you need to get off at the Lionel-Groulx stop, and then connect to the Metro Green Line (1) towards Station Honoré-Beaugrand. Get off at Station Peel (Stop ID: 10138). You are only 150m from Hotel Le Cantlie Suites.&lt;br /&gt;
&lt;br /&gt;
Cost: 8$. At the airport, tickets are sold at the International Currency Exchange (ICE) counter on the international arrivals level.&lt;br /&gt;
&lt;br /&gt;
==== Option 2 - Taxi ====&lt;br /&gt;
&lt;br /&gt;
http://www.admtl.com/Passengers/AccessAndParking/TaxisAndLimousines.aspx&lt;br /&gt;
&lt;br /&gt;
It seems that the simplest option is a taxi: there is a fixed price of 38$ for a ride downtown in the area of the hotel. (The person at the hotel insisted that this is a fixed price and if the driver asks for more then he is trying to screw you)&lt;br /&gt;
&lt;br /&gt;
==== Option 3 - Train + Subway ====&lt;br /&gt;
&lt;br /&gt;
VIA Rail offers a train shuttle from their Dorval train station to downtown (towards Montreal Central Station). The Dorval train station is not directly on the airport so you need to take the &amp;quot;AirConnect&amp;quot; shuttle to get to the train. More details here:&lt;br /&gt;
&lt;br /&gt;
http://www.viarail.ca/en/useful-info/related-services/montreal-airport-shuttle&lt;br /&gt;
&lt;br /&gt;
&amp;quot;After landing, go to the domestic or international flights terminal exit, where you'll see a clearly marked AirConnect stop. The shuttle comes by every 20 minutes, and will take you to the Dorval station for free.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Then Google suggests that the shortest route is to get off the train at Metro (Subway) Station Vendome, then take red line (2) towards Henri Bourassa and get off at Lionel Groulx. Finally take metro green line (1) towards Honoré-Beaugrand and get off at Peel. You are only 150m from Hotel Le Cantlie Suites.&lt;br /&gt;
&lt;br /&gt;
== Announcements, News, Recaps ==&lt;br /&gt;
&lt;br /&gt;
* &lt;br /&gt;
=== Photos ===&lt;br /&gt;
&lt;br /&gt;
* http://www.flickr.com/search/?q=montrealsprint2011&amp;amp;m=tags&lt;br /&gt;
&lt;br /&gt;
[[Category:Code Sprints]]&lt;br /&gt;
[[Category:Events]]&lt;/div&gt;</summary>
		<author><name>Wiki-Adube</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Montreal_Code_Sprint_2011&amp;diff=53550</id>
		<title>Montreal Code Sprint 2011</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Montreal_Code_Sprint_2011&amp;diff=53550"/>
		<updated>2011-03-01T19:41:43Z</updated>

		<summary type="html">&lt;p&gt;Wiki-Adube: /* Participation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Purpose ==&lt;br /&gt;
&lt;br /&gt;
Get together project members to make decisions and tackle larger problems (as done in previous years at the [[New York Code Sprint 2010]] and [[Toronto Code Sprint 2009]]).&lt;br /&gt;
&lt;br /&gt;
We have started a [[Montreal Code Sprint 2011 Agenda]] page for preliminary planning of tasks.&lt;br /&gt;
&lt;br /&gt;
== Timing ==&lt;br /&gt;
&lt;br /&gt;
Dates: Tuesday-Friday, March 15-18, from approximately 9am-5pm&lt;br /&gt;
&lt;br /&gt;
== Venue ==&lt;br /&gt;
&lt;br /&gt;
Communauté Métropolitaine de Montréal (CMM)&lt;br /&gt;
[http://maps.google.ca/maps?f=q&amp;amp;source=s_q&amp;amp;hl=en&amp;amp;geocode=&amp;amp;q=1002+sherbrooke+west+montreal+qc&amp;amp;sll=45.502703,-73.575719&amp;amp;sspn=0.00943,0.014977&amp;amp;ie=UTF8&amp;amp;hq=&amp;amp;hnear=1002+Rue+Sherbrooke+Ouest,+Montr%C3%A9al,+Communaut%C3%A9-Urbaine-de-Montr%C3%A9al,+Qu%C3%A9bec+H3A+1Y1&amp;amp;z=16 1002, Sherbrooke West, suite 2400, Montreal QC]&lt;br /&gt;
&lt;br /&gt;
* 2 large adjacent conference rooms located on 24th floor of a tower with great view of the city ([[Montreal Code Sprint 2011 - Possible Venues#pictures-cmm |see pictures]])&lt;br /&gt;
* Possibility to remove the wall between the two rooms to make a single larger room&lt;br /&gt;
* RJ-45 and power plugs in the floor&lt;br /&gt;
* Larger room: 14 tables for two = 28 person capacity&lt;br /&gt;
* Smaller room: 6 tables for two = 12 person capacity&lt;br /&gt;
* Possibility to rearrange the tables to fit our needs (e.g. make tables/teams of 6-8 people for instance)&lt;br /&gt;
* Projector in each room&lt;br /&gt;
* White boards on the wall between the two rooms (become unavailable if we remove the wall)&lt;br /&gt;
&lt;br /&gt;
== Sponsors ==&lt;br /&gt;
&lt;br /&gt;
We will again be looking for sponsors ($750) to support food and fun for the sprinters as they work hard and play hard for four productive days. Each $750 sponsorship will be put towards lunch and dinner costs for the sprinters, and potentially bringing in sprinters who might otherwise be unable to attend. &lt;br /&gt;
&lt;br /&gt;
To sponsor, please contact Daniel Morissette (dmorissette at mapgears dot com) directly.&lt;br /&gt;
&lt;br /&gt;
=== 2011 Sponsors ===&lt;br /&gt;
&lt;br /&gt;
750$ Sponsors:&lt;br /&gt;
* [http://www.lizardtech.com/ LizardTech]&lt;br /&gt;
* [http://www.azavea.com/ Azavea]&lt;br /&gt;
* [http://qpublic.net/ qPublic]&lt;br /&gt;
* [http://fargeo.com/ Farallon Geographics]&lt;br /&gt;
* [http://airborne.aero/ Airborne Interactive]&lt;br /&gt;
* [http://www.boreal-is.com/ Boreal - Information Strategies (Borealis)]&lt;br /&gt;
&lt;br /&gt;
Hockey Night Sponsor:&lt;br /&gt;
* [http://gatewaygeomatics.com/ Gateway Geomatics]&lt;br /&gt;
&lt;br /&gt;
Host (Room and Internet):&lt;br /&gt;
* [http://cmm.qc.ca/ Communauté Métropolitaine de Montréal (CMM)]&lt;br /&gt;
&lt;br /&gt;
== Budget ==&lt;br /&gt;
&lt;br /&gt;
* The 2011 budget is available online [https://spreadsheets.google.com/pub?hl=en&amp;amp;hl=en&amp;amp;key=0Av9Xf1ehZXz-dG4yTzQwSTVJM0sxOVNBNFdWS2dKdHc&amp;amp;single=true&amp;amp;gid=0&amp;amp;output=html here]&lt;br /&gt;
* Any surplus at the end of the event will be turned over to [http://osgeo.org/ OSGeo] or used for a future code sprint&lt;br /&gt;
&lt;br /&gt;
== Hotel ==&lt;br /&gt;
&lt;br /&gt;
* [http://hotelcantlie.com/ Hotel Cantlie Suites], located 1-2 blocks away: Group rate starting at 99$/night + taxes&lt;br /&gt;
&lt;br /&gt;
We have a group reservation. Here's the link to reserve your room:&lt;br /&gt;
&lt;br /&gt;
* English: https://reservations.ihotelier.com/crs/g_reservation.cfm?groupID=544358&amp;amp;hotelID=12608&amp;amp;languageid=1&lt;br /&gt;
* Français: https://reservations.ihotelier.com/crs/g_reservation.cfm?groupID=544358&amp;amp;hotelID=12608&amp;amp;languageid=3&lt;br /&gt;
&lt;br /&gt;
== Costs ==&lt;br /&gt;
&lt;br /&gt;
Participants should plan for the following costs:&lt;br /&gt;
&lt;br /&gt;
* Travel to Montreal, variable depending on where you are.&lt;br /&gt;
* Accommodation for four nights, $200 to $600 depending on what room you choose and whether you room share.&lt;br /&gt;
* Breakfast, dinner and other snacks.&lt;br /&gt;
* The sponsorship moneys will be put towards: morning snacks, lunches, dinner(s), social event (?)&lt;br /&gt;
&lt;br /&gt;
== Communication ==&lt;br /&gt;
&lt;br /&gt;
* Please join the mailing list:&amp;lt;br&amp;gt;http://lists.osgeo.org/mailman/listinfo/tosprint&lt;br /&gt;
&lt;br /&gt;
* IRC chat during the event:&amp;lt;br&amp;gt;Channel: #tosprint&amp;lt;br&amp;gt;Server: irc.freenode.net&lt;br /&gt;
&lt;br /&gt;
== Participation ==&lt;br /&gt;
&lt;br /&gt;
We are planning for attendance of 20-40. Please add your name and the projects you are hoping to sprint on, if you have a strong intention to attend. &lt;br /&gt;
&lt;br /&gt;
'''Update 2011-03-01: To help with planning, please confirm your participation in each of the code sprint days and nights activities via Doodle at [http://doodle.com/n99d4fkhsid4ghap http://doodle.com/n99d4fkhsid4ghap].'''&lt;br /&gt;
 &lt;br /&gt;
# [[User:Dmorissette|Daniel Morissette]] (MapServer, GDAL/OGR)&lt;br /&gt;
# [[User:msmitherdc|Michael Smith]] (MapServer, libLAS)&lt;br /&gt;
# [[User:dzwarg|David Zwarg]] (PostGIS)&lt;br /&gt;
# [[User:jadams|Jeff Adams]] (PostGIS)&lt;br /&gt;
# Frank Warmerdam (MapServer, GDAL, ...)&lt;br /&gt;
# [[User:olivier.courtin|Olivier Courtin]] (PostGIS - TinyOWS)&lt;br /&gt;
# [[User:pwramsey3|Paul Ramsey]] (PostGIS)&lt;br /&gt;
# [[User:jmckenna|Jeff McKenna]] (MapServer)&lt;br /&gt;
# [[User:assefa|Yewondwossen Assefa]] (MapServer)&lt;br /&gt;
# [[User:aboudreault|Alan Boudreault]] (MapServer)&lt;br /&gt;
# [[User:hobu|Howard Butler]] (MapServer libLAS GDAL)&lt;br /&gt;
# [[User:tbonfort|Thomas Bonfort]] (MapServer)&lt;br /&gt;
# [[User:mpg|Michael P. Gerlek]] (libLAS, C# tribe)&lt;br /&gt;
# [[User:tomkralidis|Tom Kralidis]] (MapServer) (Wed-Fri)&lt;br /&gt;
# [[User:djay|Gérald Fenoy]] (ZOO-Project)&lt;br /&gt;
# [[User:mrosen|Michael Rosen]] (liblas, gdal)&lt;br /&gt;
# Nicolas Bozon (ZOO-Project)&lt;br /&gt;
# Steve Lime (MapServer) (Tue-Thu)&lt;br /&gt;
# [[User:pierre|Pierre Racine]] (PostGIS raster)&lt;br /&gt;
# [[User:Schpidi|Stephan Meißl]] (MapServer)&lt;br /&gt;
# [[User:zjames|Zak James]] (MapServer)&lt;br /&gt;
# [[User:kirk|Kirk McKelvey]] (mrsid, liblas, gdal)&lt;br /&gt;
# [[User:quentonc|Pete Gadomski]] (liblas)&lt;br /&gt;
# Jim Klassen (MapServer, GDAL)&lt;br /&gt;
# Alexandre Dubé (GeoPrisma)&lt;br /&gt;
&lt;br /&gt;
Virtual participants (irc #tosprint)&lt;br /&gt;
&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
== Room Share ==&lt;br /&gt;
&lt;br /&gt;
If you would like to room share, &lt;br /&gt;
&lt;br /&gt;
# Reserve a room at the hotel, choosing a type with more than one bed.&lt;br /&gt;
# Put your name in this section, indicating the amount of space in your room.&lt;br /&gt;
&lt;br /&gt;
Put your names below:&lt;br /&gt;
&lt;br /&gt;
* example entry: B has a triple room, needs two roommates.&lt;br /&gt;
&lt;br /&gt;
Special offer: I, [[User:Aleroux|Alexandre Leroux]], can provide free lodging for the whole event with these parameters: one double bed, private access (we'll let you a key), private kitchen with fridge, private shower and toilet. Internet wifi included. It's a 2-minutes walk from the Snowdon subway station, making it easy to go to the Code Sprint. That would be on the basement of where my wife, daughter and myself live. If interested, contact me directly.&lt;br /&gt;
&lt;br /&gt;
== Individual Preparation ==&lt;br /&gt;
&lt;br /&gt;
* Bring your own computer&lt;br /&gt;
* Install subversion and the compiler tools, and come with a working development environment if possible.&lt;br /&gt;
&lt;br /&gt;
== FAQ ==&lt;br /&gt;
&lt;br /&gt;
* Is the Montreal Code Sprint just a coding event?&lt;br /&gt;
** Yes, a coding and documentation event. It is a working session for people who are already participants in open source projects.&lt;br /&gt;
* Will it be possible to present new projects during this event?&lt;br /&gt;
** No, this is not a presentation-oriented event. People will get together in small groups and work on areas of mutual interest within their projects.&lt;br /&gt;
&lt;br /&gt;
== Social Events ==&lt;br /&gt;
&lt;br /&gt;
* Monday March 14, 2011 @5pm: OSGeo-Québec 5 à 7 / Code Sprint Ice breaker. On the 2nd floor of http://www.mcleanspub.com/ 1210 Peel St, Montreal (450m South of the Cantlies Suites hotel on Peel Street)&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
== Eating Options ==&lt;br /&gt;
&lt;br /&gt;
Some locations recommended by locals:&lt;br /&gt;
&lt;br /&gt;
* Restaurants&lt;br /&gt;
** ...&lt;br /&gt;
* Bars&lt;br /&gt;
** &lt;br /&gt;
&lt;br /&gt;
(Please do not hesitate to add locations to this list)&lt;br /&gt;
&lt;br /&gt;
== Getting to the Sprint ==&lt;br /&gt;
&lt;br /&gt;
=== From Trudeau International Airport (YUL) ===&lt;br /&gt;
&lt;br /&gt;
Unfortunately there is no shuttle that goes straight from the airport to the hotel. &lt;br /&gt;
&lt;br /&gt;
Here are some options (See also [http://maps.google.com/maps?f=d&amp;amp;source=s_d&amp;amp;saddr=45.454231,-73.748131&amp;amp;daddr=1110+Rue+Sherbrooke+Ouest,+Montr%C3%A9al,+QC+H3A+1G6,+Canada&amp;amp;hl=en&amp;amp;geocode=%3BFRxMtgIdbU-d-ynR5QLZQBrJTDE5mLJmp5RZkQ&amp;amp;mra=dme&amp;amp;mrsp=0&amp;amp;sz=13&amp;amp;dirflg=r&amp;amp;ttype=dep&amp;amp;date=02%2F25%2F11&amp;amp;time=7:22am&amp;amp;noexp=0&amp;amp;noal=0&amp;amp;sort=def&amp;amp;sll=45.469521,-73.682384&amp;amp;sspn=0.099197,0.222301&amp;amp;ie=UTF8&amp;amp;ll=45.500813,-73.574409&amp;amp;spn=0.099141,0.222301&amp;amp;z=13&amp;amp;iwloc=statictransit:&amp;amp;start=0 Google Maps]):&lt;br /&gt;
&lt;br /&gt;
==== Option 1 - Express Bus 747 + Subway ====&lt;br /&gt;
&lt;br /&gt;
http://www.admtl.com/Passengers/AccessAndParking/STMBuses.aspx&lt;br /&gt;
&lt;br /&gt;
Take the 747 express bus from the Airport. The bus goes to Berri-UQAM, but do not go all the way to Berri-UQAM, you need to get off at the Lionel-Groulx stop, and then connect to the Metro Green Line (1) towards Station Honoré-Beaugrand. Get off at Station Peel (Stop ID: 10138). You are only 150m from Hotel Le Cantlie Suites.&lt;br /&gt;
&lt;br /&gt;
Cost: 8$. At the airport, tickets are sold at the International Currency Exchange (ICE) counter on the international arrivals level.&lt;br /&gt;
&lt;br /&gt;
==== Option 2 - Taxi ====&lt;br /&gt;
&lt;br /&gt;
http://www.admtl.com/Passengers/AccessAndParking/TaxisAndLimousines.aspx&lt;br /&gt;
&lt;br /&gt;
It seems that the simplest option is a taxi: there is a fixed price of 38$ for a ride downtown in the area of the hotel. (The person at the hotel insisted that this is a fixed price and if the driver asks for more then he is trying to screw you)&lt;br /&gt;
&lt;br /&gt;
==== Option 3 - Train + Subway ====&lt;br /&gt;
&lt;br /&gt;
VIA Rail offers a train shuttle from their Dorval train station to downtown (towards Montreal Central Station). The Dorval train station is not directly on the airport so you need to take the &amp;quot;AirConnect&amp;quot; shuttle to get to the train. More details here:&lt;br /&gt;
&lt;br /&gt;
http://www.viarail.ca/en/useful-info/related-services/montreal-airport-shuttle&lt;br /&gt;
&lt;br /&gt;
&amp;quot;After landing, go to the domestic or international flights terminal exit, where you'll see a clearly marked AirConnect stop. The shuttle comes by every 20 minutes, and will take you to the Dorval station for free.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Then Google suggests that the shortest route is to get off the train at Metro (Subway) Station Vendome, then take red line (2) towards Henri Bourassa and get off at Lionel Groulx. Finally take metro green line (1) towards Honoré-Beaugrand and get off at Peel. You are only 150m from Hotel Le Cantlie Suites.&lt;br /&gt;
&lt;br /&gt;
== Announcements, News, Recaps ==&lt;br /&gt;
&lt;br /&gt;
* &lt;br /&gt;
=== Photos ===&lt;br /&gt;
&lt;br /&gt;
* http://www.flickr.com/search/?q=montrealsprint2011&amp;amp;m=tags&lt;br /&gt;
&lt;br /&gt;
[[Category:Code Sprints]]&lt;br /&gt;
[[Category:Events]]&lt;/div&gt;</summary>
		<author><name>Wiki-Adube</name></author>
	</entry>
</feed>