OSGeo - User contributions [en]

Google Summer of Code 2013 Ideas

2013-04-05T00:59:18Z

Wiki-Whatnick: /* OSGeo Foundation member projects */

[[Image:Gsoc-2013-logo-color.jpg|350px|link=http://code.google.com/soc/]] <font size="+3"> @ </font> [[Image:OSGeo_300_127_pixel.png|link=http://www.osgeo.org]]

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

* See also ideas from [[Google Summer of Code 2010 Ideas|2010]], [[Google Summer of Code 2011 Ideas|2011]], and [[Google Summer of Code 2012 Ideas|2012]].
-----

== OSGeo Google Summer of Code 2013 ==

The [http://www.osgeo.org Open Source Geospatial Foundation] would like to extend a welcome to all SoC students. On this page you will find links to a host of ideas organized by project. You will find ideas ranging from the depths of computer science graph theory to the heights of visualization. One thing all these ideas have in common is lots and lots of spatial data.

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

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

* There is a [http://code.google.com/p/google-summer-of-code/wiki/GsocFlyers Google SoC flyer] to look at and post in appropriate places and [http://svn.osgeo.org/osgeo/marketing/flyer/google_summer_of_code/ an OSGeo flavoured one as well] (TODO: update to 2013).

* 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.

== Important dates ==

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

* April 8: Google announces accepted organizations.
: If OSGeo is accepted as an organization for Google Summer of Code, '''start talking to us earlier rather than later.'''
* April 22: '''Student applications open.
: The earlier you start the more probable it is that you will be accepted!'''
: ''There is two way feedback during the application process which really helps you improve and clarify your application before the final deadline. The better your involvement with your potential mentors during this period, the better your chances of being selected.''
* May 3: '''Student application deadline.'''
* May 27: Accepted student proposals are announced and Community Bonding Period begins
* June 17: '''Coding begins!'''
: (''you may unofficially start a week or two earlier if you know you'll have to take a week or two off during The Summer or you'll be sitting finals in the first week(s) of the program. This must be reflected in your application timeline'')
* July 29: Mid-term evaluation begins
* September 16-23: '''Pencils down!'''
* September 23-27: Final evaluations
* September 27: Students begin submitting required code samples to Google
* October 1: Final results announced

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

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

=== OSGeo Foundation member projects ===

[[Image:logo-grass.png|60px|right]]
* [http://grasswiki.osgeo.org/wiki/GRASS_SoC_Ideas_2013 '''GRASS GIS''' SoC Ideas]: GRASS GIS is an open source GIS focusing mainly on analysis. It is written as a collection of stand-alone C programs and has a new GUI written in wxPython. If you know Python, or want to implement algorithms in C take a look!

[[Image:logo-qgis.png|60px|right]]
* [http://hub.qgis.org/wiki/quantum-gis/Google_Summer_of_Code_2013 '''Quantum GIS''' SoC Ideas] Quantum GIS (QGIS) is a user friendly Open Source Geographic Information System (GIS) that runs on Linux, Unix, Mac OSX, and Windows. QGIS supports vector, raster, and database formats. It is written in C++ and Python.

[[Image:logo-ossim.png|60px|right]]
* [http://trac.osgeo.org/ossim/wiki/GSoC_2013_Ideas '''OSSIM''' SoC Ideas]: - OSSIM is a powerful suite of geospatial libraries and applications used to process imagery, maps, terrain, and vector data. 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++.

* [http://trac.osgeo.org/osgeo4w/wiki|'''OSGeo4W''']: - OSGeo4W is a binary distribution of a broad set of open source geospatial software for Win32 environments (Windows XP, Vista, etc). 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.

[[Image:logo-uDig.png|60px|right]]
* [http://udig.refractions.net/confluence/display/HACK/Summer+of+Code '''uDig''' SoC Ideas]: User-friendly Desktop GIS is a Java application written with the Eclipse RCP framework. The project has a community svn area to host student plug-ins, tutorials cover how to package up a custom application to show off your work.

[[Image:logo-gvSIG.png|60px|right]]
* [[GvSIG_GSoC_2013_Ideas|'''gvSIG''' Ideas]]: gvSIG is a free GIS project for [http://www.gvsig.org/web/projects/gvsig-desktop/description2/view?set_language=en Desktop], [http://www.gvsig.org/web/projects/gvsig-mobile/description-2/view?set_language=en PDAs], and [http://gvsigmini.org mobile phones]. The gvSIG project looks for students with Java skills that want to develop new ideas on any of these products.

[[Image:logo-opticks.png|right]]
* [http://opticks.org/confluence/display/opticksDev/Google+Summer+of+Code '''Opticks''' Ideas]: Opticks is an extensible [http://en.wikipedia.org/wiki/Remote_sensing remote sensing] and imagery analysis desktop application. It provides a framework to process remote sensing data such as [http://en.wikipedia.org/wiki/Hyperspectral_imaging Hyperspectral] (HSI), [http://en.wikipedia.org/wiki/Multi-spectral_image Multispectral] (MSI), and [http://en.wikipedia.org/wiki/Synthetic_aperture_radar Synthetic aperture radar] (SAR) imagery and video. The application is written in C++ and licensed under LGPL v2.1. Extensions are written using C++ or Python. You can review the [http://opticks.org/confluence/display/opticksExt/All+Opticks+Extensions available extensions] and [http://opticks.org/confluence/display/opticks/Feature+Tour+-+Your+Data feature tour] to get a better idea of what Opticks can do.

[[Image:logo-geos.png|60px|right]]
* [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.

[[Image:logo-geoserver-crop.png|right]]
[[Image:logo-gdal.png|60px|right]]
* [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 desk top GIS programs. This means that you can store your spatial data in almost any format you prefer but that your users do not need to know anything about GIS data. At the simplest level all they need is a web browser to see your maps exactly as you want. GeoServer is the reference implementation of the Open Geospatial Consortium (OGC) Web Feature Service (WFS) and Web Coverage Service (WCS) standards, as well as a high performance certified compliant Web Map Service (WMS).
:* ''Geoserver will accept one idea, according to the developers' availability. Please contact them to get more information.''


[[Image:logo-postgis.png|60px|right]]
* [http://trac.osgeo.org/gdal/wiki/SummerOfCode '''GDAL''' Ideas]: GDAL is a C++ library for reading and writing geospatial data raster and vector formats.


* [http://trac.osgeo.org/postgis/wiki/GoogleSummerCode '''PostGIS''' Ideas]: [http://www.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.

We expect ideas also from [http://live.osgeo.org/en/overview/mapbender_overview.html MapBender], [http://live.osgeo.org/en/overview/zoo-project_overview.html ZOO-Project], [http://live.osgeo.org/en/overview/geomoose_overview.html GeoMOOSE]...

=== Guest projects ===

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

Guest students (accepted under OSGeo umbrella):

[[Image:Logo-mapnik.png|100px|right]]
* [https://github.com/mapnik/mapnik/wiki/GSOC-Ideas '''Mapnik''' Ideas]: [http://mapnik.org/ Mapnik] is a Free Toolkit for developing mapping applications. It’s written in C++ and there are Python bindings to facilitate fast-paced agile development. It can comfortably be used for both desktop and web development, which was something I wanted from the beginning.
:* ''Mapnik students will be required to apply under OSGeo <strike>or [http://wiki.openstreetmap.org/wiki/Google_Summer_of_Code/2013 OpenStreetMap] umbrella, according to the main topic of their project.</strike>'' (oops, looks like it's just us this time)

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

== Which project do I choose? ==

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

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

Since OSGeo is an umbrella organisation for multiple projects, each project has their own discussion and development mailing lists.

'''Main OSGeo mailing lists of interest to students:'''
: Please start here, when contacting us for the first time with questions about Google Summer of Code.

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

Also see the [[Mailing Lists]] page for project specific lists, as well as the longer list at http://lists.osgeo.org.

== How to get in contact via IRC ==

Primary channel:

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

GSoC @ OSGeo inter-project discussions:

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

Project irc channels:

* irc://irc.freenode.net/#gdal
* irc://irc.freenode.net/#geoserver
* irc://irc.freenode.net/#geotools
* irc://irc.freenode.net/#grass
* irc://irc.freenode.net/#gvsig
* irc://irc.freenode.net/#mapbuilder
* irc://irc.freenode.net/#mapguide
* irc://irc.freenode.net/#mapnik
* irc://irc.freenode.net/#mapserver
* irc://irc.freenode.net/#openlayers
* irc://irc.freenode.net/#opticks
* irc://irc.freenode.net/#ossimplanet
* irc://irc.freenode.net/#pgrouting-project
* irc://irc.freenode.net/#postgis
* irc://irc.freenode.net/#qgis
* irc://irc.freenode.net/#udig
* irc://irc.oftc.net/#osm-dev

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

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

Name:

Country:

School and degree:

Email:

Phone:

OSGeo project(s):

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

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

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

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

Please provide details of previous GIS experience:

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

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

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

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

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

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

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

Do you have any known time conflicts during the official coding
period? (June 17 to Sept. 27)

== What to expect during the summer ==

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

=== Be prepared to be in constant communication with your mentors and project ===

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

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

=== Weekly reports ===

Yes, every week we expect to see a report posted to the soc@osgeo mailing list that at least answers the following questions:

# What did you get done this week?
# What do you plan on doing next week?
# Are you blocked on anything?

These questions BTW are the same as are used in real-work, when developing with the
[http://en.wikipedia.org/wiki/Scrum_(development) Scrum] [http://en.wikipedia.org/wiki/Agile_software_development development process]. ;)

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

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

=== Wiki page and blogs ===

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

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

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

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

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

FOSS4G 2009 Code Sprint

2009-10-23T21:55:29Z

Wiki-Whatnick: /* Venue */

== Organizing Contacts ==

* Jody Garnett, Tyler Mitchell

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

A code sprint is usually organized by a group that is using an open source project and wants to see something done. They fly the developers to a single location and feed them for a couple of days with the necessities of the hacking life (internet, caffeine, electricity). The communication that happens from face to face hacking usually lasts the project for a year or more. You see this a lot in projects like Drupal etc...

== Venue ==
For map and more details see [[Image:FOSS4G_2009_Code_Sprint_Information.pdf|Info.pdf]]
* '''Date: Saturday 24 October''' (the day after the conference).
* '''Time:''' 9am-5pm (http://www.timeanddate.com/worldclock/meetingdetails.html?year=2009&month=10&day=23&hour=22&min=0&sec=0&p1=240&p2=250&p3=137&p4=136)
* '''Where:''' University of Technology Sydney – Ultimo Campus, Level 3, Building 6
Peter Johnson Building '''(Building 6)'''
Faculty of Design, Architecture & Building
702-730 Harris Street,
Ultimo, NSW 2007.
* '''Rooms:''' 319, 320, 321
* '''[http://datasearch.uts.edu.au/dab/location-maps/index.html online maps]''' and '''[http://datasearch.uts.edu.au/dab/location-maps/location-dab-building.pdf building map] PDF (300kb)'''

More than 80 attendees are expected!

== Motivation and Direction ==

A day, a code base, and your imagination?

Projects can use the time and venue for organizational discussions, development roadmaps, and group resolution of thorny issues in their code bases.

Is this your First Sprint? Here is some background information to get you started:

* http://www.infrae.com/about/activities/sprintathon/tips
* http://www.onlamp.com/pub/a/python/2006/10/19/running-a-sprint.html
* Example Sprint (from same people who do GeoServer): http://www.openplans.org/projects/bbq-sprint

== Summary of Workgroups ==
List of Workgroups here, more info follows...
* PostGIS
* uDig & friends
* The desktop comparison tasks list
* OSGeo in general, especially Marketing & Education
* Geometry (note project info below, being held at different venue, on Sunday 25 October, '''the day after''' the other sprints)
* Live DVD
* OpenLayers
* MapServer
* Mapbender
* 52°North Web Processing Service + GRID

= Workgroups =
To participate, start a section below for your project.

== PostGIS ==
'''Coordinator:'''
* Paul Ramsey

'''Attending:'''
* Person 1
* Person 2

'''Goals:'''
* Bug fixes and clean-up for a 1.5 release.

== uDig & friends ==
'''Coordinator:'''
* [[User:Moovida | Andrea Antonello]]

'''Attending:'''
* [[User:Moovida | Andrea Antonello]]
* [[User:Silli | Silvia Franceschi]]
* [[User:Jive | Jody Garnett]]
* add yourself here...

'''Goals:'''

* database datastores
* style editors
* define install/update mechanisms for plugin projects (JGrass, BeeGIS, Axios)
* mosaic support for udig
* rastersymbolizer style editor

== The desktop comparison tasks list ==

'''Attending, for which project'''
* uDig [[User:Silli | Silvia Franceschi]]
* QGis ?
* gvSig ?
* GRASS [[User:clara | Clara Tattoni]], Marco Ciolli, Paolo Zatelli
* JGISShell Andreas W. Bartels

(for inspiration of tasks, see [http://grass.osgeo.org/wiki/Applications Applications])

'''Feel free to add ideas here:'''

* vector data visualization
** load a shapefile for quick visualization (with prj, without prj, with topology, without topology)
** load a particularly large shapefile
** load a dwg
** load a dxf (2D and 3D)
** ...

* vector data editing
** create new geometry layers
** add an attribute of the geometry as new column to the dataset
** show existing editing tools (snap, intersections, merge, union, subtract)
** vector analysis
** topologic analysis
** network analysis
** linear reference system
** symbology (images for points, hatch, themes, legend)
** labeling options
** ...

* raster data visualization
** load a tiff (GRASS: import vs register with r.external)
** load a jpg
** load an ecw
** load a Mrsid
** load a GRASS raster
** load a mosaic of images
** ...

* raster data editing
** map calculations on raster data
** cost surfaces
** hydro flow
** geomorphometry
** solar energy calculations
** ...

* databases
** SQL queries
** visualization of spatial data from PostGIS
** visualization of spatial data from SQLite
** visualization of spatial data from Oracle spatial
** visualization of spatial data from ArcSDE
** visualization of spatial data from MySQL
** visualization of spatial data from H2spatial
** create new datasets in the above databases
** convert between table with x,y[,z] and vector map
** ...

* web service visualization and query
** load a WMS dataset, query its information
** load a WFS dataset, query its information
** load and edit a WFS-T dataset
** load a WCS dataset
** WPS
** ...

* scripting engines
** batch mode executions of commands
** supported languages
** ...

* printing
** support for printing
** support for storing printing layouts
** ...

* other
** geocoding
** georeferencing
** creation of personalized buttons
** ...

=== See also ===
* Stefan Steiniger, Geoffrey J. Hay. Ecological Informatics 4 (2009) 183–195, Free and open source geographic information tools for landscape ecology. ([http://dx.doi.org/10.1016/j.ecoinf.2009.07.004 DOI] and [http://www.geo.unizh.ch/publications/sstein/sstein_freegitools_ecoinf2009.pdf preprint PDF])

== OSGeo in general, especially Marketing & Education ==
'''Coordinator:'''
* Tyler Mitchell

'''Attending:'''
* Arnulf Christl
* Daniel Kastl
* Cameron Shorter (discussing cross over with LiveDVD)
* ...

'''Goals:'''
For all those who are around during this day but not going to do coding and want to talk more generally about OSGeo directions, etc. Likely follow-up from [[FOSS4G_2009_BirdsOfAFeather | BoF events]]
* Review marketing and outreach ideas and needs.
* Work on the OSGeo presentation, create derivateives for different presentation lenghts and audiences
* Compile, update and comit templates for presentations
* [[Talk:The Future of OSGeo]], collect and organize opinions from the [http://lists.osgeo.org/pipermail/discuss/2009-October/thread.html OSGeo Discuss] mailing list.
* Discuss requirements for the LiveDVD from Marketing and Education

== Geometry ==

'''DATE: SUNDAY 25 OCTOBER'''

'''Time: 10am - 4pm'''

'''Venue: Intersect, Level 12, 309 Kent St'''

This sprint will be held on Sunday 25 October at a different venue (Intersect). We ask everyone attending to add their name to the list below as we are limited to 12 people. First come, first served.

'''Coordinator:'''
* Ben Caradoc-Davies

'''Attending:'''
# Ben Caradoc-Davies
# Jody Garnett
# Andrea Aime
# Andrea Antonello
# Silvia Franceschi

'''Goals:'''
* Progress ISO 19107 / GML 3D geometry collaboration (OSGeom). See <tt><java-collab@lists.osgeo.org></tt> for more.

'''Plan:'''
Some subset of Markus Schneider's proposal:
# DONE - Remove all topological and spatial analysis methods in the interfaces from the SVN for now, so we can focus on sanitising the model.
# Add factories. I would like to add two factories similar to the ones in the deegree 3 SVN:
#* SFS geometries:
#** http://download.deegree.org/deegree3/nightly/core/javadoc/org/deegree/geometry/SimpleGeometryFactory.html
#* ISO 19107/GML 3
#** http://download.deegree.org/deegree3/nightly/core/javadoc/org/deegree/geometry/GeometryFactory.html
#* In deegree 3, these factories are bound to a JTS-based implementation. As we only have interfaces for the geometry types in the osgeom repository for now (and no implementations), I would create interfaces from the factories.
# Add a basic implementation that is just a bean representation without operations. We could finally start to add JUnit tests then.
# Add GML parsers/exporters. I understood that one may want to keep this aspect out of the repository, but I don't see how we could test the difficulties in representing GML geometries (e.g external xlinks) without this. It also would make setting up geometries for testing much easier. Maybe we could keep the GML parsing/exporting isolated from the rest of the code.
# Of course we would take on the operations subject again, when we find consensus here.

== Live DVD ==
'''Coordinator:''' Cameron Shorter

'''Attending:'''
* Ricardo Pinho
* .

Virtual attendees can join us at: irc://freenode.net#foss4g

'''Goals:'''
* Brainstorm ideas for improvements to the LiveDVD
* Set guidelines in place for build
** Documentation guidelines
** Desktop layout
* Target other distribution media

For specific ideas, add them to our issue tracker here: http://trac.osgeo.org/osgeo/query?group=status&component=LiveDVD&order=priority

== OpenLayers ==
'''Coordinator:'''
* [[User:Ahocevar | Andreas Hocevar]]

'''Attending:'''
* [[User:Rdewit | Roald de Wit]]
* Bart van den Eijnden
* [[User:madair | Mike Adair]]
* Person 4

'''Goals:'''

OpenLayers bug fixes. Describe any additional goals here.

'''To prepare for the sprint, please create/update tickets (http://trac.openlayers.org) for stuff you want to work on, and add "foss4g09" in the Keywords form field of the ticket.'''

== MapServer ==
'''Coordinator:'''
* [[User:Dmorissette | Daniel Morissette]]

'''Attending:'''
* [[User: msmitherdc | Michael Smith ]]
* [[User:jmckenna | Jeff McKenna]]
* Jeff Hamm
* [[User:Schpidi | Stephan Meissl]]
* ...

'''Participating through IRC (#mapserver):'''
* Steve Lime
* [[User: pnaciona | Perry Nacionales]]
* ...

'''Goals:'''

* Work on the 5.6.0 release, including:
** Testing the current beta/release candidate
** Bug fixes
** Release of 5.6.0-RC1 (depending on how beta4 went)
** Work on documentation

* Discuss new features, future work

== Mapbender ==
The target group for this (non-coding) sprint are software architects, geoportal operator, service broker, service provider, data provider.

'''Coordinator:'''
* Arnulf Christl

'''Attending:'''
* Person 1
* Person 2

'''Goals:'''
This group will not code software but rather have informal discussions about the road map and new requirements of the software Mapbender. Some work needs to be done to define and more importantly better communicate the unique selling point of Mapbender. It is currently the only Open Source software that ships with of the box features to deploy, maintain and operate large scale geo portals using nothing but browser interfaces.

== Georuby ==
'''Coordinator:'''
* Shoaib Burq

'''Attending:'''
* Person 1
* Person 2

'''Goals:'''
* http://github.com/nofxx/postgis_adapter/issues
* http://github.com/fragility/spatial_adapter/issues
* or just hack a cute app for the fun of it :-)
* take the code for 2009.foss4g.org and refactor the ruby helpers so that 2010 committee can use it

== QGIS / Mapserver ==
'''Coordinator:'''
* Richard Duivenvoorde / Jeff McKenna

'''Attending:'''
* Michael Smith
* Person 2

'''Goals:'''
* refine /make even better the mapserverexport plugin
* ideas:
** adding a 'url'-input in gui to be able to set the mapserver for the map file
** setting bbox per layer
** STATUS default true, DUMP default true??
** postgis layer stuff
** use label alignment from qgis
** font-file use? use font-size ?
** add some extra symbols OR use of symbol-size
** ?? use of current project instead of saved mapfile (??)
** XSLT from QGIS <-> Mapserver XML <-> MapServer Mapfile

== 52°North WPS + GRID ==
'''Coordinator:'''
* Bastian Schäffer

'''Attending:'''
* Niels Hoffmann
* Robert Gibb
* ...

'''Goals:'''
* Discussion of Future Developments
* Architecture draft
* ...

== Project ==
'''Coordinator:'''
* .

'''Attending:'''
* Person 1
* Person 2

'''Goals:'''

Describe goals ...

[[Category:FOSS4G2009]]
[[Category:FOSS4G]]