<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.osgeo.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Gvsig</id>
	<title>OSGeo - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.osgeo.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Gvsig"/>
	<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/wiki/Special:Contributions/Gvsig"/>
	<updated>2026-04-11T21:46:44Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.35.9</generator>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=OSGeo_Budget_2023&amp;diff=129737</id>
		<title>OSGeo Budget 2023</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=OSGeo_Budget_2023&amp;diff=129737"/>
		<updated>2023-01-02T08:56:36Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: gvSIG budget update&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Draft budget for 2023, see [[OSGeo Budget 2022]] and [[Finance Committee#Documents]] for prior years.&lt;br /&gt;
&lt;br /&gt;
Total Approved Budget for 2022: $213,346 USD&lt;br /&gt;
&lt;br /&gt;
Total spending for 2022: TBD&lt;br /&gt;
&lt;br /&gt;
Total Approved Budget for 2023: TBD &lt;br /&gt;
&lt;br /&gt;
== OSGeo Board ==&lt;br /&gt;
&lt;br /&gt;
OSGeo board operates according to our bylaws providing vision and direction for our foundation. The board has also taken on responsibility setting for an annual budget, building partner relationships, sponsorship program and code sprints.&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! Board&lt;br /&gt;
! 2022 Approved&lt;br /&gt;
! 2022 Actual&lt;br /&gt;
! 2023 Draft&lt;br /&gt;
! Notes&lt;br /&gt;
|- &lt;br /&gt;
| Admin&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 4,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| Operational expenses including liability insurance, tax filing fees, quickbooks, mail, IRS, bank fees.&lt;br /&gt;
|-&lt;br /&gt;
| Travel&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 15,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| Travel to main FOSS4G, F2F meeting and regional/representative events&lt;br /&gt;
|-&lt;br /&gt;
| Partners and Sponsors&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| Relationship building, attending b2b functions, foss4g/foss4ge/foss4gna/foss4g-asia breakfast meetings. Meetings with sponsors during events&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Total Board Budget for 2022: $21,000 USD&lt;br /&gt;
&lt;br /&gt;
Total Board spending for 2022: TBD&lt;br /&gt;
&lt;br /&gt;
Total Board Budget for 2023: TBD&lt;br /&gt;
&lt;br /&gt;
== OSGeo Committees ==&lt;br /&gt;
&lt;br /&gt;
The following committees have been formed to fulfill out goals as an organization, each committee is provided a mandate, with the chair of the committee represented as an officer of our organization.&lt;br /&gt;
&lt;br /&gt;
* Code of Conduct Committee&lt;br /&gt;
* Conference Committee&lt;br /&gt;
* GeoForAll - committee acting as advisory board for the GeoForAll Initiative &lt;br /&gt;
* Incubation Committee - committee providing hands-on support for project teams adopting open source principles and practice.&lt;br /&gt;
* Marketing Committee - outreach and advocacy support&lt;br /&gt;
* Open GeoScience Committee&lt;br /&gt;
* System Administration Committee - foundation infrastructure &lt;br /&gt;
* UN Committee - committee responsible for our participation in the UN Open GIS program&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! OSGeo Committees&lt;br /&gt;
! 2022 Approved [Requested]&lt;br /&gt;
! 2022 Actual&lt;br /&gt;
! 2023 Draft [Requested]&lt;br /&gt;
! Notes&lt;br /&gt;
|- &lt;br /&gt;
| SAC&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 32,550 &amp;lt;br/&amp;gt; [32,550]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| [[SAC:Budget#2022]], [[SAC:Budget#2023]]&lt;br /&gt;
|-&lt;br /&gt;
| OpenGeoScience&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,500 &amp;lt;br/&amp;gt; [3,000]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| Please contact marketing committee for marketing materials (500$)&lt;br /&gt;
|-&lt;br /&gt;
| Conference&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| Marketing&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 7,500 &amp;lt;br/&amp;gt; [7,000]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
|[[Marketing Committee Budget 2022]]. Extra 500$ for OpenGeoScience material.&lt;br /&gt;
|-&lt;br /&gt;
| GeoForAll&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 4,000 &amp;lt;br/&amp;gt; [4,000]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:left;&amp;quot; |$2000 for South American student event as requested by Sergio Acosta y Lara &amp;lt;br/&amp;gt; $2000 for Global GeoforAll competition and request by labs. &lt;br /&gt;
|-&lt;br /&gt;
| UN Committee&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| No UN challenge this year&lt;br /&gt;
|-&lt;br /&gt;
| Incubation Committee&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 6,000 &amp;lt;br/&amp;gt; [8,000]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Total Committees Budget for 2022: $52,550 USD&lt;br /&gt;
&lt;br /&gt;
Total Committees spending for 2022: TBD&lt;br /&gt;
&lt;br /&gt;
Total Committees Budget for 2023: TBD&lt;br /&gt;
&lt;br /&gt;
== OSGeo Initiatives ==&lt;br /&gt;
&lt;br /&gt;
OSGeo initiatives have formed to pursue a specific short term, or long term goal. Initiatives maybe formed by a committee or the board as required. Initiatives are a great way to collaborate with projects, committees and partners.&lt;br /&gt;
&lt;br /&gt;
* FOSS4G - event series produced in collaboration with the conference committee and local chapters&lt;br /&gt;
* GeoForAll - education and research program produced in collaboration with our partners&lt;br /&gt;
* Incubation - mentor program for open source projects to be recognized as OSGeo project&lt;br /&gt;
* Local Chapters - board outreach initiative establishing regional OSGeo groups for direct grassroots advoacacy&lt;br /&gt;
* GSoC - coordinate participation in google-summer-of-code and code-in activities&lt;br /&gt;
* Travel Grant Program - provides assistance for attending OSGeo events&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! OSGeo Initiatives&lt;br /&gt;
! 2022 Approved&lt;br /&gt;
! 2022 Actual&lt;br /&gt;
! 2023 Draft&lt;br /&gt;
! Notes&lt;br /&gt;
|- &lt;br /&gt;
| FOSS4G&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 66,796&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| Seed money for 2022.&lt;br /&gt;
|-&lt;br /&gt;
| Local Chapters&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| Managed by board, considering putting aside money to help establish local chapters (for logistics, legal advise, kickoff meetings rather than any sponsorship or direct funding)&lt;br /&gt;
|-&lt;br /&gt;
| GSoC&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| Managed by board.&lt;br /&gt;
|-&lt;br /&gt;
| Travel Grant Program &lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 15,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| Managed by Conference Committee. FOSS4G 2022 asked for 10k in conference mailing list, 5k proposed by board for local events.&lt;br /&gt;
|-&lt;br /&gt;
| Events and Code Sprints&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 20,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| Managed by the board. Funding to help organize OSGeo Code Sprint and other events (e.g. QGIS User Conference, PostGIS Code Sprint, GRASS GIS Community Sprint etc.) &amp;lt;br/&amp;gt; Board note: This budget reflects the 15,000 sponsorship we got for the postponed Athens Code Sprint.&lt;br /&gt;
|-&lt;br /&gt;
| Community Projects&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 5,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| Managed by the board since community projects do not have an assigned officer to handle their budget. We have around 30 projects expected in 2022. &amp;lt;br/&amp;gt; Board note: Budgeted 300$ for each project. To be amended if we hit the ceiling of the budget. &lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Total Initiatives Budget for 2022: $106,796 USD&lt;br /&gt;
&lt;br /&gt;
Total Initiatives spending for 2022: TBD&lt;br /&gt;
&lt;br /&gt;
Total Initiatives Budget for 2023: TBD&lt;br /&gt;
&lt;br /&gt;
= Projects =&lt;br /&gt;
&lt;br /&gt;
==  OSGeo Projects ==&lt;br /&gt;
&lt;br /&gt;
OSGeo Projects each have a project steering committee, the chair of which is acknowledged as a foundation officer with spending authority on behalf of their committee.&lt;br /&gt;
&lt;br /&gt;
Notes:&lt;br /&gt;
&lt;br /&gt;
* We have reached out (2022) to the projects mailing list.&lt;br /&gt;
* Board decided to assign a default budget of $500 for any project that has reported to the board within the year.&lt;br /&gt;
* Projects with a plan may of course ask for increased funding&lt;br /&gt;
* This is a budget, representing planned spending in 2022 - actual balance available to each PSC (from fundraising, donations and sponsorship) may be considered when planning.&lt;br /&gt;
* If a project did not respond (or runs into an unforeseen expense) please contact the board throughout the year as budgets can be amended&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! OSGeo Project&lt;br /&gt;
! 2022 Approved [Requested]&lt;br /&gt;
! 2022 Actual&lt;br /&gt;
! 2023 Draft [Requested]&lt;br /&gt;
! Notes&lt;br /&gt;
|- &lt;br /&gt;
| deegree&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000 &amp;lt;br/&amp;gt; [2,000]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| https://github.com/deegree/deegree3/wiki/deegree-budget-2022&lt;br /&gt;
|-&lt;br /&gt;
| GDAL/OGR&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| 2021 spending includes Travis CI subscription.&lt;br /&gt;
|-&lt;br /&gt;
| GeoMOOSE&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,500 &amp;lt;br/&amp;gt; [2,500]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| https://github.com/geomoose/geomoose/wiki/PSC-Meeting-2021-10-15&lt;br /&gt;
|-&lt;br /&gt;
| GeoNetwork&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| GeoNode&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GEOS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GeoServer&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 3,000 &amp;lt;br/&amp;gt; [3,000]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| [[GeoServer Budget 2022]]&lt;br /&gt;
|-&lt;br /&gt;
| GeoTools&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| GRASS GIS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 4,000 &amp;lt;br/&amp;gt; [3964.49]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| [[GRASS GIS Budget 2022]]&lt;br /&gt;
|-&lt;br /&gt;
| gvSIG&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 5,000 &amp;lt;br/&amp;gt; [5,000]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD [5,000]&lt;br /&gt;
| [[GvSIG Budget 2023]]&lt;br /&gt;
|-&lt;br /&gt;
| Mapbender&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| MapServer&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
|  &lt;br /&gt;
|-&lt;br /&gt;
| Marble&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| Need to report to the board to get a budget&lt;br /&gt;
|-&lt;br /&gt;
| OpenLayers&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 3,000 &amp;lt;br/&amp;gt; [3,000]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| [[OpenLayers Budget 2022]]&lt;br /&gt;
|-&lt;br /&gt;
| OTB&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| OSGeoLive&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| PostGIS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| PROJ&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| pycsw&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,500 &amp;lt;br/&amp;gt; [2,500]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD [2,500]&lt;br /&gt;
| https://github.com/geopython/pycsw/wiki/OSGeo-Budget-2023&lt;br /&gt;
|-&lt;br /&gt;
| pygeoapi&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 300&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD [3,000]&lt;br /&gt;
| https://github.com/geopython/pygeoapi/wiki/OSGeo-Budget-2023&lt;br /&gt;
|-&lt;br /&gt;
| PyWPS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| QGIS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 5,000 &amp;lt;br/&amp;gt; [5,000]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD &lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| for website work https://www.qgis.org/en/_downloads/1545388ea396bf7e83de68df47f8cf0b/QGISBudget2022.pdf&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Total Projects Budget for 2022: $33,000 USD&lt;br /&gt;
&lt;br /&gt;
Total Projects spending for 2022: TBD&lt;br /&gt;
&lt;br /&gt;
Total Projects Budget for 2023: TBD&lt;br /&gt;
&lt;br /&gt;
==  Community Projects ==&lt;br /&gt;
&lt;br /&gt;
Community projects act through the board as they do not have a project officer. Board approved $300 for each project (see Community Projects Initiative above)&lt;br /&gt;
&lt;br /&gt;
Some guidance is offered by individual projects below.&lt;br /&gt;
&lt;br /&gt;
Please note that this table records budget requests, not approved budgets. Community Projects can ask the Board for spending approval (since they do not have a Project Officer) from the approved Community Projects budget. Projects that are also in incubation can ask the Incubation Committee for spending approval from the Incubation Committee approved budget. See notes column for actual budget approval per project.&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! Community Project&lt;br /&gt;
! 2022 Approved [Requested]&lt;br /&gt;
! 2022 Actual&lt;br /&gt;
! 2023 Draft [Requested]&lt;br /&gt;
! Notes&lt;br /&gt;
|-&lt;br /&gt;
| pgRouting&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 300&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD &lt;br /&gt;
| 2022 Board note: 300 USD approved from Community Projects budget. For more budget the project has to ask incubation committee.&lt;br /&gt;
|-&lt;br /&gt;
| istSOS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 300&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD &lt;br /&gt;
| 2022 Board note: 300 USD approved from Community Projects budget. For more budget the project has to ask incubation committee.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
= Events =&lt;br /&gt;
&lt;br /&gt;
== Community Events ==&lt;br /&gt;
&lt;br /&gt;
We have set aside a budget for community events in 2022:&lt;br /&gt;
&lt;br /&gt;
* Supporting community building events is distinct from the development focused code-sprints below&lt;br /&gt;
* We are inviting community members to contact us about events (rather than try and adjust their event to fit into our code sprint guidelines)&lt;br /&gt;
* OSGeo is is focused on our outreach goals as an organization as such our primary contribution to events is free software and enthusiasm rather than finical, we use funding to enable our members rather than for sponsorship and visibility.&lt;br /&gt;
* Please note our [https://github.com/OSGeo/osgeo/blob/master/board/documents/osgeo_financial_guidance.pdf financial guidance document]&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! Event Request&lt;br /&gt;
! 2022 Approved&lt;br /&gt;
! 2022 Actual&lt;br /&gt;
! 2023 Draft&lt;br /&gt;
! Notes&lt;br /&gt;
|-&lt;br /&gt;
| QGIS Developer Meeting and User Conference &lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Code Sprints ==&lt;br /&gt;
&lt;br /&gt;
We have asked project teams for guidance to help set our code sprint budget:&lt;br /&gt;
&lt;br /&gt;
* Please note our [https://github.com/OSGeo/osgeo/blob/master/board/documents/osgeo_financial_guidance.pdf financial guidance document] ask for event details, budget and fundraising on your part.&lt;br /&gt;
* Out priority is to share the risk with organizers allowing access to funds early to book facilities as required&lt;br /&gt;
* Code sprint budget is structured carry funds from one event to the next allowing us to hold more code-sprints with a smaller annual budget.&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! Sprint Request&lt;br /&gt;
! 2022 Approved&lt;br /&gt;
! 2022 Actual&lt;br /&gt;
! 2023 Draft&lt;br /&gt;
! Notes&lt;br /&gt;
|-&lt;br /&gt;
| OSGeo Code Sprint&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 15,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| No financial request made, seed and sponsorship money exists from previous years.&lt;br /&gt;
|-&lt;br /&gt;
| GeoServer Code Sprint&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| PostGIS Code Sprint &lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GRASS GIS Community Sprint &lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
= Approval and Amendments =&lt;br /&gt;
&lt;br /&gt;
* Budget Meeting:  [[Board_Meeting_2023-01-30]]&lt;br /&gt;
* Loomio Motion: TBD&lt;br /&gt;
* Amendments: TBD&lt;br /&gt;
&lt;br /&gt;
[[Category:Budget]]&lt;br /&gt;
[[Category:Finance]]&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=GvSIG_Budget_2023&amp;diff=129709</id>
		<title>GvSIG Budget 2023</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=GvSIG_Budget_2023&amp;diff=129709"/>
		<updated>2022-12-29T12:22:01Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: gvSIG 2023 budget&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The gvSIG project requests to OSGeo a total budget of 5000 USD for the 2023.&lt;br /&gt;
&lt;br /&gt;
It has covered:&lt;br /&gt;
&lt;br /&gt;
    Organization and webinar platform of 19th International gvSIG Conference: 1,000 USD&lt;br /&gt;
    Preparation of free online courses: 500 USD&lt;br /&gt;
    gvSIG bug fixing: 3,500 USD&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=GvSIG_Budget_2022&amp;diff=127872</id>
		<title>GvSIG Budget 2022</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=GvSIG_Budget_2022&amp;diff=127872"/>
		<updated>2022-02-07T08:11:29Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: Update gvSIG budget 2022&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The gvSIG project requests to OSGeo a total budget of 5000 USD for the 2022.&lt;br /&gt;
&lt;br /&gt;
It has covered:&lt;br /&gt;
&lt;br /&gt;
    Organization and webinar platform of 18th International gvSIG Conference: 1,000 USD&lt;br /&gt;
    Preparation of free online courses: 500 USD&lt;br /&gt;
    gvSIG bug fixing: 3,500 USD&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=OSGeo_Budget_2022&amp;diff=127705</id>
		<title>OSGeo Budget 2022</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=OSGeo_Budget_2022&amp;diff=127705"/>
		<updated>2022-01-10T12:50:46Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: Adding gvSIG budget&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Draft budget for 2022, see [[OSGeo Budget 2021]] and [[Finance Committee#Documents]] for prior years.&lt;br /&gt;
&lt;br /&gt;
Total Approved Budget for 2022: $126,700 USD&lt;br /&gt;
&lt;br /&gt;
Total spending for 2021: TBD&lt;br /&gt;
&lt;br /&gt;
Total Approved Budget for 2022: TBD&lt;br /&gt;
&lt;br /&gt;
== OSGeo Board ==&lt;br /&gt;
&lt;br /&gt;
OSGeo board operates according to our bylaws providing vision and direction for our foundation. The board has also taken on responsibility setting for an annual budget, building partner relationships, sponsorship program and code sprints.&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! Board&lt;br /&gt;
! 2021 Approved&lt;br /&gt;
! 2021 Actual&lt;br /&gt;
! 2022 Approved&lt;br /&gt;
! Notes&lt;br /&gt;
|- &lt;br /&gt;
| Admin&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 4,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| Operational expenses including liability insurance, tax filing fees, quickbooks, mail, IRS, bank fees.&lt;br /&gt;
|-&lt;br /&gt;
| Travel&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 10,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| Travel to main FOSS4G, F2F meeting and regional/representative events&lt;br /&gt;
|-&lt;br /&gt;
| Partners and Sponsors&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| Relationship building, attending b2b functions, foss4g/foss4ge/foss4gna/foss4g-asia breakfast meetings. Meetings with sponsors during events&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Total Board Budget for 2020: $16,000 USD&lt;br /&gt;
&lt;br /&gt;
Total Board spending for 2020: TBD&lt;br /&gt;
&lt;br /&gt;
Total Board Budget for 2021: TBD&lt;br /&gt;
&lt;br /&gt;
== OSGeo Committees ==&lt;br /&gt;
&lt;br /&gt;
The following committees have been formed to fulfill out goals as an organization, each committee is provided a mandate, with the chair of the committee represented as an officer of our organization.&lt;br /&gt;
&lt;br /&gt;
* Code of Conduct Committee&lt;br /&gt;
* Conference Committee&lt;br /&gt;
* GeoForAll - committee acting as advisory board for the GeoForAll Initiative &lt;br /&gt;
* Incubation Committee - committee providing hands-on support for project teams adopting open source principles and practice.&lt;br /&gt;
* Marketing Committee - outreach and advocacy support&lt;br /&gt;
* Open GeoScience Committee&lt;br /&gt;
* System Administration Committee - foundation infrastructure &lt;br /&gt;
* UN Committee - committee responsible for our participation in the UN Open GIS program&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! OSGeo Committees&lt;br /&gt;
! 2021 Approved [Requested]&lt;br /&gt;
! 2021 Actual&lt;br /&gt;
! 2022 Approved [Requested]&lt;br /&gt;
! Notes&lt;br /&gt;
|- &lt;br /&gt;
| SAC&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 30,700 &amp;lt;br/&amp;gt; [35,100]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| Open GeoScience&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,500 &amp;lt;br/&amp;gt; [5,000]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| Conference&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| Marketing&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 10,000 &amp;lt;br/&amp;gt; [15,000]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| GeoForAll&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 3,000 &amp;lt;br/&amp;gt; [3,140]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| UN Committee&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 6,000 &amp;lt;br/&amp;gt; [9,000]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD &lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| Incubation Committee&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 5,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Total Committees Budget for 2021: $57,200 USD&lt;br /&gt;
&lt;br /&gt;
Total Committees spending for 2021: TBD&lt;br /&gt;
&lt;br /&gt;
Total Committees Budget for 2022: TBD&lt;br /&gt;
&lt;br /&gt;
== OSGeo Initiatives ==&lt;br /&gt;
&lt;br /&gt;
OSGeo initiatives have formed to pursue a specific short term, or long term goal. Initiatives maybe formed by a committee or the board as required. Initiatives are a great way to collaborate with projects, committees and partners.&lt;br /&gt;
&lt;br /&gt;
* FOSS4G - event series produced in collaboration with the conference committee and local chapters&lt;br /&gt;
* GeoForAll - education and research program produced in collaboration with our partners&lt;br /&gt;
* Incubation - mentor program for open source projects to be recognized as OSGeo project&lt;br /&gt;
* Local Chapters - board outreach initiative establishing regional OSGeo groups for direct grassroots advoacacy&lt;br /&gt;
* GSoC - coordinate participation in google-summer-of-code and code-in activities&lt;br /&gt;
* Travel Grant Program - provides assistance for attending OSGeo events&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! OSGeo Initiatives&lt;br /&gt;
! 2021 Approved&lt;br /&gt;
! 2021 Actual&lt;br /&gt;
! 2022 Approved&lt;br /&gt;
! Notes&lt;br /&gt;
|- &lt;br /&gt;
| FOSS4G&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| Managed by Conference Committee. Seed money for 2022 will be allocated by the board when estimate numbers become available.&lt;br /&gt;
|-&lt;br /&gt;
| Local Chapters&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| Managed by board, considering putting aside money to help establish local chapters (for logistics, legal advise, kickoff meetings rather than any sponsorship or direct funding)&lt;br /&gt;
|-&lt;br /&gt;
| GSoC&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| Managed by board.&lt;br /&gt;
|-&lt;br /&gt;
| Travel Grant Program &lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 5,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| Managed by Conference Committee. TGP, 50-60% for global event, rest for regional events. LOC's are expected to raise matching funding from sponsors or delegates and provide free conference passes. &amp;lt;br/&amp;gt; Board note: gvSIG can apply for Travel grant here for their event.&lt;br /&gt;
|-&lt;br /&gt;
| Events and Code Sprints&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 15,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| Managed by the board. Funding to help organize OSGeo Code Sprint and other events (e.g. QGIS User Conference, PostGIS Code Sprint, GRASS GIS Community Sprint etc.) &amp;lt;br/&amp;gt; Board note: This budget reflects the 15,000 sponsorship we got for the postponed Athens Code Sprint.&lt;br /&gt;
|-&lt;br /&gt;
| Community Projects&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 5,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| Managed by the board since community projects do not have an assigned officer to handle their budget. We have around 23-25 projects expected in 2021 (see list below). &amp;lt;br/&amp;gt; Board note: Budgeted approx. 300$ for each project. To be amended if we hit the ceiling of the budget. &lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Total Initiatives Budget for 2021: $27,000 USD&lt;br /&gt;
&lt;br /&gt;
Total Initiatives spending for 2021: TBD&lt;br /&gt;
&lt;br /&gt;
Total Initiatives Budget for 2022: TBD&lt;br /&gt;
&lt;br /&gt;
= Projects =&lt;br /&gt;
&lt;br /&gt;
==  OSGeo Projects ==&lt;br /&gt;
&lt;br /&gt;
OSGeo Projects each have a project steering committee, the chair of which is acknowledged as a foundation officer with spending authority on behalf of their committee.&lt;br /&gt;
&lt;br /&gt;
Notes:&lt;br /&gt;
&lt;br /&gt;
* We have reached out (2021) to the projects mailing list with a default suggestion of 2000 for any project that responds&lt;br /&gt;
* Projects with a plan may of course ask for increased funding&lt;br /&gt;
* This is a budget, representing planned spending in 2022 - actual balance available to each PSC (from fundraising, donations and sponsorship) may be considered when planning.&lt;br /&gt;
* If a project did not respond (or runs into an unforeseen expense) please contact the board throughout the year as budgets can be amended&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! OSGeo Project&lt;br /&gt;
! 2021 Approved [Requested]&lt;br /&gt;
! 2021 Actual&lt;br /&gt;
! 2022 Approved [Requested]&lt;br /&gt;
! Notes&lt;br /&gt;
|- &lt;br /&gt;
| deegree&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GDAL/OGR&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GeoMOOSE&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | [2,500]&lt;br /&gt;
| https://github.com/geomoose/geomoose/wiki/PSC-Meeting-2021-10-15&lt;br /&gt;
|-&lt;br /&gt;
| GeoNetwork&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000 &amp;lt;br/&amp;gt; [2,500]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| GeoNode&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GEOS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GeoServer&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000 &amp;lt;br/&amp;gt; [3,000]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| [[GeoServer Budget 2022]]&lt;br /&gt;
|-&lt;br /&gt;
| GeoTools&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000 &amp;lt;br/&amp;gt; [5,000]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| GRASS GIS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000 &amp;lt;br/&amp;gt; [2,500]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| gvSIG&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000 &amp;lt;br/&amp;gt; [4,000]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | [5,000]&lt;br /&gt;
| [[GvSIG Budget 2022]]&lt;br /&gt;
|-&lt;br /&gt;
| Mapbender&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| MapServer&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
|  &lt;br /&gt;
|-&lt;br /&gt;
| Marble&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| OpenLayers&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000 &amp;lt;br/&amp;gt; [3,000]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | [3,000]&lt;br /&gt;
| [[OpenLayers Budget 2022]]&lt;br /&gt;
|-&lt;br /&gt;
| OTB&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| OSGeoLive&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| PostGIS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| PROJ&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| pycsw&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 1,950&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| https://github.com/geopython/pycsw/wiki/OSGeo-Budget-2022&lt;br /&gt;
|-&lt;br /&gt;
| PyWPS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| QGIS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 3,000 &amp;lt;br/&amp;gt; [10,000]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD &lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | [5,000]&lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Total Projects Budget for 2021: $26,500 USD&lt;br /&gt;
&lt;br /&gt;
Total Projects spending for 2022: TBD&lt;br /&gt;
&lt;br /&gt;
Total Projects Budget for 2022: TBD&lt;br /&gt;
&lt;br /&gt;
==  Community Projects ==&lt;br /&gt;
&lt;br /&gt;
Community projects act through the board as they do not have a project officer. Board approved $300 for each project (see Community Projects Initiative above)&lt;br /&gt;
&lt;br /&gt;
Some guidance is offered by individual projects below.&lt;br /&gt;
&lt;br /&gt;
Please note that this table records budget requests, not approved budgets. Community Projects can ask the Board for spending approval (since they do not have a Project Officer) from the approved Community Projects budget. Projects that are also in incubation can ask the Incubation Committee for spending approval from the Incubation Committee approved budget. See notes column for actual budget approval per project.&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! Community Project&lt;br /&gt;
! 2021 Approved [Requested]&lt;br /&gt;
! 2021 Actual&lt;br /&gt;
! 2022 Approved [Requested]&lt;br /&gt;
! Notes&lt;br /&gt;
|-&lt;br /&gt;
| pgRouting&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 300 &amp;lt;br/&amp;gt; [4,500]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD &lt;br /&gt;
| ([https://wiki.osgeo.org/wiki/PgRouting_Budget#2021 link]) 2021 Board note: 300 USD approved from Community Projects budget. For more budget the project has to ask incubation committee.&lt;br /&gt;
|-&lt;br /&gt;
| istSOS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 300 &amp;lt;br/&amp;gt; [4,500]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD &lt;br /&gt;
| ([https://wiki.osgeo.org/wiki/Istsos_Budget_2021 link]) 2021 Board note: 300 USD approved from Community Projects budget. For more budget the project has to ask incubation committee.&lt;br /&gt;
|-&lt;br /&gt;
| pygeoapi&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 300&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 132&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| https://github.com/geopython/pygeoapi/wiki/OSGeo-Budget-2022&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
= Events =&lt;br /&gt;
&lt;br /&gt;
== Community Events ==&lt;br /&gt;
&lt;br /&gt;
We have set aside a budget for community events in 2021:&lt;br /&gt;
&lt;br /&gt;
* Supporting community building events is distinct from the development focused code-sprints below&lt;br /&gt;
* We are inviting community members to contact us about events (rather than try and adjust their event to fit into our code sprint guidelines)&lt;br /&gt;
* OSGeo is is focused on our outreach goals as an organization as such our primary contribution to events is free software and enthusiasm rather than finical, we use funding to enable our members rather than for sponsorship and visibility.&lt;br /&gt;
* Please note our [https://github.com/OSGeo/osgeo/blob/master/board/documents/osgeo_financial_guidance.pdf financial guidance document]&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! Event Request&lt;br /&gt;
! 2021 Approved&lt;br /&gt;
! 2021 Actual&lt;br /&gt;
! 2022 Approved&lt;br /&gt;
! Notes&lt;br /&gt;
|-&lt;br /&gt;
| QGIS Developer Meeting and User Conference &lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Code Sprints ==&lt;br /&gt;
&lt;br /&gt;
We have asked project teams for guidance to help set our code sprint budget:&lt;br /&gt;
&lt;br /&gt;
* Please note our [https://github.com/OSGeo/osgeo/blob/master/board/documents/osgeo_financial_guidance.pdf financial guidance document] ask for event details, budget and fundraising on your part.&lt;br /&gt;
* Out priority is to share the risk with organizers allowing access to funds early to book facilities as required&lt;br /&gt;
* Code sprint budget is structured carry funds from one event to the next allowing us to hold more code-sprints with a smaller annual budget.&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! Sprint Request&lt;br /&gt;
! 2020&lt;br /&gt;
! 2020 Actual&lt;br /&gt;
! 2021 Approved&lt;br /&gt;
! Notes&lt;br /&gt;
|-&lt;br /&gt;
| OSGeo Code Sprint&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 15,000&lt;br /&gt;
| No financial request made, seed and sponsorship money exists from previous years. [[OSGeo Code Sprint 2021|Event planning]] is under way.&lt;br /&gt;
|-&lt;br /&gt;
| GeoServer Code Sprint&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| PostGIS Code Sprint &lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GRASS GIS Community Sprint &lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
= Approval and Amendments =&lt;br /&gt;
&lt;br /&gt;
* Budget Meeting:  [[Board Meeting 2021-01-31]]&lt;br /&gt;
* Loomio Motion: TBD&lt;br /&gt;
* Amendments: TBD&lt;br /&gt;
&lt;br /&gt;
[[Category:Budget]]&lt;br /&gt;
[[Category:Finance]]&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=GvSIG_Budget_2022&amp;diff=127631</id>
		<title>GvSIG Budget 2022</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=GvSIG_Budget_2022&amp;diff=127631"/>
		<updated>2021-12-30T11:50:14Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: gvSIG Budget 2022&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The gvSIG project requests to OSGeo a total budget of 5000 USD for the 2022.&lt;br /&gt;
&lt;br /&gt;
It has covered:&lt;br /&gt;
&lt;br /&gt;
    Organization and webinar platform of 18th International gvSIG Conference: 1,000 USD&lt;br /&gt;
    Preparation of free online courses: 500 USD&lt;br /&gt;
    gvSIG bug fixing: 2,500 USD&lt;br /&gt;
    Remaining items 2021: 1,000 USD&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=GvSIG_Budget_2021&amp;diff=127550</id>
		<title>GvSIG Budget 2021</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=GvSIG_Budget_2021&amp;diff=127550"/>
		<updated>2021-12-07T11:20:26Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: Update gvSIG budget 2021&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The gvSIG project requests to OSGeo a total budget of 3000 USD for the 2021.&lt;br /&gt;
&lt;br /&gt;
It has covered:&lt;br /&gt;
&lt;br /&gt;
* Organization and webinar platform of 17th International gvSIG Conference: 1,200 USD&lt;br /&gt;
* Preparation of free online courses: 500 USD&lt;br /&gt;
* gvSIG 2.6.0 bug fixing: 1,300 USD &lt;br /&gt;
&lt;br /&gt;
[[Category:Budget]]&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=OSGeo_Budget_2021&amp;diff=126066</id>
		<title>OSGeo Budget 2021</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=OSGeo_Budget_2021&amp;diff=126066"/>
		<updated>2021-01-14T09:23:30Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Draft budget for 2021, see [[OSGeo Budget 2020]] and [[Finance Committee#Documents]] for prior years.&lt;br /&gt;
&lt;br /&gt;
Total Approved Budget for 2020: $220,612 USD&lt;br /&gt;
&lt;br /&gt;
Total Approved Budget for 2021: TBD&lt;br /&gt;
&lt;br /&gt;
== OSGeo Board ==&lt;br /&gt;
&lt;br /&gt;
OSGeo board operates according to our bylaws providing vision and direction for our foundation. The board has also taken on responsibility setting for an annual budget, building partner relationships, sponsorship program and code sprints.&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! Board&lt;br /&gt;
! 2020&lt;br /&gt;
! 2020 Actual&lt;br /&gt;
! 2021 Draft&lt;br /&gt;
! Notes&lt;br /&gt;
|- &lt;br /&gt;
| Admin&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Operational expenses including liability insurance, tax filing fees, quickbooks, mail, IRS, bank fees.&lt;br /&gt;
|-&lt;br /&gt;
| Travel&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 20,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Travel to main FOSS4G, F2F meeting and regional/representative events&lt;br /&gt;
|-&lt;br /&gt;
| Partners and Sponsors&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Relationship building, attending b2b functions, foss4g/foss4ge/foss4gna/foss4g-asia breakfast meetings. Meetings with sponsors during events&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Total Board Budget for 2020: $24,000 USD&lt;br /&gt;
&lt;br /&gt;
Total Board Budget for 2021: TBD&lt;br /&gt;
&lt;br /&gt;
== OSGeo Committees ==&lt;br /&gt;
&lt;br /&gt;
The following committees have been formed to fulfill out goals as an organization, each committee is provided a mandate, with the chair of the committee represented as an officer of our organization.&lt;br /&gt;
&lt;br /&gt;
* Code of Conduct Committee&lt;br /&gt;
* Conference Committee&lt;br /&gt;
* GeoForAll - committee acting as advisory board for the GeoForAll Initiative &lt;br /&gt;
* Incubation Committee - committee providing hands-on support for project teams adopting open source principles and practice.&lt;br /&gt;
* Marketing Committee - outreach and advocacy support&lt;br /&gt;
* Open GeoScience Committee&lt;br /&gt;
* System Administration Committee - foundation infrastructure &lt;br /&gt;
* UN Committee - committee responsible for our participation in the UN Open GIS program&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! OSGeo Committees&lt;br /&gt;
! 2020&lt;br /&gt;
! 2020 Actual&lt;br /&gt;
! 2021 Requested&lt;br /&gt;
! Notes&lt;br /&gt;
|- &lt;br /&gt;
| SAC&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 28,350&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| Open GeoScience&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 7,562&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| Conference&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 1,000 &amp;lt;br/&amp;gt; [0]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| Marketing&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 22,000 &amp;lt;br/&amp;gt; [23,800]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GeoForAll&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 5,000 &amp;lt;br/&amp;gt; [8,000]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| UN Committee&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 6,000 &amp;lt;br/&amp;gt; [9,000]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0 &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| Incubation Committee&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 10,000 &amp;lt;br/&amp;gt; [12,000]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| No operational budget requested, funds requested strictly to be used to support team/mentor activities towards completing OSGeo incubation requirements.&amp;lt;br/&amp;gt; Board note: Projects under incubation have to ask the Incubation committee for the part of their budget regarding incubation activities.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Total Committees Budget for 2020: $79,912 USD&lt;br /&gt;
&lt;br /&gt;
Total Committees Budget for 2021: TBD&lt;br /&gt;
&lt;br /&gt;
== OSGeo Initiatives ==&lt;br /&gt;
&lt;br /&gt;
OSGeo initiatives have formed to pursue a specific short term, or long term goal. Initiatives maybe formed by a committee or the board as required. Initiatives are a great way to collaborate with projects, committees and partners.&lt;br /&gt;
&lt;br /&gt;
* FOSS4G - event series produced in collaboration with the conference committee and local chapters&lt;br /&gt;
* GeoForAll - education and research program produced in collaboration with our partners&lt;br /&gt;
* Incubation - mentor program for open source projects to be recognized as OSGeo project&lt;br /&gt;
* Local Chapters - board outreach initiative establishing regional OSGeo groups for direct grassroots advoacacy&lt;br /&gt;
* GSoC - coordinate participation in google-summer-of-code and code-in activities&lt;br /&gt;
* Travel Grant Program - provides assistance for attending OSGeo events&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! OSGeo Initiatives&lt;br /&gt;
! 2020&lt;br /&gt;
! 2020 Actual&lt;br /&gt;
! 2021 Requested&lt;br /&gt;
! Notes&lt;br /&gt;
|- &lt;br /&gt;
| FOSS4G&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Managed by Conference Committee. Seed money for 2021 will be allocated by the board when estimate numbers become available.&lt;br /&gt;
|-&lt;br /&gt;
| Local Chapters&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 5,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Managed by board, considering putting aside money to help establish local chapters (for logistics, legal advise, kickoff meetings rather than any sponsorship or direct funding)&lt;br /&gt;
|-&lt;br /&gt;
| GSoC&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Managed by board.&lt;br /&gt;
|-&lt;br /&gt;
| Travel Grant Program &lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 25,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Managed by Conference Committee. TGP, 50-60% for global event, rest for regional events. LOC's are expected to raise matching funding from sponsors or delegates and provide free conference passes. &amp;lt;br/&amp;gt; Board note: gvSIG can apply for Travel grant here for their event.&lt;br /&gt;
|-&lt;br /&gt;
| Events and Code Sprints&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 15,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Managed by the board. Funding to help organize OSGeo Code Sprint and other events (e.g. QGIS User Conference, PostGIS Code Sprint, GRASS GIS Community Sprint etc.) &amp;lt;br/&amp;gt; Board note: List of requested funding on approval inlcudes siglibre + foss4g belgium + gvSIG + GRASS + QGIS + UN events. Others are welcome to ask for funding from this category.&lt;br /&gt;
|-&lt;br /&gt;
| Community Projects&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 10,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Managed by the board since community projects do not have an assigned officer to handle their budget. We have around 23-25 projects expected in 2021 (see list below). &amp;lt;br/&amp;gt; Board note: Budgeted approx. 500$ for each project. To be amended if we hit the ceiling of the budget. &lt;br /&gt;
|-&lt;br /&gt;
| OSGeo4W&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 4,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Board note: Joint initiative with QGIS.org. Project advised to build a broader volunteer base. Incubation program can be of help in this regard.&lt;br /&gt;
|-&lt;br /&gt;
| GRASS website&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 6,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Money that were to be invoiced in 2019 but need to be invoiced in 2020. This is not a roll over of project budget, just an accounting request.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Total Initiatives Budget for 2020: $65,000 USD&lt;br /&gt;
&lt;br /&gt;
Total Initiatives Budget for 2021: TBD&lt;br /&gt;
&lt;br /&gt;
= Projects =&lt;br /&gt;
&lt;br /&gt;
==  OSGeo Projects ==&lt;br /&gt;
&lt;br /&gt;
OSGeo Projects each have a project steering committee, the chair of which is acknowledged as a foundation officer with spending authority on behalf of their committee.&lt;br /&gt;
&lt;br /&gt;
Notes:&lt;br /&gt;
&lt;br /&gt;
* We have reached out (2020) to the projects mailing list with a default suggestion of 2000 for any project that responds&lt;br /&gt;
* Projects with a plan may of course ask for increased funding&lt;br /&gt;
* This is a budget, representing planned spending in 2021 - actual balance available to each PSC (from fundraising, donations and sponsorship) may be considered when planning.&lt;br /&gt;
* If a project did not respond (or runs into an unforeseen expense) please contact the board throughout the year as budgets can be amended&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! OSGeo Project&lt;br /&gt;
! 2020&lt;br /&gt;
! 2020 Actual&lt;br /&gt;
! 2021 Requested&lt;br /&gt;
! Notes&lt;br /&gt;
|- &lt;br /&gt;
| deegree&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GDAL/OGR&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GeoMOOSE&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GeoNetwork&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GeoNode&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GEOS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GeoServer&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 5,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 5,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 3,000&lt;br /&gt;
| [[GeoServer Budget 2021]]&lt;br /&gt;
|-&lt;br /&gt;
| GeoTools&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 5,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GRASS GIS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 3,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,500&lt;br /&gt;
| [[GRASS GIS Budget 2021]]&lt;br /&gt;
|-&lt;br /&gt;
| gvSIG&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 4,000&lt;br /&gt;
| Details of the budget at [[GvSIG Budget 2021]]&lt;br /&gt;
|-&lt;br /&gt;
| Mapbender&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| MapServer&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
|  &lt;br /&gt;
|-&lt;br /&gt;
| Marble&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| OpenLayers&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 3,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 3,000&lt;br /&gt;
| [[OpenLayers Budget 2021]]&lt;br /&gt;
|-&lt;br /&gt;
| OTB&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| OSGeoLive&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| PostGIS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| PROJ&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 1,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| pycsw&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 3,200&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0 [[Pycsw_budget_2020|(link)]]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| PyWPS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| QGIS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 5,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0 &lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Total Projects Budget for 2020: $51,700 USD&lt;br /&gt;
&lt;br /&gt;
Total Projects Budget for 2021: TBD&lt;br /&gt;
&lt;br /&gt;
==  Community Projects ==&lt;br /&gt;
&lt;br /&gt;
Community projects act through the board as they do not have a project officer. Board approved $TBD for each project (see Community Projects Initiative above)&lt;br /&gt;
&lt;br /&gt;
* actinia&lt;br /&gt;
* FDO&lt;br /&gt;
* GC2/Vidi&lt;br /&gt;
* GeoExt&lt;br /&gt;
* GeoHealthCheck&lt;br /&gt;
* Geomajas&lt;br /&gt;
* GeoServer Client PHP&lt;br /&gt;
* GeoWebCache&lt;br /&gt;
* istSOS&lt;br /&gt;
* Loader&lt;br /&gt;
* MapGuide Open Source&lt;br /&gt;
* Mapfish&lt;br /&gt;
* Opticks&lt;br /&gt;
* OSGeo4W&lt;br /&gt;
* OSSIM&lt;br /&gt;
* OWSLib&lt;br /&gt;
* pgRouting&lt;br /&gt;
* PortableGIS&lt;br /&gt;
* Pronto Raster&lt;br /&gt;
* pygeoapi&lt;br /&gt;
* rasdaman&lt;br /&gt;
* TEAM Engine&lt;br /&gt;
* ZOO-Project&lt;br /&gt;
&lt;br /&gt;
Some incubation projects are not yet set up as part of OSGeo community:&lt;br /&gt;
&lt;br /&gt;
* Oskari&lt;br /&gt;
&lt;br /&gt;
Some guidance is offered by individual projects below.&lt;br /&gt;
&lt;br /&gt;
Please note that this table records budget requests, not approved budgets. Community Projects can ask the Board for spending approval (since they do not have a Project Officer) from the approved Community Projects budget. Projects that are also in incubation can ask the Incubation Committee for spending approval from the Incubation Committee approved budget. See notes column for actual budget approval per project.&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! Community Project&lt;br /&gt;
! 2020&lt;br /&gt;
! 2020 Actual&lt;br /&gt;
! 2021 Requested&lt;br /&gt;
! Notes&lt;br /&gt;
|- &lt;br /&gt;
| ZOO-Project&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot;| 1,250 + 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| 2020 Board note: 1,250 USD approved as part of the Incubation Committee budget. 500 USD approved from Community Projects budget. For more budget the project has to complete incubation or/and send a specific request to the board to cover from the Community Projects budget.&lt;br /&gt;
|-&lt;br /&gt;
| pgRouting&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot;| 4,000 + 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| 2020 Board note: 4,000 USD approved as part of the Incubation Committee budget. Project has to be in incubation to ask for the budget. 500 USD approved from Community Projects budget.&lt;br /&gt;
|-&lt;br /&gt;
| istSOS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 4,000 + 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| OSGeo4W&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 4,000 + 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| pygeoapi&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 322 ([https://github.com/geopython/pygeoapi/wiki/OSGeo-Budget-2020 link])&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GeoHealthCheck&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| OWSLib&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
= Events =&lt;br /&gt;
&lt;br /&gt;
== Community Events ==&lt;br /&gt;
&lt;br /&gt;
We have set aside a budget for community events in 2021:&lt;br /&gt;
&lt;br /&gt;
* Supporting community building events is distinct from the development focused code-sprints below&lt;br /&gt;
* We are inviting community members to contact us about events (rather than try and adjust their event to fit into our code sprint guidelines)&lt;br /&gt;
* OSGeo is is focused on our outreach goals as an organization as such our primary contribution to events is free software and enthusiasm rather than finical, we use funding to enable our members rather than for sponsorship and visibility.&lt;br /&gt;
* Please note our [https://github.com/OSGeo/osgeo/blob/master/board/documents/osgeo_financial_guidance.pdf financial guidance document]&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! Event Request&lt;br /&gt;
! 2020&lt;br /&gt;
! 2020 Actual&lt;br /&gt;
! 2021 Requested&lt;br /&gt;
! Notes&lt;br /&gt;
|-&lt;br /&gt;
| QGIS Developer Meeting and User Conference &lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 3,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| FOSS4G SotM Oceania Community Day &lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 1500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Code Sprints ==&lt;br /&gt;
&lt;br /&gt;
We have asked project teams for guidance to help set our code sprint budget:&lt;br /&gt;
&lt;br /&gt;
* Please note our [https://github.com/OSGeo/osgeo/blob/master/board/documents/osgeo_financial_guidance.pdf financial guidance document] ask for event details, budget and fundraising on your part.&lt;br /&gt;
* Out priority is to share the risk with organizers allowing access to funds early to book facilities as required&lt;br /&gt;
* Code sprint budget is structured carry funds from one event to the next allowing us to hold more code-sprints with a smaller annual budget.&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! Sprint Request&lt;br /&gt;
! 2020&lt;br /&gt;
! 2020 Actual&lt;br /&gt;
! 2021 Requested&lt;br /&gt;
! Notes&lt;br /&gt;
|-&lt;br /&gt;
| OSGeo Code Sprint&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| No financial request made, seed money exists from previous years. [[OSGeo Code Sprint 2020|Event planning]] is well under way.&lt;br /&gt;
|-&lt;br /&gt;
| GeoServer Code Sprint&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| PostGIS Code Sprint &lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GRASS GIS Community Sprint &lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
= Approval and Amendments =&lt;br /&gt;
&lt;br /&gt;
* Budget Meeting:  [[Board Meeting 2021-01-18]]&lt;br /&gt;
* Loomio Motion: &lt;br /&gt;
* Amendments: TBD&lt;br /&gt;
&lt;br /&gt;
[[Category:Budget]]&lt;br /&gt;
[[Category:Finance]]&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=OSGeo_Budget_2021&amp;diff=126034</id>
		<title>OSGeo Budget 2021</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=OSGeo_Budget_2021&amp;diff=126034"/>
		<updated>2021-01-05T22:06:44Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Draft budget for 2021, see [[OSGeo Budget 2020]] and [[Finance Committee#Documents]] for prior years.&lt;br /&gt;
&lt;br /&gt;
Total Approved Budget for 2020: $220,612 USD&lt;br /&gt;
&lt;br /&gt;
Total Approved Budget for 2021: TBD&lt;br /&gt;
&lt;br /&gt;
== OSGeo Board ==&lt;br /&gt;
&lt;br /&gt;
OSGeo board operates according to our bylaws providing vision and direction for our foundation. The board has also taken on responsibility setting for an annual budget, building partner relationships, sponsorship program and code sprints.&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! Board&lt;br /&gt;
! 2020&lt;br /&gt;
! 2020 Actual&lt;br /&gt;
! 2021 Draft&lt;br /&gt;
! Notes&lt;br /&gt;
|- &lt;br /&gt;
| Admin&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Operational expenses including liability insurance, tax filing fees, quickbooks, mail, IRS, bank fees.&lt;br /&gt;
|-&lt;br /&gt;
| Travel&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 20,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Travel to main FOSS4G, F2F meeting and regional/representative events&lt;br /&gt;
|-&lt;br /&gt;
| Partners and Sponsors&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Relationship building, attending b2b functions, foss4g/foss4ge/foss4gna/foss4g-asia breakfast meetings. Meetings with sponsors during events&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Total Board Budget for 2020: $24,000 USD&lt;br /&gt;
&lt;br /&gt;
Total Board Budget for 2021: TBD&lt;br /&gt;
&lt;br /&gt;
== OSGeo Committees ==&lt;br /&gt;
&lt;br /&gt;
The following committees have been formed to fulfill out goals as an organization, each committee is provided a mandate, with the chair of the committee represented as an officer of our organization.&lt;br /&gt;
&lt;br /&gt;
* Code of Conduct Committee&lt;br /&gt;
* Conference Committee&lt;br /&gt;
* GeoForAll - committee acting as advisory board for the GeoForAll Initiative &lt;br /&gt;
* Incubation Committee - committee providing hands-on support for project teams adopting open source principles and practice.&lt;br /&gt;
* Marketing Committee - outreach and advocacy support&lt;br /&gt;
* Open GeoScience Committee&lt;br /&gt;
* System Administration Committee - foundation infrastructure &lt;br /&gt;
* UN Committee - committee responsible for our participation in the UN Open GIS program&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! OSGeo Committees&lt;br /&gt;
! 2020&lt;br /&gt;
! 2020 Actual&lt;br /&gt;
! 2021 Requested&lt;br /&gt;
! Notes&lt;br /&gt;
|- &lt;br /&gt;
| SAC&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 28,350&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| Open GeoScience&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 7,562&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| Conference&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 1,000 &amp;lt;br/&amp;gt; [0]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| Marketing&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 22,000 &amp;lt;br/&amp;gt; [23,800]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GeoForAll&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 5,000 &amp;lt;br/&amp;gt; [8,000]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| UN Committee&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 6,000 &amp;lt;br/&amp;gt; [9,000]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0 &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| Incubation Committee&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 10,000 &amp;lt;br/&amp;gt; [12,000]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| No operational budget requested, funds requested strictly to be used to support team/mentor activities towards completing OSGeo incubation requirements.&amp;lt;br/&amp;gt; Board note: Projects under incubation have to ask the Incubation committee for the part of their budget regarding incubation activities.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Total Committees Budget for 2020: $79,912 USD&lt;br /&gt;
&lt;br /&gt;
Total Committees Budget for 2021: TBD&lt;br /&gt;
&lt;br /&gt;
== OSGeo Initiatives ==&lt;br /&gt;
&lt;br /&gt;
OSGeo initiatives have formed to pursue a specific short term, or long term goal. Initiatives maybe formed by a committee or the board as required. Initiatives are a great way to collaborate with projects, committees and partners.&lt;br /&gt;
&lt;br /&gt;
* FOSS4G - event series produced in collaboration with the conference committee and local chapters&lt;br /&gt;
* GeoForAll - education and research program produced in collaboration with our partners&lt;br /&gt;
* Incubation - mentor program for open source projects to be recognized as OSGeo project&lt;br /&gt;
* Local Chapters - board outreach initiative establishing regional OSGeo groups for direct grassroots advoacacy&lt;br /&gt;
* GSoC - coordinate participation in google-summer-of-code and code-in activities&lt;br /&gt;
* Travel Grant Program - provides assistance for attending OSGeo events&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! OSGeo Initiatives&lt;br /&gt;
! 2020&lt;br /&gt;
! 2020 Actual&lt;br /&gt;
! 2021 Requested&lt;br /&gt;
! Notes&lt;br /&gt;
|- &lt;br /&gt;
| FOSS4G&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Managed by Conference Committee. Seed money for 2021 will be allocated by the board when estimate numbers become available.&lt;br /&gt;
|-&lt;br /&gt;
| Local Chapters&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 5,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Managed by board, considering putting aside money to help establish local chapters (for logistics, legal advise, kickoff meetings rather than any sponsorship or direct funding)&lt;br /&gt;
|-&lt;br /&gt;
| GSoC&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Managed by board.&lt;br /&gt;
|-&lt;br /&gt;
| Travel Grant Program &lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 25,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Managed by Conference Committee. TGP, 50-60% for global event, rest for regional events. LOC's are expected to raise matching funding from sponsors or delegates and provide free conference passes. &amp;lt;br/&amp;gt; Board note: gvSIG can apply for Travel grant here for their event.&lt;br /&gt;
|-&lt;br /&gt;
| Events and Code Sprints&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 15,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Managed by the board. Funding to help organize OSGeo Code Sprint and other events (e.g. QGIS User Conference, PostGIS Code Sprint, GRASS GIS Community Sprint etc.) &amp;lt;br/&amp;gt; Board note: List of requested funding on approval inlcudes siglibre + foss4g belgium + gvSIG + GRASS + QGIS + UN events. Others are welcome to ask for funding from this category.&lt;br /&gt;
|-&lt;br /&gt;
| Community Projects&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 10,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Managed by the board since community projects do not have an assigned officer to handle their budget. We have around 23-25 projects expected in 2021 (see list below). &amp;lt;br/&amp;gt; Board note: Budgeted approx. 500$ for each project. To be amended if we hit the ceiling of the budget. &lt;br /&gt;
|-&lt;br /&gt;
| OSGeo4W&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 4,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Board note: Joint initiative with QGIS.org. Project advised to build a broader volunteer base. Incubation program can be of help in this regard.&lt;br /&gt;
|-&lt;br /&gt;
| GRASS website&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 6,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Money that were to be invoiced in 2019 but need to be invoiced in 2020. This is not a roll over of project budget, just an accounting request.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Total Initiatives Budget for 2020: $65,000 USD&lt;br /&gt;
&lt;br /&gt;
Total Initiatives Budget for 2021: TBD&lt;br /&gt;
&lt;br /&gt;
= Projects =&lt;br /&gt;
&lt;br /&gt;
==  OSGeo Projects ==&lt;br /&gt;
&lt;br /&gt;
OSGeo Projects each have a project steering committee, the chair of which is acknowledged as a foundation officer with spending authority on behalf of their committee.&lt;br /&gt;
&lt;br /&gt;
Notes:&lt;br /&gt;
&lt;br /&gt;
* We have reached out (2020) to the projects mailing list with a default suggestion of 2000 for any project that responds&lt;br /&gt;
* Projects with a plan may of course ask for increased funding&lt;br /&gt;
* This is a budget, representing planned spending in 2021 - actual balance available to each PSC (from fundraising, donations and sponsorship) may be considered when planning.&lt;br /&gt;
* If a project did not respond (or runs into an unforeseen expense) please contact the board throughout the year as budgets can be amended&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! OSGeo Project&lt;br /&gt;
! 2020&lt;br /&gt;
! 2020 Actual&lt;br /&gt;
! 2021 Requested&lt;br /&gt;
! Notes&lt;br /&gt;
|- &lt;br /&gt;
| deegree&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GDAL/OGR&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GeoMOOSE&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GeoNetwork&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GeoNode&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GEOS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GeoServer&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 5,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 5,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 3,000&lt;br /&gt;
| [[GeoServer Budget 2021]]&lt;br /&gt;
|-&lt;br /&gt;
| GeoTools&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 5,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GRASS GIS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 3,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| gvSIG&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Details of the budget at [[GvSIG Budget 2021]]&lt;br /&gt;
|-&lt;br /&gt;
| Mapbender&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| MapServer&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
|  &lt;br /&gt;
|-&lt;br /&gt;
| Marble&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| OpenLayers&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 3,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| OTB&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| OSGeoLive&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| PostGIS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| PROJ&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 1,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| pycsw&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 3,200&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0 [[Pycsw_budget_2020|(link)]]&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| PyWPS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| QGIS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 5,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0 &lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Total Projects Budget for 2020: $51,700 USD&lt;br /&gt;
&lt;br /&gt;
Total Projects Budget for 2021: TBD&lt;br /&gt;
&lt;br /&gt;
==  Community Projects ==&lt;br /&gt;
&lt;br /&gt;
Community projects act through the board as they do not have a project officer. Board approved $TBD for each project (see Community Projects Initiative above)&lt;br /&gt;
&lt;br /&gt;
* actinia&lt;br /&gt;
* FDO&lt;br /&gt;
* GC2/Vidi&lt;br /&gt;
* GeoExt&lt;br /&gt;
* GeoHealthCheck&lt;br /&gt;
* Geomajas&lt;br /&gt;
* GeoServer Client PHP&lt;br /&gt;
* GeoWebCache&lt;br /&gt;
* istSOS&lt;br /&gt;
* Loader&lt;br /&gt;
* MapGuide Open Source&lt;br /&gt;
* Mapfish&lt;br /&gt;
* Opticks&lt;br /&gt;
* OSGeo4W&lt;br /&gt;
* OSSIM&lt;br /&gt;
* OWSLib&lt;br /&gt;
* pgRouting&lt;br /&gt;
* PortableGIS&lt;br /&gt;
* Pronto Raster&lt;br /&gt;
* pygeoapi&lt;br /&gt;
* rasdaman&lt;br /&gt;
* TEAM Engine&lt;br /&gt;
* ZOO-Project&lt;br /&gt;
&lt;br /&gt;
Some incubation projects are not yet set up as part of OSGeo community:&lt;br /&gt;
&lt;br /&gt;
* Oskari&lt;br /&gt;
&lt;br /&gt;
Some guidance is offered by individual projects below.&lt;br /&gt;
&lt;br /&gt;
Please note that this table records budget requests, not approved budgets. Community Projects can ask the Board for spending approval (since they do not have a Project Officer) from the approved Community Projects budget. Projects that are also in incubation can ask the Incubation Committee for spending approval from the Incubation Committee approved budget. See notes column for actual budget approval per project.&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! Community Project&lt;br /&gt;
! 2020&lt;br /&gt;
! 2020 Actual&lt;br /&gt;
! 2021 Requested&lt;br /&gt;
! Notes&lt;br /&gt;
|- &lt;br /&gt;
| ZOO-Project&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot;| 1,250 + 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| 2020 Board note: 1,250 USD approved as part of the Incubation Committee budget. 500 USD approved from Community Projects budget. For more budget the project has to complete incubation or/and send a specific request to the board to cover from the Community Projects budget.&lt;br /&gt;
|-&lt;br /&gt;
| pgRouting&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot;| 4,000 + 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| 2020 Board note: 4,000 USD approved as part of the Incubation Committee budget. Project has to be in incubation to ask for the budget. 500 USD approved from Community Projects budget.&lt;br /&gt;
|-&lt;br /&gt;
| istSOS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 4,000 + 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| OSGeo4W&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 4,000 + 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| pygeoapi&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 322 ([https://github.com/geopython/pygeoapi/wiki/OSGeo-Budget-2020 link])&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GeoHealthCheck&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| OWSLib&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
= Events =&lt;br /&gt;
&lt;br /&gt;
== Community Events ==&lt;br /&gt;
&lt;br /&gt;
We have set aside a budget for community events in 2021:&lt;br /&gt;
&lt;br /&gt;
* Supporting community building events is distinct from the development focused code-sprints below&lt;br /&gt;
* We are inviting community members to contact us about events (rather than try and adjust their event to fit into our code sprint guidelines)&lt;br /&gt;
* OSGeo is is focused on our outreach goals as an organization as such our primary contribution to events is free software and enthusiasm rather than finical, we use funding to enable our members rather than for sponsorship and visibility.&lt;br /&gt;
* Please note our [https://github.com/OSGeo/osgeo/blob/master/board/documents/osgeo_financial_guidance.pdf financial guidance document]&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! Event Request&lt;br /&gt;
! 2020&lt;br /&gt;
! 2020 Actual&lt;br /&gt;
! 2021 Requested&lt;br /&gt;
! Notes&lt;br /&gt;
|-&lt;br /&gt;
| QGIS Developer Meeting and User Conference &lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 3,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| FOSS4G SotM Oceania Community Day &lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 1500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Code Sprints ==&lt;br /&gt;
&lt;br /&gt;
We have asked project teams for guidance to help set our code sprint budget:&lt;br /&gt;
&lt;br /&gt;
* Please note our [https://github.com/OSGeo/osgeo/blob/master/board/documents/osgeo_financial_guidance.pdf financial guidance document] ask for event details, budget and fundraising on your part.&lt;br /&gt;
* Out priority is to share the risk with organizers allowing access to funds early to book facilities as required&lt;br /&gt;
* Code sprint budget is structured carry funds from one event to the next allowing us to hold more code-sprints with a smaller annual budget.&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! Sprint Request&lt;br /&gt;
! 2020&lt;br /&gt;
! 2020 Actual&lt;br /&gt;
! 2021 Requested&lt;br /&gt;
! Notes&lt;br /&gt;
|-&lt;br /&gt;
| OSGeo Code Sprint&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| No financial request made, seed money exists from previous years. [[OSGeo Code Sprint 2020|Event planning]] is well under way.&lt;br /&gt;
|-&lt;br /&gt;
| GeoServer Code Sprint&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| PostGIS Code Sprint &lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GRASS GIS Community Sprint &lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
= Approval and Amendments =&lt;br /&gt;
&lt;br /&gt;
* Budget Meeting:  [[Board Meeting 2021-01-18]]&lt;br /&gt;
* Loomio Motion: &lt;br /&gt;
* Amendments: TBD&lt;br /&gt;
&lt;br /&gt;
[[Category:Budget]]&lt;br /&gt;
[[Category:Finance]]&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=GvSIG_Budget_2021&amp;diff=126033</id>
		<title>GvSIG Budget 2021</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=GvSIG_Budget_2021&amp;diff=126033"/>
		<updated>2021-01-05T22:03:55Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: gvSIG Budget 2021&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The gvSIG project requests to OSGeo a total budget of 4000 USD for the 2021.&lt;br /&gt;
&lt;br /&gt;
It has covered:&lt;br /&gt;
&lt;br /&gt;
* Organization and webinar platform of 17th International gvSIG Conference and 5th gvSIG Festival: 2,000 USD&lt;br /&gt;
* Preparation of free online courses: 500 USD&lt;br /&gt;
* gvSIG bug fixing: 1,500 USD &lt;br /&gt;
&lt;br /&gt;
[[Category:Budget]]&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=GvSIG_Budget_2020&amp;diff=125941</id>
		<title>GvSIG Budget 2020</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=GvSIG_Budget_2020&amp;diff=125941"/>
		<updated>2020-12-21T15:14:30Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The gvSIG project requests to OSGeo a total budget of 3000 USD for the 2020.&lt;br /&gt;
&lt;br /&gt;
It has covered:&lt;br /&gt;
&lt;br /&gt;
* Organization and webinar platform of 16th International gvSIG Conference: 1,200 USD&lt;br /&gt;
* Preparation of free online courses: 600 USD&lt;br /&gt;
* gvSIG 2.5.1 bug fixing: 1,200 USD &lt;br /&gt;
&lt;br /&gt;
[[Category:Budget]]&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=OSGeo_Budget_2020&amp;diff=122820</id>
		<title>OSGeo Budget 2020</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=OSGeo_Budget_2020&amp;diff=122820"/>
		<updated>2019-12-23T19:04:05Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: Adding gvSIG Budget for 2020&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''DRAFT'''&lt;br /&gt;
&lt;br /&gt;
Draft budget to be discussed in December board meeting, see [[OSGeo Budget 2019]] and [[Finance Committee#Documents]] for prior years.&lt;br /&gt;
&lt;br /&gt;
Total Approved Budget for 2019: $230,150 USD&lt;br /&gt;
&lt;br /&gt;
Total Approved Budget for 2020: $TBD USD&lt;br /&gt;
&lt;br /&gt;
== OSGeo Board ==&lt;br /&gt;
&lt;br /&gt;
OSGeo board operates according to our bylaws providing vision and direction for our foundation. The board has also taken on responsibility setting for an annual budget, building partner relationships, sponsorship program and code sprints.&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! Board&lt;br /&gt;
! 2019&lt;br /&gt;
! 2019 Actual&lt;br /&gt;
! 2020&lt;br /&gt;
! Notes&lt;br /&gt;
|- &lt;br /&gt;
| Admin&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 3,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Operational expenses including liability insurance, tax filing fees, accountant, bank fees.&lt;br /&gt;
|-&lt;br /&gt;
| Travel&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 22,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Travel to main FOSS4G and F2F meeting (15k), and regional/representative events (7k)&lt;br /&gt;
|-&lt;br /&gt;
| Partners&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Relationship building, attending b2b functions, foss4g/foss4ge/foss4gna/foss4g-asia breakfast meetings&lt;br /&gt;
|-&lt;br /&gt;
| Sponsors&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Meetings with sponsors during events&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Total Board Budget for 2019: $29,000 USD&lt;br /&gt;
&lt;br /&gt;
Total Board Budget for 2020: $TBD USD&lt;br /&gt;
&lt;br /&gt;
== OSGeo Committees ==&lt;br /&gt;
&lt;br /&gt;
The following committees have been formed to fulfill out goals as an organization, each committee is provided a mandate, with the chair of the committee represented as an officer of our organization.&lt;br /&gt;
&lt;br /&gt;
* Code of Conduct Committee&lt;br /&gt;
* Conference Committee&lt;br /&gt;
* GeoForAll - committee acting as advisory board for the GeoForAll Initiative &lt;br /&gt;
* Incubation Committee - committee providing hands-on support for project teams adopting open source principles and practice.&lt;br /&gt;
* Marketing Committee - outreach and advocacy support&lt;br /&gt;
* Open GeoScience Committee&lt;br /&gt;
* System Administration Committee - foundation infrastructure &lt;br /&gt;
* UN Committee - committee responsible for our participation in the UN Open GIS program&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! OSGeo Committees&lt;br /&gt;
! 2019&lt;br /&gt;
! 2019 Actual&lt;br /&gt;
! 2020&lt;br /&gt;
! Notes&lt;br /&gt;
|- &lt;br /&gt;
| SAC&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 23,750&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| Open GeoScience&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 6,100&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| Conference&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| Marketing&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 22,600&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GeoForAll&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 3,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| UN Committee&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 11,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 1,051 euro + 6,000 $&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 9,000 &lt;br /&gt;
| Activities of the Committe available at https://wiki.osgeo.org/wiki/UnitedNations_Committee &lt;br /&gt;
Budget 2019: the expenses are less because a Field Mission in South Sudan was cancelled; &lt;br /&gt;
Budget 2020: 2 OSGeo Challenges (6,000) + 3,000 for the Partecipation at the &amp;quot;6th International Symposium on Partnership for Technology in Peacekeeping&amp;quot; 22-26 June 2020)&lt;br /&gt;
|-&lt;br /&gt;
| Incubation Committee&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 10,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Total Committees Budget for 2019: $76,450 USD&lt;br /&gt;
&lt;br /&gt;
Total Committees Budget for 2020: $TBD USD&lt;br /&gt;
&lt;br /&gt;
== OSGeo Initiatives ==&lt;br /&gt;
&lt;br /&gt;
OSGeo initiatives have formed to pursue a specific short term, or long term goal. Initiatives maybe formed by a committee or the board as required. Initiatives are a great way to collaborate with projects, committees and partners.&lt;br /&gt;
&lt;br /&gt;
* FOSS4G - event series produced in collaboration with the conference committee and local chapters&lt;br /&gt;
* GeoForAll - education and research program produced in collaboration with our partners&lt;br /&gt;
* Incubation - mentor program for open source projects to be recognized as OSGeo project&lt;br /&gt;
* Local Chapters - board outreach initiative establishing regional OSGeo groups for direct grassroots advoacacy&lt;br /&gt;
* Meta CRS - interoperability initiative promoting data sharing with cross project spatial reference system compatibility&lt;br /&gt;
* Open GeoScience - outreach and advocacy geoscience community&lt;br /&gt;
* GSoC - coordinate participation in google-summer-of-code and code-in activities&lt;br /&gt;
* Travel Grant Program - provides assistance for attending OSGeo events&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! OSGeo Initiatives&lt;br /&gt;
! 2019&lt;br /&gt;
! 2019 Actual&lt;br /&gt;
! 2020&lt;br /&gt;
! Notes&lt;br /&gt;
|- &lt;br /&gt;
| FOSS4G&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Managed by Conference Committee. Seed money for 2020 will be allocated by the board when estimate numbers become available.&lt;br /&gt;
|-&lt;br /&gt;
| Local Chapters&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 5,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Managed by board, considering putting aside money to help establish local chapters (for logistics, legal advise, kickoff meetings rather than any sponsorship or direct funding)&lt;br /&gt;
|-&lt;br /&gt;
| Travel Grant Program &lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 25.000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| TGP, 50-50% for global event, rest for regional events (Previous years had a component of matching sponsor donations)&lt;br /&gt;
|-&lt;br /&gt;
| Events and Code Sprints&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 15,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Managed by the board. Funding to help organize OSGeo Code Sprint and other events (e.g. QGIS User Conference, PostGIS Code Sprint, GRASS GIS Community Sprint etc.)&lt;br /&gt;
|-&lt;br /&gt;
| Community Projects&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 15,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Managed by the board since community projects do not have an assigned officer to handle their budget. We have around 23-25 projects expected in 2020 (see list bellow). Budgeted 1000$ for each project.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Total Initiatives Budget for 2019: $60,000 USD&lt;br /&gt;
&lt;br /&gt;
Total Initiatives Budget for 2020: $TBD USD&lt;br /&gt;
&lt;br /&gt;
= Projects =&lt;br /&gt;
&lt;br /&gt;
==  OSGeo Projects ==&lt;br /&gt;
&lt;br /&gt;
OSGeo Projects each have a project steering committee, the chair of which is acknowledged as a foundation officer with spending authority on behalf of their committee.&lt;br /&gt;
&lt;br /&gt;
Notes:&lt;br /&gt;
&lt;br /&gt;
* We have reached out (2019) to the projects mailing list with a default suggestion of 2000 for any project that responds&lt;br /&gt;
* Projects with a plan may of course ask for increased funding&lt;br /&gt;
* This is a budget, representing planned spending in 2020 - actual balance available to each PSC (from fundraising, donations and sponsorship) may be considered when planning.&lt;br /&gt;
* If a project did not respond (or runs into an unforeseen expense) please contact the board throughout the year as budgets can be amended&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! OSGeo Project&lt;br /&gt;
! 2019&lt;br /&gt;
! 2019 Actual&lt;br /&gt;
! 2020&lt;br /&gt;
! Notes&lt;br /&gt;
|- &lt;br /&gt;
| deegree&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GDAL/OGR&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 5,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GeoMOOSE&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GeoNetwork&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GeoNode&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GEOS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 1,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GeoServer&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 7,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GeoTools&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GRASS GIS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 9,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| [https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2020 GRASS GIS Budget 2020]&lt;br /&gt;
|-&lt;br /&gt;
| gvSIG&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 5,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Details of the budget at [[GvSIG Budget 2020]]&lt;br /&gt;
|-&lt;br /&gt;
| Mapbender&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| MapServer&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
|  &lt;br /&gt;
|-&lt;br /&gt;
| Marble&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 1,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| OpenLayers&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 3,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| OTB&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| OSGeoLive&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| PostGIS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 3,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| PROJ&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | N/A&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | N/A&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| pycsw&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 3,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| [[Pycsw_budget_2020]]&lt;br /&gt;
|-&lt;br /&gt;
| PyWPS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 3,200&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| QGIS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 8,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Total Projects Budget for 2019: $64,700 USD&lt;br /&gt;
&lt;br /&gt;
Total Projects Budget for 2020: $TBD USD&lt;br /&gt;
&lt;br /&gt;
==  Community Projects ==&lt;br /&gt;
&lt;br /&gt;
Community projects act through the board as they do not have a project officer. Board approved $TBD for each project (see Community Projects Initiative above)&lt;br /&gt;
&lt;br /&gt;
* actinia&lt;br /&gt;
* FDO&lt;br /&gt;
* GC2/Vidi&lt;br /&gt;
* GeoExt&lt;br /&gt;
* GeoHealthCheck&lt;br /&gt;
* Geomajas&lt;br /&gt;
* GeoServer Client PHP&lt;br /&gt;
* GeoWebCache&lt;br /&gt;
* istSOS&lt;br /&gt;
* Loader&lt;br /&gt;
* MapGuide Open Source&lt;br /&gt;
* Mapfish&lt;br /&gt;
* Opticks&lt;br /&gt;
* OSGeo4W&lt;br /&gt;
* OSSIM&lt;br /&gt;
* OWSLib&lt;br /&gt;
* pgRouting&lt;br /&gt;
* PortableGIS&lt;br /&gt;
* Pronto Raster&lt;br /&gt;
* pygeoapi&lt;br /&gt;
* rasdaman&lt;br /&gt;
* TEAM Engine&lt;br /&gt;
* ZOO-Project&lt;br /&gt;
&lt;br /&gt;
Some incubation projects are not yet set up as part of OSGeo community:&lt;br /&gt;
&lt;br /&gt;
* Oskari&lt;br /&gt;
&lt;br /&gt;
Some guidance is offered by individual projects below:&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! Community Project&lt;br /&gt;
! 2019&lt;br /&gt;
! 2019 Actual&lt;br /&gt;
! 2020&lt;br /&gt;
! Notes&lt;br /&gt;
|- &lt;br /&gt;
| ZOO-Project&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot;| up to 4,000 (need specific requests to board and incubation committee)&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| pgRouting&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot;| up to 4,000 (need specific requests to board and incubation committee)&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| istSOS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | up to 4,000 (need specific requests to board and incubation committee)&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Events =&lt;br /&gt;
&lt;br /&gt;
== Community Events ==&lt;br /&gt;
&lt;br /&gt;
We are considering setting aside a budget for community events in 2020:&lt;br /&gt;
&lt;br /&gt;
* Supporting community building events is distinct from the development focused code-sprints below&lt;br /&gt;
* We are inviting community members to contact us about events (rather than try and adjust their event to fit into our code sprint guidelines)&lt;br /&gt;
* OSGeo is is focused on our outreach goals as an organization as such our primary contribution to events is free software and enthusiasm rather than finical, we use funding to enable our members rather than for sponsorship and visibility.&lt;br /&gt;
* Previously we have had requests to fund a &amp;quot;community day&amp;quot; or &amp;quot;community sprints&amp;quot; as part a larger event as distinct from sponsorship, the have been funded to the best of our ability&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! Event Request&lt;br /&gt;
! 2019&lt;br /&gt;
! 2019 Actual&lt;br /&gt;
! 2020&lt;br /&gt;
! Notes&lt;br /&gt;
|-&lt;br /&gt;
| QGIS Developer Meeting and User Conference &lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 3,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
|-&lt;br /&gt;
| FOSS4G SotM Oceania Community Day &lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 1500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 1500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 1500&lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Code Sprints ==&lt;br /&gt;
&lt;br /&gt;
We have asked project teams for guidance to help set our code sprint budget:&lt;br /&gt;
&lt;br /&gt;
* Please note our [[Code Sprint Guidelines]] ask for event details, budget and fundraising on your part.&lt;br /&gt;
* Out priority is to share the risk with organizers allowing access to funds early to book facilities as required&lt;br /&gt;
* Code sprint budget is structured carry funds from one event to the next allowing us to hold more code-sprints with a smaller annual budget.&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! Sprint Request&lt;br /&gt;
! 2019&lt;br /&gt;
! 2019 Actual&lt;br /&gt;
! 2020&lt;br /&gt;
! Notes&lt;br /&gt;
|-&lt;br /&gt;
| OSGeo Code Sprint&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | &lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| No financial request made yet, [[OSGeo Code Sprint 2020|event planning]] is well under way.&lt;br /&gt;
|-&lt;br /&gt;
| GeoServer Code Sprint&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| PostGIS Code Sprint &lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | -&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GRASS GIS Community Sprint &lt;br /&gt;
|  style=&amp;quot;text-align:right;&amp;quot; | -&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| Small Code Sprints&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 10,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Approval and Amendments =&lt;br /&gt;
&lt;br /&gt;
* Budget Meeting:  [[Board Meeting 2019-01-21]]&lt;br /&gt;
* Loomio Motion: [https://www.loomio.org/d/xmEyfoPn/osgeo-budget-2019]&lt;br /&gt;
* Amendments: TBD&lt;br /&gt;
&lt;br /&gt;
[[Category:Budget]]&lt;br /&gt;
[[Category:Finance]]&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=GvSIG_Budget_2020&amp;diff=122819</id>
		<title>GvSIG Budget 2020</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=GvSIG_Budget_2020&amp;diff=122819"/>
		<updated>2019-12-23T19:01:23Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: gvSIG Budget for 2020&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The gvSIG project requests to OSGeo a total budget of 5000 USD for the 2020.&lt;br /&gt;
&lt;br /&gt;
This is intended to cover:&lt;br /&gt;
&lt;br /&gt;
* Organization and travel grants of 16th International gvSIG Conference: 2,200 USD&lt;br /&gt;
* Organization of 5th gvSIG Festival and preparation of free online courses: 800 USD&lt;br /&gt;
* Flyers and other printed materials for events: 300 USD  &lt;br /&gt;
* Support for attending other conferences: 1,700 USD &lt;br /&gt;
&lt;br /&gt;
[[Category:Budget]]&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=GvSIG_GSoC_2019_Ideas&amp;diff=119386</id>
		<title>GvSIG GSoC 2019 Ideas</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=GvSIG_GSoC_2019_Ideas&amp;diff=119386"/>
		<updated>2019-02-01T11:43:11Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: Starting gvSIG GSOC ideas 2019&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Use this page to jot down and develop any good idea for the [[Google Summer of Code 2019|2019]] program with gvSIG project. Please, use the [http://www.gvsig.com/en/community/mailing-lists gvSIG mailing lists] for discussion and check [[Google Summer of Code 2018|2018]], [[Google Summer of Code 2017|2017]], [[Google Summer of Code 2016|2016]], [[Google Summer of Code 2015|2015]], [[Google Summer of Code 2014|2014]], [[GvSIG GSoC 2013 Ideas|2013]], [[GvSIG GSoC 2012 Ideas|2012]], [[GvSIG GSoC 2011 Ideas|2011]], [[GvSIG GSoC 2010 Ideas|2010]], [[GvSIG GSoC 2009 Ideas|2009]] ideas pages for examples or reference.&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Rules for Topology process ==&lt;br /&gt;
&lt;br /&gt;
* '''Product''': gvSIG Desktop&lt;br /&gt;
* '''Mentors''': Óscar Martínez, Mario Carrera &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Description&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=OSGeo_Budget_2019&amp;diff=119049</id>
		<title>OSGeo Budget 2019</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=OSGeo_Budget_2019&amp;diff=119049"/>
		<updated>2019-01-16T08:09:36Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: Adding gvSIG Budget&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Draft budget to be discussed in December board meeting, see [[OSGeo Budget 2018]] and [[Finance Committee#Documents]] for prior years.&lt;br /&gt;
&lt;br /&gt;
== OSGeo Board ==&lt;br /&gt;
&lt;br /&gt;
OSGeo board operates according to our bylaws providing vision and direction for our foundation. The board has also taken on responsibility setting for an annual budget, building partner relationships, sponsorship program and code sprints.&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! Board&lt;br /&gt;
! 2019&lt;br /&gt;
! Notes&lt;br /&gt;
|- &lt;br /&gt;
| Admin&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 3,000&lt;br /&gt;
| Operational expenses including insurance, tax filing fees, accountant, bank fees.&lt;br /&gt;
|-&lt;br /&gt;
| Travel&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 15,000&lt;br /&gt;
| Outreach focus&lt;br /&gt;
|-&lt;br /&gt;
| Partners and Sponsors&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| relationship building, attending b2b functions, foss4g/foss4ge/foss4gna/foss4g-asia breakfast meetings&lt;br /&gt;
|-&lt;br /&gt;
| Code Sprints&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 20,500&lt;br /&gt;
| board responsible for handling code sprint requests, breakdown covered below&lt;br /&gt;
|-&lt;br /&gt;
| Events&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 10,000&lt;br /&gt;
| Consider supporting events, to avoid confusing code sprint program above&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== OSGeo Committees ==&lt;br /&gt;
&lt;br /&gt;
The following committees have been formed to fulfill out goals as an organization, each committee is provided a mandate, with the chair of the committee represented as an officer of our organization.&lt;br /&gt;
&lt;br /&gt;
* Code of Conduct Committee&lt;br /&gt;
* Conference Committee&lt;br /&gt;
* GeoForAll - committee acting as advisory board for the GeoForAll Initiative &lt;br /&gt;
* Incubation Committee - committee providing hands-on support for project teams adopting open source principles and practice.&lt;br /&gt;
* Marketing Committee - outreach and advocacy support&lt;br /&gt;
* Open GeoScience Committee&lt;br /&gt;
* System Administration Committee - foundation infrastructure &lt;br /&gt;
* UN Committee - committee responsible for our participation in the UN Open GIS program&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! OSGeo Committees&lt;br /&gt;
! 2019&lt;br /&gt;
! Notes&lt;br /&gt;
|- &lt;br /&gt;
| SAC&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| pending request&lt;br /&gt;
|-&lt;br /&gt;
| Open GeoScience&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| pending request&lt;br /&gt;
|-&lt;br /&gt;
| Conference&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; |  25.000&lt;br /&gt;
| TGP, 50-60% for global event, rest for regional events&lt;br /&gt;
|-&lt;br /&gt;
| Marketing&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| pending request, not no active chair&lt;br /&gt;
|-&lt;br /&gt;
| GeoForAll&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 3000&lt;br /&gt;
| Introducing GeoForAll and QGIS using presentations and workshops to high school teachers and students in Mashhad, Iran. &lt;br /&gt;
|-&lt;br /&gt;
| UN Committee&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 4000-5000€&lt;br /&gt;
| UN Challenge&lt;br /&gt;
|-&lt;br /&gt;
| OSGeo Incubation&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 18,000&lt;br /&gt;
| Rough breakdown of 3,000 per incubation project to be used strictly towards progress on OSGeo incubation. Note all projects in incubation have access to additional funding via the osgeo community project program. Committee itself expects no appreciable expenses.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Total Committees Budget for 2019: TBD&lt;br /&gt;
&lt;br /&gt;
== OSGeo Initiatives ==&lt;br /&gt;
&lt;br /&gt;
OSGeo initiatives have formed to pursue a specific short term, or long term goal. Initiatives maybe formed by a committee or the board as required. Iniativies a great way to collaborate with projects, committees and partners.&lt;br /&gt;
&lt;br /&gt;
* GeoForAll - education and research program produced in collaboration with our partners&lt;br /&gt;
* FOSS4G - event series produced in collaboration with the conference committee and local chapters&lt;br /&gt;
* Local Chapters - outreach initiative establishing regional OSGeo groups for direct grassroots advoacacy&lt;br /&gt;
* Open GeoScience - outreach and advocacy geoscience community&lt;br /&gt;
* GSoC - coordinate participation in google-summer-of-code and code-in activities&lt;br /&gt;
* OSGeoLive - outreach initiative providing &lt;br /&gt;
* Meta CRS - interoperability initiative promoting data sharing with cross project spatial reference system compatibility&lt;br /&gt;
* Trave Grant Program - provides assistance for attending OSGeo events&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! OSGeo Initiatives&lt;br /&gt;
! 2019&lt;br /&gt;
! Notes&lt;br /&gt;
|- &lt;br /&gt;
| FOSS4G&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | &lt;br /&gt;
| Managed by Conference Committee&lt;br /&gt;
|-&lt;br /&gt;
| Local Chapters&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | &lt;br /&gt;
| Managed by board, no direct funding requests&lt;br /&gt;
|-&lt;br /&gt;
| Open GeoScience&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | &lt;br /&gt;
|  Managed by Open Geo Science Committee&lt;br /&gt;
|-&lt;br /&gt;
| GSoC&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | &lt;br /&gt;
| Previously had requests to help students attend events&lt;br /&gt;
|-&lt;br /&gt;
| OSGeoLive &lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Now an initiative of the OSGeoLive project&lt;br /&gt;
|-&lt;br /&gt;
| Meta CRS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | &lt;br /&gt;
| Critical group for our interoperability goal, ask participants if they need any assistance&lt;br /&gt;
|-&lt;br /&gt;
| Travel Grant Program &lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | TBD&lt;br /&gt;
| Previous years used 10k commitment + 10k matching sponsor donations&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Total Initiatives Budget for 2019: TBD&lt;br /&gt;
&lt;br /&gt;
==  OSGeo Projects ==&lt;br /&gt;
&lt;br /&gt;
OSGeo Projects each have a project steering committee, the chair of which is acknowledged as a foundation officer with spending authority on behalf of their committee.&lt;br /&gt;
&lt;br /&gt;
Notes:&lt;br /&gt;
&lt;br /&gt;
* Note this is a budget, representing planned spending in 2019 - actual balance available to each PSC (from fundraising, donations and sponsorship) may be considered when planning.&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! OSGeo Project&lt;br /&gt;
! 2019&lt;br /&gt;
! Notes&lt;br /&gt;
|- &lt;br /&gt;
| deegree&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| FDO&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GDAL/OGR&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 5000&lt;br /&gt;
| Renewal of Travis-CI plan for 11 parallel workers. Will also benefit to all other projects under the OSGeo github organization: homebrew-osgeo4mac, proj.4, libgeotiff, etc.&lt;br /&gt;
|-&lt;br /&gt;
| geomajas&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GeoMOOSE&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GeoNetwork&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GeoNode&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GEOS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GeoServer&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GeoTools&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | &lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| GRASS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| gvSIG&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 3000 USD&lt;br /&gt;
| Details of the budget at https://wiki.osgeo.org/wiki/GvSIG_Budget_2019 &lt;br /&gt;
|-&lt;br /&gt;
| Mapbender&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| MapFish&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| MapGuide Open Source&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| MapServer&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| Marble&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| OpenLayers&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| OSSIM&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| PostGIS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| pycsw&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| QGIS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | € 3,000&lt;br /&gt;
| QGIS Server: improve WFS compliance from currently 50% to 100% (daily status reports at http://tests.qgis.org/ogc_cite/wfs_110/)&lt;br /&gt;
|-&lt;br /&gt;
| PyWPS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| OSGeoLive&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | &lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Total Projects Budget for 2019: TBD&lt;br /&gt;
&lt;br /&gt;
==  Community Projects ==&lt;br /&gt;
&lt;br /&gt;
Community projects act through the board as they do not have a project officer.&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! Community Project&lt;br /&gt;
! 2019&lt;br /&gt;
! Notes&lt;br /&gt;
|- &lt;br /&gt;
| ZOO-Project&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot;| &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| pgRouting&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot;| 2,000&lt;br /&gt;
| Travel expenses to FOSS4G Romania&lt;br /&gt;
|-&lt;br /&gt;
| istSOS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | &lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Total Community Projects Budget for 2019: TBD&lt;br /&gt;
&lt;br /&gt;
== Code Sprints ==&lt;br /&gt;
&lt;br /&gt;
We have asked project teams for guidance to help set our code sprint budget:&lt;br /&gt;
&lt;br /&gt;
* please note our [[Code Sprint Guidelines]] ask for event details, budget and fundraising on your part.&lt;br /&gt;
* Code sprint funding is setup to help carry funds from one event to the next allowing us to hold more code-sprints with a smaller annual budget.&lt;br /&gt;
* Out priority is to share the risk with organizers allowing access to funds early to book facilities as required&lt;br /&gt;
* We had requests to fund sprints that were part of larger events, these escaped our 2017 planning but were still funded to the best of our abilities&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! Sprint Request&lt;br /&gt;
! 2019&lt;br /&gt;
! Notes&lt;br /&gt;
|-&lt;br /&gt;
| OSGeo annual code sprint&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | &lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GeoServer&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | &lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| PostGIS Code Sprint &lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 3,000&lt;br /&gt;
| In support of venue/event or travel for committer to other OSGeo code sprint&lt;br /&gt;
|-&lt;br /&gt;
| Bolsena Code Sprint &lt;br /&gt;
|&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| Small Code Sprints&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 10,000&lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Total Code Sprint Budget for 2019: TBD&lt;br /&gt;
&lt;br /&gt;
These funds are approved as part of the board budget for 2018.&lt;br /&gt;
&lt;br /&gt;
== Approval and Amendments ==&lt;br /&gt;
&lt;br /&gt;
* Budget Meeting:  Board_Meeting_2019-01-04&lt;br /&gt;
* Amendments: &lt;br /&gt;
&lt;br /&gt;
[[Category:Budget]]&lt;br /&gt;
[[Category:Finance]]&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=GvSIG_Budget_2019&amp;diff=118928</id>
		<title>GvSIG Budget 2019</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=GvSIG_Budget_2019&amp;diff=118928"/>
		<updated>2018-12-21T13:23:57Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: gvSIG Budget 2019&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The gvSIG project requests to OSGeo a total budget of 3000 USD for the 2019.&lt;br /&gt;
&lt;br /&gt;
This is intended to cover:&lt;br /&gt;
&lt;br /&gt;
- Organization of 15th International gvSIG Conference: 1,500 USD&lt;br /&gt;
&lt;br /&gt;
- Organization of 4th gvSIG Festival and preparation of free online courses: 500 USD&lt;br /&gt;
&lt;br /&gt;
- Support for attending conferences: 1000 USD&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=GvSIG_Report_2018&amp;diff=116082</id>
		<title>GvSIG Report 2018</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=GvSIG_Report_2018&amp;diff=116082"/>
		<updated>2018-08-09T08:04:24Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: gvSIG Annual Report 2018&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== Project Name ==&lt;br /&gt;
* https://www.osgeo.org/projects/gvsig/&lt;br /&gt;
* Contact name: Mario Carrera (Communication and Translation Manager)&lt;br /&gt;
&lt;br /&gt;
=== Key Accomplishments ===&lt;br /&gt;
gvSIG releases: &lt;br /&gt;
* Release of gvSIG Desktop 2.4 (21/02/2018) (gvSIG 2.4.1 at the end of 2018)&lt;br /&gt;
* Working in parallel on gvSIG Desktop 3.0 with a new raster architecture and avoiding commercial drivers. &lt;br /&gt;
* New gvSIG Mobile version (End of 2018)  &lt;br /&gt;
* New tools for gvSIG Crime (End of 2018)  &lt;br /&gt;
* New gvSIG Online version &lt;br /&gt;
 &lt;br /&gt;
Infrastructure: &lt;br /&gt;
* We are migrating the gvSIG case studies website (http://box5589.temp.domains/~gvsigorg//case-studies) to a new section of the gvSIG Project website (http://www.gvsig.com).  &lt;br /&gt;
* We have created the gvSIG devel mailing list for English-speaking developers (it was hosted in Joinup (https://joinup.ec.europa.eu/), the collaborative platform created by the European Commission, previously but they deleted it.&lt;br /&gt;
&lt;br /&gt;
=== Areas for Improvement ===&lt;br /&gt;
* Translations in some languages would have to be updated. We would need help on it. &lt;br /&gt;
&lt;br /&gt;
=== How is your Project Health? ===&lt;br /&gt;
During 2018 there are several meetings about gvSIG: &lt;br /&gt;
* 14th International gvSIG Conference (Spain) 10/2018 (www.gvsig.com/en/events/gvsig-conference/14th-international-gvsig-conference/)&lt;br /&gt;
* 3rd gvSIG Festival (virtual conference) 03/2018 (www.gvsig.com/en/events/gvsig-festival/3rd-gvsig-festival/)&lt;br /&gt;
* 10as Jornadas de Latinoamérica y Caribe de gvSIG (Brazil) 08/2018 (http://www.gvsig.com/es/eventos/jornadas-lac/2018) &lt;br /&gt;
* 5as Jornadas gvSIG Uruguay 10/2018 (http://www.gvsig.com/en/5as-jornadas-gvsig-uruguay) &lt;br /&gt;
* Different conferences in universities (University of León, Castilla-la-Mancha University, Polytechnics University of Cartagena, University of Extremadura)  &lt;br /&gt;
 &lt;br /&gt;
There also have been presentations at other conferences: &lt;br /&gt;
* FOSS4G-Europe (Guimaraes – Portugal) &lt;br /&gt;
* 3er Congreso Nacional de Estudiantes de Geomática, Geodesia y Geoinformática (Mexico) &lt;br /&gt;
* Jornada SIG Libre (Girona – Spain) &lt;br /&gt;
* JIDEE (Mahón – Spain) &lt;br /&gt;
* TIG Conference (Valencia – Spain) &lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
Many papers that include gvSIG are being published in scientific journals and conference proceedings in 2018. &lt;br /&gt;
&lt;br /&gt;
=== Opportunities to Help ===&lt;br /&gt;
There many ways to participate in the gvSIG project, with different levels of involvement, like: &lt;br /&gt;
* Participating on the mailing lists, for users as well as developers, in may languages. &lt;br /&gt;
* Testing the application. &lt;br /&gt;
* Doing translations of the gvSIG user interface, user and developer documentation and the gvSIG portal. &lt;br /&gt;
* Writing articles and case studies. &lt;br /&gt;
* Developing new addons. &lt;br /&gt;
* Creating new scripts for the gvSIG Scripting repository. &lt;br /&gt;
&lt;br /&gt;
You can find more information in the following page: http://www.gvsig.com/en/community &lt;br /&gt;
&lt;br /&gt;
From OSGeo we would need financial assistance to organize the gvSIG Conference. We would need help for it. &lt;br /&gt;
&lt;br /&gt;
=== Outlook for 2019 ===&lt;br /&gt;
* Release of gvSIG Desktop 3 with a new raster architecture and a lot of improvements and new features. &lt;br /&gt;
* Events (Latin American, International...)&lt;br /&gt;
* New functionalities for gvSIG Mobile. &lt;br /&gt;
* New gvSIG Online version.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__notoc__&lt;br /&gt;
[[Category: Reports 2018]]&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=GvSIG_Report_2017&amp;diff=113494</id>
		<title>GvSIG Report 2017</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=GvSIG_Report_2017&amp;diff=113494"/>
		<updated>2018-02-01T12:17:33Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== gvSIG Report 2017 ==&lt;br /&gt;
&lt;br /&gt;
=== Key Accomplishments ===&lt;br /&gt;
&lt;br /&gt;
* Release of gvSIG Desktop 2.4 RC3 (29/09/2017). &lt;br /&gt;
* Release of the new gvSIG Mobile (22/11/2017) &lt;br /&gt;
* Development of gvSIG Crime. &lt;br /&gt;
* gvSIG Batoví (gvSIG Educa)  &lt;br /&gt;
* Google Summer of Code 2017 participation. &lt;br /&gt;
&lt;br /&gt;
=== Events ===&lt;br /&gt;
&lt;br /&gt;
* 13th International gvSIG Conference (Spain) 10/2017 (http://www.gvsig.com/es/eventos/jornadas-gvsig/13as-jornadas-gvsig) &lt;br /&gt;
* 2nd gvSIG Festival (virtual conference) 05/2017 (http://www.gvsig.com/es/eventos/gvsig-festival/2o-gvsig-festival)  &lt;br /&gt;
* 9as Jornadas de Latinoamérica y Caribe de gvSIG (Brazil) 10/2017 (http://www.gvsig.com/es/eventos/jornadas-lac/2017)  &lt;br /&gt;
* 4as Jornadas de México de gvSIG (México) 10/2017 (http://www.gvsig.com/es/eventos/jornadas-mexico/2017) &lt;br /&gt;
* Different conferences in universities (University of Vigo, Miguel Hernández University in Elche, UCM in Madrid) &lt;br /&gt;
 &lt;br /&gt;
=== Presentations at other conferences ===&lt;br /&gt;
&lt;br /&gt;
* Sharing and Reuse Conference by European Commission (Lisbon – Portugal) &lt;br /&gt;
* NASA Europa Challenge (Helsinki  Finland)&lt;br /&gt;
* GIS Day Sudan (University of Karthoum - Sudan)&lt;br /&gt;
* VI Conference in Memory of Petr Semyonov-Tyan-Shansky (Lipetsk - Russia)&lt;br /&gt;
* Space Apps Challenge of NASA (Valencia - Spain)&lt;br /&gt;
* VIII Jornadas Ibéricas de Infraestructuras de Datos Espaciales (Lisbon – Portugal) &lt;br /&gt;
* Visualizar’17: Migrations (Madrid - Spain) &lt;br /&gt;
* Iberflora 2017 (Plants and flowers trade fair in Valencia - Spain)&lt;br /&gt;
* I National Meeting of Geobloggers (Valencia - Spain)&lt;br /&gt;
* Ateneo Mercantil of Valencia (Valencia – Spain)&lt;br /&gt;
* CONAMA (Valencia – Spain)&lt;br /&gt;
&lt;br /&gt;
=== Awards ===&lt;br /&gt;
&lt;br /&gt;
* 1st prize in “Cross-border category” at “Sharing &amp;amp; Reuse Awards” of European Commission.&lt;br /&gt;
* “Europa Challenge” at Helsinki awarded by NASA to the gvSIG Suite in the “Professional” category.&lt;br /&gt;
* Excellence “Internationalization” Award given by the Professional Union of Valencia.&lt;br /&gt;
* “ITC Promoter organization” prize awarded by the Valencian Telecommunications.&lt;br /&gt;
&lt;br /&gt;
=== Articles ===&lt;br /&gt;
&lt;br /&gt;
Many papers that include gvSIG were published in scientific journals and conference proceedings in 2017: https://gvsig.org/web/docusr/divulgacion/articulos/&lt;br /&gt;
&lt;br /&gt;
=== Opportunities to Help ===&lt;br /&gt;
&lt;br /&gt;
There many ways to participate in the gvSIG project, with different levels of involvement, like: &lt;br /&gt;
&lt;br /&gt;
* Participating on the mailing lists, for users as well as developers, in may languages. &lt;br /&gt;
* Testing the application. &lt;br /&gt;
* Doing translations of the gvSIG user interface, user and developer documentation and the gvSIG portal. &lt;br /&gt;
* Writing articles and case studies. &lt;br /&gt;
* Developing new addons. &lt;br /&gt;
&lt;br /&gt;
You can find more information in the following page: http://www.gvsig.com/en/community  &lt;br /&gt;
&lt;br /&gt;
=== Outlook for 2018 ===&lt;br /&gt;
&lt;br /&gt;
Release of gvSIG Desktop 2.5 &lt;br /&gt;
Improvements in gvSIG Mobile &lt;br /&gt;
Events (Latin American, International,...)&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=GvSIG_Report_2017&amp;diff=113493</id>
		<title>GvSIG Report 2017</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=GvSIG_Report_2017&amp;diff=113493"/>
		<updated>2018-02-01T12:15:28Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== gvSIG Report 2017 ==&lt;br /&gt;
&lt;br /&gt;
=== Key Accomplishments ===&lt;br /&gt;
&lt;br /&gt;
* Release of gvSIG Desktop 2.4 RC3 (29/09/2017). &lt;br /&gt;
* Release of the new gvSIG Mobile (22/11/2017) &lt;br /&gt;
* Development of gvSIG Crime. &lt;br /&gt;
* gvSIG Batoví (gvSIG Educa)  &lt;br /&gt;
* Google Summer of Code 2017 participation. &lt;br /&gt;
&lt;br /&gt;
=== Events ===&lt;br /&gt;
&lt;br /&gt;
* 13th International gvSIG Conference (Spain) 10/2017 (http://www.gvsig.com/es/eventos/jornadas-gvsig/13as-jornadas-gvsig) &lt;br /&gt;
* 2nd gvSIG Festival (virtual conference) 05/2017 (http://www.gvsig.com/es/eventos/gvsig-festival/2o-gvsig-festival)  &lt;br /&gt;
* 9as Jornadas de Latinoamérica y Caribe de gvSIG (Brazil) 10/2017 (http://www.gvsig.com/es/eventos/jornadas-lac/2017)  &lt;br /&gt;
* 4as Jornadas de México de gvSIG (México) 10/2017 (http://www.gvsig.com/es/eventos/jornadas-mexico/2017) &lt;br /&gt;
* Different conferences in universities (University of Vigo, Miguel Hernández University in Elche, UCM in Madrid) &lt;br /&gt;
 &lt;br /&gt;
=== Presentations at other conferences ===&lt;br /&gt;
&lt;br /&gt;
* Sharing and Reuse Conference by European Commission (Lisbon – Portugal) &lt;br /&gt;
* NASA Europa Challenge (Helsinki  Finland)&lt;br /&gt;
* GIS Day Sudan (University of Karthoum - Sudan)&lt;br /&gt;
* VI Conference in Memory of Petr Semyonov-Tyan-Shansky (Lipetsk - Russia)&lt;br /&gt;
* Space Apps Challenge of NASA (Valencia - Spain)&lt;br /&gt;
* VIII Jornadas Ibéricas de Infraestructuras de Datos Espaciales (Lisbon – Portugal) &lt;br /&gt;
* Visualizar’17: Migrations (Madrid - Spain) &lt;br /&gt;
* Iberflora 2017 (Plants and flowers trade fair in Valencia - Spain)&lt;br /&gt;
* I National Meeting of Geobloggers (Valencia - Spain)&lt;br /&gt;
* Ateneo Mercantil of Valencia (Valencia – Spain)&lt;br /&gt;
* CONAMA (Valencia – Spain)&lt;br /&gt;
&lt;br /&gt;
=== Awards ===&lt;br /&gt;
&lt;br /&gt;
* 1st prize in “Cross-border category” at “Sharing &amp;amp; Reuse Awards” of European Commission.&lt;br /&gt;
* “Europa Challenge” at Helsinki awarded by NASA to the gvSIG Suite in the “Professional” category.&lt;br /&gt;
* Excellence “Internationalization” Award given by the Professional Union of Valencia.&lt;br /&gt;
* “ITC Promoter organization” prize awarded by the Valencian Telecommunications.&lt;br /&gt;
&lt;br /&gt;
=== Articles ===&lt;br /&gt;
&lt;br /&gt;
Many papers that include gvSIG were published in scientific journals and conference proceedings in 2017: https://gvsig.org/web/docusr/divulgacion/articulos/&lt;br /&gt;
&lt;br /&gt;
=== Opportunities to Help ===&lt;br /&gt;
&lt;br /&gt;
There many ways to participate in the gvSIG project, with different levels of involvement, like: &lt;br /&gt;
&lt;br /&gt;
* Participating on the mailing lists, for users as well as developers, in may languages. &lt;br /&gt;
* Testing the application. &lt;br /&gt;
* Doing translations of the gvSIG user interface, user and developer documentation and the gvSIG portal. &lt;br /&gt;
* Writing articles and case studies. &lt;br /&gt;
* Developing new addons. &lt;br /&gt;
&lt;br /&gt;
You can find more information in the following page: http://www.gvsig.org/web/community/participate &lt;br /&gt;
&lt;br /&gt;
=== Outlook for 2018 ===&lt;br /&gt;
&lt;br /&gt;
Release of gvSIG Desktop 2.5 &lt;br /&gt;
Improvements in gvSIG Mobile &lt;br /&gt;
Events (Latin American, International,...)&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=GvSIG_Report_2017&amp;diff=113492</id>
		<title>GvSIG Report 2017</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=GvSIG_Report_2017&amp;diff=113492"/>
		<updated>2018-02-01T12:14:37Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: gvSIG Report 2017&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== gvSIG Report 2017 ==&lt;br /&gt;
&lt;br /&gt;
=== Key Accomplishments ===&lt;br /&gt;
&lt;br /&gt;
 * Release of gvSIG Desktop 2.4 RC3 (29/09/2017). &lt;br /&gt;
 * Release of the new gvSIG Mobile (22/11/2017) &lt;br /&gt;
 * Development of gvSIG Crime. &lt;br /&gt;
 * gvSIG Batoví (gvSIG Educa)  &lt;br /&gt;
 * Google Summer of Code 2017 participation. &lt;br /&gt;
&lt;br /&gt;
=== Events ===&lt;br /&gt;
&lt;br /&gt;
 * 13th International gvSIG Conference (Spain) 10/2017 (http://www.gvsig.com/es/eventos/jornadas-gvsig/13as-jornadas-gvsig) &lt;br /&gt;
 * 2nd gvSIG Festival (virtual conference) 05/2017 (http://www.gvsig.com/es/eventos/gvsig-festival/2o-gvsig-festival)  &lt;br /&gt;
 * 9as Jornadas de Latinoamérica y Caribe de gvSIG (Brazil) 10/2017 (http://www.gvsig.com/es/eventos/jornadas-lac/2017)  &lt;br /&gt;
 * 4as Jornadas de México de gvSIG (México) 10/2017 (http://www.gvsig.com/es/eventos/jornadas-mexico/2017) &lt;br /&gt;
 * Different conferences in universities (University of Vigo, Miguel Hernández University in Elche, UCM in Madrid) &lt;br /&gt;
 &lt;br /&gt;
=== Presentations at other conferences ===&lt;br /&gt;
&lt;br /&gt;
* Sharing and Reuse Conference by European Commission (Lisbon – Portugal) &lt;br /&gt;
* NASA Europa Challenge (Helsinki  Finland)&lt;br /&gt;
* GIS Day Sudan (University of Karthoum - Sudan)&lt;br /&gt;
* VI Conference in Memory of Petr Semyonov-Tyan-Shansky (Lipetsk - Russia)&lt;br /&gt;
* Space Apps Challenge of NASA (Valencia - Spain)&lt;br /&gt;
* VIII Jornadas Ibéricas de Infraestructuras de Datos Espaciales (Lisbon – Portugal) &lt;br /&gt;
* Visualizar’17: Migrations (Madrid - Spain) &lt;br /&gt;
* Iberflora 2017 (Plants and flowers trade fair in Valencia - Spain)&lt;br /&gt;
* I National Meeting of Geobloggers (Valencia - Spain)&lt;br /&gt;
* Ateneo Mercantil of Valencia (Valencia – Spain)&lt;br /&gt;
* CONAMA (Valencia – Spain)&lt;br /&gt;
&lt;br /&gt;
=== Awards ===&lt;br /&gt;
&lt;br /&gt;
 * 1st prize in “Cross-border category” at “Sharing &amp;amp; Reuse Awards” of European Commission.&lt;br /&gt;
 * “Europa Challenge” at Helsinki awarded by NASA to the gvSIG Suite in the “Professional” category.&lt;br /&gt;
 * Excellence “Internationalization” Award given by the Professional Union of Valencia.&lt;br /&gt;
 * “ITC Promoter organization” prize awarded by the Valencian Telecommunications.&lt;br /&gt;
&lt;br /&gt;
=== Articles ===&lt;br /&gt;
&lt;br /&gt;
Many papers that include gvSIG were published in scientific journals and conference proceedings in 2017: https://gvsig.org/web/docusr/divulgacion/articulos/&lt;br /&gt;
&lt;br /&gt;
=== Opportunities to Help ===&lt;br /&gt;
&lt;br /&gt;
There many ways to participate in the gvSIG project, with different levels of involvement, like: &lt;br /&gt;
&lt;br /&gt;
* Participating on the mailing lists, for users as well as developers, in may languages. &lt;br /&gt;
* Testing the application. &lt;br /&gt;
* Doing translations of the gvSIG user interface, user and developer documentation and the gvSIG portal. &lt;br /&gt;
* Writing articles and case studies. &lt;br /&gt;
* Developing new addons. &lt;br /&gt;
&lt;br /&gt;
You can find more information in the following page: http://www.gvsig.org/web/community/participate &lt;br /&gt;
&lt;br /&gt;
=== Outlook for 2018 ===&lt;br /&gt;
&lt;br /&gt;
Release of gvSIG Desktop 2.5 &lt;br /&gt;
Improvements in gvSIG Mobile &lt;br /&gt;
Events (Latin American, International,...)&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=GvSIG_GSoC_2018_Ideas&amp;diff=113238</id>
		<title>GvSIG GSoC 2018 Ideas</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=GvSIG_GSoC_2018_Ideas&amp;diff=113238"/>
		<updated>2018-01-18T16:57:24Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
Use this page to jot down and develop any good idea for the [[Google Summer of Code 2018|2018]] program with gvSIG project. Please, use the [http://www.gvsig.com/en/community/mailing-lists gvSIG mailing lists] for discussion and check [[Google Summer of Code 2017|2017]], [[Google Summer of Code 2016|2016]], [[Google Summer of Code 2015|2015]], [[Google Summer of Code 2014|2014]], [[GvSIG GSoC 2013 Ideas|2013]], [[GvSIG GSoC 2012 Ideas|2012]], [[GvSIG GSoC 2011 Ideas|2011]], [[GvSIG GSoC 2010 Ideas|2010]], [[GvSIG GSoC 2009 Ideas|2009]] ideas pages for examples or reference.&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== gvSIG Online plugin for gvSIG desktop ==&lt;br /&gt;
&lt;br /&gt;
* '''Product''': gvSIG Desktop&lt;br /&gt;
* '''Mentors''': César Martínez &lt;br /&gt;
* '''Student''': José Vicente Higón Valero&lt;br /&gt;
&lt;br /&gt;
gvSIG Online is a solution for Spatial Data Infrastructure in open source software. With gvSIG Online a user will be able to do public and private geoportals.&lt;br /&gt;
&lt;br /&gt;
It will allow to add a geoportal of gvSIG Online as a new data source, adding in gvSIG Desktop all the Web Map Services published in this geoportal.&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=GvSIG_GSoC_2018_Ideas&amp;diff=113237</id>
		<title>GvSIG GSoC 2018 Ideas</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=GvSIG_GSoC_2018_Ideas&amp;diff=113237"/>
		<updated>2018-01-18T16:37:44Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: gvSIG Project ideas 2018&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
Use this page to jot down and develop any good idea for the [[Google Summer of Code 2018|2018]] program with gvSIG project. Please, use the gvSIG mailing lists for discussion and check [[Google Summer of Code 2017|2017]], [[Google Summer of Code 2016|2016]], [[Google Summer of Code 2015|2015]], [[Google Summer of Code 2014|2014]], [[GvSIG GSoC 2013 Ideas|2013]], [[GvSIG GSoC 2012 Ideas|2012]], [[GvSIG GSoC 2011 Ideas|2011]], [[GvSIG GSoC 2010 Ideas|2010]], [[GvSIG GSoC 2009 Ideas|2009]] ideas pages for examples or reference.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== gvSIG Online plugin for gvSIG desktop ==&lt;br /&gt;
&lt;br /&gt;
* '''Product''': gvSIG Desktop&lt;br /&gt;
* '''Mentors''': César Martínez &lt;br /&gt;
* '''Student''': José Vicente Higón Valero&lt;br /&gt;
&lt;br /&gt;
gvSIG Online is a solution for Spatial Data Infrastructure in open source software. With gvSIG Online a user will be able to do public and private geoportals.&lt;br /&gt;
&lt;br /&gt;
It will allow to add a geoportal of gvSIG Online as a new data source, adding in gvSIG Desktop all the Web Map Services published in this geoportal.&lt;br /&gt;
&lt;br /&gt;
--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2018_Ideas&amp;diff=113233</id>
		<title>Google Summer of Code 2018 Ideas</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2018_Ideas&amp;diff=113233"/>
		<updated>2018-01-18T16:27:02Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;center&amp;gt;&lt;br /&gt;
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] &amp;lt;font size=&amp;quot;+3&amp;quot;&amp;gt; @ &amp;lt;/font&amp;gt; &lt;br /&gt;
[[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]&lt;br /&gt;
&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
-----&lt;br /&gt;
* Back to the main OSGeo [[Google Summer of Code 2018]] wiki page.&lt;br /&gt;
&lt;br /&gt;
* See also ideas from [[Google Summer of Code 2016 Ideas|2017]], [[Google Summer of Code 2016 Ideas|2016]], [[Google Summer of Code 2015 Ideas|2015]], [[Google Summer of Code 2014 Ideas|2014]], [[Google Summer of Code 2013 Ideas|2013]], [[Google Summer of Code 2012 Ideas|2012]], [[Google Summer of Code 2011 Ideas|2011]], [[Google Summer of Code 2010 Ideas|2010]], [[Google_Summer_of_Code_2009_Ideas|2009]], [[2008_SoC_Merged_Ideas|2008]], [[2007_SoC_Merged_Ideas|2007]].&lt;br /&gt;
-----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== OSGeo Google Summer of Code 2018 ==&lt;br /&gt;
&lt;br /&gt;
The [http://www.osgeo.org Open Source Geospatial Foundation] would like to extend a welcome to all SoC students. On this page you will find links to a host of ideas organized by project. You will find ideas ranging from the depths of computer science graph theory to the heights of visualization. One thing all these ideas have in common is lots and lots of spatial data.&lt;br /&gt;
&lt;br /&gt;
These ideas are '''*only*''' to motivate you, and serve as example of the kind of hills we want to charge up. Your own ideas are more than welcomed - they are encouraged. We view you as the next wave of open source leaders and the future of the geospatial industry; show us what you've got!&lt;br /&gt;
&lt;br /&gt;
* '''Students: check out the [[Google Summer of Code Recommendations for Students]] page. If you need more information on how to apply you can contact all the mentors via the OSGeo-SoC mailing list''' ([[#How to get in contact via mailing lists|see below]]) And look at [https://developers.google.com/open-source/gsoc/help/responsibilities GSoC Roles and Responsibilities ] to understand a successfull teamwork and interplay of project, mentors and students. &lt;br /&gt;
&lt;br /&gt;
* There is a [https://developers.google.com/open-source/soc/resources/flyers Google SoC flyer] to look at and post in appropriate places.&lt;br /&gt;
&lt;br /&gt;
* Ok, [[OSGeo]] is involved in working with maps and things, but what kind of projects does it really do? Have a look at the [http://planet.osgeo.org/ live blog feed] to see what people are working on right now.&lt;br /&gt;
&lt;br /&gt;
* Mentors, there's an additional link providing some tips and specifying your responsibilities on the main OSGeo [[Google Summer of Code 2018 Administrative]] wiki page.&lt;br /&gt;
&lt;br /&gt;
== The ideas pages ==&lt;br /&gt;
'''''[Check back often, it's a work in progress]'''''&lt;br /&gt;
&lt;br /&gt;
To add your page, &amp;lt;strong&amp;gt;please contact the GSoC admin team&amp;lt;/strong&amp;gt; to let them know of your ideas page, by sending an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]&lt;br /&gt;
&lt;br /&gt;
Each participating project's list of ideas is on the respective projects' wikis, with a short description of the project and what type of students would be interested in it:&lt;br /&gt;
&lt;br /&gt;
=== OSGeo Foundation graduated projects ===&lt;br /&gt;
&lt;br /&gt;
''More coming soon: Get started talking to your favorite project's development team today!''&lt;br /&gt;
&lt;br /&gt;
[[Image:logo-grass.png|60px|right]]&lt;br /&gt;
* [https://trac.osgeo.org/grass/wiki/GSoC/2018 '''GRASS GIS''' SoC Ideas]: [http://grass.osgeo.org GRASS GIS] is an open source GIS focusing on analysis, modeling and visualization. It is  a collection of modules written in C and Python and has a GUI written in wxPython. If you know Python, or want to implement algorithms in C, take a look! &lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-qgis.png|60px|right]]&lt;br /&gt;
* [https://hub.qgis.org/wiki/quantum-gis/Google_Summer_of_Code_2017 '''QGIS''' SoC Ideas]: [http://www.qgis.org QGIS] is a user friendly Open Source Geographic Information System (GIS) that runs on Linux, Unix, Mac OSX, and Windows. QGIS supports vector, raster, and database formats. It is written in C++ and Python.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-gdal.png|60px|right]]&lt;br /&gt;
* [http://trac.osgeo.org/gdal/wiki/SummerOfCode '''GDAL''' Ideas]: [http://www.gdal.org GDAL] is a C++ library for reading and writing geospatial data raster and vector formats.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
* [http://trac.osgeo.org/osgeo4w/wiki/Reports '''OSGeo4W''']: -  OSGeo4W is a binary distribution of a broad set of open source geospatial software for Win32 environments (Windows 7, XP, etc).&lt;br /&gt;
[[Image:Logo-osgeo4w-mini.png|60px|right]]&lt;br /&gt;
:* ''Idea'': We need to extend support to x64 based platforms to handle larger datasets and circumvent memory restrictions. This is a distribution and packaging project which will involve most/all of OSGeo member projects. (''ed. note: keep in mind that to fulfill GSoC requirements each project must have a majority coding component, so lots of scripting, testing, and Makefiles!'')&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
[[Image:logo-gvSIG.png|60px|right]]&lt;br /&gt;
* [[GvSIG_GSoC_2018_Ideas|'''gvSIG''' Ideas]]: gvSIG is a free GIS project for [http://www.gvsig.com/en/web/guest/products/gvsig-desktop Desktop]. The gvSIG project looks for students with Java or Python skills that want to develop new ideas on this software. &lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Pycsw-logo.png|60px|right]]&lt;br /&gt;
* [https://github.com/geopython/pycsw/wiki/OSGeo-GSoC#2017'''pycsw''' Ideas]: [http://pycsw.org pycsw] is an OGC CSW server implementation written in Python, and provides a metadata and catalogue component for spatial data infrastructures.  The pycsw project is looking for students interested in Python and search, come join us!&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-opticks.png|right]]&lt;br /&gt;
* [http://opticks.org/confluence/display/opticksDev/Google+Summer+of+Code '''Opticks''' Ideas]: [http://opticks.org/ Opticks] is an extensible [http://en.wikipedia.org/wiki/Remote_sensing remote sensing] and imagery analysis desktop application. It provides a framework to process remote sensing data such as [http://en.wikipedia.org/wiki/Hyperspectral_imaging Hyperspectral] (HSI), [http://en.wikipedia.org/wiki/Multi-spectral_image Multispectral] (MSI), and [http://en.wikipedia.org/wiki/Synthetic_aperture_radar Synthetic aperture radar] (SAR) imagery and video. The application is written in C++ and licensed under LGPL v2.1. Extensions are written using C++ or Python. You can review the [http://opticks.org/confluence/display/opticksExt/All+Opticks+Extensions available extensions] and [http://opticks.org/confluence/display/opticks/Feature+Tour+-+Your+Data feature tour] to get a better idea of what Opticks can do.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!-- &lt;br /&gt;
[[Image:logo-postgis.png|60px|right]] &lt;br /&gt;
* [http://trac.osgeo.org/postgis/wiki/GoogleSummerCode '''PostGIS''' Ideas]: [http://postgis.net PostGIS] spatially enables the popular PostgreSQL object-relational database, allowing it to be used as a back-end database for geographic information systems (GIS) and web-mapping applications.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-ossim.png|90px|right]]&lt;br /&gt;
* [https://trac.osgeo.org/ossim/wiki/GSoC_2015 '''OSSIM''' SoC Ideas]: [http://trac.osgeo.org/ossim/wiki OSSIM] Open Source Software Image Map (OSSIM) is a high performance engine for remote sensing, image processing, geographical information systems and photogrammetry. The software has been under active development since 1996 and is deployed across a number of private, federal and civilian agencies. It is written in C++.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Logo_OTB.png|60px|right]]&lt;br /&gt;
* [http://wiki.orfeo-toolbox.org/index.php/Proposals_for_GSoC_2015 '''OTB''' SoC Ideas]: [http://www.orfeo-toolbox.org ORFEO ToolBox] (OTB) is an open source library for remote sensing image processing.Targeted algorithms for high resolution optical images (Pleiades, SPOT, QuickBird, WorldView, Landsat, Ikonos), hyperspectral sensors (Hyperion) or SAR (TerraSarX, ERS, Palsar) are available. The software has been under active development since 2006 and is written in C++ and it includes also side projects also open source with GUI like Monteverdi. OTB has recently started the incubation process into OSGeo.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Mapserver.png|100px|right]]&lt;br /&gt;
* [http://wiki.osgeo.org/wiki/MapServer_2015_SOC_Ideas '''Mapserver''' SoC Ideas]: MapServer is a Web Mapping Engine; an Open Source platform for publishing spatial data and interactive mapping applications to the web.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
=== OSGeo Foundation Incubation projects ===&lt;br /&gt;
&lt;br /&gt;
[[Image:Logo-istSOS.png|100px|right]]&lt;br /&gt;
* [https://sourceforge.net/p/istsos/wiki/GSoC_ideas_2018/ '''istSOS''' Ideas]: [http://sourceforge.net/projects/istsos/ istSOS] is a complete sensor data management system for acquiring, storing and dispatching time-series observations. istSOS is compliant with the Sensor Observation Service (SOS) version 1.0 and 2.0 standard from the Open Geospatial Consortium (OGC) and offers unique extended capabilities to support scientific data analyses (integrated quality assurance, RESTful API, on the fly processing with virtual procedures, remote data aggregation and time-space re-projection etc.). istSOS core libraries are written in Python while it easy to use interface is Web based.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Pywps logo.png|80px|right]]&lt;br /&gt;
* [https://github.com/geopython/pywps/wiki/GSoC-2017-ideas '''PyWPS''' Ideas]: [http://pywps.org/ PyWPS] is an implementation of the Web Processing Service standard from the Open Geospatial Consortium. PyWPS is written in Python. PyWPS enables integration, publishing and execution of Python processes via the WPS standard.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-geos.png|60px|right]]&lt;br /&gt;
* [http://trac.osgeo.org/geos/wiki/GSoC '''GEOS''' Ideas]: GEOS (Geometry Engine - Open Source) is a C++ port of the JTS Topology Suite (JTS). It includes the OpenGIS Simple Features for SQL spatial predicate functions and spatial operators, as well as specific JTS enhanced topology functions.&lt;br /&gt;
--&amp;gt; &lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-geoserver-crop.png|50px|right]]&lt;br /&gt;
* [https://github.com/geoserver/geoserver/wiki/GSOC-Ideas GSOC Ideas]: [http://live.osgeo.org/en/overview/geoserver_overview.html '''GeoServer'''] is a web server that allows you to serve maps and data from a variety of formats to standard clients such as web browsers and desktop GIS applications.  GeoServer works with the Open Geospatial Consortium (OGC) standards Web Feature Service (WFS), Web Coverage Service (WCS), Web Processing Service (WPS) and Web Map Service (WMS) standards.&lt;br /&gt;
:* The GeoServer team asks applicants to introduce themselves on the geoserver-devel list ( Communicating in public is a key success factor to open source development )&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Geotools-logo.png|50px|right]]&lt;br /&gt;
* [http://docs.codehaus.org/display/GEOTOOLS/Google+Summer+of+Code ''GSOC'']:  [http://live.osgeo.org/en/overview/geotools_overview.html '''GeoTools'''] GeoTools is an open source Java library for working with geospatial data, including both data access, data structures, processing and a powerful rendering engine. GeoTools is a modular library used in a wide range of web service, command line tools and desktop applications.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:ZOO-Project-mini.png|right]]&lt;br /&gt;
* [http://www.zoo-project.org/trac/wiki/ZOO_GSoC_Idea '''ZOO-Project''' Ideas]: [http://www.zoo-project.org ZOO-Project] is a WPS open source project released under a MIT/X-11 style license. It provides support for WPS 1.0.0 and 2.0.0 versions  and is able to handle services implemented in various programming languages.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
We expect ideas also from [http://live.osgeo.org/en/overview/mapbender_overview.html MapBender], [http://live.osgeo.org/en/overview/geomoose_overview.html GeoMOOSE], [http://mapserver.org/ MapServer], ...&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Osgeo-live.png|150px|right]]&lt;br /&gt;
* [http://wiki.osgeo.org/wiki/Live_GIS_GSoC_2016 '''Osgeo-Live''' SoC Ideas]: [http://live.osgeo.org/en/index.html OSGeo-Live] is a self-contained bootable DVD, USB thumb drive or Virtual Machine based on Lubuntu, that allows you to try a wide variety of open source geospatial software without installing anything. It is composed entirely of free software, allowing it to be freely distributed, duplicated and passed around. It provides pre-configured applications for a range of geospatial use cases, including storage, publishing, viewing, analysis and manipulation of data. It also contains sample datasets and documentation.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
=== OSGeo Foundation community projects ===&lt;br /&gt;
&lt;br /&gt;
[[Image:Pgrouting-logo.png|60px|right]]&lt;br /&gt;
* [https://github.com/pgRouting/pgrouting/wiki/GSoC-Ideas '''pgRouting''' Ideas]: [http://pgrouting.org pgRouting] extends the PostGIS / PostgreSQL geospatial database to provide geospatial routing functionality and more.&lt;br /&gt;
&lt;br /&gt;
=== Guest projects ===&lt;br /&gt;
&lt;br /&gt;
Like-minded geospatial projects to take part under OSGeo umbrella. If you wish your software project to be listed here, please contact the GSoC admin team, by sending an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Nasa meatball logo.png|60px|right]]&lt;br /&gt;
* [[NASA-ESA_WebWorldWind_GSoC_2017_Ideas | '''NASA-ESA Web World Wind''']] Ideas: [https://webworldwind.org/ NASA-ESA Web World Wind] is a 3D virtual globe API for HTML5 and JavaScript.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
* [[OL3-Google-Maps-GSoC_2017_Ideas | '''OL3-Google-Maps''']] ideas, [http://mapgears.github.io/ol3-google-maps/ OL3-Google-Maps] is a library that allows the use of the Google Maps API within OpenLayers using JavaScript.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Oba_logo.png|60px|right]]&lt;br /&gt;
* [https://github.com/OneBusAway/onebusaway-application-modules/wiki/Google-Summer-of-Code-2017 '''OneBusAway''' Ideas]: The [http://onebusaway.org/ OneBusAway] open source project is a consortium of representatives from public sector  transit agencies, commercial firms, academic research representatives, and interested individuals, aiming at delivering robust real-time applications that meet the needs of transit providers and academic researchers.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Don't see in the list the project you're interested in? ===&lt;br /&gt;
&lt;br /&gt;
Contact them in their developers mailing list! Feel free to propose your own idea and get feedback!&lt;br /&gt;
&lt;br /&gt;
== I want to apply as a student ==&lt;br /&gt;
&lt;br /&gt;
Before applying as a student, check out the [[Google Summer of Code Recommendations for Students]] page.&lt;br /&gt;
&lt;br /&gt;
=== Which project do I choose? ===&lt;br /&gt;
&lt;br /&gt;
Most of the software projects are available pre-built on our Live demo { DVD | USB stick | VirtualMachine } with project overviews and short tutorials where you can try everything out.&lt;br /&gt;
: View the documents and download the ISO from http://live.osgeo.org&lt;br /&gt;
[[File:Osgeolive wordle.png|500px|center]]&lt;br /&gt;
&lt;br /&gt;
=== Important dates ===&lt;br /&gt;
&lt;br /&gt;
* [https://developers.google.com/open-source/gsoc/timeline '''The official timeline''']&lt;br /&gt;
&lt;br /&gt;
[Back to [[Google Summer of Code 2018]] @ OSGeo]&lt;br /&gt;
[[Category: Google Summer of Code]]&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2018_Ideas&amp;diff=113232</id>
		<title>Google Summer of Code 2018 Ideas</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2018_Ideas&amp;diff=113232"/>
		<updated>2018-01-18T16:26:03Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: gvSIG project added to participate&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;center&amp;gt;&lt;br /&gt;
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] &amp;lt;font size=&amp;quot;+3&amp;quot;&amp;gt; @ &amp;lt;/font&amp;gt; &lt;br /&gt;
[[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]&lt;br /&gt;
&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
-----&lt;br /&gt;
* Back to the main OSGeo [[Google Summer of Code 2018]] wiki page.&lt;br /&gt;
&lt;br /&gt;
* See also ideas from [[Google Summer of Code 2016 Ideas|2017]], [[Google Summer of Code 2016 Ideas|2016]], [[Google Summer of Code 2015 Ideas|2015]], [[Google Summer of Code 2014 Ideas|2014]], [[Google Summer of Code 2013 Ideas|2013]], [[Google Summer of Code 2012 Ideas|2012]], [[Google Summer of Code 2011 Ideas|2011]], [[Google Summer of Code 2010 Ideas|2010]], [[Google_Summer_of_Code_2009_Ideas|2009]], [[2008_SoC_Merged_Ideas|2008]], [[2007_SoC_Merged_Ideas|2007]].&lt;br /&gt;
-----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== OSGeo Google Summer of Code 2018 ==&lt;br /&gt;
&lt;br /&gt;
The [http://www.osgeo.org Open Source Geospatial Foundation] would like to extend a welcome to all SoC students. On this page you will find links to a host of ideas organized by project. You will find ideas ranging from the depths of computer science graph theory to the heights of visualization. One thing all these ideas have in common is lots and lots of spatial data.&lt;br /&gt;
&lt;br /&gt;
These ideas are '''*only*''' to motivate you, and serve as example of the kind of hills we want to charge up. Your own ideas are more than welcomed - they are encouraged. We view you as the next wave of open source leaders and the future of the geospatial industry; show us what you've got!&lt;br /&gt;
&lt;br /&gt;
* '''Students: check out the [[Google Summer of Code Recommendations for Students]] page. If you need more information on how to apply you can contact all the mentors via the OSGeo-SoC mailing list''' ([[#How to get in contact via mailing lists|see below]]) And look at [https://developers.google.com/open-source/gsoc/help/responsibilities GSoC Roles and Responsibilities ] to understand a successfull teamwork and interplay of project, mentors and students. &lt;br /&gt;
&lt;br /&gt;
* There is a [https://developers.google.com/open-source/soc/resources/flyers Google SoC flyer] to look at and post in appropriate places.&lt;br /&gt;
&lt;br /&gt;
* Ok, [[OSGeo]] is involved in working with maps and things, but what kind of projects does it really do? Have a look at the [http://planet.osgeo.org/ live blog feed] to see what people are working on right now.&lt;br /&gt;
&lt;br /&gt;
* Mentors, there's an additional link providing some tips and specifying your responsibilities on the main OSGeo [[Google Summer of Code 2018 Administrative]] wiki page.&lt;br /&gt;
&lt;br /&gt;
== The ideas pages ==&lt;br /&gt;
'''''[Check back often, it's a work in progress]'''''&lt;br /&gt;
&lt;br /&gt;
To add your page, &amp;lt;strong&amp;gt;please contact the GSoC admin team&amp;lt;/strong&amp;gt; to let them know of your ideas page, by sending an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]&lt;br /&gt;
&lt;br /&gt;
Each participating project's list of ideas is on the respective projects' wikis, with a short description of the project and what type of students would be interested in it:&lt;br /&gt;
&lt;br /&gt;
=== OSGeo Foundation graduated projects ===&lt;br /&gt;
&lt;br /&gt;
''More coming soon: Get started talking to your favorite project's development team today!''&lt;br /&gt;
&lt;br /&gt;
[[Image:logo-grass.png|60px|right]]&lt;br /&gt;
* [https://trac.osgeo.org/grass/wiki/GSoC/2018 '''GRASS GIS''' SoC Ideas]: [http://grass.osgeo.org GRASS GIS] is an open source GIS focusing on analysis, modeling and visualization. It is  a collection of modules written in C and Python and has a GUI written in wxPython. If you know Python, or want to implement algorithms in C, take a look! &lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-qgis.png|60px|right]]&lt;br /&gt;
* [https://hub.qgis.org/wiki/quantum-gis/Google_Summer_of_Code_2017 '''QGIS''' SoC Ideas]: [http://www.qgis.org QGIS] is a user friendly Open Source Geographic Information System (GIS) that runs on Linux, Unix, Mac OSX, and Windows. QGIS supports vector, raster, and database formats. It is written in C++ and Python.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-gdal.png|60px|right]]&lt;br /&gt;
* [http://trac.osgeo.org/gdal/wiki/SummerOfCode '''GDAL''' Ideas]: [http://www.gdal.org GDAL] is a C++ library for reading and writing geospatial data raster and vector formats.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
* [http://trac.osgeo.org/osgeo4w/wiki/Reports '''OSGeo4W''']: -  OSGeo4W is a binary distribution of a broad set of open source geospatial software for Win32 environments (Windows 7, XP, etc).&lt;br /&gt;
[[Image:Logo-osgeo4w-mini.png|60px|right]]&lt;br /&gt;
:* ''Idea'': We need to extend support to x64 based platforms to handle larger datasets and circumvent memory restrictions. This is a distribution and packaging project which will involve most/all of OSGeo member projects. (''ed. note: keep in mind that to fulfill GSoC requirements each project must have a majority coding component, so lots of scripting, testing, and Makefiles!'')&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
[[Image:logo-gvSIG.png|60px|right]]&lt;br /&gt;
* [[GvSIG_GSoC_2017_Ideas|'''gvSIG''' Ideas]]: gvSIG is a free GIS project for [http://www.gvsig.com/en/web/guest/products/gvsig-desktop Desktop]. The gvSIG project looks for students with Java or Python skills that want to develop new ideas on this software. &lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Pycsw-logo.png|60px|right]]&lt;br /&gt;
* [https://github.com/geopython/pycsw/wiki/OSGeo-GSoC#2017'''pycsw''' Ideas]: [http://pycsw.org pycsw] is an OGC CSW server implementation written in Python, and provides a metadata and catalogue component for spatial data infrastructures.  The pycsw project is looking for students interested in Python and search, come join us!&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-opticks.png|right]]&lt;br /&gt;
* [http://opticks.org/confluence/display/opticksDev/Google+Summer+of+Code '''Opticks''' Ideas]: [http://opticks.org/ Opticks] is an extensible [http://en.wikipedia.org/wiki/Remote_sensing remote sensing] and imagery analysis desktop application. It provides a framework to process remote sensing data such as [http://en.wikipedia.org/wiki/Hyperspectral_imaging Hyperspectral] (HSI), [http://en.wikipedia.org/wiki/Multi-spectral_image Multispectral] (MSI), and [http://en.wikipedia.org/wiki/Synthetic_aperture_radar Synthetic aperture radar] (SAR) imagery and video. The application is written in C++ and licensed under LGPL v2.1. Extensions are written using C++ or Python. You can review the [http://opticks.org/confluence/display/opticksExt/All+Opticks+Extensions available extensions] and [http://opticks.org/confluence/display/opticks/Feature+Tour+-+Your+Data feature tour] to get a better idea of what Opticks can do.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!-- &lt;br /&gt;
[[Image:logo-postgis.png|60px|right]] &lt;br /&gt;
* [http://trac.osgeo.org/postgis/wiki/GoogleSummerCode '''PostGIS''' Ideas]: [http://postgis.net PostGIS] spatially enables the popular PostgreSQL object-relational database, allowing it to be used as a back-end database for geographic information systems (GIS) and web-mapping applications.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-ossim.png|90px|right]]&lt;br /&gt;
* [https://trac.osgeo.org/ossim/wiki/GSoC_2015 '''OSSIM''' SoC Ideas]: [http://trac.osgeo.org/ossim/wiki OSSIM] Open Source Software Image Map (OSSIM) is a high performance engine for remote sensing, image processing, geographical information systems and photogrammetry. The software has been under active development since 1996 and is deployed across a number of private, federal and civilian agencies. It is written in C++.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Logo_OTB.png|60px|right]]&lt;br /&gt;
* [http://wiki.orfeo-toolbox.org/index.php/Proposals_for_GSoC_2015 '''OTB''' SoC Ideas]: [http://www.orfeo-toolbox.org ORFEO ToolBox] (OTB) is an open source library for remote sensing image processing.Targeted algorithms for high resolution optical images (Pleiades, SPOT, QuickBird, WorldView, Landsat, Ikonos), hyperspectral sensors (Hyperion) or SAR (TerraSarX, ERS, Palsar) are available. The software has been under active development since 2006 and is written in C++ and it includes also side projects also open source with GUI like Monteverdi. OTB has recently started the incubation process into OSGeo.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Mapserver.png|100px|right]]&lt;br /&gt;
* [http://wiki.osgeo.org/wiki/MapServer_2015_SOC_Ideas '''Mapserver''' SoC Ideas]: MapServer is a Web Mapping Engine; an Open Source platform for publishing spatial data and interactive mapping applications to the web.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
=== OSGeo Foundation Incubation projects ===&lt;br /&gt;
&lt;br /&gt;
[[Image:Logo-istSOS.png|100px|right]]&lt;br /&gt;
* [https://sourceforge.net/p/istsos/wiki/GSoC_ideas_2018/ '''istSOS''' Ideas]: [http://sourceforge.net/projects/istsos/ istSOS] is a complete sensor data management system for acquiring, storing and dispatching time-series observations. istSOS is compliant with the Sensor Observation Service (SOS) version 1.0 and 2.0 standard from the Open Geospatial Consortium (OGC) and offers unique extended capabilities to support scientific data analyses (integrated quality assurance, RESTful API, on the fly processing with virtual procedures, remote data aggregation and time-space re-projection etc.). istSOS core libraries are written in Python while it easy to use interface is Web based.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Pywps logo.png|80px|right]]&lt;br /&gt;
* [https://github.com/geopython/pywps/wiki/GSoC-2017-ideas '''PyWPS''' Ideas]: [http://pywps.org/ PyWPS] is an implementation of the Web Processing Service standard from the Open Geospatial Consortium. PyWPS is written in Python. PyWPS enables integration, publishing and execution of Python processes via the WPS standard.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-geos.png|60px|right]]&lt;br /&gt;
* [http://trac.osgeo.org/geos/wiki/GSoC '''GEOS''' Ideas]: GEOS (Geometry Engine - Open Source) is a C++ port of the JTS Topology Suite (JTS). It includes the OpenGIS Simple Features for SQL spatial predicate functions and spatial operators, as well as specific JTS enhanced topology functions.&lt;br /&gt;
--&amp;gt; &lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-geoserver-crop.png|50px|right]]&lt;br /&gt;
* [https://github.com/geoserver/geoserver/wiki/GSOC-Ideas GSOC Ideas]: [http://live.osgeo.org/en/overview/geoserver_overview.html '''GeoServer'''] is a web server that allows you to serve maps and data from a variety of formats to standard clients such as web browsers and desktop GIS applications.  GeoServer works with the Open Geospatial Consortium (OGC) standards Web Feature Service (WFS), Web Coverage Service (WCS), Web Processing Service (WPS) and Web Map Service (WMS) standards.&lt;br /&gt;
:* The GeoServer team asks applicants to introduce themselves on the geoserver-devel list ( Communicating in public is a key success factor to open source development )&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Geotools-logo.png|50px|right]]&lt;br /&gt;
* [http://docs.codehaus.org/display/GEOTOOLS/Google+Summer+of+Code ''GSOC'']:  [http://live.osgeo.org/en/overview/geotools_overview.html '''GeoTools'''] GeoTools is an open source Java library for working with geospatial data, including both data access, data structures, processing and a powerful rendering engine. GeoTools is a modular library used in a wide range of web service, command line tools and desktop applications.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:ZOO-Project-mini.png|right]]&lt;br /&gt;
* [http://www.zoo-project.org/trac/wiki/ZOO_GSoC_Idea '''ZOO-Project''' Ideas]: [http://www.zoo-project.org ZOO-Project] is a WPS open source project released under a MIT/X-11 style license. It provides support for WPS 1.0.0 and 2.0.0 versions  and is able to handle services implemented in various programming languages.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
We expect ideas also from [http://live.osgeo.org/en/overview/mapbender_overview.html MapBender], [http://live.osgeo.org/en/overview/geomoose_overview.html GeoMOOSE], [http://mapserver.org/ MapServer], ...&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Osgeo-live.png|150px|right]]&lt;br /&gt;
* [http://wiki.osgeo.org/wiki/Live_GIS_GSoC_2016 '''Osgeo-Live''' SoC Ideas]: [http://live.osgeo.org/en/index.html OSGeo-Live] is a self-contained bootable DVD, USB thumb drive or Virtual Machine based on Lubuntu, that allows you to try a wide variety of open source geospatial software without installing anything. It is composed entirely of free software, allowing it to be freely distributed, duplicated and passed around. It provides pre-configured applications for a range of geospatial use cases, including storage, publishing, viewing, analysis and manipulation of data. It also contains sample datasets and documentation.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
=== OSGeo Foundation community projects ===&lt;br /&gt;
&lt;br /&gt;
[[Image:Pgrouting-logo.png|60px|right]]&lt;br /&gt;
* [https://github.com/pgRouting/pgrouting/wiki/GSoC-Ideas '''pgRouting''' Ideas]: [http://pgrouting.org pgRouting] extends the PostGIS / PostgreSQL geospatial database to provide geospatial routing functionality and more.&lt;br /&gt;
&lt;br /&gt;
=== Guest projects ===&lt;br /&gt;
&lt;br /&gt;
Like-minded geospatial projects to take part under OSGeo umbrella. If you wish your software project to be listed here, please contact the GSoC admin team, by sending an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Nasa meatball logo.png|60px|right]]&lt;br /&gt;
* [[NASA-ESA_WebWorldWind_GSoC_2017_Ideas | '''NASA-ESA Web World Wind''']] Ideas: [https://webworldwind.org/ NASA-ESA Web World Wind] is a 3D virtual globe API for HTML5 and JavaScript.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
* [[OL3-Google-Maps-GSoC_2017_Ideas | '''OL3-Google-Maps''']] ideas, [http://mapgears.github.io/ol3-google-maps/ OL3-Google-Maps] is a library that allows the use of the Google Maps API within OpenLayers using JavaScript.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;br /&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Oba_logo.png|60px|right]]&lt;br /&gt;
* [https://github.com/OneBusAway/onebusaway-application-modules/wiki/Google-Summer-of-Code-2017 '''OneBusAway''' Ideas]: The [http://onebusaway.org/ OneBusAway] open source project is a consortium of representatives from public sector  transit agencies, commercial firms, academic research representatives, and interested individuals, aiming at delivering robust real-time applications that meet the needs of transit providers and academic researchers.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Don't see in the list the project you're interested in? ===&lt;br /&gt;
&lt;br /&gt;
Contact them in their developers mailing list! Feel free to propose your own idea and get feedback!&lt;br /&gt;
&lt;br /&gt;
== I want to apply as a student ==&lt;br /&gt;
&lt;br /&gt;
Before applying as a student, check out the [[Google Summer of Code Recommendations for Students]] page.&lt;br /&gt;
&lt;br /&gt;
=== Which project do I choose? ===&lt;br /&gt;
&lt;br /&gt;
Most of the software projects are available pre-built on our Live demo { DVD | USB stick | VirtualMachine } with project overviews and short tutorials where you can try everything out.&lt;br /&gt;
: View the documents and download the ISO from http://live.osgeo.org&lt;br /&gt;
[[File:Osgeolive wordle.png|500px|center]]&lt;br /&gt;
&lt;br /&gt;
=== Important dates ===&lt;br /&gt;
&lt;br /&gt;
* [https://developers.google.com/open-source/gsoc/timeline '''The official timeline''']&lt;br /&gt;
&lt;br /&gt;
[Back to [[Google Summer of Code 2018]] @ OSGeo]&lt;br /&gt;
[[Category: Google Summer of Code]]&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=GvSIG_GSoC_2017_Ideas&amp;diff=105813</id>
		<title>GvSIG GSoC 2017 Ideas</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=GvSIG_GSoC_2017_Ideas&amp;diff=105813"/>
		<updated>2017-03-22T13:10:15Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Use this page to jot down and develop any good idea for the [[Google Summer of Code 2017|2017]] program with gvSIG project. Please, use the gvSIG mailing lists for discussion and check [[Google Summer of Code 2016|2016]], [[Google Summer of Code 2015|2015]], [[Google Summer of Code 2014|2014]], [[GvSIG GSoC 2013 Ideas|2013]], [[GvSIG GSoC 2012 Ideas|2012]], [[GvSIG GSoC 2011 Ideas|2011]], [[GvSIG GSoC 2010 Ideas|2010]], [[GvSIG GSoC 2009 Ideas|2009]] ideas pages for examples or reference.&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== gvSIG Online plugin for gvSIG desktop ==&lt;br /&gt;
&lt;br /&gt;
* '''Product''': gvSIG Desktop&lt;br /&gt;
* '''Mentors''': César Martínez &lt;br /&gt;
* '''Student''': José Vicente Higón Valero&lt;br /&gt;
&lt;br /&gt;
gvSIG Online is a solution for Spatial Data Infrastructure in open source software. With gvSIG Online a user will be able to do public and private geoportals.&lt;br /&gt;
&lt;br /&gt;
It will allow to add a geoportal of gvSIG Online as a new data source, adding in gvSIG Desktop all the Web Map Services published in this geoportal.&lt;br /&gt;
&lt;br /&gt;
== Educational games addon for gvSIG Batoví/Educa==&lt;br /&gt;
&lt;br /&gt;
* '''Product''': gvSIG Batoví&lt;br /&gt;
* '''Mentors''': Nadia Chaer, Francisco Puga&lt;br /&gt;
* '''Student''': Carlos I. Colombana&lt;br /&gt;
&lt;br /&gt;
The main idea behind this project is to develop an addon which allows to '''''create/play''''' educational games. Also generate documentation specially oriented to users without any programming knowledge.&lt;br /&gt;
&lt;br /&gt;
The code will be mainly developed in Jython, an implementation of the Python programming language written in Java, through the scripting module of the gvSIG desktop 2.x branch.&lt;br /&gt;
&lt;br /&gt;
The developed tools will be used in geography and maps learning.&lt;br /&gt;
&lt;br /&gt;
== Data model for visualizations in gvSIG ==&lt;br /&gt;
&lt;br /&gt;
* '''Product''': gvSIG Desktop&lt;br /&gt;
* '''Mentors''': Joaquín del Cerro&lt;br /&gt;
* '''Student''': Óscar Martínez Olmos&lt;br /&gt;
&lt;br /&gt;
Data model for visualizations in gvSIG is a project that will allow the users to create data models to enhance data visualizations through different related data sources.&lt;br /&gt;
&lt;br /&gt;
This model will contain the parameters of the relations between different data sources that the user wants to visualize. It will allow gvSIG to show info not just about a specified object but all the info related to it, making far easy to explore our data. &lt;br /&gt;
&lt;br /&gt;
For example, it will be possible to create a relation for a connection between a shape and a postgres data base through a common field. So, when we ask for its info, it will show its fields info and all its related info through the connections described in the data model.&lt;br /&gt;
&lt;br /&gt;
One part of the project will be to create a visual interface that will allow users without programming skills to create new data models.&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=GvSIG_GSoC_2017_Ideas&amp;diff=104828</id>
		<title>GvSIG GSoC 2017 Ideas</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=GvSIG_GSoC_2017_Ideas&amp;diff=104828"/>
		<updated>2017-01-23T09:17:49Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: gvSIG ideas for 2017&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Use this page to jot down and develop any good idea for the [[Google Summer of Code 2017|2017]] program with gvSIG project. Please, use the gvSIG mailing lists for discussion and check [[Google Summer of Code 2016|2016]], [[Google Summer of Code 2015|2015]], [[Google Summer of Code 2014|2014]], [[GvSIG GSoC 2013 Ideas|2013]], [[GvSIG GSoC 2012 Ideas|2012]], [[GvSIG GSoC 2011 Ideas|2011]], [[GvSIG GSoC 2010 Ideas|2010]], [[GvSIG GSoC 2009 Ideas|2009]] ideas pages for examples or reference.&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== CARTO plugin for gvSIG desktop ==&lt;br /&gt;
&lt;br /&gt;
* '''Product''': gvSIG Desktop&lt;br /&gt;
* '''Mentors''': If applicable &lt;br /&gt;
* '''Student''': If applicable&lt;br /&gt;
&lt;br /&gt;
[http://carto.com/ CARTO] is a Software as a Service (SaaS) cloud computing platform that provides GIS and web mapping tools for display in a web browser. &lt;br /&gt;
&lt;br /&gt;
It will allow to view, create, edit or delete data from CARTO accounts using gvSIG Desktop.&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2017_Ideas&amp;diff=104825</id>
		<title>Google Summer of Code 2017 Ideas</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2017_Ideas&amp;diff=104825"/>
		<updated>2017-01-23T09:01:57Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: /* The ideas pages */ Correction of the link at gvSIG Project&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;center&amp;gt;&lt;br /&gt;
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] &amp;lt;font size=&amp;quot;+3&amp;quot;&amp;gt; @ &amp;lt;/font&amp;gt; &lt;br /&gt;
[[Image:OSGeo_300_127_pixel.png|300px|link=http://www.osgeo.org]]&lt;br /&gt;
&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
-----&lt;br /&gt;
* Back to the main OSGeo [[Google Summer of Code 2017]] wiki page.&lt;br /&gt;
&lt;br /&gt;
* See also ideas from [[Google Summer of Code 2016 Ideas|2016]], [[Google Summer of Code 2015 Ideas|2015]], [[Google Summer of Code 2014 Ideas|2014]], [[Google Summer of Code 2013 Ideas|2013]], [[Google Summer of Code 2012 Ideas|2012]], [[Google Summer of Code 2011 Ideas|2011]], [[Google Summer of Code 2010 Ideas|2010]], [[Google_Summer_of_Code_2009_Ideas|2009]], [[2008_SoC_Merged_Ideas|2008]], [[2007_SoC_Merged_Ideas|2007]].&lt;br /&gt;
-----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== OSGeo Google Summer of Code 2017 ==&lt;br /&gt;
&lt;br /&gt;
The [http://www.osgeo.org Open Source Geospatial Foundation] would like to extend a welcome to all SoC students. On this page you will find links to a host of ideas organized by project. You will find ideas ranging from the depths of computer science graph theory to the heights of visualization. One thing all these ideas have in common is lots and lots of spatial data.&lt;br /&gt;
&lt;br /&gt;
These ideas are '''*only*''' to motivate you, and serve as example of the kind of hills we want to charge up. Your own ideas are more than welcomed - they are encouraged. We view you as the next wave of open source leaders and the future of the geospatial industry; show us what you've got!&lt;br /&gt;
&lt;br /&gt;
* '''Students: check out the [[Google Summer of Code Recommendations for Students]] page. If you need more information on how to apply you can contact all the mentors via the OSGeo-SoC mailing list''' ([[#How to get in contact via mailing lists|see below]])&lt;br /&gt;
&lt;br /&gt;
* There is a [https://developers.google.com/open-source/soc/resources/flyers Google SoC flyer] to look at and post in appropriate places.&lt;br /&gt;
&lt;br /&gt;
* Ok, [[OSGeo]] is involved in working with maps and things, but what kind of projects does it really do? Have a look at the [http://planet.osgeo.org/ live blog feed] to see what people are working on right now.&lt;br /&gt;
&lt;br /&gt;
* Mentors, there's an additional link providing some tips and specifying your responsibilities on the main OSGeo [[Google_Summer_of_Code_2017_Administrative]] wiki page.&lt;br /&gt;
&lt;br /&gt;
== The ideas pages ==&lt;br /&gt;
'''''[Check back often, it's a work in progress]'''''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Each participating project's list of ideas is on the respective projects' wikis, with a short description of the project and what type of students would be interested in it:&lt;br /&gt;
&lt;br /&gt;
=== OSGeo Foundation member projects ===&lt;br /&gt;
&lt;br /&gt;
''More coming soon: Get started talking to your favorite project's development team today!''&lt;br /&gt;
&lt;br /&gt;
[[Image:logo-grass.png|60px|right]]&lt;br /&gt;
* [https://trac.osgeo.org/grass/wiki/GSoC/2017 '''GRASS GIS''' SoC Ideas]: [http://grass.osgeo.org GRASS GIS] is an open source GIS focusing on analysis, modeling and visualization. It is  a collection of modules written in C and Python and has a GUI written in wxPython. If you know Python, or want to implement algorithms in C, take a look!&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-qgis.png|60px|right]]&lt;br /&gt;
* [http://hub.qgis.org/wiki/quantum-gis/Google_Summer_of_Code_2016 '''QGIS''' SoC Ideas]: [http://www.qgis.org QGIS] is a user friendly Open Source Geographic Information System (GIS) that runs on Linux, Unix, Mac OSX, and Windows. QGIS supports vector, raster, and database formats. It is written in C++ and Python.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-gdal.png|60px|right]]&lt;br /&gt;
* [http://trac.osgeo.org/gdal/wiki/SummerOfCode '''GDAL''' Ideas]: [http://www.gdal.org GDAL] is a C++ library for reading and writing geospatial data raster and vector formats.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
* [http://trac.osgeo.org/osgeo4w/wiki/Reports '''OSGeo4W''']: -  OSGeo4W is a binary distribution of a broad set of open source geospatial software for Win32 environments (Windows 7, XP, etc).&lt;br /&gt;
[[Image:Logo-osgeo4w-mini.png|60px|right]]&lt;br /&gt;
:* ''Idea'': We need to extend support to x64 based platforms to handle larger datasets and circumvent memory restrictions. This is a distribution and packaging project which will involve most/all of OSGeo member projects. (''ed. note: keep in mind that to fulfill GSoC requirements each project must have a majority coding component, so lots of scripting, testing, and Makefiles!'')&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Image:logo-gvSIG.png|60px|right]]&lt;br /&gt;
* [[GvSIG_GSoC_2017_Ideas|'''gvSIG''' Ideas]]: gvSIG is a free GIS project for [http://www.gvsig.com/en/web/guest/products/gvsig-desktop Desktop]. The gvSIG project looks for students with Java or Python skills that want to develop new ideas on this software. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-opticks.png|right]]&lt;br /&gt;
* [http://opticks.org/confluence/display/opticksDev/Google+Summer+of+Code '''Opticks''' Ideas]: [http://opticks.org/ Opticks] is an extensible [http://en.wikipedia.org/wiki/Remote_sensing remote sensing] and imagery analysis desktop application. It provides a framework to process remote sensing data such as [http://en.wikipedia.org/wiki/Hyperspectral_imaging Hyperspectral] (HSI), [http://en.wikipedia.org/wiki/Multi-spectral_image Multispectral] (MSI), and [http://en.wikipedia.org/wiki/Synthetic_aperture_radar Synthetic aperture radar] (SAR) imagery and video. The application is written in C++ and licensed under LGPL v2.1. Extensions are written using C++ or Python. You can review the [http://opticks.org/confluence/display/opticksExt/All+Opticks+Extensions available extensions] and [http://opticks.org/confluence/display/opticks/Feature+Tour+-+Your+Data feature tour] to get a better idea of what Opticks can do.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!-- &lt;br /&gt;
[[Image:logo-postgis.png|60px|right]] &lt;br /&gt;
* [http://trac.osgeo.org/postgis/wiki/GoogleSummerCode '''PostGIS''' Ideas]: [http://postgis.net PostGIS] spatially enables the popular PostgreSQL object-relational database, allowing it to be used as a back-end database for geographic information systems (GIS) and web-mapping applications.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-ossim.png|90px|right]]&lt;br /&gt;
* [https://trac.osgeo.org/ossim/wiki/GSoC_2015 '''OSSIM''' SoC Ideas]: [http://trac.osgeo.org/ossim/wiki OSSIM] Open Source Software Image Map (OSSIM) is a high performance engine for remote sensing, image processing, geographical information systems and photogrammetry. The software has been under active development since 1996 and is deployed across a number of private, federal and civilian agencies. It is written in C++.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Logo_OTB.png|60px|right]]&lt;br /&gt;
* [http://wiki.orfeo-toolbox.org/index.php/Proposals_for_GSoC_2015 '''OTB''' SoC Ideas]: [http://www.orfeo-toolbox.org ORFEO ToolBox] (OTB) is an open source library for remote sensing image processing.Targeted algorithms for high resolution optical images (Pleiades, SPOT, QuickBird, WorldView, Landsat, Ikonos), hyperspectral sensors (Hyperion) or SAR (TerraSarX, ERS, Palsar) are available. The software has been under active development since 2006 and is written in C++ and it includes also side projects also open source with GUI like Monteverdi. OTB has recently started the incubation process into OSGeo.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Mapserver.png|100px|right]]&lt;br /&gt;
* [http://wiki.osgeo.org/wiki/MapServer_2015_SOC_Ideas '''Mapserver''' SoC Ideas]: MapServer is a Web Mapping Engine; an Open Source platform for publishing spatial data and interactive mapping applications to the web.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Logo-istSOS.png|100px|right]]&lt;br /&gt;
* [https://sourceforge.net/p/istsos/wiki/GSoC_ideas_2016 '''istSOS''' Ideas]: [http://sourceforge.net/projects/istsos/ istSOS] is a complete sensor data management system for acquiring, storing and dispatching time-series observations. istSOS is compliant with the Sensor Observation Service (SOS) version 1.0 and 2.0 standard from the Open Geospatial Consortium (OGC) and offers unique extended capabilities to support scientific data analyses (integrated quality assurance, RESTful API, on the fly processing with virtual procedures, remote data aggregation and time-space re-projection etc.). istSOS core libraries are written in Python while it easy to use interface is Web based.&lt;br /&gt;
--&amp;gt; &lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-geos.png|60px|right]]&lt;br /&gt;
* [http://trac.osgeo.org/geos/wiki/GSoC '''GEOS''' Ideas]: GEOS (Geometry Engine - Open Source) is a C++ port of the JTS Topology Suite (JTS). It includes the OpenGIS Simple Features for SQL spatial predicate functions and spatial operators, as well as specific JTS enhanced topology functions.&lt;br /&gt;
--&amp;gt; &lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-geoserver-crop.png|50px|right]]&lt;br /&gt;
* [https://github.com/geoserver/geoserver/wiki/GSOC-Ideas GSOC Ideas]: [http://live.osgeo.org/en/overview/geoserver_overview.html '''GeoServer'''] is a web server that allows you to serve maps and data from a variety of formats to standard clients such as web browsers and desktop GIS applications.  GeoServer works with the Open Geospatial Consortium (OGC) standards Web Feature Service (WFS), Web Coverage Service (WCS), Web Processing Service (WPS) and Web Map Service (WMS) standards.&lt;br /&gt;
:* The GeoServer team asks applicants to introduce themselves on the geoserver-devel list ( Communicating in public is a key success factor to open source development )&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Geotools-logo.png|50px|right]]&lt;br /&gt;
* [http://docs.codehaus.org/display/GEOTOOLS/Google+Summer+of+Code ''GSOC'']:  [http://live.osgeo.org/en/overview/geotools_overview.html '''GeoTools'''] GeoTools is an open source Java library for working with geospatial data, including both data access, data structures, processing and a powerful rendering engine. GeoTools is a modular library used in a wide range of web service, command line tools and desktop applications.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:ZOO-Project-mini.png|right]]&lt;br /&gt;
* [http://www.zoo-project.org/trac/wiki/ZOO_GSoC_Idea '''ZOO-Project''' Ideas]: [http://www.zoo-project.org ZOO-Project] is a WPS open source project released under a MIT/X-11 style license. It provides support for WPS 1.0.0 and 2.0.0 versions  and is able to handle services implemented in various programming languages.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
We expect ideas also from [http://live.osgeo.org/en/overview/mapbender_overview.html MapBender], [http://live.osgeo.org/en/overview/geomoose_overview.html GeoMOOSE], [http://mapserver.org/ MapServer], ...&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Osgeo-live.png|150px|right]]&lt;br /&gt;
* [http://wiki.osgeo.org/wiki/Live_GIS_GSoC_2016 '''Osgeo-Live''' SoC Ideas]: [http://live.osgeo.org/en/index.html OSGeo-Live] is a self-contained bootable DVD, USB thumb drive or Virtual Machine based on Lubuntu, that allows you to try a wide variety of open source geospatial software without installing anything. It is composed entirely of free software, allowing it to be freely distributed, duplicated and passed around. It provides pre-configured applications for a range of geospatial use cases, including storage, publishing, viewing, analysis and manipulation of data. It also contains sample datasets and documentation.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Guest projects ===&lt;br /&gt;
&lt;br /&gt;
Like-minded geospatial projects to take part under OSGeo umbrella. If you wish your software project to be listed here, please contact the GSoC admin team, by sending an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
=== See also ===&lt;br /&gt;
&lt;br /&gt;
Other like minded projects do not participate to GSoC under OSGeo umbrella, but with their own organization. You may want to visit also their page:&lt;br /&gt;
&lt;br /&gt;
[[Image:Logo-osm6.png|60px|right]] &lt;br /&gt;
* [http://wiki.openstreetmap.org/wiki/Google_Summer_of_Code/2015/Project_Ideas '''OpenStreetMap''' Ideas]: [http://osm.org/ OSM] is a project aimed squarely at creating and providing free geographic data such as street maps to anyone who wants them. The project was started because most maps you think of as free actually have legal or technical restrictions on their use, holding back people from using them in creative, productive or unexpected ways.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Don't see in the list the project you're interested in? ===&lt;br /&gt;
&lt;br /&gt;
Contact them in their developers mailing list! Feel free to propose your own idea and get feedback!&lt;br /&gt;
&lt;br /&gt;
== I want to apply as a student ==&lt;br /&gt;
&lt;br /&gt;
Before applying as a student, check out the [[Google Summer of Code Recommendations for Students]] page.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Which project do I choose? ===&lt;br /&gt;
&lt;br /&gt;
Most of the software projects are available pre-built on our Live demo { DVD | USB stick | VirtualMachine } with project overviews and short tutorials where you can try everything out.&lt;br /&gt;
: View the documents and download the ISO from http://live.osgeo.org&lt;br /&gt;
[[File:Osgeolive wordle.png|500px|center]]&lt;br /&gt;
&lt;br /&gt;
=== Important dates ===&lt;br /&gt;
&lt;br /&gt;
* [https://developers.google.com/open-source/gsoc/timeline '''The official timeline''']&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- {{done}} --&amp;gt;&lt;br /&gt;
* Feb 27: Google announces accepted organizations.&lt;br /&gt;
: Please start talking to the dev communities you are interested in ''now''.&lt;br /&gt;
* March 20:  Student applications open.&lt;br /&gt;
: The earlier you start the more probable it is that you will be accepted!&lt;br /&gt;
: ''There is two way feedback during the application process which really helps you improve and clarify your application before the final deadline. The better your involvement with your potential mentors during this period, the better your chances of being selected.''&lt;br /&gt;
* April 3:  Student application deadline.&lt;br /&gt;
* May 4: '''Accepted student proposals are announced and Community Bonding Period begins.'''&lt;br /&gt;
* May 30: '''Coding begins!'''&lt;br /&gt;
: (''you may unofficially start a week or two earlier if you know you'll have to take a week or two off during The Summer or you'll be sitting finals in the first week(s) of the program. This must be reflected in your application timeline'')&lt;br /&gt;
* June 26 - 30: Phase 1 evaluation &lt;br /&gt;
* July 28: Phase 2 evaluation&lt;br /&gt;
* August 21-29: '''Pencils down!'''&lt;br /&gt;
* August 29 - September 5: Final evaluations&lt;br /&gt;
* September 6: Final results announced&lt;br /&gt;
&lt;br /&gt;
[Back to [[Google Summer of Code 2017]] @ OSGeo]&lt;br /&gt;
[[Category: Google Summer of Code]]&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2017_Ideas&amp;diff=104824</id>
		<title>Google Summer of Code 2017 Ideas</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2017_Ideas&amp;diff=104824"/>
		<updated>2017-01-23T09:00:06Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: /* The ideas pages */  gvSIG project included&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;center&amp;gt;&lt;br /&gt;
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] &amp;lt;font size=&amp;quot;+3&amp;quot;&amp;gt; @ &amp;lt;/font&amp;gt; &lt;br /&gt;
[[Image:OSGeo_300_127_pixel.png|300px|link=http://www.osgeo.org]]&lt;br /&gt;
&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
-----&lt;br /&gt;
* Back to the main OSGeo [[Google Summer of Code 2017]] wiki page.&lt;br /&gt;
&lt;br /&gt;
* See also ideas from [[Google Summer of Code 2016 Ideas|2016]], [[Google Summer of Code 2015 Ideas|2015]], [[Google Summer of Code 2014 Ideas|2014]], [[Google Summer of Code 2013 Ideas|2013]], [[Google Summer of Code 2012 Ideas|2012]], [[Google Summer of Code 2011 Ideas|2011]], [[Google Summer of Code 2010 Ideas|2010]], [[Google_Summer_of_Code_2009_Ideas|2009]], [[2008_SoC_Merged_Ideas|2008]], [[2007_SoC_Merged_Ideas|2007]].&lt;br /&gt;
-----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== OSGeo Google Summer of Code 2017 ==&lt;br /&gt;
&lt;br /&gt;
The [http://www.osgeo.org Open Source Geospatial Foundation] would like to extend a welcome to all SoC students. On this page you will find links to a host of ideas organized by project. You will find ideas ranging from the depths of computer science graph theory to the heights of visualization. One thing all these ideas have in common is lots and lots of spatial data.&lt;br /&gt;
&lt;br /&gt;
These ideas are '''*only*''' to motivate you, and serve as example of the kind of hills we want to charge up. Your own ideas are more than welcomed - they are encouraged. We view you as the next wave of open source leaders and the future of the geospatial industry; show us what you've got!&lt;br /&gt;
&lt;br /&gt;
* '''Students: check out the [[Google Summer of Code Recommendations for Students]] page. If you need more information on how to apply you can contact all the mentors via the OSGeo-SoC mailing list''' ([[#How to get in contact via mailing lists|see below]])&lt;br /&gt;
&lt;br /&gt;
* There is a [https://developers.google.com/open-source/soc/resources/flyers Google SoC flyer] to look at and post in appropriate places.&lt;br /&gt;
&lt;br /&gt;
* Ok, [[OSGeo]] is involved in working with maps and things, but what kind of projects does it really do? Have a look at the [http://planet.osgeo.org/ live blog feed] to see what people are working on right now.&lt;br /&gt;
&lt;br /&gt;
* Mentors, there's an additional link providing some tips and specifying your responsibilities on the main OSGeo [[Google_Summer_of_Code_2017_Administrative]] wiki page.&lt;br /&gt;
&lt;br /&gt;
== The ideas pages ==&lt;br /&gt;
'''''[Check back often, it's a work in progress]'''''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Each participating project's list of ideas is on the respective projects' wikis, with a short description of the project and what type of students would be interested in it:&lt;br /&gt;
&lt;br /&gt;
=== OSGeo Foundation member projects ===&lt;br /&gt;
&lt;br /&gt;
''More coming soon: Get started talking to your favorite project's development team today!''&lt;br /&gt;
&lt;br /&gt;
[[Image:logo-grass.png|60px|right]]&lt;br /&gt;
* [https://trac.osgeo.org/grass/wiki/GSoC/2017 '''GRASS GIS''' SoC Ideas]: [http://grass.osgeo.org GRASS GIS] is an open source GIS focusing on analysis, modeling and visualization. It is  a collection of modules written in C and Python and has a GUI written in wxPython. If you know Python, or want to implement algorithms in C, take a look!&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-qgis.png|60px|right]]&lt;br /&gt;
* [http://hub.qgis.org/wiki/quantum-gis/Google_Summer_of_Code_2016 '''QGIS''' SoC Ideas]: [http://www.qgis.org QGIS] is a user friendly Open Source Geographic Information System (GIS) that runs on Linux, Unix, Mac OSX, and Windows. QGIS supports vector, raster, and database formats. It is written in C++ and Python.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-gdal.png|60px|right]]&lt;br /&gt;
* [http://trac.osgeo.org/gdal/wiki/SummerOfCode '''GDAL''' Ideas]: [http://www.gdal.org GDAL] is a C++ library for reading and writing geospatial data raster and vector formats.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
* [http://trac.osgeo.org/osgeo4w/wiki/Reports '''OSGeo4W''']: -  OSGeo4W is a binary distribution of a broad set of open source geospatial software for Win32 environments (Windows 7, XP, etc).&lt;br /&gt;
[[Image:Logo-osgeo4w-mini.png|60px|right]]&lt;br /&gt;
:* ''Idea'': We need to extend support to x64 based platforms to handle larger datasets and circumvent memory restrictions. This is a distribution and packaging project which will involve most/all of OSGeo member projects. (''ed. note: keep in mind that to fulfill GSoC requirements each project must have a majority coding component, so lots of scripting, testing, and Makefiles!'')&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Image:logo-gvSIG.png|60px|right]]&lt;br /&gt;
* [[GvSIG_GSoC_2016_Ideas|'''gvSIG''' Ideas]]: gvSIG is a free GIS project for [http://www.gvsig.com/en/web/guest/products/gvsig-desktop Desktop]. The gvSIG project looks for students with Java or Python skills that want to develop new ideas on this software. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-opticks.png|right]]&lt;br /&gt;
* [http://opticks.org/confluence/display/opticksDev/Google+Summer+of+Code '''Opticks''' Ideas]: [http://opticks.org/ Opticks] is an extensible [http://en.wikipedia.org/wiki/Remote_sensing remote sensing] and imagery analysis desktop application. It provides a framework to process remote sensing data such as [http://en.wikipedia.org/wiki/Hyperspectral_imaging Hyperspectral] (HSI), [http://en.wikipedia.org/wiki/Multi-spectral_image Multispectral] (MSI), and [http://en.wikipedia.org/wiki/Synthetic_aperture_radar Synthetic aperture radar] (SAR) imagery and video. The application is written in C++ and licensed under LGPL v2.1. Extensions are written using C++ or Python. You can review the [http://opticks.org/confluence/display/opticksExt/All+Opticks+Extensions available extensions] and [http://opticks.org/confluence/display/opticks/Feature+Tour+-+Your+Data feature tour] to get a better idea of what Opticks can do.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!-- &lt;br /&gt;
[[Image:logo-postgis.png|60px|right]] &lt;br /&gt;
* [http://trac.osgeo.org/postgis/wiki/GoogleSummerCode '''PostGIS''' Ideas]: [http://postgis.net PostGIS] spatially enables the popular PostgreSQL object-relational database, allowing it to be used as a back-end database for geographic information systems (GIS) and web-mapping applications.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-ossim.png|90px|right]]&lt;br /&gt;
* [https://trac.osgeo.org/ossim/wiki/GSoC_2015 '''OSSIM''' SoC Ideas]: [http://trac.osgeo.org/ossim/wiki OSSIM] Open Source Software Image Map (OSSIM) is a high performance engine for remote sensing, image processing, geographical information systems and photogrammetry. The software has been under active development since 1996 and is deployed across a number of private, federal and civilian agencies. It is written in C++.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Logo_OTB.png|60px|right]]&lt;br /&gt;
* [http://wiki.orfeo-toolbox.org/index.php/Proposals_for_GSoC_2015 '''OTB''' SoC Ideas]: [http://www.orfeo-toolbox.org ORFEO ToolBox] (OTB) is an open source library for remote sensing image processing.Targeted algorithms for high resolution optical images (Pleiades, SPOT, QuickBird, WorldView, Landsat, Ikonos), hyperspectral sensors (Hyperion) or SAR (TerraSarX, ERS, Palsar) are available. The software has been under active development since 2006 and is written in C++ and it includes also side projects also open source with GUI like Monteverdi. OTB has recently started the incubation process into OSGeo.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Mapserver.png|100px|right]]&lt;br /&gt;
* [http://wiki.osgeo.org/wiki/MapServer_2015_SOC_Ideas '''Mapserver''' SoC Ideas]: MapServer is a Web Mapping Engine; an Open Source platform for publishing spatial data and interactive mapping applications to the web.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Logo-istSOS.png|100px|right]]&lt;br /&gt;
* [https://sourceforge.net/p/istsos/wiki/GSoC_ideas_2016 '''istSOS''' Ideas]: [http://sourceforge.net/projects/istsos/ istSOS] is a complete sensor data management system for acquiring, storing and dispatching time-series observations. istSOS is compliant with the Sensor Observation Service (SOS) version 1.0 and 2.0 standard from the Open Geospatial Consortium (OGC) and offers unique extended capabilities to support scientific data analyses (integrated quality assurance, RESTful API, on the fly processing with virtual procedures, remote data aggregation and time-space re-projection etc.). istSOS core libraries are written in Python while it easy to use interface is Web based.&lt;br /&gt;
--&amp;gt; &lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-geos.png|60px|right]]&lt;br /&gt;
* [http://trac.osgeo.org/geos/wiki/GSoC '''GEOS''' Ideas]: GEOS (Geometry Engine - Open Source) is a C++ port of the JTS Topology Suite (JTS). It includes the OpenGIS Simple Features for SQL spatial predicate functions and spatial operators, as well as specific JTS enhanced topology functions.&lt;br /&gt;
--&amp;gt; &lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-geoserver-crop.png|50px|right]]&lt;br /&gt;
* [https://github.com/geoserver/geoserver/wiki/GSOC-Ideas GSOC Ideas]: [http://live.osgeo.org/en/overview/geoserver_overview.html '''GeoServer'''] is a web server that allows you to serve maps and data from a variety of formats to standard clients such as web browsers and desktop GIS applications.  GeoServer works with the Open Geospatial Consortium (OGC) standards Web Feature Service (WFS), Web Coverage Service (WCS), Web Processing Service (WPS) and Web Map Service (WMS) standards.&lt;br /&gt;
:* The GeoServer team asks applicants to introduce themselves on the geoserver-devel list ( Communicating in public is a key success factor to open source development )&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Geotools-logo.png|50px|right]]&lt;br /&gt;
* [http://docs.codehaus.org/display/GEOTOOLS/Google+Summer+of+Code ''GSOC'']:  [http://live.osgeo.org/en/overview/geotools_overview.html '''GeoTools'''] GeoTools is an open source Java library for working with geospatial data, including both data access, data structures, processing and a powerful rendering engine. GeoTools is a modular library used in a wide range of web service, command line tools and desktop applications.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:ZOO-Project-mini.png|right]]&lt;br /&gt;
* [http://www.zoo-project.org/trac/wiki/ZOO_GSoC_Idea '''ZOO-Project''' Ideas]: [http://www.zoo-project.org ZOO-Project] is a WPS open source project released under a MIT/X-11 style license. It provides support for WPS 1.0.0 and 2.0.0 versions  and is able to handle services implemented in various programming languages.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
We expect ideas also from [http://live.osgeo.org/en/overview/mapbender_overview.html MapBender], [http://live.osgeo.org/en/overview/geomoose_overview.html GeoMOOSE], [http://mapserver.org/ MapServer], ...&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Osgeo-live.png|150px|right]]&lt;br /&gt;
* [http://wiki.osgeo.org/wiki/Live_GIS_GSoC_2016 '''Osgeo-Live''' SoC Ideas]: [http://live.osgeo.org/en/index.html OSGeo-Live] is a self-contained bootable DVD, USB thumb drive or Virtual Machine based on Lubuntu, that allows you to try a wide variety of open source geospatial software without installing anything. It is composed entirely of free software, allowing it to be freely distributed, duplicated and passed around. It provides pre-configured applications for a range of geospatial use cases, including storage, publishing, viewing, analysis and manipulation of data. It also contains sample datasets and documentation.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Guest projects ===&lt;br /&gt;
&lt;br /&gt;
Like-minded geospatial projects to take part under OSGeo umbrella. If you wish your software project to be listed here, please contact the GSoC admin team, by sending an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
=== See also ===&lt;br /&gt;
&lt;br /&gt;
Other like minded projects do not participate to GSoC under OSGeo umbrella, but with their own organization. You may want to visit also their page:&lt;br /&gt;
&lt;br /&gt;
[[Image:Logo-osm6.png|60px|right]] &lt;br /&gt;
* [http://wiki.openstreetmap.org/wiki/Google_Summer_of_Code/2015/Project_Ideas '''OpenStreetMap''' Ideas]: [http://osm.org/ OSM] is a project aimed squarely at creating and providing free geographic data such as street maps to anyone who wants them. The project was started because most maps you think of as free actually have legal or technical restrictions on their use, holding back people from using them in creative, productive or unexpected ways.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Don't see in the list the project you're interested in? ===&lt;br /&gt;
&lt;br /&gt;
Contact them in their developers mailing list! Feel free to propose your own idea and get feedback!&lt;br /&gt;
&lt;br /&gt;
== I want to apply as a student ==&lt;br /&gt;
&lt;br /&gt;
Before applying as a student, check out the [[Google Summer of Code Recommendations for Students]] page.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Which project do I choose? ===&lt;br /&gt;
&lt;br /&gt;
Most of the software projects are available pre-built on our Live demo { DVD | USB stick | VirtualMachine } with project overviews and short tutorials where you can try everything out.&lt;br /&gt;
: View the documents and download the ISO from http://live.osgeo.org&lt;br /&gt;
[[File:Osgeolive wordle.png|500px|center]]&lt;br /&gt;
&lt;br /&gt;
=== Important dates ===&lt;br /&gt;
&lt;br /&gt;
* [https://developers.google.com/open-source/gsoc/timeline '''The official timeline''']&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- {{done}} --&amp;gt;&lt;br /&gt;
* Feb 27: Google announces accepted organizations.&lt;br /&gt;
: Please start talking to the dev communities you are interested in ''now''.&lt;br /&gt;
* March 20:  Student applications open.&lt;br /&gt;
: The earlier you start the more probable it is that you will be accepted!&lt;br /&gt;
: ''There is two way feedback during the application process which really helps you improve and clarify your application before the final deadline. The better your involvement with your potential mentors during this period, the better your chances of being selected.''&lt;br /&gt;
* April 3:  Student application deadline.&lt;br /&gt;
* May 4: '''Accepted student proposals are announced and Community Bonding Period begins.'''&lt;br /&gt;
* May 30: '''Coding begins!'''&lt;br /&gt;
: (''you may unofficially start a week or two earlier if you know you'll have to take a week or two off during The Summer or you'll be sitting finals in the first week(s) of the program. This must be reflected in your application timeline'')&lt;br /&gt;
* June 26 - 30: Phase 1 evaluation &lt;br /&gt;
* July 28: Phase 2 evaluation&lt;br /&gt;
* August 21-29: '''Pencils down!'''&lt;br /&gt;
* August 29 - September 5: Final evaluations&lt;br /&gt;
* September 6: Final results announced&lt;br /&gt;
&lt;br /&gt;
[Back to [[Google Summer of Code 2017]] @ OSGeo]&lt;br /&gt;
[[Category: Google Summer of Code]]&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=UNTraining&amp;diff=97848</id>
		<title>UNTraining</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=UNTraining&amp;diff=97848"/>
		<updated>2016-04-07T07:48:26Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: Adding more information to gvSIG project&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Welcome to the UN training page'''&lt;br /&gt;
&lt;br /&gt;
GeoForAll is supporting UN in their migration to geospatial open source applications. In this page we list the training material available for some products that UN will use. Please add your training material here, putting also the reference to all data used in such a way that everybody in using your material can be autonomous. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*'''QGIS''' &lt;br /&gt;
&lt;br /&gt;
**'''FOSS4G GeoAcademy Curriculum''' - 35 hands-on labs written primarily for QGIS with some cross over with GRASS and Inkscape. Labs are aligned to the Geospatial Technology Competency Model. Development was sponsored by a Department of Labor Grant and is released under Creative Commons Attribute 3.0 Unported license. All labs currently written for QGIS 2.8, but we are about to release labs for QGIS 2.14. In addition to labs, lecture material is also developed and being uploaded. All lab instructions and data are [http://spatialquerylab.com/foss4g-academy-curriculum/ available online on our lab website].&lt;br /&gt;
***'''Link to material''': http://spatialquerylab.com/foss4g-academy-curriculum/&lt;br /&gt;
***'''Lab''': Spatial {Query} Lab - http://www.spatialquerylab.com&lt;br /&gt;
***'''Point of Contact''': Rick Smith - Richard.Smith@tamucc.edu&lt;br /&gt;
***'''Mailing Address''': 6300 Ocean Dr., Unit 5868, Corpus Christi, TX 78412-5868, USA&lt;br /&gt;
&lt;br /&gt;
Add here: short description (at most 5 lines), URL, Lab name, mailing address of the point of contact&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
*'''gvSIG''' &lt;br /&gt;
&lt;br /&gt;
**gvSIG is a powerful, user-friendly and interoperable GIS. It is easy to work in a variety of formats, vector and raster files, databases and remote services. There are always available all kinds of tools to analyze and manage geographic information.&lt;br /&gt;
&lt;br /&gt;
gvSIG Desktop is designed to be an easily extensible solution, allowing  thus continually improving the software application and developing tailor made solutions. It is open source software, GNU / GPL license, this makes its free use, distribution, study and improvement. gvSIG Desktop integrates NASA World Wind, so it allows to work with 3D Views. &lt;br /&gt;
&lt;br /&gt;
gvSIG Online is an Open Source solution for Spatial Data Infrastructures. It is an integral platform for the Spatial Data Infrastructure (SDI) implementation, 100% open source software. A fast and powerful solution for start up the infrastructure necessary to manage spatial data in an organization in an efficient way. &lt;br /&gt;
&lt;br /&gt;
*Website: http://www.gvsig.com &lt;br /&gt;
*[http://www.gvsig.com/en/diffusion/educational-material?p_p_id=122_INSTANCE_A9eo37KAqtxs&amp;amp;p_p_lifecycle=0&amp;amp;p_p_state=normal&amp;amp;p_p_mode=view&amp;amp;p_p_col_id=column-2&amp;amp;p_p_col_count=1&amp;amp;p_r_p_564233524_resetCur=true&amp;amp;p_r_p_564233524_categoryId=25973 Educational material in English] &lt;br /&gt;
*[http://web.gvsig-training.com/index.php/en/quienes-somos-2/noticias-2/145-the-free-mooc-cycle-gvsig-for-users Free MOOC cycle &amp;quot;gvSIG for Users&amp;quot;]&lt;br /&gt;
*[https://www.youtube.com/user/gvsig gvSIG Youtube Channel]&lt;br /&gt;
*'''Point of Contact''': Mario Carrera - mcarrera [at] gvsig.com&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*'''Geoserver''' &lt;br /&gt;
&lt;br /&gt;
Add here: short description (at most 5 lines), URL, Lab name, mailing address of the point of contact&lt;br /&gt;
&lt;br /&gt;
*'''OpenLayers''' &lt;br /&gt;
&lt;br /&gt;
Add here: short description (at most 5 lines), URL, Lab name, mailing address of the point of contact&lt;br /&gt;
&lt;br /&gt;
*'''PostreSQL''' &lt;br /&gt;
&lt;br /&gt;
Add here: short description (at most 5 lines), URL, Lab name, mailing address of the point of contact&lt;br /&gt;
&lt;br /&gt;
*'''PostGIS''' &lt;br /&gt;
&lt;br /&gt;
Add here: short description (at most 5 lines), URL, Lab name, mailing address of the point of contact&lt;br /&gt;
&lt;br /&gt;
*'''Geonode''' &lt;br /&gt;
&lt;br /&gt;
Add here: short description (at most 5 lines), URL, Lab name, mailing address of the point of contact&lt;br /&gt;
&lt;br /&gt;
*'''[http://www.rasdaman.org rasdaman]'''&lt;br /&gt;
**'''Big Geo Data Lab''' - Spatio-temporal sensor, image, simulation, and statistics data of unlimited size are served rapidly by rasdaman (&amp;quot;raster data manager&amp;quot;). As a multiparallel, distributed analytics engine, rasdaman achieves unparalleled service flexibility, scalability, and performance. Being OGC [http://en.wikipedia.org/wiki/Web_Coverage_Processing_Service WCPS] and [http://en.wikipedia.org/wiki/Web_Coverage_Service WCS] Core Reference Implementation, rasdaman enables access, subsetting, and processing on the fly using open standards interfaces. The WCS suite is a central cornerstone for SDIs: a large, growing number of open-source and proprietary tools supports it (MapServer, GeoServer, OpenLayers, QGIS, ESRI ArcGIS, ...) and the OGC standards are under adoption by ISO (as forthcoming 19123-2) and INSPIRE (&amp;quot;Coverage Download Service&amp;quot;). Significant training material is available already, and is being augmented continuously:&lt;br /&gt;
**'''Link to material''': [http://rasdaman.org/wiki/Workshops OGC Big Geo Data standards and rasdaman workshops] | [http://standards.rasdaman.com/ hands-on lab on Big Data Standards] | [http://kahlua.eecs.jacobs-university.de/~lsis/Big-Earth-Data_the-ARTE-Movie/index.php Big Earth Data] (53min TV documentary) &lt;br /&gt;
**'''Point of Contact''': Peter Baumann - baumann@rasdaman.com&lt;br /&gt;
&lt;br /&gt;
*'''OSGeo-Live''' &lt;br /&gt;
&lt;br /&gt;
OSGeo-Live contains 50 of the best geospatial applications, pre-installed with datasets, along with project overviews and 10 to 15 minute quickstarts for each application. The documentation provides an excellent high level overview of the breadth of geospatial open source applications. It is also used as a plaform for many open source geospatial workshops.&lt;br /&gt;
&lt;br /&gt;
Website: http://live.osgeo.org&lt;br /&gt;
&lt;br /&gt;
Contact: Cameron Shorter &amp;lt;cam e r onDoTs hort erA T g mai l.com&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*'''Bringing GEOSS services into practice''' &lt;br /&gt;
The &amp;quot;Bringing GEOSS services into practice&amp;quot; workshop aims at teaching how to configure, use and deploy a set of open source software (PostGIS, GeoServer, GeoNetwork, PyWPS, QGIS) to set up a spatial data infrastructure (SDI). Trainees will learn how to publish and share data and metadata using OGC and ISO standards and how to register services into the Global Earth Observation System of Systems (GEOSS).&lt;br /&gt;
&lt;br /&gt;
Website: http://www.geossintopractice.org&lt;br /&gt;
&lt;br /&gt;
Lab: GeoForAll - ISE, University of Geneva: http://www.unige.ch/tigers/fr/autres-reseaux/geoforall/&lt;br /&gt;
&lt;br /&gt;
Contact: Gregory Giuliani &amp;lt;gregory.giuliani AT unige.ch&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*'''GeoMOOSE'''&lt;br /&gt;
&lt;br /&gt;
GeoMOOSE is a Web Client JavaScript Framework for displaying distributed cartographic data. GeoMOOSE has a number of strengths including modularity, configurability, and delivers a number of core functionalities in its packages. GeoMOOSE is also very light weight for servers making it easy to handle a large number of users, with a large number of layers, and a large number of services without stressing a server.&lt;br /&gt;
&lt;br /&gt;
The GeoMOOSE core is written using JavaScript and HTML. It is entirely possible to run GeoMOOSE with nothing more than a basic web server (Nginx, Apache, IIS). But besides the basic client core, GeoMOOSE also comes prepackaged with a number of built in services written in PHP. These services add the ability to perform drill-down identify operations, selection operations, and search data sets. If you have existing scripts that perform similar functions, GeoMOOSE can be tuned to work with those services, no matter which language they were written in.&lt;br /&gt;
&lt;br /&gt;
Website: http://www.geomoose.org&lt;br /&gt;
&lt;br /&gt;
Online Demo: http://demo.geomoose.org/master/&lt;br /&gt;
&lt;br /&gt;
Package download (includes operating demo with sample data): http://geomoose.org/download.html&lt;br /&gt;
&lt;br /&gt;
GeoMOOSE is also compatible with MS4W.&lt;br /&gt;
&lt;br /&gt;
Contact: Bob Basques &amp;lt;bbasques AT sharedgeo.org&amp;gt;&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2016_Administrative&amp;diff=97829</id>
		<title>Google Summer of Code 2016 Administrative</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2016_Administrative&amp;diff=97829"/>
		<updated>2016-04-06T11:48:09Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: New mentor for gvSIG project&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;center&amp;gt;&lt;br /&gt;
[[Image:GSoC2016Logo.jpg|500px|link=https://summerofcode.withgoogle.com/]] &amp;lt;font size=&amp;quot;+3&amp;quot;&amp;gt; @ &amp;lt;/font&amp;gt; [[Image:OSGeo_300_127_pixel.png|200px|link=http://www.osgeo.org]]&lt;br /&gt;
&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Back to the main OSGeo [[Google Summer of Code 2016]] @ OSGeo wiki page.&lt;br /&gt;
&lt;br /&gt;
This is the central page for OSGeo administrative information in Google Summer of Code 2016.&lt;br /&gt;
&lt;br /&gt;
== GSoC general information ==&lt;br /&gt;
&lt;br /&gt;
* [https://developers.google.com/open-source/gsoc/timeline The official timeline]&lt;br /&gt;
* [https://developers.google.com/open-source/gsoc/resources/ Google's FAQ on the program]&lt;br /&gt;
* [https://summerofcode.withgoogle.com/ Official 2016 GSoC site]&lt;br /&gt;
&lt;br /&gt;
== Contacts == &lt;br /&gt;
&lt;br /&gt;
* [[User:Madi|Margherita Di Leo]] acts as Administrative contact, with support from [[User:Aghisla|Anne Ghisla]]. Feel free to email us with any questions, we're here to help mentor the mentors as much as anything else!&lt;br /&gt;
&lt;br /&gt;
* Would-be mentors and students: you are invited to sign up to the [http://lists.osgeo.org/mailman/listinfo/soc OSGeo SoC mailing list] right away. The list is the central communication channel for mentors, students and administrators. It is used for general GSoC announcements, specific OSGeo announcements, and for clarification about the program. As soon as you subscribe it, you are encouraged to introduce yourself and your role. We look forward to hear from you!&lt;br /&gt;
&lt;br /&gt;
== Mentors ==&lt;br /&gt;
&lt;br /&gt;
If you're interested in mentoring / supervising a student for one of the software participating this year under OSGeo's umbrella, please add your name, email, OSGeo/guest software and the projects you're interested in mentoring here:&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable sortable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;4&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#D7E3D1; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|width=30px|'''Number'''&lt;br /&gt;
|width=100px|'''Name'''&lt;br /&gt;
|width=100px|'''Surname'''&lt;br /&gt;
|width=100px|'''Nickname (IRC)'''&lt;br /&gt;
|width=250px|'''email'''&lt;br /&gt;
|'''Software community'''&lt;br /&gt;
|'''Idea(s) you are available to mentor'''&lt;br /&gt;
|-&lt;br /&gt;
|1&lt;br /&gt;
|Margherita&lt;br /&gt;
|Di Leo &lt;br /&gt;
|madi&lt;br /&gt;
|diregola AT gmail DOT com &lt;br /&gt;
|admin at OSGeo&lt;br /&gt;
|Idea I would like to mentor&lt;br /&gt;
|-&lt;br /&gt;
|2&lt;br /&gt;
|Alexander&lt;br /&gt;
|Bruy &lt;br /&gt;
|alexbruy&lt;br /&gt;
|alexander.bruy AT gmail.com &lt;br /&gt;
|QGIS&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|3&lt;br /&gt;
|Victor&lt;br /&gt;
|Olaya &lt;br /&gt;
|volaya&lt;br /&gt;
|volayaf AT gmail DOT com &lt;br /&gt;
|QGIS&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|4&lt;br /&gt;
|Daniel&lt;br /&gt;
|Kastl&lt;br /&gt;
|dkastl&lt;br /&gt;
|daniel AT georepublic DOT de &lt;br /&gt;
|pgRouting&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|5&lt;br /&gt;
|Massimiliano&lt;br /&gt;
|Cannata&lt;br /&gt;
|maxi&lt;br /&gt;
|massimiliano.cannata AT gmail DOT com &lt;br /&gt;
|istSOS&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|6&lt;br /&gt;
|Milan&lt;br /&gt;
|Antonovic&lt;br /&gt;
|milan&lt;br /&gt;
|milan.antonovic AT gmail DOT com &lt;br /&gt;
|istSOS&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|7&lt;br /&gt;
|Jachym&lt;br /&gt;
|Cepicky&lt;br /&gt;
|jachym&lt;br /&gt;
|jachym.cepicky AT gmail &lt;br /&gt;
|PyWPS&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|8&lt;br /&gt;
|Andrea&lt;br /&gt;
|Antonello&lt;br /&gt;
|moovida&lt;br /&gt;
|andrea.antonello AT gmail DOT com&lt;br /&gt;
|JGrasstools, gvSIG, Geopaparazzi&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|9&lt;br /&gt;
|Rashad&lt;br /&gt;
|Kanavath&lt;br /&gt;
|rashadkm&lt;br /&gt;
|rashadkm AT gmail DOT com&lt;br /&gt;
|GRASS GIS, OSSIM, GDAL&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|10&lt;br /&gt;
|Cameron&lt;br /&gt;
|Shorter&lt;br /&gt;
|CameronShorter&lt;br /&gt;
|cameronDOTs h o r ter AT gmail com&lt;br /&gt;
|OSGeo-Live&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|11&lt;br /&gt;
|Stephen&lt;br /&gt;
|Woodbridge&lt;br /&gt;
|woodbri&lt;br /&gt;
|woodbri AT swoodbridge DOT com&lt;br /&gt;
|pgRouting&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|12&lt;br /&gt;
|Vicky&lt;br /&gt;
|Vergara&lt;br /&gt;
|cvvergara&lt;br /&gt;
|vicky AT georepublic DOT de&lt;br /&gt;
|pgRouting&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|13&lt;br /&gt;
|Dmitry&lt;br /&gt;
|Baryshnikov&lt;br /&gt;
|bishop&lt;br /&gt;
|bishop.dev AT gmail.com &lt;br /&gt;
|GDAL&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|14&lt;br /&gt;
|Luca&lt;br /&gt;
|Delucchi&lt;br /&gt;
|lucadelu&lt;br /&gt;
|lucadeluge AT gmail.com &lt;br /&gt;
|GRASS GIS&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|15&lt;br /&gt;
|Anna&lt;br /&gt;
|Petrasova&lt;br /&gt;
|&lt;br /&gt;
|kratochanna AT gmail.com &lt;br /&gt;
|GRASS GIS&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|16&lt;br /&gt;
|Stefan&lt;br /&gt;
|Steiniger&lt;br /&gt;
|&lt;br /&gt;
|sstein AT geo.uzh.ch &lt;br /&gt;
|OneBusAway, OpenTripPlanner, OpenJUMP&lt;br /&gt;
|for OneBusAway see [http://github.com/OneBusAway/onebusaway-application-modules/wiki/Google-Summer-of-Code-2016 here]&lt;br /&gt;
|-&lt;br /&gt;
|17&lt;br /&gt;
|Sean&lt;br /&gt;
|Barbeau&lt;br /&gt;
|&lt;br /&gt;
|barbeau AT cutr.usf.edu&lt;br /&gt;
|OneBusAway, OpenTripPlanner&lt;br /&gt;
|for OneBusAway see [http://github.com/OneBusAway/onebusaway-application-modules/wiki/Google-Summer-of-Code-2016 here], also there are ideas around for OpenTripPlanner Android App, and the GTFS-RT Validator&lt;br /&gt;
|-&lt;br /&gt;
|18&lt;br /&gt;
|Riccardo&lt;br /&gt;
|Rigon&lt;br /&gt;
|abouthydrology&lt;br /&gt;
|rccrd.rgn AT gmail DOT com&lt;br /&gt;
|JGrasstools, gvSIG, Geopaparazzi&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|19&lt;br /&gt;
|Vaclav&lt;br /&gt;
|Petras&lt;br /&gt;
|&lt;br /&gt;
|wenzeslaus AT gmail.com &lt;br /&gt;
|GRASS GIS&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|20&lt;br /&gt;
|Oliver&lt;br /&gt;
|May&lt;br /&gt;
|&lt;br /&gt;
|oliver AT dfc DOT be&lt;br /&gt;
|Geomajas, leaflet, openlayers, geoserver, geotools&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|21&lt;br /&gt;
|Even&lt;br /&gt;
|Rouault&lt;br /&gt;
|&lt;br /&gt;
|even dot rouault AT spatialys dot com&lt;br /&gt;
|GDAL&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|22&lt;br /&gt;
|Alexandre&lt;br /&gt;
|Dubé&lt;br /&gt;
|&lt;br /&gt;
|adube AT mapgears dot com&lt;br /&gt;
|OL3-Google-Maps&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|23&lt;br /&gt;
|Moritz&lt;br /&gt;
|Lennert&lt;br /&gt;
|&lt;br /&gt;
|mlennert AT club dot worldonline dot be&lt;br /&gt;
|GRASS GIS&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|24&lt;br /&gt;
|Roberto&lt;br /&gt;
|Marzocchi&lt;br /&gt;
|&lt;br /&gt;
|roberto dot marzocchi AT gmail dot com dot&lt;br /&gt;
|GRASS GIS&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|25&lt;br /&gt;
|Brian M&lt;br /&gt;
|Hamlin&lt;br /&gt;
|darkblue_b&lt;br /&gt;
|maplabs AT light42 DOT com&lt;br /&gt;
|SciPy geospatial stack, PostGIS, gdal 2.0&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|26&lt;br /&gt;
|Jessica&lt;br /&gt;
|Lapointe&lt;br /&gt;
|&lt;br /&gt;
|jlapointe AT mapgears dot com&lt;br /&gt;
|OL3-Google-Maps&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|27&lt;br /&gt;
|Gérald&lt;br /&gt;
|Fenoy&lt;br /&gt;
|djay&lt;br /&gt;
|gerald.fenoy AT geolabs.fr &lt;br /&gt;
|ZOO-Project&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|28&lt;br /&gt;
|Massimo&lt;br /&gt;
|Di Stefano&lt;br /&gt;
|epifanio&lt;br /&gt;
|epiesasha AT me DOT com&lt;br /&gt;
|GRASS GIS&lt;br /&gt;
| webgrass&lt;br /&gt;
|-&lt;br /&gt;
|29&lt;br /&gt;
|Patrick&lt;br /&gt;
|Hogan&lt;br /&gt;
|&lt;br /&gt;
|patrick.hogan AT nasa DOT gov&lt;br /&gt;
|NASA World Wind&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|30&lt;br /&gt;
|Oscar&lt;br /&gt;
|Kramer&lt;br /&gt;
|&lt;br /&gt;
|oscarkramer AT yahoo DOT com &lt;br /&gt;
|OSSIM&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|31&lt;br /&gt;
|Jakub&lt;br /&gt;
|Balhar&lt;br /&gt;
|&lt;br /&gt;
|jakub AT balhar DOT net&lt;br /&gt;
|NASA World Wind&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|32&lt;br /&gt;
|Jonas&lt;br /&gt;
|Eberle&lt;br /&gt;
|&lt;br /&gt;
|jonas.eberle AT gmx DOT de&lt;br /&gt;
|PyWPS&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|33&lt;br /&gt;
|Martin&lt;br /&gt;
|Landa&lt;br /&gt;
|&lt;br /&gt;
|landa.martin AT gmail DOT com&lt;br /&gt;
|GRASS GIS&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|34&lt;br /&gt;
|Rob&lt;br /&gt;
|Emanuele&lt;br /&gt;
|lossyrob&lt;br /&gt;
|rdemanuele AT gmail DOT com&lt;br /&gt;
|GDAL&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|35&lt;br /&gt;
|Anita&lt;br /&gt;
|Graser&lt;br /&gt;
|&lt;br /&gt;
|anitagraser AT gmx DOT at&lt;br /&gt;
|QGIS&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|36&lt;br /&gt;
|Giustino&lt;br /&gt;
|Tonon&lt;br /&gt;
|&lt;br /&gt;
|giustino.tonon AT unibz DOT it&lt;br /&gt;
|JGrasstools&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|37&lt;br /&gt;
|Alessandro&lt;br /&gt;
|Pasotti&lt;br /&gt;
|&lt;br /&gt;
|apasotti AT gmail DOT com&lt;br /&gt;
|QGIS&lt;br /&gt;
|QGIS Symbology Repository&lt;br /&gt;
|-&lt;br /&gt;
|38&lt;br /&gt;
|David&lt;br /&gt;
|Burken&lt;br /&gt;
|&lt;br /&gt;
|dburken AT gmail DOT com&lt;br /&gt;
|OSSIM&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|39&lt;br /&gt;
|Óg&lt;br /&gt;
|Crudden&lt;br /&gt;
|&lt;br /&gt;
|og.crudden AT gmail.com&lt;br /&gt;
|OneBusAway&lt;br /&gt;
|see [http://github.com/OneBusAway/onebusaway-application-modules/wiki/Google-Summer-of-Code-2016 here]&lt;br /&gt;
|-&lt;br /&gt;
|40&lt;br /&gt;
|Markus&lt;br /&gt;
|Neteler&lt;br /&gt;
|&lt;br /&gt;
|neteler AT osgeo DOT org&lt;br /&gt;
|GRASS GIS&lt;br /&gt;
|-&lt;br /&gt;
|41&lt;br /&gt;
|Joaquin&lt;br /&gt;
|del Cerro&lt;br /&gt;
|&lt;br /&gt;
|jjdelcerro AT gvsig DOT com&lt;br /&gt;
|gvSIG&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|42&lt;br /&gt;
|Óscar&lt;br /&gt;
|Mártinez&lt;br /&gt;
|&lt;br /&gt;
|masquesig AT gmail DOT com&lt;br /&gt;
|gvSIG&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== A Mentor's Responsibilities ==&lt;br /&gt;
&lt;br /&gt;
Being a mentor can take anywhere from 2-10 hours a week of your time depending on the student (it really ''is'' in your best interest to take on the strongest students you can find). You must have the time to be responsive and an advocate for the student. No matter how cool the project is and how much your team needs the job done, if you can't commit to supporting it, experience shows that the best thing to do is not start it, i.e. even with the best of intentions don't set a student up to fail. Long story short, student projects simply can't go ahead without proper mentoring support.&lt;br /&gt;
&lt;br /&gt;
Every student project will also have a '''backup mentor''', this person should come from your dev community and should at minimum keep up to date with the student's weekly developments. ''' Both mentors need to appoint themselves officially'''. The best way is if the student is well integrated into your development team from the start, it lessens the workload on you and betters the buy-in from the rest of the community once you're ready for the final code merge.&lt;br /&gt;
&lt;br /&gt;
You '''must''' be available at some time during the '''midterm and final evaluation period'''. If you will be away during these time periods please arrange with the OSGeo org admins and your backup mentor so that one of us can fill in your answers for you. These are hard cutoffs -- evaluations ''must'' be filed within these dates.&lt;br /&gt;
&lt;br /&gt;
== Guides for mentors ==&lt;br /&gt;
&lt;br /&gt;
* [http://en.flossmanuals.net/GSoCMentoring/ The GSoC Mentoring Guide] - A must. Do get all useful info and tips from many years of experience from GSoC mentors.&lt;br /&gt;
* [http://people.gnome.org/~federico/docs/summer-of-code-mentoring-howto/ GNOME GSoC Mentoring HOWTO]&lt;br /&gt;
* [http://emptysqua.re/blog/mentoring/ An excellent summary of mentoring, from A. Jesse Jiryu Davis]&lt;br /&gt;
&lt;br /&gt;
== Tips for mentors ==&lt;br /&gt;
&lt;br /&gt;
This section is for collecting suggestions on best practices, from mentors to other mentors. If you have good / bad experiences in mentoring, please share here! Remember that this is a public page, respect the privacy of the people.&lt;br /&gt;
&lt;br /&gt;
=== Good ideas ===&lt;br /&gt;
&lt;br /&gt;
* '''Test students before selection.''' Challenge them with small programming tasks or bug fixes. This will help them getting familiar with the dev environment well before GSoC starts, and helps mentors understand if they are capable. Think to a task much earlier to the timeline, and connect the task to the idea in the ideas page. &lt;br /&gt;
* Time management tip: Try not to mentor more than one project per year. In any case, '''you can be primary mentor only for one project.''' Consider carefully the time that you can allocate on GSoC.&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
=== Bad ideas ===&lt;br /&gt;
&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
== Learn more ==&lt;br /&gt;
&lt;br /&gt;
* Previous years SoC involvement: [http://code.google.com/soc/2008/osgeo/about.html 2008], [http://www.google-melange.com/gsoc/org/google/gsoc2009/osgeo 2009], [http://www.google-melange.com/gsoc/org/google/gsoc2010/osgeo 2010], [http://www.google-melange.com/gsoc/org/google/gsoc2011/osgeo 2011], [http://www.google-melange.com/gsoc/org/google/gsoc2012/osgeo 2012], [http://www.google-melange.com/gsoc/org/google/gsoc2013/osgeo 2013], [https://www.google-melange.com/gsoc/org2/google/gsoc2015/osgeo 2015]&lt;br /&gt;
&lt;br /&gt;
* OSGeo GSoC wiki pages: [[Google Summer of Code 2008|2008]], [[Google Summer of Code 2009|2009]], [[Google Summer of Code 2010|2010]], [[Google Summer of Code 2011|2011]], [[Google Summer of Code 2012|2012]], [[Google Summer of Code 2013|2013]], [[Google Summer of Code 2014|2014]], [[Google Summer of Code 2015|2015]]&lt;br /&gt;
&lt;br /&gt;
* OSGeo Applications: [[Google SoC Application 2009|2009]], [[Google SoC Application 2010|2010]], [[Google Summer of Code Application 2011|2011]], [[Google Summer of Code Application 2012|2012]], [[Google Summer of Code Application 2013|2013]], [[Google Summer of Code Application 2014|2014]], [[Google Summer of Code Application 2015|2015]], [[Google Summer of Code Application 2016|2016]] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category: Google Summer of Code]]&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2016_Administrative&amp;diff=97818</id>
		<title>Google Summer of Code 2016 Administrative</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2016_Administrative&amp;diff=97818"/>
		<updated>2016-04-05T10:59:58Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: /* Mentors */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;center&amp;gt;&lt;br /&gt;
[[Image:GSoC2016Logo.jpg|500px|link=https://summerofcode.withgoogle.com/]] &amp;lt;font size=&amp;quot;+3&amp;quot;&amp;gt; @ &amp;lt;/font&amp;gt; [[Image:OSGeo_300_127_pixel.png|200px|link=http://www.osgeo.org]]&lt;br /&gt;
&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Back to the main OSGeo [[Google Summer of Code 2016]] @ OSGeo wiki page.&lt;br /&gt;
&lt;br /&gt;
This is the central page for OSGeo administrative information in Google Summer of Code 2016.&lt;br /&gt;
&lt;br /&gt;
== GSoC general information ==&lt;br /&gt;
&lt;br /&gt;
* [https://developers.google.com/open-source/gsoc/timeline The official timeline]&lt;br /&gt;
* [https://developers.google.com/open-source/gsoc/resources/ Google's FAQ on the program]&lt;br /&gt;
* [https://summerofcode.withgoogle.com/ Official 2016 GSoC site]&lt;br /&gt;
&lt;br /&gt;
== Contacts == &lt;br /&gt;
&lt;br /&gt;
* [[User:Madi|Margherita Di Leo]] acts as Administrative contact, with support from [[User:Aghisla|Anne Ghisla]]. Feel free to email us with any questions, we're here to help mentor the mentors as much as anything else!&lt;br /&gt;
&lt;br /&gt;
* Would-be mentors and students: you are invited to sign up to the [http://lists.osgeo.org/mailman/listinfo/soc OSGeo SoC mailing list] right away. The list is the central communication channel for mentors, students and administrators. It is used for general GSoC announcements, specific OSGeo announcements, and for clarification about the program. As soon as you subscribe it, you are encouraged to introduce yourself and your role. We look forward to hear from you!&lt;br /&gt;
&lt;br /&gt;
== Mentors ==&lt;br /&gt;
&lt;br /&gt;
If you're interested in mentoring / supervising a student for one of the software participating this year under OSGeo's umbrella, please add your name, email, OSGeo/guest software and the projects you're interested in mentoring here:&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable sortable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;4&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#D7E3D1; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|width=30px|'''Number'''&lt;br /&gt;
|width=100px|'''Name'''&lt;br /&gt;
|width=100px|'''Surname'''&lt;br /&gt;
|width=100px|'''Nickname (IRC)'''&lt;br /&gt;
|width=250px|'''email'''&lt;br /&gt;
|'''Software community'''&lt;br /&gt;
|'''Idea(s) you are available to mentor'''&lt;br /&gt;
|-&lt;br /&gt;
|1&lt;br /&gt;
|Margherita&lt;br /&gt;
|Di Leo &lt;br /&gt;
|madi&lt;br /&gt;
|diregola AT gmail DOT com &lt;br /&gt;
|admin at OSGeo&lt;br /&gt;
|Idea I would like to mentor&lt;br /&gt;
|-&lt;br /&gt;
|2&lt;br /&gt;
|Alexander&lt;br /&gt;
|Bruy &lt;br /&gt;
|alexbruy&lt;br /&gt;
|alexander.bruy AT gmail.com &lt;br /&gt;
|QGIS&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|3&lt;br /&gt;
|Victor&lt;br /&gt;
|Olaya &lt;br /&gt;
|volaya&lt;br /&gt;
|volayaf AT gmail DOT com &lt;br /&gt;
|QGIS&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|4&lt;br /&gt;
|Daniel&lt;br /&gt;
|Kastl&lt;br /&gt;
|dkastl&lt;br /&gt;
|daniel AT georepublic DOT de &lt;br /&gt;
|pgRouting&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|5&lt;br /&gt;
|Massimiliano&lt;br /&gt;
|Cannata&lt;br /&gt;
|maxi&lt;br /&gt;
|massimiliano.cannata AT gmail DOT com &lt;br /&gt;
|istSOS&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|6&lt;br /&gt;
|Milan&lt;br /&gt;
|Antonovic&lt;br /&gt;
|milan&lt;br /&gt;
|milan.antonovic AT gmail DOT com &lt;br /&gt;
|istSOS&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|7&lt;br /&gt;
|Jachym&lt;br /&gt;
|Cepicky&lt;br /&gt;
|jachym&lt;br /&gt;
|jachym.cepicky AT gmail &lt;br /&gt;
|PyWPS&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|8&lt;br /&gt;
|Andrea&lt;br /&gt;
|Antonello&lt;br /&gt;
|moovida&lt;br /&gt;
|andrea.antonello AT gmail DOT com&lt;br /&gt;
|JGrasstools, gvSIG, Geopaparazzi&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|9&lt;br /&gt;
|Rashad&lt;br /&gt;
|Kanavath&lt;br /&gt;
|rashadkm&lt;br /&gt;
|rashadkm AT gmail DOT com&lt;br /&gt;
|GRASS GIS, OSSIM, GDAL&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|10&lt;br /&gt;
|Cameron&lt;br /&gt;
|Shorter&lt;br /&gt;
|CameronShorter&lt;br /&gt;
|cameronDOTs h o r ter AT gmail com&lt;br /&gt;
|OSGeo-Live&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|11&lt;br /&gt;
|Stephen&lt;br /&gt;
|Woodbridge&lt;br /&gt;
|woodbri&lt;br /&gt;
|woodbri AT swoodbridge DOT com&lt;br /&gt;
|pgRouting&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|12&lt;br /&gt;
|Vicky&lt;br /&gt;
|Vergara&lt;br /&gt;
|cvvergara&lt;br /&gt;
|vicky AT georepublic DOT de&lt;br /&gt;
|pgRouting&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|13&lt;br /&gt;
|Dmitry&lt;br /&gt;
|Baryshnikov&lt;br /&gt;
|bishop&lt;br /&gt;
|bishop.dev AT gmail.com &lt;br /&gt;
|GDAL&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|14&lt;br /&gt;
|Luca&lt;br /&gt;
|Delucchi&lt;br /&gt;
|lucadelu&lt;br /&gt;
|lucadeluge AT gmail.com &lt;br /&gt;
|GRASS GIS&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|15&lt;br /&gt;
|Anna&lt;br /&gt;
|Petrasova&lt;br /&gt;
|&lt;br /&gt;
|kratochanna AT gmail.com &lt;br /&gt;
|GRASS GIS&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|16&lt;br /&gt;
|Stefan&lt;br /&gt;
|Steiniger&lt;br /&gt;
|&lt;br /&gt;
|sstein AT geo.uzh.ch &lt;br /&gt;
|OneBusAway, OpenTripPlanner, OpenJUMP&lt;br /&gt;
|for OneBusAway see [http://github.com/OneBusAway/onebusaway-application-modules/wiki/Google-Summer-of-Code-2016 here]&lt;br /&gt;
|-&lt;br /&gt;
|17&lt;br /&gt;
|Sean&lt;br /&gt;
|Barbeau&lt;br /&gt;
|&lt;br /&gt;
|barbeau AT cutr.usf.edu&lt;br /&gt;
|OneBusAway, OpenTripPlanner&lt;br /&gt;
|for OneBusAway see [http://github.com/OneBusAway/onebusaway-application-modules/wiki/Google-Summer-of-Code-2016 here], also there are ideas around for OpenTripPlanner Android App, and the GTFS-RT Validator&lt;br /&gt;
|-&lt;br /&gt;
|18&lt;br /&gt;
|Riccardo&lt;br /&gt;
|Rigon&lt;br /&gt;
|abouthydrology&lt;br /&gt;
|rccrd.rgn AT gmail DOT com&lt;br /&gt;
|JGrasstools, gvSIG, Geopaparazzi&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|19&lt;br /&gt;
|Vaclav&lt;br /&gt;
|Petras&lt;br /&gt;
|&lt;br /&gt;
|wenzeslaus AT gmail.com &lt;br /&gt;
|GRASS GIS&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|20&lt;br /&gt;
|Oliver&lt;br /&gt;
|May&lt;br /&gt;
|&lt;br /&gt;
|oliver AT dfc DOT be&lt;br /&gt;
|Geomajas, leaflet, openlayers, geoserver, geotools&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|21&lt;br /&gt;
|Even&lt;br /&gt;
|Rouault&lt;br /&gt;
|&lt;br /&gt;
|even dot rouault AT spatialys dot com&lt;br /&gt;
|GDAL&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|22&lt;br /&gt;
|Alexandre&lt;br /&gt;
|Dubé&lt;br /&gt;
|&lt;br /&gt;
|adube AT mapgears dot com&lt;br /&gt;
|OL3-Google-Maps&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|23&lt;br /&gt;
|Moritz&lt;br /&gt;
|Lennert&lt;br /&gt;
|&lt;br /&gt;
|mlennert AT club dot worldonline dot be&lt;br /&gt;
|GRASS GIS&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|24&lt;br /&gt;
|Roberto&lt;br /&gt;
|Marzocchi&lt;br /&gt;
|&lt;br /&gt;
|roberto dot marzocchi AT gmail dot com dot&lt;br /&gt;
|GRASS GIS&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|25&lt;br /&gt;
|Brian M&lt;br /&gt;
|Hamlin&lt;br /&gt;
|darkblue_b&lt;br /&gt;
|maplabs AT light42 DOT com&lt;br /&gt;
|SciPy geospatial stack, PostGIS, gdal 2.0&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|26&lt;br /&gt;
|Jessica&lt;br /&gt;
|Lapointe&lt;br /&gt;
|&lt;br /&gt;
|jlapointe AT mapgears dot com&lt;br /&gt;
|OL3-Google-Maps&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|27&lt;br /&gt;
|Gérald&lt;br /&gt;
|Fenoy&lt;br /&gt;
|djay&lt;br /&gt;
|gerald.fenoy AT geolabs.fr &lt;br /&gt;
|ZOO-Project&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|28&lt;br /&gt;
|Massimo&lt;br /&gt;
|Di Stefano&lt;br /&gt;
|epifanio&lt;br /&gt;
|epiesasha AT me DOT com&lt;br /&gt;
|GRASS GIS&lt;br /&gt;
| webgrass&lt;br /&gt;
|-&lt;br /&gt;
|29&lt;br /&gt;
|Patrick&lt;br /&gt;
|Hogan&lt;br /&gt;
|&lt;br /&gt;
|patrick.hogan AT nasa DOT gov&lt;br /&gt;
|NASA World Wind&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|30&lt;br /&gt;
|Oscar&lt;br /&gt;
|Kramer&lt;br /&gt;
|&lt;br /&gt;
|oscarkramer AT yahoo DOT com &lt;br /&gt;
|OSSIM&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|31&lt;br /&gt;
|Jakub&lt;br /&gt;
|Balhar&lt;br /&gt;
|&lt;br /&gt;
|jakub AT balhar DOT net&lt;br /&gt;
|NASA World Wind&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|32&lt;br /&gt;
|Jonas&lt;br /&gt;
|Eberle&lt;br /&gt;
|&lt;br /&gt;
|jonas.eberle AT gmx DOT de&lt;br /&gt;
|PyWPS&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|33&lt;br /&gt;
|Martin&lt;br /&gt;
|Landa&lt;br /&gt;
|&lt;br /&gt;
|landa.martin AT gmail DOT com&lt;br /&gt;
|GRASS GIS&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|34&lt;br /&gt;
|Rob&lt;br /&gt;
|Emanuele&lt;br /&gt;
|lossyrob&lt;br /&gt;
|rdemanuele AT gmail DOT com&lt;br /&gt;
|GDAL&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|35&lt;br /&gt;
|Anita&lt;br /&gt;
|Graser&lt;br /&gt;
|&lt;br /&gt;
|anitagraser AT gmx DOT at&lt;br /&gt;
|QGIS&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|36&lt;br /&gt;
|Giustino&lt;br /&gt;
|Tonon&lt;br /&gt;
|&lt;br /&gt;
|giustino.tonon AT unibz DOT it&lt;br /&gt;
|JGrasstools&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|37&lt;br /&gt;
|Alessandro&lt;br /&gt;
|Pasotti&lt;br /&gt;
|&lt;br /&gt;
|apasotti AT gmail DOT com&lt;br /&gt;
|QGIS&lt;br /&gt;
|QGIS Symbology Repository&lt;br /&gt;
|-&lt;br /&gt;
|38&lt;br /&gt;
|David&lt;br /&gt;
|Burken&lt;br /&gt;
|&lt;br /&gt;
|dburken AT gmail DOT com&lt;br /&gt;
|OSSIM&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|39&lt;br /&gt;
|Óg&lt;br /&gt;
|Crudden&lt;br /&gt;
|&lt;br /&gt;
|og.crudden AT gmail.com&lt;br /&gt;
|OneBusAway&lt;br /&gt;
|see [http://github.com/OneBusAway/onebusaway-application-modules/wiki/Google-Summer-of-Code-2016 here]&lt;br /&gt;
|-&lt;br /&gt;
|40&lt;br /&gt;
|Markus&lt;br /&gt;
|Neteler&lt;br /&gt;
|&lt;br /&gt;
|neteler AT osgeo DOT org&lt;br /&gt;
|GRASS GIS&lt;br /&gt;
|-&lt;br /&gt;
|41&lt;br /&gt;
|Joaquin&lt;br /&gt;
|del Cerro&lt;br /&gt;
|&lt;br /&gt;
|jjdelcerro AT gvsig DOT com&lt;br /&gt;
|gvSIG&lt;br /&gt;
||&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== A Mentor's Responsibilities ==&lt;br /&gt;
&lt;br /&gt;
Being a mentor can take anywhere from 2-10 hours a week of your time depending on the student (it really ''is'' in your best interest to take on the strongest students you can find). You must have the time to be responsive and an advocate for the student. No matter how cool the project is and how much your team needs the job done, if you can't commit to supporting it, experience shows that the best thing to do is not start it, i.e. even with the best of intentions don't set a student up to fail. Long story short, student projects simply can't go ahead without proper mentoring support.&lt;br /&gt;
&lt;br /&gt;
Every student project will also have a '''backup mentor''', this person should come from your dev community and should at minimum keep up to date with the student's weekly developments. ''' Both mentors need to appoint themselves officially'''. The best way is if the student is well integrated into your development team from the start, it lessens the workload on you and betters the buy-in from the rest of the community once you're ready for the final code merge.&lt;br /&gt;
&lt;br /&gt;
You '''must''' be available at some time during the '''midterm and final evaluation period'''. If you will be away during these time periods please arrange with the OSGeo org admins and your backup mentor so that one of us can fill in your answers for you. These are hard cutoffs -- evaluations ''must'' be filed within these dates.&lt;br /&gt;
&lt;br /&gt;
== Guides for mentors ==&lt;br /&gt;
&lt;br /&gt;
* [http://en.flossmanuals.net/GSoCMentoring/ The GSoC Mentoring Guide] - A must. Do get all useful info and tips from many years of experience from GSoC mentors.&lt;br /&gt;
* [http://people.gnome.org/~federico/docs/summer-of-code-mentoring-howto/ GNOME GSoC Mentoring HOWTO]&lt;br /&gt;
* [http://emptysqua.re/blog/mentoring/ An excellent summary of mentoring, from A. Jesse Jiryu Davis]&lt;br /&gt;
&lt;br /&gt;
== Tips for mentors ==&lt;br /&gt;
&lt;br /&gt;
This section is for collecting suggestions on best practices, from mentors to other mentors. If you have good / bad experiences in mentoring, please share here! Remember that this is a public page, respect the privacy of the people.&lt;br /&gt;
&lt;br /&gt;
=== Good ideas ===&lt;br /&gt;
&lt;br /&gt;
* '''Test students before selection.''' Challenge them with small programming tasks or bug fixes. This will help them getting familiar with the dev environment well before GSoC starts, and helps mentors understand if they are capable. Think to a task much earlier to the timeline, and connect the task to the idea in the ideas page. &lt;br /&gt;
* Time management tip: Try not to mentor more than one project per year. In any case, '''you can be primary mentor only for one project.''' Consider carefully the time that you can allocate on GSoC.&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
=== Bad ideas ===&lt;br /&gt;
&lt;br /&gt;
* ...&lt;br /&gt;
&lt;br /&gt;
== Learn more ==&lt;br /&gt;
&lt;br /&gt;
* Previous years SoC involvement: [http://code.google.com/soc/2008/osgeo/about.html 2008], [http://www.google-melange.com/gsoc/org/google/gsoc2009/osgeo 2009], [http://www.google-melange.com/gsoc/org/google/gsoc2010/osgeo 2010], [http://www.google-melange.com/gsoc/org/google/gsoc2011/osgeo 2011], [http://www.google-melange.com/gsoc/org/google/gsoc2012/osgeo 2012], [http://www.google-melange.com/gsoc/org/google/gsoc2013/osgeo 2013], [https://www.google-melange.com/gsoc/org2/google/gsoc2015/osgeo 2015]&lt;br /&gt;
&lt;br /&gt;
* OSGeo GSoC wiki pages: [[Google Summer of Code 2008|2008]], [[Google Summer of Code 2009|2009]], [[Google Summer of Code 2010|2010]], [[Google Summer of Code 2011|2011]], [[Google Summer of Code 2012|2012]], [[Google Summer of Code 2013|2013]], [[Google Summer of Code 2014|2014]], [[Google Summer of Code 2015|2015]]&lt;br /&gt;
&lt;br /&gt;
* OSGeo Applications: [[Google SoC Application 2009|2009]], [[Google SoC Application 2010|2010]], [[Google Summer of Code Application 2011|2011]], [[Google Summer of Code Application 2012|2012]], [[Google Summer of Code Application 2013|2013]], [[Google Summer of Code Application 2014|2014]], [[Google Summer of Code Application 2015|2015]], [[Google Summer of Code Application 2016|2016]] &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category: Google Summer of Code]]&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=UNTraining&amp;diff=97757</id>
		<title>UNTraining</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=UNTraining&amp;diff=97757"/>
		<updated>2016-03-29T14:12:44Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: Improving the gvSIG information&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Welcome to the UN training page'''&lt;br /&gt;
&lt;br /&gt;
GeoForAll is supporting UN in their migration to geospatial open source applications. In this page we list the training material available for some products that UN will use. Please add your training material here, putting also the reference to all data used in such a way that everybody in using your material can be autonomous. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*'''QGIS''' &lt;br /&gt;
&lt;br /&gt;
**'''FOSS4G GeoAcademy Curriculum''' - 35 hands-on labs written primarily for QGIS with some cross over with GRASS and Inkscape. Labs are aligned to the Geospatial Technology Competency Model. Development was sponsored by a Department of Labor Grant and is released under Creative Commons Attribute 3.0 Unported license. All labs currently written for QGIS 2.8, but we are about to release labs for QGIS 2.14. In addition to labs, lecture material is also developed and being uploaded. All lab instructions and data are [http://spatialquerylab.com/foss4g-academy-curriculum/ available online on our lab website].&lt;br /&gt;
***'''Link to material''': http://spatialquerylab.com/foss4g-academy-curriculum/&lt;br /&gt;
***'''Lab''': Spatial {Query} Lab - http://www.spatialquerylab.com&lt;br /&gt;
***'''Point of Contact''': Rick Smith - Richard.Smith@tamucc.edu&lt;br /&gt;
***'''Mailing Address''': 6300 Ocean Dr., Unit 5868, Corpus Christi, TX 78412-5868, USA&lt;br /&gt;
&lt;br /&gt;
Add here: short description (at most 5 lines), URL, Lab name, mailing address of the point of contact&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
*'''gvSIG''' &lt;br /&gt;
&lt;br /&gt;
**gvSIG is a powerful, user-friendly and interoperable GIS. It is easy to work in a variety of formats, vector and raster files, databases and remote services. There are always available all kinds of tools to analyze and manage geographic information.&lt;br /&gt;
&lt;br /&gt;
gvSIG Desktop is designed to be an easily extensible solution, allowing  thus continually improving the software application and developing tailor made solutions. It is open source software, GNU / GPL license, this makes its free use, distribution, study and improvement.&lt;br /&gt;
&lt;br /&gt;
gvSIG Online is an Open Source solution for Spatial Data Infrastructures. It is an integral platform for the Spatial Data Infrastructure (SDI) implementation, 100% open source software. A fast and powerful solution for start up the infrastructure necessary to manage spatial data in an organization in an efficient way. &lt;br /&gt;
&lt;br /&gt;
*Website: http://www.gvsig.com &lt;br /&gt;
*[http://www.gvsig.com/en/diffusion/educational-material?p_p_id=122_INSTANCE_A9eo37KAqtxs&amp;amp;p_p_lifecycle=0&amp;amp;p_p_state=normal&amp;amp;p_p_mode=view&amp;amp;p_p_col_id=column-2&amp;amp;p_p_col_count=1&amp;amp;p_r_p_564233524_resetCur=true&amp;amp;p_r_p_564233524_categoryId=25973 Educational material in English] &lt;br /&gt;
*[http://web.gvsig-training.com/index.php/en/quienes-somos-2/noticias-2/145-the-free-mooc-cycle-gvsig-for-users Free MOOC cycle &amp;quot;gvSIG for Users&amp;quot;]&lt;br /&gt;
*'''Point of Contact''': Mario Carrera - mcarrera [at] gvsig.com&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*'''Geoserver''' &lt;br /&gt;
&lt;br /&gt;
Add here: short description (at most 5 lines), URL, Lab name, mailing address of the point of contact&lt;br /&gt;
&lt;br /&gt;
*'''OpenLayers''' &lt;br /&gt;
&lt;br /&gt;
Add here: short description (at most 5 lines), URL, Lab name, mailing address of the point of contact&lt;br /&gt;
&lt;br /&gt;
*'''PostreSQL''' &lt;br /&gt;
&lt;br /&gt;
Add here: short description (at most 5 lines), URL, Lab name, mailing address of the point of contact&lt;br /&gt;
&lt;br /&gt;
*'''PostGIS''' &lt;br /&gt;
&lt;br /&gt;
Add here: short description (at most 5 lines), URL, Lab name, mailing address of the point of contact&lt;br /&gt;
&lt;br /&gt;
*'''Geonode''' &lt;br /&gt;
&lt;br /&gt;
Add here: short description (at most 5 lines), URL, Lab name, mailing address of the point of contact&lt;br /&gt;
&lt;br /&gt;
*'''[http://www.rasdaman.org rasdaman]'''&lt;br /&gt;
**'''Big Geo Data Lab''' - Spatio-temporal sensor, image, simulation, and statistics data of unlimited size are served rapidly by rasdaman (&amp;quot;raster data manager&amp;quot;). As a multiparallel, distributed analytics engine, rasdaman achieves unparalleled service flexibility, scalability, and performance. Being OGC [http://en.wikipedia.org/wiki/Web_Coverage_Processing_Service WCPS] and [http://en.wikipedia.org/wiki/Web_Coverage_Service WCS] Core Reference Implementation, rasdaman enables access, subsetting, and processing on the fly using open standards interfaces. The WCS suite is a central cornerstone for SDIs: a large, growing number of open-source and proprietary tools supports it (MapServer, GeoServer, OpenLayers, QGIS, ESRI ArcGIS, ...) and the OGC standards are under adoption by ISO (as forthcoming 19123-2) and INSPIRE (&amp;quot;Coverage Download Service&amp;quot;). Significant training material is available already, and is being augmented continuously:&lt;br /&gt;
**'''Link to material''': [http://rasdaman.org/wiki/Workshops OGC Big Geo Data standards and rasdaman workshops] | [http://standards.rasdaman.com/ hands-on lab on Big Data Standards] | [http://kahlua.eecs.jacobs-university.de/~lsis/Big-Earth-Data_the-ARTE-Movie/index.php Big Earth Data] (53min TV documentary) &lt;br /&gt;
**'''Point of Contact''': Peter Baumann - baumann@rasdaman.com&lt;br /&gt;
&lt;br /&gt;
*'''OSGeo-Live''' &lt;br /&gt;
&lt;br /&gt;
OSGeo-Live contains 50 of the best geospatial applications, pre-installed with datasets, along with project overviews and 10 to 15 minute quickstarts for each application. The documentation provides an excellent high level overview of the breadth of geospatial open source applications. It is also used as a plaform for many open source geospatial workshops.&lt;br /&gt;
&lt;br /&gt;
Website: http://live.osge.org&lt;br /&gt;
&lt;br /&gt;
Contact: Cameron Shorter &amp;lt;cam e r onDoTs hort erA T g mai l.com&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*'''Bringing GEOSS services into practice''' &lt;br /&gt;
The &amp;quot;Bringing GEOSS services into practice&amp;quot; workshop aims at teaching how to configure, use and deploy a set of open source software (PostGIS, GeoServer, GeoNetwork, PyWPS, QGIS) to set up a spatial data infrastructure (SDI). Trainees will learn how to publish and share data and metadata using OGC and ISO standards and how to register services into the Global Earth Observation System of Systems (GEOSS).&lt;br /&gt;
&lt;br /&gt;
Website: http://www.geossintopractice.org&lt;br /&gt;
&lt;br /&gt;
Lab: GeoForAll - ISE, University of Geneva: http://www.unige.ch/tigers/fr/autres-reseaux/geoforall/&lt;br /&gt;
&lt;br /&gt;
Contact: Gregory Giuliani &amp;lt;gregory.giuliani AT unige.ch&amp;gt;&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=UNTraining&amp;diff=97756</id>
		<title>UNTraining</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=UNTraining&amp;diff=97756"/>
		<updated>2016-03-29T14:09:48Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: Adding gvSIG to the possible solutions&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Welcome to the UN training page'''&lt;br /&gt;
&lt;br /&gt;
GeoForAll is supporting UN in their migration to geospatial open source applications. In this page we list the training material available for some products that UN will use. Please add your training material here, putting also the reference to all data used in such a way that everybody in using your material can be autonomous. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*'''QGIS''' &lt;br /&gt;
&lt;br /&gt;
**'''FOSS4G GeoAcademy Curriculum''' - 35 hands-on labs written primarily for QGIS with some cross over with GRASS and Inkscape. Labs are aligned to the Geospatial Technology Competency Model. Development was sponsored by a Department of Labor Grant and is released under Creative Commons Attribute 3.0 Unported license. All labs currently written for QGIS 2.8, but we are about to release labs for QGIS 2.14. In addition to labs, lecture material is also developed and being uploaded. All lab instructions and data are [http://spatialquerylab.com/foss4g-academy-curriculum/ available online on our lab website].&lt;br /&gt;
***'''Link to material''': http://spatialquerylab.com/foss4g-academy-curriculum/&lt;br /&gt;
***'''Lab''': Spatial {Query} Lab - http://www.spatialquerylab.com&lt;br /&gt;
***'''Point of Contact''': Rick Smith - Richard.Smith@tamucc.edu&lt;br /&gt;
***'''Mailing Address''': 6300 Ocean Dr., Unit 5868, Corpus Christi, TX 78412-5868, USA&lt;br /&gt;
&lt;br /&gt;
Add here: short description (at most 5 lines), URL, Lab name, mailing address of the point of contact&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
*'''gvSIG''' &lt;br /&gt;
&lt;br /&gt;
***gvSIG is a powerful, user-friendly and interoperable GIS. It is easy to work in a variety of formats, vector and raster files, databases and remote services. There are always available all kinds of tools to analyze and manage geographic information.&lt;br /&gt;
&lt;br /&gt;
gvSIG Desktop is designed to be an easily extensible solution, allowing  thus continually improving the software application and developing tailor made solutions. It is open source software, GNU / GPL license, this makes its free use, distribution, study and improvement.&lt;br /&gt;
&lt;br /&gt;
gvSIG Online is an Open Source solution for Spatial Data Infrastructures. It is an integral platform for the Spatial Data Infrastructure (SDI) implementation, 100% open source software. A fast and powerful solution for start up the infrastructure necessary to manage spatial data in an organization in an efficient way. &lt;br /&gt;
&lt;br /&gt;
***Website: http://www.gvsig.com &lt;br /&gt;
***[http://www.gvsig.com/en/diffusion/educational-material?p_p_id=122_INSTANCE_A9eo37KAqtxs&amp;amp;p_p_lifecycle=0&amp;amp;p_p_state=normal&amp;amp;p_p_mode=view&amp;amp;p_p_col_id=column-2&amp;amp;p_p_col_count=1&amp;amp;p_r_p_564233524_resetCur=true&amp;amp;p_r_p_564233524_categoryId=25973 Educational material in English] &lt;br /&gt;
***[http://web.gvsig-training.com/index.php/en/quienes-somos-2/noticias-2/145-the-free-mooc-cycle-gvsig-for-users Free MOOC cycle &amp;quot;gvSIG for Users&amp;quot;]&lt;br /&gt;
***'''Point of Contact''': Mario Carrera - mcarrera [at] gvsig.com&lt;br /&gt;
&lt;br /&gt;
*'''Geoserver''' &lt;br /&gt;
&lt;br /&gt;
Add here: short description (at most 5 lines), URL, Lab name, mailing address of the point of contact&lt;br /&gt;
&lt;br /&gt;
*'''OpenLayers''' &lt;br /&gt;
&lt;br /&gt;
Add here: short description (at most 5 lines), URL, Lab name, mailing address of the point of contact&lt;br /&gt;
&lt;br /&gt;
*'''PostreSQL''' &lt;br /&gt;
&lt;br /&gt;
Add here: short description (at most 5 lines), URL, Lab name, mailing address of the point of contact&lt;br /&gt;
&lt;br /&gt;
*'''PostGIS''' &lt;br /&gt;
&lt;br /&gt;
Add here: short description (at most 5 lines), URL, Lab name, mailing address of the point of contact&lt;br /&gt;
&lt;br /&gt;
*'''Geonode''' &lt;br /&gt;
&lt;br /&gt;
Add here: short description (at most 5 lines), URL, Lab name, mailing address of the point of contact&lt;br /&gt;
&lt;br /&gt;
*'''[http://www.rasdaman.org rasdaman]'''&lt;br /&gt;
**'''Big Geo Data Lab''' - Spatio-temporal sensor, image, simulation, and statistics data of unlimited size are served rapidly by rasdaman (&amp;quot;raster data manager&amp;quot;). As a multiparallel, distributed analytics engine, rasdaman achieves unparalleled service flexibility, scalability, and performance. Being OGC [http://en.wikipedia.org/wiki/Web_Coverage_Processing_Service WCPS] and [http://en.wikipedia.org/wiki/Web_Coverage_Service WCS] Core Reference Implementation, rasdaman enables access, subsetting, and processing on the fly using open standards interfaces. The WCS suite is a central cornerstone for SDIs: a large, growing number of open-source and proprietary tools supports it (MapServer, GeoServer, OpenLayers, QGIS, ESRI ArcGIS, ...) and the OGC standards are under adoption by ISO (as forthcoming 19123-2) and INSPIRE (&amp;quot;Coverage Download Service&amp;quot;). Significant training material is available already, and is being augmented continuously:&lt;br /&gt;
**'''Link to material''': [http://rasdaman.org/wiki/Workshops OGC Big Geo Data standards and rasdaman workshops] | [http://standards.rasdaman.com/ hands-on lab on Big Data Standards] | [http://kahlua.eecs.jacobs-university.de/~lsis/Big-Earth-Data_the-ARTE-Movie/index.php Big Earth Data] (53min TV documentary) &lt;br /&gt;
**'''Point of Contact''': Peter Baumann - baumann@rasdaman.com&lt;br /&gt;
&lt;br /&gt;
*'''OSGeo-Live''' &lt;br /&gt;
&lt;br /&gt;
OSGeo-Live contains 50 of the best geospatial applications, pre-installed with datasets, along with project overviews and 10 to 15 minute quickstarts for each application. The documentation provides an excellent high level overview of the breadth of geospatial open source applications. It is also used as a plaform for many open source geospatial workshops.&lt;br /&gt;
&lt;br /&gt;
Website: http://live.osge.org&lt;br /&gt;
&lt;br /&gt;
Contact: Cameron Shorter &amp;lt;cam e r onDoTs hort erA T g mai l.com&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*'''Bringing GEOSS services into practice''' &lt;br /&gt;
The &amp;quot;Bringing GEOSS services into practice&amp;quot; workshop aims at teaching how to configure, use and deploy a set of open source software (PostGIS, GeoServer, GeoNetwork, PyWPS, QGIS) to set up a spatial data infrastructure (SDI). Trainees will learn how to publish and share data and metadata using OGC and ISO standards and how to register services into the Global Earth Observation System of Systems (GEOSS).&lt;br /&gt;
&lt;br /&gt;
Website: http://www.geossintopractice.org&lt;br /&gt;
&lt;br /&gt;
Lab: GeoForAll - ISE, University of Geneva: http://www.unige.ch/tigers/fr/autres-reseaux/geoforall/&lt;br /&gt;
&lt;br /&gt;
Contact: Gregory Giuliani &amp;lt;gregory.giuliani AT unige.ch&amp;gt;&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=GvSIG_GSoC_2016_Ideas&amp;diff=97426</id>
		<title>GvSIG GSoC 2016 Ideas</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=GvSIG_GSoC_2016_Ideas&amp;diff=97426"/>
		<updated>2016-03-14T18:32:56Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: Removing one of the ideas&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Use this page to jot down and develop any good idea for the [[Google Summer of Code 2016|2016]] program with gvSIG project. Please, use the gvSIG mailing lists for discussion and check  [[Google Summer of Code 2015|2015]], [[Google Summer of Code 2014|2014]], [[GvSIG GSoC 2013 Ideas|2013]], [[GvSIG GSoC 2012 Ideas|2012]], [[GvSIG GSoC 2011 Ideas|2011]], [[GvSIG GSoC 2010 Ideas|2010]], [[GvSIG GSoC 2009 Ideas|2009]] ideas pages for examples or reference.&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Integrating a tool for urban storm drainage design in gvSIG ==&lt;br /&gt;
&lt;br /&gt;
* '''Product''': gvSIG Desktop&lt;br /&gt;
* '''Possible mentors''': Andrea Antonello, Joaquin del Cerro&lt;br /&gt;
* '''Possible student''': Silvia Franceschi&lt;br /&gt;
&lt;br /&gt;
The main idea behind this project is to port/develop a tool for the design and verification of storm drainage and sewer systems in gvSIG.&lt;br /&gt;
The tool calculates the maximum discharge using a simplified geomorphology based hydrological model considering the morphology of the surface, the drainage area and its permeability.&lt;br /&gt;
Based on this calculation the flow of the water in the pipes is simulated using a cinematic model considering the main characteristics of the pipes (slope, diameter, roughness).&lt;br /&gt;
The results of the simulations are the needed diameter and slope for each pipe of the storm drainage network.&lt;br /&gt;
&lt;br /&gt;
== Add tests and educational games support to gvSIG Educa  ==&lt;br /&gt;
&lt;br /&gt;
* '''Product''': gvSIG Desktop&lt;br /&gt;
* '''Mentors''': Óscar Martínez, Joaquin del Cerro &lt;br /&gt;
* '''Student''': Carlos Colombana &lt;br /&gt;
&lt;br /&gt;
The objective would be to extend the thematic maps support already available to allow to design and play tests and educational games, to be used in geography and maps learning.&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2016_Ideas&amp;diff=96647</id>
		<title>Google Summer of Code 2016 Ideas</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2016_Ideas&amp;diff=96647"/>
		<updated>2016-02-17T08:51:22Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;center&amp;gt;&lt;br /&gt;
[[Image:GSoC2016Logo.jpg|500px|link=https://summerofcode.withgoogle.com/]] &amp;lt;font size=&amp;quot;+3&amp;quot;&amp;gt; @ &amp;lt;/font&amp;gt; &lt;br /&gt;
[[Image:OSGeo_300_127_pixel.png|200px|link=http://www.osgeo.org]]&lt;br /&gt;
&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
-----&lt;br /&gt;
* Back to the main OSGeo [[Google Summer of Code 2016]] wiki page.&lt;br /&gt;
&lt;br /&gt;
* 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]], [[Google Summer of Code 2013 Ideas|2013]] , [[Google Summer of Code 2014 Ideas|2014]] and [[Google Summer of Code 2014 Ideas|2015]].&lt;br /&gt;
-----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== OSGeo Google Summer of Code 2016 ==&lt;br /&gt;
&lt;br /&gt;
The [http://www.osgeo.org Open Source Geospatial Foundation] would like to extend a welcome to all SoC students. On this page you will find links to a host of ideas organized by project. You will find ideas ranging from the depths of computer science graph theory to the heights of visualization. One thing all these ideas have in common is lots and lots of spatial data.&lt;br /&gt;
&lt;br /&gt;
These ideas are '''*only*''' to motivate you, and serve as example of the kind of hills we want to charge up. Your own ideas are more than welcomed - they are encouraged. We view you as the next wave of open source leaders; show us what you've got.&lt;br /&gt;
&lt;br /&gt;
* '''Students: check out the [[Google Summer of Code Recommendations for Students]] page. If you need more information on how to apply you can contact all the mentors via the OSGeo-SoC mailing list''' ([[#How to get in contact via mailing lists|see below]])&lt;br /&gt;
&lt;br /&gt;
* There is a [https://developers.google.com/open-source/soc/resources/flyers Google SoC flyer] to look at and post in appropriate places.&lt;br /&gt;
&lt;br /&gt;
* Ok, [[OSGeo]] is involved in working with maps and things, but what kind of projects does it really do? Have a look at the [http://planet.osgeo.org/ live blog feed] to see what people are working on right now.&lt;br /&gt;
&lt;br /&gt;
* Mentors, there's an additional link providing some tips and specifying your responsibilities on the main OSGeo [[Google_Summer_of_Code_2016_Administrative]] wiki page.&lt;br /&gt;
&lt;br /&gt;
== The ideas pages ==&lt;br /&gt;
'''''[Check back often, it's a work in progress]'''''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Each participating project's list of ideas is on the respective projects' wikis, with a short description of the project and what type of students would be interested in it:&lt;br /&gt;
&lt;br /&gt;
=== OSGeo Foundation member projects ===&lt;br /&gt;
&lt;br /&gt;
''More coming soon: Get started talking to your favorite project's development team today!''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:logo-grass.png|60px|right]]&lt;br /&gt;
* [https://trac.osgeo.org/grass/wiki/GSoC/2016 '''GRASS GIS''' SoC Ideas]: [http://grass.osgeo.org GRASS GIS] is an open source GIS focusing on analysis, modeling and visualization. It is  a collection of modules written in C and Python and has a GUI written in wxPython. If you know Python, or want to implement algorithms in C, take a look!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:logo-qgis.png|60px|right]]&lt;br /&gt;
* [http://hub.qgis.org/wiki/quantum-gis/Google_Summer_of_Code_2016 '''QGIS''' SoC Ideas]: [http://www.qgis.org QGIS] is a user friendly Open Source Geographic Information System (GIS) that runs on Linux, Unix, Mac OSX, and Windows. QGIS supports vector, raster, and database formats. It is written in C++ and Python.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-gdal.png|60px|right]]&lt;br /&gt;
* [http://trac.osgeo.org/gdal/wiki/SummerOfCode '''GDAL''' Ideas]: [http://www.gdal.org GDAL] is a C++ library for reading and writing geospatial data raster and vector formats.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
* [http://trac.osgeo.org/osgeo4w/wiki/Reports '''OSGeo4W''']: -  OSGeo4W is a binary distribution of a broad set of open source geospatial software for Win32 environments (Windows 7, XP, etc).&lt;br /&gt;
[[Image:Logo-osgeo4w-mini.png|60px|right]]&lt;br /&gt;
:* ''Idea'': We need to extend support to x64 based platforms to handle larger datasets and circumvent memory restrictions. This is a distribution and packaging project which will involve most/all of OSGeo member projects. (''ed. note: keep in mind that to fulfill GSoC requirements each project must have a majority coding component, so lots of scripting, testing, and Makefiles!'')--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:logo-gvSIG.png|60px|right]]&lt;br /&gt;
* [[GvSIG_GSoC_2016_Ideas|'''gvSIG''' Ideas]]: gvSIG is a free GIS project for [http://www.gvsig.com/en/web/guest/products/gvsig-desktop Desktop]. The gvSIG project looks for students with Java or Python skills that want to develop new ideas on this software. &lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-opticks.png|right]]&lt;br /&gt;
* [http://opticks.org/confluence/display/opticksDev/Google+Summer+of+Code '''Opticks''' Ideas]: [http://opticks.org/ Opticks] is an extensible [http://en.wikipedia.org/wiki/Remote_sensing remote sensing] and imagery analysis desktop application. It provides a framework to process remote sensing data such as [http://en.wikipedia.org/wiki/Hyperspectral_imaging Hyperspectral] (HSI), [http://en.wikipedia.org/wiki/Multi-spectral_image Multispectral] (MSI), and [http://en.wikipedia.org/wiki/Synthetic_aperture_radar Synthetic aperture radar] (SAR) imagery and video. The application is written in C++ and licensed under LGPL v2.1. Extensions are written using C++ or Python. You can review the [http://opticks.org/confluence/display/opticksExt/All+Opticks+Extensions available extensions] and [http://opticks.org/confluence/display/opticks/Feature+Tour+-+Your+Data feature tour] to get a better idea of what Opticks can do.--&amp;gt;&lt;br /&gt;
&amp;lt;!-- &lt;br /&gt;
[[Image:Osgeolive_60px.png|right]]&lt;br /&gt;
* [http://wiki.osgeo.org/wiki/Live_GIS_GSoC_2015 '''OSGeo-Live''' Ideas]: [http://live.osgeo.org OSGeo-Live] packages over 50 of the best geospatial open source projects, preconfigured with data, quickstarts and project overviews. We have packaging and automated build projects. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- &lt;br /&gt;
[[Image:logo-postgis.png|60px|right]] &lt;br /&gt;
* [http://trac.osgeo.org/postgis/wiki/GoogleSummerCode '''PostGIS''' Ideas]: [http://postgis.net PostGIS] spatially enables the popular PostgreSQL object-relational database, allowing it to be used as a back-end database for geographic information systems (GIS) and web-mapping applications.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-ossim.png|90px|right]]&lt;br /&gt;
* [https://trac.osgeo.org/ossim/wiki/GSoC_2015 '''OSSIM''' SoC Ideas]: [http://trac.osgeo.org/ossim/wiki OSSIM] Open Source Software Image Map (OSSIM) is a high performance engine for remote sensing, image processing, geographical information systems and photogrammetry. The software has been under active development since 1996 and is deployed across a number of private, federal and civilian agencies. It is written in C++.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Logo_OTB.png|60px|right]]&lt;br /&gt;
* [http://wiki.orfeo-toolbox.org/index.php/Proposals_for_GSoC_2015 '''OTB''' SoC Ideas]: [http://www.orfeo-toolbox.org ORFEO ToolBox] (OTB) is an open source library for remote sensing image processing.Targeted algorithms for high resolution optical images (Pleiades, SPOT, QuickBird, WorldView, Landsat, Ikonos), hyperspectral sensors (Hyperion) or SAR (TerraSarX, ERS, Palsar) are available. The software has been under active development since 2006 and is written in C++ and it includes also side projects also open source with GUI like Monteverdi. OTB has recently started the incubation process into OSGeo.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Mapserver.png|100px|right]]&lt;br /&gt;
* [http://wiki.osgeo.org/wiki/MapServer_2015_SOC_Ideas '''Mapserver''' SoC Ideas]: MapServer is a Web Mapping Engine; an Open Source platform for publishing spatial data and interactive mapping applications to the web.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Logo-istSOS.png|60px|right]]&lt;br /&gt;
* [http://sourceforge.net/p/istsos/wiki/GSoC%20ideas%202015/ '''istSOS''' Ideas]: [http://sourceforge.net/projects/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.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-geos.png|60px|right]]&lt;br /&gt;
* [http://trac.osgeo.org/geos/wiki/GSoC '''GEOS''' Ideas]: GEOS (Geometry Engine - Open Source) is a C++ port of the JTS Topology Suite (JTS). It includes the OpenGIS Simple Features for SQL spatial predicate functions and spatial operators, as well as specific JTS enhanced topology functions.&lt;br /&gt;
--&amp;gt; &lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-geoserver-crop.png|50px|right]]&lt;br /&gt;
* [https://github.com/geoserver/geoserver/wiki/GSOC-Ideas GSOC Ideas]: [http://live.osgeo.org/en/overview/geoserver_overview.html '''GeoServer'''] is a web server that allows you to serve maps and data from a variety of formats to standard clients such as web browsers and desktop GIS applications.  GeoServer works with the Open Geospatial Consortium (OGC) standards Web Feature Service (WFS), Web Coverage Service (WCS), Web Processing Service (WPS) and Web Map Service (WMS) standards.&lt;br /&gt;
:* The GeoServer team asks applicants to introduce themselves on the geoserver-devel list ( Communicating in public is a key success factor to open source development )--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Geotools-logo.png|50px|right]]&lt;br /&gt;
* [http://docs.codehaus.org/display/GEOTOOLS/Google+Summer+of+Code ''GSOC'']:  [http://live.osgeo.org/en/overview/geotools_overview.html '''GeoTools'''] GeoTools is an open source Java library for working with geospatial data, including both data access, data structures, processing and a powerful rendering engine. GeoTools is a modular library used in a wide range of web service, command line tools and desktop applications.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:ZOO-Project-mini.png|right]]&lt;br /&gt;
* [http://zoo-project.org/trac/wiki/ZOO_SoC_Idea_2015 '''ZOO-Project''' Soc Ideas]: ZOO-Project is a WPS (Web Processing Service) open source project released under  MIT/X-11 style license. It provides an OGC WPS compliant developer-friendly framework to create and chain WPS Web services. --&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:ZOO-Project-mini.png|right]]&lt;br /&gt;
* [http://www.zoo-project.org/trac/wiki/ZOO_SoC_Ideas '''ZOO-Project''' Ideas]: [http://www.zoo-project.org ZOO-Project] is a WPS open source project released under a MIT/X-11 style license. We are seeking a developper to handle migration from SpiderMonky to Google v8 JavaScript runtime environment, upgrade the ZOO-API, build a demo package and develop new services dedicated to raster gesture.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
We expect ideas also from [http://live.osgeo.org/en/overview/mapbender_overview.html MapBender], [http://live.osgeo.org/en/overview/geomoose_overview.html GeoMOOSE], [http://mapserver.org/ MapServer], ...&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Osgeo-live.png|230px|right]]&lt;br /&gt;
* [http://wiki.osgeo.org/wiki/Live_GIS_GSoC_2015 '''Osgeo-Live''' SoC Ideas]: [http://live.osgeo.org/en/index.html OSGeo-Live] is a self-contained bootable DVD, USB thumb drive or Virtual Machine based on Lubuntu, that allows you to try a wide variety of open source geospatial software without installing anything. It is composed entirely of free software, allowing it to be freely distributed, duplicated and passed around. It provides pre-configured applications for a range of geospatial use cases, including storage, publishing, viewing, analysis and manipulation of data. It also contains sample datasets and documentation.--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Guest projects ===&lt;br /&gt;
&lt;br /&gt;
Like-minded geospatial projects to take part under OSGeo umbrella. If you wish your software project to be listed here, please contact [[User:Madi|Madi]] or Anne.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:Pgrouting-logo.png|60px|right]]&lt;br /&gt;
* [https://github.com/pgRouting/pgrouting/wiki/GSoC-Ideas '''pgRouting''' Ideas]: [http://pgrouting.org pgRouting] extends the PostGIS / PostgreSQL geospatial database to provide geospatial routing functionality and more.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Image:Pywps-logo.png|60px|right]]&lt;br /&gt;
* [https://github.com/geopython/pywps/wiki/GSoC-2016-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. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-uDig.png|60px|right]]&lt;br /&gt;
* [https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-Ideas-2015 '''JGrasstools''' and '''uDig''' Spatial Toolbox SoC Ideas]: The JGrasstools project is a geospatial modules library dedicated to hydrology and geomorphology. It is the base of the modules for uDig's Spatial Toolbox.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:otp-logo.png|80px|right]]&lt;br /&gt;
* [http://github.com/opentripplanner/OpenTripPlanner/wiki/2015-Google-Summer-of-Code-Ideas '''OpenTripPlanner''' Ideas]: [http://github.com/opentripplanner/OpenTripPlanner OpenTripPlanner] is an open source multi-modal trip planner. It depends on open data in open standard file formats (GTFS and OpenStreetMap), includes a REST API for journey planning, a map-based Javascript client, and an [http://github.com/CUTR-at-USF/OpenTripPlanner-for-Android/wiki Android App].--&amp;gt;&lt;br /&gt;
&amp;lt;!-- &lt;br /&gt;
please contact us first&lt;br /&gt;
* [http://lsi.iiit.ac.in/redmine/projects/lsiviewer/wiki/GSoC_2015 '''LSIViewer''' Ideas]: [http://lsi.iiit.ac.in/redmine/projects/lsiviewer/wiki/Main/ LSIViewer] Libre Spatial Information Viewer (LSIViewer) is a web based geospatial data viewer which allows you to view your data, style it, export to SVG/PNG/JPEG formats and can be for used in reports and presentation. It uses Wt, a C++ web toolkit which comes with its own http server and has good support for embedded platforms. The initial version had support for only shapefiles but around 13 vector formats, OSM layer, 3D view has been experimental on the lab's internal repository.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Logo-cartaro.png|60px|right]]&lt;br /&gt;
* [https://groups.drupal.org/node/407408 '''Cartaro''' Ideas]: [http://cartaro.org Cartaro] provides geospatial functionality and web services within the Drupal Content Management System (CMS). It is builds upon robust Open Source components: the PostGIS database, GeoServer and GeoWebCache web services, OpenLayers maps in the browser, all managed from within the powerful Drupal CMS.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Geonode logo.png|60px|right]]&lt;br /&gt;
* [https://github.com/GeoNode/geonode/wiki/Google-Summer-of-Code-Ideas-2015 '''GeoNode''' Ideas]: [http://geonode.org/ GeoNode] is an Open Source Geospatial Content Management System: a web-based application and platform for developing Geospatial Information Systems (GIS) and for deploying spatial data infrastructures (SDI). It is designed to be easily extended and modified, and can be integrated into existing platforms. Written with the Python Django web application, it is based on other great Open Source components such as PostGIS, GeoServer, OpenLayers and GeoExplorer.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:neo4j-spatial_64.png|right]]&lt;br /&gt;
* [https://github.com/neo4j/GSoC/wiki '''Neo4j Spatial''' Ideas]: [https://github.com/neo4j/spatial Neo4j Spatial] is an Open Source library extending the popular [http://neo4j.org Neo4j Graph Database] with a number of features for GIS enabling your data model. It embeds and relies on JTS and GeoTools, and provides the ability to store your domain model in many internal formats, and has utilities for import and export of Shapefiles and OpenStreetMap data. We've received contributions from GSoC projects in 2010, 2011 and 2012.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Logo-cartoDB.png|70px|right]]&lt;br /&gt;
* [https://github.com/CartoDB/cartodb/wiki/GoogleSummerCode '''CartoDB Ideas''']: [http://cartodb.com/develop CartoDB] is a cloud based mapping, analysis and visualization engine that lets users build spatial applications for both mobile and the web. Students will need to be able to use PHP and PostgreSQL.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
* '''FIXME''': move to a member project's idea page:&lt;br /&gt;
: ''[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.''&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Logo-mapnik.png|100px|right]]&lt;br /&gt;
* [https://github.com/mapnik/mapnik/wiki/GSOC-Ideas '''Mapnik''' Ideas]: [http://mapnik.org/ Mapnik] is a Free Toolkit for developing mapping applications. It\u2019s 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.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== See also ===&lt;br /&gt;
&lt;br /&gt;
Other like minded projects do not participate to GSoC under OSGeo umbrella, but with their own organization. You may want to visit also their page:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
* [https://wiki.52north.org/bin/view/Projects/GSoC2015ProjectIdeas '''52°North''' Ideas]--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- [[Image:Logo-osm6.png|60px|right]] &lt;br /&gt;
* [http://wiki.openstreetmap.org/wiki/Google_Summer_of_Code/2015/Project_Ideas '''OpenStreetMap''' Ideas]--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[http://osm.org/ OSM] is a project aimed squarely at creating and providing free geographic data such as street maps to anyone who wants them. The project was started because most maps you think of as free actually have legal or technical restrictions on their use, holding back people from using them in creative, productive or unexpected ways.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Don't see in the list the project you're interested in? ===&lt;br /&gt;
&lt;br /&gt;
Contact them in their developers mailing list! Feel free to propose your own idea and get feedback!&lt;br /&gt;
&lt;br /&gt;
== I want to apply as a student ==&lt;br /&gt;
&lt;br /&gt;
Before applying as a student, check out the [[Google Summer of Code Recommendations for Students]] page.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Which project do I choose? ===&lt;br /&gt;
&lt;br /&gt;
Most of the software projects are available pre-built on our Live demo { DVD | USB stick | VirtualMachine } with project overviews and short tutorials where you can try everything out.&lt;br /&gt;
: View the documents and download the ISO from http://live.osgeo.org&lt;br /&gt;
[[File:Osgeolive wordle.png|400px|center]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Important dates ===&lt;br /&gt;
&lt;br /&gt;
* [https://developers.google.com/open-source/gsoc/timeline '''The official timeline''']&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- {{done}} --&amp;gt;&lt;br /&gt;
* Feb 29: Google announces accepted organizations.&lt;br /&gt;
: Please start talking to the dev communities you are interested in ''now''.&lt;br /&gt;
* March 14:  Student applications open.&lt;br /&gt;
: The earlier you start the more probable it is that you will be accepted!&lt;br /&gt;
: ''There is two way feedback during the application process which really helps you improve and clarify your application before the final deadline. The better your involvement with your potential mentors during this period, the better your chances of being selected.''&lt;br /&gt;
* March 25:  Student application deadline.&lt;br /&gt;
* April 22: '''Accepted student proposals are announced and Community Bonding Period begins.'''&lt;br /&gt;
* May 23: '''Coding begins!'''&lt;br /&gt;
: (''you may unofficially start a week or two earlier if you know you'll have to take a week or two off during The Summer or you'll be sitting finals in the first week(s) of the program. This must be reflected in your application timeline'')&lt;br /&gt;
* June 20 - 27: Mid-term evaluation &lt;br /&gt;
* August 15-23: '''Pencils down!'''&lt;br /&gt;
* August 23 -29: Final evaluations&lt;br /&gt;
* August 30: Final results announced&lt;br /&gt;
&lt;br /&gt;
[Back to [[Google Summer of Code 2016]] @ OSGeo]&lt;br /&gt;
[[Category: Google Summer of Code]]&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=GvSIG_GSoC_2016_Ideas&amp;diff=96636</id>
		<title>GvSIG GSoC 2016 Ideas</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=GvSIG_GSoC_2016_Ideas&amp;diff=96636"/>
		<updated>2016-02-16T14:40:39Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: Created page with &amp;quot;Use this page to jot down and develop any good idea for the 2016 program with gvSIG project. Please, use the gvSIG mailing lists for discussion...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Use this page to jot down and develop any good idea for the [[Google Summer of Code 2016|2016]] program with gvSIG project. Please, use the gvSIG mailing lists for discussion and check  [[Google Summer of Code 2015|2015]], [[Google Summer of Code 2014|2014]], [[GvSIG GSoC 2013 Ideas|2013]], [[GvSIG GSoC 2012 Ideas|2012]], [[GvSIG GSoC 2011 Ideas|2011]], [[GvSIG GSoC 2010 Ideas|2010]], [[GvSIG GSoC 2009 Ideas|2009]] ideas pages for examples or reference.&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Integrating R library into gvSIG Desktop ==&lt;br /&gt;
&lt;br /&gt;
* '''Product''': gvSIG Desktop&lt;br /&gt;
* '''Possible mentor''': &lt;br /&gt;
* '''Possible students''': &lt;br /&gt;
&lt;br /&gt;
The main idea behind this project is about integrating the R library into gvSIG Desktop. R is a free software environment for statistical computing and graphics.&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2016_Ideas&amp;diff=96628</id>
		<title>Google Summer of Code 2016 Ideas</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2016_Ideas&amp;diff=96628"/>
		<updated>2016-02-16T13:14:18Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;center&amp;gt;&lt;br /&gt;
[[Image:GSoC2016Logo.jpg|500px|link=https://summerofcode.withgoogle.com/]] &amp;lt;font size=&amp;quot;+3&amp;quot;&amp;gt; @ &amp;lt;/font&amp;gt; &lt;br /&gt;
[[Image:OSGeo_300_127_pixel.png|200px|link=http://www.osgeo.org]]&lt;br /&gt;
&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
-----&lt;br /&gt;
* Back to the main OSGeo [[Google Summer of Code 2016]] wiki page.&lt;br /&gt;
&lt;br /&gt;
* 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]], [[Google Summer of Code 2013 Ideas|2013]] , [[Google Summer of Code 2014 Ideas|2014]] and [[Google Summer of Code 2014 Ideas|2015]].&lt;br /&gt;
-----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== OSGeo Google Summer of Code 2016 ==&lt;br /&gt;
&lt;br /&gt;
The [http://www.osgeo.org Open Source Geospatial Foundation] would like to extend a welcome to all SoC students. On this page you will find links to a host of ideas organized by project. You will find ideas ranging from the depths of computer science graph theory to the heights of visualization. One thing all these ideas have in common is lots and lots of spatial data.&lt;br /&gt;
&lt;br /&gt;
These ideas are '''*only*''' to motivate you, and serve as example of the kind of hills we want to charge up. Your own ideas are more than welcomed - they are encouraged. We view you as the next wave of open source leaders; show us what you've got.&lt;br /&gt;
&lt;br /&gt;
* '''Students: check out the [[Google Summer of Code Recommendations for Students]] page. If you need more information on how to apply you can contact all the mentors via the OSGeo-SoC mailing list''' ([[#How to get in contact via mailing lists|see below]])&lt;br /&gt;
&lt;br /&gt;
* There is a [https://developers.google.com/open-source/soc/resources/flyers Google SoC flyer] to look at and post in appropriate places.&lt;br /&gt;
&lt;br /&gt;
* Ok, [[OSGeo]] is involved in working with maps and things, but what kind of projects does it really do? Have a look at the [http://planet.osgeo.org/ live blog feed] to see what people are working on right now.&lt;br /&gt;
&lt;br /&gt;
* Mentors, there's an additional link providing some tips and specifying your responsibilities on the main OSGeo [[Google_Summer_of_Code_2016_Administrative]] wiki page.&lt;br /&gt;
&lt;br /&gt;
== The ideas pages ==&lt;br /&gt;
'''''[Check back often, it's a work in progress]'''''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Each participating project's list of ideas is on the respective projects' wikis, with a short description of the project and what type of students would be interested in it:&lt;br /&gt;
&lt;br /&gt;
=== OSGeo Foundation member projects ===&lt;br /&gt;
&lt;br /&gt;
* ''More coming soon: Get started talking to your favorite project's development team today!''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:logo-grass.png|60px|right]]&lt;br /&gt;
* [https://trac.osgeo.org/grass/wiki/GSoC/2015 '''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!--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:logo-qgis.png|60px|right]]&lt;br /&gt;
* [http://hub.qgis.org/wiki/quantum-gis/Google_Summer_of_Code_2015 '''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.--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:logo-gdal.png|60px|right]]&lt;br /&gt;
* [http://trac.osgeo.org/gdal/wiki/SummerOfCode '''GDAL''' Ideas]: [http://www.gdal.org GDAL] is a C++ library for reading and writing geospatial data raster and vector formats.--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
* [http://trac.osgeo.org/osgeo4w/wiki/Reports '''OSGeo4W''']: -  OSGeo4W is a binary distribution of a broad set of open source geospatial software for Win32 environments (Windows 7, XP, etc).&lt;br /&gt;
[[Image:Logo-osgeo4w-mini.png|60px|right]]&lt;br /&gt;
:* ''Idea'': We need to extend support to x64 based platforms to handle larger datasets and circumvent memory restrictions. This is a distribution and packaging project which will involve most/all of OSGeo member projects. (''ed. note: keep in mind that to fulfill GSoC requirements each project must have a majority coding component, so lots of scripting, testing, and Makefiles!'')--&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!--[[Image:logo-gvSIG.png|60px|right]]&lt;br /&gt;
* [[GvSIG_GSoC_2016_Ideas|'''gvSIG''' Ideas]]: gvSIG is a free GIS project for [http://www.gvsig.com/en/web/guest/products/gvsig-desktop Desktop]. The gvSIG project looks for students with Java or Python skills that want to develop new ideas on this software. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:logo-opticks.png|right]]&lt;br /&gt;
* [http://opticks.org/confluence/display/opticksDev/Google+Summer+of+Code '''Opticks''' Ideas]: [http://opticks.org/ Opticks] is an extensible [http://en.wikipedia.org/wiki/Remote_sensing remote sensing] and imagery analysis desktop application. It provides a framework to process remote sensing data such as [http://en.wikipedia.org/wiki/Hyperspectral_imaging Hyperspectral] (HSI), [http://en.wikipedia.org/wiki/Multi-spectral_image Multispectral] (MSI), and [http://en.wikipedia.org/wiki/Synthetic_aperture_radar Synthetic aperture radar] (SAR) imagery and video. The application is written in C++ and licensed under LGPL v2.1. Extensions are written using C++ or Python. You can review the [http://opticks.org/confluence/display/opticksExt/All+Opticks+Extensions available extensions] and [http://opticks.org/confluence/display/opticks/Feature+Tour+-+Your+Data feature tour] to get a better idea of what Opticks can do.--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- &lt;br /&gt;
[[Image:Osgeolive_60px.png|right]]&lt;br /&gt;
* [http://wiki.osgeo.org/wiki/Live_GIS_GSoC_2015 '''OSGeo-Live''' Ideas]: [http://live.osgeo.org OSGeo-Live] packages over 50 of the best geospatial open source projects, preconfigured with data, quickstarts and project overviews. We have packaging and automated build projects. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- &lt;br /&gt;
[[Image:logo-postgis.png|60px|right]] &lt;br /&gt;
* [http://trac.osgeo.org/postgis/wiki/GoogleSummerCode '''PostGIS''' Ideas]: [http://postgis.net PostGIS] spatially enables the popular PostgreSQL object-relational database, allowing it to be used as a back-end database for geographic information systems (GIS) and web-mapping applications.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-ossim.png|90px|right]]&lt;br /&gt;
* [https://trac.osgeo.org/ossim/wiki/GSoC_2015 '''OSSIM''' SoC Ideas]: [http://trac.osgeo.org/ossim/wiki OSSIM] Open Source Software Image Map (OSSIM) is a high performance engine for remote sensing, image processing, geographical information systems and photogrammetry. The software has been under active development since 1996 and is deployed across a number of private, federal and civilian agencies. It is written in C++.--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:Logo_OTB.png|60px|right]]&lt;br /&gt;
* [http://wiki.orfeo-toolbox.org/index.php/Proposals_for_GSoC_2015 '''OTB''' SoC Ideas]: [http://www.orfeo-toolbox.org ORFEO ToolBox] (OTB) is an open source library for remote sensing image processing.Targeted algorithms for high resolution optical images (Pleiades, SPOT, QuickBird, WorldView, Landsat, Ikonos), hyperspectral sensors (Hyperion) or SAR (TerraSarX, ERS, Palsar) are available. The software has been under active development since 2006 and is written in C++ and it includes also side projects also open source with GUI like Monteverdi. OTB has recently started the incubation process into OSGeo.--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:Mapserver.png|100px|right]]&lt;br /&gt;
* [http://wiki.osgeo.org/wiki/MapServer_2015_SOC_Ideas '''Mapserver''' SoC Ideas]: MapServer is a Web Mapping Engine; an Open Source platform for publishing spatial data and interactive mapping applications to the web.--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:Logo-istSOS.png|60px|right]]&lt;br /&gt;
* [http://sourceforge.net/p/istsos/wiki/GSoC%20ideas%202015/ '''istSOS''' Ideas]: [http://sourceforge.net/projects/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.--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-geos.png|60px|right]]&lt;br /&gt;
* [http://trac.osgeo.org/geos/wiki/GSoC '''GEOS''' Ideas]: GEOS (Geometry Engine - Open Source) is a C++ port of the JTS Topology Suite (JTS). It includes the OpenGIS Simple Features for SQL spatial predicate functions and spatial operators, as well as specific JTS enhanced topology functions.&lt;br /&gt;
--&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:logo-geoserver-crop.png|50px|right]]&lt;br /&gt;
* [https://github.com/geoserver/geoserver/wiki/GSOC-Ideas GSOC Ideas]: [http://live.osgeo.org/en/overview/geoserver_overview.html '''GeoServer'''] is a web server that allows you to serve maps and data from a variety of formats to standard clients such as web browsers and desktop GIS applications.  GeoServer works with the Open Geospatial Consortium (OGC) standards Web Feature Service (WFS), Web Coverage Service (WCS), Web Processing Service (WPS) and Web Map Service (WMS) standards.&lt;br /&gt;
:* The GeoServer team asks applicants to introduce themselves on the geoserver-devel list ( Communicating in public is a key success factor to open source development )--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:Geotools-logo.png|50px|right]]&lt;br /&gt;
* [http://docs.codehaus.org/display/GEOTOOLS/Google+Summer+of+Code ''GSOC'']:  [http://live.osgeo.org/en/overview/geotools_overview.html '''GeoTools'''] GeoTools is an open source Java library for working with geospatial data, including both data access, data structures, processing and a powerful rendering engine. GeoTools is a modular library used in a wide range of web service, command line tools and desktop applications.--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:ZOO-Project-mini.png|right]]&lt;br /&gt;
* [http://zoo-project.org/trac/wiki/ZOO_SoC_Idea_2015 '''ZOO-Project''' Soc Ideas]: ZOO-Project is a WPS (Web Processing Service) open source project released under  MIT/X-11 style license. It provides an OGC WPS compliant developer-friendly framework to create and chain WPS Web services. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:ZOO-Project-mini.png|right]]&lt;br /&gt;
* [http://www.zoo-project.org/trac/wiki/ZOO_SoC_Ideas '''ZOO-Project''' Ideas]: [http://www.zoo-project.org ZOO-Project] is a WPS open source project released under a MIT/X-11 style license. We are seeking a developper to handle migration from SpiderMonky to Google v8 JavaScript runtime environment, upgrade the ZOO-API, build a demo package and develop new services dedicated to raster gesture.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
We expect ideas also from [http://live.osgeo.org/en/overview/mapbender_overview.html MapBender], [http://live.osgeo.org/en/overview/geomoose_overview.html GeoMOOSE], [http://mapserver.org/ MapServer], ...&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:Osgeo-live.png|230px|right]]&lt;br /&gt;
* [http://wiki.osgeo.org/wiki/Live_GIS_GSoC_2015 '''Osgeo-Live''' SoC Ideas]: [http://live.osgeo.org/en/index.html OSGeo-Live] is a self-contained bootable DVD, USB thumb drive or Virtual Machine based on Lubuntu, that allows you to try a wide variety of open source geospatial software without installing anything. It is composed entirely of free software, allowing it to be freely distributed, duplicated and passed around. It provides pre-configured applications for a range of geospatial use cases, including storage, publishing, viewing, analysis and manipulation of data. It also contains sample datasets and documentation.--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Guest projects ===&lt;br /&gt;
&lt;br /&gt;
Like-minded geospatial projects to take part under OSGeo umbrella. If you wish your software project to be listed here, please contact [[User:Madi|Madi]] or Anne.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:Pgrouting-logo.png|60px|right]]&lt;br /&gt;
* [https://github.com/pgRouting/pgrouting/wiki/GSoC-Ideas '''pgRouting''' Ideas]: [http://pgrouting.org pgRouting] extends the PostGIS / PostgreSQL geospatial database to provide geospatial routing functionality and more.--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:Pywps-logo.png|60px|right]]&lt;br /&gt;
* [https://github.com/jachym/pywps-4/wiki/GSOC-2015-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. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:logo-uDig.png|60px|right]]&lt;br /&gt;
* [https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-Ideas-2015 '''JGrasstools''' and '''uDig''' Spatial Toolbox SoC Ideas]: The JGrasstools project is a geospatial modules library dedicated to hydrology and geomorphology. It is the base of the modules for uDig's Spatial Toolbox.--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:otp-logo.png|80px|right]]&lt;br /&gt;
* [http://github.com/opentripplanner/OpenTripPlanner/wiki/2015-Google-Summer-of-Code-Ideas '''OpenTripPlanner''' Ideas]: [http://github.com/opentripplanner/OpenTripPlanner OpenTripPlanner] is an open source multi-modal trip planner. It depends on open data in open standard file formats (GTFS and OpenStreetMap), includes a REST API for journey planning, a map-based Javascript client, and an [http://github.com/CUTR-at-USF/OpenTripPlanner-for-Android/wiki Android App].--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- please contact us first&lt;br /&gt;
* [http://lsi.iiit.ac.in/redmine/projects/lsiviewer/wiki/GSoC_2015 '''LSIViewer''' Ideas]: [http://lsi.iiit.ac.in/redmine/projects/lsiviewer/wiki/Main/ LSIViewer] Libre Spatial Information Viewer (LSIViewer) is a web based geospatial data viewer which allows you to view your data, style it, export to SVG/PNG/JPEG formats and can be for used in reports and presentation. It uses Wt, a C++ web toolkit which comes with its own http server and has good support for embedded platforms. The initial version had support for only shapefiles but around 13 vector formats, OSM layer, 3D view has been experimental on the lab's internal repository.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Logo-cartaro.png|60px|right]]&lt;br /&gt;
* [https://groups.drupal.org/node/407408 '''Cartaro''' Ideas]: [http://cartaro.org Cartaro] provides geospatial functionality and web services within the Drupal Content Management System (CMS). It is builds upon robust Open Source components: the PostGIS database, GeoServer and GeoWebCache web services, OpenLayers maps in the browser, all managed from within the powerful Drupal CMS.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Geonode logo.png|60px|right]]&lt;br /&gt;
* [https://github.com/GeoNode/geonode/wiki/Google-Summer-of-Code-Ideas-2015 '''GeoNode''' Ideas]: [http://geonode.org/ GeoNode] is an Open Source Geospatial Content Management System: a web-based application and platform for developing Geospatial Information Systems (GIS) and for deploying spatial data infrastructures (SDI). It is designed to be easily extended and modified, and can be integrated into existing platforms. Written with the Python Django web application, it is based on other great Open Source components such as PostGIS, GeoServer, OpenLayers and GeoExplorer.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:neo4j-spatial_64.png|right]]&lt;br /&gt;
* [https://github.com/neo4j/GSoC/wiki '''Neo4j Spatial''' Ideas]: [https://github.com/neo4j/spatial Neo4j Spatial] is an Open Source library extending the popular [http://neo4j.org Neo4j Graph Database] with a number of features for GIS enabling your data model. It embeds and relies on JTS and GeoTools, and provides the ability to store your domain model in many internal formats, and has utilities for import and export of Shapefiles and OpenStreetMap data. We've received contributions from GSoC projects in 2010, 2011 and 2012.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Logo-cartoDB.png|70px|right]]&lt;br /&gt;
* [https://github.com/CartoDB/cartodb/wiki/GoogleSummerCode '''CartoDB Ideas''']: [http://cartodb.com/develop CartoDB] is a cloud based mapping, analysis and visualization engine that lets users build spatial applications for both mobile and the web. Students will need to be able to use PHP and PostgreSQL.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
* '''FIXME''': move to a member project's idea page:&lt;br /&gt;
: ''[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.''&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Logo-mapnik.png|100px|right]]&lt;br /&gt;
* [https://github.com/mapnik/mapnik/wiki/GSOC-Ideas '''Mapnik''' Ideas]: [http://mapnik.org/ Mapnik] is a Free Toolkit for developing mapping applications. It\u2019s 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.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== See also ===&lt;br /&gt;
&lt;br /&gt;
Other like minded projects do not participate to GSoC under OSGeo umbrella, but with their own organization. You may want to visit also their page:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
* [https://wiki.52north.org/bin/view/Projects/GSoC2015ProjectIdeas '''52°North''' Ideas]--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- [[Image:Logo-osm6.png|60px|right]] &lt;br /&gt;
* [http://wiki.openstreetmap.org/wiki/Google_Summer_of_Code/2015/Project_Ideas '''OpenStreetMap''' Ideas]--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[http://osm.org/ OSM] is a project aimed squarely at creating and providing free geographic data such as street maps to anyone who wants them. The project was started because most maps you think of as free actually have legal or technical restrictions on their use, holding back people from using them in creative, productive or unexpected ways.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Don't see in the list the project you're interested in? ===&lt;br /&gt;
&lt;br /&gt;
Contact them in their developers mailing list! Feel free to propose your own idea and get feedback!&lt;br /&gt;
&lt;br /&gt;
== I want to apply as a student ==&lt;br /&gt;
&lt;br /&gt;
Before applying as a student, check out the [[Google Summer of Code Recommendations for Students]] page.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Which project do I choose? ===&lt;br /&gt;
&lt;br /&gt;
Most of the software projects are available pre-built on our Live demo { DVD | USB stick | VirtualMachine } with project overviews and short tutorials where you can try everything out.&lt;br /&gt;
: View the documents and download the ISO from http://live.osgeo.org&lt;br /&gt;
[[File:Osgeolive wordle.png|400px|center]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Important dates ===&lt;br /&gt;
&lt;br /&gt;
* [https://developers.google.com/open-source/gsoc/timeline '''The official timeline''']&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- {{done}} --&amp;gt;&lt;br /&gt;
* Feb 29: Google announces accepted organizations.&lt;br /&gt;
: Please start talking to the dev communities you are interested in ''now''.&lt;br /&gt;
* March 14:  Student applications open.&lt;br /&gt;
: The earlier you start the more probable it is that you will be accepted!&lt;br /&gt;
: ''There is two way feedback during the application process which really helps you improve and clarify your application before the final deadline. The better your involvement with your potential mentors during this period, the better your chances of being selected.''&lt;br /&gt;
* March 25:  Student application deadline.&lt;br /&gt;
* April 22: '''Accepted student proposals are announced and Community Bonding Period begins.'''&lt;br /&gt;
* May 23: '''Coding begins!'''&lt;br /&gt;
: (''you may unofficially start a week or two earlier if you know you'll have to take a week or two off during The Summer or you'll be sitting finals in the first week(s) of the program. This must be reflected in your application timeline'')&lt;br /&gt;
* June 20 - 27: Mid-term evaluation &lt;br /&gt;
* August 15-23: '''Pencils down!'''&lt;br /&gt;
* August 23 -29: Final evaluations&lt;br /&gt;
* August 30: Final results announced&lt;br /&gt;
&lt;br /&gt;
[Back to [[Google Summer of Code 2016]] @ OSGeo]&lt;br /&gt;
[[Category: Google Summer of Code]]&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2016_Ideas&amp;diff=96627</id>
		<title>Google Summer of Code 2016 Ideas</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2016_Ideas&amp;diff=96627"/>
		<updated>2016-02-16T13:02:18Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: /* The ideas pages */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;center&amp;gt;&lt;br /&gt;
[[Image:GSoC2016Logo.jpg|500px|link=https://summerofcode.withgoogle.com/]] &amp;lt;font size=&amp;quot;+3&amp;quot;&amp;gt; @ &amp;lt;/font&amp;gt; &lt;br /&gt;
[[Image:OSGeo_300_127_pixel.png|200px|link=http://www.osgeo.org]]&lt;br /&gt;
&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
-----&lt;br /&gt;
* Back to the main OSGeo [[Google Summer of Code 2016]] wiki page.&lt;br /&gt;
&lt;br /&gt;
* 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]], [[Google Summer of Code 2013 Ideas|2013]] , [[Google Summer of Code 2014 Ideas|2014]] and [[Google Summer of Code 2014 Ideas|2015]].&lt;br /&gt;
-----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== OSGeo Google Summer of Code 2016 ==&lt;br /&gt;
&lt;br /&gt;
The [http://www.osgeo.org Open Source Geospatial Foundation] would like to extend a welcome to all SoC students. On this page you will find links to a host of ideas organized by project. You will find ideas ranging from the depths of computer science graph theory to the heights of visualization. One thing all these ideas have in common is lots and lots of spatial data.&lt;br /&gt;
&lt;br /&gt;
These ideas are '''*only*''' to motivate you, and serve as example of the kind of hills we want to charge up. Your own ideas are more than welcomed - they are encouraged. We view you as the next wave of open source leaders; show us what you've got.&lt;br /&gt;
&lt;br /&gt;
* '''Students: check out the [[Google Summer of Code Recommendations for Students]] page. If you need more information on how to apply you can contact all the mentors via the OSGeo-SoC mailing list''' ([[#How to get in contact via mailing lists|see below]])&lt;br /&gt;
&lt;br /&gt;
* There is a [https://developers.google.com/open-source/soc/resources/flyers Google SoC flyer] to look at and post in appropriate places.&lt;br /&gt;
&lt;br /&gt;
* Ok, [[OSGeo]] is involved in working with maps and things, but what kind of projects does it really do? Have a look at the [http://planet.osgeo.org/ live blog feed] to see what people are working on right now.&lt;br /&gt;
&lt;br /&gt;
* Mentors, there's an additional link providing some tips and specifying your responsibilities on the main OSGeo [[Google_Summer_of_Code_2016_Administrative]] wiki page.&lt;br /&gt;
&lt;br /&gt;
== The ideas pages ==&lt;br /&gt;
'''''[Check back often, it's a work in progress]'''''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Each participating project's list of ideas is on the respective projects' wikis, with a short description of the project and what type of students would be interested in it:&lt;br /&gt;
&lt;br /&gt;
=== OSGeo Foundation member projects ===&lt;br /&gt;
&lt;br /&gt;
* ''More coming soon: Get started talking to your favorite project's development team today!''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:logo-grass.png|60px|right]]&lt;br /&gt;
* [https://trac.osgeo.org/grass/wiki/GSoC/2015 '''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!--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:logo-qgis.png|60px|right]]&lt;br /&gt;
* [http://hub.qgis.org/wiki/quantum-gis/Google_Summer_of_Code_2015 '''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.--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:logo-gdal.png|60px|right]]&lt;br /&gt;
* [http://trac.osgeo.org/gdal/wiki/SummerOfCode '''GDAL''' Ideas]: [http://www.gdal.org GDAL] is a C++ library for reading and writing geospatial data raster and vector formats.--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
* [http://trac.osgeo.org/osgeo4w/wiki/Reports '''OSGeo4W''']: -  OSGeo4W is a binary distribution of a broad set of open source geospatial software for Win32 environments (Windows 7, XP, etc).&lt;br /&gt;
[[Image:Logo-osgeo4w-mini.png|60px|right]]&lt;br /&gt;
:* ''Idea'': We need to extend support to x64 based platforms to handle larger datasets and circumvent memory restrictions. This is a distribution and packaging project which will involve most/all of OSGeo member projects. (''ed. note: keep in mind that to fulfill GSoC requirements each project must have a majority coding component, so lots of scripting, testing, and Makefiles!'')--&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
[[Image:logo-gvSIG.png|60px|right]]&lt;br /&gt;
* [[GvSIG_GSoC_2016_Ideas|'''gvSIG''' Ideas]]: gvSIG is a free GIS project for [http://www.gvsig.com/en/web/guest/products/gvsig-desktop Desktop]. The gvSIG project looks for students with Java or Python skills that want to develop new ideas on this software. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:logo-opticks.png|right]]&lt;br /&gt;
* [http://opticks.org/confluence/display/opticksDev/Google+Summer+of+Code '''Opticks''' Ideas]: [http://opticks.org/ Opticks] is an extensible [http://en.wikipedia.org/wiki/Remote_sensing remote sensing] and imagery analysis desktop application. It provides a framework to process remote sensing data such as [http://en.wikipedia.org/wiki/Hyperspectral_imaging Hyperspectral] (HSI), [http://en.wikipedia.org/wiki/Multi-spectral_image Multispectral] (MSI), and [http://en.wikipedia.org/wiki/Synthetic_aperture_radar Synthetic aperture radar] (SAR) imagery and video. The application is written in C++ and licensed under LGPL v2.1. Extensions are written using C++ or Python. You can review the [http://opticks.org/confluence/display/opticksExt/All+Opticks+Extensions available extensions] and [http://opticks.org/confluence/display/opticks/Feature+Tour+-+Your+Data feature tour] to get a better idea of what Opticks can do.--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- &lt;br /&gt;
[[Image:Osgeolive_60px.png|right]]&lt;br /&gt;
* [http://wiki.osgeo.org/wiki/Live_GIS_GSoC_2015 '''OSGeo-Live''' Ideas]: [http://live.osgeo.org OSGeo-Live] packages over 50 of the best geospatial open source projects, preconfigured with data, quickstarts and project overviews. We have packaging and automated build projects. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- &lt;br /&gt;
[[Image:logo-postgis.png|60px|right]] &lt;br /&gt;
* [http://trac.osgeo.org/postgis/wiki/GoogleSummerCode '''PostGIS''' Ideas]: [http://postgis.net PostGIS] spatially enables the popular PostgreSQL object-relational database, allowing it to be used as a back-end database for geographic information systems (GIS) and web-mapping applications.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-ossim.png|90px|right]]&lt;br /&gt;
* [https://trac.osgeo.org/ossim/wiki/GSoC_2015 '''OSSIM''' SoC Ideas]: [http://trac.osgeo.org/ossim/wiki OSSIM] Open Source Software Image Map (OSSIM) is a high performance engine for remote sensing, image processing, geographical information systems and photogrammetry. The software has been under active development since 1996 and is deployed across a number of private, federal and civilian agencies. It is written in C++.--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:Logo_OTB.png|60px|right]]&lt;br /&gt;
* [http://wiki.orfeo-toolbox.org/index.php/Proposals_for_GSoC_2015 '''OTB''' SoC Ideas]: [http://www.orfeo-toolbox.org ORFEO ToolBox] (OTB) is an open source library for remote sensing image processing.Targeted algorithms for high resolution optical images (Pleiades, SPOT, QuickBird, WorldView, Landsat, Ikonos), hyperspectral sensors (Hyperion) or SAR (TerraSarX, ERS, Palsar) are available. The software has been under active development since 2006 and is written in C++ and it includes also side projects also open source with GUI like Monteverdi. OTB has recently started the incubation process into OSGeo.--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:Mapserver.png|100px|right]]&lt;br /&gt;
* [http://wiki.osgeo.org/wiki/MapServer_2015_SOC_Ideas '''Mapserver''' SoC Ideas]: MapServer is a Web Mapping Engine; an Open Source platform for publishing spatial data and interactive mapping applications to the web.--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:Logo-istSOS.png|60px|right]]&lt;br /&gt;
* [http://sourceforge.net/p/istsos/wiki/GSoC%20ideas%202015/ '''istSOS''' Ideas]: [http://sourceforge.net/projects/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.--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-geos.png|60px|right]]&lt;br /&gt;
* [http://trac.osgeo.org/geos/wiki/GSoC '''GEOS''' Ideas]: GEOS (Geometry Engine - Open Source) is a C++ port of the JTS Topology Suite (JTS). It includes the OpenGIS Simple Features for SQL spatial predicate functions and spatial operators, as well as specific JTS enhanced topology functions.&lt;br /&gt;
--&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:logo-geoserver-crop.png|50px|right]]&lt;br /&gt;
* [https://github.com/geoserver/geoserver/wiki/GSOC-Ideas GSOC Ideas]: [http://live.osgeo.org/en/overview/geoserver_overview.html '''GeoServer'''] is a web server that allows you to serve maps and data from a variety of formats to standard clients such as web browsers and desktop GIS applications.  GeoServer works with the Open Geospatial Consortium (OGC) standards Web Feature Service (WFS), Web Coverage Service (WCS), Web Processing Service (WPS) and Web Map Service (WMS) standards.&lt;br /&gt;
:* The GeoServer team asks applicants to introduce themselves on the geoserver-devel list ( Communicating in public is a key success factor to open source development )--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:Geotools-logo.png|50px|right]]&lt;br /&gt;
* [http://docs.codehaus.org/display/GEOTOOLS/Google+Summer+of+Code ''GSOC'']:  [http://live.osgeo.org/en/overview/geotools_overview.html '''GeoTools'''] GeoTools is an open source Java library for working with geospatial data, including both data access, data structures, processing and a powerful rendering engine. GeoTools is a modular library used in a wide range of web service, command line tools and desktop applications.--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:ZOO-Project-mini.png|right]]&lt;br /&gt;
* [http://zoo-project.org/trac/wiki/ZOO_SoC_Idea_2015 '''ZOO-Project''' Soc Ideas]: ZOO-Project is a WPS (Web Processing Service) open source project released under  MIT/X-11 style license. It provides an OGC WPS compliant developer-friendly framework to create and chain WPS Web services. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:ZOO-Project-mini.png|right]]&lt;br /&gt;
* [http://www.zoo-project.org/trac/wiki/ZOO_SoC_Ideas '''ZOO-Project''' Ideas]: [http://www.zoo-project.org ZOO-Project] is a WPS open source project released under a MIT/X-11 style license. We are seeking a developper to handle migration from SpiderMonky to Google v8 JavaScript runtime environment, upgrade the ZOO-API, build a demo package and develop new services dedicated to raster gesture.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
We expect ideas also from [http://live.osgeo.org/en/overview/mapbender_overview.html MapBender], [http://live.osgeo.org/en/overview/geomoose_overview.html GeoMOOSE], [http://mapserver.org/ MapServer], ...&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:Osgeo-live.png|230px|right]]&lt;br /&gt;
* [http://wiki.osgeo.org/wiki/Live_GIS_GSoC_2015 '''Osgeo-Live''' SoC Ideas]: [http://live.osgeo.org/en/index.html OSGeo-Live] is a self-contained bootable DVD, USB thumb drive or Virtual Machine based on Lubuntu, that allows you to try a wide variety of open source geospatial software without installing anything. It is composed entirely of free software, allowing it to be freely distributed, duplicated and passed around. It provides pre-configured applications for a range of geospatial use cases, including storage, publishing, viewing, analysis and manipulation of data. It also contains sample datasets and documentation.--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Guest projects ===&lt;br /&gt;
&lt;br /&gt;
Like-minded geospatial projects to take part under OSGeo umbrella. If you wish your software project to be listed here, please contact [[User:Madi|Madi]] or Anne.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:Pgrouting-logo.png|60px|right]]&lt;br /&gt;
* [https://github.com/pgRouting/pgrouting/wiki/GSoC-Ideas '''pgRouting''' Ideas]: [http://pgrouting.org pgRouting] extends the PostGIS / PostgreSQL geospatial database to provide geospatial routing functionality and more.--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:Pywps-logo.png|60px|right]]&lt;br /&gt;
* [https://github.com/jachym/pywps-4/wiki/GSOC-2015-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. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:logo-uDig.png|60px|right]]&lt;br /&gt;
* [https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-Ideas-2015 '''JGrasstools''' and '''uDig''' Spatial Toolbox SoC Ideas]: The JGrasstools project is a geospatial modules library dedicated to hydrology and geomorphology. It is the base of the modules for uDig's Spatial Toolbox.--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:otp-logo.png|80px|right]]&lt;br /&gt;
* [http://github.com/opentripplanner/OpenTripPlanner/wiki/2015-Google-Summer-of-Code-Ideas '''OpenTripPlanner''' Ideas]: [http://github.com/opentripplanner/OpenTripPlanner OpenTripPlanner] is an open source multi-modal trip planner. It depends on open data in open standard file formats (GTFS and OpenStreetMap), includes a REST API for journey planning, a map-based Javascript client, and an [http://github.com/CUTR-at-USF/OpenTripPlanner-for-Android/wiki Android App].--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- please contact us first&lt;br /&gt;
* [http://lsi.iiit.ac.in/redmine/projects/lsiviewer/wiki/GSoC_2015 '''LSIViewer''' Ideas]: [http://lsi.iiit.ac.in/redmine/projects/lsiviewer/wiki/Main/ LSIViewer] Libre Spatial Information Viewer (LSIViewer) is a web based geospatial data viewer which allows you to view your data, style it, export to SVG/PNG/JPEG formats and can be for used in reports and presentation. It uses Wt, a C++ web toolkit which comes with its own http server and has good support for embedded platforms. The initial version had support for only shapefiles but around 13 vector formats, OSM layer, 3D view has been experimental on the lab's internal repository.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Logo-cartaro.png|60px|right]]&lt;br /&gt;
* [https://groups.drupal.org/node/407408 '''Cartaro''' Ideas]: [http://cartaro.org Cartaro] provides geospatial functionality and web services within the Drupal Content Management System (CMS). It is builds upon robust Open Source components: the PostGIS database, GeoServer and GeoWebCache web services, OpenLayers maps in the browser, all managed from within the powerful Drupal CMS.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Geonode logo.png|60px|right]]&lt;br /&gt;
* [https://github.com/GeoNode/geonode/wiki/Google-Summer-of-Code-Ideas-2015 '''GeoNode''' Ideas]: [http://geonode.org/ GeoNode] is an Open Source Geospatial Content Management System: a web-based application and platform for developing Geospatial Information Systems (GIS) and for deploying spatial data infrastructures (SDI). It is designed to be easily extended and modified, and can be integrated into existing platforms. Written with the Python Django web application, it is based on other great Open Source components such as PostGIS, GeoServer, OpenLayers and GeoExplorer.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:neo4j-spatial_64.png|right]]&lt;br /&gt;
* [https://github.com/neo4j/GSoC/wiki '''Neo4j Spatial''' Ideas]: [https://github.com/neo4j/spatial Neo4j Spatial] is an Open Source library extending the popular [http://neo4j.org Neo4j Graph Database] with a number of features for GIS enabling your data model. It embeds and relies on JTS and GeoTools, and provides the ability to store your domain model in many internal formats, and has utilities for import and export of Shapefiles and OpenStreetMap data. We've received contributions from GSoC projects in 2010, 2011 and 2012.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Logo-cartoDB.png|70px|right]]&lt;br /&gt;
* [https://github.com/CartoDB/cartodb/wiki/GoogleSummerCode '''CartoDB Ideas''']: [http://cartodb.com/develop CartoDB] is a cloud based mapping, analysis and visualization engine that lets users build spatial applications for both mobile and the web. Students will need to be able to use PHP and PostgreSQL.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
* '''FIXME''': move to a member project's idea page:&lt;br /&gt;
: ''[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.''&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Logo-mapnik.png|100px|right]]&lt;br /&gt;
* [https://github.com/mapnik/mapnik/wiki/GSOC-Ideas '''Mapnik''' Ideas]: [http://mapnik.org/ Mapnik] is a Free Toolkit for developing mapping applications. It\u2019s 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.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== See also ===&lt;br /&gt;
&lt;br /&gt;
Other like minded projects do not participate to GSoC under OSGeo umbrella, but with their own organization. You may want to visit also their page:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
* [https://wiki.52north.org/bin/view/Projects/GSoC2015ProjectIdeas '''52°North''' Ideas]--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- [[Image:Logo-osm6.png|60px|right]] &lt;br /&gt;
* [http://wiki.openstreetmap.org/wiki/Google_Summer_of_Code/2015/Project_Ideas '''OpenStreetMap''' Ideas]--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[http://osm.org/ OSM] is a project aimed squarely at creating and providing free geographic data such as street maps to anyone who wants them. The project was started because most maps you think of as free actually have legal or technical restrictions on their use, holding back people from using them in creative, productive or unexpected ways.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Don't see in the list the project you're interested in? ===&lt;br /&gt;
&lt;br /&gt;
Contact them in their developers mailing list! Feel free to propose your own idea and get feedback!&lt;br /&gt;
&lt;br /&gt;
== I want to apply as a student ==&lt;br /&gt;
&lt;br /&gt;
Before applying as a student, check out the [[Google Summer of Code Recommendations for Students]] page.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Which project do I choose? ===&lt;br /&gt;
&lt;br /&gt;
Most of the software projects are available pre-built on our Live demo { DVD | USB stick | VirtualMachine } with project overviews and short tutorials where you can try everything out.&lt;br /&gt;
: View the documents and download the ISO from http://live.osgeo.org&lt;br /&gt;
[[File:Osgeolive wordle.png|400px|center]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Important dates ===&lt;br /&gt;
&lt;br /&gt;
* [https://developers.google.com/open-source/gsoc/timeline '''The official timeline''']&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- {{done}} --&amp;gt;&lt;br /&gt;
* Feb 29: Google announces accepted organizations.&lt;br /&gt;
: Please start talking to the dev communities you are interested in ''now''.&lt;br /&gt;
* March 14:  Student applications open.&lt;br /&gt;
: The earlier you start the more probable it is that you will be accepted!&lt;br /&gt;
: ''There is two way feedback during the application process which really helps you improve and clarify your application before the final deadline. The better your involvement with your potential mentors during this period, the better your chances of being selected.''&lt;br /&gt;
* March 25:  Student application deadline.&lt;br /&gt;
* April 22: '''Accepted student proposals are announced and Community Bonding Period begins.'''&lt;br /&gt;
* May 23: '''Coding begins!'''&lt;br /&gt;
: (''you may unofficially start a week or two earlier if you know you'll have to take a week or two off during The Summer or you'll be sitting finals in the first week(s) of the program. This must be reflected in your application timeline'')&lt;br /&gt;
* June 20 - 27: Mid-term evaluation &lt;br /&gt;
* August 15-23: '''Pencils down!'''&lt;br /&gt;
* August 23 -29: Final evaluations&lt;br /&gt;
* August 30: Final results announced&lt;br /&gt;
&lt;br /&gt;
[Back to [[Google Summer of Code 2016]] @ OSGeo]&lt;br /&gt;
[[Category: Google Summer of Code]]&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2016_Ideas&amp;diff=96626</id>
		<title>Google Summer of Code 2016 Ideas</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Google_Summer_of_Code_2016_Ideas&amp;diff=96626"/>
		<updated>2016-02-16T13:01:22Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;center&amp;gt;&lt;br /&gt;
[[Image:GSoC2016Logo.jpg|500px|link=https://summerofcode.withgoogle.com/]] &amp;lt;font size=&amp;quot;+3&amp;quot;&amp;gt; @ &amp;lt;/font&amp;gt; &lt;br /&gt;
[[Image:OSGeo_300_127_pixel.png|200px|link=http://www.osgeo.org]]&lt;br /&gt;
&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
-----&lt;br /&gt;
* Back to the main OSGeo [[Google Summer of Code 2016]] wiki page.&lt;br /&gt;
&lt;br /&gt;
* 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]], [[Google Summer of Code 2013 Ideas|2013]] , [[Google Summer of Code 2014 Ideas|2014]] and [[Google Summer of Code 2014 Ideas|2015]].&lt;br /&gt;
-----&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== OSGeo Google Summer of Code 2016 ==&lt;br /&gt;
&lt;br /&gt;
The [http://www.osgeo.org Open Source Geospatial Foundation] would like to extend a welcome to all SoC students. On this page you will find links to a host of ideas organized by project. You will find ideas ranging from the depths of computer science graph theory to the heights of visualization. One thing all these ideas have in common is lots and lots of spatial data.&lt;br /&gt;
&lt;br /&gt;
These ideas are '''*only*''' to motivate you, and serve as example of the kind of hills we want to charge up. Your own ideas are more than welcomed - they are encouraged. We view you as the next wave of open source leaders; show us what you've got.&lt;br /&gt;
&lt;br /&gt;
* '''Students: check out the [[Google Summer of Code Recommendations for Students]] page. If you need more information on how to apply you can contact all the mentors via the OSGeo-SoC mailing list''' ([[#How to get in contact via mailing lists|see below]])&lt;br /&gt;
&lt;br /&gt;
* There is a [https://developers.google.com/open-source/soc/resources/flyers Google SoC flyer] to look at and post in appropriate places.&lt;br /&gt;
&lt;br /&gt;
* Ok, [[OSGeo]] is involved in working with maps and things, but what kind of projects does it really do? Have a look at the [http://planet.osgeo.org/ live blog feed] to see what people are working on right now.&lt;br /&gt;
&lt;br /&gt;
* Mentors, there's an additional link providing some tips and specifying your responsibilities on the main OSGeo [[Google_Summer_of_Code_2016_Administrative]] wiki page.&lt;br /&gt;
&lt;br /&gt;
== The ideas pages ==&lt;br /&gt;
'''''[Check back often, it's a work in progress]'''''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Each participating project's list of ideas is on the respective projects' wikis, with a short description of the project and what type of students would be interested in it:&lt;br /&gt;
&lt;br /&gt;
=== OSGeo Foundation member projects ===&lt;br /&gt;
&lt;br /&gt;
* ''More coming soon: Get started talking to your favorite project's development team today!''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:logo-grass.png|60px|right]]&lt;br /&gt;
* [https://trac.osgeo.org/grass/wiki/GSoC/2015 '''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!--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:logo-qgis.png|60px|right]]&lt;br /&gt;
* [http://hub.qgis.org/wiki/quantum-gis/Google_Summer_of_Code_2015 '''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.--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:logo-gdal.png|60px|right]]&lt;br /&gt;
* [http://trac.osgeo.org/gdal/wiki/SummerOfCode '''GDAL''' Ideas]: [http://www.gdal.org GDAL] is a C++ library for reading and writing geospatial data raster and vector formats.--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
* [http://trac.osgeo.org/osgeo4w/wiki/Reports '''OSGeo4W''']: -  OSGeo4W is a binary distribution of a broad set of open source geospatial software for Win32 environments (Windows 7, XP, etc).&lt;br /&gt;
[[Image:Logo-osgeo4w-mini.png|60px|right]]&lt;br /&gt;
:* ''Idea'': We need to extend support to x64 based platforms to handle larger datasets and circumvent memory restrictions. This is a distribution and packaging project which will involve most/all of OSGeo member projects. (''ed. note: keep in mind that to fulfill GSoC requirements each project must have a majority coding component, so lots of scripting, testing, and Makefiles!'')--&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
[[Image:logo-gvSIG.png|60px|right]]&lt;br /&gt;
* [[GvSIG_GSoC_2015_Ideas|'''gvSIG''' Ideas]]: gvSIG is a free GIS project for [http://www.gvsig.com/en/web/guest/products/gvsig-desktop Desktop]. The gvSIG project looks for students with Java or Python skills that want to develop new ideas on this software. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:logo-opticks.png|right]]&lt;br /&gt;
* [http://opticks.org/confluence/display/opticksDev/Google+Summer+of+Code '''Opticks''' Ideas]: [http://opticks.org/ Opticks] is an extensible [http://en.wikipedia.org/wiki/Remote_sensing remote sensing] and imagery analysis desktop application. It provides a framework to process remote sensing data such as [http://en.wikipedia.org/wiki/Hyperspectral_imaging Hyperspectral] (HSI), [http://en.wikipedia.org/wiki/Multi-spectral_image Multispectral] (MSI), and [http://en.wikipedia.org/wiki/Synthetic_aperture_radar Synthetic aperture radar] (SAR) imagery and video. The application is written in C++ and licensed under LGPL v2.1. Extensions are written using C++ or Python. You can review the [http://opticks.org/confluence/display/opticksExt/All+Opticks+Extensions available extensions] and [http://opticks.org/confluence/display/opticks/Feature+Tour+-+Your+Data feature tour] to get a better idea of what Opticks can do.--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- &lt;br /&gt;
[[Image:Osgeolive_60px.png|right]]&lt;br /&gt;
* [http://wiki.osgeo.org/wiki/Live_GIS_GSoC_2015 '''OSGeo-Live''' Ideas]: [http://live.osgeo.org OSGeo-Live] packages over 50 of the best geospatial open source projects, preconfigured with data, quickstarts and project overviews. We have packaging and automated build projects. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- &lt;br /&gt;
[[Image:logo-postgis.png|60px|right]] &lt;br /&gt;
* [http://trac.osgeo.org/postgis/wiki/GoogleSummerCode '''PostGIS''' Ideas]: [http://postgis.net PostGIS] spatially enables the popular PostgreSQL object-relational database, allowing it to be used as a back-end database for geographic information systems (GIS) and web-mapping applications.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-ossim.png|90px|right]]&lt;br /&gt;
* [https://trac.osgeo.org/ossim/wiki/GSoC_2015 '''OSSIM''' SoC Ideas]: [http://trac.osgeo.org/ossim/wiki OSSIM] Open Source Software Image Map (OSSIM) is a high performance engine for remote sensing, image processing, geographical information systems and photogrammetry. The software has been under active development since 1996 and is deployed across a number of private, federal and civilian agencies. It is written in C++.--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:Logo_OTB.png|60px|right]]&lt;br /&gt;
* [http://wiki.orfeo-toolbox.org/index.php/Proposals_for_GSoC_2015 '''OTB''' SoC Ideas]: [http://www.orfeo-toolbox.org ORFEO ToolBox] (OTB) is an open source library for remote sensing image processing.Targeted algorithms for high resolution optical images (Pleiades, SPOT, QuickBird, WorldView, Landsat, Ikonos), hyperspectral sensors (Hyperion) or SAR (TerraSarX, ERS, Palsar) are available. The software has been under active development since 2006 and is written in C++ and it includes also side projects also open source with GUI like Monteverdi. OTB has recently started the incubation process into OSGeo.--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:Mapserver.png|100px|right]]&lt;br /&gt;
* [http://wiki.osgeo.org/wiki/MapServer_2015_SOC_Ideas '''Mapserver''' SoC Ideas]: MapServer is a Web Mapping Engine; an Open Source platform for publishing spatial data and interactive mapping applications to the web.--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:Logo-istSOS.png|60px|right]]&lt;br /&gt;
* [http://sourceforge.net/p/istsos/wiki/GSoC%20ideas%202015/ '''istSOS''' Ideas]: [http://sourceforge.net/projects/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.--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:logo-geos.png|60px|right]]&lt;br /&gt;
* [http://trac.osgeo.org/geos/wiki/GSoC '''GEOS''' Ideas]: GEOS (Geometry Engine - Open Source) is a C++ port of the JTS Topology Suite (JTS). It includes the OpenGIS Simple Features for SQL spatial predicate functions and spatial operators, as well as specific JTS enhanced topology functions.&lt;br /&gt;
--&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:logo-geoserver-crop.png|50px|right]]&lt;br /&gt;
* [https://github.com/geoserver/geoserver/wiki/GSOC-Ideas GSOC Ideas]: [http://live.osgeo.org/en/overview/geoserver_overview.html '''GeoServer'''] is a web server that allows you to serve maps and data from a variety of formats to standard clients such as web browsers and desktop GIS applications.  GeoServer works with the Open Geospatial Consortium (OGC) standards Web Feature Service (WFS), Web Coverage Service (WCS), Web Processing Service (WPS) and Web Map Service (WMS) standards.&lt;br /&gt;
:* The GeoServer team asks applicants to introduce themselves on the geoserver-devel list ( Communicating in public is a key success factor to open source development )--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:Geotools-logo.png|50px|right]]&lt;br /&gt;
* [http://docs.codehaus.org/display/GEOTOOLS/Google+Summer+of+Code ''GSOC'']:  [http://live.osgeo.org/en/overview/geotools_overview.html '''GeoTools'''] GeoTools is an open source Java library for working with geospatial data, including both data access, data structures, processing and a powerful rendering engine. GeoTools is a modular library used in a wide range of web service, command line tools and desktop applications.--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:ZOO-Project-mini.png|right]]&lt;br /&gt;
* [http://zoo-project.org/trac/wiki/ZOO_SoC_Idea_2015 '''ZOO-Project''' Soc Ideas]: ZOO-Project is a WPS (Web Processing Service) open source project released under  MIT/X-11 style license. It provides an OGC WPS compliant developer-friendly framework to create and chain WPS Web services. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:ZOO-Project-mini.png|right]]&lt;br /&gt;
* [http://www.zoo-project.org/trac/wiki/ZOO_SoC_Ideas '''ZOO-Project''' Ideas]: [http://www.zoo-project.org ZOO-Project] is a WPS open source project released under a MIT/X-11 style license. We are seeking a developper to handle migration from SpiderMonky to Google v8 JavaScript runtime environment, upgrade the ZOO-API, build a demo package and develop new services dedicated to raster gesture.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
We expect ideas also from [http://live.osgeo.org/en/overview/mapbender_overview.html MapBender], [http://live.osgeo.org/en/overview/geomoose_overview.html GeoMOOSE], [http://mapserver.org/ MapServer], ...&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:Osgeo-live.png|230px|right]]&lt;br /&gt;
* [http://wiki.osgeo.org/wiki/Live_GIS_GSoC_2015 '''Osgeo-Live''' SoC Ideas]: [http://live.osgeo.org/en/index.html OSGeo-Live] is a self-contained bootable DVD, USB thumb drive or Virtual Machine based on Lubuntu, that allows you to try a wide variety of open source geospatial software without installing anything. It is composed entirely of free software, allowing it to be freely distributed, duplicated and passed around. It provides pre-configured applications for a range of geospatial use cases, including storage, publishing, viewing, analysis and manipulation of data. It also contains sample datasets and documentation.--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Guest projects ===&lt;br /&gt;
&lt;br /&gt;
Like-minded geospatial projects to take part under OSGeo umbrella. If you wish your software project to be listed here, please contact [[User:Madi|Madi]] or Anne.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:Pgrouting-logo.png|60px|right]]&lt;br /&gt;
* [https://github.com/pgRouting/pgrouting/wiki/GSoC-Ideas '''pgRouting''' Ideas]: [http://pgrouting.org pgRouting] extends the PostGIS / PostgreSQL geospatial database to provide geospatial routing functionality and more.--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:Pywps-logo.png|60px|right]]&lt;br /&gt;
* [https://github.com/jachym/pywps-4/wiki/GSOC-2015-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. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:logo-uDig.png|60px|right]]&lt;br /&gt;
* [https://github.com/moovida/jgrasstools/wiki/Google-Summer-of-Code-Ideas-2015 '''JGrasstools''' and '''uDig''' Spatial Toolbox SoC Ideas]: The JGrasstools project is a geospatial modules library dedicated to hydrology and geomorphology. It is the base of the modules for uDig's Spatial Toolbox.--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Image:otp-logo.png|80px|right]]&lt;br /&gt;
* [http://github.com/opentripplanner/OpenTripPlanner/wiki/2015-Google-Summer-of-Code-Ideas '''OpenTripPlanner''' Ideas]: [http://github.com/opentripplanner/OpenTripPlanner OpenTripPlanner] is an open source multi-modal trip planner. It depends on open data in open standard file formats (GTFS and OpenStreetMap), includes a REST API for journey planning, a map-based Javascript client, and an [http://github.com/CUTR-at-USF/OpenTripPlanner-for-Android/wiki Android App].--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- please contact us first&lt;br /&gt;
* [http://lsi.iiit.ac.in/redmine/projects/lsiviewer/wiki/GSoC_2015 '''LSIViewer''' Ideas]: [http://lsi.iiit.ac.in/redmine/projects/lsiviewer/wiki/Main/ LSIViewer] Libre Spatial Information Viewer (LSIViewer) is a web based geospatial data viewer which allows you to view your data, style it, export to SVG/PNG/JPEG formats and can be for used in reports and presentation. It uses Wt, a C++ web toolkit which comes with its own http server and has good support for embedded platforms. The initial version had support for only shapefiles but around 13 vector formats, OSM layer, 3D view has been experimental on the lab's internal repository.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Logo-cartaro.png|60px|right]]&lt;br /&gt;
* [https://groups.drupal.org/node/407408 '''Cartaro''' Ideas]: [http://cartaro.org Cartaro] provides geospatial functionality and web services within the Drupal Content Management System (CMS). It is builds upon robust Open Source components: the PostGIS database, GeoServer and GeoWebCache web services, OpenLayers maps in the browser, all managed from within the powerful Drupal CMS.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Geonode logo.png|60px|right]]&lt;br /&gt;
* [https://github.com/GeoNode/geonode/wiki/Google-Summer-of-Code-Ideas-2015 '''GeoNode''' Ideas]: [http://geonode.org/ GeoNode] is an Open Source Geospatial Content Management System: a web-based application and platform for developing Geospatial Information Systems (GIS) and for deploying spatial data infrastructures (SDI). It is designed to be easily extended and modified, and can be integrated into existing platforms. Written with the Python Django web application, it is based on other great Open Source components such as PostGIS, GeoServer, OpenLayers and GeoExplorer.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:neo4j-spatial_64.png|right]]&lt;br /&gt;
* [https://github.com/neo4j/GSoC/wiki '''Neo4j Spatial''' Ideas]: [https://github.com/neo4j/spatial Neo4j Spatial] is an Open Source library extending the popular [http://neo4j.org Neo4j Graph Database] with a number of features for GIS enabling your data model. It embeds and relies on JTS and GeoTools, and provides the ability to store your domain model in many internal formats, and has utilities for import and export of Shapefiles and OpenStreetMap data. We've received contributions from GSoC projects in 2010, 2011 and 2012.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Logo-cartoDB.png|70px|right]]&lt;br /&gt;
* [https://github.com/CartoDB/cartodb/wiki/GoogleSummerCode '''CartoDB Ideas''']: [http://cartodb.com/develop CartoDB] is a cloud based mapping, analysis and visualization engine that lets users build spatial applications for both mobile and the web. Students will need to be able to use PHP and PostgreSQL.--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
* '''FIXME''': move to a member project's idea page:&lt;br /&gt;
: ''[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.''&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[[Image:Logo-mapnik.png|100px|right]]&lt;br /&gt;
* [https://github.com/mapnik/mapnik/wiki/GSOC-Ideas '''Mapnik''' Ideas]: [http://mapnik.org/ Mapnik] is a Free Toolkit for developing mapping applications. It\u2019s 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.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== See also ===&lt;br /&gt;
&lt;br /&gt;
Other like minded projects do not participate to GSoC under OSGeo umbrella, but with their own organization. You may want to visit also their page:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
* [https://wiki.52north.org/bin/view/Projects/GSoC2015ProjectIdeas '''52°North''' Ideas]--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- [[Image:Logo-osm6.png|60px|right]] &lt;br /&gt;
* [http://wiki.openstreetmap.org/wiki/Google_Summer_of_Code/2015/Project_Ideas '''OpenStreetMap''' Ideas]--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
[http://osm.org/ OSM] is a project aimed squarely at creating and providing free geographic data such as street maps to anyone who wants them. The project was started because most maps you think of as free actually have legal or technical restrictions on their use, holding back people from using them in creative, productive or unexpected ways.&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Don't see in the list the project you're interested in? ===&lt;br /&gt;
&lt;br /&gt;
Contact them in their developers mailing list! Feel free to propose your own idea and get feedback!&lt;br /&gt;
&lt;br /&gt;
== I want to apply as a student ==&lt;br /&gt;
&lt;br /&gt;
Before applying as a student, check out the [[Google Summer of Code Recommendations for Students]] page.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Which project do I choose? ===&lt;br /&gt;
&lt;br /&gt;
Most of the software projects are available pre-built on our Live demo { DVD | USB stick | VirtualMachine } with project overviews and short tutorials where you can try everything out.&lt;br /&gt;
: View the documents and download the ISO from http://live.osgeo.org&lt;br /&gt;
[[File:Osgeolive wordle.png|400px|center]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Important dates ===&lt;br /&gt;
&lt;br /&gt;
* [https://developers.google.com/open-source/gsoc/timeline '''The official timeline''']&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- {{done}} --&amp;gt;&lt;br /&gt;
* Feb 29: Google announces accepted organizations.&lt;br /&gt;
: Please start talking to the dev communities you are interested in ''now''.&lt;br /&gt;
* March 14:  Student applications open.&lt;br /&gt;
: The earlier you start the more probable it is that you will be accepted!&lt;br /&gt;
: ''There is two way feedback during the application process which really helps you improve and clarify your application before the final deadline. The better your involvement with your potential mentors during this period, the better your chances of being selected.''&lt;br /&gt;
* March 25:  Student application deadline.&lt;br /&gt;
* April 22: '''Accepted student proposals are announced and Community Bonding Period begins.'''&lt;br /&gt;
* May 23: '''Coding begins!'''&lt;br /&gt;
: (''you may unofficially start a week or two earlier if you know you'll have to take a week or two off during The Summer or you'll be sitting finals in the first week(s) of the program. This must be reflected in your application timeline'')&lt;br /&gt;
* June 20 - 27: Mid-term evaluation &lt;br /&gt;
* August 15-23: '''Pencils down!'''&lt;br /&gt;
* August 23 -29: Final evaluations&lt;br /&gt;
* August 30: Final results announced&lt;br /&gt;
&lt;br /&gt;
[Back to [[Google Summer of Code 2016]] @ OSGeo]&lt;br /&gt;
[[Category: Google Summer of Code]]&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Board_Press_Release_gvSIG_Graduates_Incubation&amp;diff=88794</id>
		<title>Board Press Release gvSIG Graduates Incubation</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Board_Press_Release_gvSIG_Graduates_Incubation&amp;diff=88794"/>
		<updated>2015-11-23T09:02:33Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Subject ==&lt;br /&gt;
&lt;br /&gt;
gvSIG Graduates OSGeo Incubation&lt;br /&gt;
&lt;br /&gt;
== News Date ==&lt;br /&gt;
&lt;br /&gt;
22 Nov 2015&lt;br /&gt;
&lt;br /&gt;
== Details ==&lt;br /&gt;
&lt;br /&gt;
OSGeo is pleased to announce that the gvSIG project has graduated from incubation and is now a full fledged OSGeo project. Manuel Madrid, a long time member of the gvSIG Project Steering Committee (PSC), has been appointed as project officer.&lt;br /&gt;
&lt;br /&gt;
[[File:gvsig-logo.jpg||right|x|link=http://www.gvsig.com]]&lt;br /&gt;
[http://www.gvsig.com gvSIG] is an Open Source desktop application designed for capturing, storing, handling, analyzing and deploying any kind of referenced geographic information in order to solve complex management and planning problems. gvSIG is known for having a user-friendly interface, being able to access the most common formats, both vector and raster ones. It features a wide range of tools for working with geographic-like information (query tools, layout creation, geoprocessing, networks, etc.), which turns gvSIG into the ideal tool for users working in the land realm.&lt;br /&gt;
&lt;br /&gt;
Graduating  [http://www.osgeo.org/incubator incubation] includes fulfilling requirements for open community operation, a responsible project governance model, code provenance, and general good project operation. Graduation is the OSGeo seal of approval for a project and gives potential users and the community at large an added confidence in the viability and safety of the project.&lt;br /&gt;
&lt;br /&gt;
The project steering committee says, &amp;quot;The gvSIG team is thrilled to be recognized as a full OSGeo project. There have been strong ties between the two communities with common objectives to spread open source for geomatics, and develop a business model based on collaboration and shared knowledge. We are very happy to be included as part of OSGeo and a member of such an esteemed group of projects&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
OSGeo would also like to thank Dimitris Kotzinos, Jeroen Ticheler and Jorge Sanz for their assistance during this Incubation process.&lt;br /&gt;
&lt;br /&gt;
Congratulations to the gvSIG community!&lt;br /&gt;
&lt;br /&gt;
[[Category:Board]]&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=GvSIG_Incubation_Checklist&amp;diff=86957</id>
		<title>GvSIG Incubation Checklist</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=GvSIG_Incubation_Checklist&amp;diff=86957"/>
		<updated>2015-10-01T12:32:24Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Document Status =&lt;br /&gt;
&lt;br /&gt;
'''Version''': 2.0&lt;br /&gt;
&lt;br /&gt;
'''Last Updated''': October 2015.&lt;br /&gt;
&lt;br /&gt;
'''Status''': Draft&lt;br /&gt;
&lt;br /&gt;
= Purpose =&lt;br /&gt;
&lt;br /&gt;
The purpose of this checklist is to determine whether an Incubator Project produces quality products, remains true to its stated licence and is sustainable. Satisfying this checklist is a pre-requisite for graduation.&lt;br /&gt;
&lt;br /&gt;
A project should have institutionalized the processes in this list or provide justification why the process is not used.&lt;br /&gt;
&lt;br /&gt;
See also:&lt;br /&gt;
&lt;br /&gt;
* [http://www.osgeo.org/incubator/process/application.html Incubation Application Questionnaire]&lt;br /&gt;
* [http://www.osgeo.org/incubator/process/statustemplate.html Project Status Template]&lt;br /&gt;
&lt;br /&gt;
= Terms and Definitions =&lt;br /&gt;
&lt;br /&gt;
; Mentor : A member of the Incubation Committee chosen to assist a Project through the Incubation Process.&lt;br /&gt;
; Institutionalized Process : A documented process which which addresses a need and is actively in use. It typically takes months before a process becomes institutionalized. ''A more detailed definition of institutionalization is found in the [http://www.sei.cmu.edu/pub/documents/02.reports/pdf/02tr012.pdf Capability Maturity Model (CMMI)] - &amp;quot;Generic Goal 2: Institutionalize a Managed Process&amp;quot;''&lt;br /&gt;
; Open Source License : a license recognized by the [http://opensource.org Open Source Initiative]&lt;br /&gt;
&lt;br /&gt;
= Incubation Checklist =&lt;br /&gt;
&lt;br /&gt;
== Open ==&lt;br /&gt;
	 &lt;br /&gt;
The project has demonstrated that it has an open, active and healthy user and developer community:	&lt;br /&gt;
# Open: projects are expected to function in an open and public manner and include:&lt;br /&gt;
#* Open source license(s), '''yes: gvSIG is developed under GNU/GPL version 3 license'''&lt;br /&gt;
#* Open communication channels, '''yes: there are several users and developers mailing lists in different languages (http://www.gvsig.com/en/community/mailing-lists). There's also a mail address (info@gvsig.com), a phone number (0034-961110070) and a fax number (0034-901021995)'''&lt;br /&gt;
#* Open decision making process, '''yes: About gvSIG organization and technical decisions: https://redmine.gvsig.net/redmine/projects/gvsig-desktop/wiki/Wiki. A post is published after every version of gvSIG with the novelties of the next one.''' &lt;br /&gt;
# Active and healthy community: '''yes, there's an active community of users and developers from multiple countries at the world.'''&lt;br /&gt;
#* The project should have a community of developers and users who actively collaborate and support each other in a healthy way. ''' yes. Users and developers use mailing lists for collaboration and supporting. There are four main mailing lists (in Spanish and English, for developers and for users) and there are also local mailing lists (in different languages or for different areas, like Argentina, Brazil, Italy or Russia among others). For mailing list activity visit: http://osgeo-org.1560.x6.nabble.com/gvSIG-project-f4102529.html Users and developers use the tracker for uploading the errors in gvSIG (https://redmine.gvsig.net/redmine/projects/gvsig-desktop/issues). There are a lot of testers at the community, and there's group of translators, who translate documentation and interface. There are developers that provide patches, new developments, and scripts (at the scripting repository: http://outreach.gvsig.org/scripts/). There's also a web portal for the gvSIG case-studies provided by the community (http://outreach.gvsig.org/case-studies).'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;Eg. collaboration on project activities such as testing, release and feature development.&amp;lt;/i&amp;gt;&lt;br /&gt;
#* Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organizations. '''yes. There are multiple developers from different organizations and a professional structure. The community is participating actively on the development. The commits by developer at the core, the main project, are shown in https://redmine.gvsig.net/redmine/projects/gvsig-desktop/repository/statistics. There are also different sub-projects for the different extensions with their own commits: https://redmine.gvsig.net/redmine/projects. The activity of the project every day is in: https://redmine.gvsig.net/redmine/projects/gvsig-desktop/activity. The gvSIG project is managed by the gvSIG Association, that is composed of four associate companies and more than 40 collaborating companies, as well as different public entities (governments, technical institutes...) and universities. '''&amp;lt;br/&amp;gt; &amp;lt;i&amp;gt; Eg. The project is resilient enough to sustain loss of a developer or supporting organization, 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.&amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Copyright and License ==&lt;br /&gt;
&lt;br /&gt;
We need to ensure that the project owns or otherwise has obtained the ability to release the project code by completing the following steps:&lt;br /&gt;
# All project source code is available under an Open Source license. '''Yes, gvSIG is developed under GNU/GPL version 3 license. All the source code of the different versions is in https://devel.gvsig.org/svn/gvsig-desktop/'''&lt;br /&gt;
# Project documentation is available under an open license, such as Creative Commons. '''Yes. The documentation is under Creative Commons 3.0 CC BY-SA license (there are workshops, tutorials and manuals). They are available in http://www.gvsig.com/. There's a Youtube channel with a lot of videos about the project too: https://www.youtube.com/user/gvsig. All the presentations of the gvSIG Conferences are available too, and the videos are published when they are recorded. There are articles, books and posters about the project compiled at the gvSIG web portal. http://www.gvsig.com/en/diffusion'''&lt;br /&gt;
# 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]. '''Yes. All the information is vetted before publishing (manuals, source code, cartography...). See the gvSIG Code Provenance Review at http://docs.gvsig.org/plone/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2-1-0/provenance-review'''&lt;br /&gt;
# The project maintains a list of all copyright holders identified in the Provenance Review Document. '''No, as all the source code is owned by the gvSIG Association. All the developers have signed the CLA (http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/como-contribuir-en-gvsig/contribuciones-y-parches-al-codigo-de-gvsig/cla-status). '''&lt;br /&gt;
# All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived. '''Yes: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/como-contribuir-en-gvsig/contribuciones-y-parches-al-codigo-de-gvsig/cla-status'''&lt;br /&gt;
&lt;br /&gt;
== Processes ==&lt;br /&gt;
&lt;br /&gt;
# The project has code under configuration management. '''Yes: the main svn is in https://devel.gvsig.org/svn/gvsig-desktop'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;Eg, subversion, git.&amp;lt;/i&amp;gt;&lt;br /&gt;
# The project uses an issue tracker and keeps the status of the issue tracker up to date. '''Yes: The main project is in https://redmine.gvsig.net/redmine/projects/gvsig-desktop/issues. gvSIG is composed of different sub-projects or extensions: https://redmine.gvsig.net/redmine/projects with their own trackers.'''&lt;br /&gt;
# The project has documented its management processes. '''Yes. There are different documents for the different areas'''&lt;br /&gt;
#* About gvSIG Technical decisions: '''https://redmine.gvsig.net/redmine/projects/gvsig-desktop/wiki/Wiki'''&lt;br /&gt;
#* Suggesting new features: '''https://redmine.gvsig.net/redmine/projects/gvsig-desktop/issues/new'''&lt;br /&gt;
#* Developing contributions: '''http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/como-contribuir-en-gvsig'''&lt;br /&gt;
#* Commiters guide: '''http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/guia-para-commiters-de-gvsig'''&lt;br /&gt;
#* Developers guide: '''http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide'''&lt;br /&gt;
#* Documentation guide:''' http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/guia-para-documentar'''&lt;br /&gt;
&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;This is typically done within a Developers Guide or Project Management Plan.&amp;lt;/i&amp;gt;&lt;br /&gt;
#* The project has a suitable open governance policy ensuring decisions are made, documented and adhered to in a public manner. '''Yes: there's a Technical Steering Committee (TSC) formed by professional structure of gvSIG Association and active developers of the community. More information about this in: https://redmine.gvsig.net/redmine/projects/gvsig-desktop/wiki/Wiki. A post is published after every version of gvSIG with the novelties of the next one decided in TSC meetings.'''&amp;lt;br/&amp;gt;&lt;br /&gt;
#* The project uses public communication channels for decision making to maintain transparency. '''Yes: A post is published in gvSIG blog after every version of gvSIG with the novelties of the next one decided in TSC meetings. The road map for the following versions of the application, with the changes, is in https://redmine.gvsig.net/redmine/projects/gvsig-desktop/roadmap.'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt; E.g. archived email list(s), archived IRC channel(s), public issue tracker.  &amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Documentation ==&lt;br /&gt;
&lt;br /&gt;
# The project has user documentation: '''Yes: User documentation is available in http://www.gvsig.com/en/products/gvsig-desktop/documentation. There are workshops, tutorials, posters, articles, presentations and books in http://www.gvsig.com/en/diffusion. There's a Youtube channel with a huge quantity of videos about the project too: https://www.youtube.com/user/gvsig.'''&lt;br /&gt;
#* Including sufficient detail to guide a new user through performing the core functionality provided by the application.&lt;br /&gt;
# The project has developer documentation: '''Yes: Developer documentation http://www.gvsig.com/en/products/gvsig-desktop/development'''&lt;br /&gt;
#* Including checkout and build instructions. '''Yes: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2-1-0/trabajar-con-el-nucleo-de-gvsig/compile_gvsig'''&lt;br /&gt;
#* Including commented code, ideally published for developer use. '''Yes: maven site of main project http://devel.gvsig.org/sites/org.gvsig.desktop/2.0.17/''' &amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;Examples: javadocs for Java applications, or Sphinx documentation for Python applications.&amp;lt;/i&amp;gt;&lt;br /&gt;
#* Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project's programming conventions. '''Yes: It's available at the developer documentation http://www.gvsig.com/en/products/gvsig-desktop/development''' &lt;br /&gt;
&lt;br /&gt;
==Release Procedure==&lt;br /&gt;
&lt;br /&gt;
In order to maintain a consistent level of quality, the project should follow defined release and testing processes.&lt;br /&gt;
&lt;br /&gt;
# The project follows a defined release process: '''yes: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2-1-0/release-guide'''&lt;br /&gt;
#* Which includes execution of the testing process before releasing a stable release. '''yes, there's a testing procedure available for gvSIG, which is a workshop with the cartography: http://docs.gvsig.org/plone/docusr/doctesting/interesting-links-for-testers/view'''&lt;br /&gt;
# The project follows a documented testing process. '''There's also a quick testing process for an initial test: http://downloads.gvsig.org/download/testing/testgvSIG_en.pdf '''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;This includes manual testing&amp;lt;/i&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
# Release and testing processes provide sufficient detail for an experienced programmer to follow. '''Yes, it's available at the documentation section for developers: http://www.gvsig.com/en/products/gvsig-desktop/development'''.&lt;br /&gt;
&lt;br /&gt;
= OSGeo Committees and Community =&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Board ==&lt;br /&gt;
&lt;br /&gt;
The OSGeo [[Board]] holds ultimate responsibility for all OSGeo activities. The Board requests:&lt;br /&gt;
&lt;br /&gt;
# A project provide a Project Officer as a contact point: '''Yes'''&lt;br /&gt;
#* The Project Officer should be listed at: [[Contacts#Software_Projects|Project Officer]]&lt;br /&gt;
#* This person is established when the incubation committee recommends the project for graduation&lt;br /&gt;
#* 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).&lt;br /&gt;
&lt;br /&gt;
== Marketing ==&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&lt;br /&gt;
# 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:&lt;br /&gt;
#* Application Overview '''Yes. http://live.osgeo.org/en/overview/gvsig_overview.html'''&lt;br /&gt;
#* Application Quick Start '''Yes. http://live.osgeo.org/en/quickstart/gvsig_quickstart.html'''&lt;br /&gt;
#* Logo '''Yes. http://live.osgeo.org/_images/logo-gvSIG.png'''&lt;br /&gt;
#* Graphical Image '''Yes. http://live.osgeo.org/_images/gvsig_desktop.png'''&lt;br /&gt;
# Ideally, stable version(s) of executable applications are bundled with appropriate distributions. '''Yes: OSGeo-Live.'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;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.)&amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Projects ==&lt;br /&gt;
&lt;br /&gt;
Projects do not exist in isolation; and are expected to communicate and collaborate on key issues. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;i&amp;gt;As an example the PostGIS release procedure asks that the release be checked with MapServer, GeoServer and others.&amp;lt;/i&amp;gt; gvSIG uses several libraries, like gdal or NASA World Wind, and they are reviewed and updated before releasing the gvSIG versions. &lt;br /&gt;
&lt;br /&gt;
== SAC ==&lt;br /&gt;
&lt;br /&gt;
gvSIG has several mailing lists operating by the OSGeo infrastructure: https://lists.osgeo.org/mailman/listinfo&lt;br /&gt;
&lt;br /&gt;
[[Category: Incubation]]&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=GvSIG_Incubation_Checklist&amp;diff=86956</id>
		<title>GvSIG Incubation Checklist</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=GvSIG_Incubation_Checklist&amp;diff=86956"/>
		<updated>2015-10-01T12:31:13Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Document Status =&lt;br /&gt;
&lt;br /&gt;
'''Version''': 2.0&lt;br /&gt;
&lt;br /&gt;
'''Last Updated''': October 2015.&lt;br /&gt;
&lt;br /&gt;
'''Status''': Draft&lt;br /&gt;
&lt;br /&gt;
= Purpose =&lt;br /&gt;
&lt;br /&gt;
The purpose of this checklist is to determine whether an Incubator Project produces quality products, remains true to its stated licence and is sustainable. Satisfying this checklist is a pre-requisite for graduation.&lt;br /&gt;
&lt;br /&gt;
A project should have institutionalized the processes in this list or provide justification why the process is not used.&lt;br /&gt;
&lt;br /&gt;
See also:&lt;br /&gt;
&lt;br /&gt;
* [http://www.osgeo.org/incubator/process/application.html Incubation Application Questionnaire]&lt;br /&gt;
* [http://www.osgeo.org/incubator/process/statustemplate.html Project Status Template]&lt;br /&gt;
&lt;br /&gt;
= Terms and Definitions =&lt;br /&gt;
&lt;br /&gt;
; Mentor : A member of the Incubation Committee chosen to assist a Project through the Incubation Process.&lt;br /&gt;
; Institutionalized Process : A documented process which which addresses a need and is actively in use. It typically takes months before a process becomes institutionalized. ''A more detailed definition of institutionalization is found in the [http://www.sei.cmu.edu/pub/documents/02.reports/pdf/02tr012.pdf Capability Maturity Model (CMMI)] - &amp;quot;Generic Goal 2: Institutionalize a Managed Process&amp;quot;''&lt;br /&gt;
; Open Source License : a license recognized by the [http://opensource.org Open Source Initiative]&lt;br /&gt;
&lt;br /&gt;
= Incubation Checklist =&lt;br /&gt;
&lt;br /&gt;
== Open ==&lt;br /&gt;
	 &lt;br /&gt;
The project has demonstrated that it has an open, active and healthy user and developer community:	&lt;br /&gt;
# Open: projects are expected to function in an open and public manner and include:&lt;br /&gt;
#* Open source license(s), '''yes: gvSIG is developed under GNU/GPL version 3 license'''&lt;br /&gt;
#* Open communication channels, '''yes: there are several users and developers mailing lists in different languages (http://www.gvsig.com/en/community/mailing-lists). There's also a mail address (info@gvsig.com), a phone number (0034-961110070) and a fax number (0034-901021995)'''&lt;br /&gt;
#* Open decision making process, '''yes: About gvSIG organization and technical decisions: https://redmine.gvsig.net/redmine/projects/gvsig-desktop/wiki/Wiki. A post is published after every version of gvSIG with the novelties of the next one.''' The information on the gvSIG Technical Steering Committee can be found at http://wiki.osgeo.org/wiki/GvSIG_Technical_Steering_Committee&lt;br /&gt;
# Active and healthy community: '''yes, there's an active community of users and developers from multiple countries at the world.'''&lt;br /&gt;
#* The project should have a community of developers and users who actively collaborate and support each other in a healthy way. ''' yes. Users and developers use mailing lists for collaboration and supporting. There are four main mailing lists (in Spanish and English, for developers and for users) and there are also local mailing lists (in different languages or for different areas, like Argentina, Brazil, Italy or Russia among others). For mailing list activity visit: http://osgeo-org.1560.x6.nabble.com/gvSIG-project-f4102529.html Users and developers use the tracker for uploading the errors in gvSIG (https://redmine.gvsig.net/redmine/projects/gvsig-desktop/issues). There are a lot of testers at the community, and there's group of translators, who translate documentation and interface. There are developers that provide patches, new developments, and scripts (at the scripting repository: http://outreach.gvsig.org/scripts/). There's also a web portal for the gvSIG case-studies provided by the community (http://outreach.gvsig.org/case-studies).'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;Eg. collaboration on project activities such as testing, release and feature development.&amp;lt;/i&amp;gt;&lt;br /&gt;
#* Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organizations. '''yes. There are multiple developers from different organizations and a professional structure. The community is participating actively on the development. The commits by developer at the core, the main project, are shown in https://redmine.gvsig.net/redmine/projects/gvsig-desktop/repository/statistics. There are also different sub-projects for the different extensions with their own commits: https://redmine.gvsig.net/redmine/projects. The activity of the project every day is in: https://redmine.gvsig.net/redmine/projects/gvsig-desktop/activity. The gvSIG project is managed by the gvSIG Association, that is composed of four associate companies and more than 40 collaborating companies, as well as different public entities (governments, technical institutes...) and universities. '''&amp;lt;br/&amp;gt; &amp;lt;i&amp;gt; Eg. The project is resilient enough to sustain loss of a developer or supporting organization, 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.&amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Copyright and License ==&lt;br /&gt;
&lt;br /&gt;
We need to ensure that the project owns or otherwise has obtained the ability to release the project code by completing the following steps:&lt;br /&gt;
# All project source code is available under an Open Source license. '''Yes, gvSIG is developed under GNU/GPL version 3 license. All the source code of the different versions is in https://devel.gvsig.org/svn/gvsig-desktop/'''&lt;br /&gt;
# Project documentation is available under an open license, such as Creative Commons. '''Yes. The documentation is under Creative Commons 3.0 CC BY-SA license (there are workshops, tutorials and manuals). They are available in http://www.gvsig.com/. There's a Youtube channel with a lot of videos about the project too: https://www.youtube.com/user/gvsig. All the presentations of the gvSIG Conferences are available too, and the videos are published when they are recorded. There are articles, books and posters about the project compiled at the gvSIG web portal. http://www.gvsig.com/en/diffusion'''&lt;br /&gt;
# 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]. '''Yes. All the information is vetted before publishing (manuals, source code, cartography...). See the gvSIG Code Provenance Review at http://docs.gvsig.org/plone/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2-1-0/provenance-review'''&lt;br /&gt;
# The project maintains a list of all copyright holders identified in the Provenance Review Document. '''No, as all the source code is owned by the gvSIG Association. All the developers have signed the CLA (http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/como-contribuir-en-gvsig/contribuciones-y-parches-al-codigo-de-gvsig/cla-status). '''&lt;br /&gt;
# All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived. '''Yes: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/como-contribuir-en-gvsig/contribuciones-y-parches-al-codigo-de-gvsig/cla-status'''&lt;br /&gt;
&lt;br /&gt;
== Processes ==&lt;br /&gt;
&lt;br /&gt;
# The project has code under configuration management. '''Yes: the main svn is in https://devel.gvsig.org/svn/gvsig-desktop'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;Eg, subversion, git.&amp;lt;/i&amp;gt;&lt;br /&gt;
# The project uses an issue tracker and keeps the status of the issue tracker up to date. '''Yes: The main project is in https://redmine.gvsig.net/redmine/projects/gvsig-desktop/issues. gvSIG is composed of different sub-projects or extensions: https://redmine.gvsig.net/redmine/projects with their own trackers.'''&lt;br /&gt;
# The project has documented its management processes. '''Yes. There are different documents for the different areas'''&lt;br /&gt;
#* About gvSIG Technical decisions: '''https://redmine.gvsig.net/redmine/projects/gvsig-desktop/wiki/Wiki'''&lt;br /&gt;
#* Suggesting new features: '''https://redmine.gvsig.net/redmine/projects/gvsig-desktop/issues/new'''&lt;br /&gt;
#* Developing contributions: '''http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/como-contribuir-en-gvsig'''&lt;br /&gt;
#* Commiters guide: '''http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/guia-para-commiters-de-gvsig'''&lt;br /&gt;
#* Developers guide: '''http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide'''&lt;br /&gt;
#* Documentation guide:''' http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/guia-para-documentar'''&lt;br /&gt;
&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;This is typically done within a Developers Guide or Project Management Plan.&amp;lt;/i&amp;gt;&lt;br /&gt;
#* The project has a suitable open governance policy ensuring decisions are made, documented and adhered to in a public manner. '''Yes: there's a Technical Steering Committee (TSC) formed by professional structure of gvSIG Association and active developers of the community. More information about this in: https://redmine.gvsig.net/redmine/projects/gvsig-desktop/wiki/Wiki. A post is published after every version of gvSIG with the novelties of the next one decided in TSC meetings.'''&amp;lt;br/&amp;gt;&lt;br /&gt;
#* The project uses public communication channels for decision making to maintain transparency. '''Yes: A post is published in gvSIG blog after every version of gvSIG with the novelties of the next one decided in TSC meetings. The road map for the following versions of the application, with the changes, is in https://redmine.gvsig.net/redmine/projects/gvsig-desktop/roadmap.'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt; E.g. archived email list(s), archived IRC channel(s), public issue tracker.  &amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Documentation ==&lt;br /&gt;
&lt;br /&gt;
# The project has user documentation: '''Yes: User documentation is available in http://www.gvsig.com/en/products/gvsig-desktop/documentation. There are workshops, tutorials, posters, articles, presentations and books in http://www.gvsig.com/en/diffusion. There's a Youtube channel with a huge quantity of videos about the project too: https://www.youtube.com/user/gvsig.'''&lt;br /&gt;
#* Including sufficient detail to guide a new user through performing the core functionality provided by the application.&lt;br /&gt;
# The project has developer documentation: '''Yes: Developer documentation http://www.gvsig.com/en/products/gvsig-desktop/development'''&lt;br /&gt;
#* Including checkout and build instructions. '''Yes: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2-1-0/trabajar-con-el-nucleo-de-gvsig/compile_gvsig'''&lt;br /&gt;
#* Including commented code, ideally published for developer use. '''Yes: maven site of main project http://devel.gvsig.org/sites/org.gvsig.desktop/2.0.17/''' &amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;Examples: javadocs for Java applications, or Sphinx documentation for Python applications.&amp;lt;/i&amp;gt;&lt;br /&gt;
#* Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project's programming conventions. '''Yes: It's available at the developer documentation http://www.gvsig.com/en/products/gvsig-desktop/development''' &lt;br /&gt;
&lt;br /&gt;
==Release Procedure==&lt;br /&gt;
&lt;br /&gt;
In order to maintain a consistent level of quality, the project should follow defined release and testing processes.&lt;br /&gt;
&lt;br /&gt;
# The project follows a defined release process: '''yes: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2-1-0/release-guide'''&lt;br /&gt;
#* Which includes execution of the testing process before releasing a stable release. '''yes, there's a testing procedure available for gvSIG, which is a workshop with the cartography: http://docs.gvsig.org/plone/docusr/doctesting/interesting-links-for-testers/view'''&lt;br /&gt;
# The project follows a documented testing process. '''There's also a quick testing process for an initial test: http://downloads.gvsig.org/download/testing/testgvSIG_en.pdf '''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;This includes manual testing&amp;lt;/i&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
# Release and testing processes provide sufficient detail for an experienced programmer to follow. '''Yes, it's available at the documentation section for developers: http://www.gvsig.com/en/products/gvsig-desktop/development'''.&lt;br /&gt;
&lt;br /&gt;
= OSGeo Committees and Community =&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Board ==&lt;br /&gt;
&lt;br /&gt;
The OSGeo [[Board]] holds ultimate responsibility for all OSGeo activities. The Board requests:&lt;br /&gt;
&lt;br /&gt;
# A project provide a Project Officer as a contact point: '''Yes'''&lt;br /&gt;
#* The Project Officer should be listed at: [[Contacts#Software_Projects|Project Officer]]&lt;br /&gt;
#* This person is established when the incubation committee recommends the project for graduation&lt;br /&gt;
#* 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).&lt;br /&gt;
&lt;br /&gt;
== Marketing ==&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&lt;br /&gt;
# 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:&lt;br /&gt;
#* Application Overview '''Yes. http://live.osgeo.org/en/overview/gvsig_overview.html'''&lt;br /&gt;
#* Application Quick Start '''Yes. http://live.osgeo.org/en/quickstart/gvsig_quickstart.html'''&lt;br /&gt;
#* Logo '''Yes. http://live.osgeo.org/_images/logo-gvSIG.png'''&lt;br /&gt;
#* Graphical Image '''Yes. http://live.osgeo.org/_images/gvsig_desktop.png'''&lt;br /&gt;
# Ideally, stable version(s) of executable applications are bundled with appropriate distributions. '''Yes: OSGeo-Live.'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;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.)&amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Projects ==&lt;br /&gt;
&lt;br /&gt;
Projects do not exist in isolation; and are expected to communicate and collaborate on key issues. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;i&amp;gt;As an example the PostGIS release procedure asks that the release be checked with MapServer, GeoServer and others.&amp;lt;/i&amp;gt; gvSIG uses several libraries, like gdal or NASA World Wind, and they are reviewed and updated before releasing the gvSIG versions. &lt;br /&gt;
&lt;br /&gt;
== SAC ==&lt;br /&gt;
&lt;br /&gt;
gvSIG has several mailing lists operating by the OSGeo infrastructure: https://lists.osgeo.org/mailman/listinfo&lt;br /&gt;
&lt;br /&gt;
[[Category: Incubation]]&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=GvSIG_Incubation_Checklist&amp;diff=84583</id>
		<title>GvSIG Incubation Checklist</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=GvSIG_Incubation_Checklist&amp;diff=84583"/>
		<updated>2015-06-16T11:54:48Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Document Status =&lt;br /&gt;
&lt;br /&gt;
'''Version''': 2.0&lt;br /&gt;
&lt;br /&gt;
'''Last Updated''': June 2015.&lt;br /&gt;
&lt;br /&gt;
'''Status''': Draft&lt;br /&gt;
&lt;br /&gt;
= Purpose =&lt;br /&gt;
&lt;br /&gt;
The purpose of this checklist is to determine whether an Incubator Project produces quality products, remains true to its stated licence and is sustainable. Satisfying this checklist is a pre-requisite for graduation.&lt;br /&gt;
&lt;br /&gt;
A project should have institutionalized the processes in this list or provide justification why the process is not used.&lt;br /&gt;
&lt;br /&gt;
See also:&lt;br /&gt;
&lt;br /&gt;
* [http://www.osgeo.org/incubator/process/application.html Incubation Application Questionnaire]&lt;br /&gt;
* [http://www.osgeo.org/incubator/process/statustemplate.html Project Status Template]&lt;br /&gt;
&lt;br /&gt;
= Terms and Definitions =&lt;br /&gt;
&lt;br /&gt;
; Mentor : A member of the Incubation Committee chosen to assist a Project through the Incubation Process.&lt;br /&gt;
; Institutionalized Process : A documented process which which addresses a need and is actively in use. It typically takes months before a process becomes institutionalized. ''A more detailed definition of institutionalization is found in the [http://www.sei.cmu.edu/pub/documents/02.reports/pdf/02tr012.pdf Capability Maturity Model (CMMI)] - &amp;quot;Generic Goal 2: Institutionalize a Managed Process&amp;quot;''&lt;br /&gt;
; Open Source License : a license recognized by the [http://opensource.org Open Source Initiative]&lt;br /&gt;
&lt;br /&gt;
= Incubation Checklist =&lt;br /&gt;
&lt;br /&gt;
== Open ==&lt;br /&gt;
	 &lt;br /&gt;
The project has demonstrated that it has an open, active and healthy user and developer community:	&lt;br /&gt;
# Open: projects are expected to function in an open and public manner and include:&lt;br /&gt;
#* Open source license(s), '''yes: gvSIG is developed under GNU/GPL version 3 license'''&lt;br /&gt;
#* Open communication channels, '''yes: there are several users and developers mailing lists in different languages (http://www.gvsig.com/en/community/mailing-lists). There's also a mail address (info@gvsig.com), a phone number (0034-961110070) and a fax number (0034-901021995)'''&lt;br /&gt;
#* Open decision making process, '''yes: Public mailing list of the gvSIG Technical Steering Committee (TSC) (http://joinup.ec.europa.eu/mailman/listinfo/gvsig-desktop-tsc-pub). There's a roadmap with the decisions taken by the board of the Technical Steering Committee: https://redmine.gvsig.net/redmine/projects/gvsig-cdt-board/roadmap. A post is published after every version of gvSIG with the novelties of the next one.'''&lt;br /&gt;
# Active and healthy community: '''yes, there's an active community of users and developers from multiple countries at the world.'''&lt;br /&gt;
#* The project should have a community of developers and users who actively collaborate and support each other in a healthy way. ''' yes. Users and developers use mailing lists for collaboration and supporting. There are four main mailing lists (in Spanish and English, for developers and for users) and there are also local mailing lists (in different languages or for different areas, like Argentina, Brazil, Italy or Russia among others). Users and developers use the tracker for uploading the errors in gvSIG (https://redmine.gvsig.net/redmine/projects/gvsig-desktop/issues). There are a lot of testers at the community, and there's group of translators, who translate documentation and interface. There are developers that provide patches, new developments, and scripts (at the scripting repository: http://outreach.gvsig.org/scripts/). There's also a web portal for the gvSIG case-studies provided by the community (http://outreach.gvsig.org/case-studies).'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;Eg. collaboration on project activities such as testing, release and feature development.&amp;lt;/i&amp;gt;&lt;br /&gt;
#* Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organizations. '''yes. There are multiple developers from different organizations. The community is participating actively on the development. The commits by developer at the core, the main project, are shown in https://redmine.gvsig.net/redmine/projects/gvsig-desktop/repository/statistics. There are also different sub-projects for the different extensions with their own commits: https://redmine.gvsig.net/redmine/projects. The activity of the project every day is in: https://redmine.gvsig.net/redmine/projects/gvsig-desktop/activity. The gvSIG project is managed by the gvSIG Association, that is composed of four associate companies and more than 40 collaborating companies, as well as different public entities (governments, technical institutes...) and universities. '''&amp;lt;br/&amp;gt; &amp;lt;i&amp;gt; Eg. The project is resilient enough to sustain loss of a developer or supporting organization, 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.&amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Copyright and License ==&lt;br /&gt;
&lt;br /&gt;
We need to ensure that the project owns or otherwise has obtained the ability to release the project code by completing the following steps:&lt;br /&gt;
# All project source code is available under an Open Source license. '''Yes. All the source code of the different versions is in https://devel.gvsig.org/svn/gvsig-desktop/'''&lt;br /&gt;
# Project documentation is available under an open license, such as Creative Commons. '''Yes. The documentation is under an open license (there are workshops, tutorials and manuals). They are available in http://www.gvsig.com/. There's a Youtube channel with a lot of videos about the project too: https://www.youtube.com/user/gvsig. All the presentations of the gvSIG Conferences are available too, and the videos are published when they are recorded. There are articles, books and posters about the project compiled at the gvSIG web portal. '''&lt;br /&gt;
# 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]. '''Yes. All the information is vetted before publishing (manuals, source code, cartography...).'''&lt;br /&gt;
# The project maintains a list of all copyright holders identified in the Provenance Review Document. '''No, as all the source code is owned by the gvSIG Association. All the developers have signed the CLA (http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/como-contribuir-en-gvsig/contribuciones-y-parches-al-codigo-de-gvsig/cla-status). '''&lt;br /&gt;
# All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived. '''Yes: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/como-contribuir-en-gvsig/contribuciones-y-parches-al-codigo-de-gvsig/cla-status'''&lt;br /&gt;
&lt;br /&gt;
== Processes ==&lt;br /&gt;
&lt;br /&gt;
# The project has code under configuration management. '''Yes: the main svn is in https://devel.gvsig.org/svn/gvsig-desktop'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;Eg, subversion, git.&amp;lt;/i&amp;gt;&lt;br /&gt;
# The project uses an issue tracker and keeps the status of the issue tracker up to date. '''Yes: The main project is in https://redmine.gvsig.net/redmine/projects/gvsig-desktop/issues. gvSIG is composed of different sub-projects or extensions: https://redmine.gvsig.net/redmine/projects with their own trackers.'''&lt;br /&gt;
# The project has documented its management processes. '''Yes. There are different documents for the different areas'''&lt;br /&gt;
#* How to contribute: '''http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/como-contribuir-en-gvsig'''&lt;br /&gt;
#* Commiters guide: '''http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/guia-para-commiters-de-gvsig'''&lt;br /&gt;
#* Developers guide: '''http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide'''&lt;br /&gt;
#* Documentation guide:''' http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/guia-para-documentar'''&lt;br /&gt;
&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;This is typically done within a Developers Guide or Project Management Plan.&amp;lt;/i&amp;gt;&lt;br /&gt;
#* The project has a suitable open governance policy ensuring decisions are made, documented and adhered to in a public manner. '''Yes: there's a Technical Steering Committee (TSC) http://docs.gvsig.org/web/working-groups/organizacion. There's a roadmap with the decisions taken by the board of the Technical Steering Committee: https://redmine.gvsig.net/redmine/projects/gvsig-cdt-board/roadmap'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;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 organizations as there will be a greater variety of technical visions and the project is more resilient to a sponsor leaving.&amp;lt;/i&amp;gt;&lt;br /&gt;
#* The project uses public communication channels for decision making to maintain transparency. '''Yes: Archives of the TSC mailing list http://joinup.ec.europa.eu/mailman/listinfo/gvsig-desktop-tsc-pub. The road map for the following versions of the application, with the changes, is in https://redmine.gvsig.net/redmine/projects/gvsig-desktop/roadmap.'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt; E.g. archived email list(s), archived IRC channel(s), public issue tracker.  &amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Documentation ==&lt;br /&gt;
&lt;br /&gt;
# The project has user documentation: '''Yes: User documentation is available in http://www.gvsig.com/en/products/gvsig-desktop/documentation. There are workshops, tutorials, posters, articles, presentations and books in http://www.gvsig.com/en/diffusion. There's a Youtube channel with a huge quantity of videos about the project too: https://www.youtube.com/user/gvsig.'''&lt;br /&gt;
#* Including sufficient detail to guide a new user through performing the core functionality provided by the application.&lt;br /&gt;
# The project has developer documentation: '''Yes: Developer documentation http://www.gvsig.com/en/products/gvsig-desktop/development'''&lt;br /&gt;
#* Including checkout and build instructions. '''Yes: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2-1-0/trabajar-con-el-nucleo-de-gvsig/compile_gvsig'''&lt;br /&gt;
#* Including commented code, ideally published for developer use. '''Yes: maven site of main project http://devel.gvsig.org/sites/org.gvsig.desktop/2.0.17/''' &amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;Examples: javadocs for Java applications, or Sphinx documentation for Python applications.&amp;lt;/i&amp;gt;&lt;br /&gt;
#* Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project's programming conventions. '''Yes: It's available at the developer documentation http://www.gvsig.com/en/products/gvsig-desktop/development''' &lt;br /&gt;
&lt;br /&gt;
==Release Procedure==&lt;br /&gt;
&lt;br /&gt;
In order to maintain a consistent level of quality, the project should follow defined release and testing processes.&lt;br /&gt;
&lt;br /&gt;
# The project follows a defined release process: '''yes: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2-1-0/release-guide'''&lt;br /&gt;
#* Which includes execution of the testing process before releasing a stable release. '''yes, there's a testing procedure available for gvSIG, which is a workshop with the cartography: http://docs.gvsig.org/plone/docusr/doctesting/interesting-links-for-testers/view'''&lt;br /&gt;
# The project follows a documented testing process. '''There's also a quick testing process for an initial test: http://downloads.gvsig.org/download/testing/testgvSIG_en.pdf '''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;This includes manual testing&amp;lt;/i&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
# Release and testing processes provide sufficient detail for an experienced programmer to follow. '''Yes, it's available at the documentation section for developers: http://www.gvsig.com/en/products/gvsig-desktop/development'''.&lt;br /&gt;
&lt;br /&gt;
= OSGeo Committees and Community =&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Board ==&lt;br /&gt;
&lt;br /&gt;
The OSGeo [[Board]] holds ultimate responsibility for all OSGeo activities. The Board requests:&lt;br /&gt;
&lt;br /&gt;
# A project provide a Project Officer as a contact point: '''Yes'''&lt;br /&gt;
#* The Project Officer should be listed at: [[Contacts#Software_Projects|Project Officer]]&lt;br /&gt;
#* This person is established when the incubation committee recommends the project for graduation&lt;br /&gt;
#* 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).&lt;br /&gt;
&lt;br /&gt;
== Marketing ==&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&lt;br /&gt;
# 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:&lt;br /&gt;
#* Application Overview '''Yes. http://live.osgeo.org/en/overview/gvsig_overview.html'''&lt;br /&gt;
#* Application Quick Start '''Yes. http://live.osgeo.org/en/quickstart/gvsig_quickstart.html'''&lt;br /&gt;
#* Logo '''Yes. http://live.osgeo.org/_images/logo-gvSIG.png'''&lt;br /&gt;
#* Graphical Image '''Yes. http://live.osgeo.org/_images/gvsig_desktop.png'''&lt;br /&gt;
# Ideally, stable version(s) of executable applications are bundled with appropriate distributions. '''Yes: OSGeo-Live.'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;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.)&amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Projects ==&lt;br /&gt;
&lt;br /&gt;
Projects do not exist in isolation; and are expected to communicate and collaborate on key issues. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;i&amp;gt;As an example the PostGIS release procedure asks that the release be checked with MapServer, GeoServer and others.&amp;lt;/i&amp;gt; gvSIG uses several libraries, like gdal or NASA World Wind, and they are reviewed and updated before releasing the gvSIG versions. &lt;br /&gt;
&lt;br /&gt;
== SAC ==&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
* A http://projectname.osgeo.org domain name. '''Yes.'''&lt;br /&gt;
&lt;br /&gt;
A project may optionally request SAC help to make use of:&lt;br /&gt;
* OSGeo issue tracker&lt;br /&gt;
* OSGeo mailing list '''Yes.'''&lt;br /&gt;
* OSGeo svn&lt;br /&gt;
* http://downloads.osgeo.org&lt;br /&gt;
&lt;br /&gt;
[[Category: Incubation]]&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=GvSIG_Incubation_Checklist&amp;diff=84582</id>
		<title>GvSIG Incubation Checklist</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=GvSIG_Incubation_Checklist&amp;diff=84582"/>
		<updated>2015-06-16T11:52:09Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Document Status =&lt;br /&gt;
&lt;br /&gt;
'''Version''': 2.0&lt;br /&gt;
&lt;br /&gt;
'''Last Updated''': June 2015.&lt;br /&gt;
&lt;br /&gt;
'''Status''': Draft&lt;br /&gt;
&lt;br /&gt;
= Purpose =&lt;br /&gt;
&lt;br /&gt;
The purpose of this checklist is to determine whether an Incubator Project produces quality products, remains true to its stated licence and is sustainable. Satisfying this checklist is a pre-requisite for graduation.&lt;br /&gt;
&lt;br /&gt;
A project should have institutionalized the processes in this list or provide justification why the process is not used.&lt;br /&gt;
&lt;br /&gt;
See also:&lt;br /&gt;
&lt;br /&gt;
* [http://www.osgeo.org/incubator/process/application.html Incubation Application Questionnaire]&lt;br /&gt;
* [http://www.osgeo.org/incubator/process/statustemplate.html Project Status Template]&lt;br /&gt;
&lt;br /&gt;
= Terms and Definitions =&lt;br /&gt;
&lt;br /&gt;
; Mentor : A member of the Incubation Committee chosen to assist a Project through the Incubation Process.&lt;br /&gt;
; Institutionalized Process : A documented process which which addresses a need and is actively in use. It typically takes months before a process becomes institutionalized. ''A more detailed definition of institutionalization is found in the [http://www.sei.cmu.edu/pub/documents/02.reports/pdf/02tr012.pdf Capability Maturity Model (CMMI)] - &amp;quot;Generic Goal 2: Institutionalize a Managed Process&amp;quot;''&lt;br /&gt;
; Open Source License : a license recognized by the [http://opensource.org Open Source Initiative]&lt;br /&gt;
&lt;br /&gt;
= Incubation Checklist =&lt;br /&gt;
&lt;br /&gt;
== Open ==&lt;br /&gt;
	 &lt;br /&gt;
The project has demonstrated that it has an open, active and healthy user and developer community:	&lt;br /&gt;
# Open: projects are expected to function in an open and public manner and include:&lt;br /&gt;
#* Open source license(s), '''yes: gvSIG is developed under GNU/GPL version 3 license'''&lt;br /&gt;
#* Open communication channels, '''yes: there are several users and developers mailing lists in different languages (http://www.gvsig.com/en/community/mailing-lists). There's also a mail address (info@gvsig.com), a phone number (0034-961110070) and a fax number (0034-901021995)'''&lt;br /&gt;
#* Open decision making process, '''yes: Public mailing list of the gvSIG Technical Steering Committee (TSC) (http://joinup.ec.europa.eu/mailman/listinfo/gvsig-desktop-tsc-pub). There's a roadmap with the decisions taken by the board of the Technical Steering Committee: https://redmine.gvsig.net/redmine/projects/gvsig-cdt-board/roadmap. A post is published after every version of gvSIG with the novelties of the next one.'''&lt;br /&gt;
# Active and healthy community: '''yes, there's an active community of users and developers from multiple countries at the world.'''&lt;br /&gt;
#* The project should have a community of developers and users who actively collaborate and support each other in a healthy way. ''' yes. Users and developers use mailing lists for collaboration and supporting. There are four main mailing lists (in Spanish and English, for developers and for users) and there are also local mailing lists (in different languages or for different areas, like Argentina, Brazil, Italy or Russia among others). Users and developers use the tracker for uploading the errors in gvSIG (https://redmine.gvsig.net/redmine/projects/gvsig-desktop/issues). There are a lot of testers at the community, and there's group of translators, who translate documentation and interface. There are developers that provide patches, new developments, and scripts (at the scripting repository: http://outreach.gvsig.org/scripts/). There's also a web portal for the gvSIG case-studies provided by the community (http://outreach.gvsig.org/case-studies).'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;Eg. collaboration on project activities such as testing, release and feature development.&amp;lt;/i&amp;gt;&lt;br /&gt;
#* Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organizations. '''yes. There are multiple developers from different organizations. The community is participating actively on the development. The commits by developer at the core, the main project, are shown in https://redmine.gvsig.net/redmine/projects/gvsig-desktop/repository/statistics. There are also different sub-projects for the different extensions with their own commits: https://redmine.gvsig.net/redmine/projects. The activity of the project every day is in: https://redmine.gvsig.net/redmine/projects/gvsig-desktop/activity. The gvSIG project is managed by the gvSIG Association, that is composed of four associate companies and more than 40 collaborating companies, as well as different public entities (governments, technical institutes...) and universities. '''&amp;lt;br/&amp;gt; &amp;lt;i&amp;gt; Eg. The project is resilient enough to sustain loss of a developer or supporting organization, 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.&amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Copyright and License ==&lt;br /&gt;
&lt;br /&gt;
We need to ensure that the project owns or otherwise has obtained the ability to release the project code by completing the following steps:&lt;br /&gt;
# All project source code is available under an Open Source license. '''Yes. All the source code of the different versions is in https://devel.gvsig.org/svn/gvsig-desktop/'''&lt;br /&gt;
# Project documentation is available under an open license, such as Creative Commons. '''Yes. The documentation is under an open license (there are workshops, tutorials and manuals). They are available in http://www.gvsig.com/. There's a Youtube channel with a lot of videos about the project too: https://www.youtube.com/user/gvsig. All the presentations of the gvSIG Conferences are available too, and the videos are published when they are recorded. There are articles, books and posters about the project compiled at the gvSIG web portal. '''&lt;br /&gt;
# 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]. '''Yes. All the information is vetted before publishing (manuals, source code, cartography...).'''&lt;br /&gt;
# The project maintains a list of all copyright holders identified in the Provenance Review Document. '''No, as all the source code is owned by the gvSIG Association. All the developers have signed the CLA (http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/como-contribuir-en-gvsig/contribuciones-y-parches-al-codigo-de-gvsig/cla-status). '''&lt;br /&gt;
# All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived. '''Yes: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/como-contribuir-en-gvsig/contribuciones-y-parches-al-codigo-de-gvsig/cla-status'''&lt;br /&gt;
&lt;br /&gt;
== Processes ==&lt;br /&gt;
&lt;br /&gt;
# The project has code under configuration management. '''Yes: the main svn is in https://devel.gvsig.org/svn/gvsig-desktop'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;Eg, subversion, git.&amp;lt;/i&amp;gt;&lt;br /&gt;
# The project uses an issue tracker and keeps the status of the issue tracker up to date. '''Yes: The main project is in https://redmine.gvsig.net/redmine/projects/gvsig-desktop/issues. gvSIG is composed of different sub-projects or extensions: https://redmine.gvsig.net/redmine/projects with their own trackers.'''&lt;br /&gt;
# The project has documented its management processes. '''Yes. There are different documents for the different areas'''&lt;br /&gt;
#* How to contribute: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/como-contribuir-en-gvsig&lt;br /&gt;
#* Commiters guide: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/guia-para-commiters-de-gvsig&lt;br /&gt;
#* Developers guide: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide&lt;br /&gt;
#* Documentation guide: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/guia-para-documentar&lt;br /&gt;
&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;This is typically done within a Developers Guide or Project Management Plan.&amp;lt;/i&amp;gt;&lt;br /&gt;
#* The project has a suitable open governance policy ensuring decisions are made, documented and adhered to in a public manner. '''Yes: there's a Technical Steering Committee (TSC) http://docs.gvsig.org/web/working-groups/organizacion. There's a roadmap with the decisions taken by the board of the Technical Steering Committee: https://redmine.gvsig.net/redmine/projects/gvsig-cdt-board/roadmap'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;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 organizations as there will be a greater variety of technical visions and the project is more resilient to a sponsor leaving.&amp;lt;/i&amp;gt;&lt;br /&gt;
#* The project uses public communication channels for decision making to maintain transparency. '''Yes: Archives of the TSC mailing list http://joinup.ec.europa.eu/mailman/listinfo/gvsig-desktop-tsc-pub'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt; E.g. archived email list(s), archived IRC channel(s), public issue tracker. '''The road map for the following versions of the application, with the changes, is in https://redmine.gvsig.net/redmine/projects/gvsig-desktop/roadmap.''' &amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Documentation ==&lt;br /&gt;
&lt;br /&gt;
# The project has user documentation: '''Yes: User documentation is available in http://www.gvsig.com/en/products/gvsig-desktop/documentation. There are workshops, tutorials, posters, articles, presentations and books in http://www.gvsig.com/en/diffusion. There's a Youtube channel with a huge quantity of videos about the project too: https://www.youtube.com/user/gvsig.'''&lt;br /&gt;
#* Including sufficient detail to guide a new user through performing the core functionality provided by the application.&lt;br /&gt;
# The project has developer documentation: '''Yes: Developer documentation http://www.gvsig.com/en/products/gvsig-desktop/development'''&lt;br /&gt;
#* Including checkout and build instructions. '''Yes: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2-1-0/trabajar-con-el-nucleo-de-gvsig/compile_gvsig'''&lt;br /&gt;
#* Including commented code, ideally published for developer use. '''Yes: maven site of main project http://devel.gvsig.org/sites/org.gvsig.desktop/2.0.17/''' &amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;Examples: javadocs for Java applications, or Sphinx documentation for Python applications.&amp;lt;/i&amp;gt;&lt;br /&gt;
#* Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project's programming conventions. '''Yes: It's available at the developer documentation http://www.gvsig.com/en/products/gvsig-desktop/development''' &lt;br /&gt;
&lt;br /&gt;
==Release Procedure==&lt;br /&gt;
&lt;br /&gt;
In order to maintain a consistent level of quality, the project should follow defined release and testing processes.&lt;br /&gt;
&lt;br /&gt;
# The project follows a defined release process: '''yes: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2-1-0/release-guide'''&lt;br /&gt;
#* Which includes execution of the testing process before releasing a stable release. '''yes, there's a testing procedure available for gvSIG, which is a workshop with the cartography: http://docs.gvsig.org/plone/docusr/doctesting/interesting-links-for-testers/view'''&lt;br /&gt;
# The project follows a documented testing process. '''There's also a quick testing process for an initial test: http://downloads.gvsig.org/download/testing/testgvSIG_en.pdf '''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;This includes manual testing&amp;lt;/i&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
# Release and testing processes provide sufficient detail for an experienced programmer to follow. '''Yes, it's available at the documentation section for developers: http://www.gvsig.com/en/products/gvsig-desktop/development'''.&lt;br /&gt;
&lt;br /&gt;
= OSGeo Committees and Community =&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Board ==&lt;br /&gt;
&lt;br /&gt;
The OSGeo [[Board]] holds ultimate responsibility for all OSGeo activities. The Board requests:&lt;br /&gt;
&lt;br /&gt;
# A project provide a Project Officer as a contact point: '''Yes'''&lt;br /&gt;
#* The Project Officer should be listed at: [[Contacts#Software_Projects|Project Officer]]&lt;br /&gt;
#* This person is established when the incubation committee recommends the project for graduation&lt;br /&gt;
#* 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).&lt;br /&gt;
&lt;br /&gt;
== Marketing ==&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&lt;br /&gt;
# 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:&lt;br /&gt;
#* Application Overview '''Yes. http://live.osgeo.org/en/overview/gvsig_overview.html'''&lt;br /&gt;
#* Application Quick Start '''Yes. http://live.osgeo.org/en/quickstart/gvsig_quickstart.html'''&lt;br /&gt;
#* Logo '''Yes. http://live.osgeo.org/_images/logo-gvSIG.png'''&lt;br /&gt;
#* Graphical Image '''Yes. http://live.osgeo.org/_images/gvsig_desktop.png'''&lt;br /&gt;
# Ideally, stable version(s) of executable applications are bundled with appropriate distributions. '''Yes: OSGeo-Live.'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;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.)&amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Projects ==&lt;br /&gt;
&lt;br /&gt;
Projects do not exist in isolation; and are expected to communicate and collaborate on key issues. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;i&amp;gt;As an example the PostGIS release procedure asks that the release be checked with MapServer, GeoServer and others.&amp;lt;/i&amp;gt; gvSIG uses several libraries, like gdal or NASA World Wind, and they are reviewed and updated before releasing the gvSIG versions. &lt;br /&gt;
&lt;br /&gt;
== SAC ==&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
* A http://projectname.osgeo.org domain name. '''Yes.'''&lt;br /&gt;
&lt;br /&gt;
A project may optionally request SAC help to make use of:&lt;br /&gt;
* OSGeo issue tracker&lt;br /&gt;
* OSGeo mailing list '''Yes.'''&lt;br /&gt;
* OSGeo svn&lt;br /&gt;
* http://downloads.osgeo.org&lt;br /&gt;
&lt;br /&gt;
[[Category: Incubation]]&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=GvSIG_Incubation_Checklist&amp;diff=84581</id>
		<title>GvSIG Incubation Checklist</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=GvSIG_Incubation_Checklist&amp;diff=84581"/>
		<updated>2015-06-16T11:47:40Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Document Status =&lt;br /&gt;
&lt;br /&gt;
'''Version''': 2.0&lt;br /&gt;
&lt;br /&gt;
'''Last Updated''': June 2015.&lt;br /&gt;
&lt;br /&gt;
'''Status''': Draft&lt;br /&gt;
&lt;br /&gt;
= Purpose =&lt;br /&gt;
&lt;br /&gt;
The purpose of this checklist is to determine whether an Incubator Project produces quality products, remains true to its stated licence and is sustainable. Satisfying this checklist is a pre-requisite for graduation.&lt;br /&gt;
&lt;br /&gt;
A project should have institutionalized the processes in this list or provide justification why the process is not used.&lt;br /&gt;
&lt;br /&gt;
See also:&lt;br /&gt;
&lt;br /&gt;
* [http://www.osgeo.org/incubator/process/application.html Incubation Application Questionnaire]&lt;br /&gt;
* [http://www.osgeo.org/incubator/process/statustemplate.html Project Status Template]&lt;br /&gt;
&lt;br /&gt;
= Terms and Definitions =&lt;br /&gt;
&lt;br /&gt;
; Mentor : A member of the Incubation Committee chosen to assist a Project through the Incubation Process.&lt;br /&gt;
; Institutionalized Process : A documented process which which addresses a need and is actively in use. It typically takes months before a process becomes institutionalized. ''A more detailed definition of institutionalization is found in the [http://www.sei.cmu.edu/pub/documents/02.reports/pdf/02tr012.pdf Capability Maturity Model (CMMI)] - &amp;quot;Generic Goal 2: Institutionalize a Managed Process&amp;quot;''&lt;br /&gt;
; Open Source License : a license recognized by the [http://opensource.org Open Source Initiative]&lt;br /&gt;
&lt;br /&gt;
= Incubation Checklist =&lt;br /&gt;
&lt;br /&gt;
== Open ==&lt;br /&gt;
	 &lt;br /&gt;
The project has demonstrated that it has an open, active and healthy user and developer community:	&lt;br /&gt;
# Open: projects are expected to function in an open and public manner and include:&lt;br /&gt;
#* Open source license(s), '''yes: gvSIG is developed under GNU/GPL version 3 license'''&lt;br /&gt;
#* Open communication channels, '''yes: there are several users and developers mailing lists in different languages (http://www.gvsig.com/en/community/mailing-lists). There's also a mail address (info@gvsig.com), a phone number (0034-961110070) and a fax number (0034-901021995)'''&lt;br /&gt;
#* Open decision making process, '''yes: Public mailing list of the gvSIG Technical Steering Committee (TSC) (http://joinup.ec.europa.eu/mailman/listinfo/gvsig-desktop-tsc-pub). There's a roadmap with the decisions taken by the board of the Technical Steering Committee: https://redmine.gvsig.net/redmine/projects/gvsig-cdt-board/roadmap. A post is published after every version of gvSIG with the novelties of the next one.'''&lt;br /&gt;
# Active and healthy community: '''yes, there's an active community of users and developers from multiple countries at the world.'''&lt;br /&gt;
#* The project should have a community of developers and users who actively collaborate and support each other in a healthy way. ''' yes. Users and developers use mailing lists for collaboration and supporting. There are four main mailing lists (in Spanish and English, for developers and for users) and there are also local mailing lists (in different languages or for different areas, like Argentina, Brazil, Italy or Russia among others). Users and developers use the tracker for uploading the errors in gvSIG (https://redmine.gvsig.net/redmine/projects/gvsig-desktop/issues). There are a lot of testers at the community, and there's group of translators, who translate documentation and interface. There are developers that provide patches, new developments, and scripts (at the scripting repository: http://outreach.gvsig.org/scripts/). There's also a web portal for the gvSIG case-studies provided by the community (http://outreach.gvsig.org/case-studies).'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;Eg. collaboration on project activities such as testing, release and feature development.&amp;lt;/i&amp;gt;&lt;br /&gt;
#* Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organizations. '''yes. There are multiple developers from different organizations. The community is participating actively on the development. The commits by developer at the core, the main project, are shown in https://redmine.gvsig.net/redmine/projects/gvsig-desktop/repository/statistics. There are also different sub-projects for the different extensions with their own commits: https://redmine.gvsig.net/redmine/projects. The activity of the project every day is in: https://redmine.gvsig.net/redmine/projects/gvsig-desktop/activity. The gvSIG project is managed by the gvSIG Association, that is composed of four associate companies and more than 40 collaborating companies, as well as different public entities (governments, technical institutes...) and universities. '''&amp;lt;br/&amp;gt; &amp;lt;i&amp;gt; Eg. The project is resilient enough to sustain loss of a developer or supporting organization, 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.&amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Copyright and License ==&lt;br /&gt;
&lt;br /&gt;
We need to ensure that the project owns or otherwise has obtained the ability to release the project code by completing the following steps:&lt;br /&gt;
# All project source code is available under an Open Source license. '''Yes. All the source code of the different versions is in https://devel.gvsig.org/svn/gvsig-desktop/'''&lt;br /&gt;
# Project documentation is available under an open license, such as Creative Commons. '''Yes. The documentation is under an open license (there are workshops, tutorials and manuals). They are available in http://www.gvsig.com/. There's a Youtube channel with a lot of videos about the project too: https://www.youtube.com/user/gvsig. All the presentations of the gvSIG Conferences are available too, and the videos are published when they are recorded. There are articles, books and posters about the project compiled at the gvSIG web portal. '''&lt;br /&gt;
# 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]. '''Yes. All the information is vetted before publishing (manuals, source code, cartography...).'''&lt;br /&gt;
# The project maintains a list of all copyright holders identified in the Provenance Review Document. '''No, as all the source code is owned by the gvSIG Association. All the developers have signed the CLA (http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/como-contribuir-en-gvsig/contribuciones-y-parches-al-codigo-de-gvsig/cla-status). '''&lt;br /&gt;
# All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived. '''Yes: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/como-contribuir-en-gvsig/contribuciones-y-parches-al-codigo-de-gvsig/cla-status'''&lt;br /&gt;
&lt;br /&gt;
== Processes ==&lt;br /&gt;
&lt;br /&gt;
# The project has code under configuration management. '''Yes: the main svn is in https://devel.gvsig.org/svn/gvsig-desktop'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;Eg, subversion, git.&amp;lt;/i&amp;gt;&lt;br /&gt;
# The project uses an issue tracker and keeps the status of the issue tracker up to date. '''Yes: The main project is in https://redmine.gvsig.net/redmine/projects/gvsig-desktop/issues. gvSIG is composed of different sub-projects or extensions: https://redmine.gvsig.net/redmine/projects with their own trackers.'''&lt;br /&gt;
# The project has documented its management processes. '''Yes. There are different documents for the different areas'''&lt;br /&gt;
#* How to contribute: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/como-contribuir-en-gvsig&lt;br /&gt;
#* Commiters guide: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/guia-para-commiters-de-gvsig&lt;br /&gt;
#* Developers guide: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide&lt;br /&gt;
#* Documentation guide: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/guia-para-documentar&lt;br /&gt;
&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;This is typically done within a Developers Guide or Project Management Plan.&amp;lt;/i&amp;gt;&lt;br /&gt;
#* The project has a suitable open governance policy ensuring decisions are made, documented and adhered to in a public manner. '''Yes: there's a Technical Steering Committee (TSC) http://docs.gvsig.org/web/working-groups/organizacion. There's a roadmap with the decisions taken by the board of the Technical Steering Committee: https://redmine.gvsig.net/redmine/projects/gvsig-cdt-board/roadmap'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;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 organizations as there will be a greater variety of technical visions and the project is more resilient to a sponsor leaving.&amp;lt;/i&amp;gt;&lt;br /&gt;
#* The project uses public communication channels for decision making to maintain transparency. '''Yes: Archives of the TSC mailing list http://joinup.ec.europa.eu/mailman/listinfo/gvsig-desktop-tsc-pub'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt; E.g. archived email list(s), archived IRC channel(s), public issue tracker. The road map for the following versions of the application, with the changes, is in https://redmine.gvsig.net/redmine/projects/gvsig-desktop/roadmap. &amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Documentation ==&lt;br /&gt;
&lt;br /&gt;
# The project has user documentation: '''Yes: User documentation is available in http://www.gvsig.com/en/products/gvsig-desktop/documentation. There are workshops, tutorials, posters, articles, presentations and books in http://www.gvsig.com/en/diffusion. There's a Youtube channel with a huge quantity of videos about the project too: https://www.youtube.com/user/gvsig.'''&lt;br /&gt;
#* Including sufficient detail to guide a new user through performing the core functionality provided by the application.&lt;br /&gt;
# The project has developer documentation: '''Yes: Developer documentation http://www.gvsig.com/en/products/gvsig-desktop/development'''&lt;br /&gt;
#* Including checkout and build instructions. '''Yes: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2-1-0/trabajar-con-el-nucleo-de-gvsig/compile_gvsig'''&lt;br /&gt;
#* Including commented code, ideally published for developer use. '''Yes: maven site of main project http://devel.gvsig.org/sites/org.gvsig.desktop/2.0.17/''' &amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;Examples: javadocs for Java applications, or Sphinx documentation for Python applications.&amp;lt;/i&amp;gt;&lt;br /&gt;
#* Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project's programming conventions. '''Yes: It's available at the developer documentation http://www.gvsig.com/en/products/gvsig-desktop/development''' &lt;br /&gt;
&lt;br /&gt;
==Release Procedure==&lt;br /&gt;
&lt;br /&gt;
In order to maintain a consistent level of quality, the project should follow defined release and testing processes.&lt;br /&gt;
&lt;br /&gt;
# The project follows a defined release process: '''yes: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2-1-0/release-guide'''&lt;br /&gt;
#* Which includes execution of the testing process before releasing a stable release. '''yes, there's a testing procedure available for gvSIG, which is a workshop with the cartography: http://docs.gvsig.org/plone/docusr/doctesting/interesting-links-for-testers/view'''&lt;br /&gt;
# The project follows a documented testing process. '''There's also a quick testing process for an initial test: http://downloads.gvsig.org/download/testing/testgvSIG_en.pdf '''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;This includes manual testing&amp;lt;/i&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
# Release and testing processes provide sufficient detail for an experienced programmer to follow. '''Yes, it's available at the documentation section for developers: http://www.gvsig.com/en/products/gvsig-desktop/development'''.&lt;br /&gt;
&lt;br /&gt;
= OSGeo Committees and Community =&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Board ==&lt;br /&gt;
&lt;br /&gt;
The OSGeo [[Board]] holds ultimate responsibility for all OSGeo activities. The Board requests:&lt;br /&gt;
&lt;br /&gt;
# A project provide a Project Officer as a contact point: '''Yes'''&lt;br /&gt;
#* The Project Officer should be listed at: [[Contacts#Software_Projects|Project Officer]]&lt;br /&gt;
#* This person is established when the incubation committee recommends the project for graduation&lt;br /&gt;
#* 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).&lt;br /&gt;
&lt;br /&gt;
== Marketing ==&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&lt;br /&gt;
# 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:&lt;br /&gt;
#* Application Overview '''Yes. http://live.osgeo.org/en/overview/gvsig_overview.html'''&lt;br /&gt;
#* Application Quick Start '''Yes. http://live.osgeo.org/en/quickstart/gvsig_quickstart.html'''&lt;br /&gt;
#* Logo '''Yes. http://live.osgeo.org/_images/logo-gvSIG.png'''&lt;br /&gt;
#* Graphical Image '''Yes. http://live.osgeo.org/_images/gvsig_desktop.png'''&lt;br /&gt;
# Ideally, stable version(s) of executable applications are bundled with appropriate distributions. '''Yes: OSGeo-Live.'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;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.)&amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Projects ==&lt;br /&gt;
&lt;br /&gt;
Projects do not exist in isolation; and are expected to communicate and collaborate on key issues. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;i&amp;gt;As an example the PostGIS release procedure asks that the release be checked with MapServer, GeoServer and others.&amp;lt;/i&amp;gt; gvSIG uses several libraries, like gdal or NASA World Wind, and they are reviewed and updated before releasing the gvSIG versions. &lt;br /&gt;
&lt;br /&gt;
== SAC ==&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
* A http://projectname.osgeo.org domain name. '''Yes.'''&lt;br /&gt;
&lt;br /&gt;
A project may optionally request SAC help to make use of:&lt;br /&gt;
* OSGeo issue tracker&lt;br /&gt;
* OSGeo mailing list '''Yes.'''&lt;br /&gt;
* OSGeo svn&lt;br /&gt;
* http://downloads.osgeo.org&lt;br /&gt;
&lt;br /&gt;
[[Category: Incubation]]&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=GvSIG_Incubation_Checklist&amp;diff=84580</id>
		<title>GvSIG Incubation Checklist</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=GvSIG_Incubation_Checklist&amp;diff=84580"/>
		<updated>2015-06-16T11:46:10Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Document Status =&lt;br /&gt;
&lt;br /&gt;
'''Version''': 2.0&lt;br /&gt;
&lt;br /&gt;
'''Last Updated''': June 2015.&lt;br /&gt;
&lt;br /&gt;
'''Status''': Draft&lt;br /&gt;
&lt;br /&gt;
= Purpose =&lt;br /&gt;
&lt;br /&gt;
The purpose of this checklist is to determine whether an Incubator Project produces quality products, remains true to its stated licence and is sustainable. Satisfying this checklist is a pre-requisite for graduation.&lt;br /&gt;
&lt;br /&gt;
A project should have institutionalized the processes in this list or provide justification why the process is not used.&lt;br /&gt;
&lt;br /&gt;
See also:&lt;br /&gt;
&lt;br /&gt;
* [http://www.osgeo.org/incubator/process/application.html Incubation Application Questionnaire]&lt;br /&gt;
* [http://www.osgeo.org/incubator/process/statustemplate.html Project Status Template]&lt;br /&gt;
&lt;br /&gt;
= Terms and Definitions =&lt;br /&gt;
&lt;br /&gt;
; Mentor : A member of the Incubation Committee chosen to assist a Project through the Incubation Process.&lt;br /&gt;
; Institutionalized Process : A documented process which which addresses a need and is actively in use. It typically takes months before a process becomes institutionalized. ''A more detailed definition of institutionalization is found in the [http://www.sei.cmu.edu/pub/documents/02.reports/pdf/02tr012.pdf Capability Maturity Model (CMMI)] - &amp;quot;Generic Goal 2: Institutionalize a Managed Process&amp;quot;''&lt;br /&gt;
; Open Source License : a license recognized by the [http://opensource.org Open Source Initiative]&lt;br /&gt;
&lt;br /&gt;
= Incubation Checklist =&lt;br /&gt;
&lt;br /&gt;
== Open ==&lt;br /&gt;
	 &lt;br /&gt;
The project has demonstrated that it has an open, active and healthy user and developer community:	&lt;br /&gt;
# Open: projects are expected to function in an open and public manner and include:&lt;br /&gt;
#* Open source license(s), '''yes: gvSIG is developed under GNU/GPL version 3 license'''&lt;br /&gt;
#* Open communication channels, '''yes: there are several users and developers mailing lists in different languages (http://www.gvsig.com/en/community/mailing-lists). There's also a mail address (info@gvsig.com), a phone number (0034-961110070) and a fax number (0034-901021995)'''&lt;br /&gt;
#* Open decision making process, '''yes: Public mailing list of the gvSIG Technical Steering Committee (TSC) (http://joinup.ec.europa.eu/mailman/listinfo/gvsig-desktop-tsc-pub). There's a roadmap with the decisions taken by the board of the Technical Steering Committee: https://redmine.gvsig.net/redmine/projects/gvsig-cdt-board/roadmap. A post is published after every version of gvSIG with the novelties of the next one.'''&lt;br /&gt;
# Active and healthy community: '''yes, there's an active community of users and developers from multiple countries at the world.'''&lt;br /&gt;
#* The project should have a community of developers and users who actively collaborate and support each other in a healthy way. ''' yes. Users and developers use mailing lists for collaboration and supporting. There are four main mailing lists (in Spanish and English, for developers and for users) and there are also local mailing lists (in different languages or for different areas, like Argentina, Brazil, Italy or Russia among others). Users and developers use the tracker for uploading the errors in gvSIG (https://redmine.gvsig.net/redmine/projects/gvsig-desktop/issues). There are a lot of testers at the community, and there's group of translators, who translate documentation and interface. There are developers that provide patches, new developments, and scripts (at the scripting repository: http://outreach.gvsig.org/scripts/). There's also a web portal for the gvSIG case-studies provided by the community (http://outreach.gvsig.org/case-studies).'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;Eg. collaboration on project activities such as testing, release and feature development.&amp;lt;/i&amp;gt;&lt;br /&gt;
#* Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organizations. '''yes. There are multiple developers from different organizations. The community is participating actively on the development. The commits by developer at the core, the main project, are shown in https://redmine.gvsig.net/redmine/projects/gvsig-desktop/repository/statistics. There are also different sub-projects for the different extensions with their own commits: https://redmine.gvsig.net/redmine/projects. The activity of the project every day is in: https://redmine.gvsig.net/redmine/projects/gvsig-desktop/activity. The gvSIG project is managed by the gvSIG Association, that is composed of four associate companies and more than 40 collaborating companies, as well as different public entities (governments, technical institutes...) and universities. '''&amp;lt;br/&amp;gt; &amp;lt;i&amp;gt; Eg. The project is resilient enough to sustain loss of a developer or supporting organization, 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.&amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Copyright and License ==&lt;br /&gt;
&lt;br /&gt;
We need to ensure that the project owns or otherwise has obtained the ability to release the project code by completing the following steps:&lt;br /&gt;
# All project source code is available under an Open Source license. '''Yes. All the source code of the different versions is in https://devel.gvsig.org/svn/gvsig-desktop/'''&lt;br /&gt;
# Project documentation is available under an open license, such as Creative Commons. '''Yes. The documentation is under an open license (there are workshops, tutorials and manuals). They are available in http://www.gvsig.com/. There's a Youtube channel with a lot of videos about the project too: https://www.youtube.com/user/gvsig. All the presentations of the gvSIG Conferences are available too, and the videos are published when they are recorded. There are articles, books and posters about the project compiled at the gvSIG web portal. '''&lt;br /&gt;
# 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]. '''Yes. All the information is vetted before publishing (manuals, source code, cartography...).'''&lt;br /&gt;
# The project maintains a list of all copyright holders identified in the Provenance Review Document. '''No, as all the source code is owned by the gvSIG Association. All the developers have signed the CLA (http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/como-contribuir-en-gvsig/contribuciones-y-parches-al-codigo-de-gvsig/cla-status). '''&lt;br /&gt;
# All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived. '''Yes: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/como-contribuir-en-gvsig/contribuciones-y-parches-al-codigo-de-gvsig/cla-status'''&lt;br /&gt;
&lt;br /&gt;
== Processes ==&lt;br /&gt;
&lt;br /&gt;
# The project has code under configuration management. '''Yes: the main svn is in https://devel.gvsig.org/svn/gvsig-desktop'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;Eg, subversion, git.&amp;lt;/i&amp;gt;&lt;br /&gt;
# The project uses an issue tracker and keeps the status of the issue tracker up to date. '''Yes: The main project is in https://redmine.gvsig.net/redmine/projects/gvsig-desktop/issues. gvSIG is composed of different sub-projects or extensions: https://redmine.gvsig.net/redmine/projects with their own trackers.'''&lt;br /&gt;
# The project has documented its management processes. '''Yes. There are different documents for the different areas'''&lt;br /&gt;
#* How to contribute: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/como-contribuir-en-gvsig&lt;br /&gt;
#* Commiters guide: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/guia-para-commiters-de-gvsig&lt;br /&gt;
#* Developers guide: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide&lt;br /&gt;
#* Documentation guide: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/guia-para-documentar&lt;br /&gt;
&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;This is typically done within a Developers Guide or Project Management Plan.&amp;lt;/i&amp;gt;&lt;br /&gt;
#* The project has a suitable open governance policy ensuring decisions are made, documented and adhered to in a public manner. '''Yes: there's a Technical Steering Committee (TSC) http://docs.gvsig.org/web/working-groups/organizacion. There's a roadmap with the decisions taken by the board of the Technical Steering Committee: https://redmine.gvsig.net/redmine/projects/gvsig-cdt-board/roadmap'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;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 organizations as there will be a greater variety of technical visions and the project is more resilient to a sponsor leaving.&amp;lt;/i&amp;gt;&lt;br /&gt;
#* The project uses public communication channels for decision making to maintain transparency. '''Yes: Archives of the TSC mailing list http://joinup.ec.europa.eu/mailman/listinfo/gvsig-desktop-tsc-pub'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt; E.g. archived email list(s), archived IRC channel(s), public issue tracker. The road map for the following versions of the application, with the changes, is in https://redmine.gvsig.net/redmine/projects/gvsig-desktop/roadmap. &amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Documentation ==&lt;br /&gt;
&lt;br /&gt;
# The project has user documentation: '''Yes: User documentation is available in http://www.gvsig.com/en/products/gvsig-desktop/documentation. There are workshops, tutorials, posters, articles, presentations and books in http://www.gvsig.com/en/diffusion. There's a Youtube channel with a huge quantity of videos about the project too: https://www.youtube.com/user/gvsig.'''&lt;br /&gt;
#* Including sufficient detail to guide a new user through performing the core functionality provided by the application.&lt;br /&gt;
# The project has developer documentation: '''Yes: Developer documentation http://www.gvsig.com/en/products/gvsig-desktop/development'''&lt;br /&gt;
#* Including checkout and build instructions. '''Yes: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2-1-0/trabajar-con-el-nucleo-de-gvsig/compile_gvsig'''&lt;br /&gt;
#* Including commented code, ideally published for developer use. '''Yes: maven site of main project http://devel.gvsig.org/sites/org.gvsig.desktop/2.0.17/''' &amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;Examples: javadocs for Java applications, or Sphinx documentation for Python applications.&amp;lt;/i&amp;gt;&lt;br /&gt;
#* Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project's programming conventions. '''Yes: It's available at the developer documentation http://www.gvsig.com/en/products/gvsig-desktop/development''' &lt;br /&gt;
&lt;br /&gt;
==Release Procedure==&lt;br /&gt;
&lt;br /&gt;
In order to maintain a consistent level of quality, the project should follow defined release and testing processes.&lt;br /&gt;
&lt;br /&gt;
# The project follows a defined release process: '''yes: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2-1-0/release-guide'''&lt;br /&gt;
#* Which includes execution of the testing process before releasing a stable release. '''yes, there's a testing procedure available for gvSIG, which is a workshop with the cartography: http://docs.gvsig.org/plone/docusr/doctesting/interesting-links-for-testers/view'''&lt;br /&gt;
# The project follows a documented testing process. There's also a quick testing process for an initial test: http://downloads.gvsig.org/download/testing/testgvSIG_en.pdf &amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;This includes manual testing&amp;lt;/i&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
# Release and testing processes provide sufficient detail for an experienced programmer to follow. '''Yes, it's available at the documentation section for developers: http://www.gvsig.com/en/products/gvsig-desktop/development'''.&lt;br /&gt;
&lt;br /&gt;
= OSGeo Committees and Community =&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Board ==&lt;br /&gt;
&lt;br /&gt;
The OSGeo [[Board]] holds ultimate responsibility for all OSGeo activities. The Board requests:&lt;br /&gt;
&lt;br /&gt;
# A project provide a Project Officer as a contact point: '''Yes'''&lt;br /&gt;
#* The Project Officer should be listed at: [[Contacts#Software_Projects|Project Officer]]&lt;br /&gt;
#* This person is established when the incubation committee recommends the project for graduation&lt;br /&gt;
#* 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).&lt;br /&gt;
&lt;br /&gt;
== Marketing ==&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&lt;br /&gt;
# 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:&lt;br /&gt;
#* Application Overview '''Yes. http://live.osgeo.org/en/overview/gvsig_overview.html'''&lt;br /&gt;
#* Application Quick Start '''Yes. http://live.osgeo.org/en/quickstart/gvsig_quickstart.html'''&lt;br /&gt;
#* Logo '''Yes. http://live.osgeo.org/_images/logo-gvSIG.png'''&lt;br /&gt;
#* Graphical Image '''Yes. http://live.osgeo.org/_images/gvsig_desktop.png'''&lt;br /&gt;
# Ideally, stable version(s) of executable applications are bundled with appropriate distributions. '''Yes: OSGeo-Live.'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;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.)&amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Projects ==&lt;br /&gt;
&lt;br /&gt;
Projects do not exist in isolation; and are expected to communicate and collaborate on key issues. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;i&amp;gt;As an example the PostGIS release procedure asks that the release be checked with MapServer, GeoServer and others.&amp;lt;/i&amp;gt; gvSIG uses several libraries, like gdal or NASA World Wind, and they are reviewed and updated before releasing the gvSIG versions. &lt;br /&gt;
&lt;br /&gt;
== SAC ==&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
* A http://projectname.osgeo.org domain name. '''Yes.'''&lt;br /&gt;
&lt;br /&gt;
A project may optionally request SAC help to make use of:&lt;br /&gt;
* OSGeo issue tracker&lt;br /&gt;
* OSGeo mailing list '''Yes.'''&lt;br /&gt;
* OSGeo svn&lt;br /&gt;
* http://downloads.osgeo.org&lt;br /&gt;
&lt;br /&gt;
[[Category: Incubation]]&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=GvSIG_Incubation_Checklist&amp;diff=84579</id>
		<title>GvSIG Incubation Checklist</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=GvSIG_Incubation_Checklist&amp;diff=84579"/>
		<updated>2015-06-16T11:17:01Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Document Status =&lt;br /&gt;
&lt;br /&gt;
'''Version''': 2.0&lt;br /&gt;
&lt;br /&gt;
'''Last Updated''': June 2015.&lt;br /&gt;
&lt;br /&gt;
'''Status''': Draft&lt;br /&gt;
&lt;br /&gt;
= Purpose =&lt;br /&gt;
&lt;br /&gt;
The purpose of this checklist is to determine whether an Incubator Project produces quality products, remains true to its stated licence and is sustainable. Satisfying this checklist is a pre-requisite for graduation.&lt;br /&gt;
&lt;br /&gt;
A project should have institutionalized the processes in this list or provide justification why the process is not used.&lt;br /&gt;
&lt;br /&gt;
See also:&lt;br /&gt;
&lt;br /&gt;
* [http://www.osgeo.org/incubator/process/application.html Incubation Application Questionnaire]&lt;br /&gt;
* [http://www.osgeo.org/incubator/process/statustemplate.html Project Status Template]&lt;br /&gt;
&lt;br /&gt;
= Terms and Definitions =&lt;br /&gt;
&lt;br /&gt;
; Mentor : A member of the Incubation Committee chosen to assist a Project through the Incubation Process.&lt;br /&gt;
; Institutionalized Process : A documented process which which addresses a need and is actively in use. It typically takes months before a process becomes institutionalized. ''A more detailed definition of institutionalization is found in the [http://www.sei.cmu.edu/pub/documents/02.reports/pdf/02tr012.pdf Capability Maturity Model (CMMI)] - &amp;quot;Generic Goal 2: Institutionalize a Managed Process&amp;quot;''&lt;br /&gt;
; Open Source License : a license recognized by the [http://opensource.org Open Source Initiative]&lt;br /&gt;
&lt;br /&gt;
= Incubation Checklist =&lt;br /&gt;
&lt;br /&gt;
== Open ==&lt;br /&gt;
	 &lt;br /&gt;
The project has demonstrated that it has an open, active and healthy user and developer community:	&lt;br /&gt;
# Open: projects are expected to function in an open and public manner and include:&lt;br /&gt;
#* Open source license(s), '''yes: gvSIG is developed under GNU/GPL version 3 license'''&lt;br /&gt;
#* Open communication channels, '''yes: there are several users and developers mailing lists in different languages (http://www.gvsig.com/en/community/mailing-lists). There's also a mail address (info@gvsig.com), a phone number (0034-961110070) and a fax number (0034-901021995)'''&lt;br /&gt;
#* Open decision making process, '''yes: Public mailing list of the gvSIG Technical Steering Committee (TSC) (http://joinup.ec.europa.eu/mailman/listinfo/gvsig-desktop-tsc-pub). There's a roadmap with the decisions taken by the board of the Technical Steering Committee: https://redmine.gvsig.net/redmine/projects/gvsig-cdt-board/roadmap. A post is published after every version of gvSIG with the novelties of the next one.'''&lt;br /&gt;
# Active and healthy community: '''yes, there's an active community of users and developers from multiple countries at the world.'''&lt;br /&gt;
#* The project should have a community of developers and users who actively collaborate and support each other in a healthy way. ''' yes. Users and developers use mailing lists for collaboration and supporting. There are four main mailing lists (in Spanish and English, for developers and for users) and there are also local mailing lists (in different languages or for different areas, like Argentina, Brazil, Italy or Russia among others). Users and developers use the tracker for uploading the errors in gvSIG (https://redmine.gvsig.net/redmine/projects/gvsig-desktop/issues). There are a lot of testers at the community, and there's group of translators, who translate documentation and interface. There are developers that provide patches, new developments, and scripts (at the scripting repository: http://outreach.gvsig.org/scripts/). There's also a web portal for the gvSIG case-studies provided by the community (http://outreach.gvsig.org/case-studies).'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;Eg. collaboration on project activities such as testing, release and feature development.&amp;lt;/i&amp;gt;&lt;br /&gt;
#* Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organizations. '''yes. There are multiple developers from different organizations. The community is participating actively on the development. The commits by developer at the core, the main project, are shown in https://redmine.gvsig.net/redmine/projects/gvsig-desktop/repository/statistics. There are also different sub-projects for the different extensions with their own commits: https://redmine.gvsig.net/redmine/projects. The activity of the project every day is in: https://redmine.gvsig.net/redmine/projects/gvsig-desktop/activity. The gvSIG project is managed by the gvSIG Association, that is composed of four associate companies and more than 40 collaborating companies, as well as different public entities (governments, technical institutes...) and universities. '''&amp;lt;br/&amp;gt; &amp;lt;i&amp;gt; Eg. The project is resilient enough to sustain loss of a developer or supporting organization, 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.&amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Copyright and License ==&lt;br /&gt;
&lt;br /&gt;
We need to ensure that the project owns or otherwise has obtained the ability to release the project code by completing the following steps:&lt;br /&gt;
# All project source code is available under an Open Source license. '''Yes. All the source code of the different versions is in https://devel.gvsig.org/svn/gvsig-desktop/'''&lt;br /&gt;
# Project documentation is available under an open license, such as Creative Commons. '''Yes. The documentation is under an open license (there are workshops, tutorials and manuals). They are available in http://www.gvsig.com/. There's a Youtube channel with a lot of videos about the project too: https://www.youtube.com/user/gvsig. All the presentations of the gvSIG Conferences are available too, and the videos are published when they are recorded. There are articles, books and posters about the project compiled at the gvSIG web portal. '''&lt;br /&gt;
# 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]. '''Yes. All the information is vetted before publishing (manuals, source code, cartography...).'''&lt;br /&gt;
# The project maintains a list of all copyright holders identified in the Provenance Review Document. '''No, as all the source code is owned by the gvSIG Association. All the developers have signed the CLA (http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/como-contribuir-en-gvsig/contribuciones-y-parches-al-codigo-de-gvsig/cla-status). '''&lt;br /&gt;
# All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived. '''Yes: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/como-contribuir-en-gvsig/contribuciones-y-parches-al-codigo-de-gvsig/cla-status'''&lt;br /&gt;
&lt;br /&gt;
== Processes ==&lt;br /&gt;
&lt;br /&gt;
# The project has code under configuration management. '''Yes: the main svn is in https://devel.gvsig.org/svn/gvsig-desktop'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;Eg, subversion, git.&amp;lt;/i&amp;gt;&lt;br /&gt;
# The project uses an issue tracker and keeps the status of the issue tracker up to date. '''Yes: The main project is in https://redmine.gvsig.net/redmine/projects/gvsig-desktop/issues. gvSIG is composed of different sub-projects or extensions: https://redmine.gvsig.net/redmine/projects with their own trackers.'''&lt;br /&gt;
# The project has documented its management processes. '''Yes. There are different documents for the different areas'''&lt;br /&gt;
#* How to contribute: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/como-contribuir-en-gvsig&lt;br /&gt;
#* Commiters guide: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/guia-para-commiters-de-gvsig&lt;br /&gt;
#* Developers guide: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide&lt;br /&gt;
#* Documentation guide: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/guia-para-documentar&lt;br /&gt;
&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;This is typically done within a Developers Guide or Project Management Plan.&amp;lt;/i&amp;gt;&lt;br /&gt;
#* The project has a suitable open governance policy ensuring decisions are made, documented and adhered to in a public manner. '''Yes: there's a Technical Steering Committee (TSC) http://docs.gvsig.org/web/working-groups/organizacion. There's a roadmap with the decisions taken by the board of the Technical Steering Committee: https://redmine.gvsig.net/redmine/projects/gvsig-cdt-board/roadmap'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;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 organizations as there will be a greater variety of technical visions and the project is more resilient to a sponsor leaving.&amp;lt;/i&amp;gt;&lt;br /&gt;
#* The project uses public communication channels for decision making to maintain transparency. '''Yes: Archives of the TSC mailing list http://joinup.ec.europa.eu/mailman/listinfo/gvsig-desktop-tsc-pub'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt; E.g. archived email list(s), archived IRC channel(s), public issue tracker. The road map for the following versions of the application, with the changes, is in https://redmine.gvsig.net/redmine/projects/gvsig-desktop/roadmap. &amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Documentation ==&lt;br /&gt;
&lt;br /&gt;
# The project has user documentation: '''Yes: User documentation is available in http://www.gvsig.com/en/products/gvsig-desktop/documentation. There are workshops, tutorials, posters, articles, presentations and books in http://www.gvsig.com/en/diffusion. There's a Youtube channel with a huge quantity of videos about the project too: https://www.youtube.com/user/gvsig.'''&lt;br /&gt;
#* Including sufficient detail to guide a new user through performing the core functionality provided by the application.&lt;br /&gt;
# The project has developer documentation: '''Yes: Developer documentation http://www.gvsig.com/en/products/gvsig-desktop/development'''&lt;br /&gt;
#* Including checkout and build instructions. '''Yes: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2-1-0/trabajar-con-el-nucleo-de-gvsig/compile_gvsig'''&lt;br /&gt;
#* Including commented code, ideally published for developer use. '''Yes: maven site of main project http://devel.gvsig.org/sites/org.gvsig.desktop/2.0.17/''' &amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;Examples: javadocs for Java applications, or Sphinx documentation for Python applications.&amp;lt;/i&amp;gt;&lt;br /&gt;
#* Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project's programming conventions. '''Yes: It's available at the developer documentation http://www.gvsig.com/en/products/gvsig-desktop/development''' &lt;br /&gt;
&lt;br /&gt;
==Release Procedure==&lt;br /&gt;
&lt;br /&gt;
In order to maintain a consistent level of quality, the project should follow defined release and testing processes.&lt;br /&gt;
&lt;br /&gt;
# The project follows a defined release process: '''yes: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2-1-0/release-guide'''&lt;br /&gt;
#* Which includes execution of the testing process before releasing a stable release. '''yes, there's a testing procedure&lt;br /&gt;
# The project follows a documented testing process. http://downloads.gvsig.org/download/testing/testgvSIG_en.pdf &amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;This includes manual testing&amp;lt;/i&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
# Release and testing processes provide sufficient detail for an experienced programmer to follow. '''Yes, it's available at the documentation section for developers: http://www.gvsig.com/en/products/gvsig-desktop/development'''.&lt;br /&gt;
&lt;br /&gt;
= OSGeo Committees and Community =&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Board ==&lt;br /&gt;
&lt;br /&gt;
The OSGeo [[Board]] holds ultimate responsibility for all OSGeo activities. The Board requests:&lt;br /&gt;
&lt;br /&gt;
# A project provide a Project Officer as a contact point: '''Yes'''&lt;br /&gt;
#* The Project Officer should be listed at: [[Contacts#Software_Projects|Project Officer]]&lt;br /&gt;
#* This person is established when the incubation committee recommends the project for graduation&lt;br /&gt;
#* 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).&lt;br /&gt;
&lt;br /&gt;
== Marketing ==&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&lt;br /&gt;
# 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:&lt;br /&gt;
#* Application Overview '''Yes.'''&lt;br /&gt;
#* Application Quick Start '''Yes.'''&lt;br /&gt;
#* Logo '''Yes.'''&lt;br /&gt;
#* Graphical Image '''Yes.'''&lt;br /&gt;
# Ideally, stable version(s) of executable applications are bundled with appropriate distributions. '''Yes: OSGeo-Live.'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;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.)&amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Projects ==&lt;br /&gt;
&lt;br /&gt;
Projects do not exist in isolation; and are expected to communicate and collaborate on key issues. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;i&amp;gt;As an example the PostGIS release procedure asks that the release be checked with MapServer, GeoServer and others.&amp;lt;/i&amp;gt; Not currently.&lt;br /&gt;
&lt;br /&gt;
== SAC ==&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
* A http://projectname.osgeo.org domain name. '''Yes.'''&lt;br /&gt;
&lt;br /&gt;
A project may optionally request SAC help to make use of:&lt;br /&gt;
* OSGeo issue tracker&lt;br /&gt;
* OSGeo mailing list '''Yes.'''&lt;br /&gt;
* OSGeo svn&lt;br /&gt;
* http://downloads.osgeo.org&lt;br /&gt;
&lt;br /&gt;
[[Category: Incubation]]&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=GvSIG_Incubation_Checklist&amp;diff=84576</id>
		<title>GvSIG Incubation Checklist</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=GvSIG_Incubation_Checklist&amp;diff=84576"/>
		<updated>2015-06-16T10:16:47Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Document Status =&lt;br /&gt;
&lt;br /&gt;
'''Version''': 2.0&lt;br /&gt;
&lt;br /&gt;
'''Last Updated''': June 2015.&lt;br /&gt;
&lt;br /&gt;
'''Status''': Draft&lt;br /&gt;
&lt;br /&gt;
= Purpose =&lt;br /&gt;
&lt;br /&gt;
The purpose of this checklist is to determine whether an Incubator Project produces quality products, remains true to its stated licence and is sustainable. Satisfying this checklist is a pre-requisite for graduation.&lt;br /&gt;
&lt;br /&gt;
A project should have institutionalized the processes in this list or provide justification why the process is not used.&lt;br /&gt;
&lt;br /&gt;
See also:&lt;br /&gt;
&lt;br /&gt;
* [http://www.osgeo.org/incubator/process/application.html Incubation Application Questionnaire]&lt;br /&gt;
* [http://www.osgeo.org/incubator/process/statustemplate.html Project Status Template]&lt;br /&gt;
&lt;br /&gt;
= Terms and Definitions =&lt;br /&gt;
&lt;br /&gt;
; Mentor : A member of the Incubation Committee chosen to assist a Project through the Incubation Process.&lt;br /&gt;
; Institutionalized Process : A documented process which which addresses a need and is actively in use. It typically takes months before a process becomes institutionalized. ''A more detailed definition of institutionalization is found in the [http://www.sei.cmu.edu/pub/documents/02.reports/pdf/02tr012.pdf Capability Maturity Model (CMMI)] - &amp;quot;Generic Goal 2: Institutionalize a Managed Process&amp;quot;''&lt;br /&gt;
; Open Source License : a license recognized by the [http://opensource.org Open Source Initiative]&lt;br /&gt;
&lt;br /&gt;
= Incubation Checklist =&lt;br /&gt;
&lt;br /&gt;
== Open ==&lt;br /&gt;
	 &lt;br /&gt;
The project has demonstrated that it has an open, active and healthy user and developer community:	&lt;br /&gt;
# Open: projects are expected to function in an open and public manner and include:&lt;br /&gt;
#* Open source license(s), '''yes: gvSIG is developed under GNU/GPL version 3 license'''&lt;br /&gt;
#* Open communication channels, '''yes: there are several users and developers mailing lists in different languages (http://www.gvsig.com/en/community/mailing-lists)'''&lt;br /&gt;
#* Open decision making process, '''yes: Public mailing list of the gvSIG Technical Steering Committee (TSC) (http://joinup.ec.europa.eu/mailman/listinfo/gvsig-desktop-tsc-pub)'''&lt;br /&gt;
# Active and healthy community: '''yes, there's an active community of users and developers from multiple countries at the world.'''&lt;br /&gt;
#* The project should have a community of developers and users who actively collaborate and support each other in a healthy way. ''' yes. Users and developers use mailing lists for collaboration and supporting. There are four main mailing lists (in Spanish and English, for developers and for users) and there are also local mailing lists (in different languages or for different areas, like Argentina, Brazil, Italy or Russia among others). Users and developers use the bugtracker for uploading the errors in gvSIG (https://redmine.gvsig.net/redmine/projects/gvsig-desktop/issues). There are a lot of testers at the community, and there's group of translators, who translate documentation and interface. There are developers that provide patches, new developments, and scripts (at the scripting repository: http://outreach.gvsig.org/scripts/). There's also a web portal for the gvSIG case-studies provided by the community (http://outreach.gvsig.org/case-studies).'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;Eg. collaboration on project activities such as testing, release and feature development.&amp;lt;/i&amp;gt;&lt;br /&gt;
#* Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organizations. '''yes. There are multiple developers from different organizations. The community is participating actively on the development. The commits by developer at the core, the main project, are shown in https://redmine.gvsig.net/redmine/projects/gvsig-desktop/repository/statistics. There are also different sub-projects for the different extensions with their own commits: https://redmine.gvsig.net/redmine/projects. The activity of the project every day is in: https://redmine.gvsig.net/redmine/projects/gvsig-desktop/activity. The gvSIG project is managed by the gvSIG Association, that is composed of four associate companies and more than 40 collaborating companies, as well as different public entities (governments, technical institutes...) and universities. '''&amp;lt;br/&amp;gt; &amp;lt;i&amp;gt; Eg. The project is resilient enough to sustain loss of a developer or supporting organization, 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.&amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Copyright and License ==&lt;br /&gt;
&lt;br /&gt;
We need to ensure that the project owns or otherwise has obtained the ability to release the project code by completing the following steps:&lt;br /&gt;
# All project source code is available under an Open Source license. '''Yes. All the source code of the different versions is in https://devel.gvsig.org/svn/gvsig-desktop/'''&lt;br /&gt;
# Project documentation is available under an open license, such as Creative Commons. '''Yes. The documentation is under an open license (there are workshops, tutorials and manuals). They are available in http://www.gvsig.com/. There's a Youtube channel with a lot of videos about the project too: https://www.youtube.com/user/gvsig. All the presentations of the gvSIG Conferences are available too, and the videos are published when they are recorded. There are articles, books and posters about the project compiled at the gvSIG web portal. '''&lt;br /&gt;
# 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]. '''Yes. All the information is vetted before publishing (manuals, source code, cartography...).'''&lt;br /&gt;
# The project maintains a list of all copyright holders identified in the Provenance Review Document. '''No, as all the source code is owned by the gvSIG Association. All the developers have signed the CLA (http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/como-contribuir-en-gvsig/contribuciones-y-parches-al-codigo-de-gvsig/cla-status). '''&lt;br /&gt;
# All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived. '''Yes: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/como-contribuir-en-gvsig/contribuciones-y-parches-al-codigo-de-gvsig/cla-status'''&lt;br /&gt;
&lt;br /&gt;
== Processes ==&lt;br /&gt;
&lt;br /&gt;
# The project has code under configuration management. '''Yes: main svn https://devel.gvsig.org/svn/gvsig-desktop'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;Eg, subversion, git.&amp;lt;/i&amp;gt;&lt;br /&gt;
# The project uses an issue tracker and keeps the status of the issue tracker up to date. '''Yes: The main project is in https://redmine.gvsig.net/redmine/projects/gvsig-desktop/issues. gvSIG is composed of different sub-projects or extensions: https://redmine.gvsig.net/redmine/projects with their own tracker.'''&lt;br /&gt;
# The project has documented its management processes. '''Yes. There are different documents for the different areas'''&lt;br /&gt;
#* How to contribute: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/como-contribuir-en-gvsig&lt;br /&gt;
#* Commiters guide: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/guia-para-commiters-de-gvsig&lt;br /&gt;
#* Developers guide: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide&lt;br /&gt;
#* Documentation guide: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/guia-para-documentar&lt;br /&gt;
&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;This is typically done within a Developers Guide or Project Management Plan.&amp;lt;/i&amp;gt;&lt;br /&gt;
#* The project has a suitable open governance policy ensuring decisions are made, documented and adhered to in a public manner. '''Yes: TSC http://docs.gvsig.org/web/working-groups/organizacion'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;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 organizations as there will be a greater variety of technical visions and the project is more resilient to a sponsor leaving.&amp;lt;/i&amp;gt;&lt;br /&gt;
#* The project uses public communication channels for decision making to maintain transparency. '''Yes: Archives of the TSC mailing list http://joinup.ec.europa.eu/mailman/listinfo/gvsig-desktop-tsc-pub'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt; E.g. archived email list(s), archived IRC channel(s), public issue tracker. The road map for the following versions of the application, with the changes, is in https://redmine.gvsig.net/redmine/projects/gvsig-desktop/roadmap. &amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Documentation ==&lt;br /&gt;
&lt;br /&gt;
# The project has user documentation: '''Yes: User documentation is available in http://www.gvsig.com/en/products/gvsig-desktop/documentation. There are workshops, tutorials, posters, articles, presentations and books in http://www.gvsig.com/en/diffusion. There's a Youtube channel with a huge quantity of videos about the project too: https://www.youtube.com/user/gvsig.'''&lt;br /&gt;
#* Including sufficient detail to guide a new user through performing the core functionality provided by the application.&lt;br /&gt;
# The project has developer documentation: '''Yes: Developer documentation http://www.gvsig.com/en/products/gvsig-desktop/development'''&lt;br /&gt;
#* Including checkout and build instructions. '''Yes: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2-1-0/trabajar-con-el-nucleo-de-gvsig/compile_gvsig'''&lt;br /&gt;
#* Including commented code, ideally published for developer use. '''Yes: maven site of main project http://devel.gvsig.org/sites/org.gvsig.desktop/2.0.17/''' &amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;Examples: javadocs for Java applications, or Sphinx documentation for Python applications.&amp;lt;/i&amp;gt;&lt;br /&gt;
#* Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project's programming conventions. &lt;br /&gt;
&lt;br /&gt;
==Release Procedure==&lt;br /&gt;
&lt;br /&gt;
In order to maintain a consistent level of quality, the project should follow defined release and testing processes.&lt;br /&gt;
&lt;br /&gt;
# The project follows a defined release process: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2-1-0/release-guide&lt;br /&gt;
#* Which includes execution of the testing process before releasing a stable release. &lt;br /&gt;
# The project follows a documented testing process. http://downloads.gvsig.org/download/testing/testgvSIG_en.pdf &amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;This includes manual testing&amp;lt;/i&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
# Release and testing processes provide sufficient detail for an experienced programmer to follow. '''Yes, it's available at the documentation section for developers: http://www.gvsig.com/en/products/gvsig-desktop/development'''.&lt;br /&gt;
&lt;br /&gt;
= OSGeo Committees and Community =&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Board ==&lt;br /&gt;
&lt;br /&gt;
The OSGeo [[Board]] holds ultimate responsibility for all OSGeo activities. The Board requests:&lt;br /&gt;
&lt;br /&gt;
# A project provide a Project Officer as a contact point: '''Yes'''&lt;br /&gt;
#* The Project Officer should be listed at: [[Contacts#Software_Projects|Project Officer]]&lt;br /&gt;
#* This person is established when the incubation committee recommends the project for graduation&lt;br /&gt;
#* 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).&lt;br /&gt;
&lt;br /&gt;
== Marketing ==&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&lt;br /&gt;
# 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:&lt;br /&gt;
#* Application Overview '''Yes.'''&lt;br /&gt;
#* Application Quick Start '''Yes.'''&lt;br /&gt;
#* Logo '''Yes.'''&lt;br /&gt;
#* Graphical Image '''Yes.'''&lt;br /&gt;
# Ideally, stable version(s) of executable applications are bundled with appropriate distributions. '''Yes: OSGeo-Live.'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;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.)&amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Projects ==&lt;br /&gt;
&lt;br /&gt;
Projects do not exist in isolation; and are expected to communicate and collaborate on key issues. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;i&amp;gt;As an example the PostGIS release procedure asks that the release be checked with MapServer, GeoServer and others.&amp;lt;/i&amp;gt; Not currently.&lt;br /&gt;
&lt;br /&gt;
== SAC ==&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
* A http://projectname.osgeo.org domain name. '''Yes.'''&lt;br /&gt;
&lt;br /&gt;
A project may optionally request SAC help to make use of:&lt;br /&gt;
* OSGeo issue tracker&lt;br /&gt;
* OSGeo mailing list '''Yes.'''&lt;br /&gt;
* OSGeo svn&lt;br /&gt;
* http://downloads.osgeo.org&lt;br /&gt;
&lt;br /&gt;
[[Category: Incubation]]&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=GvSIG_Incubation_Checklist&amp;diff=84567</id>
		<title>GvSIG Incubation Checklist</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=GvSIG_Incubation_Checklist&amp;diff=84567"/>
		<updated>2015-06-15T12:03:20Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Document Status =&lt;br /&gt;
&lt;br /&gt;
'''Version''': 2.0&lt;br /&gt;
&lt;br /&gt;
'''Last Updated''': June 2015.&lt;br /&gt;
&lt;br /&gt;
'''Status''': Draft&lt;br /&gt;
&lt;br /&gt;
= Purpose =&lt;br /&gt;
&lt;br /&gt;
The purpose of this checklist is to determine whether an Incubator Project produces quality products, remains true to its stated licence and is sustainable. Satisfying this checklist is a pre-requisite for graduation.&lt;br /&gt;
&lt;br /&gt;
A project should have institutionalized the processes in this list or provide justification why the process is not used.&lt;br /&gt;
&lt;br /&gt;
See also:&lt;br /&gt;
&lt;br /&gt;
* [http://www.osgeo.org/incubator/process/application.html Incubation Application Questionnaire]&lt;br /&gt;
* [http://www.osgeo.org/incubator/process/statustemplate.html Project Status Template]&lt;br /&gt;
&lt;br /&gt;
= Terms and Definitions =&lt;br /&gt;
&lt;br /&gt;
; Mentor : A member of the Incubation Committee chosen to assist a Project through the Incubation Process.&lt;br /&gt;
; Institutionalized Process : A documented process which which addresses a need and is actively in use. It typically takes months before a process becomes institutionalized. ''A more detailed definition of institutionalization is found in the [http://www.sei.cmu.edu/pub/documents/02.reports/pdf/02tr012.pdf Capability Maturity Model (CMMI)] - &amp;quot;Generic Goal 2: Institutionalize a Managed Process&amp;quot;''&lt;br /&gt;
; Open Source License : a license recognized by the [http://opensource.org Open Source Initiative]&lt;br /&gt;
&lt;br /&gt;
= Incubation Checklist =&lt;br /&gt;
&lt;br /&gt;
== Open ==&lt;br /&gt;
	 &lt;br /&gt;
The project has demonstrated that it has an open, active and healthy user and developer community:	&lt;br /&gt;
# Open: projects are expected to function in an open and public manner and include:&lt;br /&gt;
#* Open source license(s), '''yes: GNU/GPL version 3'''&lt;br /&gt;
#* Open communication channels, '''yes: users and developers mailing lists (http://www.gvsig.com/en/community/mailing-lists)'''&lt;br /&gt;
#* Open decision making process, '''yes: Public mailing list of the gvSIG Technical Steering Committee (TSC) (http://joinup.ec.europa.eu/mailman/listinfo/gvsig-desktop-tsc-pub)'''&lt;br /&gt;
# Active and healthy community: '''yes'''&lt;br /&gt;
#* The project should have a community of developers and users who actively collaborate and support each other in a healthy way. ''' yes. Users and developers use mailing lists for collaboration and supporting. There are some main mailing lists (in Spanish and English) and there are also local ones (in different languages). Users and developers use the bugtracker for uploading the errors in gvSIG. There's a group of testers, and another group of translators, who translate documentation and the interface.'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;Eg. collaboration on project activities such as testing, release and feature development.&amp;lt;/i&amp;gt;&lt;br /&gt;
#* Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organizations. '''yes. There are multiple developers from different organizations. The community is participating on the development. The project is managed by the gvSIG Association, that is composed of four associate companies and more than 40 collaborating companies, as well as different public entities (governments, technical institutes...) and universities. The activity of the project every day is at the management web portal: https://redmine.gvsig.net/redmine/projects/gvsig-desktop/activity. '''&amp;lt;br/&amp;gt; &amp;lt;i&amp;gt; Eg. The project is resilient enough to sustain loss of a developer or supporting organization, 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.&amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Copyright and License ==&lt;br /&gt;
&lt;br /&gt;
We need to ensure that the project owns or otherwise has obtained the ability to release the project code by completing the following steps:&lt;br /&gt;
# All project source code is available under an Open Source license. '''Yes. All the source code of the different versions is in https://devel.gvsig.org/svn/gvsig-desktop/'''&lt;br /&gt;
# Project documentation is available under an open license, such as Creative Commons. '''Yes. All the documentation is under an open license (tutorials, manuals, presentations... They are available in http://www.gvsig.com/'''&lt;br /&gt;
# 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]. '''Yes. All the information is vetted before publishing (manuals, source code, cartography...).'''&lt;br /&gt;
# The project maintains a list of all copyright holders identified in the Provenance Review Document. '''No, as all the source code is owned by the gvSIG Association.'''&lt;br /&gt;
# All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived. '''Yes: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/como-contribuir-en-gvsig/contribuciones-y-parches-al-codigo-de-gvsig/cla-status'''&lt;br /&gt;
&lt;br /&gt;
== Processes ==&lt;br /&gt;
&lt;br /&gt;
# The project has code under configuration management. '''Yes: main svn https://devel.gvsig.org/svn/gvsig-desktop'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;Eg, subversion, git.&amp;lt;/i&amp;gt;&lt;br /&gt;
# The project uses an issue tracker and keeps the status of the issue tracker up to date. '''Yes: https://redmine.gvsig.net/redmine/projects/gvsig-desktop/issues'''&lt;br /&gt;
# The project has documented its management processes. '''Yes.'''&lt;br /&gt;
#* How to contribute: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/como-contribuir-en-gvsig&lt;br /&gt;
#* Commiters guide: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/guia-para-commiters-de-gvsig&lt;br /&gt;
#* Developers guide: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide&lt;br /&gt;
#* Documentation guide: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/guia-para-documentar&lt;br /&gt;
&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;This is typically done within a Developers Guide or Project Management Plan.&amp;lt;/i&amp;gt;&lt;br /&gt;
#* The project has a suitable open governance policy ensuring decisions are made, documented and adhered to in a public manner. '''Yes: TSC http://docs.gvsig.org/web/working-groups/organizacion'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;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 organizations as there will be a greater variety of technical visions and the project is more resilient to a sponsor leaving.&amp;lt;/i&amp;gt;&lt;br /&gt;
#* The project uses public communication channels for decision making to maintain transparency. '''Yes: Archives of the TSC mailing list http://joinup.ec.europa.eu/mailman/listinfo/gvsig-desktop-tsc-pub'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt; E.g. archived email list(s), archived IRC channel(s), public issue tracker.&amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Documentation ==&lt;br /&gt;
&lt;br /&gt;
# The project has user documentation: '''Yes: User documentation http://www.gvsig.com/en/products/gvsig-desktop/documentation'''&lt;br /&gt;
#* Including sufficient detail to guide a new user through performing the core functionality provided by the application.&lt;br /&gt;
# The project has developer documentation: '''Yes: Developer documentation http://www.gvsig.com/en/products/gvsig-desktop/development'''&lt;br /&gt;
#* Including checkout and build instructions. '''Yes: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2-1-0/trabajar-con-el-nucleo-de-gvsig/compile_gvsig'''&lt;br /&gt;
#* Including commented code, ideally published for developer use. '''Yes: maven site of main project http://devel.gvsig.org/sites/org.gvsig.desktop/2.0.17/''' &amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;Examples: javadocs for Java applications, or Sphinx documentation for Python applications.&amp;lt;/i&amp;gt;&lt;br /&gt;
#* Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project's programming conventions.&lt;br /&gt;
&lt;br /&gt;
==Release Procedure==&lt;br /&gt;
&lt;br /&gt;
In order to maintain a consistent level of quality, the project should follow defined release and testing processes.&lt;br /&gt;
&lt;br /&gt;
# The project follows a defined release process: http://docs.gvsig.org/web/projects/gvsig-desktop/docs/devel/gvsig-devel-guide/2-1-0/release-guide&lt;br /&gt;
#* Which includes execution of the testing process before releasing a stable release. &lt;br /&gt;
# The project follows a documented testing process. http://downloads.gvsig.org/download/testing/testgvSIG_en.pdf &amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;This includes manual testing&amp;lt;/i&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
# Release and testing processes provide sufficient detail for an experienced programmer to follow. '''Yes'''.&lt;br /&gt;
&lt;br /&gt;
= OSGeo Committees and Community =&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Board ==&lt;br /&gt;
&lt;br /&gt;
The OSGeo [[Board]] holds ultimate responsibility for all OSGeo activities. The Board requests:&lt;br /&gt;
&lt;br /&gt;
# A project provide a Project Officer as a contact point: '''Yes'''&lt;br /&gt;
#* The Project Officer should be listed at: [[Contacts#Software_Projects|Project Officer]]&lt;br /&gt;
#* This person is established when the incubation committee recommends the project for graduation&lt;br /&gt;
#* 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).&lt;br /&gt;
&lt;br /&gt;
== Marketing ==&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&lt;br /&gt;
# 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:&lt;br /&gt;
#* Application Overview '''Yes.'''&lt;br /&gt;
#* Application Quick Start '''Yes.'''&lt;br /&gt;
#* Logo '''Yes.'''&lt;br /&gt;
#* Graphical Image '''Yes.'''&lt;br /&gt;
# Ideally, stable version(s) of executable applications are bundled with appropriate distributions. '''Yes: OSGeo-Live.'''&amp;lt;br/&amp;gt;&amp;lt;i&amp;gt;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.)&amp;lt;/i&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Projects ==&lt;br /&gt;
&lt;br /&gt;
Projects do not exist in isolation; and are expected to communicate and collaborate on key issues. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;i&amp;gt;As an example the PostGIS release procedure asks that the release be checked with MapServer, GeoServer and others.&amp;lt;/i&amp;gt; Not currently.&lt;br /&gt;
&lt;br /&gt;
== SAC ==&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
* A http://projectname.osgeo.org domain name. '''Yes.'''&lt;br /&gt;
&lt;br /&gt;
A project may optionally request SAC help to make use of:&lt;br /&gt;
* OSGeo issue tracker&lt;br /&gt;
* OSGeo mailing list '''Yes.'''&lt;br /&gt;
* OSGeo svn&lt;br /&gt;
* http://downloads.osgeo.org&lt;br /&gt;
&lt;br /&gt;
[[Category: Incubation]]&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=GvSIG_GSoC_2015_Ideas&amp;diff=83025</id>
		<title>GvSIG GSoC 2015 Ideas</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=GvSIG_GSoC_2015_Ideas&amp;diff=83025"/>
		<updated>2015-03-25T13:18:19Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Use this page to jot down and develop any good idea for the [[Google Summer of Code 2015]] program with gvSIG project. Please, use the gvSIG mailing lists for discussion and check [[Google Summer of Code 2014]] [[GvSIG GSoC 2013 Ideas|2013]], [[GvSIG GSoC 2012 Ideas|2012]], [[GvSIG GSoC 2011 Ideas|2011]], [[GvSIG GSoC 2010 Ideas|2010]], [[GvSIG GSoC 2009 Ideas|2009]] ideas pages for examples or reference.&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Add OpenCL support with Aparapi for Geoprocessing in gvSIG desktop ==&lt;br /&gt;
&lt;br /&gt;
* '''Product''': gvSIG Desktop&lt;br /&gt;
* '''Possible mentor''': If applicable&lt;br /&gt;
* '''Possible student''': Anish Chandran&lt;br /&gt;
&lt;br /&gt;
[https://code.google.com/p/aparapi/ Aparapi] is a library which allows Java developers to take advantage of the compute power of GPU and APU devices by executing data parallel code fragments on the GPU rather than being confined to the local CPU. It does this by converting Java bytecode to OpenCL at runtime and executing on the GPU, if for any reason Aparapi can't execute on the GPU it will execute in a Java thread pool.&lt;br /&gt;
&lt;br /&gt;
Large amounts of geographic data-processing might be involved in the execution of a geoprocess. And many geoprocessing algorithms are suitable to be converted to parallel code, allowing for much better execution performance and capacity.&lt;br /&gt;
&lt;br /&gt;
The objective would be to integrate the Aparapi library in gvSIG, so it might be used in the development of new parallel geoprocessing algorithms which take advantage of current GPUs. Also some geoprocesses would have to be developed or converted to use the Aparapi library to check the benefits and the proper operation of the idea.&lt;br /&gt;
&lt;br /&gt;
== Port Network Analysis Extension to gvSIG 2.x branch ==&lt;br /&gt;
&lt;br /&gt;
* '''Product''': gvSIG Desktop&lt;br /&gt;
* '''Mentors''': Joaquín del Cerro, Fran Peñarrubia &lt;br /&gt;
* '''Student''': Eva Rodríguez &lt;br /&gt;
&lt;br /&gt;
Port gvSIG Network Analysis Extension from 1.12 release to the new 2.x branch.&lt;br /&gt;
&lt;br /&gt;
Network Analysis extension allows to calculate routes, service areas, origin - destination matrices, connectivity analysis... It supports speeds for several vehicles, barriers, turn costs, etc.&lt;br /&gt;
&lt;br /&gt;
Improvement: Use GraphHopper [http://graphhopper.com/] library to use new algorithm Contraction Hierarchies (much faster) when calculating routes.&lt;br /&gt;
&lt;br /&gt;
Skills needed: Java, Eclipse development. Some notions about Maven would be interesting.&lt;br /&gt;
&lt;br /&gt;
== CartoDB plugin for gvSIG desktop ==&lt;br /&gt;
&lt;br /&gt;
* '''Product''': gvSIG Desktop&lt;br /&gt;
* '''Mentors''': Óscar Martínez, Joaquín del Cerro &lt;br /&gt;
* '''Student''': Juan Luis Gómez&lt;br /&gt;
&lt;br /&gt;
[http://cartodb.com/ CartoDB] is a Software as a Service (SaaS) cloud computing platform that provides GIS and web mapping tools for display in a web browser. &lt;br /&gt;
&lt;br /&gt;
It will allow to view, create, edit or delete data from CartoDB accounts using gvSIG Desktop. &lt;br /&gt;
&lt;br /&gt;
== Add tests and educational games support to gvSIG Educa  ==&lt;br /&gt;
&lt;br /&gt;
* '''Product''': gvSIG Desktop&lt;br /&gt;
* '''Mentors''': Óscar Martínez, Francisco Díaz &lt;br /&gt;
* '''Student''': Carlos Colombana &lt;br /&gt;
&lt;br /&gt;
The objective would be to extend the thematic maps support already available to allow to design and play tests and educational games, to be used in geography and maps learning.&lt;br /&gt;
&lt;br /&gt;
== Expand the capabilities of Jython scripting for gvSIG Desktop ==&lt;br /&gt;
&lt;br /&gt;
* '''Product''': gvSIG Desktop&lt;br /&gt;
* '''Possible mentor''': &lt;br /&gt;
* '''Possible students''': Sandeep Kumar&lt;br /&gt;
&lt;br /&gt;
Expand the capabilities of Jython scripting in gvSIG Desktop as geoprocessing, reports,...&lt;br /&gt;
&lt;br /&gt;
== Integrating R library into gvSIG Desktop ==&lt;br /&gt;
&lt;br /&gt;
* '''Product''': gvSIG Desktop&lt;br /&gt;
* '''Possible mentor''': &lt;br /&gt;
* '''Possible students''': &lt;br /&gt;
&lt;br /&gt;
The main idea behind this project is about integrating the R library into gvSIG Desktop. R is a free software environment for statistical computing and graphics.&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=GvSIG_GSoC_2015_Ideas&amp;diff=82485</id>
		<title>GvSIG GSoC 2015 Ideas</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=GvSIG_GSoC_2015_Ideas&amp;diff=82485"/>
		<updated>2015-03-04T12:26:30Z</updated>

		<summary type="html">&lt;p&gt;Gvsig: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Use this page to jot down and develop any good idea for the [[Google Summer of Code 2015]] program with gvSIG project. Please, use the gvSIG mailing lists for discussion and check [[Google Summer of Code 2014]] [[GvSIG GSoC 2013 Ideas|2013]], [[GvSIG GSoC 2012 Ideas|2012]], [[GvSIG GSoC 2011 Ideas|2011]], [[GvSIG GSoC 2010 Ideas|2010]], [[GvSIG GSoC 2009 Ideas|2009]] ideas pages for examples or reference.&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Add OpenCL support with Aparapi for Geoprocessing in gvSIG desktop ==&lt;br /&gt;
&lt;br /&gt;
* '''Product''': gvSIG Desktop&lt;br /&gt;
* '''Possible mentor''': If applicable&lt;br /&gt;
* '''Possible student''': Anish Chandran&lt;br /&gt;
&lt;br /&gt;
[https://code.google.com/p/aparapi/ Aparapi] is a library which allows Java developers to take advantage of the compute power of GPU and APU devices by executing data parallel code fragments on the GPU rather than being confined to the local CPU. It does this by converting Java bytecode to OpenCL at runtime and executing on the GPU, if for any reason Aparapi can't execute on the GPU it will execute in a Java thread pool.&lt;br /&gt;
&lt;br /&gt;
Large amounts of geographic data-processing might be involved in the execution of a geoprocess. And many geoprocessing algorithms are suitable to be converted to parallel code, allowing for much better execution performance and capacity.&lt;br /&gt;
&lt;br /&gt;
The objective would be to integrate the Aparapi library in gvSIG, so it might be used in the development of new parallel geoprocessing algorithms which take advantage of current GPUs. Also some geoprocesses would have to be developed or converted to use the Aparapi library to check the benefits and the proper operation of the idea.&lt;br /&gt;
&lt;br /&gt;
== Port Network Analysis Extension to gvSIG 2.x branch ==&lt;br /&gt;
&lt;br /&gt;
* '''Product''': gvSIG Desktop&lt;br /&gt;
* '''Possible mentor''': &lt;br /&gt;
* '''Possible students''': &lt;br /&gt;
&lt;br /&gt;
Port gvSIG Network Analysis Extension from 1.12 release to the new 2.x branch.&lt;br /&gt;
&lt;br /&gt;
Network Analysis extension allows to calculate routes, service areas, origin - destination matrices, connectivity analysis... It supports speeds for several vehicles, barriers, turn costs, etc.&lt;br /&gt;
&lt;br /&gt;
Improvement: Use GraphHopper [http://graphhopper.com/] library to use new algorithm Contraction Hierarchies (much faster) when calculating routes.&lt;br /&gt;
&lt;br /&gt;
Skills needed: Java, Eclipse development. Some notions about Maven would be interesting.&lt;br /&gt;
&lt;br /&gt;
== CartoDB plugin for gvSIG desktop ==&lt;br /&gt;
&lt;br /&gt;
* '''Product''': gvSIG Desktop&lt;br /&gt;
* '''Possible mentor''': &lt;br /&gt;
* '''Possible students''': &lt;br /&gt;
&lt;br /&gt;
[http://cartodb.com/ CartoDB] is a Software as a Service (SaaS) cloud computing platform that provides GIS and web mapping tools for display in a web browser. &lt;br /&gt;
&lt;br /&gt;
It will allow to view, create, edit or delete data from CartoDB accounts using gvSIG Desktop.&lt;br /&gt;
&lt;br /&gt;
== Expand the capabilities of Jython scripting for gvSIG Desktop ==&lt;br /&gt;
&lt;br /&gt;
* '''Product''': gvSIG Desktop&lt;br /&gt;
* '''Possible mentor''': &lt;br /&gt;
* '''Possible students''': &lt;br /&gt;
&lt;br /&gt;
Expand the capabilities of Jython scripting in gvSIG Desktop as geoprocessing, reports,...&lt;br /&gt;
&lt;br /&gt;
== Integrating R library into gvSIG Desktop ==&lt;br /&gt;
&lt;br /&gt;
* '''Product''': gvSIG Desktop&lt;br /&gt;
* '''Possible mentor''': &lt;br /&gt;
* '''Possible students''': &lt;br /&gt;
&lt;br /&gt;
The main idea behind this project is about integrating the R library into gvSIG Desktop. R is a free software environment for statistical computing and graphics.&lt;/div&gt;</summary>
		<author><name>Gvsig</name></author>
	</entry>
</feed>