OSGeo - User contributions [en]

Google Summer of Code 2025 Ideas

2025-03-02T20:11:28Z

Maxi: /* The ideas pages */

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ 
[[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

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

* See also ideas from [[Google Summer of Code 2024 Ideas|2024]], [[Google Summer of Code 2023 Ideas|2023]], [[Google Summer of Code 2022 Ideas|2022]], [[Google Summer of Code 2021 Ideas|2021]],[[Google Summer of Code 2020 Ideas|2020]], [[Google Summer of Code 2019 Ideas|2019]], [[Google Summer of Code 2018 Ideas|2018]], [[Google Summer of Code 2017 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]].
-----

== OSGeo Google Summer of Code 2025 ==

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

These ideas are '''*only*''' to motivate you and serve as an example of the kind of hills we want to charge up. Your own ideas are more than welcome - 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!

* '''Contributors: check out the [[Google Summer of Code Recommendations for Students]] page.
* If you need more information on how to apply you can contact us on [https://discourse.osgeo.org/c/initiatives/soc/43 OSGeo's discourse]
* Read the [https://developers.google.com/open-source/gsoc/help/responsibilities GSoC Roles and Responsibilities ] to understand successful teamwork and interplay of project, mentors, and students.

* There is a [https://developers.google.com/open-source/soc/resources/flyers Google SoC flyer] to look at and post in appropriate places.

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

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

== Recent Modifications in GSoC (Must Read) ==

* The program is open to all the students who are 18 years and older AND to the beginners in open source development, who might not be university students but are 18 years and older. With folks around the world changing careers, returning to the workforce, and learning on their own (outside of academic programs) we see an opportunity to reach a plethora of excited individuals who want to learn more about open source and be a part of our amazing GSoC communities. Check [https://summerofcode.withgoogle.com/rules/ Eligibility] here.

* GSoC Contributors will be able to choose from multiple-size projects: medium at ~175 hours, large at ~350 hours and small at ~90 hours. This is to remove the barrier of available time that many potential contributors have and open the program to people who want to learn about open source development but can’t dedicate all or even half of their summer to the program.

* We are building increased flexibility around the timing of projects - there is an option to extend the standard 12-week coding time frame to a maximum of 22 weeks. This is to allow folks who may realize that spreading the work over say, 16 weeks, is a more realistic goal with their current life situation. Or for contributors who have life happen in the middle of the program and they can’t work on their projects for a few weeks, but they can come back to it after a month to finish it. This would make it easier for GSoC Contributors and mentors to be able to navigate together when obstacles occur and the GSoC Contributor can successfully complete their project.

== The ideas pages ==

To add your page, please contact the GSoC admin team to let them know of your ideas page, by sending an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]

=== OSGeo Foundation graduated project ===

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

[[Image:Pgrouting-logo.png|60px|right]]
* [https://github.com/pgRouting/pgrouting/wiki/GSoC-Ideas:-2025 '''pgRouting''' Ideas]: [http://pgrouting.org pgRouting] extends the PostGIS / PostgreSQL geospatial database to provide geospatial routing functionality and more.

[[Image:ZOO-Project-mini.png|60px|right]]
* [https://github.com/ZOO-Project/ZOO-Project/wiki/Google%E2%80%90Summer%E2%80%90of%E2%80%90Code%E2%80%902025%E2%80%90Project%E2%80%90Ideas '''ZOO-Project''' Ideas]: The [https://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.

[[Image:IstSOS4-logo.png|60px|right]]
* [https://github.com/istSOS/istSOS4/wiki/Google%E2%80%90Summer%E2%80%90of%E2%80%90Code%E2%80%902025%E2%80%90Project%E2%80%90Ideas '''istSOS''' Ideas]: The [https://www.istsos.org istSOS] project is sensor data management tool that allows collection, maintenance and publishing of monitoring observations using the Open Geospatial Consortium (OGC) SensorThingsAPI standard.



== I want to apply as a student ==

Before applying as a student, check out the [[Google Summer of Code Recommendations for Students]] page.

=== Which project do I choose? ===

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

=== Important dates ===

* [https://developers.google.com/open-source/gsoc/timeline '''The official timeline''']

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

File:IstSOS4-logo.png

2025-03-02T20:08:40Z

Maxi:

Google Summer of Code 2024 Ideas

2024-02-06T05:58:54Z

Maxi:

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ 
[[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

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

* See also ideas from [[Google Summer of Code 2022 Ideas|2023]], [Google Summer of Code 2022 Ideas|2022]], [[Google Summer of Code 2021 Ideas|2021]],[[Google Summer of Code 2020 Ideas|2020]], [[Google Summer of Code 2019 Ideas|2019]], [[Google Summer of Code 2018 Ideas|2018]], [[Google Summer of Code 2017 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]].
-----

== OSGeo Google Summer of Code 2024 ==

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

These ideas are '''*only*''' to motivate you and serve as an example of the kind of hills we want to charge up. Your own ideas are more than welcome - 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!

* '''Contributors: 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 successful teamwork and interplay of project, mentors, and students.

* There is a [https://developers.google.com/open-source/soc/resources/flyers Google SoC flyer] to look at and post in appropriate places.

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

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

== New Modifications with GSoC 2022 and continuing ahead (Must Read) ==

* Since 2022, the program will be open to all newcomers of open source that are 18 years and older, no longer focusing solely on university students. With folks around the world changing careers, returning to the workforce, and learning on their own (outside of academic programs) we see an opportunity to reach a plethora of excited individuals who want to learn more about open source and be a part of our amazing GSoC communities. Check [https://summerofcode.withgoogle.com/rules/ Eligibility] here.

* GSoC Contributors will also be able to choose from multiple-size projects ~175 hours (medium) and 350 hours (large). We understand not everyone can spend 30 hours a week on a coding project for 12 weeks but they would like to be a part of these communities with the help of mentors.

* We are building increased flexibility around the timing of projects - there is an option to extend the standard 12-week coding time frame to a maximum of 22 weeks. This is to allow folks who may realize that spreading the work over say, 16 weeks, is a more realistic goal with their current life situation. Or for contributors who have life happen in the middle of the program and they can’t work on their projects for a few weeks, but they can come back to it after a month to finish it. Hopefully, this makes it easier for GSoC Contributors and mentors to be able to navigate together when obstacles occur and the GSoC Contributor can successfully complete their project.

== The ideas pages ==

To add your page, please contact the GSoC admin team to let them know of your ideas page, by sending an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]

=== OSGeo Foundation graduated project ===

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



[[Image:Pgrouting-logo.png|60px|right]]
* [https://github.com/pgRouting/pgrouting/wiki/GSoC-Ideas:-2024 '''pgRouting''' Ideas]: [http://pgrouting.org pgRouting] extends the PostGIS / PostgreSQL geospatial database to provide geospatial routing functionality and more.

=== OSGeo Foundation Incubation project ===

[[Image:ZOO-Project-mini.png|60px|right]]
* [https://github.com/ZOO-Project/ZOO-Project/wiki/Google-Summer-of-Code-2024-Project-Ideas '''ZOO-Project''' Ideas]: The [https://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.

* [https://github.com/istSOS/istsos2/wiki/istSOS-GSoC-2024 '''istSOS''' Ideas]: The [https://www.iatsos.org istSOS] project is sensor data management tool that allows collection, maintenance and publishing of monitoring observations using the Open Geospatial Consortium (OGC) Sensor Observation Service (SOS) standard.



== I want to apply as a student ==

Before applying as a student, check out the [[Google Summer of Code Recommendations for Students]] page.

=== Which project do I choose? ===

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

=== Important dates ===

* [https://developers.google.com/open-source/gsoc/timeline '''The official timeline''']

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

Google Summer of Code 2023 Ideas

2023-03-22T23:24:30Z

Maxi: Added istsos project ideas

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ 
[[Image:Osgeo-logo.png|300px|link=http://www.osgeo.org]]
</center>

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

* See also ideas from [[Google Summer of Code 2022 Ideas|2022]], [[Google Summer of Code 2021 Ideas|2021]],[[Google Summer of Code 2020 Ideas|2020]], [[Google Summer of Code 2019 Ideas|2019]], [[Google Summer of Code 2018 Ideas|2018]], [[Google Summer of Code 2017 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]].
-----

== OSGeo Google Summer of Code 2023 ==

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

These ideas are '''*only*''' to motivate you and serve as an example of the kind of hills we want to charge up. Your own ideas are more than welcome - 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!

* '''Contributors: 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 successful teamwork and interplay of project, mentors, and students.

* There is a [https://developers.google.com/open-source/soc/resources/flyers Google SoC flyer] to look at and post in appropriate places.

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

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

== New Modifications with GSoC 2022 and continuing ahead (Must Read) ==

* Since 2022, the program will be open to all newcomers of open source that are 18 years and older, no longer focusing solely on university students. With folks around the world changing careers, returning to the workforce, and learning on their own (outside of academic programs) we see an opportunity to reach a plethora of excited individuals who want to learn more about open source and be a part of our amazing GSoC communities. Check [https://summerofcode.withgoogle.com/rules/ Eligibility] here.

* GSoC Contributors will also be able to choose from multiple-size projects ~175 hours (medium) and 350 hours (large). We understand not everyone can spend 30 hours a week on a coding project for 12 weeks but they would like to be a part of these communities with the help of mentors.

* We are building increased flexibility around the timing of projects - there is an option to extend the standard 12-week coding time frame to a maximum of 22 weeks. This is to allow folks who may realize that spreading the work over say, 16 weeks, is a more realistic goal with their current life situation. Or for contributors who have life happen in the middle of the program and they can’t work on their projects for a few weeks, but they can come back to it after a month to finish it. Hopefully, this makes it easier for GSoC Contributors and mentors to be able to navigate together when obstacles occur and the GSoC Contributor can successfully complete their project.

== The ideas pages ==

To add your page, please contact the GSoC admin team to let them know of your ideas page, by sending an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]

=== OSGeo Foundation graduated project ===

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



[[Image:Pgrouting-logo.png|60px|right]]
* [https://github.com/pgRouting/pgrouting/wiki/GSoC-Ideas:-2023 '''pgRouting''' Ideas]: [http://pgrouting.org pgRouting] extends the PostGIS / PostgreSQL geospatial database to provide geospatial routing functionality and more.

=== OSGeo Foundation Incubation project ===

[[Image:ZOO-Project-mini.png|60px|right]]
* [https://github.com/ZOO-Project/ZOO-Project/wiki/Google-Summer-of-Code-2023-Project-Ideas '''ZOO-Project''' Ideas]: The [https://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.

* [https://github.com/istSOS/istsos2/wiki/GSoC-2023-project-ideas '''istSOS''' Ideas]: The [https://www.iatsos.org istSOS] project is sensor data management tool that allows collection, maintenance and publishing of monitoring observations using the Open Geospatial Consortium (OGC) Sensor Observation Service (SOS) standard.

=== OSGeo Foundation Guest Project ===

* [https://github.com/ec-jrc/re3gistry/wiki/Google-Summer-of-Code-2023 '''Re3gistry''' Ideas]:
The Re3gistry software is a reusable open-source solution for managing and sharing 'reference codes' through the use of persistent URIs, ensuring concepts are correctly referenced in any domain. Licensed under the EUPL, it has been developed in a context-neutral way as an open-source project to be deployed or further developed by anyone in any domain.

== I want to apply as a student ==

Before applying as a student, check out the [[Google Summer of Code Recommendations for Students]] page.

=== Which project do I choose? ===

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

=== Important dates ===

* [https://developers.google.com/open-source/gsoc/timeline '''The official timeline''']

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

OSGeo Budget 2023

2023-01-20T06:14:26Z

Maxi:

Draft budget for 2023, see [[OSGeo Budget 2022]] and [[Finance Committee#Documents]] for prior years.

Total Approved Budget for 2022: $213,346 USD

Total spending for 2022: TBD

Total Approved Budget for 2023: TBD

== OSGeo Board ==

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.

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! Board
! 2022 Approved
! 2022 Actual
! 2023 Draft
! Notes
|-
| Admin
| style="text-align:right;" | 4,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Operational expenses including liability insurance, tax filing fees, quickbooks, mail, IRS, bank fees.
|-
| Travel
| style="text-align:right;" | 15,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Travel to main FOSS4G, F2F meeting and regional/representative events
|-
| Partners and Sponsors
| style="text-align:right;" | 2,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Relationship building, attending b2b functions, foss4g/foss4ge/foss4gna/foss4g-asia breakfast meetings. Meetings with sponsors during events
|}

Total Board Budget for 2022: $21,000 USD

Total Board spending for 2022: TBD

Total Board Budget for 2023: TBD

== OSGeo Committees ==

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.

* Code of Conduct Committee
* Conference Committee
* GeoForAll - committee acting as advisory board for the GeoForAll Initiative
* Incubation Committee - committee providing hands-on support for project teams adopting open source principles and practice.
* Marketing Committee - outreach and advocacy support
* Open GeoScience Committee
* System Administration Committee - foundation infrastructure
* UN Committee - committee responsible for our participation in the UN Open GIS program

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! OSGeo Committees
! 2022 Approved [Requested]
! 2022 Actual
! 2023 Draft [Requested]
! Notes
|-
| SAC
| style="text-align:right;" | 32,550 [32,550]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| [[SAC:Budget#2023]]
|-
| OpenGeoScience
| style="text-align:right;" | 2,500 [3,000]
| style="text-align:right;" | 0
| style="text-align:right;" | 3,000
| EGU townhall + sprint support for open research data and standards integration
|-
| Conference
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| Marketing
| style="text-align:right;" | 7,500 [7,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoForAll
| style="text-align:right;" | 4,000 [4,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| UN Committee
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| No UN challenge this year
|-
| Incubation Committee
| style="text-align:right;" | 6,000 [8,000]
| style="text-align:right;" | 8,000
| style="text-align:right;" | TBD
| Request budget to support growing interest in incubation program. Also interested in improving documentation for the osgeo board "community project" program so that consistent links can be handed out to interested parties.
|}

Total Committees Budget for 2022: $52,550 USD

Total Committees spending for 2022: TBD

Total Committees Budget for 2023: TBD

== OSGeo Initiatives ==

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.

* FOSS4G - event series produced in collaboration with the conference committee and local chapters
* GeoForAll - education and research program produced in collaboration with our partners
* Incubation - mentor program for open source projects to be recognized as OSGeo project
* Local Chapters - board outreach initiative establishing regional OSGeo groups for direct grassroots advoacacy
* GSoC - coordinate participation in google-summer-of-code and code-in activities
* Travel Grant Program - provides assistance for attending OSGeo events

Proposed initiatives:

* security - proposed emergency funding for osgeo projects confronted with disruptive security issue. Application similar to code-sprint requires both a solid budget and a formal CVE report to work against.
* opengis harmonization - proposed response to [https://git.osgeo.org/gitea/osgeo/todo/issues/142 #142] coordinating required activities across projects (rather than as individual budget requests listed below).

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! OSGeo Initiatives
! 2022 Approved
! 2022 Actual
! 2023 Draft
! Notes
|-
| FOSS4G
| style="text-align:right;" | 66,796
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Seed money for 2022.
|-
| Local Chapters
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| 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)
|-
| GSoC
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Managed by board.
|-
| Travel Grant Program
| style="text-align:right;" | 15,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Managed by Conference Committee. FOSS4G 2022 asked for 10k in conference mailing list, 5k proposed by board for local events.
|-
| Events and Code Sprints
| style="text-align:right;" | 20,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| 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.) Board note: This budget reflects the 15,000 sponsorship we got for the postponed Athens Code Sprint.
|-
| Community Projects
| style="text-align:right;" | 5,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| 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. Board note: Budgeted 300$ for each project. To be amended if we hit the ceiling of the budget.
|
|}

Total Initiatives Budget for 2022: $106,796 USD

Total Initiatives spending for 2022: TBD

Total Initiatives Budget for 2023: TBD

= Projects =

== OSGeo Projects ==

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.

Notes:

* We have reached out (2022) to the projects mailing list.
* Board decided to assign a default budget of $500 for any project that has reported to the board within the year.
* Projects with a plan may of course ask for increased funding
* 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.
* If a project did not respond (or runs into an unforeseen expense) please contact the board throughout the year as budgets can be amended

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! OSGeo Project
! 2022 Approved [Requested]
! 2022 Actual
! 2023 Draft [Requested]
! Notes
|-
| deegree
| style="text-align:right;" | 2,000 [2,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| https://github.com/deegree/deegree3/wiki/deegree-budget-2023
|-
| GDAL/OGR
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoMOOSE
| style="text-align:right;" | 2,500 [2,500]
| style="text-align:right;" | 2,500 (in process)
| style="text-align:right;" | TBD [2,500]
| https://github.com/geomoose/geomoose/wiki/PSC-Meeting-2022-10-21
|-
| GeoNetwork
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoNode
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GEOS
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoServer
| style="text-align:right;" | 3,000 [3,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| [[GeoServer Budget 2023]]
|-
| GeoTools
| style="text-align:right;" | 500
| style="text-align:right;" | 10,500
| style="text-align:right;" | TBD
| [https://github.com/geotools/geotools/wiki/GeoTools-Budget-Request-2023 GeoTools Budget Request 2023]
|-
| GRASS GIS
| style="text-align:right;" | 4,000 [3964.49]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| gvSIG
| style="text-align:right;" | 5,000 [5,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD [5,000]
| [[GvSIG Budget 2023]]
|-
| Mapbender
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| MapServer
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| Marble
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Need to report to the board to get a budget
|-
| OpenLayers
| style="text-align:right;" | 3,000 [3,000]
| style="text-align:right;" | 0
| style="text-align:right;" | 3,000
| https://wiki.osgeo.org/wiki/OpenLayers_Budget_2023
|-
| OTB
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| OSGeoLive
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| PostGIS
| style="text-align:right;" | 500
| style="text-align:right;" | 0
| style="text-align:right;" | [3,500]
| for trademark expenses
|-
| PROJ
| style="text-align:right;" | 500
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| pycsw
| style="text-align:right;" | 2,500 [2,500]
| style="text-align:right;" | 0
| style="text-align:right;" | TBD [2,500]
| https://github.com/geopython/pycsw/wiki/OSGeo-Budget-2023
|-
| pygeoapi
| style="text-align:right;" | 300
| style="text-align:right;" | 0
| style="text-align:right;" | TBD [4,000]
| https://github.com/geopython/pygeoapi/wiki/OSGeo-Budget-2023
|-
| PyWPS
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| QGIS
| style="text-align:right;" | 5,000 [5,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|}

Total Projects Budget for 2022: $33,000 USD

Total Projects spending for 2022: TBD

Total Projects Budget for 2023: TBD

== Community Projects ==

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)

Some guidance is offered by individual projects below.

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 have been accepted into the incubation program can ask the Incubation Committee for assistance to work on incubation (such requests are included in the incubation committee budget not here).

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! Community Project
! 2022 Approved [Requested]
! 2022 Actual
! 2023 Draft [Requested]
! Notes
|-
| pgRouting
| style="text-align:right;" | 300
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| 2022 Board note: 300 USD approved from Community Projects budget.
|-
| istSOS
| style="text-align:right;" | 300
| style="text-align:right;" | 0
| style="text-align:right;" | 1000
| request to support a sprint on code renew to support other specification (STAC)
|-
| GeoWebCache
| style="text-align:right;" | 300
| style="text-align:right;" |
| style="text-align:right;" | 5000
| GeoWebCache request funding to work on Issue [https://git.osgeo.org/gitea/osgeo/todo/issues/142 #142] (either directly or as part of a cross-project initaitive)
|-
|}

= Events =

== Community Events ==

We have set aside a budget for community events in 2022:

* Supporting community building events is distinct from the development focused code-sprints below
* We are inviting community members to contact us about events (rather than try and adjust their event to fit into our code sprint guidelines)
* 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.
* Please note our [https://github.com/OSGeo/osgeo/blob/master/board/documents/osgeo_financial_guidance.pdf financial guidance document]

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! Event Request
! 2022 Approved
! 2022 Actual
! 2023 Draft
! Notes
|-
| QGIS Developer Meeting and User Conference
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|}

== Code Sprints ==

We have asked project teams for guidance to help set our code sprint budget:

* 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.
* Out priority is to share the risk with organizers allowing access to funds early to book facilities as required
* 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.

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! Sprint Request
! 2022 Approved
! 2022 Actual
! 2023 Draft
! Notes
|-
| OSGeo Code Sprint
| style="text-align:right;" | 15,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| No financial request made, seed and sponsorship money exists from previous years.
|-
| GeoServer Code Sprint
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| PostGIS Code Sprint
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GRASS GIS Community Sprint
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|}

= Approval and Amendments =

* Budget Meeting: [[Board_Meeting_2023-01-30]]
* Loomio Motion: TBD
* Amendments: TBD

[[Category:Budget]]
[[Category:Finance]]

OSGeo Budget 2023

2023-01-20T06:12:33Z

Maxi:

Draft budget for 2023, see [[OSGeo Budget 2022]] and [[Finance Committee#Documents]] for prior years.

Total Approved Budget for 2022: $213,346 USD

Total spending for 2022: TBD

Total Approved Budget for 2023: TBD

== OSGeo Board ==

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.

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! Board
! 2022 Approved
! 2022 Actual
! 2023 Draft
! Notes
|-
| Admin
| style="text-align:right;" | 4,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Operational expenses including liability insurance, tax filing fees, quickbooks, mail, IRS, bank fees.
|-
| Travel
| style="text-align:right;" | 15,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Travel to main FOSS4G, F2F meeting and regional/representative events
|-
| Partners and Sponsors
| style="text-align:right;" | 2,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Relationship building, attending b2b functions, foss4g/foss4ge/foss4gna/foss4g-asia breakfast meetings. Meetings with sponsors during events
|}

Total Board Budget for 2022: $21,000 USD

Total Board spending for 2022: TBD

Total Board Budget for 2023: TBD

== OSGeo Committees ==

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.

* Code of Conduct Committee
* Conference Committee
* GeoForAll - committee acting as advisory board for the GeoForAll Initiative
* Incubation Committee - committee providing hands-on support for project teams adopting open source principles and practice.
* Marketing Committee - outreach and advocacy support
* Open GeoScience Committee
* System Administration Committee - foundation infrastructure
* UN Committee - committee responsible for our participation in the UN Open GIS program

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! OSGeo Committees
! 2022 Approved [Requested]
! 2022 Actual
! 2023 Draft [Requested]
! Notes
|-
| SAC
| style="text-align:right;" | 32,550 [32,550]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| [[SAC:Budget#2023]]
|-
| OpenGeoScience
| style="text-align:right;" | 2,500 [3,000]
| style="text-align:right;" | 0
| style="text-align:right;" | 3,000
| EGU townhall + sprint support for open research data and standards integration
|-
| Conference
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| Marketing
| style="text-align:right;" | 7,500 [7,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoForAll
| style="text-align:right;" | 4,000 [4,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| UN Committee
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| No UN challenge this year
|-
| Incubation Committee
| style="text-align:right;" | 6,000 [8,000]
| style="text-align:right;" | 8,000
| style="text-align:right;" | TBD
| Request budget to support growing interest in incubation program. Also interested in improving documentation for the osgeo board "community project" program so that consistent links can be handed out to interested parties.
|}

Total Committees Budget for 2022: $52,550 USD

Total Committees spending for 2022: TBD

Total Committees Budget for 2023: TBD

== OSGeo Initiatives ==

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.

* FOSS4G - event series produced in collaboration with the conference committee and local chapters
* GeoForAll - education and research program produced in collaboration with our partners
* Incubation - mentor program for open source projects to be recognized as OSGeo project
* Local Chapters - board outreach initiative establishing regional OSGeo groups for direct grassroots advoacacy
* GSoC - coordinate participation in google-summer-of-code and code-in activities
* Travel Grant Program - provides assistance for attending OSGeo events

Proposed initiatives:

* security - proposed emergency funding for osgeo projects confronted with disruptive security issue. Application similar to code-sprint requires both a solid budget and a formal CVE report to work against.
* opengis harmonization - proposed response to [https://git.osgeo.org/gitea/osgeo/todo/issues/142 #142] coordinating required activities across projects (rather than as individual budget requests listed below).

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! OSGeo Initiatives
! 2022 Approved
! 2022 Actual
! 2023 Draft
! Notes
|-
| FOSS4G
| style="text-align:right;" | 66,796
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Seed money for 2022.
|-
| Local Chapters
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| 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)
|-
| GSoC
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Managed by board.
|-
| Travel Grant Program
| style="text-align:right;" | 15,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Managed by Conference Committee. FOSS4G 2022 asked for 10k in conference mailing list, 5k proposed by board for local events.
|-
| Events and Code Sprints
| style="text-align:right;" | 20,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| 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.) Board note: This budget reflects the 15,000 sponsorship we got for the postponed Athens Code Sprint.
|-
| Community Projects
| style="text-align:right;" | 5,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| 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. Board note: Budgeted 300$ for each project. To be amended if we hit the ceiling of the budget.
|
|}

Total Initiatives Budget for 2022: $106,796 USD

Total Initiatives spending for 2022: TBD

Total Initiatives Budget for 2023: TBD

= Projects =

== OSGeo Projects ==

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.

Notes:

* We have reached out (2022) to the projects mailing list.
* Board decided to assign a default budget of $500 for any project that has reported to the board within the year.
* Projects with a plan may of course ask for increased funding
* 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.
* If a project did not respond (or runs into an unforeseen expense) please contact the board throughout the year as budgets can be amended

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! OSGeo Project
! 2022 Approved [Requested]
! 2022 Actual
! 2023 Draft [Requested]
! Notes
|-
| deegree
| style="text-align:right;" | 2,000 [2,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| https://github.com/deegree/deegree3/wiki/deegree-budget-2023
|-
| GDAL/OGR
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoMOOSE
| style="text-align:right;" | 2,500 [2,500]
| style="text-align:right;" | 2,500 (in process)
| style="text-align:right;" | TBD [2,500]
| https://github.com/geomoose/geomoose/wiki/PSC-Meeting-2022-10-21
|-
| GeoNetwork
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoNode
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GEOS
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoServer
| style="text-align:right;" | 3,000 [3,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| [[GeoServer Budget 2023]]
|-
| GeoTools
| style="text-align:right;" | 500
| style="text-align:right;" | 10,500
| style="text-align:right;" | TBD
| [https://github.com/geotools/geotools/wiki/GeoTools-Budget-Request-2023 GeoTools Budget Request 2023]
|-
| GRASS GIS
| style="text-align:right;" | 4,000 [3964.49]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| gvSIG
| style="text-align:right;" | 5,000 [5,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD [5,000]
| [[GvSIG Budget 2023]]
|-
| Mapbender
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| MapServer
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| Marble
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Need to report to the board to get a budget
|-
| OpenLayers
| style="text-align:right;" | 3,000 [3,000]
| style="text-align:right;" | 0
| style="text-align:right;" | 3,000
| https://wiki.osgeo.org/wiki/OpenLayers_Budget_2023
|-
| OTB
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| OSGeoLive
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| PostGIS
| style="text-align:right;" | 500
| style="text-align:right;" | 0
| style="text-align:right;" | [3,500]
| for trademark expenses
|-
| PROJ
| style="text-align:right;" | 500
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| pycsw
| style="text-align:right;" | 2,500 [2,500]
| style="text-align:right;" | 0
| style="text-align:right;" | TBD [2,500]
| https://github.com/geopython/pycsw/wiki/OSGeo-Budget-2023
|-
| pygeoapi
| style="text-align:right;" | 300
| style="text-align:right;" | 0
| style="text-align:right;" | TBD [4,000]
| https://github.com/geopython/pygeoapi/wiki/OSGeo-Budget-2023
|-
| PyWPS
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| QGIS
| style="text-align:right;" | 5,000 [5,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|}

Total Projects Budget for 2022: $33,000 USD

Total Projects spending for 2022: TBD

Total Projects Budget for 2023: TBD

== Community Projects ==

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)

Some guidance is offered by individual projects below.

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 have been accepted into the incubation program can ask the Incubation Committee for assistance to work on incubation (such requests are included in the incubation committee budget not here).

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! Community Project
! 2022 Approved [Requested]
! 2022 Actual
! 2023 Draft [Requested]
! Notes
|-
| pgRouting
| style="text-align:right;" | 300
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| 2022 Board note: 300 USD approved from Community Projects budget.
|-
| istSOS
| style="text-align:right;" | 300
| style="text-align:right;" | 0
| style="text-align:right;" | 1000
| 2022 Board note: request to support a sprint on code renew to support other specification (STAC)
|-
| GeoWebCache
| style="text-align:right;" | 300
| style="text-align:right;" |
| style="text-align:right;" | 5000
| GeoWebCache request funding to work on Issue [https://git.osgeo.org/gitea/osgeo/todo/issues/142 #142] (either directly or as part of a cross-project initaitive)
|-
|}

= Events =

== Community Events ==

We have set aside a budget for community events in 2022:

* Supporting community building events is distinct from the development focused code-sprints below
* We are inviting community members to contact us about events (rather than try and adjust their event to fit into our code sprint guidelines)
* 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.
* Please note our [https://github.com/OSGeo/osgeo/blob/master/board/documents/osgeo_financial_guidance.pdf financial guidance document]

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! Event Request
! 2022 Approved
! 2022 Actual
! 2023 Draft
! Notes
|-
| QGIS Developer Meeting and User Conference
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|}

== Code Sprints ==

We have asked project teams for guidance to help set our code sprint budget:

* 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.
* Out priority is to share the risk with organizers allowing access to funds early to book facilities as required
* 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.

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! Sprint Request
! 2022 Approved
! 2022 Actual
! 2023 Draft
! Notes
|-
| OSGeo Code Sprint
| style="text-align:right;" | 15,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| No financial request made, seed and sponsorship money exists from previous years.
|-
| GeoServer Code Sprint
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| PostGIS Code Sprint
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GRASS GIS Community Sprint
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|}

= Approval and Amendments =

* Budget Meeting: [[Board_Meeting_2023-01-30]]
* Loomio Motion: TBD
* Amendments: TBD

[[Category:Budget]]
[[Category:Finance]]

OSGeo Budget 2023

2023-01-19T16:40:21Z

Maxi:

Draft budget for 2023, see [[OSGeo Budget 2022]] and [[Finance Committee#Documents]] for prior years.

Total Approved Budget for 2022: $213,346 USD

Total spending for 2022: TBD

Total Approved Budget for 2023: TBD

== OSGeo Board ==

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.

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! Board
! 2022 Approved
! 2022 Actual
! 2023 Draft
! Notes
|-
| Admin
| style="text-align:right;" | 4,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Operational expenses including liability insurance, tax filing fees, quickbooks, mail, IRS, bank fees.
|-
| Travel
| style="text-align:right;" | 15,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Travel to main FOSS4G, F2F meeting and regional/representative events
|-
| Partners and Sponsors
| style="text-align:right;" | 2,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Relationship building, attending b2b functions, foss4g/foss4ge/foss4gna/foss4g-asia breakfast meetings. Meetings with sponsors during events
|}

Total Board Budget for 2022: $21,000 USD

Total Board spending for 2022: TBD

Total Board Budget for 2023: TBD

== OSGeo Committees ==

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.

* Code of Conduct Committee
* Conference Committee
* GeoForAll - committee acting as advisory board for the GeoForAll Initiative
* Incubation Committee - committee providing hands-on support for project teams adopting open source principles and practice.
* Marketing Committee - outreach and advocacy support
* Open GeoScience Committee
* System Administration Committee - foundation infrastructure
* UN Committee - committee responsible for our participation in the UN Open GIS program

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! OSGeo Committees
! 2022 Approved [Requested]
! 2022 Actual
! 2023 Draft [Requested]
! Notes
|-
| SAC
| style="text-align:right;" | 32,550 [32,550]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| [[SAC:Budget#2023]]
|-
| OpenGeoScience
| style="text-align:right;" | 2,500 [3,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | 3,000
| Please contact marketing committee for marketing materials (500$)
|-
| Conference
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| Marketing
| style="text-align:right;" | 7,500 [7,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoForAll
| style="text-align:right;" | 4,000 [4,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| UN Committee
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| No UN challenge this year
|-
| Incubation Committee
| style="text-align:right;" | 6,000 [8,000]
| style="text-align:right;" | 8,000
| style="text-align:right;" | TBD
| Request budget to support growing interest in incubation program. Also interested in improving documentation for the osgeo board "community project" program so that consistent links can be handed out to interested parties.
|}

Total Committees Budget for 2022: $52,550 USD

Total Committees spending for 2022: TBD

Total Committees Budget for 2023: TBD

== OSGeo Initiatives ==

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.

* FOSS4G - event series produced in collaboration with the conference committee and local chapters
* GeoForAll - education and research program produced in collaboration with our partners
* Incubation - mentor program for open source projects to be recognized as OSGeo project
* Local Chapters - board outreach initiative establishing regional OSGeo groups for direct grassroots advoacacy
* GSoC - coordinate participation in google-summer-of-code and code-in activities
* Travel Grant Program - provides assistance for attending OSGeo events

Proposed initiatives:

* security - proposed emergency funding for osgeo projects confronted with disruptive security issue. Application similar to code-sprint requires both a solid budget and a formal CVE report to work against.
* opengis harmonization - proposed response to [https://git.osgeo.org/gitea/osgeo/todo/issues/142 #142] coordinating required activities across projects (rather than as individual budget requests listed below).

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! OSGeo Initiatives
! 2022 Approved
! 2022 Actual
! 2023 Draft
! Notes
|-
| FOSS4G
| style="text-align:right;" | 66,796
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Seed money for 2022.
|-
| Local Chapters
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| 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)
|-
| GSoC
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Managed by board.
|-
| Travel Grant Program
| style="text-align:right;" | 15,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Managed by Conference Committee. FOSS4G 2022 asked for 10k in conference mailing list, 5k proposed by board for local events.
|-
| Events and Code Sprints
| style="text-align:right;" | 20,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| 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.) Board note: This budget reflects the 15,000 sponsorship we got for the postponed Athens Code Sprint.
|-
| Community Projects
| style="text-align:right;" | 5,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| 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. Board note: Budgeted 300$ for each project. To be amended if we hit the ceiling of the budget.
|
|}

Total Initiatives Budget for 2022: $106,796 USD

Total Initiatives spending for 2022: TBD

Total Initiatives Budget for 2023: TBD

= Projects =

== OSGeo Projects ==

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.

Notes:

* We have reached out (2022) to the projects mailing list.
* Board decided to assign a default budget of $500 for any project that has reported to the board within the year.
* Projects with a plan may of course ask for increased funding
* 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.
* If a project did not respond (or runs into an unforeseen expense) please contact the board throughout the year as budgets can be amended

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! OSGeo Project
! 2022 Approved [Requested]
! 2022 Actual
! 2023 Draft [Requested]
! Notes
|-
| deegree
| style="text-align:right;" | 2,000 [2,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| https://github.com/deegree/deegree3/wiki/deegree-budget-2023
|-
| GDAL/OGR
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoMOOSE
| style="text-align:right;" | 2,500 [2,500]
| style="text-align:right;" | 2,500 (in process)
| style="text-align:right;" | TBD [2,500]
| https://github.com/geomoose/geomoose/wiki/PSC-Meeting-2022-10-21
|-
| GeoNetwork
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoNode
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GEOS
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoServer
| style="text-align:right;" | 3,000 [3,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| [[GeoServer Budget 2023]]
|-
| GeoTools
| style="text-align:right;" | 500
| style="text-align:right;" | 10,500
| style="text-align:right;" | TBD
| [https://github.com/geotools/geotools/wiki/GeoTools-Budget-Request-2023 GeoTools Budget Request 2023]
|-
| GRASS GIS
| style="text-align:right;" | 4,000 [3964.49]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| gvSIG
| style="text-align:right;" | 5,000 [5,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD [5,000]
| [[GvSIG Budget 2023]]
|-
| Mapbender
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| MapServer
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| Marble
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Need to report to the board to get a budget
|-
| OpenLayers
| style="text-align:right;" | 3,000 [3,000]
| style="text-align:right;" | 0
| style="text-align:right;" | 3,000
| https://wiki.osgeo.org/wiki/OpenLayers_Budget_2023
|-
| OTB
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| OSGeoLive
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| PostGIS
| style="text-align:right;" | 500
| style="text-align:right;" | 0
| style="text-align:right;" | [3,500]
| for trademark expenses
|-
| PROJ
| style="text-align:right;" | 500
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| pycsw
| style="text-align:right;" | 2,500 [2,500]
| style="text-align:right;" | 0
| style="text-align:right;" | TBD [2,500]
| https://github.com/geopython/pycsw/wiki/OSGeo-Budget-2023
|-
| pygeoapi
| style="text-align:right;" | 300
| style="text-align:right;" | 0
| style="text-align:right;" | TBD [4,000]
| https://github.com/geopython/pygeoapi/wiki/OSGeo-Budget-2023
|-
| PyWPS
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| QGIS
| style="text-align:right;" | 5,000 [5,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|}

Total Projects Budget for 2022: $33,000 USD

Total Projects spending for 2022: TBD

Total Projects Budget for 2023: TBD

== Community Projects ==

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)

Some guidance is offered by individual projects below.

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 have been accepted into the incubation program can ask the Incubation Committee for assistance to work on incubation (such requests are included in the incubation committee budget not here).

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! Community Project
! 2022 Approved [Requested]
! 2022 Actual
! 2023 Draft [Requested]
! Notes
|-
| pgRouting
| style="text-align:right;" | 300
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| 2022 Board note: 300 USD approved from Community Projects budget.
|-
| istSOS
| style="text-align:right;" | 300
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| 2022 Board note: 300 USD approved from Community Projects budget.
|-
| GeoWebCache
| style="text-align:right;" | 300
| style="text-align:right;" |
| style="text-align:right;" | 5000
| GeoWebCache request funding to work on Issue [https://git.osgeo.org/gitea/osgeo/todo/issues/142 #142] (either directly or as part of a cross-project initaitive)
|-
|}

= Events =

== Community Events ==

We have set aside a budget for community events in 2022:

* Supporting community building events is distinct from the development focused code-sprints below
* We are inviting community members to contact us about events (rather than try and adjust their event to fit into our code sprint guidelines)
* 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.
* Please note our [https://github.com/OSGeo/osgeo/blob/master/board/documents/osgeo_financial_guidance.pdf financial guidance document]

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! Event Request
! 2022 Approved
! 2022 Actual
! 2023 Draft
! Notes
|-
| QGIS Developer Meeting and User Conference
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|}

== Code Sprints ==

We have asked project teams for guidance to help set our code sprint budget:

* 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.
* Out priority is to share the risk with organizers allowing access to funds early to book facilities as required
* 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.

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! Sprint Request
! 2022 Approved
! 2022 Actual
! 2023 Draft
! Notes
|-
| OSGeo Code Sprint
| style="text-align:right;" | 15,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| No financial request made, seed and sponsorship money exists from previous years.
|-
| GeoServer Code Sprint
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| PostGIS Code Sprint
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GRASS GIS Community Sprint
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|}

= Approval and Amendments =

* Budget Meeting: [[Board_Meeting_2023-01-30]]
* Loomio Motion: TBD
* Amendments: TBD

[[Category:Budget]]
[[Category:Finance]]

User:Maxi71

2022-01-23T10:17:55Z

Maxi: Maxi moved page User:Maxi71 to User:Maxi: Automatically moved page while renaming the user "Maxi71" to "Maxi"

#REDIRECT [[User:Maxi]]

User:Maxi

2022-01-23T10:17:55Z

Maxi: Maxi moved page User:Maxi71 to User:Maxi: Automatically moved page while renaming the user "Maxi71" to "Maxi"

#redirect:[[Massimiliano Cannata]]

Massimiliano Cannata

2021-03-30T19:56:40Z

Maxi:

{{OSGeo Member
|Name=Massimiliano Cannata
|JobTitle=Professor in enginering geomatics
|Company=University of Applied Sciences and Arts of Southern Switzerland (SUPSI)
|Address=Campus Trevano, Canobbio, Switzerland
|Country=Switzerland
|City=Canobbio
|Coordinate=46.026803, 8.961485
|LocalChapter=GFOSS.it
|Email=massimiliano.cannata AT supsi DOT ch
|Phone=+41 (0)58 666 62 14
|Photo=Massimiliano_cannata.jpg
|Languages=English; Italian;
|Info=Massimiliano received his PhD in Gedoesy and Geomatics after his master degree in environmental engineering at the Politecnico di Milano. Since 2007 he's the head of the geomatic division within the Institute of Earth Sciences (www.ist.supsi.ch) in Switzerland.

He participated in the community since it's inception at various levels. He's a former director of the Open Source Geospatial foundation (OSGeo) and member of the project steering committee of the projects and ZOO (http://www.zoo-project.org). From 2006 to 2016 he was also PSC member of the GIS GRASS (http://grass.osgeo.org). He's group lead the developement of the istSOS project (http://istsos.org) implementing open standards for sensor observation services. Co-chair of the UnitedNation committee and of the Open Geoscience committee.
}}
{{OSGeo Experience
|User=Yes
|Committee=Yes
|Board=No
|Coder=No
|Translate=No
|PSC=Yes
|ExBoard=Yes
|Charter=Yes
|Chair=Yes
|SolKatz=No
|Committer=No
}}
{{OSGeo Member FormEdit}}
===[http://www.ist.supsi.ch/index.php?page=Collaboratori_mcannata Massimiliano Cannata]===

[[File:Massimiliano_cannata.jpg|thumb|right|100px|Massimiliano Cannata]]

Professor in enginering geomatics at University of Applied Sciences and Arts of Southern Switzerland (SUPSI)

;Location:
----------
Campus Trevano, Canobbio, Switzerland

;Short Bio
--------------
Massimiliano received his PhD in Gedoesy and Geomatics after his master degree in environmental engineering at the Politecnico di Milano. Since 2007 he's the head of the geomatic division within the Institute of Earth Sciences (www.ist.supsi.ch) in Switzerland.

He participated in the community since it's inception at various levels. He's a director of the Open Source Geospatial foundation (OSGeo) and member of the project steering committee of the projects and ZOO (http://www.zoo-project.org). From 2006 to 2016 he was also PSC member of the GIS GRASS (http://grass.osgeo.org). He's group lead the developement of the istSOS project (http://istsos.org) implementing open standards for sensor observation services. Co-chair of the UnitedNation committee and of the Open Geoscience committee.

;Research
---------------
Massimiliano start his research activities working on methodologies for LiDAR data filtering and analyses, but from 2002, he start focusing his activities on the GIS embedded environmental modeling, geospatial Web technologies and interoperability and the sensor Web.

He conducted a large number of research project and consultancies for the local government administration in the field of spatial data infrastructure, natural hazard mitigation, environmental monitoring network, decision support systems. He also leads the scientific execution of projects funded by the World Bank, the European Union and gained extensive experince in working with developing countries.

;Education
---------------
Currently Massimiliano is teaching Gematic I, Geomatic II and GIS in the Bachelor of Science SUPSI in Civil engineering and Geoinformation and 3D data in the Bachelor of Science SUPSI in Architeture. From 2006 to 2010 Lecturer ex cathedra at the Academy of Architecture in Mendrisio.

;OSGeo Experience
------------------
[[File:OSGeo_board.png|link=OSGeo_Advocate#OSGeo_Board_Members]] - [[File:OSGeo_charter.png|link=OSGeo_Advocate#OSGeo_Charter_Members]] - [[File:OSGeo_committee.png|link=OSGeo_Advocate#Developers_and_Committee_Members]] - [[File:OSGeo_psc.png|link=OSGeo_Advocate#Voted_position_in_an_OSGeo_community]] - [[File:OSGeo_user.png|link=OSGeo_Advocate#OSGeo_Community_Members]]

;* [[UnitedNations Committee|UnitedNations_Committee]] co-Chair
;* [[Open_Geoscience_Committee|Open Geoscience Committee]] co-Chair
:* [[http://istsos.org|istSOS]] PSC chair
:* GRASS PSC member (from 2006 to 20016)
:* ZOO PSC member (from 2010)
:* Italian OSGeo Chapter founder
:* Italian OSGeo liason officer (from 2004 to 2008)

;Contact:
---------
: Email: massimiliano.cannata AT supsi DOT ch
: Phone (work): +41 (0)58 666 62 14

;Spoken Language(s):
--------------------
: English, Italian

Profile last updated: 19 Aug 2016

[[Category:OSGeo Member]]
[[Category:Former_OSGeo_Director]]
[[Category:OSGeo Charter Member]]
[[Category:OSGeo Advocate]]

OSGeo Budget 2021

2021-01-17T16:34:50Z

Maxi: /* Community Projects */

Draft budget for 2021, see [[OSGeo Budget 2020]] and [[Finance Committee#Documents]] for prior years.

Total Approved Budget for 2020: $220,612 USD

Total Approved Budget for 2021: TBD

== OSGeo Board ==

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.

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! Board
! 2020
! 2020 Actual
! 2021 Draft
! Notes
|-
| Admin
| style="text-align:right;" | 2,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| Operational expenses including liability insurance, tax filing fees, quickbooks, mail, IRS, bank fees.
|-
| Travel
| style="text-align:right;" | 20,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| Travel to main FOSS4G, F2F meeting and regional/representative events
|-
| Partners and Sponsors
| style="text-align:right;" | 2,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| Relationship building, attending b2b functions, foss4g/foss4ge/foss4gna/foss4g-asia breakfast meetings. Meetings with sponsors during events
|}

Total Board Budget for 2020: $24,000 USD

Total Board Budget for 2021: TBD

== OSGeo Committees ==

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.

* Code of Conduct Committee
* Conference Committee
* GeoForAll - committee acting as advisory board for the GeoForAll Initiative
* Incubation Committee - committee providing hands-on support for project teams adopting open source principles and practice.
* Marketing Committee - outreach and advocacy support
* Open GeoScience Committee
* System Administration Committee - foundation infrastructure
* UN Committee - committee responsible for our participation in the UN Open GIS program

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! OSGeo Committees
! 2020
! 2020 Actual
! 2021 Requested
! Notes
|-
| SAC
| style="text-align:right;" | 28,350
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| Open GeoScience
| style="text-align:right;" | 7,562
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| Conference
| style="text-align:right;" | 1,000 [0]
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| Marketing
| style="text-align:right;" | 22,000 [23,800]
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| GeoForAll
| style="text-align:right;" | 5,000 [8,000]
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| UN Committee
| style="text-align:right;" | 6,000 [9,000]
| style="text-align:right;" | 0
| style="text-align:right;" | 9,000
|
We would like to request three prizes, each to the value of USD 3,000. The number of prizes and amounts are based on previous years, however, we understand that 2020 was a difficult year and that there could be budget constraints because the conference could not take place.

We plan to arrange the OSGeo Educational Challenge similarly to that in 2018 [1] and 2019 [2], for which the material is now available on the OSGeo Wiki, see e.g. [3], [4] and [5]. The challenge supports the objectives of the OSGeo UN Committee [6], i.e. promoting the development and use of open source software that meets UN needs and supports the aims of the UN. For various reasons, we were not able to arrange the challenge in 2020, but we are planning to have the next one in 2021. Vicky Vergara has already expressed interest in mentoring a challenge related to developing training material for pgrouting. The other two challenges are planned on topics related to COVID-19 (with QGIS) and Geo Artificial Intelligence (GeoAI), a topic of interest in the UN Open GIS initiative.

[1] https://www.osgeo.org/foundation-news/osgeo-un-committee-educational-challenge/ 
[2] https://www.osgeo.org/foundation-news/2019-osgeo-un-committee-educational-challenge/ 
[3] https://wiki.osgeo.org/wiki/Training_Material_for_UN_Open_GIS_OpenData 
[4] https://wiki.osgeo.org/wiki/Training_Material_for_UN_Open_GIS_Spiral_3 
[5] https://wiki.osgeo.org/wiki/Training_Material_for_2019_UN_Open_GIS_Challenge_2_-_Open_geospatial_data_and_software_for_UN_SDG_16,_Peace_justice_and_open_institutions 
[6] https://www.osgeo.org/initiatives/un-initiative/ 

|-
| Incubation Committee
| style="text-align:right;" | 10,000 [12,000]
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| No operational budget requested, funds requested strictly to be used to support team/mentor activities towards completing OSGeo incubation requirements. Board note: Projects under incubation have to ask the Incubation committee for the part of their budget regarding incubation activities.
|}

Total Committees Budget for 2020: $79,912 USD

Total Committees Budget for 2021: TBD

== OSGeo Initiatives ==

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.

* FOSS4G - event series produced in collaboration with the conference committee and local chapters
* GeoForAll - education and research program produced in collaboration with our partners
* Incubation - mentor program for open source projects to be recognized as OSGeo project
* Local Chapters - board outreach initiative establishing regional OSGeo groups for direct grassroots advoacacy
* GSoC - coordinate participation in google-summer-of-code and code-in activities
* Travel Grant Program - provides assistance for attending OSGeo events

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! OSGeo Initiatives
! 2020
! 2020 Actual
! 2021 Requested
! Notes
|-
| FOSS4G
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| Managed by Conference Committee. Seed money for 2021 will be allocated by the board when estimate numbers become available.
|-
| Local Chapters
| style="text-align:right;" | 5,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| 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)
|-
| GSoC
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| Managed by board.
|-
| Travel Grant Program
| style="text-align:right;" | 25,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| 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. Board note: gvSIG can apply for Travel grant here for their event.
|-
| Events and Code Sprints
| style="text-align:right;" | 15,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| 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.) 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.
|-
| Community Projects
| style="text-align:right;" | 10,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| 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). Board note: Budgeted approx. 500$ for each project. To be amended if we hit the ceiling of the budget.
|-
| OSGeo4W
| style="text-align:right;" | 4,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| Board note: Joint initiative with QGIS.org. Project advised to build a broader volunteer base. Incubation program can be of help in this regard.
|-
| GRASS website
| style="text-align:right;" | 6,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| 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.
|}

Total Initiatives Budget for 2020: $65,000 USD

Total Initiatives Budget for 2021: TBD

= Projects =

== OSGeo Projects ==

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.

Notes:

* We have reached out (2020) to the projects mailing list with a default suggestion of 2000 for any project that responds
* Projects with a plan may of course ask for increased funding
* 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.
* If a project did not respond (or runs into an unforeseen expense) please contact the board throughout the year as budgets can be amended

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! OSGeo Project
! 2020
! 2020 Actual
! 2021 Requested
! Notes
|-
| deegree
| style="text-align:right;" | 2,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| GDAL/OGR
| style="text-align:right;" | 2,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| GeoMOOSE
| style="text-align:right;" | 2,500
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| GeoNetwork
| style="text-align:right;" | 2,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| GeoNode
| style="text-align:right;" | 2,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| GEOS
| style="text-align:right;" | 2,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| GeoServer
| style="text-align:right;" | 5,000
| style="text-align:right;" | 5,000
| style="text-align:right;" | 3,000
| [[GeoServer Budget 2021]]
|-
| GeoTools
| style="text-align:right;" | 5,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| GRASS GIS
| style="text-align:right;" | 3,000
| style="text-align:right;" | 0
| style="text-align:right;" | 2,500
| [[GRASS GIS Budget 2021]]
|-
| gvSIG
| style="text-align:right;" | 2,000
| style="text-align:right;" | 0
| style="text-align:right;" | 4,000
| Details of the budget at [[GvSIG Budget 2021]]
|-
| Mapbender
| style="text-align:right;" | 2,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| MapServer
| style="text-align:right;" | 2,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| Marble
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| OpenLayers
| style="text-align:right;" | 3,000
| style="text-align:right;" | 0
| style="text-align:right;" | 3,000
| [[OpenLayers Budget 2021]]
|-
| OTB
| style="text-align:right;" | 2,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| OSGeoLive
| style="text-align:right;" | 2,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| PostGIS
| style="text-align:right;" | 2,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| PROJ
| style="text-align:right;" | 1,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| pycsw
| style="text-align:right;" | 3,200
| style="text-align:right;" | 0 [[Pycsw_budget_2020|(link)]]
| style="text-align:right;" | 0
|
|-
| PyWPS
| style="text-align:right;" | 2,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| QGIS
| style="text-align:right;" | 5,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|}

Total Projects Budget for 2020: $51,700 USD

Total Projects Budget for 2021: TBD

== Community Projects ==

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)

* actinia
* FDO
* GC2/Vidi
* GeoExt
* GeoHealthCheck
* Geomajas
* GeoServer Client PHP
* GeoWebCache
* istSOS
* Loader
* MapGuide Open Source
* Mapfish
* Opticks
* OSGeo4W
* OSSIM
* OWSLib
* pgRouting
* PortableGIS
* Pronto Raster
* pygeoapi
* rasdaman
* TEAM Engine
* ZOO-Project

Some incubation projects are not yet set up as part of OSGeo community:

* Oskari

Some guidance is offered by individual projects below.

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.

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! Community Project
! 2020
! 2020 Actual
! 2021 Requested
! Notes
|-
| ZOO-Project
| style="text-align:right;"| 1,250 + 500
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| 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.
|-
| pgRouting
| style="text-align:right;"| 4,000 + 500
| style="text-align:right;" | 0
| style="text-align:right;" | 4,000 + 500 ([https://wiki.osgeo.org/wiki/PgRouting_Budget#2021 link])
| 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.
|-
| istSOS
| style="text-align:right;" | 4,000 + 500
| style="text-align:right;" | 0
| style="text-align:right;" | 4,000 + 500 ([https://wiki.osgeo.org/wiki/Istsos_Budget_2021 link])
| 2020 Board note: 4,000 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.
|-
| OSGeo4W
| style="text-align:right;" | 4,000 + 500
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| pygeoapi
| style="text-align:right;" | 500
| style="text-align:right;" | 322 ([https://github.com/geopython/pygeoapi/wiki/OSGeo-Budget-2020 link])
| style="text-align:right;" | 0
|
|-
| GeoHealthCheck
| style="text-align:right;" | 500
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| OWSLib
| style="text-align:right;" | 500
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
|}

= Events =

== Community Events ==

We have set aside a budget for community events in 2021:

* Supporting community building events is distinct from the development focused code-sprints below
* We are inviting community members to contact us about events (rather than try and adjust their event to fit into our code sprint guidelines)
* 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.
* Please note our [https://github.com/OSGeo/osgeo/blob/master/board/documents/osgeo_financial_guidance.pdf financial guidance document]

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! Event Request
! 2020
! 2020 Actual
! 2021 Requested
! Notes
|-
| QGIS Developer Meeting and User Conference
| style="text-align:right;" | 3,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| FOSS4G SotM Oceania Community Day
| style="text-align:right;" | 1500
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|}

== Code Sprints ==

We have asked project teams for guidance to help set our code sprint budget:

* 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.
* Out priority is to share the risk with organizers allowing access to funds early to book facilities as required
* 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.

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! Sprint Request
! 2020
! 2020 Actual
! 2021 Requested
! Notes
|-
| OSGeo Code Sprint
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| No financial request made, seed money exists from previous years. [[OSGeo Code Sprint 2020|Event planning]] is well under way.
|-
| GeoServer Code Sprint
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| PostGIS Code Sprint
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| GRASS GIS Community Sprint
| style="text-align:right;" | 2,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|}

= Approval and Amendments =

* Budget Meeting: [[Board Meeting 2021-01-18]]
* Loomio Motion:
* Amendments: TBD

[[Category:Budget]]
[[Category:Finance]]

Istsos Budget 2021

2021-01-17T16:29:24Z

Maxi: Created page with "== istSOS Budget 2020 == TOTAL = 4'500 * Incubation sprint & tasks (travel grants for community/code sprints): 4'000 USD Jul/Aug, 5 days in Malaga * House rent: 1'500..."

== istSOS Budget 2020 ==

TOTAL = 4'500

* Incubation sprint & tasks (travel grants for community/code sprints): 4'000 USD
Jul/Aug, 5 days in Malaga
* House rent: 1'500 USD
* Travel grants for community members and Mentor: 2'500 USD

* Marketing (T-shirts for sprints): 500 USD

OSGeo Budget 2020

2019-12-31T05:07:42Z

Maxi:

'''DRAFT'''

Draft budget to be discussed in December board meeting, see [[OSGeo Budget 2019]] and [[Finance Committee#Documents]] for prior years.

Total Approved Budget for 2019: $230,150 USD

Total Approved Budget for 2020: $TBD USD

== OSGeo Board ==

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.

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! Board
! 2019
! 2019 Actual
! 2020
! Notes
|-
| Admin
| style="text-align:right;" | 3,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| Operational expenses including liability insurance, tax filing fees, accountant, bank fees.
|-
| Travel
| style="text-align:right;" | 22,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| Travel to main FOSS4G and F2F meeting (15k), and regional/representative events (7k)
|-
| Partners
| style="text-align:right;" | 2,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| Relationship building, attending b2b functions, foss4g/foss4ge/foss4gna/foss4g-asia breakfast meetings
|-
| Sponsors
| style="text-align:right;" | 2,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| Meetings with sponsors during events
|}

Total Board Budget for 2019: $29,000 USD

Total Board Budget for 2020: $TBD USD

== OSGeo Committees ==

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.

* Code of Conduct Committee
* Conference Committee
* GeoForAll - committee acting as advisory board for the GeoForAll Initiative
* Incubation Committee - committee providing hands-on support for project teams adopting open source principles and practice.
* Marketing Committee - outreach and advocacy support
* Open GeoScience Committee
* System Administration Committee - foundation infrastructure
* UN Committee - committee responsible for our participation in the UN Open GIS program

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! OSGeo Committees
! 2019
! 2019 Actual
! 2020
! Notes
|-
| SAC
| style="text-align:right;" | 23,750
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| Open GeoScience
| style="text-align:right;" | 6,100
| style="text-align:right;" | 1064 (EGU event) + X
| style="text-align:right;" | 7,562
|
|-
| Conference
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| Marketing
| style="text-align:right;" | 27,600
| style="text-align:right;" | 22,600
| style="text-align:right;" | 23,800
| See [[Marketing Committee Budget 2020]] for activities
|-
| GeoForAll
| style="text-align:right;" | 3,000
| style="text-align:right;" | 0
| style="text-align:right;" | 8,000
| There was no requests for G4A prizes in 2019.
For 2020, an activity similar to Hacktober/GCI/bug bounty is planned. This will be opened to everyone. The award for participating will be a t-shirt. $5,000 is requested for the printing and shipping of 250 t-shirts. The aim of the activity will be to encourage existing or new members to contribute to either the code or docs of OSGeo projects. This would be the higher priority activity for 2020. 
Then we would like to request two awards of $1500 (total $3000) for a microgrant award. The idea with the grant is to encourage G4A labs to contribute and work together.
|-
| UN Committee
| style="text-align:right;" | 11,000
| style="text-align:right;" | 1,051 euro + 6,000 $
| style="text-align:right;" | 9,000
| Activities of the Committe available at https://wiki.osgeo.org/wiki/UnitedNations_Committee
Budget 2019: the expenses are less because a Field Mission in South Sudan was cancelled;
Budget 2020: 2 OSGeo Challenges (6,000) + 3,000 for the Partecipation at the "6th International Symposium on Partnership for Technology in Peacekeeping" 22-26 June 2020)
|-
| Incubation Committee
| style="text-align:right;" | 10,000
| style="text-align:right;" | 10,000
| style="text-align:right;" | 12,000
| No operational budget requested (board's community initiative takes care of that). Funds requested strictly to be used to support team/mentor activities towards completing osgeo incubation requirements.
|}

Total Committees Budget for 2019: $76,450 USD

Total Committees Budget for 2020: $TBD USD

== OSGeo Initiatives ==

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.

* FOSS4G - event series produced in collaboration with the conference committee and local chapters
* GeoForAll - education and research program produced in collaboration with our partners
* Incubation - mentor program for open source projects to be recognized as OSGeo project
* Local Chapters - board outreach initiative establishing regional OSGeo groups for direct grassroots advoacacy
* Meta CRS - interoperability initiative promoting data sharing with cross project spatial reference system compatibility
* Open GeoScience - outreach and advocacy geoscience community
* GSoC - coordinate participation in google-summer-of-code and code-in activities
* Travel Grant Program - provides assistance for attending OSGeo events

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! OSGeo Initiatives
! 2019
! 2019 Actual
! 2020
! Notes
|-
| FOSS4G
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| Managed by Conference Committee. Seed money for 2020 will be allocated by the board when estimate numbers become available.
|-
| Local Chapters
| style="text-align:right;" | 5,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| 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)
|-
| Travel Grant Program
| style="text-align:right;" | 25.000
| style="text-align:right;" |15-18,000
| style="text-align:right;" | 25,000
| (Need to check actual spend in 2019)
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.
|-
| Events and Code Sprints
| style="text-align:right;" | 15,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| 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.)
|-
| Community Projects
| style="text-align:right;" | 15,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| 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.
|}

Total Initiatives Budget for 2019: $60,000 USD

Total Initiatives Budget for 2020: $TBD USD

= Projects =

== OSGeo Projects ==

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.

Notes:

* We have reached out (2019) to the projects mailing list with a default suggestion of 2000 for any project that responds
* Projects with a plan may of course ask for increased funding
* 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.
* If a project did not respond (or runs into an unforeseen expense) please contact the board throughout the year as budgets can be amended

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! OSGeo Project
! 2019
! 2019 Actual
! 2020
! Notes
|-
| deegree
| style="text-align:right;" | 2,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| GDAL/OGR
| style="text-align:right;" | 5,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| GeoMOOSE
| style="text-align:right;" | 2,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| GeoNetwork
| style="text-align:right;" | 2,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| GeoNode
| style="text-align:right;" | 2,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| GEOS
| style="text-align:right;" | 1,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| GeoServer
| style="text-align:right;" | 7,000
| style="text-align:right;" | 7,000
| style="text-align:right;" | 5,000
| [[GeoServer Budget 2020]]
|-
| GeoTools
| style="text-align:right;" | 2,000
| style="text-align:right;" | 2,000
| style="text-align:right;" | 5,000
| [https://github.com/geotools/geotools/wiki/GeoTools-Budget-Request-2020 GeoTools Budget Request 2020]
|-
| GRASS GIS
| style="text-align:right;" | 9,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| [https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2020 GRASS GIS Budget 2020]
|-
| gvSIG
| style="text-align:right;" | 5,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| Details of the budget at [[GvSIG Budget 2020]]
|-
| Mapbender
| style="text-align:right;" | 2,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| MapServer
| style="text-align:right;" | 2,500
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| Marble
| style="text-align:right;" | 1,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| OpenLayers
| style="text-align:right;" | 3,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| [[OpenLayers_Budget_2020]]
|-
| OTB
| style="text-align:right;" | 2,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| OSGeoLive
| style="text-align:right;" | 2,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| PostGIS
| style="text-align:right;" | 3,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| PROJ
| style="text-align:right;" | N/A
| style="text-align:right;" | N/A
| style="text-align:right;" | 0
|
|-
| pycsw
| style="text-align:right;" | 3,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| [[Pycsw_budget_2020]]
|-
| PyWPS
| style="text-align:right;" | 3,200
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| QGIS
| style="text-align:right;" | 8,000
| style="text-align:right;" | 11,000
| style="text-align:right;" | 10,000
|
|}

Total Projects Budget for 2019: $64,700 USD

Total Projects Budget for 2020: $TBD USD

== Community Projects ==

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)

* actinia
* FDO
* GC2/Vidi
* GeoExt
* GeoHealthCheck
* Geomajas
* GeoServer Client PHP
* GeoWebCache
* istSOS
* Loader
* MapGuide Open Source
* Mapfish
* Opticks
* OSGeo4W
* OSSIM
* OWSLib
* pgRouting
* PortableGIS
* Pronto Raster
* pygeoapi
* rasdaman
* TEAM Engine
* ZOO-Project

Some incubation projects are not yet set up as part of OSGeo community:

* Oskari

Some guidance is offered by individual projects below:

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! Community Project
! 2019
! 2019 Actual
! 2020
! Notes
|-
| ZOO-Project
| style="text-align:right;"| up to 4,000 (need specific requests to board and incubation committee)
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| pgRouting
| style="text-align:right;"| up to 4,000 (need specific requests to board and incubation committee)
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| istSOS
| style="text-align:right;" | up to 4,000 (need specific requests to board and incubation committee)
| style="text-align:right;" | 0
| style="text-align:right;" | TBD (up to 4,000 USD?)
| see: [http://osgeo-org.1560.x6.nabble.com/istSOS-budget-2020-incubation-sprints-marketing-td5426010.html istSOS budget 2020]
|-
|}

= Events =

== Community Events ==

We are considering setting aside a budget for community events in 2020:

* Supporting community building events is distinct from the development focused code-sprints below
* We are inviting community members to contact us about events (rather than try and adjust their event to fit into our code sprint guidelines)
* 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.
* Previously we have had requests to fund a "community day" or "community sprints" as part a larger event as distinct from sponsorship, the have been funded to the best of our ability

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! Event Request
! 2019
! 2019 Actual
! 2020
! Notes
|-
| QGIS Developer Meeting and User Conference
| style="text-align:right;" | 3,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|-
| FOSS4G SotM Oceania Community Day
| style="text-align:right;" | 1500
| style="text-align:right;" | 1500
| style="text-align:right;" | 1500
|
|}

== Code Sprints ==

We have asked project teams for guidance to help set our code sprint budget:

* Please note our [[Code Sprint Guidelines]] ask for event details, budget and fundraising on your part.
* Out priority is to share the risk with organizers allowing access to funds early to book facilities as required
* 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.

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! Sprint Request
! 2019
! 2019 Actual
! 2020
! Notes
|-
| OSGeo Code Sprint
| style="text-align:right;" |
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| No financial request made yet, [[OSGeo Code Sprint 2020|event planning]] is well under way.
|-
| GeoServer Code Sprint
| style="text-align:right;" | 2,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| PostGIS Code Sprint
| style="text-align:right;" | -
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| GRASS GIS Community Sprint
| style="text-align:right;" | -
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| Small Code Sprints
| style="text-align:right;" | 10,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|}

= Approval and Amendments =

* Budget Meeting: [[Board Meeting 2019-01-21]]
* Loomio Motion: [https://www.loomio.org/d/xmEyfoPn/osgeo-budget-2019]
* Amendments: TBD

[[Category:Budget]]
[[Category:Finance]]

Istsos sprint 2019

2019-11-22T10:54:20Z

Maxi: Created page with " WHEN ------ from the 9th to the 12th December 2019 WHERE -------- - to be decided, option is @SUPSI in Lugano WHAT ---------- *Coding # istSOS2 porting from py2 to py3 # en..."

WHEN
------
from the 9th to the 12th December 2019

WHERE
--------
- to be decided, option is @SUPSI in Lugano

WHAT
----------
*Coding
# istSOS2 porting from py2 to py3
# enhancement of data gathering (json query)
# test using different Application (see uWSGI, Tornado, etc..)
# async query
# ...(pls. add more)...

*Incubation
# review incubation status
# identify and assign tasks
# finalize code provenance for included libs
# ...(pls. add more)...

WHO
---------
# Massimiliano Cannata
# Milan Antonovic
# Daniele Strigaro
# ...(pls. add yoursefl)...

TODO
-------
# preparing T-shirts
# organize snacks/food

Possible budget: see [[OSGeo Budget 2019|OSGeo_Budget_2019]]

IstSOS Incubation Graduation Checklist

2019-08-31T19:33:10Z

Maxi: /* Incubator Application Questionnaire version 2.0 */

= This page has moved =

* https://trac.osgeo.org/osgeolive/wiki/Incubator%20Application
* https://trac.osgeo.org/osgeolive/wiki/Graduation%20List

= Incubator Application Questionnaire version 2.0 =

Questions from the Incubator Application Questionnaire version 2.0. 
# Please provide the name and email address of the principal Project Owner. massimiliano dot cannata AT gmail X com
# Please provide the names and emails of co-project owners (if any). [TODO] Refer to members of the [[istSOS_Managemnt PSC_Members|TODO]].
# Please provide the names, emails and entity affiliation of all official committers. [TO BE UPDATED] Refer to https://github.com/massimiliano-cannata/istsos2/blob/master/COMMITTERS.txt 
# Please describe your Project. istSOS is an OGC SOS server implementation written in Python. istSOS allows to collect, manage and share observations from monitoring sensors according to the Sensor Observation Service standard. Along to the SOS specification, istSOS offers a number of extending features accessible trough it web admin interface and its RESTful API like data aggregation, virtual procedures, time zone reprojection, authentication and authorization, json and csv output format, and others.
# Why is OSGeo Incubation good for your project? We wish to officially demonstrate the level of quality of the project.
# What type of application does this project represent(client, server, standalone, library, etc.): istSOS is a server application, even if an administration interface is available with the package (i.e.:similarly to geoserver).
# Please describe any relationships to other open source projects. [TO COMPLETE] istSOS is part of the OSGeo-Live project.
# Please describe any relationships with commercial companies or products. WHat is the scope of this question? why not relation with government or accademy? this soud discriminatory
# Please explain how your project will use an open governance policy, ensuring decisions are made, documented and adhered to in a public manner. [TODO] All decisions are currently made at istSOS PSC meetings whose minutes is publicly shared for comments and further discussion. 
# Which open source license(s) will the source code be released under? GNU General Public License, see https://github.com/massimiliano-cannata/istsos2/blob/master/LICENSE.txt

# Please describe the maturity and history of your project. For instance,
#* What is the origin of your project (commercial, experimental, thesis or other higher education, government, or some other source)? OSGeo-Live was initially developed as a promotional distribution for handing out at FOSS4G conferences and the like, and has since grown, especially into supporting educational programs.
#* How many people actively contribute (code, documentation, other?) to the project at this time? Literally hundreds of people, as per: http://live.osgeo.org/en/sponsors.html
#* How many people have commit access to the source code repository? Literally hundreds of people, as per: http://live.osgeo.org/en/sponsors.html
#* Approximately how many users are currently using this project? Probably tens of thousands of people per year are exposed to OSGeo-Live at conferences around the world.
#* What type of users does your project attract (government, commercial, hobby, academic research, etc. )? Primarily people new to OSGeo software who want to know more.
# Do you wish to host any portion of this project using the OSGeo infrastructure? If so, what? We are already using some of OSGeo hosting, in particular, the OSGeo Issue tracker.
# Does the project support open standards? Which ones and to what extent? (OGC, w3c, etc.) Has the software been certified to any standard (CITE for example)? If not, is it the intention of the project owners to seek certification at some point? There are many projects which OSGeo-Live packages which follow OGC standards. Most OGC standards are covered. To a certain extent, OSGeo-Live follows debian packaging conventions.
# Is the code free of patents, trademarks, and do you control the copyright? OSGeo-Live is free of patents and trademarks. Copyright is owned by numerous people and organisations who have contributed to OSGeo-Live.
# Does the project include an automated build and test? The build process is mostly automated. Automated testing is not very feasible for an integration project such as OSGeo-Live, and as such most testing is manual.
# What language(s) are used in this project? (C/Java/perl/etc) Most of OSGeo-Live code is shell scripts for installing applications. The packages we bundle are written in numerous languages.
# What is the dominant written language (i.e. English, French, Spanish, German, etc) of the core developers? Primary document is English. Documentation is translated into over 10 languages.
# What is the (estimated) size of a full release of this project? How many users do you expect to download the project when it is released? Our distribution aims to fit on a 4Gig USB or DVD for a mini distribution, or 8 Gig USB for full distribution.
# Do you already have an OSGeo Mentor to guide you through the incubation process? Yes, Jody Garnett.

= OSGeo-Live Incubation Checklist =
This page addresses the status of OSGeo-Live as per version 2.0 of the [http://www.osgeo.org/incubator/process/project_graduation_checklist.html OSGeo Incubation Checklist]. It is derived from the [http://wiki.osgeo.org/wiki/Project_Graduation_Checklist#Document_Status wiki] version of the document.

For the purposes of incubation auditing, the scope of the OSGeo-Live project comprises of the scripts and processes used to build OSGeo-Live, but doesn't include the specific projects being packages (many of which are addressing OSGeo Incubation separately in their own right).

= Incubation Checklist =

== Open ==

The project has demonstrated that it has an open, active and healthy user and developer community:
# Open: projects are expected to function in an open and public manner and include:
#* Open source license(s),
#**YES: Code is under LGPL, Documentation under Creative Commons, as per http://live.osgeo.org/en/copyright.html
#* Open communication channels,
#**YES: We have an active email list, and hold weekly IRC meetings during build cycles. http://wiki.osgeo.org/wiki/Live_GIS_Disc#Contact_Us
#* Open decision making process,
#**YES: Decision making process is documented at https://wiki.osgeo.org/wiki/Live_GIS_Management
# Active and healthy community:
#* The project should have a community of developers and users who actively collaborate and support each other in a healthy way. Eg. collaboration on project activities such as testing, release and feature development.
#**YES: A few hundred people have contributed to OSGeo-Live. Most contributions have been in writing application installer scripts, associated documentation, as well as translations. A list of contributors are at: http://live.osgeo.org/en/sponsors.html
#* Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organisations. Eg. The project is resilient enough to sustain loss of a developer or supporting organisation, often referred to as having a high [http://en.wikipedia.org/wiki/Bus_factor bus factor]. Decisions are made openly instead of behind closed doors, which empowers all developers to take ownership of the project and facilitates spreading of knowledge between current and future team members.
#**YES: Contributors come from a wide range of organisations (as seen by email addresses of contributors). Sponsoring organisations are also listed at: http://live.osgeo.org/en/sponsors.html

== Copyright and License ==

We need to ensure that the project owns or otherwise has obtained the ability to release the project code by completing the following steps:
# All project source code is available under an Open Source license. YES: Code is under LGPL, as per http://live.osgeo.org/en/copyright.html
# Project documentation is available under an open license, such as Creative Commons. YES: Documentation is under Creative Commons licence, as per http://live.osgeo.org/en/copyright.html
# 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. TBD: Provenance Review is required.
# The project maintains a list of all copyright holders identified in the Provenance Review Document. YES: All contributors are listed at: http://live.osgeo.org/en/sponsors.html
# All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived. YES: All contributors have publicly accepted the terms of the OSGeo-Live license. This is archived in the [http://lists.osgeo.org/mailman/listinfo/live-demo OSGeo-Live email list]. The process is described here: http://wiki.osgeo.org/wiki/Live_GIS_Disc#Subversion

== Processes ==

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

== Documentation ==

# The project has user documentation:
#* Including sufficient detail to guide a new user through performing the core functionality provided by the application. 
YES: The project has extensive Project Overviews and Quickstarts, specifically designed for getting new users up and running quickly. These are linked from: http://live.osgeo.org/en/index.html and http://live.osgeo.org/en/overview/overview.html
# The project has developer documentation: YES: How to add a new project to OSGeo-Live is covered in detail. Linked from: http://wiki.osgeo.org/wiki/Live_GIS_Disc#How_to_add_a_project_to_OSGeoLive
#* Including checkout and build instructions. YES: Linked from: http://wiki.osgeo.org/wiki/Live_GIS_Disc#How_to_add_a_project_to_OSGeoLive
#* Including commented code, ideally published for developer use. Examples: javadocs for Java applications, or Sphinx documentation for Python applications. YES: Code is primarily relatively small shell script files, which include comment. 
#* Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project's programming conventions. <br\>YES

==Release Procedure==

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

# The project follows a defined release process:
#* Which includes execution of the testing process before releasing a stable release. The project has an established build and release process, but it needs to be more clearly documented. Some information here: http://wiki.osgeo.org/wiki/Live_GIS_Disc#Build_Process . The release management role is well established, but not documented. This includes setting up a schedule, sending out press releases, chasing up projects, etc, etc.
# The project follows a documented testing process. Ideally, this includes both automated and manual testing Ideally this includes documented conformance to set quality goals, such as reporting Percentage Code Coverage of Unit Tests. OSGeo-Live is an integration project, which is difficult to create automated testing for. Instead we rely on manual testing. The testing process is well practiced, but needs to be documented better.
# Release and testing processes provide sufficient detail for an experienced programmer to follow. TBD: Waiting on improved documentation.

IstSOS Incubation Graduation Checklist

2019-08-31T18:51:09Z

Maxi:

= This page has moved =

* https://trac.osgeo.org/osgeolive/wiki/Incubator%20Application
* https://trac.osgeo.org/osgeolive/wiki/Graduation%20List

= Incubator Application Questionnaire version 2.0 =

Questions from the Incubator Application Questionnaire version 2.0. 
# Please provide the name and email address of the principal Project Owner. massimiliano dot cannata AT gmail X com
# Please provide the names and emails of co-project owners (if any). [TODO] Refer to members of the [[istSOS_Managemnt PSC_Members|TODO]].
# Please provide the names, emails and entity affiliation of all official committers. [TO BE UPDATED] Refer to https://github.com/massimiliano-cannata/istsos2/blob/master/COMMITTERS.txt 
# Please describe your Project. istSOS is an OGC SOS server implementation written in Python. istSOS allows to collect, manage and share observations from monitoring sensors according to the Sensor Observation Service standard. Along to the SOS specification, istSOS offers a number of extending features accessible trough it web admin interface and its RESTful API like data aggregation, virtual procedures, time zone reprojection, authentication and authorization, json and csv output format, and others.
# Why is OSGeo Incubation good for your project? We wish to officially demonstrate the level of quality of the project.
# What type of application does this project represent(client, server, standalone, library, etc.): istSOS is a server application, even if an administration interface is available with the package (i.e.:similarly to geoserver).
# Please describe any relationships to other open source projects. [TO COMPLETE] istSOS is part of the OSGeo-Live project.
# Please describe any relationships with commercial companies or products. WHat is the scope of this question? why not relation with government or accademy? this soud discriminatory
# Please explain how your project will use an open governance policy, ensuring decisions are made, documented and adhered to in a public manner. [TODO] All decisions are currently made at istSOS PSC meetings whose minutes is publicly shared for comments and further discussion. 

# Which open source license(s) will the source code be released under? The licenses used for the OSGeo-Live build scripts and documentation are: Creative Commons Attribution-ShareAlike 3.0 Unported License for Quickstarts, Creative Commons Attribution 3.0 Unported License for Project Overviews, LGPL version >=2.1 for the install scripts, One of the OSI approved Open Source licenses for installed applications, Public domain, CC-By-SA, and Open Data Commons Open Database License (ODbL) for data
# Please describe the maturity and history of your project. For instance,
#* What is the origin of your project (commercial, experimental, thesis or other higher education, government, or some other source)? OSGeo-Live was initially developed as a promotional distribution for handing out at FOSS4G conferences and the like, and has since grown, especially into supporting educational programs.
#* How many people actively contribute (code, documentation, other?) to the project at this time? Literally hundreds of people, as per: http://live.osgeo.org/en/sponsors.html
#* How many people have commit access to the source code repository? Literally hundreds of people, as per: http://live.osgeo.org/en/sponsors.html
#* Approximately how many users are currently using this project? Probably tens of thousands of people per year are exposed to OSGeo-Live at conferences around the world.
#* What type of users does your project attract (government, commercial, hobby, academic research, etc. )? Primarily people new to OSGeo software who want to know more.
# Do you wish to host any portion of this project using the OSGeo infrastructure? If so, what? We are already using some of OSGeo hosting, in particular, the OSGeo Issue tracker.
# Does the project support open standards? Which ones and to what extent? (OGC, w3c, etc.) Has the software been certified to any standard (CITE for example)? If not, is it the intention of the project owners to seek certification at some point? There are many projects which OSGeo-Live packages which follow OGC standards. Most OGC standards are covered. To a certain extent, OSGeo-Live follows debian packaging conventions.
# Is the code free of patents, trademarks, and do you control the copyright? OSGeo-Live is free of patents and trademarks. Copyright is owned by numerous people and organisations who have contributed to OSGeo-Live.
# Does the project include an automated build and test? The build process is mostly automated. Automated testing is not very feasible for an integration project such as OSGeo-Live, and as such most testing is manual.
# What language(s) are used in this project? (C/Java/perl/etc) Most of OSGeo-Live code is shell scripts for installing applications. The packages we bundle are written in numerous languages.
# What is the dominant written language (i.e. English, French, Spanish, German, etc) of the core developers? Primary document is English. Documentation is translated into over 10 languages.
# What is the (estimated) size of a full release of this project? How many users do you expect to download the project when it is released? Our distribution aims to fit on a 4Gig USB or DVD for a mini distribution, or 8 Gig USB for full distribution.
# Do you already have an OSGeo Mentor to guide you through the incubation process? Yes, Jody Garnett.

= OSGeo-Live Incubation Checklist =
This page addresses the status of OSGeo-Live as per version 2.0 of the [http://www.osgeo.org/incubator/process/project_graduation_checklist.html OSGeo Incubation Checklist]. It is derived from the [http://wiki.osgeo.org/wiki/Project_Graduation_Checklist#Document_Status wiki] version of the document.

For the purposes of incubation auditing, the scope of the OSGeo-Live project comprises of the scripts and processes used to build OSGeo-Live, but doesn't include the specific projects being packages (many of which are addressing OSGeo Incubation separately in their own right).

= Incubation Checklist =

== Open ==

The project has demonstrated that it has an open, active and healthy user and developer community:
# Open: projects are expected to function in an open and public manner and include:
#* Open source license(s),
#**YES: Code is under LGPL, Documentation under Creative Commons, as per http://live.osgeo.org/en/copyright.html
#* Open communication channels,
#**YES: We have an active email list, and hold weekly IRC meetings during build cycles. http://wiki.osgeo.org/wiki/Live_GIS_Disc#Contact_Us
#* Open decision making process,
#**YES: Decision making process is documented at https://wiki.osgeo.org/wiki/Live_GIS_Management
# Active and healthy community:
#* The project should have a community of developers and users who actively collaborate and support each other in a healthy way. Eg. collaboration on project activities such as testing, release and feature development.
#**YES: A few hundred people have contributed to OSGeo-Live. Most contributions have been in writing application installer scripts, associated documentation, as well as translations. A list of contributors are at: http://live.osgeo.org/en/sponsors.html
#* Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organisations. Eg. The project is resilient enough to sustain loss of a developer or supporting organisation, often referred to as having a high [http://en.wikipedia.org/wiki/Bus_factor bus factor]. Decisions are made openly instead of behind closed doors, which empowers all developers to take ownership of the project and facilitates spreading of knowledge between current and future team members.
#**YES: Contributors come from a wide range of organisations (as seen by email addresses of contributors). Sponsoring organisations are also listed at: http://live.osgeo.org/en/sponsors.html

== Copyright and License ==

We need to ensure that the project owns or otherwise has obtained the ability to release the project code by completing the following steps:
# All project source code is available under an Open Source license. YES: Code is under LGPL, as per http://live.osgeo.org/en/copyright.html
# Project documentation is available under an open license, such as Creative Commons. YES: Documentation is under Creative Commons licence, as per http://live.osgeo.org/en/copyright.html
# 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. TBD: Provenance Review is required.
# The project maintains a list of all copyright holders identified in the Provenance Review Document. YES: All contributors are listed at: http://live.osgeo.org/en/sponsors.html
# All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived. YES: All contributors have publicly accepted the terms of the OSGeo-Live license. This is archived in the [http://lists.osgeo.org/mailman/listinfo/live-demo OSGeo-Live email list]. The process is described here: http://wiki.osgeo.org/wiki/Live_GIS_Disc#Subversion

== Processes ==

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

== Documentation ==

# The project has user documentation:
#* Including sufficient detail to guide a new user through performing the core functionality provided by the application. 
YES: The project has extensive Project Overviews and Quickstarts, specifically designed for getting new users up and running quickly. These are linked from: http://live.osgeo.org/en/index.html and http://live.osgeo.org/en/overview/overview.html
# The project has developer documentation: YES: How to add a new project to OSGeo-Live is covered in detail. Linked from: http://wiki.osgeo.org/wiki/Live_GIS_Disc#How_to_add_a_project_to_OSGeoLive
#* Including checkout and build instructions. YES: Linked from: http://wiki.osgeo.org/wiki/Live_GIS_Disc#How_to_add_a_project_to_OSGeoLive
#* Including commented code, ideally published for developer use. Examples: javadocs for Java applications, or Sphinx documentation for Python applications. YES: Code is primarily relatively small shell script files, which include comment. 
#* Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project's programming conventions. <br\>YES

==Release Procedure==

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

# The project follows a defined release process:
#* Which includes execution of the testing process before releasing a stable release. The project has an established build and release process, but it needs to be more clearly documented. Some information here: http://wiki.osgeo.org/wiki/Live_GIS_Disc#Build_Process . The release management role is well established, but not documented. This includes setting up a schedule, sending out press releases, chasing up projects, etc, etc.
# The project follows a documented testing process. Ideally, this includes both automated and manual testing Ideally this includes documented conformance to set quality goals, such as reporting Percentage Code Coverage of Unit Tests. OSGeo-Live is an integration project, which is difficult to create automated testing for. Instead we rely on manual testing. The testing process is well practiced, but needs to be documented better.
# Release and testing processes provide sufficient detail for an experienced programmer to follow. TBD: Waiting on improved documentation.

IstSOS Incubation Graduation Checklist

2019-08-31T18:29:11Z

Maxi:

= This page has moved =

* https://trac.osgeo.org/osgeolive/wiki/Incubator%20Application
* https://trac.osgeo.org/osgeolive/wiki/Graduation%20List

= Incubator Application Questionnaire version 2.0 =

Questions from the Incubator Application Questionnaire version 2.0. 
# Please provide the name and email address of the principal Project Owner. massimiliano dot cannata AT gmail X com
# Please provide the names and emails of co-project owners (if any). Refer to members of the [[istSOS_Managemnt PSC_Members|TODO]].
# Please provide the names, emails and entity affiliation of all official committers. Refer to https://github.com/massimiliano-cannata/istsos2/blob/master/COMMITTERS.txt TO BE UPDATED
# Please describe your Project. istSOS is an OGC SOS server implementation written in Python. istSOS allows to collect, manage and share observations from monitoring sensors according to the Sensor Observation Service standard. Along to the SOS specification, istSOS offers a number of extending features accessible trough it web admin interface and its RESTful API like data aggregation, virtual procedures, time zone reprojection, authentication and authorization, json and csv output format, and others.
# Why is OSGeo Incubation good for your project? We wish to officially demonstrate the level of quality of the project.
# What type of application does this project represent(client, server, standalone, library, etc.): istSOS is a server application, even if an administration interface is available with the package (i.e.:similarly to geoserver).
# Please describe any relationships to other open source projects. istSOS is part of the OSGeo-Live project. [COMPLETE]

# Please describe any relationships with commercial companies or products. Numerous organisations provide resources to support OSGeo-Live. These are listed at: http://live.osgeo.org/en/sponsors.html
# Please explain how your project will use an open governance policy, ensuring decisions are made, documented and adhered to in a public manner. All decisions are currently made on public email lists or publicly archived IRC. (There have been a few times where personally, financially, or politically sensitive matters have been taken off list, but these situations are rare.)
# Which open source license(s) will the source code be released under? The licenses used for the OSGeo-Live build scripts and documentation are: Creative Commons Attribution-ShareAlike 3.0 Unported License for Quickstarts, Creative Commons Attribution 3.0 Unported License for Project Overviews, LGPL version >=2.1 for the install scripts, One of the OSI approved Open Source licenses for installed applications, Public domain, CC-By-SA, and Open Data Commons Open Database License (ODbL) for data
# Please describe the maturity and history of your project. For instance,
#* What is the origin of your project (commercial, experimental, thesis or other higher education, government, or some other source)? OSGeo-Live was initially developed as a promotional distribution for handing out at FOSS4G conferences and the like, and has since grown, especially into supporting educational programs.
#* How many people actively contribute (code, documentation, other?) to the project at this time? Literally hundreds of people, as per: http://live.osgeo.org/en/sponsors.html
#* How many people have commit access to the source code repository? Literally hundreds of people, as per: http://live.osgeo.org/en/sponsors.html
#* Approximately how many users are currently using this project? Probably tens of thousands of people per year are exposed to OSGeo-Live at conferences around the world.
#* What type of users does your project attract (government, commercial, hobby, academic research, etc. )? Primarily people new to OSGeo software who want to know more.
# Do you wish to host any portion of this project using the OSGeo infrastructure? If so, what? We are already using some of OSGeo hosting, in particular, the OSGeo Issue tracker.
# Does the project support open standards? Which ones and to what extent? (OGC, w3c, etc.) Has the software been certified to any standard (CITE for example)? If not, is it the intention of the project owners to seek certification at some point? There are many projects which OSGeo-Live packages which follow OGC standards. Most OGC standards are covered. To a certain extent, OSGeo-Live follows debian packaging conventions.
# Is the code free of patents, trademarks, and do you control the copyright? OSGeo-Live is free of patents and trademarks. Copyright is owned by numerous people and organisations who have contributed to OSGeo-Live.
# Does the project include an automated build and test? The build process is mostly automated. Automated testing is not very feasible for an integration project such as OSGeo-Live, and as such most testing is manual.
# What language(s) are used in this project? (C/Java/perl/etc) Most of OSGeo-Live code is shell scripts for installing applications. The packages we bundle are written in numerous languages.
# What is the dominant written language (i.e. English, French, Spanish, German, etc) of the core developers? Primary document is English. Documentation is translated into over 10 languages.
# What is the (estimated) size of a full release of this project? How many users do you expect to download the project when it is released? Our distribution aims to fit on a 4Gig USB or DVD for a mini distribution, or 8 Gig USB for full distribution.
# Do you already have an OSGeo Mentor to guide you through the incubation process? Yes, Jody Garnett.

= OSGeo-Live Incubation Checklist =
This page addresses the status of OSGeo-Live as per version 2.0 of the [http://www.osgeo.org/incubator/process/project_graduation_checklist.html OSGeo Incubation Checklist]. It is derived from the [http://wiki.osgeo.org/wiki/Project_Graduation_Checklist#Document_Status wiki] version of the document.

For the purposes of incubation auditing, the scope of the OSGeo-Live project comprises of the scripts and processes used to build OSGeo-Live, but doesn't include the specific projects being packages (many of which are addressing OSGeo Incubation separately in their own right).

= Incubation Checklist =

== Open ==

The project has demonstrated that it has an open, active and healthy user and developer community:
# Open: projects are expected to function in an open and public manner and include:
#* Open source license(s),
#**YES: Code is under LGPL, Documentation under Creative Commons, as per http://live.osgeo.org/en/copyright.html
#* Open communication channels,
#**YES: We have an active email list, and hold weekly IRC meetings during build cycles. http://wiki.osgeo.org/wiki/Live_GIS_Disc#Contact_Us
#* Open decision making process,
#**YES: Decision making process is documented at https://wiki.osgeo.org/wiki/Live_GIS_Management
# Active and healthy community:
#* The project should have a community of developers and users who actively collaborate and support each other in a healthy way. Eg. collaboration on project activities such as testing, release and feature development.
#**YES: A few hundred people have contributed to OSGeo-Live. Most contributions have been in writing application installer scripts, associated documentation, as well as translations. A list of contributors are at: http://live.osgeo.org/en/sponsors.html
#* Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organisations. Eg. The project is resilient enough to sustain loss of a developer or supporting organisation, often referred to as having a high [http://en.wikipedia.org/wiki/Bus_factor bus factor]. Decisions are made openly instead of behind closed doors, which empowers all developers to take ownership of the project and facilitates spreading of knowledge between current and future team members.
#**YES: Contributors come from a wide range of organisations (as seen by email addresses of contributors). Sponsoring organisations are also listed at: http://live.osgeo.org/en/sponsors.html

== Copyright and License ==

We need to ensure that the project owns or otherwise has obtained the ability to release the project code by completing the following steps:
# All project source code is available under an Open Source license. YES: Code is under LGPL, as per http://live.osgeo.org/en/copyright.html
# Project documentation is available under an open license, such as Creative Commons. YES: Documentation is under Creative Commons licence, as per http://live.osgeo.org/en/copyright.html
# 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. TBD: Provenance Review is required.
# The project maintains a list of all copyright holders identified in the Provenance Review Document. YES: All contributors are listed at: http://live.osgeo.org/en/sponsors.html
# All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived. YES: All contributors have publicly accepted the terms of the OSGeo-Live license. This is archived in the [http://lists.osgeo.org/mailman/listinfo/live-demo OSGeo-Live email list]. The process is described here: http://wiki.osgeo.org/wiki/Live_GIS_Disc#Subversion

== Processes ==

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

== Documentation ==

# The project has user documentation:
#* Including sufficient detail to guide a new user through performing the core functionality provided by the application. 
YES: The project has extensive Project Overviews and Quickstarts, specifically designed for getting new users up and running quickly. These are linked from: http://live.osgeo.org/en/index.html and http://live.osgeo.org/en/overview/overview.html
# The project has developer documentation: YES: How to add a new project to OSGeo-Live is covered in detail. Linked from: http://wiki.osgeo.org/wiki/Live_GIS_Disc#How_to_add_a_project_to_OSGeoLive
#* Including checkout and build instructions. YES: Linked from: http://wiki.osgeo.org/wiki/Live_GIS_Disc#How_to_add_a_project_to_OSGeoLive
#* Including commented code, ideally published for developer use. Examples: javadocs for Java applications, or Sphinx documentation for Python applications. YES: Code is primarily relatively small shell script files, which include comment. 
#* Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project's programming conventions. <br\>YES

==Release Procedure==

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

# The project follows a defined release process:
#* Which includes execution of the testing process before releasing a stable release. The project has an established build and release process, but it needs to be more clearly documented. Some information here: http://wiki.osgeo.org/wiki/Live_GIS_Disc#Build_Process . The release management role is well established, but not documented. This includes setting up a schedule, sending out press releases, chasing up projects, etc, etc.
# The project follows a documented testing process. Ideally, this includes both automated and manual testing Ideally this includes documented conformance to set quality goals, such as reporting Percentage Code Coverage of Unit Tests. OSGeo-Live is an integration project, which is difficult to create automated testing for. Instead we rely on manual testing. The testing process is well practiced, but needs to be documented better.
# Release and testing processes provide sufficient detail for an experienced programmer to follow. TBD: Waiting on improved documentation.

IstSOS Incubation Graduation Checklist

2019-08-31T18:12:09Z

Maxi:

= This page has moved =

* https://trac.osgeo.org/osgeolive/wiki/Incubator%20Application
* https://trac.osgeo.org/osgeolive/wiki/Graduation%20List

= Incubator Application Questionnaire version 2.0 =

Questions from the Incubator Application Questionnaire version 2.0. 
# Please provide the name and email address of the principal Project Owner. massimiliano dot cannata AT gmail X com
# Please provide the names and emails of co-project owners (if any). Refer to members of the [[istSOS_Managemnt PSC_Members|TODO]].
# Please provide the names, emails and entity affiliation of all official committers. Refer to [[https://github.com/massimiliano-cannata/istsos2/blob/master/COMMITTERS.txt|istSOS committers list]] TO BE UPDATED

# Please describe your Project. istSOS is an OGC SOS server implementation written in Python. istSOS allows for managing and dispatch observations from monitoring sensors according to the Sensor Observation Service standard.
# Why is OSGeo Incubation good for your project? We wish to officially demonstrate the level of quality of the project.
# What type of application does this project represent(client, server, standalone, library, etc.): istSOS is a server application, even if an administration interface is available with the package (i.e.:similarly to geoserver).

# Please describe any relationships to other open source projects. OSGeo-Live is in communication with all the 50+ projects we package.
# Please describe any relationships with commercial companies or products. Numerous organisations provide resources to support OSGeo-Live. These are listed at: http://live.osgeo.org/en/sponsors.html
# Please explain how your project will use an open governance policy, ensuring decisions are made, documented and adhered to in a public manner. All decisions are currently made on public email lists or publicly archived IRC. (There have been a few times where personally, financially, or politically sensitive matters have been taken off list, but these situations are rare.)
# Which open source license(s) will the source code be released under? The licenses used for the OSGeo-Live build scripts and documentation are: Creative Commons Attribution-ShareAlike 3.0 Unported License for Quickstarts, Creative Commons Attribution 3.0 Unported License for Project Overviews, LGPL version >=2.1 for the install scripts, One of the OSI approved Open Source licenses for installed applications, Public domain, CC-By-SA, and Open Data Commons Open Database License (ODbL) for data
# Please describe the maturity and history of your project. For instance,
#* What is the origin of your project (commercial, experimental, thesis or other higher education, government, or some other source)? OSGeo-Live was initially developed as a promotional distribution for handing out at FOSS4G conferences and the like, and has since grown, especially into supporting educational programs.
#* How many people actively contribute (code, documentation, other?) to the project at this time? Literally hundreds of people, as per: http://live.osgeo.org/en/sponsors.html
#* How many people have commit access to the source code repository? Literally hundreds of people, as per: http://live.osgeo.org/en/sponsors.html
#* Approximately how many users are currently using this project? Probably tens of thousands of people per year are exposed to OSGeo-Live at conferences around the world.
#* What type of users does your project attract (government, commercial, hobby, academic research, etc. )? Primarily people new to OSGeo software who want to know more.
# Do you wish to host any portion of this project using the OSGeo infrastructure? If so, what? We are already using some of OSGeo hosting, in particular, the OSGeo Issue tracker.
# Does the project support open standards? Which ones and to what extent? (OGC, w3c, etc.) Has the software been certified to any standard (CITE for example)? If not, is it the intention of the project owners to seek certification at some point? There are many projects which OSGeo-Live packages which follow OGC standards. Most OGC standards are covered. To a certain extent, OSGeo-Live follows debian packaging conventions.
# Is the code free of patents, trademarks, and do you control the copyright? OSGeo-Live is free of patents and trademarks. Copyright is owned by numerous people and organisations who have contributed to OSGeo-Live.
# Does the project include an automated build and test? The build process is mostly automated. Automated testing is not very feasible for an integration project such as OSGeo-Live, and as such most testing is manual.
# What language(s) are used in this project? (C/Java/perl/etc) Most of OSGeo-Live code is shell scripts for installing applications. The packages we bundle are written in numerous languages.
# What is the dominant written language (i.e. English, French, Spanish, German, etc) of the core developers? Primary document is English. Documentation is translated into over 10 languages.
# What is the (estimated) size of a full release of this project? How many users do you expect to download the project when it is released? Our distribution aims to fit on a 4Gig USB or DVD for a mini distribution, or 8 Gig USB for full distribution.
# Do you already have an OSGeo Mentor to guide you through the incubation process? Yes, Jody Garnett.

= OSGeo-Live Incubation Checklist =
This page addresses the status of OSGeo-Live as per version 2.0 of the [http://www.osgeo.org/incubator/process/project_graduation_checklist.html OSGeo Incubation Checklist]. It is derived from the [http://wiki.osgeo.org/wiki/Project_Graduation_Checklist#Document_Status wiki] version of the document.

For the purposes of incubation auditing, the scope of the OSGeo-Live project comprises of the scripts and processes used to build OSGeo-Live, but doesn't include the specific projects being packages (many of which are addressing OSGeo Incubation separately in their own right).

= Incubation Checklist =

== Open ==

The project has demonstrated that it has an open, active and healthy user and developer community:
# Open: projects are expected to function in an open and public manner and include:
#* Open source license(s),
#**YES: Code is under LGPL, Documentation under Creative Commons, as per http://live.osgeo.org/en/copyright.html
#* Open communication channels,
#**YES: We have an active email list, and hold weekly IRC meetings during build cycles. http://wiki.osgeo.org/wiki/Live_GIS_Disc#Contact_Us
#* Open decision making process,
#**YES: Decision making process is documented at https://wiki.osgeo.org/wiki/Live_GIS_Management
# Active and healthy community:
#* The project should have a community of developers and users who actively collaborate and support each other in a healthy way. Eg. collaboration on project activities such as testing, release and feature development.
#**YES: A few hundred people have contributed to OSGeo-Live. Most contributions have been in writing application installer scripts, associated documentation, as well as translations. A list of contributors are at: http://live.osgeo.org/en/sponsors.html
#* Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organisations. Eg. The project is resilient enough to sustain loss of a developer or supporting organisation, often referred to as having a high [http://en.wikipedia.org/wiki/Bus_factor bus factor]. Decisions are made openly instead of behind closed doors, which empowers all developers to take ownership of the project and facilitates spreading of knowledge between current and future team members.
#**YES: Contributors come from a wide range of organisations (as seen by email addresses of contributors). Sponsoring organisations are also listed at: http://live.osgeo.org/en/sponsors.html

== Copyright and License ==

We need to ensure that the project owns or otherwise has obtained the ability to release the project code by completing the following steps:
# All project source code is available under an Open Source license. YES: Code is under LGPL, as per http://live.osgeo.org/en/copyright.html
# Project documentation is available under an open license, such as Creative Commons. YES: Documentation is under Creative Commons licence, as per http://live.osgeo.org/en/copyright.html
# 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. TBD: Provenance Review is required.
# The project maintains a list of all copyright holders identified in the Provenance Review Document. YES: All contributors are listed at: http://live.osgeo.org/en/sponsors.html
# All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived. YES: All contributors have publicly accepted the terms of the OSGeo-Live license. This is archived in the [http://lists.osgeo.org/mailman/listinfo/live-demo OSGeo-Live email list]. The process is described here: http://wiki.osgeo.org/wiki/Live_GIS_Disc#Subversion

== Processes ==

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

== Documentation ==

# The project has user documentation:
#* Including sufficient detail to guide a new user through performing the core functionality provided by the application. 
YES: The project has extensive Project Overviews and Quickstarts, specifically designed for getting new users up and running quickly. These are linked from: http://live.osgeo.org/en/index.html and http://live.osgeo.org/en/overview/overview.html
# The project has developer documentation: YES: How to add a new project to OSGeo-Live is covered in detail. Linked from: http://wiki.osgeo.org/wiki/Live_GIS_Disc#How_to_add_a_project_to_OSGeoLive
#* Including checkout and build instructions. YES: Linked from: http://wiki.osgeo.org/wiki/Live_GIS_Disc#How_to_add_a_project_to_OSGeoLive
#* Including commented code, ideally published for developer use. Examples: javadocs for Java applications, or Sphinx documentation for Python applications. YES: Code is primarily relatively small shell script files, which include comment. 
#* Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project's programming conventions. <br\>YES

==Release Procedure==

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

# The project follows a defined release process:
#* Which includes execution of the testing process before releasing a stable release. The project has an established build and release process, but it needs to be more clearly documented. Some information here: http://wiki.osgeo.org/wiki/Live_GIS_Disc#Build_Process . The release management role is well established, but not documented. This includes setting up a schedule, sending out press releases, chasing up projects, etc, etc.
# The project follows a documented testing process. Ideally, this includes both automated and manual testing Ideally this includes documented conformance to set quality goals, such as reporting Percentage Code Coverage of Unit Tests. OSGeo-Live is an integration project, which is difficult to create automated testing for. Instead we rely on manual testing. The testing process is well practiced, but needs to be documented better.
# Release and testing processes provide sufficient detail for an experienced programmer to follow. TBD: Waiting on improved documentation.

IstSOS Incubation Graduation Checklist

2019-08-30T16:54:43Z

Maxi: Created page with "= This page has moved = * https://trac.osgeo.org/osgeolive/wiki/Incubator%20Application * https://trac.osgeo.org/osgeolive/wiki/Graduation%20List = Incubator Application Que..."

= This page has moved =

* https://trac.osgeo.org/osgeolive/wiki/Incubator%20Application
* https://trac.osgeo.org/osgeolive/wiki/Graduation%20List

= Incubator Application Questionnaire version 2.0 =

Questions from the Incubator Application Questionnaire version 2.0. 
# Please provide the name and email address of the principal Project Owner. massimiliano dot cannata AT gmail X com
# Please provide the names and emails of co-project owners (if any). Refer to members of the [[istSOS_Managemnt PSC_Members|TODO]].
# Please provide the names, emails and entity affiliation of all official committers. Refer to [[istSOS committers list|TODO]]
# Please describe your Project. istSOS is an OGC SOS server implementation written in Python. istSOS allows for managing and dispatch observations from monitoring sensors according to the Sensor Observation Service standard.
# Why is OSGeo Incubation good for your project? We wish to officially demonstrate the level of quality of the project.
# What type of application does this project represent(client, server, standalone, library, etc.): istSOS is a server application, even if an administration interface is available with the package (i.e.:similarly to geoserver).

# Please describe any relationships to other open source projects. OSGeo-Live is in communication with all the 50+ projects we package.
# Please describe any relationships with commercial companies or products. Numerous organisations provide resources to support OSGeo-Live. These are listed at: http://live.osgeo.org/en/sponsors.html
# Please explain how your project will use an open governance policy, ensuring decisions are made, documented and adhered to in a public manner. All decisions are currently made on public email lists or publicly archived IRC. (There have been a few times where personally, financially, or politically sensitive matters have been taken off list, but these situations are rare.)
# Which open source license(s) will the source code be released under? The licenses used for the OSGeo-Live build scripts and documentation are: Creative Commons Attribution-ShareAlike 3.0 Unported License for Quickstarts, Creative Commons Attribution 3.0 Unported License for Project Overviews, LGPL version >=2.1 for the install scripts, One of the OSI approved Open Source licenses for installed applications, Public domain, CC-By-SA, and Open Data Commons Open Database License (ODbL) for data
# Please describe the maturity and history of your project. For instance,
#* What is the origin of your project (commercial, experimental, thesis or other higher education, government, or some other source)? OSGeo-Live was initially developed as a promotional distribution for handing out at FOSS4G conferences and the like, and has since grown, especially into supporting educational programs.
#* How many people actively contribute (code, documentation, other?) to the project at this time? Literally hundreds of people, as per: http://live.osgeo.org/en/sponsors.html
#* How many people have commit access to the source code repository? Literally hundreds of people, as per: http://live.osgeo.org/en/sponsors.html
#* Approximately how many users are currently using this project? Probably tens of thousands of people per year are exposed to OSGeo-Live at conferences around the world.
#* What type of users does your project attract (government, commercial, hobby, academic research, etc. )? Primarily people new to OSGeo software who want to know more.
# Do you wish to host any portion of this project using the OSGeo infrastructure? If so, what? We are already using some of OSGeo hosting, in particular, the OSGeo Issue tracker.
# Does the project support open standards? Which ones and to what extent? (OGC, w3c, etc.) Has the software been certified to any standard (CITE for example)? If not, is it the intention of the project owners to seek certification at some point? There are many projects which OSGeo-Live packages which follow OGC standards. Most OGC standards are covered. To a certain extent, OSGeo-Live follows debian packaging conventions.
# Is the code free of patents, trademarks, and do you control the copyright? OSGeo-Live is free of patents and trademarks. Copyright is owned by numerous people and organisations who have contributed to OSGeo-Live.
# Does the project include an automated build and test? The build process is mostly automated. Automated testing is not very feasible for an integration project such as OSGeo-Live, and as such most testing is manual.
# What language(s) are used in this project? (C/Java/perl/etc) Most of OSGeo-Live code is shell scripts for installing applications. The packages we bundle are written in numerous languages.
# What is the dominant written language (i.e. English, French, Spanish, German, etc) of the core developers? Primary document is English. Documentation is translated into over 10 languages.
# What is the (estimated) size of a full release of this project? How many users do you expect to download the project when it is released? Our distribution aims to fit on a 4Gig USB or DVD for a mini distribution, or 8 Gig USB for full distribution.
# Do you already have an OSGeo Mentor to guide you through the incubation process? Yes, Jody Garnett.

= OSGeo-Live Incubation Checklist =
This page addresses the status of OSGeo-Live as per version 2.0 of the [http://www.osgeo.org/incubator/process/project_graduation_checklist.html OSGeo Incubation Checklist]. It is derived from the [http://wiki.osgeo.org/wiki/Project_Graduation_Checklist#Document_Status wiki] version of the document.

For the purposes of incubation auditing, the scope of the OSGeo-Live project comprises of the scripts and processes used to build OSGeo-Live, but doesn't include the specific projects being packages (many of which are addressing OSGeo Incubation separately in their own right).

= Incubation Checklist =

== Open ==

The project has demonstrated that it has an open, active and healthy user and developer community:
# Open: projects are expected to function in an open and public manner and include:
#* Open source license(s),
#**YES: Code is under LGPL, Documentation under Creative Commons, as per http://live.osgeo.org/en/copyright.html
#* Open communication channels,
#**YES: We have an active email list, and hold weekly IRC meetings during build cycles. http://wiki.osgeo.org/wiki/Live_GIS_Disc#Contact_Us
#* Open decision making process,
#**YES: Decision making process is documented at https://wiki.osgeo.org/wiki/Live_GIS_Management
# Active and healthy community:
#* The project should have a community of developers and users who actively collaborate and support each other in a healthy way. Eg. collaboration on project activities such as testing, release and feature development.
#**YES: A few hundred people have contributed to OSGeo-Live. Most contributions have been in writing application installer scripts, associated documentation, as well as translations. A list of contributors are at: http://live.osgeo.org/en/sponsors.html
#* Long term viability of the project is demonstrated by showing participation and direction from multiple developers, who come from multiple organisations. Eg. The project is resilient enough to sustain loss of a developer or supporting organisation, often referred to as having a high [http://en.wikipedia.org/wiki/Bus_factor bus factor]. Decisions are made openly instead of behind closed doors, which empowers all developers to take ownership of the project and facilitates spreading of knowledge between current and future team members.
#**YES: Contributors come from a wide range of organisations (as seen by email addresses of contributors). Sponsoring organisations are also listed at: http://live.osgeo.org/en/sponsors.html

== Copyright and License ==

We need to ensure that the project owns or otherwise has obtained the ability to release the project code by completing the following steps:
# All project source code is available under an Open Source license. YES: Code is under LGPL, as per http://live.osgeo.org/en/copyright.html
# Project documentation is available under an open license, such as Creative Commons. YES: Documentation is under Creative Commons licence, as per http://live.osgeo.org/en/copyright.html
# 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. TBD: Provenance Review is required.
# The project maintains a list of all copyright holders identified in the Provenance Review Document. YES: All contributors are listed at: http://live.osgeo.org/en/sponsors.html
# All code contributors have agreed to abide by the project's license policy, and this agreement has been documented and archived. YES: All contributors have publicly accepted the terms of the OSGeo-Live license. This is archived in the [http://lists.osgeo.org/mailman/listinfo/live-demo OSGeo-Live email list]. The process is described here: http://wiki.osgeo.org/wiki/Live_GIS_Disc#Subversion

== Processes ==

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

== Documentation ==

# The project has user documentation:
#* Including sufficient detail to guide a new user through performing the core functionality provided by the application. 
YES: The project has extensive Project Overviews and Quickstarts, specifically designed for getting new users up and running quickly. These are linked from: http://live.osgeo.org/en/index.html and http://live.osgeo.org/en/overview/overview.html
# The project has developer documentation: YES: How to add a new project to OSGeo-Live is covered in detail. Linked from: http://wiki.osgeo.org/wiki/Live_GIS_Disc#How_to_add_a_project_to_OSGeoLive
#* Including checkout and build instructions. YES: Linked from: http://wiki.osgeo.org/wiki/Live_GIS_Disc#How_to_add_a_project_to_OSGeoLive
#* Including commented code, ideally published for developer use. Examples: javadocs for Java applications, or Sphinx documentation for Python applications. YES: Code is primarily relatively small shell script files, which include comment. 
#* Providing sufficient detail for an experience programmer to contribute patches or a new module in accordance with the project's programming conventions. <br\>YES

==Release Procedure==

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

# The project follows a defined release process:
#* Which includes execution of the testing process before releasing a stable release. The project has an established build and release process, but it needs to be more clearly documented. Some information here: http://wiki.osgeo.org/wiki/Live_GIS_Disc#Build_Process . The release management role is well established, but not documented. This includes setting up a schedule, sending out press releases, chasing up projects, etc, etc.
# The project follows a documented testing process. Ideally, this includes both automated and manual testing Ideally this includes documented conformance to set quality goals, such as reporting Percentage Code Coverage of Unit Tests. OSGeo-Live is an integration project, which is difficult to create automated testing for. Instead we rely on manual testing. The testing process is well practiced, but needs to be documented better.
# Release and testing processes provide sufficient detail for an experienced programmer to follow. TBD: Waiting on improved documentation.

Open Geoscience Committee/budget 2019

2019-01-22T20:33:16Z

Maxi: /* Open Science Committee Budget Planning 2019 */

= Open Science Committee Budget Planning 2019 =

''' The OpenGeosSci committee requests to OSGeo a total budget for the 2019 of <big>7,560 USD</big>'''.

This is intended to cover:
* 1 hosted event at EGU 2019 ([[EGU_Townhall_2019|EGU Townhall 2019]], including catering costs) (2,562 USD)
* Outreach (Open Science, AGU, etc.) (3,000 USD)
* Hackathons (2,000 USD)

== EGU General Assembly ==
*'''Event''': townhall ([[EGU Townhall 2019]])
*'''Venue rental''': none
*'''Catering''': 2,278 USD (based on previous experience) [required]
*'''Promotional material''': 285 USD (Posters/flyers/media/giveaways announcing the event) [required]
*<big>''' Sub-Total requested budget: USD 2,562 USD / 2250 EUR
'''</big>

== Outreach at Open Science events ==
* '''Training/Promotional material''': 500 USD (Handsout, USB live, Open Hardware, etc.)
* '''Registrations/travel costs''': 1,500 USD
* '''OSGeo Open Science Awards''': 1,000 USD

== Hackathons / Open Science Sprints ==
* '''Catering & handout''': 1000 USD
* '''Venue rental''': 1000 USD

[[Category:Budget]]

Open Geoscience Committee/budget 2019

2019-01-22T20:32:37Z

Maxi: /* Open Science Committee Budget Planning 2019 */

= Open Science Committee Budget Planning 2019 =

''' The OpenGeosSci committee requests to OSGeo a total budget for the 2019 of <big>6,100 USD</big>'''.

This is intended to cover:
* 1 hosted event at EGU 2019 ([[EGU_Townhall_2019|EGU Townhall 2019]], including catering costs) (2,562 USD)
* Outreach (Open Science, AGU, etc.) (3,000 USD)
* Hackathons (2,000 USD)

== EGU General Assembly ==
*'''Event''': townhall ([[EGU Townhall 2019]])
*'''Venue rental''': none
*'''Catering''': 2,278 USD (based on previous experience) [required]
*'''Promotional material''': 285 USD (Posters/flyers/media/giveaways announcing the event) [required]
*<big>''' Sub-Total requested budget: USD 2,562 USD / 2250 EUR
'''</big>

== Outreach at Open Science events ==
* '''Training/Promotional material''': 500 USD (Handsout, USB live, Open Hardware, etc.)
* '''Registrations/travel costs''': 1,500 USD
* '''OSGeo Open Science Awards''': 1,000 USD

== Hackathons / Open Science Sprints ==
* '''Catering & handout''': 1000 USD
* '''Venue rental''': 1000 USD

[[Category:Budget]]

Open Geoscience Committee/budget 2019

2019-01-18T13:42:37Z

Maxi: /* Outreach at AGU General Assembly (or other Open Science events) */

= Open Science Committee Budget Planning 2019 =

''' The OpenGeosSci committee requests to OSGeo a total budget for the 2019 of <big>6,100 USD</big>'''.

This is intended to cover:
* 1 hosted event at EGU 2019 ([[EGU_Townhall_2019|EGU Townhall 2019]], including catering costs) (2,600 USD)
* Outreach (Open Science, AGU, etc.) (2,000 USD)
* Hackatons (1,000 USD)
* Unforenseen costs (500 USD)

== EGU General Assembly ==
*'''Event''': townhall ([[EGU Townhall 2019]])
*'''Venue rental''': none
*'''Catering''': 2,278 USD (based on previous experience) [required]
*'''Promotional material''': 285 USD (Posters/flyers/media/giveaways announcing the event) [required]
*<big>''' Sub-Total requested budget: #### USD 2,562 USD / 2250 EUR
'''</big>

== Outreach at Open Science events ==
* '''Training/Promotional material''': 500 USD (Handsout, USB live, Open Hardware, etc.)
* '''Registrations/travel costs''': 1,500 USD
* '''OSGeo Open Science Awards''': 1,000 USD

== Hackathons / Open Science Sprints ==
* '''Catering & handout''': 1000 USD
* '''Venue rental''': 1000 USD

[[Category:Budget]]

Open Geoscience Committee/budget 2019

2019-01-18T13:40:29Z

Maxi: /* Hackathons / Open Science Sprints */

= Open Science Committee Budget Planning 2019 =

''' The OpenGeosSci committee requests to OSGeo a total budget for the 2019 of <big>6,100 USD</big>'''.

This is intended to cover:
* 1 hosted event at EGU 2019 ([[EGU_Townhall_2019|EGU Townhall 2019]], including catering costs) (2,600 USD)
* Outreach (Open Science, AGU, etc.) (2,000 USD)
* Hackatons (1,000 USD)
* Unforenseen costs (500 USD)

== EGU General Assembly ==
*'''Event''': townhall ([[EGU Townhall 2019]])
*'''Venue rental''': none
*'''Catering''': 2,278 USD (based on previous experience) [required]
*'''Promotional material''': 285 USD (Posters/flyers/media/giveaways announcing the event) [required]
*<big>''' Sub-Total requested budget: #### USD 2,562 USD / 2250 EUR
'''</big>

== Outreach at AGU General Assembly (or other Open Science events) ==
* '''Training/Promotional material''': 500 USD (Handsout, USB live, Open Hardware, etc.)
* '''Registrations/travel costs''': 1,500 USD

== Hackathons / Open Science Sprints ==
* '''Catering & handout''': 1000 USD
* '''Venue rental''': 1000 USD

[[Category:Budget]]

Istsos Budget 2019

2018-12-18T16:46:00Z

Maxi: Created page with "= istSOS Budget Planning 2018 = ''' The istSOS community project in incubation requests to OSGeo a total budget for the 2019 of <big>4,000 USD</big>'''. This is intended to..."

= istSOS Budget Planning 2018 =

''' The istSOS community project in incubation requests to OSGeo a total budget for the 2019 of <big>4,000 USD</big>'''.

This is intended to cover:
* '''1 incubation/graduation sprint''' (including travel grant for mentor) 3,000 USD
* '''T-shirts for community sprints & promotion/users''' 500 USD
* '''Stickers''' (conferences, talks, general promotion) 500 USD

Open Geoscience Committee/budget 2019

2018-12-18T16:21:22Z

Maxi:

= Open Science Committee Budget Planning 2019 =

''' The OpenGeosSci committee requests to OSGeo a total budget for the 2019 of <big>6,100 USD</big>'''.

This is intended to cover:
* 1 hosted event at EGU 2019 (Townhall/Splinter, including catering costs) (2,600 USD)
* Outreach (Open Science, AGU, etc.) (2,000 USD)
* Hackatons (1,000 USD)
* Unforenseen costs (500 USD)

== EGU General Assembly ==
*'''Event''': townhall ([[EGU Townhall 2019]])
*'''Venue rental''': none
*'''Catering''': 2,000 USD (based on previous experience) [required]
*'''Promotional material''': 100 USD (Posters/flyers announcing the event) [required]
*'''Give aways''': 500 USD (production of OSGeo-live USB-drives)
*<big>''' Sub-Total requested budget: #### USD [Expenses: 1200 EUR / 1400 USD]
'''</big>

== Outreach at AGU General Assembly (or other Open Science events) ==
* '''Training/Promotional material''': 500 USD (Handsout, USB live, Open Hardware, etc.)
* '''Registrations/travel costs''': 1,500 USD

== Hackatons / Open Science Sprints ==
* '''Catering & handsout''': 500 USD
* '''Venue rental''': 500 USD

OSGeo OpenGeoscience Award 2018

2018-06-12T09:28:22Z

Maxi: /* Process */

== "OSGeo OpenGeoscience" Awards ==

It is important that OSGeo has strong strategic focus in open science and this Awards initiative is aimed at further expanding and promoting our objectives.

The "OSGeo OpenGeoscience" Awards for is awarded to researcher who have demonstrated contributions to FOSS4G. The aim of the awards is to recognise the excellent contributions from researchers worldwide not only to FOSS4G but also acknowledge their contributions to open knowledge and being good global citizens by helping spread the benefits of science to all. Also by giving certificates will be a great moral boost for the researchers. This recognition is much much bigger than the monetary award .The awards will be given at selected OPEN SOURCE GEOSPATIAL RESEARCH AND EDUCATION SYMPOSIUM (OGRS) 2018 http://2018.ogrs-community.org to ensure geographic distribution and participation.

== Process ==
* scientist participating to the award will send their agreement at least one week before of the event
* the committee appointed by Open Geoscience committee will select the winner during the OGRS event
* a delegate of the Open Geoscience committe will announce the winner at the closing session of the event

* a few days later the OGRS 2018 event, send award recipient details (name, bank information, address) to treasurer@osgeo.org and president@osgeo.org
* OSGeo Treasurer can then prepare transfer of funds
* OSGeo President or Open Geoscience Committee Chair can then prepare short letter informing of award (to be placed in envelope that will be presented to recipient)
* post-event a news release should be sent to news_item@osgeo.org

OSGeo OpenGeoscience Award 2018

2018-06-11T13:45:55Z

Maxi: /* Process */

== "OSGeo OpenGeoscience" Awards ==

It is important that OSGeo has strong strategic focus in open science and this Awards initiative is aimed at further expanding and promoting our objectives.

The "OSGeo OpenGeoscience" Awards for is awarded to researcher who have demonstrated contributions to FOSS4G. The aim of the awards is to recognise the excellent contributions from researchers worldwide not only to FOSS4G but also acknowledge their contributions to open knowledge and being good global citizens by helping spread the benefits of science to all. Also by giving certificates will be a great moral boost for the researchers. This recognition is much much bigger than the monetary award .The awards will be given at selected OPEN SOURCE GEOSPATIAL RESEARCH AND EDUCATION SYMPOSIUM (OGRS) 2018 http://2018.ogrs-community.org to ensure geographic distribution and participation.

== Process ==
* scientist participating to the award will send their agreement at least one week before of the event
* the committee selected by Open Geoscience committee will select the winner during the OGRS event
* a delegate of the Open Geoscience committe will announce the winner at the closing session of the event

* a few days later the OGRS 2018 event, send award recipient details (name, bank information, address) to treasurer@osgeo.org and president@osgeo.org
* OSGeo Treasurer can then prepare transfer of funds
* OSGeo President or Open Geoscience Committee Chair can then prepare short letter informing of award (to be placed in envelope that will be presented to recipient)
* post-event a news release should be sent to news_item@osgeo.org

OSGeo OpenGeoscience Award 2018

2018-06-11T13:45:26Z

Maxi: Created page with "== "OSGeo OpenGeoscience" Awards == It is important that OSGeo has strong strategic focus in open science and this Awards initiative is aimed at further expanding and promoti..."

== "OSGeo OpenGeoscience" Awards ==

It is important that OSGeo has strong strategic focus in open science and this Awards initiative is aimed at further expanding and promoting our objectives.

The "OSGeo OpenGeoscience" Awards for is awarded to researcher who have demonstrated contributions to FOSS4G. The aim of the awards is to recognise the excellent contributions from researchers worldwide not only to FOSS4G but also acknowledge their contributions to open knowledge and being good global citizens by helping spread the benefits of science to all. Also by giving certificates will be a great moral boost for the researchers. This recognition is much much bigger than the monetary award .The awards will be given at selected OPEN SOURCE GEOSPATIAL RESEARCH AND EDUCATION SYMPOSIUM (OGRS) 2018 http://2018.ogrs-community.org to ensure geographic distribution and participation.

= Process =
* scientist participating to the award will send their agreement at least one week before of the event
* the committee selected by Open Geoscience committee will select the winner during the OGRS event
* a delegate of the Open Geoscience committe will announce the winner at the closing session of the event

* a few days later the OGRS 2018 event, send award recipient details (name, bank information, address) to treasurer@osgeo.org and president@osgeo.org
* OSGeo Treasurer can then prepare transfer of funds
* OSGeo President or Open Geoscience Committee Chair can then prepare short letter informing of award (to be placed in envelope that will be presented to recipient)
* post-event a news release should be sent to news_item@osgeo.org

Open Geoscience Committee

2018-06-11T13:28:15Z

Maxi: /* Activities */

== Background ==
The idea for the committee was conceived during a EGU-themed birds of a feather meeting at the FOSS4G-Europe in Como, Italy on July 16 2015

== Motivation ==

There is currently no established interface between the OSGeo communities and geoscience organisations like the American Geoscience Union (AGU) or the European Geoscience Union (EGU). At the same time OSGeo members publish their scientific work, which is based on FOSS and open data, within such organisations, often without being aware of each other. Further, students and young scientists who are using FOSS as a base for their work need information on how to share this work and reap the recognition within Academia which they deserve.

Within geoscience, the new role model of "Open Science" or "Science 2.0" is emerging. Many desiderata for future "open scientists", including publication of both the data and software, active international networking and reach out to industry and society are already common practice within OSGeo. Therefore OSGeo can provide guidance by best practices on how these practices can be established within Academia.

== Goals ==

* Launch the discussion how to address "Open Geoscience" among all stakeholders within OSGeo.

* Development of best practices within and beyond OSGeo.

* Establish communication with scientific communities such as EGU and AGU.

* Create working groups on specific open geoscience topics

== Communication ==

* through the OpenGeoscience mailing list ([https://lists.osgeo.org/cgi-bin/mailman/listinfo/opengeoscience subscribe])

* conf calls are held via the [https://osgeo.slack.com/messages/opengeoscience/ OSGeo slack channel]. Slack uses text based communication (similar to ICQ)

== Activities ==

* [[Open_Geoscience_and_EGU_activities]]
* [[Open_Monitoring_Systems_Working_Group]]
* [[Open_Lunar_Science_Working_Group]] (tentative)
* [[Best practices for use of persistent identifiers (DOI, ORCID etc.) in OSGeo ]] (tentative)
* [[OSGeo OpenGeoscience Award 2018]]

== Meetings ==
All [[Open_Geoscience_Committee/meetings|Open Geoscience Meetings]] are open to anyone who wants to listen in or comment. Please refer to [[Open_Geoscience_Committee/meetings|Open Geoscience Meetings]] for agenda, dates and minutes.

== Members ==
* [[User:Peter_Loewe|Peter Löwe]], Founding Member ['''Chair''']
* [[User:Maxi71| Massimilano Cannata]], Founding Member ['''Co-Chair''']
* [[User:Madi| Margherita Di Leo]], Founding Member
* [[Jeff McKenna]], Founding Member
* [[User:goliadranger | Phillip Davis]], Member Geo For All Education Committee
* [[User:maria| Maria Brovelli]], GeoForAll Europa Chair
* Christian Strobl (German Remote Sensing Data Center, DLR-DFD)
* [[User:raffalba| Raffaele Albano]], Member

== Events ==
FOSS related conferences/sessions are listed at this [[Open_Geoscience_Committee/events | page]]

== Pictures ==
Holding the 1st "charter" of the committee. On that paper was written: "Open Geoscience Committee: an entry for Open Source geoscience topics."

<center>

[[File:OGC_founding_event_01_20150716.jpg|400px|thumb|left|Founding meeting 01]]
[[File:OGC_founding_event_02_20150716.jpg|400px|thumb|center|Founding meeting 02]]

</center>

[[Category:OpenGeoScience]]
[[Category:Committees]]

OSGEO at ISPRS2020

2018-05-28T17:22:03Z

Maxi:

=== OSGeo participation at XXIVth ISPRS Congress ===

==== About ====

The [http://www.isprs2020-nice.com/ XXIVth ISPRS Congress] will be 14-20. June, 2020 in Nice, France. OSGeo has [[MOU_ISPRS|MoU]] with ISPRS which includes collaboration and participation in conferences.
OSGeo was invited to organize:

- a '''Forum on Geo-Open-Science, Geo-Open-Source and Geo-Open-Data'''. The motivation of fora is to encourage strong exchanges between academia, institutions, industry, and users on important structuring subjects. The program built for the fora must cover all aspects of the theme (integrating also policy issues) and not only scientific/technical aspects.

- a '''OSGeo Pavilion''', where to group open-source companies to give them higher visibility and a stronger impact during the congress.

==== OSGeo volunteers for XXIVth ISPRS Congress ====

[[User:Maria|Maria Brovelli]]

[[User:Helena|Helena Mitasova]]

[[User:Sanand| Suchith Anand]]

[[User:kotzino| Dimitris Kotzinos]]

[[User:Mlennert| Moritz Lennert]]

[[User:patrick.hogan| Patrick Hogan]]

[[User:Darshana Rawal| Darshana Rawal]]

[[User:serenacoetzee| Serena Coetzee]]

[[User:Cschweik| Charlie Schweik]]

[[User:Maxi71| Massimiliano Cannata]]

[[Category:Conference]]

Google Summer of Code 2017 Improvements

2017-09-05T05:04:59Z

Maxi:

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ [[Image:OSGeo_300_127_pixel.png|300px|link=http://www.osgeo.org]]
</center>

== This page collects suggestions and ideas for improvement of OSGeo Google Summer of Code ==

* See also lesson learned from '''[[Google Summer of Code 2011 Improvements|2011]]'''; '''[[Google Summer of Code 2012 Improvements|2012]]'''; '''[[Google Summer of Code 2013 Improvements|2013]]'''; '''[[Google Summer of Code 2014 Improvements|2014]]''';'''[[Google Summer of Code 2015 Improvements|2015]]'''

* '''Add your idea here''': Explain it here.
Idea: Better bonding to community by sending the weekly report also to the developers mailing list (if it exists).?

* '''report template form'''
Having a standardized form to fill in weekly reports would help students, mentors and admins to keep track of deadlines without jumping from link to link...

== Topics to be discussed at the upcoming Mentor summit ==

Google mentor summit is a great occasion to meet other organizations and gsoc admins and share good practices, clarify doubts, discuss potential problems and possible improvements. There is always room for improvement! So please, list hereinafter suggestions on topics that you wish your OSGeo delegates should bring to mentor summit for discussion.

* '''Add your topic here''': Explain it here.

[[Category:Google Summer of Code]]

Europe archive

2017-07-21T10:44:03Z

Maxi: /* List of initial members */

= Europe =

Welcome to the wiki page of the Europe OSGeo chapter.

== ToDo list ==

* Decide about the legal structure
* Write meeting report of the meeting October 5 2016 (Maria - Vasile - Dirk)

== Introduction ==

FOSS4G Europe is rooted in the FOSS4G Central and Eastern Europe conference series, back in 2012. The latter evolved in 2014 as the first edition of FOSS4G Europe in Bremen. The conference is now becoming the main european FOSS4G event, gathering people and OSGeo local chapters from all over Europe and beyond.

Since the conference in Bremen, thoughts and ideas where exchanged to organise OSGeo more on a European basis. The Industry group was started, a platform of people supporting the idea arose, but there was no real initiative for action.

This year we (OSGeoEU) have the ambition to organise a legal entity OSGEO-EU to create a stronger software group in Europe to defend the rights of open source from the perspective of the Geo-ecosystem.

In preparation for this official expression of interest, a couple of
meetings have already taken place.
a physical BOF @FOSS4G 2014 in Bremen, some mails, a BOF @FOSS4G 2015 in Como and some one physical meetings.

== Why should OSGeo have a European local chapter ==

* Europe has specific needs in terms adoption rate of open source software.
* An important initiative called 'INSPIRE' needs specific localised attention.
* OSGeo.EU is a sparring partner and representation (Single point of contact) for the European institutions in Brussels on behalve OSGeo, the other committees, local chapters and projects. Giving the existing local chapters a voice in Brussels.
* Europe also has specific business ecosystem.
** more than 99% of all the European businesses are SME's
** software industry in Europe is as big as the software industry in the US, but the driving forces are more divided
** FLOSS can be used as an opportunity to create a strong industry leadership in Europe
** OSGeo.EU can play a supporting role in this process

== Mission and objectives ==

After discussion amongst the active local chapter members we come to the
following list of mission objectives:

* Community-building and networking around specific European themes

* support the European OSGeo members using FOSS4G software, help them to organise and bring into contact with governmental agencies and research institutes. Help them with European funded projects.

* encourage interoperability in European projects

* support European open standards and European directives such as INSPIRE

* provide support for the use of OSGeo software in education via European curriculum development, outreach, and capacity building

* to encourage communication between the different European local chapters

* to encourage different communities to work together where relevant

* Organisation of events

* Networking with other typically European organisations and groups (notably OSM, JRC, European projects, FIWARE, EUROGI, SMESpire, ... )

* Being logical parter to European Commission to discuss about open source software for geospatial and open geospatial data

== List of initial members ==

The European OSGeo Chapter has the support of the following initial
founding members (alphabetic?? - first name):

* [http://wiki.osgeo.org/wiki/User:Dirkf Dirk Frigne] - Vice president
* [http://wiki.osgeo.org/wiki/User:Vasile Vasile Crăciunescu] - board member
* [[Jáchym Čepický]] - Secretary of OSGeo
* [http://wiki.osgeo.org/wiki/User:Schpidi Stephan Meißl] - charter member
* [http://wiki.osgeo.org/wiki/User:Till_Adams Till Adams] - charter member
* [http://wiki.osgeo.org/wiki/User:MarcVloemans Marc Vloemans] - Charter member
* [http://wiki.osgeo.org/wiki/User:Neteler Markus Neteler] - Charter member
* [http://wiki.osgeo.org/wiki/User:Jgrocha Jorge Gustavo Rocha] - Charter member
* [https://wiki.osgeo.org/wiki/User:Alexbruy Alexander Bruy] - Charter member
* [https://wiki.osgeo.org/wiki/User:OliverMay Oliver May] - Charter member
* [http://wiki.osgeo.org/wiki/User:Delawen María Arias de Reyna] - charter member
* [https://wiki.osgeo.org/wiki/Angelos_Tzotsos Angelos Tzotsos] - Board member
* [[Jeff McKenna]] - President Emeritus
* [http://wiki.osgeo.org/wiki/User:ianturton Ian Turton] - charter member
* [[Jorge Sanz]] - Charter member
* [http://wiki.osgeo.org/wiki/User:djay Gérald Fenoy] - Charter member
* [http://wiki.osgeo.org/wiki/User:ajolma Ari Jolma] - Charter member
* Kari Salovaara - Charter member
* [http://wiki.osgeo.org/wiki/Milena_Nowotarska Milena Nowotarska] Milena Nowotarska - Charter member
* [https://wiki.osgeo.org/wiki/User:Maxi71 Massimiliano Cannata] - Charter member
* [https://wiki.osgeo.org/wiki/User:Nbozon Nicolas Bozon] - Charter member
* [https://wiki.osgeo.org/wiki/User:Maria Maria Brovelli] - Board member
* [https://wiki.osgeo.org/wiki/User:Silvia_franceschi Silvia Franceschi] - Charter member
* [https://wiki.osgeo.org/wiki/User:Andrea_antonello Andrea Antonello] - Charter member

== Some early stuff ==
[[Local_Chapter_EU_History History]]

==Building relations with other European communities==
===SMESpire===
* Goal: look if SMESPire is a good platform to organise the European FOSS Geo-ICT industry
* action: contact Giacomo Martirano / action: Dirk Frigne - ongoing
===FIWare===
* [[https://www.fiware.org/]]
* action: investigate if structural relationship can be of interest for OSGeo.
===new entry===
* reference to the event
*register your name if you will participate

== Tradeshows and events ==
* European Events where OSGeo is represented

===ISPRS===
[[ISPRS 2016]]
* contact: [[User:Jachym|Jachym]]

=== FOSSDEM ===

[https://fosdem.org/2016/practical/ FOSSDEM 2016]
* contact: [[User:johanvdw|Johanvdw]]

=== GWF2016 ===
[http://geospatialworldforum.org/ GWF 2016]
* contact: [[User:Dirkf|Dirk Frigne]]

=== FOSS4G 2016 ===
[http://2016.foss4g.org/home.html FOSS4G 2016 Bonn]
* OSGeo Europe local chapter BoF https://www.flickr.com/photos/stevenfeldman/29294641505/in/pool-foss4g/
* contact: [[User:MarcVloemans|Marc Vloemans]]

=== FOSS4G 2017 ===
[http://europe.foss4g.org/2017/ FOSS4G 2017 Paris]
* topic talks - volunteers
* contact: [[User:Dirkf|Dirk Frigne]]
** TT01 An overview of the best Free and Open Source Software for Geospatial
** TT02 OSGeo-Live for INSPIRE
** TT03 Sustainability of OSGeo projects
** TT04 FOSS4G-Europe welcomes new volunteers to the OSGeo community
** TT05 The future of SDI
** TT06 Economics of FOSS4G - "Sustainability of OSGeo projects"

== Communication & Comments ==

=== Mailing list ===

* OSGeo Europe ([https://lists.osgeo.org/mailman/listinfo/eu subscribe]) ([http://osgeo-org.1560.x6.nabble.com/European-Union-Chapter-f5250537.html search])

=== Meeting minutes ===

==== Meeting 24 May 2016 ====
* workshop on the initial wiki page - discussion mission and goals
* change the status from draft to final
* decide for formal proposal to the next board meeting
* attendees:
 
Till Adams (Fossgis) 
Marc Vloemans (Chair Marketing committee) 
Dirk Frigne (Vice President OSGeo) 
Pieter De Graef (Charter member) 
Gert-Jan van der Weijden (OSGeo.nl) 
Johan Van de Wauw (OSGeo.be) 

==== BoF 24 Aug 2016 ====
* bof at FOSS4G 2016 [[Europe-meeting-2016-08|2016_08_24]]

==== BoF 19 Jul 2017 ====
* bof at FOSS4G-Europe [[Europe-meeting-2017-07|2017_07_19]]

[[Category:Local Chapters]]
[[Category:Europe]]

Google Summer of Code 2017 Administrative

2017-03-08T14:55:19Z

Maxi: /* Mentors */

Google Summer of Code 2017 Administrative

2017-03-08T14:51:07Z

Maxi: /* Mentors */

Google Summer of Code 2017 Ideas

2017-02-01T17:05:20Z

Maxi: /* The ideas pages */

<center>
[[Image:GSoC2016Logo.jpg|400px|link=https://developers.google.com/open-source/gsoc/]] @ 
[[Image:OSGeo_300_127_pixel.png|300px|link=http://www.osgeo.org]]
</center>

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

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

== OSGeo Google Summer of Code 2017 ==

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

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

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

* There is a [https://developers.google.com/open-source/soc/resources/flyers Google SoC flyer] to look at and post in appropriate places.

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

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

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

If you are an OSGeo project lead about to add your page, please contact the GSoC admin team to let them know of your ideas page, by sending an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]

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

=== OSGeo Foundation member projects ===

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

[[Image:logo-grass.png|60px|right]]
* [https://trac.osgeo.org/grass/wiki/GSoC/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!





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

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







[[Image:Logo-istSOS.png|100px|right]]
* [https://sourceforge.net/p/istsos/wiki/GSoC_ideas_2017/ '''istSOS''' Ideas]: [http://sourceforge.net/projects/istsos/ istSOS] is a complete sensor data management system for acquiring, storing and dispatching time-series observations. istSOS is compliant with the Sensor Observation Service (SOS) version 1.0 and 2.0 standard from the Open Geospatial Consortium (OGC) and offers unique extended capabilities to support scientific data analyses (integrated quality assurance, RESTful API, on the fly processing with virtual procedures, remote data aggregation and time-space re-projection etc.). istSOS core libraries are written in Python while it easy to use interface is Web based.








=== Guest projects ===

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]

[[Image:Pgrouting-logo.png|60px|right]]
* [https://github.com/pgRouting/pgrouting/wiki/GSoC-Ideas '''pgRouting''' Ideas]: [http://pgrouting.org pgRouting] extends the PostGIS / PostgreSQL geospatial database to provide geospatial routing functionality and more.

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



=== Don't see in the list the project you're interested in? ===

Contact them in their developers mailing list! Feel free to propose your own idea and get feedback!

== I want to apply as a student ==

Before applying as a student, check out the [[Google Summer of Code Recommendations for Students]] page.

=== Which project do I choose? ===

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

=== Important dates ===

* [https://developers.google.com/open-source/gsoc/timeline '''The official timeline''']


* Feb 27: Google announces accepted organizations.
: Please start talking to the dev communities you are interested in ''now''.
* March 20: Student applications open.
: The earlier you start the more probable it is that you will be accepted!
: ''There is two way feedback during the application process which really helps you improve and clarify your application before the final deadline. The better your involvement with your potential mentors during this period, the better your chances of being selected.''
* April 3: Student application deadline.
* May 4: '''Accepted student proposals are announced and Community Bonding Period begins.'''
* May 30: '''Coding begins!'''
: (''you may unofficially start a week or two earlier if you know you'll have to take a week or two off during The Summer or you'll be sitting finals in the first week(s) of the program. This must be reflected in your application timeline'')
* June 26 - 30: Phase 1 evaluation
* July 28: Phase 2 evaluation
* August 21-29: '''Pencils down!'''
* August 29 - September 5: Final evaluations
* September 6: Final results announced

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

Open Lunar Science Working Group

2017-01-29T05:35:23Z

Maxi:

The '''Open Lunar Science Working Group''' is a tentative working group active in the Geoscience domain within the [[Open_Geoscience_Committee|OSGeo Open Geoscience Committee]] specifically created to contribute to all the [http://lunar.xprize.org Google Lunar XPRIZE] teams by providing FOSS4G solutions and data.



= WG Members =
* Put your name here!!!

= Objectives =

''Draft''

= Activities Plan =

* collect available data
* provide open dataset
* call for a challenge

Open Geoscience Committee

2017-01-29T05:32:59Z

Maxi:

== Background ==
The idea for the committee was conceived during a EGU-themed birds of a feather meeting at the FOSS4G-Europe in Como, Italy on July 16 2015

== Motivation ==

There is currently no established interface between the OSGeo communities and geoscience organisations like the American Geoscience Union (AGU) or the European Geoscience Union (EGU). At the same time OSGeo members publish their scientific work, which is based on FOSS and open data, within such organisations, often without being aware of each other. Further, students and young scientists who are using FOSS as a base for their work need information on how to share this work and reap the recognition within Academia which they deserve.

Within geoscience, the new role model of "Open Science" or "Science 2.0" is emerging. Many desiderata for future "open scientists", including publication of both the data and software, active international networking and reach out to industry and society are already common practice within OSGeo. Therefore OSGeo can provide guidance by best practices on how these practices can be established within Academia.

== Goals ==

* Launch the discussion how to address "Open Geoscience" among all stakeholders within OSGeo.

* Development of best practices within and beyond OSGeo.

* Establish communication with scientific communities such as EGU and AGU.

* Create working groups on specific open geoscience topics

== Communication ==

* through the OpenGeoscience mailing list ([https://lists.osgeo.org/cgi-bin/mailman/listinfo/opengeoscience subscribe])

* conf calls are held via the [https://osgeo.slack.com/messages/opengeoscience/ OSGeo slack channel]. Slack uses text based communication (similar to ICQ)

== Activities ==

* [[Open_Geoscience_and_EGU_activities]]
* [[Open_Monitoring_Systems_Working_Group]]
* [[Open_Lunar_Science_Working_Group]] (tentative)

== Meetings ==
All [[Open_Geoscience_Committee/meetings|Open Geoscience Meetings]] are open to anyone who wants to listen in or comment. Please refer to [[Open_Geoscience_Committee/meetings|Open Geoscience Meetings]] for agenda, dates and minutes.

== Members ==
* [[User:Peter_Loewe|Peter Löwe]], Founding Member ['''Chair''']
* [[User:Maxi71| Massimiiano Cannata]], Founding Member ['''Co-Chair''']
* [[User:Madi| Margherita Di Leo]], Founding Member
* [[Jeff McKenna]], Founding Member
* [[User:goliadranger | Phillip Davis]], Member Geo For All Education Committee
* [[User:maria| Maria Brovelli]], GeoForAll Europa Chair
* Christian Strobl (German Remote Sensing Data Center, DLR-DFD)
* [[User:raffalba| Raffaele Albano]], Member

== Events ==
FOSS related conferences/sessions are listed at this [[Open_Geoscience_Committee/events | page]]

== Pictures ==
Holding the 1st "charter" of the committee. On that paper was written: "Open Geoscience Committee: an entry for Open Source geoscience topics."

<center>

[[File:OGC_founding_event_01_20150716.jpg|400px|thumb|left|Founding meeting 01]]
[[File:OGC_founding_event_02_20150716.jpg|400px|thumb|center|Founding meeting 02]]

</center>

[[Category:OpenGeoScience]]
[[Category:Committees]]

Open Lunar Science Working Group

2017-01-29T05:30:59Z

Maxi: Created page with "The '''Open Lunar Science Working Group''' is a tentative working group in the Geoscience domain to contribute providing FOSS4G solutions and data to all the [http://lunar.xpr..."

The '''Open Lunar Science Working Group''' is a tentative working group in the Geoscience domain to contribute providing FOSS4G solutions and data to all the [http://lunar.xprize.org Google Lunar XPRIZE] teams.



= WG Members =
* Put your name here!!!

= Objectives =

''Draft''

= Activities Plan =

* collect available data
* provide open dataset
* call for a challenge

OSGeo Budget 2017

2016-12-15T12:33:17Z

Maxi: /* Draft 2017 Budget */

The board is taking a different approach to the 2017 budget, dividing up by committee. We have reached out to each committee for guidance on their 2017 requirements.

The following DRAFT placeholder is based on the 2016 budget; broken down by committee to get an idea of proposed spending.

== Planning ==

For [[OSGeo Budget 2016]] the board budgeted 70000 split across several goals:

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
! Activity
! Budget
! Spent
! Notes
|-
| Admin
| style="text-align:right;" | 8000
| style="text-align:right;" | n/a
| administration overhead
|-
| Insurance
| style="text-align:right;" | 3000
| style="text-align:right;" | 3000
| officer liability insurance
|-
| SAC
| style="text-align:right;" | 13000
| style="text-align:right;" | 6000
| infrastructure and online presence
|-
| Outreach
| style="text-align:right;" | 15000
| style="text-align:right;" | 4000
| starter kits, LiveDVD/USB, Marketing, OSGeo Student Awards
|-
| Travel
| style="text-align:right;" | 15000
| style="text-align:right;" | 7000
| director & president travel - facilitate interaction with external parties (UN, OGC,...)
|-
| Events
| style="text-align:right;" | 20000
| style="text-align:right;" | 20000
| OSGeo internal (townhall, codesprint, ) and external (e.g.. ISPRS, EGU, GWF...) events
|}

This represents a total budget of 75000, of which the community managed to spend 41000.

If we directly migrate 2016 budget into a breakdown by committee we can have a baseline for our 2017 budget:

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
! Committee
! 2016 Budget
! Notes
|-
| Board: Admin
| style="text-align:right;" | 10000
|
|-
| Board: travel
| style="text-align:right;" | 10000
| director & president travel (outreach)
|-
| Board: internal events
| style="text-align:right;" | 15000
| codesprints, meetings, community building, sponsoring students
|-
| Board: outreach events
| style="text-align:right;" | 5000
|
|-
| SAC
| style="text-align:right;" | 13000
|
|-
| Marketing
| style="text-align:right;" | 12000
|
|-
| GeoForAll Budget
| style="text-align:right;" | 3000
| education
|-
| UNCommittee
| style="text-align:right;" | 10000
| The UNCommittee expectation of 10000 is based on its costs in 2016 (when it was only in operation for half the year). The UN represents one of the largest bodies of GIS users in the world making this an important strategic relationship for OSGeo.
|}

=== Committee Contact List ===

In the [[Board_Meeting_2016-11-25]] we agreed to reach out to each committee for budget requests / requirements:
Thus far we have:

* Board of Directors - contact venka :)
* Code of Conduct Committee -
* (done) Conference Committee - Angelos contacted committee avout [http://osgeo-org.1560.x6.nabble.com/Conference-Committee-Guidelines-td5298661.html operations] and [http://osgeo-org.1560.x6.nabble.com/Conference-Committee-Guidelines-td5298661.html budget]
* Finance Committee -
* (done) Geo for All - Maria contacted Suchith
* (done) Incubation Committee - jody contacted list about [http://osgeo-org.1560.x6.nabble.com/committee-website-and-operation-tc5297450.html operations] and [http://osgeo-org.1560.x6.nabble.com/incubation-committee-budget-tc5297896.html budget]
* (done) Marketing Committee - jody contacted the list [http://osgeo-org.1560.x6.nabble.com/marketing-committee-guidelines-tp5297725.html operations] and [http://osgeo-org.1560.x6.nabble.com/marketing-committee-budget-and-request-from-the-board-tp5297736.html budget]
* (done) Open GeoScience Committee - maria contacted maxi ($6000 request for townhall at EGU and open monitoring hackatons)
* Project Steering Committees:
** GeoNode - jody to contact jeff
** (done) GRASS GIS - Helena to contact Markus ($1500 budget request for a code sprint)
** gvSIG
** Marble
** (done) QGIS - Anita contacted PSC
** FDO
** GDAL/OGR
** GEOS
** GeoTools - jody to contact geotools-devel
** OSSIM
** PostGIS
** GeoNetwork
** pycsw
** deegree
** geomajas
** GeoMOOSE
** GeoServer - jody to contact simone
** Mapbender
** MapFish
** MapGuide Open Source
** MapServer
** OpenLayers
* Public Geospatial Data Committee -
* (done) System Administration Committee - Angelos contacted committee about both [http://osgeo-org.1560.x6.nabble.com/System-Administrator-Committee-Guidelines-td5298680.html operations] and [http://osgeo-org.1560.x6.nabble.com/System-Administrator-Committee-Budget-2017-td5298685.html budget]
* (done) UN Committee - Maria contacted Suchith and Maxi

==== Marketing Committee ====

Marketing committee has provided their usual operational budget, in addition to a budget for rebooting the website:

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
! Category
! Activity
! 2016 Budget
! 2017 Budget
! Notes
|-
| A
| website reboot
| style="text-align:right;" | n/a
| style="text-align:right;" | 50000
| new website and logo design
|-
| B
| marketing collateral
| style="text-align:right;" | n/a
| style="text-align:right;" | 10000
| a clean up of existing/preparation of new marketing collateral
|-
| C
| event support
| style="text-align:right;" | 12000
| style="text-align:right;" | 10000
| Downloadable marketing collateral, event formats etc (ongoing) via the website. Event banners/flyers and Live-CD/USB sticks (e.g. Foss4g booths)
|-
| C
| operations
| style="text-align:right;" | n/a
| style="text-align:right;" | 5000
| Miscellaneous activities/purchases (e.g. MailChimp account for FOSS4G's).
|-
|
| TOTAL
| style="text-align:right;" | 12000
| style="text-align:right;" | 75000
|
|}

== Draft 2017 Budget ==

The following draft budget is updated as we hear back from each community.

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
! OSGeo Board
! 2016 Baseline
! 2017 Draft
! Notes
|- style="vertical-align:top;"
| Administration
| style="text-align:right;" | 10,000
| style="text-align:right;" | 10,000
|
|- style="vertical-align:top;"
| Travel
| style="text-align:right;" | 10,000
| style="text-align:right;" | 10,000
| director & president travel (outreach)
|- style="vertical-align:top;"
| Internal events
| style="text-align:right;" | 15,000
| style="text-align:right;" | 12,000
| codesprints, meetings, community building, sponsoring students (reduced to due to lack of face 2 face meeting)
|- style="vertical-align:top;"
| Outreach events
| style="text-align:right;" | 5,000
| style="text-align:right;" | n/a
| (responsibility moved to marketing committee)
|- style="vertical-align:top;"
|-
! OSGeo Committee
! 2016 Baseline
! 2017 Draft
! Notes
|- style="vertical-align:top;"
| SAC
| style="text-align:right;" | 13,000
| style="text-align:right;" | 15,000
| (assume additional costs for website reboot)
|- style="vertical-align:top;"
| Open Geoscience
| style="text-align:right;" | 0
| style="text-align:right;" | 6,000
| This is intended to cover:
* 1 Townhall event at EGU (2,600 USD)
* 4/5 open monitoring hackatons (3,000 USD)
* others minor unforenseen costs (400 USD)
Details are availble here:[[Open Geoscience Committee/budget 2017|OpenGeosci budget_2017]]
|- style="vertical-align:top;"
| Marketing
| style="text-align:right;" | 12,000
| style="text-align:right;" | 25,000
| (carrying over budget from 2016?)
|- style="vertical-align:top;"
| Marketing: Website RFQ
| style="text-align:right;" |
| style="text-align:right;" | 50,000
|
|- style="vertical-align:top;"
| GeoForAll Budget
| style="text-align:right;" | 3,000
| style="text-align:right;" | 3,000
| education
|- style="vertical-align:top;"
| UNCommittee
| style="text-align:right;" | 10,000
| style="text-align:right;" | 3,000
| participation to 2 international meeting of the Open GIS initiative by UN whose OSGeo is part per 1 person ~ 3'000 (note that GeoForAll participation is intended to be funded by geo4all)
|-
! Project Steering Committee
! 2016 Baseline
! 2017 Draft
! Notes
|- style="vertical-align:top;"
| GRASS
| style="text-align:right;" |
| style="text-align:right;" | 1,500
| code sprint
|-
| QGIS
| style="text-align:right;" | 2,000
| style="text-align:right;" | 3,000
| 1x developer meeting & 1x user conference
|-
| GeoServer
| style="text-align:right;" | 1,500
| style="text-align:right;" | 2,000
| 1x developer meeting / sprint
|}

Open Geoscience Committee/budget 2017

2016-12-15T11:40:19Z

Maxi: /* BUDGET */

= BUDGET =

'''The OpenGeosSci committee requests to OSGeo a total budget for the 2017 of <big>6,000 USD</big>'''.

This is intended to cover:
* 1 Townhall event at EGU (2,600 USD)
* 4/5 open monitoring hackatons (3,000 USD)
* others minor unforenseen costs (400 USD)

Here the detailed estimates based on previous conducted events.

== EGU ==
*'''Event''': townhall
*'''Venue rental''': none
*'''Catering''': 2,000 USD (based on last years experience) [required]
*'''Promotional material''': 100 USD (Posters/flyers announcing the event) [required]
*'''Give aways''': 500 USD (production of OSGeo-live USB-drives)
*<big>'''Sub-Total requested budget: 2,600 USD</big>
'''
== Open monitoring hackatons ==
*'''Events''': 4/5 hackatons with about 20 attendees
*'''Venue rental''': none (in combination with FOSS4G-IT, FOSS4G-Asia, FOSS4G-EU, FOSS4G, ...)
*'''Catering & handsout''': 2,000 USD (4/5 contribution for coffee breaks and handsout)
*'''Training/Promotional material''': 1000 USD (100 open hardware kit , OSGeo branded arduino + temp. sensor + led)
*<big>'''Sub-Total requested budget: 3,000 USD'''</big>

OSGeo Budget 2017

2016-12-15T11:40:03Z

Maxi: /* Draft 2017 Budget */

The board is taking a different approach to the 2017 budget, dividing up by committee. We have reached out to each committee for guidance on their 2017 requirements.

The following DRAFT placeholder is based on the 2016 budget; broken down by committee to get an idea of proposed spending.

== Planning ==

For [[OSGeo Budget 2016]] the board budgeted 70000 split across several goals:

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
! Activity
! Budget
! Spent
! Notes
|-
| Admin
| style="text-align:right;" | 8000
| style="text-align:right;" | n/a
| administration overhead
|-
| Insurance
| style="text-align:right;" | 3000
| style="text-align:right;" | 3000
| officer liability insurance
|-
| SAC
| style="text-align:right;" | 13000
| style="text-align:right;" | 6000
| infrastructure and online presence
|-
| Outreach
| style="text-align:right;" | 15000
| style="text-align:right;" | 4000
| starter kits, LiveDVD/USB, Marketing, OSGeo Student Awards
|-
| Travel
| style="text-align:right;" | 15000
| style="text-align:right;" | 7000
| director & president travel - facilitate interaction with external parties (UN, OGC,...)
|-
| Events
| style="text-align:right;" | 20000
| style="text-align:right;" | 20000
| OSGeo internal (townhall, codesprint, ) and external (e.g.. ISPRS, EGU, GWF...) events
|}

This represents a total budget of 75000, of which the community managed to spend 41000.

If we directly migrate 2016 budget into a breakdown by committee we can have a baseline for our 2017 budget:

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
! Committee
! 2016 Budget
! Notes
|-
| Board: Admin
| style="text-align:right;" | 10000
|
|-
| Board: travel
| style="text-align:right;" | 10000
| director & president travel (outreach)
|-
| Board: internal events
| style="text-align:right;" | 15000
| codesprints, meetings, community building, sponsoring students
|-
| Board: outreach events
| style="text-align:right;" | 5000
|
|-
| SAC
| style="text-align:right;" | 13000
|
|-
| Marketing
| style="text-align:right;" | 12000
|
|-
| GeoForAll Budget
| style="text-align:right;" | 3000
| education
|-
| UNCommittee
| style="text-align:right;" | 10000
| The UNCommittee expectation of 10000 is based on its costs in 2016 (when it was only in operation for half the year). The UN represents one of the largest bodies of GIS users in the world making this an important strategic relationship for OSGeo.
|}

=== Committee Contact List ===

In the [[Board_Meeting_2016-11-25]] we agreed to reach out to each committee for budget requests / requirements:
Thus far we have:

* Board of Directors - contact venka :)
* Code of Conduct Committee -
* (done) Conference Committee - Angelos contacted committee avout [http://osgeo-org.1560.x6.nabble.com/Conference-Committee-Guidelines-td5298661.html operations] and [http://osgeo-org.1560.x6.nabble.com/Conference-Committee-Guidelines-td5298661.html budget]
* Finance Committee -
* (done) Geo for All - Maria contacted Suchith
* (done) Incubation Committee - jody contacted list about [http://osgeo-org.1560.x6.nabble.com/committee-website-and-operation-tc5297450.html operations] and [http://osgeo-org.1560.x6.nabble.com/incubation-committee-budget-tc5297896.html budget]
* (done) Marketing Committee - jody contacted the list [http://osgeo-org.1560.x6.nabble.com/marketing-committee-guidelines-tp5297725.html operations] and [http://osgeo-org.1560.x6.nabble.com/marketing-committee-budget-and-request-from-the-board-tp5297736.html budget]
* (done) Open GeoScience Committee - maria contacted maxi ($6000 request for townhall at EGU and open monitoring hackatons)
* Project Steering Committees:
** GeoNode - jody to contact jeff
** (done) GRASS GIS - Helena to contact Markus ($1500 budget request for a code sprint)
** gvSIG
** Marble
** (done) QGIS - Anita contacted PSC
** FDO
** GDAL/OGR
** GEOS
** GeoTools - jody to contact geotools-devel
** OSSIM
** PostGIS
** GeoNetwork
** pycsw
** deegree
** geomajas
** GeoMOOSE
** GeoServer - jody to contact simone
** Mapbender
** MapFish
** MapGuide Open Source
** MapServer
** OpenLayers
* Public Geospatial Data Committee -
* (done) System Administration Committee - Angelos contacted committee about both [http://osgeo-org.1560.x6.nabble.com/System-Administrator-Committee-Guidelines-td5298680.html operations] and [http://osgeo-org.1560.x6.nabble.com/System-Administrator-Committee-Budget-2017-td5298685.html budget]
* (done) UN Committee - Maria contacted Suchith and Maxi

==== Marketing Committee ====

Marketing committee has provided their usual operational budget, in addition to a budget for rebooting the website:

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
! Category
! Activity
! 2016 Budget
! 2017 Budget
! Notes
|-
| A
| website reboot
| style="text-align:right;" | n/a
| style="text-align:right;" | 50000
| new website and logo design
|-
| B
| marketing collateral
| style="text-align:right;" | n/a
| style="text-align:right;" | 10000
| a clean up of existing/preparation of new marketing collateral
|-
| C
| event support
| style="text-align:right;" | 12000
| style="text-align:right;" | 10000
| Downloadable marketing collateral, event formats etc (ongoing) via the website. Event banners/flyers and Live-CD/USB sticks (e.g. Foss4g booths)
|-
| C
| operations
| style="text-align:right;" | n/a
| style="text-align:right;" | 5000
| Miscellaneous activities/purchases (e.g. MailChimp account for FOSS4G's).
|-
|
| TOTAL
| style="text-align:right;" | 12000
| style="text-align:right;" | 75000
|
|}

== Draft 2017 Budget ==

The following draft budget is updated as we hear back from each community.

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
! OSGeo Board
! 2016 Baseline
! 2017 Draft
! Notes
|- style="vertical-align:top;"
| Administration
| style="text-align:right;" | 10,000
| style="text-align:right;" | 10,000
|
|- style="vertical-align:top;"
| Travel
| style="text-align:right;" | 10,000
| style="text-align:right;" | 10,000
| director & president travel (outreach)
|- style="vertical-align:top;"
| Internal events
| style="text-align:right;" | 15,000
| style="text-align:right;" | 12,000
| codesprints, meetings, community building, sponsoring students (reduced to due to lack of face 2 face meeting)
|- style="vertical-align:top;"
| Outreach events
| style="text-align:right;" | 5,000
| style="text-align:right;" | n/a
| (responsibility moved to marketing committee)
|- style="vertical-align:top;"
|-
! OSGeo Committee
! 2016 Baseline
! 2017 Draft
! Notes
|- style="vertical-align:top;"
| SAC
| style="text-align:right;" | 13,000
| style="text-align:right;" | 15,000
| (assume additional costs for website reboot)
|- style="vertical-align:top;"
| open Geoscience
| style="text-align:right;" | 0
| style="text-align:right;" | 6,000
| This is intended to cover:
* 1 Townhall event at EGU (2,600 USD)
* 4/5 open monitoring hackatons (3,000 USD)
* others minor unforenseen costs (400 USD)
Details are availble here:[[Open Geoscience Committee/budget 2017|OpenGeosci budget_2017]]
|- style="vertical-align:top;"
| Marketing
| style="text-align:right;" | 12,000
| style="text-align:right;" | 25,000
| (carrying over budget from 2016?)
|- style="vertical-align:top;"
| Marketing: Website RFQ
| style="text-align:right;" |
| style="text-align:right;" | 50,000
|
|- style="vertical-align:top;"
| GeoForAll Budget
| style="text-align:right;" | 3,000
| style="text-align:right;" | 3,000
| education
|- style="vertical-align:top;"
| UNCommittee
| style="text-align:right;" | 10,000
| style="text-align:right;" | 10,000
|
|-
! Project Steering Committee
! 2016 Baseline
! 2017 Draft
! Notes
|- style="vertical-align:top;"
| GRASS
| style="text-align:right;" |
| style="text-align:right;" | 1,500
| code sprint
|-
| QGIS
| style="text-align:right;" |
| style="text-align:right;" | 3,000
| 1x developer meeting & 1x user conference
|-
| GeoServer
| style="text-align:right;" | 1,500
| style="text-align:right;" | 2,000
| 1x developer meeting / sprint
|}

OSGeo Budget 2017

2016-12-15T11:39:09Z

Maxi: /* Draft 2017 Budget */

The board is taking a different approach to the 2017 budget, dividing up by committee. We have reached out to each committee for guidance on their 2017 requirements.

The following DRAFT placeholder is based on the 2016 budget; broken down by committee to get an idea of proposed spending.

== Planning ==

For [[OSGeo Budget 2016]] the board budgeted 70000 split across several goals:

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
! Activity
! Budget
! Spent
! Notes
|-
| Admin
| style="text-align:right;" | 8000
| style="text-align:right;" | n/a
| administration overhead
|-
| Insurance
| style="text-align:right;" | 3000
| style="text-align:right;" | 3000
| officer liability insurance
|-
| SAC
| style="text-align:right;" | 13000
| style="text-align:right;" | 6000
| infrastructure and online presence
|-
| Outreach
| style="text-align:right;" | 15000
| style="text-align:right;" | 4000
| starter kits, LiveDVD/USB, Marketing, OSGeo Student Awards
|-
| Travel
| style="text-align:right;" | 15000
| style="text-align:right;" | 7000
| director & president travel - facilitate interaction with external parties (UN, OGC,...)
|-
| Events
| style="text-align:right;" | 20000
| style="text-align:right;" | 20000
| OSGeo internal (townhall, codesprint, ) and external (e.g.. ISPRS, EGU, GWF...) events
|}

This represents a total budget of 75000, of which the community managed to spend 41000.

If we directly migrate 2016 budget into a breakdown by committee we can have a baseline for our 2017 budget:

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
! Committee
! 2016 Budget
! Notes
|-
| Board: Admin
| style="text-align:right;" | 10000
|
|-
| Board: travel
| style="text-align:right;" | 10000
| director & president travel (outreach)
|-
| Board: internal events
| style="text-align:right;" | 15000
| codesprints, meetings, community building, sponsoring students
|-
| Board: outreach events
| style="text-align:right;" | 5000
|
|-
| SAC
| style="text-align:right;" | 13000
|
|-
| Marketing
| style="text-align:right;" | 12000
|
|-
| GeoForAll Budget
| style="text-align:right;" | 3000
| education
|-
| UNCommittee
| style="text-align:right;" | 10000
| The UNCommittee expectation of 10000 is based on its costs in 2016 (when it was only in operation for half the year). The UN represents one of the largest bodies of GIS users in the world making this an important strategic relationship for OSGeo.
|}

=== Committee Contact List ===

In the [[Board_Meeting_2016-11-25]] we agreed to reach out to each committee for budget requests / requirements:
Thus far we have:

* Board of Directors - contact venka :)
* Code of Conduct Committee -
* (done) Conference Committee - Angelos contacted committee avout [http://osgeo-org.1560.x6.nabble.com/Conference-Committee-Guidelines-td5298661.html operations] and [http://osgeo-org.1560.x6.nabble.com/Conference-Committee-Guidelines-td5298661.html budget]
* Finance Committee -
* (done) Geo for All - Maria contacted Suchith
* (done) Incubation Committee - jody contacted list about [http://osgeo-org.1560.x6.nabble.com/committee-website-and-operation-tc5297450.html operations] and [http://osgeo-org.1560.x6.nabble.com/incubation-committee-budget-tc5297896.html budget]
* (done) Marketing Committee - jody contacted the list [http://osgeo-org.1560.x6.nabble.com/marketing-committee-guidelines-tp5297725.html operations] and [http://osgeo-org.1560.x6.nabble.com/marketing-committee-budget-and-request-from-the-board-tp5297736.html budget]
* (done) Open GeoScience Committee - maria contacted maxi ($6000 request for townhall at EGU and open monitoring hackatons)
* Project Steering Committees:
** GeoNode - jody to contact jeff
** (done) GRASS GIS - Helena to contact Markus ($1500 budget request for a code sprint)
** gvSIG
** Marble
** (done) QGIS - Anita contacted PSC
** FDO
** GDAL/OGR
** GEOS
** GeoTools - jody to contact geotools-devel
** OSSIM
** PostGIS
** GeoNetwork
** pycsw
** deegree
** geomajas
** GeoMOOSE
** GeoServer - jody to contact simone
** Mapbender
** MapFish
** MapGuide Open Source
** MapServer
** OpenLayers
* Public Geospatial Data Committee -
* (done) System Administration Committee - Angelos contacted committee about both [http://osgeo-org.1560.x6.nabble.com/System-Administrator-Committee-Guidelines-td5298680.html operations] and [http://osgeo-org.1560.x6.nabble.com/System-Administrator-Committee-Budget-2017-td5298685.html budget]
* (done) UN Committee - Maria contacted Suchith and Maxi

==== Marketing Committee ====

Marketing committee has provided their usual operational budget, in addition to a budget for rebooting the website:

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
! Category
! Activity
! 2016 Budget
! 2017 Budget
! Notes
|-
| A
| website reboot
| style="text-align:right;" | n/a
| style="text-align:right;" | 50000
| new website and logo design
|-
| B
| marketing collateral
| style="text-align:right;" | n/a
| style="text-align:right;" | 10000
| a clean up of existing/preparation of new marketing collateral
|-
| C
| event support
| style="text-align:right;" | 12000
| style="text-align:right;" | 10000
| Downloadable marketing collateral, event formats etc (ongoing) via the website. Event banners/flyers and Live-CD/USB sticks (e.g. Foss4g booths)
|-
| C
| operations
| style="text-align:right;" | n/a
| style="text-align:right;" | 5000
| Miscellaneous activities/purchases (e.g. MailChimp account for FOSS4G's).
|-
|
| TOTAL
| style="text-align:right;" | 12000
| style="text-align:right;" | 75000
|
|}

== Draft 2017 Budget ==

The following draft budget is updated as we hear back from each community.

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
! OSGeo Board
! 2016 Baseline
! 2017 Draft
! Notes
|- style="vertical-align:top;"
| Administration
| style="text-align:right;" | 10,000
| style="text-align:right;" | 10,000
|
|- style="vertical-align:top;"
| Travel
| style="text-align:right;" | 10,000
| style="text-align:right;" | 10,000
| director & president travel (outreach)
|- style="vertical-align:top;"
| Internal events
| style="text-align:right;" | 15,000
| style="text-align:right;" | 12,000
| codesprints, meetings, community building, sponsoring students (reduced to due to lack of face 2 face meeting)
|- style="vertical-align:top;"
| Outreach events
| style="text-align:right;" | 5,000
| style="text-align:right;" | n/a
| (responsibility moved to marketing committee)
|- style="vertical-align:top;"
|-
! OSGeo Committee
! 2016 Baseline
! 2017 Draft
! Notes
|- style="vertical-align:top;"
| SAC
| style="text-align:right;" | 13,000
| style="text-align:right;" | 15,000
| (assume additional costs for website reboot)
|- style="vertical-align:top;"
| open Geoscience
| style="text-align:right;" | 0
| style="text-align:right;" | 6,000
| This is intended to cover:
* 1 Townhall event at EGU (2,600 USD)
* 4/5 open monitoring hackatons (3,000 USD)
* others minor unforenseen costs (4,00 USD)
Details are availble here:[[Open Geoscience Committee/budget 2017|OpenGeosci budget_2017]]
|- style="vertical-align:top;"
| Marketing
| style="text-align:right;" | 12,000
| style="text-align:right;" | 25,000
| (carrying over budget from 2016?)
|- style="vertical-align:top;"
| Marketing: Website RFQ
| style="text-align:right;" |
| style="text-align:right;" | 50,000
|
|- style="vertical-align:top;"
| GeoForAll Budget
| style="text-align:right;" | 3,000
| style="text-align:right;" | 3,000
| education
|- style="vertical-align:top;"
| UNCommittee
| style="text-align:right;" | 10,000
| style="text-align:right;" | 10,000
|
|-
! Project Steering Committee
! 2016 Baseline
! 2017 Draft
! Notes
|- style="vertical-align:top;"
| GRASS
| style="text-align:right;" |
| style="text-align:right;" | 1,500
| code sprint
|-
| QGIS
| style="text-align:right;" |
| style="text-align:right;" | 3,000
| 1x developer meeting & 1x user conference
|-
| GeoServer
| style="text-align:right;" | 1,500
| style="text-align:right;" | 2,000
| 1x developer meeting / sprint
|}

Open Geoscience Committee/budget 2017

2016-12-15T11:37:26Z

Maxi: Created page with "= BUDGET = '''The OpenGeosSci committee requests to OSGeo a total budget for the 2017 of <big>6,000 USD</big>'''. This is intended to cover: * 1 Townhall event at EGU (2,60..."

= BUDGET =

'''The OpenGeosSci committee requests to OSGeo a total budget for the 2017 of <big>6,000 USD</big>'''.

This is intended to cover:
* 1 Townhall event at EGU (2,600 USD)
* 4/5 open monitoring hackatons (3,000 USD)
* others minor unforenseen costs (4,00 USD)

Here the detailed estimates based on previous conducted events.

== EGU ==
*'''Event''': townhall
*'''Venue rental''': none
*'''Catering''': 2,000 USD (based on last years experience) [required]
*'''Promotional material''': 100 USD (Posters/flyers announcing the event) [required]
*'''Give aways''': 500 USD (production of OSGeo-live USB-drives)
*<big>'''Sub-Total requested budget: 2,600 USD</big>
'''
== Open monitoring hackatons ==
*'''Events''': 4/5 hackatons with about 20 attendees
*'''Venue rental''': none (in combination with FOSS4G-IT, FOSS4G-Asia, FOSS4G-EU, FOSS4G, ...)
*'''Catering & handsout''': 2,000 USD (4/5 contribution for coffee breaks and handsout)
*'''Training/Promotional material''': 1000 USD (100 open hardware kit , OSGeo branded arduino + temp. sensor + led)
*<big>'''Sub-Total requested budget: 3,000 USD'''</big>

Building fully open climatic monitoring system

2016-12-05T09:35:07Z

Maxi: /* Participants */

= [https://wiki.osgeo.org/wiki/Open_Monitoring_Systems_Working_Group OSGeo's Open Monitoring System WG] hackathon =

This event will be held in Italy, in San Michele all'Adige at Fondazione Edmund Mach [http://osm.org/go/0Cvti3RZ9--?m= OSM]. The event is a workshop to learn how to create a open climatic monitoring system. The dates are '''6th and 7th December 2016'''.

== Program ==
=== Day 1 ===
* 09:00 Introduction, Open Software and Open Hardware (Talk)
* 10:00 introduction to OGC Sensor Observation Service with istSOS (Talk)
* 10:30 coffee break
* 11:00 Arduino IDE: troubleshooting, compiling (Talk+hands-on)
Download the IDE: https://www.arduino.cc/en/Main/Software
Blink example (hands-on)
//BLINK EXAMPLE, switch on and off the Arduino board LED
void setup() {
pinMode(LED_BUILTIN, OUTPUT); // Will connect to the board LED
}
void loop() {
digitalWrite(LED_BUILTIN, HIGH); // turn the LED on (HIGH is the voltage level)
delay(3000); // wait for 3 seconds
digitalWrite(LED_BUILTIN, LOW); // turn the LED off by making the voltage LOW
delay(2000); // wait for 2 seconds
}
* 12:30 Lunch
* 13.30 Arduino hands on: blink (cntd) and temperature, temperature and humidity, other sensors like CO2 (Hands on)
* 14:00 Introduction to weather station (Talk)
Each station consists of an Arduino microcontroller,
a weather shield, a GSM board, weather sensors, and
a micro-SD card. Access to the manuals for assembling,
maintaining and programming the stations can be found at:
http://www.iwmi.cgiar.org/resources/mobile-weather-stations/
A similar Arduino-based station full-kit is found at:
http://store.switchdoc.com/ourweather-complete-weather-kit/
* 14:30 Discover weather station components (Hands on)
* 15:00 coffee break
* 15:30 Building weather station (Hands on)
* 17:30 end

=== Day 2 ===
* 09:00 Soldering workshop (Hands on)
* 10:00 Prototyping your own sensor system and introduce arduino enslaved to raspberrypi (Talk)
* 10:30 coffee break
* 11:00 Prototyping your own sensor system and introduce arduino enslaved to raspberrypi (Hands on)
import serial,sys
ser = serial.Serial("/dev/USB0", 9600)
while 1:
sys.stdout.write(ser.readline())
sys.stdout.flush()
* 12:30 Introduction about communication: GSM, Wifi, RF, USB (Talk)
* 13:00 Lunch
* 14:00 Connecting to istSOS for data management, analysis and distribution
* 15:30 coffee break
* 16:00 Connecting to istSOS for data management, analysis and distribution (cont.)
* 17:00 end

== Components to bring ==

To follow completely the hackathon everyone need to come with the following components

=== Required ===
Material:
* arduino nano v3 with soldered pins
* weather components:
# EITHER:
- Arduino Uno R3
- SparkFun Weather Shield DEV-12081
- Arduino Stackable Header Kit - R3PRT-11417
- GPS Receiver - GP-735 (56 Channel) GPS-13670
- JST SH Jumper 6 Wire - 1.75" GPS-00574
- RJ11 6-Pin Connector PRT-00132
# OR:
- [http://www.switchdoc.com/ourweather/ OurWeather] station complete kit
* leds
* some sensors (DS18B20 or DHT22 or gas)
* some jumper wires/cable

=== Suggested ===
* raspberry pi with raspbian OS
* arduino nano v3 non soldered with separated headers
* arduino shield for communication (GSM, Wifi, RF)
* arduino data logger shield OpenLog ([http://www.banggood.com Banggood])
* Weather Meters SEN-08942 (this come with [http://www.switchdoc.com/ourweather/ OurWeather])
* solder iron
* soldering led

== Participants ==

The maximum number of participant is 20 people.

{| class="wikitable"
|-
! Number !! Name !! Arrival date !! Departure date !! Affiliation !! Your own sensors !! Note
|-
| 1 || Luca Delucchi || - || - || Fondazione E. Mach || ||
|-
| 2 || Robero Zorer || - || - || Fondazione E. Mach || ||
|-
| 3 || Massimiliano Cannata || - || - || SUPSI || ||
|-
| 4 || Daniele Strigaro || - || - || SUPSI || ||
|-
| 5 || Milan Antonovic || - || - || SUPSI || ||
|-
| 6 || <s>Mirko Cardoso</s> || - || - || SUPSI || ||
|-
| 7 || Yann Chemin || 4th or 5th || 8th || Freelance || ||
|-
| 8 || <s>Ilaria Ferrando</s> || - || - || UNIGE || ||
|-
| 9 || Ivan Piffer || - || - || Fondazione E. Mach || ||
|-
| 10 || Francesca Cagnacci || - || - || Fondazione E. Mach || ||
|-
| 11 || Federico Ossi || - || - || Fondazione E. Mach || ||
|-
| 12 || Martina Costi|| - || - || Università di Trento || ||
|-
| 13 || Clara Tattoni|| - || - || FEM/Unitn || ||
|-
| 14 || Nikos Alexandris|| - || - || Freelancer || ||
|-
| 15 || Antonio Galea || - || - || Freelancer || ||
|-
| 16 || Alessandro Stefani || - || - || || ||
|-
| 17 || Paolo Lenti || - || - || Fondazione E. Mach || ||
|-
| 18 || Sébastien Wenger || - || - || - || ||
|-
| || ADD || YOUR || SELF || || ||
|}

== Sponsors ==
* [http://www.fmach.it Fondazione Edmund Mach], providing logistic support and organization effort

Building fully open climatic monitoring system

2016-12-05T09:34:27Z

Maxi: /* Participants */

= [https://wiki.osgeo.org/wiki/Open_Monitoring_Systems_Working_Group OSGeo's Open Monitoring System WG] hackathon =

This event will be held in Italy, in San Michele all'Adige at Fondazione Edmund Mach [http://osm.org/go/0Cvti3RZ9--?m= OSM]. The event is a workshop to learn how to create a open climatic monitoring system. The dates are '''6th and 7th December 2016'''.

== Program ==
=== Day 1 ===
* 09:00 Introduction, Open Software and Open Hardware (Talk)
* 10:00 introduction to OGC Sensor Observation Service with istSOS (Talk)
* 10:30 coffee break
* 11:00 Arduino IDE: troubleshooting, compiling (Talk+hands-on)
Download the IDE: https://www.arduino.cc/en/Main/Software
Blink example (hands-on)
//BLINK EXAMPLE, switch on and off the Arduino board LED
void setup() {
pinMode(LED_BUILTIN, OUTPUT); // Will connect to the board LED
}
void loop() {
digitalWrite(LED_BUILTIN, HIGH); // turn the LED on (HIGH is the voltage level)
delay(3000); // wait for 3 seconds
digitalWrite(LED_BUILTIN, LOW); // turn the LED off by making the voltage LOW
delay(2000); // wait for 2 seconds
}
* 12:30 Lunch
* 13.30 Arduino hands on: blink (cntd) and temperature, temperature and humidity, other sensors like CO2 (Hands on)
* 14:00 Introduction to weather station (Talk)
Each station consists of an Arduino microcontroller,
a weather shield, a GSM board, weather sensors, and
a micro-SD card. Access to the manuals for assembling,
maintaining and programming the stations can be found at:
http://www.iwmi.cgiar.org/resources/mobile-weather-stations/
A similar Arduino-based station full-kit is found at:
http://store.switchdoc.com/ourweather-complete-weather-kit/
* 14:30 Discover weather station components (Hands on)
* 15:00 coffee break
* 15:30 Building weather station (Hands on)
* 17:30 end

=== Day 2 ===
* 09:00 Soldering workshop (Hands on)
* 10:00 Prototyping your own sensor system and introduce arduino enslaved to raspberrypi (Talk)
* 10:30 coffee break
* 11:00 Prototyping your own sensor system and introduce arduino enslaved to raspberrypi (Hands on)
import serial,sys
ser = serial.Serial("/dev/USB0", 9600)
while 1:
sys.stdout.write(ser.readline())
sys.stdout.flush()
* 12:30 Introduction about communication: GSM, Wifi, RF, USB (Talk)
* 13:00 Lunch
* 14:00 Connecting to istSOS for data management, analysis and distribution
* 15:30 coffee break
* 16:00 Connecting to istSOS for data management, analysis and distribution (cont.)
* 17:00 end

== Components to bring ==

To follow completely the hackathon everyone need to come with the following components

=== Required ===
Material:
* arduino nano v3 with soldered pins
* weather components:
# EITHER:
- Arduino Uno R3
- SparkFun Weather Shield DEV-12081
- Arduino Stackable Header Kit - R3PRT-11417
- GPS Receiver - GP-735 (56 Channel) GPS-13670
- JST SH Jumper 6 Wire - 1.75" GPS-00574
- RJ11 6-Pin Connector PRT-00132
# OR:
- [http://www.switchdoc.com/ourweather/ OurWeather] station complete kit
* leds
* some sensors (DS18B20 or DHT22 or gas)
* some jumper wires/cable

=== Suggested ===
* raspberry pi with raspbian OS
* arduino nano v3 non soldered with separated headers
* arduino shield for communication (GSM, Wifi, RF)
* arduino data logger shield OpenLog ([http://www.banggood.com Banggood])
* Weather Meters SEN-08942 (this come with [http://www.switchdoc.com/ourweather/ OurWeather])
* solder iron
* soldering led

== Participants ==

The maximum number of participant is 20 people.

{| class="wikitable"
|-
! Number !! Name !! Arrival date !! Departure date !! Affiliation !! Your own sensors !! Note
|-
| 1 || Luca Delucchi || - || - || Fondazione E. Mach || ||
|-
| 2 || Robero Zorer || - || - || Fondazione E. Mach || ||
|-
| 3 || Massimiliano Cannata || - || - || SUPSI || ||
|-
| 4 || Daniele Strigaro || - || - || SUPSI || ||
|-
| 5 || Milan Antonovic || - || - || SUPSI || ||
|-
| 6 || <s>Mirko Cardoso</s> || - || - || SUPSI || ||
|-
| 7 || Yann Chemin || 4th or 5th || 8th || Freelance || ||
|-
| 8 || Ilaria Ferrando || - || - || UNIGE || ||
|-
| 9 || Ivan Piffer || - || - || Fondazione E. Mach || ||
|-
| 10 || Francesca Cagnacci || - || - || Fondazione E. Mach || ||
|-
| 11 || Federico Ossi || - || - || Fondazione E. Mach || ||
|-
| 12 || Martina Costi|| - || - || Università di Trento || ||
|-
| 13 || Clara Tattoni|| - || - || FEM/Unitn || ||
|-
| 14 || Nikos Alexandris|| - || - || Freelancer || ||
|-
| 15 || Antonio Galea || - || - || Freelancer || ||
|-
| 16 || Alessandro Stefani || - || - || || ||
|-
| 17 || Paolo Lenti || - || - || Fondazione E. Mach || ||
|-
| 18 || Sébastien Wenger || - || - || - || ||
|-
| || ADD || YOUR || SELF || || ||
|}

== Sponsors ==
* [http://www.fmach.it Fondazione Edmund Mach], providing logistic support and organization effort

Talk:UN OpenGIS logo contest

2016-11-14T10:59:22Z

Maxi: Maxi71 moved page Talk:UN OpenGIS logo contest to Talk:UN Open GIS logo contest: OpenGIS is a trademark name

#REDIRECT [[Talk:UN Open GIS logo contest]]

Talk:UN Open GIS logo contest

2016-11-14T10:59:22Z

Maxi: Maxi71 moved page Talk:UN OpenGIS logo contest to Talk:UN Open GIS logo contest: OpenGIS is a trademark name

Good day, we are very excited about the logo contest. I have submitted a first logo, but I have a few questions:

# Should the logo include the UN logo? I tried to read up on logo usage, when placed with with the UN logo in their CI manual. Do you perhaps have any layout guidelines?
# Should the logo include the full text wording "UN OpenGIS Initiative"? or only be the icon, as on Submission 1
# Should the colour scheme be aligned with the UN corporate colours or will the logo stand a lone with its own color scheme?
# Are there specific Fonts that are preferable?

(posted 23:35, 7 August 2016‎ Idavanos)

:I'd recommend to ask this on the mailing list because I don't think many people are following this discussion page. --[[User:Anitagraser|Anitagraser]] ([[User talk:Anitagraser|talk]]) 12:05, 8 August 2016 (PDT)

UN OpenGIS logo contest

2016-11-14T10:59:19Z

Maxi: Maxi71 moved page UN OpenGIS logo contest to UN Open GIS logo contest: OpenGIS is a trademark name

#REDIRECT [[UN Open GIS logo contest]]

UN Open GIS logo contest

2016-11-14T10:59:19Z

Maxi: Maxi71 moved page UN OpenGIS logo contest to UN Open GIS logo contest: OpenGIS is a trademark name

The UN open GIS Initiative is to identify and develop an Open Source GIS bundle that meets
the requirements of UN operations, taking full advantage of the expertise of mission
partners (partner nations, technology contributing countries, international organizations,
academia, NGO’s, private sector).

The strategic approach shall be developed with best and shared principles, standards and
ownership, in a prioritized manner that addresses capability gaps and needs without
duplicating efforts of other Member States or entities. The UN open GIS Initiative strategy
shall collaboratively and cooperatively develop, validate, assess, migrate, and implement
sound technical capabilities with all the appropriate documentation and training that in the
end provides a united effort to improve the effectiveness and efficiency of utilizing Open
Source GIS around the world.

= Logo Contest =

OSGeo has been involved in the initiative trough the OSGeo [[UnitedNations_Committee|UnitedNations Committee]]
and is currently actively contributing to the UN open GIS initiative.

With this contest, the [[UnitedNations_Committee|UnitedNations Committee]] would like to invite the artistic
minds in our community to develop the official logo of the UN open GIS initiative.

This ''UN open GIS'' logo will be used on official documents of the UN open GIS initiative.

Anyone may submit artwork. We are looking for the best, so spread the word to your colleagues, family and friends.

The winning designer will receive a UN, OSGeo and G4A awarding certificate and her/his name will be awarded on the webpage of UN OpenGIS initiative.

== Contest Parameters ==

All artwork must be uploaded to the OSGeo wiki and listed on this site by '''11:59pm GMT, August 31st, 2016'''.

While designing, please keep in mind the strategy manifesto and that your design has to work as a United Nations OpenGIS initiative.

== Submission Format ==

Upload a high resolution (at least 1200x1200 px) version of your design to the [[Special:Upload|OSGeo wiki upload]] naming it ''UN_contest_XXXXX'' and list it on this site.
Additional SVG versions will be appreciated.

Alternatively you can send the image or a link to the downloadable image directly to massimiliano[dot]cannata[at]gmail[dot]com

== Legal ==

The United Nation will acquire ownership of the winning design by assignment of copyright, and the winning designer will disclaim any trademarks and without limitation all other rights related to the design (paperwork will be required).

By submitting a design for entry in the competition, the designer acknowledges that he/she is the person that made the design and is its rightful owner.

The designer also certifies that the design is completely original and does not infringe upon the rights of any third party and that it does not violate any copyright.

== Voting ==

All members of UN OpenGIS initiative will be allowed to place a single vote. In the case of a tie, the UN OpenGIS's Co-Chairs will have the final say.

Details will be announced once the design has been accepted and placed online for review.

==Submissions==

Submitted images will be listed here

<gallery>
File:UN contest draft1.png|Submission 1
File:UN contest grantps.png|Submission 2
File:UN contest -OpenGIS-Logo-smaprs-1.png|Submission 3
File:UN_contest_kinow1.png|Submission 4
File:UN_contest_kinow2.png|Submission 5
File:UN contest -OpenGIS-Logo-smaprs-2.jpg|Submission 6
File:UN contest -OpenGIS-Logo-smaprs-3.png|Submission 7
File:UN_contest_IdaVanOs1.jpg|Submission 8
File:UN_contest_IdaVanOs1_icon.png|Submission 9
File:UN_contest_GregoriosNtouvelos_icon.png|Submission 10
File:UN_contest_baluleetaroland_1.jpg|Submission 11
File:UN_contest_baluleetaroland_2.jpg|Submission 12
File:UN_contest_IdaVanOs2.jpg|Submission 13
File:UN_contest_IdaVanOs2_icon.png|Submission 14
File:UN-OpenGIS_Sooraj_01.jpg|Submission 15
File:UN-OpenGIS_Sooraj_02.jpg|Submission 16
File:UN-OpenGIS_sooraj_03.jpg|Submission 17
File:UN_contest_IdaVanOs3.jpg|Submission 18
File:UN_contest_IdaVanOs4.jpg|Submission 19
File:UN_contest_Nipesh.jpg|Submission 20
File:UN_contest_AASAS.jpg|Submission 21
File:UN_contest_KyoungSooEom.png|Submission 22
File:UN_contest_Pooja.jpg|Submission 23
File:UN_contest_Pooja1.jpg|Submission 24
File:UN_contest_baluleeta.jpg|Submission 25
File:UN_contest_baluleeta2.jpg|Submission 26
File:UN_contest_baluleeta3.jpg|Submission 27
File:UN_contest_wknowles1.png|Submission 28
File:UN_contest_wknowles2.png|Submission 28
File:UNo_GIS_v1.jpg|Submission 29
File:UN contest VolksNav1.png|Submission 30
File:UN contest VolksNav2.png|Submission 31
File:UN contest VolksNav3.png|Submission 32
File:UN contest VolksNav4.png|Submission 33
File:Gis1.png|Submission 34
File:UN_contest_Soo2.jpg|Sumbmission 35
File:UN_Contest_logo.jpg|Sumbmission 36
File:UN_contest_Julia_BM_1.jpg|Sumbmission 37
File:UN_contest_Julia_BM_2.jpg|Sumbmission 38
File:UN_contest_Julia_BM_3.jpg|Sumbmission 39
File:UN_openGIS_IlariaDeLeo01.jpg|Sumbmission 40
File:UN_openGIS_IlariaDeLeo02.jpg|Sumbmission 41
File:UN_openGIS_IlariaDeLeo03.jpg|Sumbmission 42
File:UN_openGIS_IlariaDeLeo4.jpg|Sumbmission 43
File:UN_openGIS_IlariaDeLeo05.jpg|Sumbmission 44
File:UN_openGIS_IlariaDeLeo06.jpg|Sumbmission 45
File:UN_openGIS_IlariaDeLeo07.jpg|Sumbmission 46
File:UN_openGIS_IlariaDeLeo08.jpg|Sumbmission 47
File:UN_openGIS_IlariaDeLeo09.jpg|Sumbmission 48
File:UN_contest_Arashgh1.jpg|Sumbmission 49
File:UN_contest_Arashgh2.jpg|Sumbmission 50
File:UN_contest_gebauerova_01.jpg|Sumbmission 51
File:UN_contest_gebauerova_02.jpg|Sumbmission 52

</gallery>

File:UN openGIS IlariaDeLeo01.jpg

2016-11-14T10:52:33Z

Maxi: Maxi71 uploaded a new version of File:UN openGIS IlariaDeLeo01.jpg