OSGeo - User contributions [en]

Google Summer of Code 2014 Ideas

2014-02-13T13:46:35Z

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

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

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

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

== OSGeo Google Summer of Code 2014 ==

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

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

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

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

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

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

== Important dates ==

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


* February 24: Google announces accepted organizations.
: If OSGeo is accepted as an organization for Google Summer of Code, '''start talking to us earlier rather than later.'''

* March 10: Student applications open.
: The earlier you start the more probable it is that you will be accepted!
: ''There is two way feedback during the application process which really helps you improve and clarify your application before the final deadline. The better your involvement with your potential mentors during this period, the better your chances of being selected.''
* March 21: Student application deadline.
* April 21: '''Accepted student proposals are announced and Community Bonding Period begins.'''
* May 19: '''Coding begins!'''
: (''you may unofficially start a week or two earlier if you know you'll have to take a week or two off during The Summer or you'll be sitting finals in the first week(s) of the program. This must be reflected in your application timeline'')
* June 23: Mid-term evaluation begins
* August 11-18: '''Pencils down!'''
* August 18-22: Final evaluations
* August 22: Students begin submitting required code samples to Google
* August 25: Final results announced

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

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

=== OSGeo Foundation member projects ===

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

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

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

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

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

* [http://wiki.osgeo.org/wiki/Live_GIS_GSoC_2014 OSGeo-Live Ideas]: [http://live.osgeo.org OSGeo-Live] packages over 50 of the best geospatial open source projects, preconfigured with data, quickstarts and project overviews.

 
[[Image:logo-gvSIG.png|60px|right]]
* [[GvSIG_GSoC_2014_Ideas|'''gvSIG''' Ideas]]: gvSIG is a free GIS project for [http://www.gvsig.org/web/projects/gvsig-desktop/description2/view?set_language=en Desktop], [http://www.gvsig.org/web/projects/gvsig-mobile/description-2/view?set_language=en PDAs], and [http://gvsigmini.org mobile phones]. The gvSIG project looks for students with Java skills that want to develop new ideas on any of these products.
[[Image:logo-opticks.png|right]]
* [http://opticks.org/confluence/display/opticksDev/Google+Summer+of+Code '''Opticks''' Ideas]: 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.
 



  

=== Guest projects ===

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

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

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

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

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

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

[[Image:logo-uDig.png|60px|right]]
* [https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-Ideas-2014 '''JGrasstools''' and '''uDig''' SoC Ideas]: User-friendly Desktop GIS ([http://udig.github.io/ uDig]) is a Java application written with the Eclipse RCP framework. The project has a community svn area to host student plug-ins, tutorials cover how to package up a custom application to show off your work.

* '''FIXME''': move to a member project's idea page:
: ''[http://sites.google.com/site/foss4gku/projects/gsoc-feature-based-map-algebra '''Feature-based Map Algebra''' SoC Ideas] Map algebra (or cartographic modeling) operations provide powerful tools for analyzing and manipulating geographic data in the raster data model both in commercial and open source GIS software. This project extends these operations to the vector data model and makes them available in PostGIS and QGIS. It will be implemented primarily using the Python programming language.''



== Which project do I choose? ==

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

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

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

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

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

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

== How to get in contact via IRC ==

Primary channel:

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

GSoC @ OSGeo inter-project discussions:

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

Project irc channels:

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

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

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

Name:

Country:

School and degree:

Email:

Phone:

OSGeo project(s):

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

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

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

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

Please provide details of previous GIS experience:

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

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

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

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

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

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

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

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

== What to expect during the summer ==

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

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

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

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

=== Weekly reports ===

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

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

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

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

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

=== Wiki page and blogs ===

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

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

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

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

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

Opticks Incubation Checklist

2013-07-10T13:20:03Z

Wiki-Dadkins:

= Opticks Incubation Checklist =
Completed sections have been filled out, and sections with work remaining to be done have been marked with TODO.

== Open ==

The project has demonstrated that it has an open, active and healthy user and developer community:
# Open: projects are expected to function in an open and public manner and include:
#* LGPL v2.1 License
#* Open communication via IRC and mailing lists
#* Open decision-making via [http://opticks.org/confluence/display/opticks/Opticks+Governance+Policy this] policy
# Active and healthy community:
#* TODO: The project should have a community of developers and users who actively collaborate and support each other in a healthy way. Eg. collaboration on project activities such as testing, release and feature development.
#* TODO: Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organisations. Eg. The project is resilient enough to sustain loss of a developer or supporting organisation, often referred to as having a high [http://en.wikipedia.org/wiki/Bus_factor bus factor]. Decisions are made openly instead of behind closed doors, which empowers all developers to take ownership of the project and facilitates spreading of knowledge between current and future team members.

== Copyright and License ==

We need to ensure that the project owns or otherwise has obtained the ability to release the project code by completing the following steps:
# LGPL v2.1 license.
# TODO: Project documentation is available under an open license, such as Creative Commons.
# TODO: The project code, documentation and data has been adequately vetted to assure it is all properly licensed, and a copyright notice included, as per a [http://www.osgeo.org/incubator/process/codereview.html Provenance Review].
# TODO: The project maintains a list of all copyright holders identified in the Provenance Review Document.
# TODO: All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived.

== Processes ==

# Configuration management: svn
# Issue tracker: [https://issues.opticks.org]
#* Open decision-making via [http://opticks.org/confluence/display/opticks/Opticks+Governance+Policy this] policy
#* Open communication via IRC and mailing lists

== Documentation ==

# The project has user documentation:
#* Included with the binary download and online.
#* [http://opticks.org/confluence/display/opticks/Feature+Tour+-+Your+Data Opticks Feature Tour]
# The project has developer documentation:
#* Including checkout and build instructions in svn repository.
#* Full documentation of the Opticks C++ SDK, published by doxygen.
#* Contributing patches to Opticks is explained [http://opticks.org/confluence/display/opticksDev/Welcome+To+Opticks+Development here]

==Release Procedure==

In order to maintain a consistent level of quality, the project should follow defined release and testing processes.

# TODO: The project follows a defined release process:
#* TODO: Which includes execution of the testing process before releasing a stable release.
# TODO: The project follows a documented testing process. Ideally, this includes both automated and manual testing Ideally this includes documented conformance to set quality goals, such as reporting Percentage Code Coverage of Unit Tests.
# TODO: Release and testing processes provide sufficient detail for an experienced programmer to follow.

= OSGeo Committees and Community =

The OSGeo Foundation is made up of a number of committees, projects and local chapters. This section gathers up information these groups have requested from OSGeo projects. These expectations are not mandatory requirements before graduation, but a project should be prepared to address them in order to be considered a good OSGeo citizen.

== Board ==

The OSGeo [[Board]] holds ultimate responsibility for all OSGeo activities. The Board requests:

# TODO: A project provide a Project Officer as a contract point:
#* TODO: The Project Officer should be listed at: [[Contacts#Software_Projects|Project Officer]]
#* TODO: This person is established when the incubation committee recommends the project for graduation
#* TODO: Your community can change the project officer as needed (just add an agenda item to the next board meeting so they can recognise the change of officer).

== Marketing ==

Access to OSGeo's [[Marketing_Committee]] and associated [[Marketing_Pipeline]] is one of the key benefits of joining the OSGeo foundation. The Marketing Committee requests:

# Marketing artefacts have been created about the project in line with the incubation criteria listed in the OSGeo Marketing Committee's [http://wiki.osgeo.org/wiki/Marketing_Artefacts Marketing Artefacts]. This lists the documentation requirements for [http://live.osgeo.org OSGeo-Live]. Marketing Artefacts include:
#* TODO: Application Overview
#* TODO: Application Quickstart
#* The Opticks icon is included with the application and online.
# TODO: Ideally, stable version(s) of executable applications are bundled with appropriate distributions. In most cases, this will at least include [http://live.osgeo.org OSGeo-Live], but may also include [http://wiki.debian.org/DebianGis DebianGIS], [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS], and/or [http://trac.osgeo.org/osgeo4w/ osgeo4w] [http://www.maptools.org/ms4w/ ms4w], etc.)

== Projects ==

TODO: Projects do not exist in isolation; and are expected to communicate and collaborate on key issues.

As an example the PostGIS release procedure asks that the release be checked with MapServer, GeoServer and others.

== SAC ==

The [[SAC|System Administration Committee]] is available to help infrastructure and facilities. Information for this committee is collected as part of the [[Project Status Template]]. The following should be set up:
* TODO: A http://projectname.osgeo.org domain name.

A project may optionally request SAC help to make use of:
* OSGeo issue tracker - not requested
* OSGeo mailing list - not requested
* OSGeo svn - not requested
* http://downloads.osgeo.org - not requested

Opticks Incubation Checklist

2013-07-10T13:18:59Z

Wiki-Dadkins:

= Opticks Incubation Checklist =
Completed sections have been filled out, and sections with work remaining to be done have been marked with TODO.

== Open ==

The project has demonstrated that it has an open, active and healthy user and developer community:
# Open: projects are expected to function in an open and public manner and include:
#* LGPL v2.1 License
#* Open communication via IRC and mailing lists
#* Open decision-making via [http://opticks.org/confluence/display/opticks/Opticks+Governance+Policy this] policy
# Active and healthy community:
#* TODO: The project should have a community of developers and users who actively collaborate and support each other in a healthy way. Eg. collaboration on project activities such as testing, release and feature development.
#* TODO: Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organisations. Eg. The project is resilient enough to sustain loss of a developer or supporting organisation, often referred to as having a high [http://en.wikipedia.org/wiki/Bus_factor bus factor]. Decisions are made openly instead of behind closed doors, which empowers all developers to take ownership of the project and facilitates spreading of knowledge between current and future team members.

== Copyright and License ==

We need to ensure that the project owns or otherwise has obtained the ability to release the project code by completing the following steps:
# LGPL v2.1 license.
# TODO: Project documentation is available under an open license, such as Creative Commons.
# TODO: The project code, documentation and data has been adequately vetted to assure it is all properly licensed, and a copyright notice included, as per a [http://www.osgeo.org/incubator/process/codereview.html Provenance Review].
# TODO: The project maintains a list of all copyright holders identified in the Provenance Review Document.
# TODO: All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived.

== Processes ==

# Configuration management: svn
# Issue tracker: [https://issues.opticks.org]
#* Open decision-making via [http://opticks.org/confluence/display/opticks/Opticks+Governance+Policy this] policy
#* Open communication via IRC and mailing lists

== Documentation ==

# The project has user documentation:
#* Included with the binary download and online.
# The project has developer documentation:
#* Including checkout and build instructions in svn repository.
#* Full documentation of the Opticks C++ SDK, published by doxygen.
#* Contributing patches to Opticks is explained [http://opticks.org/confluence/display/opticksDev/Welcome+To+Opticks+Development here]

==Release Procedure==

In order to maintain a consistent level of quality, the project should follow defined release and testing processes.

# TODO: The project follows a defined release process:
#* TODO: Which includes execution of the testing process before releasing a stable release.
# TODO: The project follows a documented testing process. Ideally, this includes both automated and manual testing Ideally this includes documented conformance to set quality goals, such as reporting Percentage Code Coverage of Unit Tests.
# TODO: Release and testing processes provide sufficient detail for an experienced programmer to follow.

= OSGeo Committees and Community =

The OSGeo Foundation is made up of a number of committees, projects and local chapters. This section gathers up information these groups have requested from OSGeo projects. These expectations are not mandatory requirements before graduation, but a project should be prepared to address them in order to be considered a good OSGeo citizen.

== Board ==

The OSGeo [[Board]] holds ultimate responsibility for all OSGeo activities. The Board requests:

# TODO: A project provide a Project Officer as a contract point:
#* TODO: The Project Officer should be listed at: [[Contacts#Software_Projects|Project Officer]]
#* TODO: This person is established when the incubation committee recommends the project for graduation
#* TODO: Your community can change the project officer as needed (just add an agenda item to the next board meeting so they can recognise the change of officer).

== Marketing ==

Access to OSGeo's [[Marketing_Committee]] and associated [[Marketing_Pipeline]] is one of the key benefits of joining the OSGeo foundation. The Marketing Committee requests:

# Marketing artefacts have been created about the project in line with the incubation criteria listed in the OSGeo Marketing Committee's [http://wiki.osgeo.org/wiki/Marketing_Artefacts Marketing Artefacts]. This lists the documentation requirements for [http://live.osgeo.org OSGeo-Live]. Marketing Artefacts include:
#* TODO: Application Overview
#* [http://opticks.org/confluence/display/opticks/Feature+Tour+-+Your+Data Opticks Feature Tour]
#* The Opticks icon is included with the application and online.
# TODO: Ideally, stable version(s) of executable applications are bundled with appropriate distributions. In most cases, this will at least include [http://live.osgeo.org OSGeo-Live], but may also include [http://wiki.debian.org/DebianGis DebianGIS], [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS], and/or [http://trac.osgeo.org/osgeo4w/ osgeo4w] [http://www.maptools.org/ms4w/ ms4w], etc.)

== Projects ==

TODO: Projects do not exist in isolation; and are expected to communicate and collaborate on key issues.

As an example the PostGIS release procedure asks that the release be checked with MapServer, GeoServer and others.

== SAC ==

The [[SAC|System Administration Committee]] is available to help infrastructure and facilities. Information for this committee is collected as part of the [[Project Status Template]]. The following should be set up:
* TODO: A http://projectname.osgeo.org domain name.

A project may optionally request SAC help to make use of:
* OSGeo issue tracker - not requested
* OSGeo mailing list - not requested
* OSGeo svn - not requested
* http://downloads.osgeo.org - not requested

Opticks Incubation Checklist

2013-07-10T12:57:07Z

Wiki-Dadkins: Created page with "= Opticks Incubation Checklist = == Open == The project has demonstrated that it has an open, active and healthy user and developer community: # Open: projects are expected ..."

= Opticks Incubation Checklist =

== Open ==

The project has demonstrated that it has an open, active and healthy user and developer community:
# Open: projects are expected to function in an open and public manner and include:
#* Open source license(s),
#* Open communication channels,
#* Open decision making process,
# Active and healthy community:
#* The project should have a community of developers and users who actively collaborate and support each other in a healthy way. Eg. collaboration on project activities such as testing, release and feature development.
#* Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organisations. Eg. The project is resilient enough to sustain loss of a developer or supporting organisation, often referred to as having a high [http://en.wikipedia.org/wiki/Bus_factor bus factor]. Decisions are made openly instead of behind closed doors, which empowers all developers to take ownership of the project and facilitates spreading of knowledge between current and future team members.

== Copyright and License ==

We need to ensure that the project owns or otherwise has obtained the ability to release the project code by completing the following steps:
# All project source code is available under an Open Source license.
# Project documentation is available under an open license, such as Creative Commons.
# The project code, documentation and data has been adequately vetted to assure it is all properly licensed, and a copyright notice included, as per a [http://www.osgeo.org/incubator/process/codereview.html Provenance Review].
# The project maintains a list of all copyright holders identified in the Provenance Review Document.
# All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived.

== Processes ==

# The project has code under configuration management. Eg, subversion, git.
# The project uses an issue tracker and keeps the status of the issue tracker up to date.
# The project has documented its management processes. This is typically done within a Developers Guide or Project Management Plan.
#* The project has a suitable open governance policy ensuring decisions are made, documented and adhered to in a public manner. This typically means a Project Management Committee has been established with a process for adding new members. A robust Project Management Committee will typically draw upon developers, users and key stakeholders from multiple organisations as there will be a greater variety of technical visions and the project is more resilient to a sponsor leaving.
#* The project uses public communication channels for decision making to maintain transparency. E.g. archived email list(s), archived IRC channel(s), public issue tracker.

== Documentation ==

# The project has user documentation:
#* Including sufficient detail to guide a new user through performing the core functionality provided by the application.
# The project has developer documentation:
#* Including checkout and build instructions.
#* Including commented code, ideally published for developer use. Examples: javadocs for Java applications, or Sphinx documentation for Python applications.
#* Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project's programming conventions.

==Release Procedure==

In order to maintain a consistent level of quality, the project should follow defined release and testing processes.

# The project follows a defined release process:
#* Which includes execution of the testing process before releasing a stable release.
# The project follows a documented testing process. Ideally, this includes both automated and manual testing Ideally this includes documented conformance to set quality goals, such as reporting Percentage Code Coverage of Unit Tests.
# Release and testing processes provide sufficient detail for an experienced programmer to follow.

= OSGeo Committees and Community =

The OSGeo Foundation is made up of a number of committees, projects and local chapters. This section gathers up information these groups have requested from OSGeo projects. These expectations are not mandatory requirements before graduation, but a project should be prepared to address them in order to be considered a good OSGeo citizen.

== Board ==

The OSGeo [[Board]] holds ultimate responsibility for all OSGeo activities. The Board requests:

# A project provide a Project Officer as a contract point:
#* The Project Officer should be listed at: [[Contacts#Software_Projects|Project Officer]]
#* This person is established when the incubation committee recommends the project for graduation
#* Your community can change the project officer as needed (just add an agenda item to the next board meeting so they can recognise the change of officer).

== Marketing ==

Access to OSGeo's [[Marketing_Committee]] and associated [[Marketing_Pipeline]] is one of the key benefits of joining the OSGeo foundation. The Marketing Committee requests:

# Marketing artefacts have been created about the project in line with the incubation criteria listed in the OSGeo Marketing Committee's [http://wiki.osgeo.org/wiki/Marketing_Artefacts Marketing Artefacts]. This lists the documentation requirements for [http://live.osgeo.org OSGeo-Live]. Marketing Artefacts include:
#* Application Overview
#* Application Quick Start
#* Logo
#* Graphical Image
# Ideally, stable version(s) of executable applications are bundled with appropriate distributions. In most cases, this will at least include [http://live.osgeo.org OSGeo-Live], but may also include [http://wiki.debian.org/DebianGis DebianGIS], [https://wiki.ubuntu.com/UbuntuGIS UbuntuGIS], and/or [http://trac.osgeo.org/osgeo4w/ osgeo4w] [http://www.maptools.org/ms4w/ ms4w], etc.)

== Projects ==

Projects do not exist in isolation; and are expected to communicate and collaborate on key issues.

As an example the PostGIS release procedure asks that the release be checked with MapServer, GeoServer and others.

== SAC ==

The [[SAC|System Administration Committee]] is available to help infrastructure and facilities. Information for this committee is collected as part of the [[Project Status Template]]. The following should be set up:
* A http://projectname.osgeo.org domain name.

A project may optionally request SAC help to make use of:
* OSGeo issue tracker
* OSGeo mailing list
* OSGeo svn
* http://downloads.osgeo.org

Incubation Committee

2013-07-10T12:56:55Z

Wiki-Dadkins:

The project incubation committee is responsible for overseeing the incubation process for new projects entering the foundation. The incubation committee provides resources to assist new projects to reach full membership, and makes recommendations to the board when they feel projects have completed incubation.

== Documents ==

* Official incubator public web page is at: http://osgeo.org/incubator/index.html (with members list).
* [[Incubation FAQ]]
* [[Official_IncCom_Documents]]
* Incubation process docs: http://osgeo.org/incubator/process/index.html (original [[Official_IncCom_Documents|wiki draft documents]])
* [[Incubation Badges]]

Draft or Example Documents
* Draft [[Commiter Responsibilities Guidelines]]
* OSGeo Distribution and Committer [[http://www.osgeo.org/content/foundation/legal/licenses.html licenses] which can be used as is, or as an example for projects starting off with participatory open source.
** Geotools Copyright Assignment ([http://download.osgeo.org/osgeo/legal/GeotoolsAssignmentToOSGeo.pdf pdf], [http://download.osgeo.org/osgeo/legal/GeotoolsAssignmentToOSGeo.odt odt]) - previous example
** [[Project Copyright Assignment]] - previous example
* [[Contributor Agreement]] and FAQ
* [[Incubation Phases]] proposal

Projects:
* [[OSGeo Labs]] - for young, OSGeo related projects that haven't reached incubation status
* List of [[Project Steering Committees]]

Reference:
* [[Project Infrastructure Migration]]
* [http://producingoss.com/html-chunk/index.html Producing OSS] - by Karl Fogel - an excellent primer on running an FOSS project.

Reports:
* [[Incubation Committee Report 2012]]
* [[Incubation Committee Report 2011]]

Trac:
* [http://trac.osgeo.org/osgeo/query?status=new&status=assigned&status=reopened&component=Incubator&order=priority Open Incubator Trac Issues]
* [http://trac.osgeo.org/osgeo/query?status=new&status=assigned&status=reopened&component=Incubator&keywords=%7Eapplication&order=priority Pending Incubation Applications]

== Meetings and Reports ==
Meetings are scheduled via [http://lists.osgeo.org/mailman/listinfo/incubator Mailing List] and take place via [[Getting_Started#Jump_on_IRC | IRC]] at the times specified in the [[Foundation Calendar]].
* [[IncCom Meeting1|First Meeting]] - March 13th 2006
* [[IncCom Meeting2|Second Meeting]] - March 20th 2006
* [[IncCom Meeting3|Third Meeting]] - March 27th 2006
* [[IncCom Meeting4|Fourth Meeting]] - April 10th 2006
* [[IncCom Meeting5|Fifth Meeting]] - April 24th 2006
* [[IncCom Meeting6|Sixth Meeting]] - June 19th 2006
* [[IncCom Meeting7|Seventh Meeting]] - August 7th 2006
* [[IncCom Meeting8|Eighth Meeting]] - October 30th 2006
* [[IncCom Meeting9|Nineth Meeting]] - February 12th 2007
* [[IncCom Meeting10|Tenth Meeting]] - June 11th 2007
* [[IncCom Meeting11|Eleventh Meeting]] - October 29th 2007
* [[IncCom Meeting12|Twelfth Meeting]] - September 8th 2008
* [[IncCom Meeting13|Thirteenth Meeting]] - October 29th 2009
* [[IncCom Meeting14|Fourteenth Meeting]] - March 1th 2010
* [[IncCom Meeting15]] - Nov 21 2011
* [[IncCom Meeting16]] - Jan 17 2012
* [[IncCom Meeting17]] - March 19 2012
* [[IncCom Meeting18]] - May 21 2012
* [[IncCom Meeting19]] - July 23 2012
* [[IncCom Meeting20]] - Sep 24 2012
* [[IncCom Meeting21]] - Feb 18 2013
* [[IncCom Report22]] - Jul 15 2013

== Progress in the incubator ==

The OSGeo incubation process takes place in three stages:

# Initial Application
# Incubation
## Project Status: project details, and a few resourcing questions for the system admin committee (see [[Project Status Template]]).
## Provenance Review: quick check to ensure the project is open source and has permission to distribute its source code.
## Final Checklist: review the project procedures and gather requested information for OSGeo participation
# Graduation

The following projects are currently in OSGeo incubation:

* gvSIG: http://www.osgeo.org/gvsig
*# [[gvSIG Incubation Status]]
*# [[gvSIG Provenance Review]]
*# no check list provided

* Marble: http://marble.kde.org
*#[[Marble Incubation Status]]
*# no provenance review provided
*# no check list provided

* MetaCRS: http://trac.osgeo.org/metacrs/
*# [[MetaCRS Incubation Status]]
*# no provenance review provided
*# no check list provided

* Opticks: http://opticks.org
*# [[Opticks Incubation Status]]
*# no provenance review provided
*# [[Opticks Incubation Checklist]]

* rasdaman: http://www.rasdaman.org
*# [[ rasdaman Incubation Status ]]
*# no provenance review provided
*# http://www.rasdaman.org/wiki/OSGeoIncubationChecklist

* Zoo-Project: http://www.zoo-project.org
*# status template not filled out
*# no provenance review provided
*# no check list provided

* pycsw: http://pycsw.org
*# status template not filled out
*# no provenance review provided
*# no check list provided

* TEAM Engine: http://teamengine.sourceforge.net
*# status template not filled out
*# no provenance review provided
*# no check list provided

The above pages are used to track the progress of incubation projects and are used by the developer team (and OSGeo mentor). In many cases the links
will take you to a project specific wiki or website in order to be closer to their target community.

When projects have completed the incubation checklist their mentor will recommend them to the Incubation committee for graduation.

== Graduated ==

The following status and provenance documents are for historical purposes, and are no longer actively maintained.

* Community Mapbuilder: [[Community Mapbuilder Incubation Progress]] | [[Community Mapbuilder Provenance Review]]
* deegree: [[deegree Incubation Status]] | [[deegree Provenance Review]]
* FDO: [[FDO Incubation Status]] | [[FDO Provenance Review]]
* GEOS: [[GEOS Incubation Status]] | [[GEOS Provenance Review]]
* GDAL/OGR: [[GDAL Incubation Progress]] | [[GDAL Provenance Review]]
* Geomajas: [[GeoMajas Incubation Status]] | [[GeoMajas Provenance Review]]
* GeoNetwork: [[GeoNetwork Incubation Status]] | [[GeoNetwork Provenance Review]]
* GeoMoose: [[GeoMoose Incubation Status]] | [[GeoMoose Provenance Review]] | [[GeoMoose Incubation Checklist]]
* GeoTools: [[GeoTools Incubation Progress]] | [[GeoTools Provenance Review]]
* GeoServer: [[http://geoserver.org/display/GEOS/OSGEO+incubation+questionnaire Incubation Questionnaire]] | [[http://geoserver.org/display/GEOS/GeoServer+Incubation+Status Incubation Status]] | [[http://geoserver.org/display/GEOS/GeoServer+Provenance+Review Provenance Review]] | [[http://geoserver.org/display/GEOS/GeoServer+Incubation+Checklist Incubation Checklist]] | [[Geoserver Mentor Notes]]
* GRASS: [[GRASS Incubation Progress]] | [[GRASS Provenance Review]]
* Mapbender: [[Mapbender Incubation Progress]] | [[Mapbender Provenance Review]]
* MapFish: [[MapFish Incubation Status]] | [[MapFish Provenance Review]] (Graduated: August 2011)
* MapGuide: [[MapGuide Incubation Status]] | [[MapGuide Provenance Review]]
* MapServer: [[MapServer incubation status]] | [[MapServer Provenance Review]]
* OpenLayers: [[OpenLayers Incubation Status]] | [[OpenLayers Provenance Review]]
* PostGIS: [[PostGIS Incubation Status]] | [[PostGIS Provenance Review]]
* OSSIM: [[OSSIM incubation status]] | [http://trac.osgeo.org/ossim/wiki/ossimprovenance OSSIM Provenance Review]
* QGIS: [[QGIS Incubation Status]] | [[QGIS Provenance Review]]

The initial projects to go through the incubation process helped define what is required. The above pages tracked the progress (and capture the experience) of these projects.

[[Category:Incubation]]
[[Category:Committees]]

Incubation Committee

2012-11-29T14:03:22Z

Wiki-Dadkins:

The project incubation committee is responsible for overseeing the incubation process for new projects entering the foundation. The incubation committee provides resources to assist new projects to reach full membership, and makes recommendations to the board when they feel projects have completed incubation.

== Documents ==

* Official incubator public web page is at: http://osgeo.org/incubator/index.html (with members list).
* [[Incubation FAQ]]
* [[Official_IncCom_Documents]]
* Incubation process docs: http://osgeo.org/incubator/process/index.html (original [[Official_IncCom_Documents|wiki draft documents]])
* [[Incubation Badges]]

Draft or Example Documents
* Draft [[Commiter Responsibilities Guidelines]]
* Geotools Copyright Assignment ([http://download.osgeo.org/osgeo/legal/GeotoolsAssignmentToOSGeo.pdf pdf], [http://download.osgeo.org/osgeo/legal/GeotoolsAssignmentToOSGeo.odt odt]) -suitable for use as a template by other projects
* [[Project Copyright Assignment]] (older copyright assignment - GeoTools template now preferred)
* [[Contributor Agreement]] and FAQ
* [[Incubation Phases]] proposal

Projects:
* [[OSGeo Labs]] - for young, OSGeo related projects that haven't reached incubation status
* List of [[Project Steering Committees]]

Reference:
* [[Project Infrastructure Migration]]
* [http://producingoss.com/html-chunk/index.html Producing OSS] - by Karl Fogel - an excellent primer on running an FOSS project.

Reports:
* [[Incubation Committee Report 2011]]

Trac:
* [http://trac.osgeo.org/osgeo/query?status=new&status=assigned&status=reopened&component=Incubator&order=priority Open Incubator Trac Issues]
* [http://trac.osgeo.org/osgeo/query?status=new&status=assigned&status=reopened&component=Incubator&keywords=%7Eapplication&order=priority Pending Incubation Applications]

== Meetings ==
Meetings are scheduled via [http://lists.osgeo.org/mailman/listinfo/incubator Mailing List] and take place via [[Getting_Started#Jump_on_IRC | IRC]] at the times specified in the [[Foundation Calendar]].
* [[IncCom Meeting1|First Meeting]] - March 13th 2006
* [[IncCom Meeting2|Second Meeting]] - March 20th 2006
* [[IncCom Meeting3|Third Meeting]] - March 27th 2006
* [[IncCom Meeting4|Fourth Meeting]] - April 10th 2006
* [[IncCom Meeting5|Fifth Meeting]] - April 24th 2006
* [[IncCom Meeting6|Sixth Meeting]] - June 19th 2006
* [[IncCom Meeting7|Seventh Meeting]] - August 7th 2006
* [[IncCom Meeting8|Eighth Meeting]] - October 30th 2006
* [[IncCom Meeting9|Nineth Meeting]] - February 12th 2007
* [[IncCom Meeting10|Tenth Meeting]] - June 11th 2007
* [[IncCom Meeting11|Eleventh Meeting]] - October 29th 2007
* [[IncCom Meeting12|Twelfth Meeting]] - September 8th 2008
* [[IncCom Meeting13|Thirteenth Meeting]] - October 29th 2009
* [[IncCom Meeting14|Fourteenth Meeting]] - March 1th 2010
* [[IncCom Meeting15]] - Nov 21 2011
* [[IncCom Meeting16]] - Jan 17 2012
* [[IncCom Meeting17]] - March 19 2012
* [[IncCom Meeting18]] - May 21 2012
* [[IncCom Meeting19]] - July 23 2012
* [[IncCom Meeting20]] - Sep 24 2012

== Progress in the incubator ==
We are watching the initial projects go through the incubation process as a method of defining what is required. The following pages track the progress (and experience) of these projects.

* [[Project Status Template]]

* gvSIG: [[gvSIG Incubation Status]] | [[gvSIG Provenance Review]]
* GeoServer: [[http://geoserver.org/display/GEOS/OSGEO+incubation+questionnaire Incubation Questionnaire]] | [[http://geoserver.org/display/GEOS/GeoServer+Incubation+Status Incubation Status]] | [[http://geoserver.org/display/GEOS/GeoServer+Provenance+Review Provenance Review]] | [[http://geoserver.org/display/GEOS/GeoServer+Incubation+Checklist Incubation Checklist]]
* GeoMoose: [[GeoMoose Incubation Status]] | [[GeoMoose Provenance Review]] | [[GeoMoose Incubation Checklist]]
* Marble [[Marble Incubation Status]]
* MetaCRS: [[MetaCRS Incubation Status]] | [[MetaCRS Provenance Review]]
* Opticks: [[Opticks Incubation Status]]
* rasdaman: [[ rasdaman Incubation Status ]]
* Zoo-Project

Each project may also have a page describing the Incubation process on their own community website. Please make sure to you link to the above pages and update the OSGeo Wiki page regularly so that IncCom can keep up to date.

== Graduated ==

The following status and provenance documents are for historical purposes, and are no longer actively maintained.

* Community Mapbuilder: [[Community Mapbuilder Incubation Progress]] | [[Community Mapbuilder Provenance Review]]
* deegree: [[deegree Incubation Status]] | [[deegree Provenance Review]]
* FDO: [[FDO Incubation Status]] | [[FDO Provenance Review]]
* GEOS: [[GEOS Incubation Status]] | [[GEOS Provenance Review]]
* GDAL/OGR: [[GDAL Incubation Progress]] | [[GDAL Provenance Review]]
* Geomajas: [[GeoMajas Incubation Status]] | [[GeoMajas Provenance Review]]
* GeoNetwork: [[GeoNetwork Incubation Status]] | [[GeoNetwork Provenance Review]]
* Geotools: [[GeoTools Incubation Progress]] | [[GeoTools Provenance Review]]
* GRASS: [[GRASS Incubation Progress]] | [[GRASS Provenance Review]]
* Mapbender: [[Mapbender Incubation Progress]] | [[Mapbender Provenance Review]]
* MapFish: [[MapFish Incubation Status]] | [[MapFish Provenance Review]] (Graduated: August 2011)
* MapGuide: [[MapGuide Incubation Status]] | [[MapGuide Provenance Review]]
* MapServer: [[MapServer incubation status]] | [[MapServer Provenance Review]]
* OpenLayers: [[OpenLayers Incubation Status]] | [[OpenLayers Provenance Review]]
* PostGIS: [[PostGIS Incubation Status]] | [[PostGIS Provenance Review]]
* OSSIM: [[OSSIM incubation status]] | [http://trac.osgeo.org/ossim/wiki/ossimprovenance OSSIM Provenance Review]
* QGIS: [[QGIS Incubation Status]] | [[QGIS Provenance Review]]

[[Category:Incubation]]
[[Category:Committees]]

Opticks Incubation Status

2012-11-29T14:03:08Z

Wiki-Dadkins:

== General ==

; Has the project been approved for incubation by the OSGeo board?
: Yes

; Has an Incubation Mentor been assigned to the project?
: Yes, [[Mark_Lucas]] graciously volunteered to be our mentor.

== Infrastructure Transition ==

''Note, for each of the following it isn't necessary to move to foundation infrastructure, but if you aren't a reason should be provided.''

; Has the projectname.osgeo.org domain been populated with the projects web presence?
: There are no plans as of right now to transition away from http://opticks.org since that has been the project's homepage for quite some time now.

; Is the OSGeo bug tracker being used for the project?
: There are no plans as of right now to transition away from https://issues.opticks.org since that has been the project's bug tracker for quite some time now.

; Is the OSGeo mailing list manager (http://lists.osgeo.org/) being used for the project?
: There are no plans as of right now to transition away from sourceforge since that has been the project's mailing list manager for quite some time now.

; Is the OSGeo SVN being used for the project?
: There are no plans as of right now to transition away from sourceforge since that has been the project's svn host for quite some time now.

; Are binary and source downloads available from http://download.osgeo.org ?
: No, because they are available at http://opticks.org (although we could mirror them here).

== Community Functioning ==

; Is there a functioning user support mechanisms (ie. mailing list)?
: Yes, we have a user mailing list and #opticks on freenode.

; Are source and binary downloads for the package available?
: Yes, although source must be retrieved from svn.

; Has a Project Steering Committee been formed, and given control of the project?
: Yes, see [http://opticks.org/confluence/display/opticks/Opticks+Governance+Policy this] page for detailed information.

; Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines, etc.
: Yes, see [http://opticks.org/confluence/display/opticks/Opticks+Governance+Policy this] page for detailed information.

; How many active developers are there? Are they from multiple organizations?
: Indicate number and some organizations involved.

== Foundation Membership ==

; Have project documents been updated to reflect membership in the foundation, and the relationship of the project to the foundation?
: Not yet, details and timeline are still TBD.

; Has an effort been made to brand the project web site with OSGeo foundation web styling and branding marks?
: Not yet, details and timeline are still TBD.

== Code Copyright Review ==

; Has a [[Code Provenance Review]] document been prepared for the project?
: Not yet, details and timeline are still TBD.

; Have issues raised in the provenance review been adequately addressed?
: N/A

; Are [[Commiter Responsibilities Guidelines]] covering legal issues in place?
: Not yet, details and timeline are still TBD.

[[Category:Incubation]]

Opticks Incubation Status

2012-11-29T14:02:38Z

Wiki-Dadkins: Created page with "== General == ; Has the project been approved for incubation by the OSGeo board? : Yes ; Has an Incubation Mentor been assigned to the project? : Yes, Mark_Lucas graciousl..."

== General ==

; Has the project been approved for incubation by the OSGeo board?
: Yes

; Has an Incubation Mentor been assigned to the project?
: Yes, [[Mark_Lucas]] graciously volunteered to be our mentor.

== Infrastructure Transition ==

''Note, for each of the following it isn't necessary to move to foundation infrastructure, but if you aren't a reason should be provided.''

; Has the projectname.osgeo.org domain been populated with the projects web presence?
: There are no plans as of right now to transition away from http://opticks.org since that has been the project's homepage for quite some time now.

; Is the OSGeo bug tracker being used for the project?
: There are no plans as of right now to transition away from https://issues.opticks.org since that has been the project's bug tracker for quite some time now.

; Is the OSGeo mailing list manager (http://lists.osgeo.org/) being used for the project?
: There are no plans as of right now to transition away from sourceforge since that has been the project's mailing list manager for quite some time now.

; Is the OSGeo SVN being used for the project?
: There are no plans as of right now to transition away from sourceforge since that has been the project's svn host for quite some time now.

; Are binary and source downloads available from http://download.osgeo.org ?
: No, because they are available at http://opticks.org (although we could mirror them here).

== Community Functioning ==

; Is there a functioning user support mechanisms (ie. mailing list)?
: Yes, we have a user mailing list and #opticks on freenode.

; Are source and binary downloads for the package available?
: Yes, although source must be retrieve from svn.

; Has a Project Steering Committee been formed, and given control of the project?
: Yes, see [http://opticks.org/confluence/display/opticks/Opticks+Governance+Policy this] page for detailed information.

; Does the Project Steering Committee have documentation on project procedures for PSC decisions, contributor guidelines, etc.
: Yes, see [http://opticks.org/confluence/display/opticks/Opticks+Governance+Policy this] page for detailed information.

; How many active developers are there? Are they from multiple organizations?
: Indicate number and some organizations involved.

== Foundation Membership ==

; Have project documents been updated to reflect membership in the foundation, and the relationship of the project to the foundation?
: Not yet, details and timeline are still TBD.

; Has an effort been made to brand the project web site with OSGeo foundation web styling and branding marks?
: Not yet, details and timeline are still TBD.

== Code Copyright Review ==

; Has a [[Code Provenance Review]] document been prepared for the project?
: Not yet, details and timeline are still TBD.

; Have issues raised in the provenance review been adequately addressed?
: N/A

; Are [[Commiter Responsibilities Guidelines]] covering legal issues in place?
: Not yet, details and timeline are still TBD.

[[Category:Incubation]]

IncCom Meeting18

2012-05-03T12:19:10Z

Wiki-Dadkins: /* Agenda */

= Time =

* Proposed date: Mon, 21 May 2012
** [http://www.timeanddate.com/worldclock/meetingdetails.html?year=2012&month=05&day=21&hour=13&min=0&sec=0&p1=47&p2=87&p3=179&p4=44%5D Australia 11pm India 6:30pm Europe 3pm America 9am]
** [http://www.timeanddate.com/worldclock/meetingdetails.html?year=2012&month=05&day=21&hour=21&min=0&sec=0&p1=47&p2=87&p3=179&p4=44%5D Australia 7am India 2:30am Europe 11pm America 5pm]
* Location: IRC channel [irc://irc.freenode.net/#osgeo #osgeo] (alternative [http://irc.telascience.org/ Web] client).

= Agenda =

1) Approve minutes from [[IncCom Meeting17]]

2) From email list

* GEOS proposed for graduation; motioned carried on April 9th with +1 from Cameron Shorter, Frank
Warmerdam, Jorge Gaspar Sanz Salinas, and Jody Garnett); Frank to add to next board meeting
* [[Draft_Project_Graduation_Checklist_Draft]] proposed; motion carried on April 15th with +1 from Cameron Shorter, Frank
Warmerdam, Jody Garnett, Daniel Morissette, Arnulf, Jorge Gaspar Sanz Salinas, Bob Basques, Steve Lime. Website page pending?
* ZOO-Project to enter incubation with FrankW as mentor?
* [[Incubation_Committee_Report_2011]] completed

3) status update from mentors or team representatives

* geomoose / Jody Garnett
* geoserver / pspencer
* gvSig / jsanz
* MetaCRS / Daniel Morissette
* PostGIS / Arnulf (away?)
* rasdaman / Bruce Bannerman (Jody Backup)
* ZOO-Project / FrankW

4) Review pending incubation applications

[http://trac.osgeo.org/osgeo/query?status=new&status=assigned&status=reopened&component=Incubator&keywords=%7Eapplication&order=priority Pending Applications in Trac]

* Opticks / dadkins

5) Review open incubation issues

[http://trac.osgeo.org/osgeo/query?status=assigned&status=new&status=reopened&group=component&component=Incubator&order=priority Open Incubation Issues]

= Minutes =

Full log:

http://irclogs.geoapt.com/osgeo/%23osgeo.2012-05-21.log

# Attending:
# Accepted minuets from [IncCom_Meeting17]
# etc...

[[Category:Incubation]]

Google Summer of Code 2012 Ideas

2012-03-05T13:37:49Z

Wiki-Dadkins: /* The ideas pages */

[[Image:Gsoc-2012-logo-color.png|350px|link=http://code.google.com/soc/]] @ [[Image:OSGeo_300_127_pixel.png|link=http://www.osgeo.org]]

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

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

=OSGeo Google Summer of Code 2012=

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

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

'''If you need more information on how to apply you can contact all the mentoring organisations via soc at lists.osgeo.org'''

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

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

=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.co.nz/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 intergrate you into the developer community, so you should get involved from the start. The more you communicate the easier it will be. Don't be afraid that the mentors will request your phone number. It is only to make sure that we can reach you, in case of problems.

==Weekly reports==
Yes, every week we expect to see a report posted to the soc@osgeo mailing list that at least answers the following questions:
# What did you get done this week?
# What do you plan on doing next week?
# Are you blocked on anything?
These questions BTW are the same as are used in real-work, when developing with the
[http://en.wikipedia.org/wiki/Scrum_(development) Scrum] [http://en.wikipedia.org/wiki/Agile_software_development development process]. ;)

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

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

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

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

=Timeline=

* '''[http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2012/faqs#timeline The official timeline]'''


* March 16: Google announces accepted organizations. If OSGeo is accepted as an organization for Google Summer of Code, start talking to us earlier rather than later.
* '''March 26''': 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.
* '''April 6''': Student application deadline.
* April 23: Accepted student proposals are announced.
* '''May 21''': 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 13: Mid-term evaluation.
* '''August 13''': Pencils down!
* August 24: Final evaluation deadline
* August 27: Final results announced
* August 31: Students begin submitting required code samples to Google

= The ideas pages =

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



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

* [http://www.qgis.org/wiki/Google_Summer_of_Code_2012 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.





* [[OpenRouter 2012 SOC Ideas|OpenRouter/pgRouting 2012 SOC Ideas]]: OpenRouter/pgRouting is a couple of projects that are building routing and driving direction libraries and applications that can be integrated with other applications.













* [[GvSIG GSoC 2012 Ideas|gvSIG]] is the free GIS project developed by the gvSIG Association. gvSIG is at this time a group of software developments for [http://www.gvsig.org/web/projects/gvsig-desktop/description2/view?set_language=en Desktop],[http://www.gvsig.org/web/projects/gvsig-mobile/description-2/view?set_language=en PDAs] and [http://gvsigmini.org mobile phones]. The gvSIG project looks for students with Java skills that want to develop new ideas on any of gvSIG products.



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



= Application Template =

(All questions must be answered)

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?

= What is the main public mailing list for your organization? =
Since OSGeo is an umbrella organisation for multiple projects, each project has their own discussion and development mailing lists.

'''Main OSGeo mailing lists of interest to students.'''

Please start here, when contacting us for the first time with questions about Google Summer of Code.

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

Also see the [[Mailing Lists]] page for project specific lists.

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

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

Project irc channels:

* irc://irc.freenode.net/#gdal
* irc://irc.freenode.net/#geoserver
* irc://irc.freenode.net/#geotools
* irc://irc.freenode.net/#grass
* irc://irc.freenode.net/#gvsig
* irc://irc.freenode.net/#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

[Back to [[Google Summer of Code 2012]] @ OSGeo]

[[Category: Google Summer of Code]]

Google Summer of Code Application 2012

2012-03-05T13:36:11Z

Wiki-Dadkins: /* Why is your organization applying to participate in GSoC 2012? What do you hope to gain by participating? */

[[Image:Gsoc-2012-logo-color.png|300px|right]]
[[Image:OSGeo_300_127_pixel.png|300px|right]]

: http://www.google-melange.com
== Application Deadline ==

Status: ''Not yet applied''

: http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2012/faqs#timeline

* Monday, '''February 27''': 12:00 PST (19:00 UTC)
: Mentoring organizations can begin submitting applications to Google.

* Friday, '''March 9''': 16:00 PST (23:00 UTC)
: Mentoring organization application deadline.

== Old ==

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

== Pending ==

* Verify if the application rules have changed in any way since we last looked at them.

* Apply

== New ==

* Anne!

=== For discussion ===

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

proposed additional question for the application:

* HB: not really a question, but I propose we should reinforce that all questions must be answered by the students, they can't pick and choose the ones that make them look good. e.g. the student must be aware that if they fail to e.g. supply a timeline their application is incomplete and they won't be chosen.

* HB: in the timeline question I propose we emphasize midterm deliverable(s). Also, what do you think about the idea of asking for internal 25% and 75% deliverables? (to avoid major shocks at the midterm and concertina workloads), with a note that 50,75,100% deliverables can be adjusted at quarterly delivery dates?

* HB: also re the all important timeline, I suggest we make it clear (somewhere) early on that learning how to compile, install, and use the software, and also spending weeks reading books is really stuff they should be doing before applying and on into the community bonding period. The previous years where coding for some projects didn't start until week 3-4 as the student didn't have the project code building yet isn't good enough IMO.

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

* ...

== The Application ==

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

=== Description ===

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

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

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

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

Metadata Catalog: '''GeoNetwork'''

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

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

=== Main Organization License ===

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

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

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

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

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

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

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

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

* No

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

OSGeo participated in 2011, with a very good success rate. Many of the students continued to work with their OSGeo projects after the end of summer, and even become official contributors. The mentoring has been overall effective, and the communication among students, mentors and admins has been constant. Still, getting in contact with elusive participants represented the main difficulty, and has been addressed case to case.

OSGeo sent 2 delegates to Mentor Summit, and benefited of the presence of 2 more, who were already in Mountain View. As previous year, the delegates chaired a Geospatial session, and improved connections with many other projects.

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

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

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

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

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

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

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

=== If your organization participated in past GSoCs, please let us know the ratio of students passing to students allocated ===
''e.g. 2006: 3/6 for 3 out of 6 students passed in 2006.''

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

2011 app comment: ''the breakdown of the failures is interesting-
Were failures all from first-time-SOC / outside-of-osgeo projects?
* MapGuide - OSGeo - student who failed was a last minute replacement for Sergei who we gave to another SOC org during the conflict resolution swap-meet.
* MapWindow - non-member OSGeo
* GeoKettle - non-member OSGeo
*

2c thoughts: So we could do better helping our "outsider" projects in? Or perhaps projects already accepted into OSGeo have a long history and established already-integrated teams, thus correlation with success in an OSGeo-led endeavour is not entirely surprising. (aka we can twist our friends arms with greater force than we can our guests).''

I'd better say that long time OSGeo projects have a history of communication with OSGeo itself and with other projects. New OSGeo projects, as non members or in incubation, need more guidance on that. Another factor is the size of the community: if it is very small, the efforts are concentrated on coding and on non-GSoC tasks, that leads to less interaction. ([[User:Aghisla]])

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

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

http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2012_Ideas

=== What is the main development mailing list for your organization? ===
''This question will be shown to students who would like to get more information about applying to your organization for GSoC 2011. If your organization uses more than one list, please make sure to include a description of the list so students know which to use.''
(required)

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

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

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

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

=== Does your organization have an application template you would like to see students use? ===
''If so, please provide it now. Please note that it is a very good idea to ask students to provide you with their contact information as part of your template. Their contact details will not be shared with you automatically via the GSoC 2011 site.''

Name:

Country:

School and degree:

Email:

Phone:

OSGeo project(s):

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

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

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

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

Please provide details of previous GIS experience:

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

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

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

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

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

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

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

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

The project administrator is appointed by the OSGeo board at the beginning of the year. The project administrator asks for one or two people he trusts to be the backup administrators. Mentors are selected by project steering committees and development teams based on their reputation as skilled developers, domain experience, previously demonstrated ability to support new project developers, and stated willingness to devote time to the mentoring process. We also try very hard to match up the student working on a specific module or tool with a developer with the best expertise in the relevant area.

We have in the past not voted up an otherwise good student project if there was no mentor capable of overseeing the project from a technical standpoint. Fortunately we have had a strong response from the developer pool so this has not been a major problem - it is however important to make the student aware of it, to avoid misunderstandings. Moreover, this should not happen with students who are approaching OSGeo for the first time, as they are less likely to know the right people/lists to contact.

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

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

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

Other possibilities include:

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

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

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

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

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

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

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

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

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

n/a

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

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

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

As in 2011, there is also the Opticks project, but they are participating under the OSGeo umbrella, since they are progressing in the OSGeo incubation process.

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

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

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

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

Backup administrators:
* Wolf Bergenheim (melange: ?)
* Hamish Bowman (melange: hamish)

[Back to [[Google Summer of Code 2012]] @ OSGeo]

[[Category: Google Summer of Code]]

IncCom Meeting15

2011-11-17T13:28:16Z

Wiki-Dadkins: /* Agenda */

= Time =

* Proposed date: Mon, 21 Nov 2011
* Proposed time Australia 11pm, 6pm India, 2pm Europe, 8am Americas: [http://www.timeanddate.com/worldclock/meetingdetails.html?year=2011&month=11&day=21&hour=13&min=0&sec=0&p1=47&p2=87&p3=179&p4=44]
* Proposed location: IRC channel [irc://irc.freenode.net/#osgeo #osgeo] (alternative [http://irc.telascience.org/ Web] client).

= Agenda =

1) Approve minutes from [[IncCom Meeting14]]

2) status update from mentors / team representatives

3) review incubation applications

* geomoose incubation application / Jody Garnett mentor [http://trac.osgeo.org/osgeo/ticket/147]
* zoo wps application [http://trac.osgeo.org/osgeo/ticket/828]
* rasdaman application / Bruce Bannerman mentor / [http://trac.osgeo.org/osgeo/ticket/553]
* Opticks application / Mark Lucas mentor / [http://trac.osgeo.org/osgeo/ticket/666]

4) Review open incubation issues [http://trac.osgeo.org/osgeo/query?status=assigned&status=new&status=reopened&group=component&component=Incubator&order=priority]

= Minutes =

Full Log: http://logs.qgis.org/osgeo/