OSGeo - User contributions [en]

OSGeo Budget 2025

2024-12-21T03:52:13Z

Wenzeslaus: /* OSGeo Projects */

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

Total Approved Budget for 2024: $149,000 USD

Total spending for 2024: TBD

Total Approved Budget for 2025: 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
! 2024 Approved
! 2025 Actual
! 2026 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;" | 10,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;" | 1,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 2024: $15,000 USD

Total Board spending for 2024: TBD

Total Board Budget for 2025: 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
* Public Geospatial Data Committee
* System Administration Committee - foundation infrastructure
* UN Committee - committee responsible for our participation in the UN Open GIS program
* Standards Committee

{|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
! 2024 Approved [Requested]
! 2024 Actual
! 2025 Draft [Requested]
! Notes
|-
| SAC
| style="text-align:right;" | 21,500 [53,450]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| OpenGeoScience
| style="text-align:right;" | 1,000 [3,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| Conference
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| Marketing
| style="text-align:right;" | 5,000 [22,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| [[Marketing_Committee_Budget_2025]]
|-
| GeoForAll
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| UN Committee
| style="text-align:right;" | 2,500 [4,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| Incubation Committee
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|}

Total Committees Budget for 2024: $30,000 USD

Total Committees spending for 2024: TBD

Total Committees Budget for 2025: 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:

* no new initiatives proposed for 2025

{|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
! 2024 Approved
! 2024 Actual
! 2025 Draft [Requested]
! Notes
|-
| FOSS4G
| style="text-align:right;" | (48,000)
| style="text-align:right;" | -
| style="text-align:right;" | TBD
| Seed money for 2025.
|-
| 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;" | 10,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Managed by Conference Committee. Recommendation: 7k for FOSS4G 2024, 3k for local events
|-
| Events and Code Sprints
| style="text-align:right;" | 15,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.
|-
| Community Projects
| style="text-align:right;" | 3,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. Board note: Budgeted TBD$ for the first TBD projects to ask.
|}

Total Initiatives Budget for 2024: $76,000 USD

Total Initiatives spending for 2024: TBD

Total Initiatives Budget for 2025: 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 (2025) to the projects mailing list.
* Board decided to not assign a default budget this year.
* Board decided that the maximum amount per project this year cannot be more than $TBD USD.
* This is a budget, representing planned spending in 2025 - 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
! 2024 Approved [Requested]
! 2024 Actual
! 2025 Draft [Requested]
! Notes
|-
| deegree
| style="text-align:right;" | 2,000 [2,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GDAL/OGR
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoMOOSE
| style="text-align:right;" | 2,500 [4,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoNetwork
| style="text-align:right;" | 2,000 [2,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoNode
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GEOS
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoServer
| style="text-align:right;" | 2,000 [2,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | [$2000]
| [https://github.com/geoserver/geoserver/wiki/GeoServer-2025-Sponsorship-Opportunities GeoServer 2025 sponsorship opportunities]
|-
| GeoTools
| style="text-align:right;" | 2,000 [2,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GRASS GIS
| style="text-align:right;" | 2,500 [5,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | 5,001.60
| [[GRASS GIS Budget 2025]]
|-
| gvSIG
| style="text-align:right;" | 2,500 [5,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | [5000]
| https://wiki.osgeo.org/wiki/GvSIG_Budget_2025
|-
| Mapbender
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| MapServer
| style="text-align:right;" | 2,500 [4,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;" | 2,500 [3,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | [3,000]
| [https://github.com/openlayers/openlayers/wiki/OpenLayers-2025-Sponsorship-Opportunities OpenLayers 2025 sponsorship opportunities]
|-
| OTB
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| OSGeoLive
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| PostGIS
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| PROJ
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| pycsw
| style="text-align:right;" | 2,500 [3,000]
| style="text-align:right;" | 0
| style="text-align:right;" | [3,000]
| style="text-align:right;" | https://github.com/geopython/pycsw/wiki/OSGeo-Budget-2025
|
|-
| pygeoapi
| style="text-align:right;" | 2,500 [4,000]
| style="text-align:right;" | 2,074
| style="text-align:right;" | [4,000]
| style="text-align:right;" | https://github.com/geopython/pygeoapi/wiki/OSGeo-Budget-2025
|
|-
| PyWPS
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| QGIS
| style="text-align:right;" | 2,500 [5,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| ZOO-Project
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
|}

Total Projects Budget for 2024: $28,000 USD

Total Projects spending for 2024: TBD

Total Projects Budget for 2025: 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)

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
! 2024 Approved [Requested]
! 2024 Actual
! 2025 Draft [Requested]
! Notes
|-
| GeoWebCache
| style="text-align:right;" | 300 [250]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| mappyfile
| style="text-align:right;" | 300 [300]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoHealthCheck
| style="text-align:right;" | 300 [250]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoStyler
| style="text-align:right;" | -
| style="text-align:right;" | -
| style="text-align:right;" | TBD
|
|-
|}

= Events =

== Community Events ==

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

* 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
! 2024 Approved
! 2024 Actual
! 2025 Draft [Requested]
! Notes
|-
| List your event here
| 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.
* Our 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
! 2024 Approved
! 2024 Actual
! 2025 Draft [Requested]
! Notes
|-
| OSGeo Code Sprint
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| 4,395 surplus from Vienna. Not included in the budget.
|-
| GeoStyler Code Sprint
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| style="text-align:right;" | [3675€]
| Detailed request sent to board@lists.osgeo.org on 16.12.2024, subject: "Request for funding the GeoStyler Code Sprint 2025"
|-
|}

= Approval and Amendments =

* Budget Meeting:
* Loomio Motion:
* Amendments:

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

OSGeo Budget 2025

2024-12-21T03:51:43Z

Wenzeslaus: /* OSGeo Projects */

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

Total Approved Budget for 2024: $149,000 USD

Total spending for 2024: TBD

Total Approved Budget for 2025: 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
! 2024 Approved
! 2025 Actual
! 2026 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;" | 10,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;" | 1,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 2024: $15,000 USD

Total Board spending for 2024: TBD

Total Board Budget for 2025: 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
* Public Geospatial Data Committee
* System Administration Committee - foundation infrastructure
* UN Committee - committee responsible for our participation in the UN Open GIS program
* Standards Committee

{|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
! 2024 Approved [Requested]
! 2024 Actual
! 2025 Draft [Requested]
! Notes
|-
| SAC
| style="text-align:right;" | 21,500 [53,450]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| OpenGeoScience
| style="text-align:right;" | 1,000 [3,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| Conference
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| Marketing
| style="text-align:right;" | 5,000 [22,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| [[Marketing_Committee_Budget_2025]]
|-
| GeoForAll
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| UN Committee
| style="text-align:right;" | 2,500 [4,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| Incubation Committee
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|}

Total Committees Budget for 2024: $30,000 USD

Total Committees spending for 2024: TBD

Total Committees Budget for 2025: 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:

* no new initiatives proposed for 2025

{|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
! 2024 Approved
! 2024 Actual
! 2025 Draft [Requested]
! Notes
|-
| FOSS4G
| style="text-align:right;" | (48,000)
| style="text-align:right;" | -
| style="text-align:right;" | TBD
| Seed money for 2025.
|-
| 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;" | 10,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Managed by Conference Committee. Recommendation: 7k for FOSS4G 2024, 3k for local events
|-
| Events and Code Sprints
| style="text-align:right;" | 15,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.
|-
| Community Projects
| style="text-align:right;" | 3,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. Board note: Budgeted TBD$ for the first TBD projects to ask.
|}

Total Initiatives Budget for 2024: $76,000 USD

Total Initiatives spending for 2024: TBD

Total Initiatives Budget for 2025: 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 (2025) to the projects mailing list.
* Board decided to not assign a default budget this year.
* Board decided that the maximum amount per project this year cannot be more than $TBD USD.
* This is a budget, representing planned spending in 2025 - 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
! 2024 Approved [Requested]
! 2024 Actual
! 2025 Draft [Requested]
! Notes
|-
| deegree
| style="text-align:right;" | 2,000 [2,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GDAL/OGR
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoMOOSE
| style="text-align:right;" | 2,500 [4,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoNetwork
| style="text-align:right;" | 2,000 [2,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoNode
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GEOS
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoServer
| style="text-align:right;" | 2,000 [2,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | [$2000]
| [https://github.com/geoserver/geoserver/wiki/GeoServer-2025-Sponsorship-Opportunities GeoServer 2025 sponsorship opportunities]
|-
| GeoTools
| style="text-align:right;" | 2,000 [2,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GRASS GIS
| style="text-align:right;" | 2,500 [5,000]
| style="text-align:right;" | 5,001.60
| style="text-align:right;" | [[GRASS GIS Budget 2025]]
|
|-
| gvSIG
| style="text-align:right;" | 2,500 [5,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | [5000]
| https://wiki.osgeo.org/wiki/GvSIG_Budget_2025
|-
| Mapbender
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| MapServer
| style="text-align:right;" | 2,500 [4,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;" | 2,500 [3,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | [3,000]
| [https://github.com/openlayers/openlayers/wiki/OpenLayers-2025-Sponsorship-Opportunities OpenLayers 2025 sponsorship opportunities]
|-
| OTB
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| OSGeoLive
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| PostGIS
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| PROJ
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| pycsw
| style="text-align:right;" | 2,500 [3,000]
| style="text-align:right;" | 0
| style="text-align:right;" | [3,000]
| style="text-align:right;" | https://github.com/geopython/pycsw/wiki/OSGeo-Budget-2025
|
|-
| pygeoapi
| style="text-align:right;" | 2,500 [4,000]
| style="text-align:right;" | 2,074
| style="text-align:right;" | [4,000]
| style="text-align:right;" | https://github.com/geopython/pygeoapi/wiki/OSGeo-Budget-2025
|
|-
| PyWPS
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| QGIS
| style="text-align:right;" | 2,500 [5,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| ZOO-Project
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
|}

Total Projects Budget for 2024: $28,000 USD

Total Projects spending for 2024: TBD

Total Projects Budget for 2025: 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)

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
! 2024 Approved [Requested]
! 2024 Actual
! 2025 Draft [Requested]
! Notes
|-
| GeoWebCache
| style="text-align:right;" | 300 [250]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| mappyfile
| style="text-align:right;" | 300 [300]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoHealthCheck
| style="text-align:right;" | 300 [250]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoStyler
| style="text-align:right;" | -
| style="text-align:right;" | -
| style="text-align:right;" | TBD
|
|-
|}

= Events =

== Community Events ==

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

* 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
! 2024 Approved
! 2024 Actual
! 2025 Draft [Requested]
! Notes
|-
| List your event here
| 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.
* Our 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
! 2024 Approved
! 2024 Actual
! 2025 Draft [Requested]
! Notes
|-
| OSGeo Code Sprint
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| 4,395 surplus from Vienna. Not included in the budget.
|-
| GeoStyler Code Sprint
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| style="text-align:right;" | [3675€]
| Detailed request sent to board@lists.osgeo.org on 16.12.2024, subject: "Request for funding the GeoStyler Code Sprint 2025"
|-
|}

= Approval and Amendments =

* Budget Meeting:
* Loomio Motion:
* Amendments:

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

GRASS GIS Budget 2025

2024-12-21T03:21:57Z

Wenzeslaus: Budget request

The GRASS GIS project asks for a total budget of '''5,001.60 USD''' from OSGeo to cover the following expenses:

{| class="wikitable"
! Item !! USD total !! USD requested !! Notes
|-
| PSC represenative at AGM || 3,500.00 || 1,500.00 || Effort will be made to find a local representative to reduce the cost
|-
| Travel to OSGeo Sprint || 2,200.00 || 1,000.00 || Multiple travels on a continent or one travel to a different continent
|-
| Student grants || 2,000.00 || 1,000.00 || See Student Grants wiki page, 4 grants offered
|-
| Community grants || 3,000.00 || 1,000.00 || Community members can apply with a plan, PSC decides by motion
|-
| T-shirts, swag for users, conferences, ... || 400.00 || 200.00 || Community members can request for local or global events
|-
| Stickers and magnets (as above) || 400.00 || 100.00 || Community members can request for local or global events
|-
| Social media management service || 201.60 || 201.60 || Publer in Dec for 1 year 3 accounts if evaluated positively in 2025
|-
| Total || 11,701.60 || '''5,001.60''' ||
|}

The total will covered from funding "requested" from OSGeo and from other sources such as donations at [https://opencollective.com/osgeo/projects/grass Open Collective].

The full budget for GRASS GIS is found at: https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2025

[[Category:Budget]]

GRASS GIS Budget 2024

2023-12-26T17:49:31Z

Wenzeslaus: Add numbers to items

The GRASS GIS project asks for a total budget of '''5000 USD''' from OSGeo to cover the following expenses:

* 2000 USD - 2 (out of 4) micro grants for students (see our [https://grasswiki.osgeo.org/wiki/Student_Grants Student grant] program)
* 2200 USD - Travel to OSGeo sprint and PSC representation at OSGeo AGM
* 800 USD - Marketing efforts (Community members can request for local or global events)

Other expenses will be covered from additional funding sources such as in-kind contributions and donations at [https://opencollective.com/osgeo/projects/grass Open Collective].

The full budget for GRASS GIS is found at: https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2024

[[Category:Budget]]

GRASS GIS Community Meeting 2024: Budget

2023-12-20T18:55:50Z

Wenzeslaus: /* Basic Information */ Add myself as contact person for budget

The following information is requested as part of [[Code_Sprint_Guidelines|OSGeo Code Sprint Guidelines]].

== Request for support of the GRASS GIS Community Meeting 2024 ==

=== Basic Information ===

The GRASS GIS community meeting will take place in June or July, 2024 in Prague. The event is organized by a group formed by GRASS GIS PSC. Contact person for budget questions is Vaclav Petras.

==== Audience ====

Based on previous events, we expect between 10 and 20 people for this meeting. The meeting is open to all users, supporters, contributors, power users and developers who want to make a meaningful contribution to the project. To maximize participation, we are raising money for travel and other expenses. Last year, a total of 17 people participated in the event in-person, additional 4 people participated remotely, and 2 leaders from other projects connected remotely as well.

==== Region ====

The event is global. The in-person meeting will take place in Prague, Czechia.

==== Project and Focus ====

Building on momentum from the 40th birthday meeting, we will continue the revisions of the maintenance processes and infrastructure - a process which highly benefits from the current maintainers being in one place (and time zone). Other topics which require highly synchronous collaboration will be included such as Markdown documentation and CMake build transitions. Other contributors are expected to enhance the collection of processing tools and their documentation. A [https://grass.osgeo.org/news/2023_08_13_grass_community_meeting_prague_june_2023_report/ press release] gives an overview of last year's event.

==== Length ====

The meeting will last 5 days. Last year's event included a weekend to support participants who need to join outside of their work.

==== Venue ====

The space for the event is being negotiated. We are working towards an in-kind contribution of the space for the event.

=== Expected Budget ===

==== Costs ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! EUR
! USD
! Explanation
|-
| Participant travel and lodging
| 13,000.00
| 14,300.00
| Average 867 EUR per person estimated from 2023 expenses (15 participants)
|-
| Food, drink, snacks
| 3,000.00
| 3,300.00
| 15 participants, 5 days, 40 EUR per day and person (estimated from 2023 rate)
|-
| Venue small expenses
| 100.00
| 110.00
| 40 EUR Wifi fee, office supplies (estimated from 2023)
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Sponsorship ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! '''EUR'''
! '''USD'''
! Explanation
|-
| OSGeo
| 5,000.00
| 5,500.00
| OSGeo budget for sprints
|-
| In-kind contributions
| 7,000.00
| 7,700.00
| Estimated payments covered by other organizations (travel, lodging)
|-
| Community contributions
| 4,100.00
| 4,510.00
| Newly or previously collected donations to GRASS GIS
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Non-monetary In-kind Contributions ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! Contributors
|-
|Space
|To be negotiated
|-
| Time for planning
| North Carolina State University, CONICET, Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis
|-
| Time for participation
| North Carolina State University, Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis
|}

==== Profit, Loss and Risk ====

There is no fee for participation and no profit is expected. Surplus money will go to the general GRASS budget, that is esp. the [https://grasswiki.osgeo.org/wiki/Student_Grants student mini grant program]. Assuming the travel will be reimbursed to participants, the risk of canceled and not taken flights is taken by the potential participants. No or insufficient funding will lead to lower participation. Last year, most participants asked for and received travel support. Loss or failure to acquire the anticipated in-kind contributions will result in a significantly smaller event unless a sponsor steps in.

[[Category:Code Sprints]]
[[Category:C Tribe Code Sprint]]
[[Category:Budget]]

GRASS GIS Community Meeting 2024: Budget

2023-12-15T22:53:54Z

Wenzeslaus: /* Venue */

The following information is requested as part of [[Code_Sprint_Guidelines|OSGeo Code Sprint Guidelines]].

== Request for support of the GRASS GIS Community Meeting 2024 ==

=== Basic Information ===

The GRASS GIS community meeting will take place in June or July, 2024 in Prague. The event is organized by a group formed by GRASS GIS PSC.

==== Audience ====

Based on previous events, we expect between 10 and 20 people for this meeting. The meeting is open to all users, supporters, contributors, power users and developers who want to make a meaningful contribution to the project. To maximize participation, we are raising money for travel and other expenses. Last year, a total of 17 people participated in the event in-person, additional 4 people participated remotely, and 2 leaders from other projects connected remotely as well.

==== Region ====

The event is global. The in-person meeting will take place in Prague, Czechia.

==== Project and Focus ====

Building on momentum from the 40th birthday meeting, we will continue the revisions of the maintenance processes and infrastructure - a process which highly benefits from the current maintainers being in one place (and time zone). Other topics which require highly synchronous collaboration will be included such as Markdown documentation and CMake build transitions. Other contributors are expected to enhance the collection of processing tools and their documentation. A [https://grass.osgeo.org/news/2023_08_13_grass_community_meeting_prague_june_2023_report/ press release] gives an overview of last year's event.

==== Length ====

The meeting will last 5 days. Last year's event included a weekend to support participants who need to join outside of their work.

==== Venue ====

The space for the event is being negotiated. We are working towards an in-kind contribution of the space for the event.

=== Expected Budget ===

==== Costs ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! EUR
! USD
! Explanation
|-
| Participant travel and lodging
| 13,000.00
| 14,300.00
| Average 867 EUR per person estimated from 2023 expenses (15 participants)
|-
| Food, drink, snacks
| 3,000.00
| 3,300.00
| 15 participants, 5 days, 40 EUR per day and person (estimated from 2023 rate)
|-
| Venue small expenses
| 100.00
| 110.00
| 40 EUR Wifi fee, office supplies (estimated from 2023)
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Sponsorship ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! '''EUR'''
! '''USD'''
! Explanation
|-
| OSGeo
| 5,000.00
| 5,500.00
| OSGeo budget for sprints
|-
| In-kind contributions
| 7,000.00
| 7,700.00
| Estimated payments covered by other organizations (travel, lodging)
|-
| Community contributions
| 4,100.00
| 4,510.00
| Newly or previously collected donations to GRASS GIS
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Non-monetary In-kind Contributions ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! Contributors
|-
|Space
|To be negotiated
|-
| Time for planning
| North Carolina State University, CONICET, Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis
|-
| Time for participation
| North Carolina State University, Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis
|}

==== Profit, Loss and Risk ====

There is no fee for participation and no profit is expected. Surplus money will go to the general GRASS budget, that is esp. the [https://grasswiki.osgeo.org/wiki/Student_Grants student mini grant program]. Assuming the travel will be reimbursed to participants, the risk of canceled and not taken flights is taken by the potential participants. No or insufficient funding will lead to lower participation. Last year, most participants asked for and received travel support. Loss or failure to acquire the anticipated in-kind contributions will result in a significantly smaller event unless a sponsor steps in.

[[Category:Code Sprints]]
[[Category:C Tribe Code Sprint]]
[[Category:Budget]]

GRASS GIS Community Meeting 2024: Budget

2023-12-15T22:53:01Z

Wenzeslaus: /* Audience */

The following information is requested as part of [[Code_Sprint_Guidelines|OSGeo Code Sprint Guidelines]].

== Request for support of the GRASS GIS Community Meeting 2024 ==

=== Basic Information ===

The GRASS GIS community meeting will take place in June or July, 2024 in Prague. The event is organized by a group formed by GRASS GIS PSC.

==== Audience ====

Based on previous events, we expect between 10 and 20 people for this meeting. The meeting is open to all users, supporters, contributors, power users and developers who want to make a meaningful contribution to the project. To maximize participation, we are raising money for travel and other expenses. Last year, a total of 17 people participated in the event in-person, additional 4 people participated remotely, and 2 leaders from other projects connected remotely as well.

==== Region ====

The event is global. The in-person meeting will take place in Prague, Czechia.

==== Project and Focus ====

Building on momentum from the 40th birthday meeting, we will continue the revisions of the maintenance processes and infrastructure - a process which highly benefits from the current maintainers being in one place (and time zone). Other topics which require highly synchronous collaboration will be included such as Markdown documentation and CMake build transitions. Other contributors are expected to enhance the collection of processing tools and their documentation. A [https://grass.osgeo.org/news/2023_08_13_grass_community_meeting_prague_june_2023_report/ press release] gives an overview of last year's event.

==== Length ====

The meeting will last 5 days. Last year's event included a weekend to support participants who need to join outside of their work.

==== Venue ====

The space for the event is being negotiated. We are working towards an in-kind contribution of the space.

=== Expected Budget ===

==== Costs ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! EUR
! USD
! Explanation
|-
| Participant travel and lodging
| 13,000.00
| 14,300.00
| Average 867 EUR per person estimated from 2023 expenses (15 participants)
|-
| Food, drink, snacks
| 3,000.00
| 3,300.00
| 15 participants, 5 days, 40 EUR per day and person (estimated from 2023 rate)
|-
| Venue small expenses
| 100.00
| 110.00
| 40 EUR Wifi fee, office supplies (estimated from 2023)
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Sponsorship ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! '''EUR'''
! '''USD'''
! Explanation
|-
| OSGeo
| 5,000.00
| 5,500.00
| OSGeo budget for sprints
|-
| In-kind contributions
| 7,000.00
| 7,700.00
| Estimated payments covered by other organizations (travel, lodging)
|-
| Community contributions
| 4,100.00
| 4,510.00
| Newly or previously collected donations to GRASS GIS
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Non-monetary In-kind Contributions ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! Contributors
|-
|Space
|To be negotiated
|-
| Time for planning
| North Carolina State University, CONICET, Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis
|-
| Time for participation
| North Carolina State University, Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis
|}

==== Profit, Loss and Risk ====

There is no fee for participation and no profit is expected. Surplus money will go to the general GRASS budget, that is esp. the [https://grasswiki.osgeo.org/wiki/Student_Grants student mini grant program]. Assuming the travel will be reimbursed to participants, the risk of canceled and not taken flights is taken by the potential participants. No or insufficient funding will lead to lower participation. Last year, most participants asked for and received travel support. Loss or failure to acquire the anticipated in-kind contributions will result in a significantly smaller event unless a sponsor steps in.

[[Category:Code Sprints]]
[[Category:C Tribe Code Sprint]]
[[Category:Budget]]

GRASS GIS Community Meeting 2024: Budget

2023-12-15T22:52:33Z

Wenzeslaus: /* Length */

The following information is requested as part of [[Code_Sprint_Guidelines|OSGeo Code Sprint Guidelines]].

== Request for support of the GRASS GIS Community Meeting 2024 ==

=== Basic Information ===

The GRASS GIS community meeting will take place in June or July, 2024 in Prague. The event is organized by a group formed by GRASS GIS PSC.

==== Audience ====

Based on previous events, we expect between 10 and 20 people for this meeting. The meeting is open to all users, supporters, contributors, power users and developers who want to make a meaningful contribution to the project. To maximize participation, we are raising money for travel and other expenses. Last year, total of 17 people participated in the event in-person, additional 4 people participated remotely, and 2 leaders from other projects connected remotely as well.

==== Region ====

The event is global. The in-person meeting will take place in Prague, Czechia.

==== Project and Focus ====

Building on momentum from the 40th birthday meeting, we will continue the revisions of the maintenance processes and infrastructure - a process which highly benefits from the current maintainers being in one place (and time zone). Other topics which require highly synchronous collaboration will be included such as Markdown documentation and CMake build transitions. Other contributors are expected to enhance the collection of processing tools and their documentation. A [https://grass.osgeo.org/news/2023_08_13_grass_community_meeting_prague_june_2023_report/ press release] gives an overview of last year's event.

==== Length ====

The meeting will last 5 days. Last year's event included a weekend to support participants who need to join outside of their work.

==== Venue ====

The space for the event is being negotiated. We are working towards an in-kind contribution of the space.

=== Expected Budget ===

==== Costs ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! EUR
! USD
! Explanation
|-
| Participant travel and lodging
| 13,000.00
| 14,300.00
| Average 867 EUR per person estimated from 2023 expenses (15 participants)
|-
| Food, drink, snacks
| 3,000.00
| 3,300.00
| 15 participants, 5 days, 40 EUR per day and person (estimated from 2023 rate)
|-
| Venue small expenses
| 100.00
| 110.00
| 40 EUR Wifi fee, office supplies (estimated from 2023)
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Sponsorship ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! '''EUR'''
! '''USD'''
! Explanation
|-
| OSGeo
| 5,000.00
| 5,500.00
| OSGeo budget for sprints
|-
| In-kind contributions
| 7,000.00
| 7,700.00
| Estimated payments covered by other organizations (travel, lodging)
|-
| Community contributions
| 4,100.00
| 4,510.00
| Newly or previously collected donations to GRASS GIS
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Non-monetary In-kind Contributions ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! Contributors
|-
|Space
|To be negotiated
|-
| Time for planning
| North Carolina State University, CONICET, Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis
|-
| Time for participation
| North Carolina State University, Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis
|}

==== Profit, Loss and Risk ====

There is no fee for participation and no profit is expected. Surplus money will go to the general GRASS budget, that is esp. the [https://grasswiki.osgeo.org/wiki/Student_Grants student mini grant program]. Assuming the travel will be reimbursed to participants, the risk of canceled and not taken flights is taken by the potential participants. No or insufficient funding will lead to lower participation. Last year, most participants asked for and received travel support. Loss or failure to acquire the anticipated in-kind contributions will result in a significantly smaller event unless a sponsor steps in.

[[Category:Code Sprints]]
[[Category:C Tribe Code Sprint]]
[[Category:Budget]]

GRASS GIS Community Meeting 2024: Budget

2023-12-15T22:23:19Z

Wenzeslaus: /* Length */

The following information is requested as part of [[Code_Sprint_Guidelines|OSGeo Code Sprint Guidelines]].

== Request for support of the GRASS GIS Community Meeting 2024 ==

=== Basic Information ===

The GRASS GIS community meeting will take place in June or July, 2024 in Prague. The event is organized by a group formed by GRASS GIS PSC.

==== Audience ====

Based on previous events, we expect between 10 and 20 people for this meeting. The meeting is open to all users, supporters, contributors, power users and developers who want to make a meaningful contribution to the project. To maximize participation, we are raising money for travel and other expenses. Last year, total of 17 people participated in the event in-person, additional 4 people participated remotely, and 2 leaders from other projects connected remotely as well.

==== Region ====

The event is global. The in-person meeting will take place in Prague, Czechia.

==== Project and Focus ====

Building on momentum from the 40th birthday meeting, we will continue the revisions of the maintenance processes and infrastructure - a process which highly benefits from the current maintainers being in one place (and time zone). Other topics which require highly synchronous collaboration will be included such as Markdown documentation and CMake build transitions. Other contributors are expected to enhance the collection of processing tools and their documentation. A [https://grass.osgeo.org/news/2023_08_13_grass_community_meeting_prague_june_2023_report/ press release] gives an overview of last year's event.

==== Length ====

The meeting will last 5 days. Last year's event included weekend to support participants who need to join outside of their work.

==== Venue ====

The space for the event is being negotiated. We are working towards an in-kind contribution of the space.

=== Expected Budget ===

==== Costs ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! EUR
! USD
! Explanation
|-
| Participant travel and lodging
| 13,000.00
| 14,300.00
| Average 867 EUR per person estimated from 2023 expenses (15 participants)
|-
| Food, drink, snacks
| 3,000.00
| 3,300.00
| 15 participants, 5 days, 40 EUR per day and person (estimated from 2023 rate)
|-
| Venue small expenses
| 100.00
| 110.00
| 40 EUR Wifi fee, office supplies (estimated from 2023)
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Sponsorship ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! '''EUR'''
! '''USD'''
! Explanation
|-
| OSGeo
| 5,000.00
| 5,500.00
| OSGeo budget for sprints
|-
| In-kind contributions
| 7,000.00
| 7,700.00
| Estimated payments covered by other organizations (travel, lodging)
|-
| Community contributions
| 4,100.00
| 4,510.00
| Newly or previously collected donations to GRASS GIS
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Non-monetary In-kind Contributions ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! Contributors
|-
|Space
|To be negotiated
|-
| Time for planning
| North Carolina State University, CONICET, Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis
|-
| Time for participation
| North Carolina State University, Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis
|}

==== Profit, Loss and Risk ====

There is no fee for participation and no profit is expected. Surplus money will go to the general GRASS budget, that is esp. the [https://grasswiki.osgeo.org/wiki/Student_Grants student mini grant program]. Assuming the travel will be reimbursed to participants, the risk of canceled and not taken flights is taken by the potential participants. No or insufficient funding will lead to lower participation. Last year, most participants asked for and received travel support. Loss or failure to acquire the anticipated in-kind contributions will result in a significantly smaller event unless a sponsor steps in.

[[Category:Code Sprints]]
[[Category:C Tribe Code Sprint]]
[[Category:Budget]]

GRASS GIS Community Meeting 2024: Budget

2023-12-15T22:23:00Z

Wenzeslaus: /* Basic Information */

The following information is requested as part of [[Code_Sprint_Guidelines|OSGeo Code Sprint Guidelines]].

== Request for support of the GRASS GIS Community Meeting 2024 ==

=== Basic Information ===

The GRASS GIS community meeting will take place in June or July, 2024 in Prague. The event is organized by a group formed by GRASS GIS PSC.

==== Audience ====

Based on previous events, we expect between 10 and 20 people for this meeting. The meeting is open to all users, supporters, contributors, power users and developers who want to make a meaningful contribution to the project. To maximize participation, we are raising money for travel and other expenses. Last year, total of 17 people participated in the event in-person, additional 4 people participated remotely, and 2 leaders from other projects connected remotely as well.

==== Region ====

The event is global. The in-person meeting will take place in Prague, Czechia.

==== Project and Focus ====

Building on momentum from the 40th birthday meeting, we will continue the revisions of the maintenance processes and infrastructure - a process which highly benefits from the current maintainers being in one place (and time zone). Other topics which require highly synchronous collaboration will be included such as Markdown documentation and CMake build transitions. Other contributors are expected to enhance the collection of processing tools and their documentation. A [https://grass.osgeo.org/news/2023_08_13_grass_community_meeting_prague_june_2023_report/ press release] gives an overview of last year's event.

==== Length ====

The meeting will last 5 days. Last year event included weekend to support participants who need to join outside of their work.

==== Venue ====

The space for the event is being negotiated. We are working towards an in-kind contribution of the space.

=== Expected Budget ===

==== Costs ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! EUR
! USD
! Explanation
|-
| Participant travel and lodging
| 13,000.00
| 14,300.00
| Average 867 EUR per person estimated from 2023 expenses (15 participants)
|-
| Food, drink, snacks
| 3,000.00
| 3,300.00
| 15 participants, 5 days, 40 EUR per day and person (estimated from 2023 rate)
|-
| Venue small expenses
| 100.00
| 110.00
| 40 EUR Wifi fee, office supplies (estimated from 2023)
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Sponsorship ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! '''EUR'''
! '''USD'''
! Explanation
|-
| OSGeo
| 5,000.00
| 5,500.00
| OSGeo budget for sprints
|-
| In-kind contributions
| 7,000.00
| 7,700.00
| Estimated payments covered by other organizations (travel, lodging)
|-
| Community contributions
| 4,100.00
| 4,510.00
| Newly or previously collected donations to GRASS GIS
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Non-monetary In-kind Contributions ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! Contributors
|-
|Space
|To be negotiated
|-
| Time for planning
| North Carolina State University, CONICET, Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis
|-
| Time for participation
| North Carolina State University, Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis
|}

==== Profit, Loss and Risk ====

There is no fee for participation and no profit is expected. Surplus money will go to the general GRASS budget, that is esp. the [https://grasswiki.osgeo.org/wiki/Student_Grants student mini grant program]. Assuming the travel will be reimbursed to participants, the risk of canceled and not taken flights is taken by the potential participants. No or insufficient funding will lead to lower participation. Last year, most participants asked for and received travel support. Loss or failure to acquire the anticipated in-kind contributions will result in a significantly smaller event unless a sponsor steps in.

[[Category:Code Sprints]]
[[Category:C Tribe Code Sprint]]
[[Category:Budget]]

GRASS GIS Community Meeting 2024: Budget

2023-12-15T22:22:23Z

Wenzeslaus: /* Length */

The following information is requested as part of [[Code_Sprint_Guidelines|OSGeo Code Sprint Guidelines]].

== Request for support of the GRASS GIS Community Meeting 2024 ==

=== Basic Information ===

The GRASS GIS community meeting will take place in June or July, 2024 in Prague.

==== Audience ====

Based on previous events, we expect between 10 and 20 people for this meeting. The meeting is open to all users, supporters, contributors, power users and developers who want to make a meaningful contribution to the project. To maximize participation, we are raising money for travel and other expenses. Last year, total of 17 people participated in the event in-person, additional 4 people participated remotely, and 2 leaders from other projects connected remotely as well.

==== Region ====

The event is global. The in-person meeting will take place in Prague, Czechia.

==== Project and Focus ====

Building on momentum from the 40th birthday meeting, we will continue the revisions of the maintenance processes and infrastructure - a process which highly benefits from the current maintainers being in one place (and time zone). Other topics which require highly synchronous collaboration will be included such as Markdown documentation and CMake build transitions. Other contributors are expected to enhance the collection of processing tools and their documentation. A [https://grass.osgeo.org/news/2023_08_13_grass_community_meeting_prague_june_2023_report/ press release] gives an overview of last year's event.

==== Length ====

The meeting will last 5 days. Last year event included weekend to support participants who need to join outside of their work.

==== Venue ====

The space for the event is being negotiated. We are working towards an in-kind contribution of the space.

=== Expected Budget ===

==== Costs ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! EUR
! USD
! Explanation
|-
| Participant travel and lodging
| 13,000.00
| 14,300.00
| Average 867 EUR per person estimated from 2023 expenses (15 participants)
|-
| Food, drink, snacks
| 3,000.00
| 3,300.00
| 15 participants, 5 days, 40 EUR per day and person (estimated from 2023 rate)
|-
| Venue small expenses
| 100.00
| 110.00
| 40 EUR Wifi fee, office supplies (estimated from 2023)
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Sponsorship ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! '''EUR'''
! '''USD'''
! Explanation
|-
| OSGeo
| 5,000.00
| 5,500.00
| OSGeo budget for sprints
|-
| In-kind contributions
| 7,000.00
| 7,700.00
| Estimated payments covered by other organizations (travel, lodging)
|-
| Community contributions
| 4,100.00
| 4,510.00
| Newly or previously collected donations to GRASS GIS
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Non-monetary In-kind Contributions ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! Contributors
|-
|Space
|To be negotiated
|-
| Time for planning
| North Carolina State University, CONICET, Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis
|-
| Time for participation
| North Carolina State University, Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis
|}

==== Profit, Loss and Risk ====

There is no fee for participation and no profit is expected. Surplus money will go to the general GRASS budget, that is esp. the [https://grasswiki.osgeo.org/wiki/Student_Grants student mini grant program]. Assuming the travel will be reimbursed to participants, the risk of canceled and not taken flights is taken by the potential participants. No or insufficient funding will lead to lower participation. Last year, most participants asked for and received travel support. Loss or failure to acquire the anticipated in-kind contributions will result in a significantly smaller event unless a sponsor steps in.

[[Category:Code Sprints]]
[[Category:C Tribe Code Sprint]]
[[Category:Budget]]

GRASS GIS Community Meeting 2024: Budget

2023-12-15T22:19:10Z

Wenzeslaus: /* Project and Focus */

The following information is requested as part of [[Code_Sprint_Guidelines|OSGeo Code Sprint Guidelines]].

== Request for support of the GRASS GIS Community Meeting 2024 ==

=== Basic Information ===

The GRASS GIS community meeting will take place in June or July, 2024 in Prague.

==== Audience ====

Based on previous events, we expect between 10 and 20 people for this meeting. The meeting is open to all users, supporters, contributors, power users and developers who want to make a meaningful contribution to the project. To maximize participation, we are raising money for travel and other expenses. Last year, total of 17 people participated in the event in-person, additional 4 people participated remotely, and 2 leaders from other projects connected remotely as well.

==== Region ====

The event is global. The in-person meeting will take place in Prague, Czechia.

==== Project and Focus ====

Building on momentum from the 40th birthday meeting, we will continue the revisions of the maintenance processes and infrastructure - a process which highly benefits from the current maintainers being in one place (and time zone). Other topics which require highly synchronous collaboration will be included such as Markdown documentation and CMake build transitions. Other contributors are expected to enhance the collection of processing tools and their documentation. A [https://grass.osgeo.org/news/2023_08_13_grass_community_meeting_prague_june_2023_report/ press release] gives an overview of last year's event.

==== Length ====

The meeting will last 5 days which include a weekend to support participants who need to join outside of their work (determined by the planning team).

==== Venue ====

The space for the event is being negotiated. We are working towards an in-kind contribution of the space.

=== Expected Budget ===

==== Costs ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! EUR
! USD
! Explanation
|-
| Participant travel and lodging
| 13,000.00
| 14,300.00
| Average 867 EUR per person estimated from 2023 expenses (15 participants)
|-
| Food, drink, snacks
| 3,000.00
| 3,300.00
| 15 participants, 5 days, 40 EUR per day and person (estimated from 2023 rate)
|-
| Venue small expenses
| 100.00
| 110.00
| 40 EUR Wifi fee, office supplies (estimated from 2023)
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Sponsorship ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! '''EUR'''
! '''USD'''
! Explanation
|-
| OSGeo
| 5,000.00
| 5,500.00
| OSGeo budget for sprints
|-
| In-kind contributions
| 7,000.00
| 7,700.00
| Estimated payments covered by other organizations (travel, lodging)
|-
| Community contributions
| 4,100.00
| 4,510.00
| Newly or previously collected donations to GRASS GIS
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Non-monetary In-kind Contributions ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! Contributors
|-
|Space
|To be negotiated
|-
| Time for planning
| North Carolina State University, CONICET, Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis
|-
| Time for participation
| North Carolina State University, Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis
|}

==== Profit, Loss and Risk ====

There is no fee for participation and no profit is expected. Surplus money will go to the general GRASS budget, that is esp. the [https://grasswiki.osgeo.org/wiki/Student_Grants student mini grant program]. Assuming the travel will be reimbursed to participants, the risk of canceled and not taken flights is taken by the potential participants. No or insufficient funding will lead to lower participation. Last year, most participants asked for and received travel support. Loss or failure to acquire the anticipated in-kind contributions will result in a significantly smaller event unless a sponsor steps in.

[[Category:Code Sprints]]
[[Category:C Tribe Code Sprint]]
[[Category:Budget]]

GRASS GIS Community Meeting 2024: Budget

2023-12-15T21:36:57Z

Wenzeslaus: /* Profit, Loss and Risk */

The following information is requested as part of [[Code_Sprint_Guidelines|OSGeo Code Sprint Guidelines]].

== Request for support of the GRASS GIS Community Meeting 2024 ==

=== Basic Information ===

The GRASS GIS community meeting will take place in June or July, 2024 in Prague.

==== Audience ====

Based on previous events, we expect between 10 and 20 people for this meeting. The meeting is open to all users, supporters, contributors, power users and developers who want to make a meaningful contribution to the project. To maximize participation, we are raising money for travel and other expenses. Last year, total of 17 people participated in the event in-person, additional 4 people participated remotely, and 2 leaders from other projects connected remotely as well.

==== Region ====

The event is global. The in-person meeting will take place in Prague, Czechia.

==== Project and Focus ====

(to be updated)

We will work on GRASS GIS and integrations with related OSGeo projects. We will revise connection to QGIS to make it easier to maintain, and we will migrate the build to CMake to improve Windows builds including PDAL support. Furthermore, we will move documentation to Markdown to make it easier to contribute to and we will add images and examples for tools and workflows which still miss them. Finally, we will automate and document maintenance processes to reduce the burden on maintainers and thus improve the project sustainability.

A [https://grass.osgeo.org/news/2023_08_13_grass_community_meeting_prague_june_2023_report/ press release] gives an overview of the last year's event.

==== Length ====

The meeting will last 5 days which include a weekend to support participants who need to join outside of their work (determined by the planning team).

==== Venue ====

The space for the event is being negotiated. We are working towards an in-kind contribution of the space.

=== Expected Budget ===

==== Costs ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! EUR
! USD
! Explanation
|-
| Participant travel and lodging
| 13,000.00
| 14,300.00
| Average 867 EUR per person estimated from 2023 expenses (15 participants)
|-
| Food, drink, snacks
| 3,000.00
| 3,300.00
| 15 participants, 5 days, 40 EUR per day and person (estimated from 2023 rate)
|-
| Venue small expenses
| 100.00
| 110.00
| 40 EUR Wifi fee, office supplies (estimated from 2023)
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Sponsorship ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! '''EUR'''
! '''USD'''
! Explanation
|-
| OSGeo
| 5,000.00
| 5,500.00
| OSGeo budget for sprints
|-
| In-kind contributions
| 7,000.00
| 7,700.00
| Estimated payments covered by other organizations (travel, lodging)
|-
| Community contributions
| 4,100.00
| 4,510.00
| Newly or previously collected donations to GRASS GIS
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Non-monetary In-kind Contributions ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! Contributors
|-
|Space
|To be negotiated
|-
| Time for planning
| North Carolina State University, CONICET, Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis
|-
| Time for participation
| North Carolina State University, Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis
|}

==== Profit, Loss and Risk ====

There is no fee for participation and no profit is expected. Surplus money will go to the general GRASS budget, that is esp. the [https://grasswiki.osgeo.org/wiki/Student_Grants student mini grant program]. Assuming the travel will be reimbursed to participants, the risk of canceled and not taken flights is taken by the potential participants. No or insufficient funding will lead to lower participation. Last year, most participants asked for and received travel support. Loss or failure to acquire the anticipated in-kind contributions will result in a significantly smaller event unless a sponsor steps in.

[[Category:Code Sprints]]
[[Category:C Tribe Code Sprint]]
[[Category:Budget]]

GRASS GIS Community Meeting 2024: Budget

2023-12-15T21:32:03Z

Wenzeslaus: /* Non-monetary In-kind Contributions */

The following information is requested as part of [[Code_Sprint_Guidelines|OSGeo Code Sprint Guidelines]].

== Request for support of the GRASS GIS Community Meeting 2024 ==

=== Basic Information ===

The GRASS GIS community meeting will take place in June or July, 2024 in Prague.

==== Audience ====

Based on previous events, we expect between 10 and 20 people for this meeting. The meeting is open to all users, supporters, contributors, power users and developers who want to make a meaningful contribution to the project. To maximize participation, we are raising money for travel and other expenses. Last year, total of 17 people participated in the event in-person, additional 4 people participated remotely, and 2 leaders from other projects connected remotely as well.

==== Region ====

The event is global. The in-person meeting will take place in Prague, Czechia.

==== Project and Focus ====

(to be updated)

We will work on GRASS GIS and integrations with related OSGeo projects. We will revise connection to QGIS to make it easier to maintain, and we will migrate the build to CMake to improve Windows builds including PDAL support. Furthermore, we will move documentation to Markdown to make it easier to contribute to and we will add images and examples for tools and workflows which still miss them. Finally, we will automate and document maintenance processes to reduce the burden on maintainers and thus improve the project sustainability.

A [https://grass.osgeo.org/news/2023_08_13_grass_community_meeting_prague_june_2023_report/ press release] gives an overview of the last year's event.

==== Length ====

The meeting will last 5 days which include a weekend to support participants who need to join outside of their work (determined by the planning team).

==== Venue ====

The space for the event is being negotiated. We are working towards an in-kind contribution of the space.

=== Expected Budget ===

==== Costs ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! EUR
! USD
! Explanation
|-
| Participant travel and lodging
| 13,000.00
| 14,300.00
| Average 867 EUR per person estimated from 2023 expenses (15 participants)
|-
| Food, drink, snacks
| 3,000.00
| 3,300.00
| 15 participants, 5 days, 40 EUR per day and person (estimated from 2023 rate)
|-
| Venue small expenses
| 100.00
| 110.00
| 40 EUR Wifi fee, office supplies (estimated from 2023)
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Sponsorship ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! '''EUR'''
! '''USD'''
! Explanation
|-
| OSGeo
| 5,000.00
| 5,500.00
| OSGeo budget for sprints
|-
| In-kind contributions
| 7,000.00
| 7,700.00
| Estimated payments covered by other organizations (travel, lodging)
|-
| Community contributions
| 4,100.00
| 4,510.00
| Newly or previously collected donations to GRASS GIS
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Non-monetary In-kind Contributions ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! Contributors
|-
|Space
|To be negotiated
|-
| Time for planning
| North Carolina State University, CONICET, Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis
|-
| Time for participation
| North Carolina State University, Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis
|}

==== Profit, Loss and Risk ====

There is no fee for participation and no profit is expected. Surplus money will go to the general GRASS budget, that is esp. the [https://grasswiki.osgeo.org/wiki/Student_Grants student mini grant program]. Assuming the travel will be reimbursed to participants, the risk of canceled and not taken flights is taken by the potential participants. No or insufficient funding will lead to lower participation. Last year, most participants asked for and received travel support.

[[Category:Code Sprints]]
[[Category:C Tribe Code Sprint]]
[[Category:Budget]]

GRASS GIS Community Meeting 2024: Budget

2023-12-15T21:29:02Z

Wenzeslaus: /* Profit, Loss and Risk */

The following information is requested as part of [[Code_Sprint_Guidelines|OSGeo Code Sprint Guidelines]].

== Request for support of the GRASS GIS Community Meeting 2024 ==

=== Basic Information ===

The GRASS GIS community meeting will take place in June or July, 2024 in Prague.

==== Audience ====

Based on previous events, we expect between 10 and 20 people for this meeting. The meeting is open to all users, supporters, contributors, power users and developers who want to make a meaningful contribution to the project. To maximize participation, we are raising money for travel and other expenses. Last year, total of 17 people participated in the event in-person, additional 4 people participated remotely, and 2 leaders from other projects connected remotely as well.

==== Region ====

The event is global. The in-person meeting will take place in Prague, Czechia.

==== Project and Focus ====

(to be updated)

We will work on GRASS GIS and integrations with related OSGeo projects. We will revise connection to QGIS to make it easier to maintain, and we will migrate the build to CMake to improve Windows builds including PDAL support. Furthermore, we will move documentation to Markdown to make it easier to contribute to and we will add images and examples for tools and workflows which still miss them. Finally, we will automate and document maintenance processes to reduce the burden on maintainers and thus improve the project sustainability.

A [https://grass.osgeo.org/news/2023_08_13_grass_community_meeting_prague_june_2023_report/ press release] gives an overview of the last year's event.

==== Length ====

The meeting will last 5 days which include a weekend to support participants who need to join outside of their work (determined by the planning team).

==== Venue ====

The space for the event is being negotiated. We are working towards an in-kind contribution of the space.

=== Expected Budget ===

==== Costs ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! EUR
! USD
! Explanation
|-
| Participant travel and lodging
| 13,000.00
| 14,300.00
| Average 867 EUR per person estimated from 2023 expenses (15 participants)
|-
| Food, drink, snacks
| 3,000.00
| 3,300.00
| 15 participants, 5 days, 40 EUR per day and person (estimated from 2023 rate)
|-
| Venue small expenses
| 100.00
| 110.00
| 40 EUR Wifi fee, office supplies (estimated from 2023)
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Sponsorship ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! '''EUR'''
! '''USD'''
! Explanation
|-
| OSGeo
| 5,000.00
| 5,500.00
| OSGeo budget for sprints
|-
| In-kind contributions
| 7,000.00
| 7,700.00
| Estimated payments covered by other organizations (travel, lodging)
|-
| Community contributions
| 4,100.00
| 4,510.00
| Newly or previously collected donations to GRASS GIS
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Non-monetary In-kind Contributions ====

{|
|width="22%"| Space
|width="77%"| To be negotiated
|-
| Time for planning
| North Carolina State University, CONICET, Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis
|-
| Time for participation
| North Carolina State University, Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis
|}

==== Profit, Loss and Risk ====

There is no fee for participation and no profit is expected. Surplus money will go to the general GRASS budget, that is esp. the [https://grasswiki.osgeo.org/wiki/Student_Grants student mini grant program]. Assuming the travel will be reimbursed to participants, the risk of canceled and not taken flights is taken by the potential participants. No or insufficient funding will lead to lower participation. Last year, most participants asked for and received travel support.

[[Category:Code Sprints]]
[[Category:C Tribe Code Sprint]]
[[Category:Budget]]

GRASS GIS Community Meeting 2024: Budget

2023-12-15T21:27:18Z

Wenzeslaus: /* Basic Information */

The following information is requested as part of [[Code_Sprint_Guidelines|OSGeo Code Sprint Guidelines]].

== Request for support of the GRASS GIS Community Meeting 2024 ==

=== Basic Information ===

The GRASS GIS community meeting will take place in June or July, 2024 in Prague.

==== Audience ====

Based on previous events, we expect between 10 and 20 people for this meeting. The meeting is open to all users, supporters, contributors, power users and developers who want to make a meaningful contribution to the project. To maximize participation, we are raising money for travel and other expenses. Last year, total of 17 people participated in the event in-person, additional 4 people participated remotely, and 2 leaders from other projects connected remotely as well.

==== Region ====

The event is global. The in-person meeting will take place in Prague, Czechia.

==== Project and Focus ====

(to be updated)

We will work on GRASS GIS and integrations with related OSGeo projects. We will revise connection to QGIS to make it easier to maintain, and we will migrate the build to CMake to improve Windows builds including PDAL support. Furthermore, we will move documentation to Markdown to make it easier to contribute to and we will add images and examples for tools and workflows which still miss them. Finally, we will automate and document maintenance processes to reduce the burden on maintainers and thus improve the project sustainability.

A [https://grass.osgeo.org/news/2023_08_13_grass_community_meeting_prague_june_2023_report/ press release] gives an overview of the last year's event.

==== Length ====

The meeting will last 5 days which include a weekend to support participants who need to join outside of their work (determined by the planning team).

==== Venue ====

The space for the event is being negotiated. We are working towards an in-kind contribution of the space.

=== Expected Budget ===

==== Costs ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! EUR
! USD
! Explanation
|-
| Participant travel and lodging
| 13,000.00
| 14,300.00
| Average 867 EUR per person estimated from 2023 expenses (15 participants)
|-
| Food, drink, snacks
| 3,000.00
| 3,300.00
| 15 participants, 5 days, 40 EUR per day and person (estimated from 2023 rate)
|-
| Venue small expenses
| 100.00
| 110.00
| 40 EUR Wifi fee, office supplies (estimated from 2023)
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Sponsorship ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! '''EUR'''
! '''USD'''
! Explanation
|-
| OSGeo
| 5,000.00
| 5,500.00
| OSGeo budget for sprints
|-
| In-kind contributions
| 7,000.00
| 7,700.00
| Estimated payments covered by other organizations (travel, lodging)
|-
| Community contributions
| 4,100.00
| 4,510.00
| Newly or previously collected donations to GRASS GIS
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Non-monetary In-kind Contributions ====

{|
|width="22%"| Space
|width="77%"| To be negotiated
|-
| Time for planning
| North Carolina State University, CONICET, Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis
|-
| Time for participation
| North Carolina State University, Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis
|}

==== Profit, Loss and Risk ====

There is no fee for participation and no profit is expected. Surplus money will go to the general GRASS budget, that is esp. the [https://grasswiki.osgeo.org/wiki/Student_Grants student mini grant program]. Assuming the travel will be reimbursed to participants, the risk of canceled and not taken flights is taken by the potential participants. No or insufficient funding will lead to lower participation as several potential participants expressed a high interest in travel support.

[[Category:Code Sprints]]
[[Category:C Tribe Code Sprint]]
[[Category:Budget]]

OSGeo Budget 2024

2023-12-15T20:49:35Z

Wenzeslaus: /* Code Sprints */

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

Total Approved Budget for 2023: $171,650 USD

Total spending for 2023: TBD

Total Approved Budget for 2024: 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
! 2023 Approved
! 2023 Actual
! 2024 Draft
! Notes
|-
| Admin
| style="text-align:right;" | 4,000
| style="text-align:right;" | TBD
| style="text-align:right;" | 4,000
| 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;" | 15,000
| Travel to main FOSS4G, F2F meeting and regional/representative events
|-
| Partners and Sponsors
| style="text-align:right;" | 1,000
| style="text-align:right;" | TBD
| style="text-align:right;" | 1,000
| Relationship building, attending b2b functions, foss4g/foss4ge/foss4gna/foss4g-asia breakfast meetings. Meetings with sponsors during events
|}

Total Board Budget for 2023: $20,000 USD

Total Board spending for 2023: TBD

Total Board Budget for 2024: $20,000 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
! 2023 Approved [Requested]
! 2023 Actual
! 2024 Draft [Requested]
! Notes
|-
| SAC
| style="text-align:right;" | 32,550 [32,550]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| OpenGeoScience
| style="text-align:right;" | 1,500 [3,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| Conference
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| Marketing
| style="text-align:right;" | 4,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
|
|-
| Incubation Committee
| style="text-align:right;" | 6,000 [8,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|}

Total Committees Budget for 2023: $48,550 USD

Total Committees spending for 2023: 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
! 2023 Approved
! 2023 Actual
! 2024 Draft [Requested]
! Notes
|-
| FOSS4G
| style="text-align:right;" | (56,478)
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Seed money for 2024. Not accounted in the total budget, since they are expected to return after the conference.
|-
| 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. Recommendation: 10k for FOSS4G 2024, 5k 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.
|-
| 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 2024. Board note: Budgeted 300$ for each project. To be amended if we hit the ceiling of the budget.
|-
| opengis.org namespace fix
| style="text-align:right;" | 15,000 [20,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|
|}

Total Initiatives Budget for 2023: $55,000 USD

Total Initiatives spending for 2023: TBD

Total Initiatives Budget for 2024: 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 (2024) to the projects mailing list.
* Board decided to assign a default budget of $1000 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 2024 - 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
! 2023 Approved [Requested]
! 2023 Actual
! 2024 Draft [Requested]
! Notes
|-
| deegree
| style="text-align:right;" | 2,000 [2,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GDAL/OGR
| style="text-align:right;" | 1000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoMOOSE
| style="text-align:right;" | 2,500 [2,500]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoNetwork
| style="text-align:right;" | 1,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoNode
| style="text-align:right;" | 1,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GEOS
| style="text-align:right;" | 1,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoServer
| style="text-align:right;" | 4,700 [5,500]
| style="text-align:right;" | TBD
| style="text-align:right;" | 2,000
| [https://github.com/geoserver/geoserver/wiki/GeoServer-2024-Sponsorship-Opportunities GeoServer 2024 Sponsorship Opportunities]
|-
| GeoTools
| style="text-align:right;" | 2000 [10,500]
| style="text-align:right;" | TBD
| style="text-align:right;" | 2,000
| [https://github.com/geotools/geotools/wiki/GeoTools-2024-Sponsorship-Opportunities GeoTools 2024 Sponsorship Opportunities]
|-
| GRASS GIS
| style="text-align:right;" | 5,400 [5,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | 5,000
| [[GRASS GIS Budget 2024]]
|-
| gvSIG
| style="text-align:right;" | 5,000 [5,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | 5,000
| [https://wiki.osgeo.org/wiki/GvSIG_Budget_2024 gvSIG Budget 2024]
|-
| Mapbender
| style="text-align:right;" | 1,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| MapServer
| style="text-align:right;" | 3,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;" | TBD
| style="text-align:right;" | TBD
|
|-
| OTB
| style="text-align:right;" | 1,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| OSGeoLive
| style="text-align:right;" | 1,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| PostGIS
| style="text-align:right;" | 3,500 [3,500]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| PROJ
| style="text-align:right;" | 1,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| pycsw
| style="text-align:right;" | 2,500 [2,500]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| pygeoapi
| style="text-align:right;" | 4,000 [4,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| PyWPS
| style="text-align:right;" | 1,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| QGIS
| style="text-align:right;" | 1,000
| style="text-align:right;" | TBD
| style="text-align:right;" | 5,000
|
|-
| ZOO-Project
| style="text-align:right;" | 300
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| 2023 budget as community project
|-
|}

Total Projects Budget for 2023: $48,100 USD

Total Projects spending for 2023: TBD

Total Projects Budget for 2024: 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
! 2023 Approved [Requested]
! 2023 Actual
! 2024 Approved [Requested]
! Notes
|-
| istSOS
| style="text-align:right;" | 300 [1000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoWebCache
| style="text-align:right;" | 300 [5000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
|}

= Events =

== Community Events ==

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

* 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
! 2023 Approved
! 2023 Actual
! 2024 Approved
! Notes
|-
| List your event here
| 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.
* Our 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
! 2023 Approved
! 2023 Actual
! 2024 Approved
! Notes
|-
| OSGeo Code Sprint
| style="text-align:right;" | 15,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| Bolsena Code Sprint
| style="text-align:right;" | 3,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GRASS GIS Community Meeting
| style="text-align:right;" |
| style="text-align:right;" |
| style="text-align:right;" | 5,500 (requested)
| [[GRASS GIS Community Meeting 2024: Budget]]
|-
|}

= Approval and Amendments =

* Budget Meeting: [[Board_Meeting_2023-12-26]]
* Loomio Motion: TBD
* Amendments: TBD

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

OSGeo Budget 2024

2023-12-15T20:48:28Z

Wenzeslaus: /* Code Sprints */

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

Total Approved Budget for 2023: $171,650 USD

Total spending for 2023: TBD

Total Approved Budget for 2024: 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
! 2023 Approved
! 2023 Actual
! 2024 Draft
! Notes
|-
| Admin
| style="text-align:right;" | 4,000
| style="text-align:right;" | TBD
| style="text-align:right;" | 4,000
| 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;" | 15,000
| Travel to main FOSS4G, F2F meeting and regional/representative events
|-
| Partners and Sponsors
| style="text-align:right;" | 1,000
| style="text-align:right;" | TBD
| style="text-align:right;" | 1,000
| Relationship building, attending b2b functions, foss4g/foss4ge/foss4gna/foss4g-asia breakfast meetings. Meetings with sponsors during events
|}

Total Board Budget for 2023: $20,000 USD

Total Board spending for 2023: TBD

Total Board Budget for 2024: $20,000 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
! 2023 Approved [Requested]
! 2023 Actual
! 2024 Draft [Requested]
! Notes
|-
| SAC
| style="text-align:right;" | 32,550 [32,550]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| OpenGeoScience
| style="text-align:right;" | 1,500 [3,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| Conference
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| Marketing
| style="text-align:right;" | 4,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
|
|-
| Incubation Committee
| style="text-align:right;" | 6,000 [8,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|}

Total Committees Budget for 2023: $48,550 USD

Total Committees spending for 2023: 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
! 2023 Approved
! 2023 Actual
! 2024 Draft [Requested]
! Notes
|-
| FOSS4G
| style="text-align:right;" | (56,478)
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Seed money for 2024. Not accounted in the total budget, since they are expected to return after the conference.
|-
| 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. Recommendation: 10k for FOSS4G 2024, 5k 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.
|-
| 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 2024. Board note: Budgeted 300$ for each project. To be amended if we hit the ceiling of the budget.
|-
| opengis.org namespace fix
| style="text-align:right;" | 15,000 [20,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|
|}

Total Initiatives Budget for 2023: $55,000 USD

Total Initiatives spending for 2023: TBD

Total Initiatives Budget for 2024: 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 (2024) to the projects mailing list.
* Board decided to assign a default budget of $1000 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 2024 - 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
! 2023 Approved [Requested]
! 2023 Actual
! 2024 Draft [Requested]
! Notes
|-
| deegree
| style="text-align:right;" | 2,000 [2,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GDAL/OGR
| style="text-align:right;" | 1000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoMOOSE
| style="text-align:right;" | 2,500 [2,500]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoNetwork
| style="text-align:right;" | 1,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoNode
| style="text-align:right;" | 1,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GEOS
| style="text-align:right;" | 1,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoServer
| style="text-align:right;" | 4,700 [5,500]
| style="text-align:right;" | TBD
| style="text-align:right;" | 2,000
| [https://github.com/geoserver/geoserver/wiki/GeoServer-2024-Sponsorship-Opportunities GeoServer 2024 Sponsorship Opportunities]
|-
| GeoTools
| style="text-align:right;" | 2000 [10,500]
| style="text-align:right;" | TBD
| style="text-align:right;" | 2,000
| [https://github.com/geotools/geotools/wiki/GeoTools-2024-Sponsorship-Opportunities GeoTools 2024 Sponsorship Opportunities]
|-
| GRASS GIS
| style="text-align:right;" | 5,400 [5,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | 5,000
| [[GRASS GIS Budget 2024]]
|-
| gvSIG
| style="text-align:right;" | 5,000 [5,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | 5,000
| [https://wiki.osgeo.org/wiki/GvSIG_Budget_2024 gvSIG Budget 2024]
|-
| Mapbender
| style="text-align:right;" | 1,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| MapServer
| style="text-align:right;" | 3,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;" | TBD
| style="text-align:right;" | TBD
|
|-
| OTB
| style="text-align:right;" | 1,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| OSGeoLive
| style="text-align:right;" | 1,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| PostGIS
| style="text-align:right;" | 3,500 [3,500]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| PROJ
| style="text-align:right;" | 1,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| pycsw
| style="text-align:right;" | 2,500 [2,500]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| pygeoapi
| style="text-align:right;" | 4,000 [4,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| PyWPS
| style="text-align:right;" | 1,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| QGIS
| style="text-align:right;" | 1,000
| style="text-align:right;" | TBD
| style="text-align:right;" | 5,000
|
|-
| ZOO-Project
| style="text-align:right;" | 300
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| 2023 budget as community project
|-
|}

Total Projects Budget for 2023: $48,100 USD

Total Projects spending for 2023: TBD

Total Projects Budget for 2024: 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
! 2023 Approved [Requested]
! 2023 Actual
! 2024 Approved [Requested]
! Notes
|-
| istSOS
| style="text-align:right;" | 300 [1000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoWebCache
| style="text-align:right;" | 300 [5000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
|}

= Events =

== Community Events ==

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

* 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
! 2023 Approved
! 2023 Actual
! 2024 Approved
! Notes
|-
| List your event here
| 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.
* Our 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
! 2023 Approved
! 2023 Actual
! 2024 Approved
! Notes
|-
| OSGeo Code Sprint
| style="text-align:right;" | 15,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| Bolsena Code Sprint
| style="text-align:right;" | 3,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GRASS GIS Community Meeting
| style="text-align:right;" |
| style="text-align:right;" |
| style="text-align:right;" | 5,500
|
|-
|}

= Approval and Amendments =

* Budget Meeting: [[Board_Meeting_2023-12-26]]
* Loomio Motion: TBD
* Amendments: TBD

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

OSGeo Budget 2024

2023-12-15T20:45:11Z

Wenzeslaus: /* OSGeo Projects */

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

Total Approved Budget for 2023: $171,650 USD

Total spending for 2023: TBD

Total Approved Budget for 2024: 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
! 2023 Approved
! 2023 Actual
! 2024 Draft
! Notes
|-
| Admin
| style="text-align:right;" | 4,000
| style="text-align:right;" | TBD
| style="text-align:right;" | 4,000
| 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;" | 15,000
| Travel to main FOSS4G, F2F meeting and regional/representative events
|-
| Partners and Sponsors
| style="text-align:right;" | 1,000
| style="text-align:right;" | TBD
| style="text-align:right;" | 1,000
| Relationship building, attending b2b functions, foss4g/foss4ge/foss4gna/foss4g-asia breakfast meetings. Meetings with sponsors during events
|}

Total Board Budget for 2023: $20,000 USD

Total Board spending for 2023: TBD

Total Board Budget for 2024: $20,000 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
! 2023 Approved [Requested]
! 2023 Actual
! 2024 Draft [Requested]
! Notes
|-
| SAC
| style="text-align:right;" | 32,550 [32,550]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| OpenGeoScience
| style="text-align:right;" | 1,500 [3,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| Conference
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| Marketing
| style="text-align:right;" | 4,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
|
|-
| Incubation Committee
| style="text-align:right;" | 6,000 [8,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|}

Total Committees Budget for 2023: $48,550 USD

Total Committees spending for 2023: 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
! 2023 Approved
! 2023 Actual
! 2024 Draft [Requested]
! Notes
|-
| FOSS4G
| style="text-align:right;" | (56,478)
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Seed money for 2024. Not accounted in the total budget, since they are expected to return after the conference.
|-
| 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. Recommendation: 10k for FOSS4G 2024, 5k 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.
|-
| 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 2024. Board note: Budgeted 300$ for each project. To be amended if we hit the ceiling of the budget.
|-
| opengis.org namespace fix
| style="text-align:right;" | 15,000 [20,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|
|}

Total Initiatives Budget for 2023: $55,000 USD

Total Initiatives spending for 2023: TBD

Total Initiatives Budget for 2024: 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 (2024) to the projects mailing list.
* Board decided to assign a default budget of $1000 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 2024 - 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
! 2023 Approved [Requested]
! 2023 Actual
! 2024 Draft [Requested]
! Notes
|-
| deegree
| style="text-align:right;" | 2,000 [2,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GDAL/OGR
| style="text-align:right;" | 1000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoMOOSE
| style="text-align:right;" | 2,500 [2,500]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoNetwork
| style="text-align:right;" | 1,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoNode
| style="text-align:right;" | 1,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GEOS
| style="text-align:right;" | 1,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoServer
| style="text-align:right;" | 4,700 [5,500]
| style="text-align:right;" | TBD
| style="text-align:right;" | 2,000
| [https://github.com/geoserver/geoserver/wiki/GeoServer-2024-Sponsorship-Opportunities GeoServer 2024 Sponsorship Opportunities]
|-
| GeoTools
| style="text-align:right;" | 2000 [10,500]
| style="text-align:right;" | TBD
| style="text-align:right;" | 2,000
| [https://github.com/geotools/geotools/wiki/GeoTools-2024-Sponsorship-Opportunities GeoTools 2024 Sponsorship Opportunities]
|-
| GRASS GIS
| style="text-align:right;" | 5,400 [5,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | 5,000
| [[GRASS GIS Budget 2024]]
|-
| gvSIG
| style="text-align:right;" | 5,000 [5,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | 5,000
| [https://wiki.osgeo.org/wiki/GvSIG_Budget_2024 gvSIG Budget 2024]
|-
| Mapbender
| style="text-align:right;" | 1,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| MapServer
| style="text-align:right;" | 3,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;" | TBD
| style="text-align:right;" | TBD
|
|-
| OTB
| style="text-align:right;" | 1,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| OSGeoLive
| style="text-align:right;" | 1,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| PostGIS
| style="text-align:right;" | 3,500 [3,500]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| PROJ
| style="text-align:right;" | 1,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| pycsw
| style="text-align:right;" | 2,500 [2,500]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| pygeoapi
| style="text-align:right;" | 4,000 [4,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| PyWPS
| style="text-align:right;" | 1,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| QGIS
| style="text-align:right;" | 1,000
| style="text-align:right;" | TBD
| style="text-align:right;" | 5,000
|
|-
| ZOO-Project
| style="text-align:right;" | 300
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| 2023 budget as community project
|-
|}

Total Projects Budget for 2023: $48,100 USD

Total Projects spending for 2023: TBD

Total Projects Budget for 2024: 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
! 2023 Approved [Requested]
! 2023 Actual
! 2024 Approved [Requested]
! Notes
|-
| istSOS
| style="text-align:right;" | 300 [1000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoWebCache
| style="text-align:right;" | 300 [5000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
|}

= Events =

== Community Events ==

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

* 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
! 2023 Approved
! 2023 Actual
! 2024 Approved
! Notes
|-
| List your event here
| 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
! 2023 Approved
! 2023 Actual
! 2024 Approved
! Notes
|-
| OSGeo Code Sprint
| style="text-align:right;" | 15,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| Bolsena Code Sprint
| style="text-align:right;" | 3,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
|}

= Approval and Amendments =

* Budget Meeting: [[Board_Meeting_2023-12-26]]
* Loomio Motion: TBD
* Amendments: TBD

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

GRASS GIS Budget 2024

2023-12-15T20:26:49Z

Wenzeslaus:

The GRASS GIS project asks for a total budget of '''5000 USD''' from OSGeo to cover the following expenses:

* 2 (our of 4) micro grants for students (see our [https://grasswiki.osgeo.org/wiki/Student_Grants Student grant] program)
* Travel to OSGeo sprint and PSC representation at OSGeo AGM
* Marketing efforts

Other expenses will be covered from additional funding sources such as in-kind contributions and donations at [https://opencollective.com/osgeo/projects/grass Open Collective].

The full budget for GRASS GIS is found at: https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2024

[[Category:Budget]]

GRASS GIS Community Meeting 2024: Budget

2023-12-15T16:50:35Z

Wenzeslaus: /* Sponsorship */

The following information is requested as part of [[Code_Sprint_Guidelines|OSGeo Code Sprint Guidelines]].

== Request for support of the GRASS GIS Community Meeting 2024 ==

=== Basic Information ===

(to be updated)

The GRASS GIS 40th birthday community meeting will take place from June 2 to 6, 2023 in Prague. Further details can be found at [https://grasswiki.osgeo.org/wiki/GRASS_Community_Meeting_Prague_2023 GRASS GIS Community Meeting 2023].

==== Audience ====

Based on previous events, we expect between 10 and 20 people for this meeting. The meeting is open to all users, supporters, contributors, power users and developers who want to make a meaningful contribution to the project. To maximize participation, we are raising money for travel and other expenses. So far, 14 people from four continents expressed interest to participate in-person.

==== Region ====

The event is global. The in-person meeting will take place in Prague, Czechia. The planning team is currently considering what remote participation options would best serve online participants.

==== Project and Focus ====

(to be updated)

We will work on GRASS GIS and integrations with related OSGeo projects. We will revise connection to QGIS to make it easier to maintain, and we will migrate the build to CMake to improve Windows builds including PDAL support. Furthermore, we will move documentation to Markdown to make it easier to contribute to and we will add images and examples for tools and workflows which still miss them. Finally, we will automate and document maintenance processes to reduce the burden on maintainers and thus improve the project sustainability.

==== Length ====

The meeting will last 5 days which include a weekend to support participants who need to join outside of their work (determined by the planning team).

==== Venue ====

(to be updated)

The space for the meeting will be provided by the Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU).

=== Expected Budget ===

==== Costs ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! EUR
! USD
! Explanation
|-
| Participant travel and lodging
| 13,000.00
| 14,300.00
| Average 867 EUR per person estimated from 2023 expenses (15 participants)
|-
| Food, drink, snacks
| 3,000.00
| 3,300.00
| 15 participants, 5 days, 40 EUR per day and person (estimated from 2023 rate)
|-
| Venue small expenses
| 100.00
| 110.00
| 40 EUR Wifi fee, office supplies (estimated from 2023)
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Sponsorship ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! '''EUR'''
! '''USD'''
! Explanation
|-
| OSGeo
| 5,000.00
| 5,500.00
| OSGeo budget for sprints
|-
| In-kind contributions
| 7,000.00
| 7,700.00
| Estimated payments covered by other organizations (travel, lodging)
|-
| Community contributions
| 4,100.00
| 4,510.00
| Newly or previously collected donations to GRASS GIS
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Non-monetary In-kind Contributions ====

{|
|width="22%"| Space
|width="77%"| To be negotiated
|-
| Time for planning
| North Carolina State University, CONICET, Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis
|-
| Time for participation
| North Carolina State University, Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis
|}

==== Profit, Loss and Risk ====

There is no fee for participation and no profit is expected. Surplus money will go to the general GRASS budget, that is esp. the [https://grasswiki.osgeo.org/wiki/Student_Grants student mini grant program]. Assuming the travel will be reimbursed to participants, the risk of canceled and not taken flights is taken by the potential participants. No or insufficient funding will lead to lower participation as several potential participants expressed a high interest in travel support.

[[Category:Code Sprints]]
[[Category:C Tribe Code Sprint]]
[[Category:Budget]]

GRASS GIS Community Meeting 2024: Budget

2023-12-15T16:35:38Z

Wenzeslaus: /* Non-monetary In-kind Contributions */

The following information is requested as part of [[Code_Sprint_Guidelines|OSGeo Code Sprint Guidelines]].

== Request for support of the GRASS GIS Community Meeting 2024 ==

=== Basic Information ===

(to be updated)

The GRASS GIS 40th birthday community meeting will take place from June 2 to 6, 2023 in Prague. Further details can be found at [https://grasswiki.osgeo.org/wiki/GRASS_Community_Meeting_Prague_2023 GRASS GIS Community Meeting 2023].

==== Audience ====

Based on previous events, we expect between 10 and 20 people for this meeting. The meeting is open to all users, supporters, contributors, power users and developers who want to make a meaningful contribution to the project. To maximize participation, we are raising money for travel and other expenses. So far, 14 people from four continents expressed interest to participate in-person.

==== Region ====

The event is global. The in-person meeting will take place in Prague, Czechia. The planning team is currently considering what remote participation options would best serve online participants.

==== Project and Focus ====

(to be updated)

We will work on GRASS GIS and integrations with related OSGeo projects. We will revise connection to QGIS to make it easier to maintain, and we will migrate the build to CMake to improve Windows builds including PDAL support. Furthermore, we will move documentation to Markdown to make it easier to contribute to and we will add images and examples for tools and workflows which still miss them. Finally, we will automate and document maintenance processes to reduce the burden on maintainers and thus improve the project sustainability.

==== Length ====

The meeting will last 5 days which include a weekend to support participants who need to join outside of their work (determined by the planning team).

==== Venue ====

(to be updated)

The space for the meeting will be provided by the Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU).

=== Expected Budget ===

==== Costs ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! EUR
! USD
! Explanation
|-
| Participant travel and lodging
| 13,000.00
| 14,300.00
| Average 867 EUR per person estimated from 2023 expenses (15 participants)
|-
| Food, drink, snacks
| 3,000.00
| 3,300.00
| 15 participants, 5 days, 40 EUR per day and person (estimated from 2023 rate)
|-
| Venue small expenses
| 100.00
| 110.00
| 40 EUR Wifi fee, office supplies (estimated from 2023)
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Sponsorship ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! '''EUR'''
! '''USD'''
! Explanation
|-
| OSGeo
| 5,000.00
| 5,500.00
| OSGeo budget for sprints
|-
| In-kind contributions
| 7,000.00
| 7,700.00
| Estimated payments covered by other organizations (travel, lodging)
|-
| Community contributions
| 4,100.00
| 4,510.00
| Newly or previously collected donations
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Non-monetary In-kind Contributions ====

{|
|width="22%"| Space
|width="77%"| To be negotiated
|-
| Time for planning
| North Carolina State University, CONICET, Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis
|-
| Time for participation
| North Carolina State University, Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis
|}

==== Profit, Loss and Risk ====

There is no fee for participation and no profit is expected. Surplus money will go to the general GRASS budget, that is esp. the [https://grasswiki.osgeo.org/wiki/Student_Grants student mini grant program]. Assuming the travel will be reimbursed to participants, the risk of canceled and not taken flights is taken by the potential participants. No or insufficient funding will lead to lower participation as several potential participants expressed a high interest in travel support.

[[Category:Code Sprints]]
[[Category:C Tribe Code Sprint]]
[[Category:Budget]]

GRASS GIS Community Meeting 2024: Budget

2023-12-15T16:35:23Z

Wenzeslaus: /* Non-monetary In-kind Contributions */

The following information is requested as part of [[Code_Sprint_Guidelines|OSGeo Code Sprint Guidelines]].

== Request for support of the GRASS GIS Community Meeting 2024 ==

=== Basic Information ===

(to be updated)

The GRASS GIS 40th birthday community meeting will take place from June 2 to 6, 2023 in Prague. Further details can be found at [https://grasswiki.osgeo.org/wiki/GRASS_Community_Meeting_Prague_2023 GRASS GIS Community Meeting 2023].

==== Audience ====

Based on previous events, we expect between 10 and 20 people for this meeting. The meeting is open to all users, supporters, contributors, power users and developers who want to make a meaningful contribution to the project. To maximize participation, we are raising money for travel and other expenses. So far, 14 people from four continents expressed interest to participate in-person.

==== Region ====

The event is global. The in-person meeting will take place in Prague, Czechia. The planning team is currently considering what remote participation options would best serve online participants.

==== Project and Focus ====

(to be updated)

We will work on GRASS GIS and integrations with related OSGeo projects. We will revise connection to QGIS to make it easier to maintain, and we will migrate the build to CMake to improve Windows builds including PDAL support. Furthermore, we will move documentation to Markdown to make it easier to contribute to and we will add images and examples for tools and workflows which still miss them. Finally, we will automate and document maintenance processes to reduce the burden on maintainers and thus improve the project sustainability.

==== Length ====

The meeting will last 5 days which include a weekend to support participants who need to join outside of their work (determined by the planning team).

==== Venue ====

(to be updated)

The space for the meeting will be provided by the Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU).

=== Expected Budget ===

==== Costs ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! EUR
! USD
! Explanation
|-
| Participant travel and lodging
| 13,000.00
| 14,300.00
| Average 867 EUR per person estimated from 2023 expenses (15 participants)
|-
| Food, drink, snacks
| 3,000.00
| 3,300.00
| 15 participants, 5 days, 40 EUR per day and person (estimated from 2023 rate)
|-
| Venue small expenses
| 100.00
| 110.00
| 40 EUR Wifi fee, office supplies (estimated from 2023)
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Sponsorship ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! '''EUR'''
! '''USD'''
! Explanation
|-
| OSGeo
| 5,000.00
| 5,500.00
| OSGeo budget for sprints
|-
| In-kind contributions
| 7,000.00
| 7,700.00
| Estimated payments covered by other organizations (travel, lodging)
|-
| Community contributions
| 4,100.00
| 4,510.00
| Newly or previously collected donations
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Non-monetary In-kind Contributions ====

{|
|width="22%"| Space
|width="77%"| To be negotiated
|-
| Time for planning
| North Carolina State University, CONICET, Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis
| Time for participation
| North Carolina State University, Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis
|}

==== Profit, Loss and Risk ====

There is no fee for participation and no profit is expected. Surplus money will go to the general GRASS budget, that is esp. the [https://grasswiki.osgeo.org/wiki/Student_Grants student mini grant program]. Assuming the travel will be reimbursed to participants, the risk of canceled and not taken flights is taken by the potential participants. No or insufficient funding will lead to lower participation as several potential participants expressed a high interest in travel support.

[[Category:Code Sprints]]
[[Category:C Tribe Code Sprint]]
[[Category:Budget]]

GRASS GIS Community Meeting 2024: Budget

2023-12-15T16:29:47Z

Wenzeslaus: /* Expected Budget */

The following information is requested as part of [[Code_Sprint_Guidelines|OSGeo Code Sprint Guidelines]].

== Request for support of the GRASS GIS Community Meeting 2024 ==

=== Basic Information ===

(to be updated)

The GRASS GIS 40th birthday community meeting will take place from June 2 to 6, 2023 in Prague. Further details can be found at [https://grasswiki.osgeo.org/wiki/GRASS_Community_Meeting_Prague_2023 GRASS GIS Community Meeting 2023].

==== Audience ====

Based on previous events, we expect between 10 and 20 people for this meeting. The meeting is open to all users, supporters, contributors, power users and developers who want to make a meaningful contribution to the project. To maximize participation, we are raising money for travel and other expenses. So far, 14 people from four continents expressed interest to participate in-person.

==== Region ====

The event is global. The in-person meeting will take place in Prague, Czechia. The planning team is currently considering what remote participation options would best serve online participants.

==== Project and Focus ====

(to be updated)

We will work on GRASS GIS and integrations with related OSGeo projects. We will revise connection to QGIS to make it easier to maintain, and we will migrate the build to CMake to improve Windows builds including PDAL support. Furthermore, we will move documentation to Markdown to make it easier to contribute to and we will add images and examples for tools and workflows which still miss them. Finally, we will automate and document maintenance processes to reduce the burden on maintainers and thus improve the project sustainability.

==== Length ====

The meeting will last 5 days which include a weekend to support participants who need to join outside of their work (determined by the planning team).

==== Venue ====

(to be updated)

The space for the meeting will be provided by the Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU).

=== Expected Budget ===

==== Costs ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! EUR
! USD
! Explanation
|-
| Participant travel and lodging
| 13,000.00
| 14,300.00
| Average 867 EUR per person estimated from 2023 expenses (15 participants)
|-
| Food, drink, snacks
| 3,000.00
| 3,300.00
| 15 participants, 5 days, 40 EUR per day and person (estimated from 2023 rate)
|-
| Venue small expenses
| 100.00
| 110.00
| 40 EUR Wifi fee, office supplies (estimated from 2023)
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Sponsorship ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! '''EUR'''
! '''USD'''
! Explanation
|-
| OSGeo
| 5,000.00
| 5,500.00
| OSGeo budget for sprints
|-
| In-kind contributions
| 7,000.00
| 7,700.00
| Estimated payments covered by other organizations (travel, lodging)
|-
| Community contributions
| 4,100.00
| 4,510.00
| Newly or previously collected donations
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Non-monetary In-kind Contributions ====

{|
|width="22%"| Space
|width="77%"| To be negotiated
|-
| Time for planning
| North Carolina State University, CONICET, Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis
|}

==== Profit, Loss and Risk ====

There is no fee for participation and no profit is expected. Surplus money will go to the general GRASS budget, that is esp. the [https://grasswiki.osgeo.org/wiki/Student_Grants student mini grant program]. Assuming the travel will be reimbursed to participants, the risk of canceled and not taken flights is taken by the potential participants. No or insufficient funding will lead to lower participation as several potential participants expressed a high interest in travel support.

[[Category:Code Sprints]]
[[Category:C Tribe Code Sprint]]
[[Category:Budget]]

GRASS GIS Community Meeting 2024: Budget

2023-12-15T16:25:04Z

Wenzeslaus: /* In-kind Contributions */

The following information is requested as part of [[Code_Sprint_Guidelines|OSGeo Code Sprint Guidelines]].

== Request for support of the GRASS GIS Community Meeting 2024 ==

=== Basic Information ===

(to be updated)

The GRASS GIS 40th birthday community meeting will take place from June 2 to 6, 2023 in Prague. Further details can be found at [https://grasswiki.osgeo.org/wiki/GRASS_Community_Meeting_Prague_2023 GRASS GIS Community Meeting 2023].

==== Audience ====

Based on previous events, we expect between 10 and 20 people for this meeting. The meeting is open to all users, supporters, contributors, power users and developers who want to make a meaningful contribution to the project. To maximize participation, we are raising money for travel and other expenses. So far, 14 people from four continents expressed interest to participate in-person.

==== Region ====

The event is global. The in-person meeting will take place in Prague, Czechia. The planning team is currently considering what remote participation options would best serve online participants.

==== Project and Focus ====

(to be updated)

We will work on GRASS GIS and integrations with related OSGeo projects. We will revise connection to QGIS to make it easier to maintain, and we will migrate the build to CMake to improve Windows builds including PDAL support. Furthermore, we will move documentation to Markdown to make it easier to contribute to and we will add images and examples for tools and workflows which still miss them. Finally, we will automate and document maintenance processes to reduce the burden on maintainers and thus improve the project sustainability.

==== Length ====

The meeting will last 5 days which include a weekend to support participants who need to join outside of their work (determined by the planning team).

==== Venue ====

(to be updated)

The space for the meeting will be provided by the Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU).

=== Expected Budget ===

(to be updated)

==== Costs ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! EUR
! USD
! Explanation
|-
| Participant travel and lodging
| 13,000.00
| 14,300.00
| Average 867 EUR per person estimated from 2023 expenses (15 participants)
|-
| Food, drink, snacks
| 3,000.00
| 3,300.00
| 15 participants, 5 days, 40 EUR per day and person (estimated from 2023 rate)
|-
| Venue small expenses
| 100.00
| 110.00
| 40 EUR Wifi fee, office supplies (estimated from 2023)
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Sponsorship ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! '''EUR'''
! '''USD'''
! Explanation
|-
| OSGeo
| 5,000.00
| 5,500.00
| OSGeo budget for sprints
|-
| In-kind contributions
| 7,000.00
| 7,700.00
| Estimated payments covered by other organizations (travel, lodging)
|-
| Community contributions
| 4,100.00
| 4,510.00
| Newly or previously collected donations
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Non-monetary In-kind Contributions ====

{|
|width="22%"| Space
|width="77%"| To be negotiated
|-
| Time for planning
| North Carolina State University, CONICET, Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis
|}

==== Profit, Loss and Risk ====

There is no fee for participation and no profit is expected. Surplus money will go to the general GRASS budget, that is esp. the [https://grasswiki.osgeo.org/wiki/Student_Grants student mini grant program]. Assuming the travel will be reimbursed to participants, the risk of canceled and not taken flights is taken by the potential participants. No or insufficient funding will lead to lower participation as several potential participants expressed a high interest in travel support.

[[Category:Code Sprints]]
[[Category:C Tribe Code Sprint]]
[[Category:Budget]]

GRASS GIS Community Meeting 2024: Budget

2023-12-15T16:24:18Z

Wenzeslaus: /* In-kind Contributions */

The following information is requested as part of [[Code_Sprint_Guidelines|OSGeo Code Sprint Guidelines]].

== Request for support of the GRASS GIS Community Meeting 2024 ==

=== Basic Information ===

(to be updated)

The GRASS GIS 40th birthday community meeting will take place from June 2 to 6, 2023 in Prague. Further details can be found at [https://grasswiki.osgeo.org/wiki/GRASS_Community_Meeting_Prague_2023 GRASS GIS Community Meeting 2023].

==== Audience ====

Based on previous events, we expect between 10 and 20 people for this meeting. The meeting is open to all users, supporters, contributors, power users and developers who want to make a meaningful contribution to the project. To maximize participation, we are raising money for travel and other expenses. So far, 14 people from four continents expressed interest to participate in-person.

==== Region ====

The event is global. The in-person meeting will take place in Prague, Czechia. The planning team is currently considering what remote participation options would best serve online participants.

==== Project and Focus ====

(to be updated)

We will work on GRASS GIS and integrations with related OSGeo projects. We will revise connection to QGIS to make it easier to maintain, and we will migrate the build to CMake to improve Windows builds including PDAL support. Furthermore, we will move documentation to Markdown to make it easier to contribute to and we will add images and examples for tools and workflows which still miss them. Finally, we will automate and document maintenance processes to reduce the burden on maintainers and thus improve the project sustainability.

==== Length ====

The meeting will last 5 days which include a weekend to support participants who need to join outside of their work (determined by the planning team).

==== Venue ====

(to be updated)

The space for the meeting will be provided by the Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU).

=== Expected Budget ===

(to be updated)

==== Costs ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! EUR
! USD
! Explanation
|-
| Participant travel and lodging
| 13,000.00
| 14,300.00
| Average 867 EUR per person estimated from 2023 expenses (15 participants)
|-
| Food, drink, snacks
| 3,000.00
| 3,300.00
| 15 participants, 5 days, 40 EUR per day and person (estimated from 2023 rate)
|-
| Venue small expenses
| 100.00
| 110.00
| 40 EUR Wifi fee, office supplies (estimated from 2023)
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Sponsorship ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! '''EUR'''
! '''USD'''
! Explanation
|-
| OSGeo
| 5,000.00
| 5,500.00
| OSGeo budget for sprints
|-
| In-kind contributions
| 7,000.00
| 7,700.00
| Estimated payments covered by other organizations (travel, lodging)
|-
| Community contributions
| 4,100.00
| 4,510.00
| Newly or previously collected donations
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== In-kind Contributions ====

{|
|width="22%"| Space
|width="77%"| To be negotiated
|-
| Time for planning
| North Carolina State University, CONICET, Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis
|}

==== Profit, Loss and Risk ====

There is no fee for participation and no profit is expected. Surplus money will go to the general GRASS budget, that is esp. the [https://grasswiki.osgeo.org/wiki/Student_Grants student mini grant program]. Assuming the travel will be reimbursed to participants, the risk of canceled and not taken flights is taken by the potential participants. No or insufficient funding will lead to lower participation as several potential participants expressed a high interest in travel support.

[[Category:Code Sprints]]
[[Category:C Tribe Code Sprint]]
[[Category:Budget]]

GRASS GIS Community Meeting 2024: Budget

2023-12-15T16:20:26Z

Wenzeslaus: /* Costs */

The following information is requested as part of [[Code_Sprint_Guidelines|OSGeo Code Sprint Guidelines]].

== Request for support of the GRASS GIS Community Meeting 2024 ==

=== Basic Information ===

(to be updated)

The GRASS GIS 40th birthday community meeting will take place from June 2 to 6, 2023 in Prague. Further details can be found at [https://grasswiki.osgeo.org/wiki/GRASS_Community_Meeting_Prague_2023 GRASS GIS Community Meeting 2023].

==== Audience ====

Based on previous events, we expect between 10 and 20 people for this meeting. The meeting is open to all users, supporters, contributors, power users and developers who want to make a meaningful contribution to the project. To maximize participation, we are raising money for travel and other expenses. So far, 14 people from four continents expressed interest to participate in-person.

==== Region ====

The event is global. The in-person meeting will take place in Prague, Czechia. The planning team is currently considering what remote participation options would best serve online participants.

==== Project and Focus ====

(to be updated)

We will work on GRASS GIS and integrations with related OSGeo projects. We will revise connection to QGIS to make it easier to maintain, and we will migrate the build to CMake to improve Windows builds including PDAL support. Furthermore, we will move documentation to Markdown to make it easier to contribute to and we will add images and examples for tools and workflows which still miss them. Finally, we will automate and document maintenance processes to reduce the burden on maintainers and thus improve the project sustainability.

==== Length ====

The meeting will last 5 days which include a weekend to support participants who need to join outside of their work (determined by the planning team).

==== Venue ====

(to be updated)

The space for the meeting will be provided by the Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU).

=== Expected Budget ===

(to be updated)

==== Costs ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! EUR
! USD
! Explanation
|-
| Participant travel and lodging
| 13,000.00
| 14,300.00
| Average 867 EUR per person estimated from 2023 expenses (15 participants)
|-
| Food, drink, snacks
| 3,000.00
| 3,300.00
| 15 participants, 5 days, 40 EUR per day and person (estimated from 2023 rate)
|-
| Venue small expenses
| 100.00
| 110.00
| 40 EUR Wifi fee, office supplies (estimated from 2023)
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== Sponsorship ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! '''EUR'''
! '''USD'''
! Explanation
|-
| OSGeo
| 5,000.00
| 5,500.00
| OSGeo budget for sprints
|-
| In-kind contributions
| 7,000.00
| 7,700.00
| Estimated payments covered by other organizations (travel, lodging)
|-
| Community contributions
| 4,100.00
| 4,510.00
| Newly or previously collected donations
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== In-kind Contributions ====

{|
|width="22%"| Space
|width="77%"| Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU)
|-
| Time (planning and participation)
| Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis, North Carolina State University, CONICET
|}

==== Profit, Loss and Risk ====

There is no fee for participation and no profit is expected. Surplus money will go to the general GRASS budget, that is esp. the [https://grasswiki.osgeo.org/wiki/Student_Grants student mini grant program]. Assuming the travel will be reimbursed to participants, the risk of canceled and not taken flights is taken by the potential participants. No or insufficient funding will lead to lower participation as several potential participants expressed a high interest in travel support.

[[Category:Code Sprints]]
[[Category:C Tribe Code Sprint]]
[[Category:Budget]]

GRASS GIS Community Meeting 2024: Budget

2023-12-15T16:19:05Z

Wenzeslaus: /* Sponsorship */

The following information is requested as part of [[Code_Sprint_Guidelines|OSGeo Code Sprint Guidelines]].

== Request for support of the GRASS GIS Community Meeting 2024 ==

=== Basic Information ===

(to be updated)

The GRASS GIS 40th birthday community meeting will take place from June 2 to 6, 2023 in Prague. Further details can be found at [https://grasswiki.osgeo.org/wiki/GRASS_Community_Meeting_Prague_2023 GRASS GIS Community Meeting 2023].

==== Audience ====

Based on previous events, we expect between 10 and 20 people for this meeting. The meeting is open to all users, supporters, contributors, power users and developers who want to make a meaningful contribution to the project. To maximize participation, we are raising money for travel and other expenses. So far, 14 people from four continents expressed interest to participate in-person.

==== Region ====

The event is global. The in-person meeting will take place in Prague, Czechia. The planning team is currently considering what remote participation options would best serve online participants.

==== Project and Focus ====

(to be updated)

We will work on GRASS GIS and integrations with related OSGeo projects. We will revise connection to QGIS to make it easier to maintain, and we will migrate the build to CMake to improve Windows builds including PDAL support. Furthermore, we will move documentation to Markdown to make it easier to contribute to and we will add images and examples for tools and workflows which still miss them. Finally, we will automate and document maintenance processes to reduce the burden on maintainers and thus improve the project sustainability.

==== Length ====

The meeting will last 5 days which include a weekend to support participants who need to join outside of their work (determined by the planning team).

==== Venue ====

(to be updated)

The space for the meeting will be provided by the Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU).

=== Expected Budget ===

(to be updated)

==== Costs ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! EUR
! USD
! Explanation
|-
| Participant travel and lodging
| 10,780.00
| 11,750.20
| Average 770 EUR per person computed from collected expenses provided by the planning team (5 days, 6 nights), full travel support for the PSC Chair and full support for 13 participants (or partial support for >13 participants).
|-
| Food, drink, snacks
| 2,100.00
| 2,289.00
| 14 participants, 5 days, 30 EUR per day and person.
|-
| Swag
| 400.00
| 436.00
| T-shirts, stickers to take to home communities, or other swag (to be determined by the planning team, 20 EUR per participant, 20 participants)
|-
| Venue small expenses
| 100.00
| 109.00
| 40 EUR Wifi fee, office supplies, cables (as needed)
|-
| '''Total'''
| '''13,380.00'''
| '''14,584.20'''
|
|}

==== Sponsorship ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! '''EUR'''
! '''USD'''
! Explanation
|-
| OSGeo
| 5,000.00
| 5,500.00
| OSGeo budget for sprints
|-
| In-kind contributions
| 7,000.00
| 7,700.00
| Estimated payments covered by other organizations (travel, lodging)
|-
| Community contributions
| 4,100.00
| 4,510.00
| Newly or previously collected donations
|-
| '''Total'''
| '''16,100.00'''
| '''17,710.00'''
|
|}

==== In-kind Contributions ====

{|
|width="22%"| Space
|width="77%"| Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU)
|-
| Time (planning and participation)
| Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis, North Carolina State University, CONICET
|}

==== Profit, Loss and Risk ====

There is no fee for participation and no profit is expected. Surplus money will go to the general GRASS budget, that is esp. the [https://grasswiki.osgeo.org/wiki/Student_Grants student mini grant program]. Assuming the travel will be reimbursed to participants, the risk of canceled and not taken flights is taken by the potential participants. No or insufficient funding will lead to lower participation as several potential participants expressed a high interest in travel support.

[[Category:Code Sprints]]
[[Category:C Tribe Code Sprint]]
[[Category:Budget]]

GRASS GIS Community Meeting 2024: Budget

2023-12-15T16:15:47Z

Wenzeslaus: Created page with "The following information is requested as part of OSGeo Code Sprint Guidelines. == Request for support of the GRASS GIS Community Meeting 2024 ==..."

The following information is requested as part of [[Code_Sprint_Guidelines|OSGeo Code Sprint Guidelines]].

== Request for support of the GRASS GIS Community Meeting 2024 ==

=== Basic Information ===

(to be updated)

The GRASS GIS 40th birthday community meeting will take place from June 2 to 6, 2023 in Prague. Further details can be found at [https://grasswiki.osgeo.org/wiki/GRASS_Community_Meeting_Prague_2023 GRASS GIS Community Meeting 2023].

==== Audience ====

Based on previous events, we expect between 10 and 20 people for this meeting. The meeting is open to all users, supporters, contributors, power users and developers who want to make a meaningful contribution to the project. To maximize participation, we are raising money for travel and other expenses. So far, 14 people from four continents expressed interest to participate in-person.

==== Region ====

The event is global. The in-person meeting will take place in Prague, Czechia. The planning team is currently considering what remote participation options would best serve online participants.

==== Project and Focus ====

(to be updated)

We will work on GRASS GIS and integrations with related OSGeo projects. We will revise connection to QGIS to make it easier to maintain, and we will migrate the build to CMake to improve Windows builds including PDAL support. Furthermore, we will move documentation to Markdown to make it easier to contribute to and we will add images and examples for tools and workflows which still miss them. Finally, we will automate and document maintenance processes to reduce the burden on maintainers and thus improve the project sustainability.

==== Length ====

The meeting will last 5 days which include a weekend to support participants who need to join outside of their work (determined by the planning team).

==== Venue ====

(to be updated)

The space for the meeting will be provided by the Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU).

=== Expected Budget ===

(to be updated)

==== Costs ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! EUR
! USD
! Explanation
|-
| Participant travel and lodging
| 10,780.00
| 11,750.20
| Average 770 EUR per person computed from collected expenses provided by the planning team (5 days, 6 nights), full travel support for the PSC Chair and full support for 13 participants (or partial support for >13 participants).
|-
| Food, drink, snacks
| 2,100.00
| 2,289.00
| 14 participants, 5 days, 30 EUR per day and person.
|-
| Swag
| 400.00
| 436.00
| T-shirts, stickers to take to home communities, or other swag (to be determined by the planning team, 20 EUR per participant, 20 participants)
|-
| Venue small expenses
| 100.00
| 109.00
| 40 EUR Wifi fee, office supplies, cables (as needed)
|-
| '''Total'''
| '''13,380.00'''
| '''14,584.20'''
|
|}

==== Sponsorship ====

{| class="wikitable"
! style="font-weight: bold;" | Item Description
! '''EUR'''
! '''USD'''
! Explanation
|-
| OSGeo
| 6,700.00
| 7,303.00
|
|-
| FOSSGIS e.V.
| 5,000.00
| 5,450.00
|
|-
| Community
| 2,030.00
| 2,212.70
| Previous sprints: 600 EUR 2011, 840 EUR in 2013; Estimated annual budget in OpenCollective: 732 EUR
|-
| Currently available [https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2023 project budget]
| 0.00
| 0.00
| Approximately 1600 EUR is currently available in OpenCollective and PayPal pools. Ideally left as a backup.
|-
| '''Total'''
| '''13,730.00'''
| '''14,965.70'''
|
|}

==== In-kind Contributions ====

{|
|width="22%"| Space
|width="77%"| Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU)
|-
| Time (planning and participation)
| Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU), mundialis, North Carolina State University, CONICET
|}

==== Profit, Loss and Risk ====

There is no fee for participation and no profit is expected. Surplus money will go to the general GRASS budget, that is esp. the [https://grasswiki.osgeo.org/wiki/Student_Grants student mini grant program]. Assuming the travel will be reimbursed to participants, the risk of canceled and not taken flights is taken by the potential participants. No or insufficient funding will lead to lower participation as several potential participants expressed a high interest in travel support.

[[Category:Code Sprints]]
[[Category:C Tribe Code Sprint]]
[[Category:Budget]]

GRASS GIS Budget 2024

2023-12-14T17:29:36Z

Wenzeslaus: Created page with "The GRASS GIS project asks for a total budget of '''4800 USD''' from OSGeo to cover the following expenses: * 2 (our of 4) micro grants for students (see our [https://grasswi..."

The GRASS GIS project asks for a total budget of '''4800 USD''' from OSGeo to cover the following expenses:

* 2 (our of 4) micro grants for students (see our [https://grasswiki.osgeo.org/wiki/Student_Grants Student grant] program)
* Travel to OSGeo sprint and PSC representation at OSGeo AGM
* Marketing efforts

Other expenses will be covered from additional funding sources such as in-kind contributions and donations at [https://opencollective.com/osgeo/projects/grass Open Collective].

The full budget for GRASS GIS is found at: https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2024

[[Category:Budget]]

OSGeo Community Sprint 2023

2023-09-01T15:25:06Z

Wenzeslaus: /* Project Plans */ add GRASS GIS

Annual Code Sprint comes to Vienna (Austria) in 2023!

Powered by [[Image:Osgeo-logo.png|250px|link=https://www.osgeo.org]]

== Purpose ==

Bring together project members to make decisions and tackle larger geospatial
problems as in previous years:
* [[OSGeo_Virtual_Community_Sprint_2020|Virtual Event]] (2020)
* [[OSGeo_Community_Sprint_2019|Minnesota]] (2019)
* [[OSGeo Code Sprint 2018|Bonn]] (2018)
* [[Daytona Beach Code Sprint 2017|Daytona_Beach]] (2017)
* [[Paris Code Sprint 2016|Paris]] (2016)
* [[Philadelphia Code Sprint 2015|Philadelphia]] (2015)
* [[Vienna Code Sprint 2014|Vienna]] (2014)
* [[Boston Code Sprint 2013|Boston]] (2013)
* [[IslandWood Code Sprint 2012|Island Wood (Seattle)]] (2012)
* [[Montreal Code Sprint 2011|Montreal]] (2011)
* [[New York Code Sprint 2010|New York City]] (2010)
* [[Toronto Code Sprint 2009|Toronto]] (2009)

== Sponsors ==

'''Sponsoring ''' Find out about [[OSGeo_Community_Sprint_2023#Sponsoring |Sponsoring the Event]].

; <big>Venue Sponsor</big>
{| border=0 cellspacing=15 cellpadding=10
||
[[File:BIDS23.jpg|340px|Big Data from Space 2023 (BiDS)|link=https://www.bigdatafromspace2023.org/]]
 
https://www.bigdatafromspace2023.org/
|}

; <big>Gold Sponsors</big>
{| border=0 cellspacing=15 cellpadding=10
||
[[File:GC-Group logo.png|220px|GeoCue|link=http://www.geocue.com/]]
 
http://www.geocue.com/
||
[[File:safe-software-logo.png|220px|Safe Software|link=https://www.safe.com/]]
 
https://www.safe.com/
||
[[File:RIEGL.png|310px|RIEGL|link=http://www.riegl.com/]]
 
http://www.riegl.com/
|}

; <big>Silver Sponsors</big>
{| border=0 cellspacing=15 cellpadding=10
||
[[File:Hobulogo.png|160px|Hobu|link=https://hobu.co/]]
 
https://hobu.co/
||
[[File:Bh-logo.jpg|300px|link=https://www.bhinc.com/]]
 
[https://www.bhinc.com/ https://www.bhinc.com/]
||
[[File:Crunchydata.png|160px|CrunchyData||link=http://www.crunchydata.com/]]
 
[http://www.crunchydata.com/ http://www.crunchydata.com/]
|}
{| border=0 cellspacing=15 cellpadding=10
||
[[File:Gaia3D.png|240px|Gaia3D||link=https://gaia3d.com/en/]]
 
[https://gaia3d.com/en/ https://gaia3d.com/en/]
|}

; <big>Bronze Sponsors</big>
{| border=0 cellspacing=15 cellpadding=10
||
[[File:CoordinateSolutions_TRANS.png|210px|link=http://www.coordinatesolutions.com/]]
 
[http://www.coordinatesolutions.com/ http://www.coordinatesolutions.com/]
||
[[File:Logo-EOX.png|140px|EOX IT Services GmbH|link=http://eox.at]]
 
[http://eox.at http://eox.at]
||
[[File:Pixel8_logo_full.png|140px|link=https://www.pixel8.earth/]]
 
[https://www.pixel8.earth/ https://www.pixel8.earth/]
|}
{| border=0 cellspacing=15 cellpadding=10
||
[[File:Azavea-logo.png|160px|link=https://www.azavea.com/]]
 
[https://www.azavea.com/ https://www.azavea.com/]
||
[[File:Greenwood_logo.png|210px|link=https://greenwoodmap.com/]]
 
[https://greenwoodmap.com/ https://greenwoodmap.com/]
|}

== Dates and Times ==

* Date: November 6 to November 9
* Time: 9:00am to 1:30pm each day

== Other Events in Q4 2023 ==

* ''please add your event''

== Location ==

* [https://en.wikipedia.org/wiki/Vienna Vienna], Austria

=== BIDS23 ===
The OSGeo Community Sprint 2023 will be hosted by the Big Data from Space 2023 (BiDS) event.

BiDS brings together key actors from industry, academia, EU entities and government to reveal user needs, exchange ideas and showcase latest technical solutions and applications touching all aspects of space and big data technologies, providing a unique opportunity to discuss and present the most recent innovations and challenges encountered in the context of big data from space. The 2023 edition of BiDS will focus not only technologies enabling insight and foresight inferable from big data from space. Together, we want to emphasize how breakthrough space data driven technologies impact on society’s grand challenges, such as climate change and the green transition.

The event, organized by the [https://www.esa.int/ European Space Agency] (ESA) together with the [https://www.satcen.europa.eu/ European Union Satellite Center] (SatCen) and the [https://commission.europa.eu/about-european-commission/departments-and-executive-agencies/joint-research-centre_en Joint Research Center] (JRC), will take place at the [https://www.acv.at/en/ Austria Center Vienna], and counts with the support of the partners [https://www.ffg.at/en FFG], [https://austria-in-space.at/en/ Austria in Space] and the [https://www.bmk.gv.at/en.html Federal Ministry Republic of Austria].

=== Coding Venue ===
* The Austria Center Vienna will be the host of BIDS '23.
* As Austria's largest conference center, it opened in 1987 and has 19 halls, 180 meeting rooms, and 26,000 square meters of exhibition and networking space with a capacity of up to 22,800 guests.
* It is a popular destination in the international conference circuit and is located next to a UN headquarters, making it a unique location for the latest edition of Big Data from Space.
* [https://www.acv.at/en/ Austria Center Vienna], Bruno-Kreisky-Platz 1, 1220 Wien, Austria
* [https://www.openstreetmap.org/#map=16/48.2343/16.4144 OpenStreetMap]

=== Parking ===
* Austria Center Vienna provides parking space

=== Accommodation ===
Several hotels and apartments are close to the venue. You will be able to find lots of options within walking distance.
Here are a few options:

{|border=1
|-
| '''Hotel Name''' || '''Price Range (Euros)''' || '''Distance''' || '''Notes'''
|-
|}

=== How to get there ===

'''Travelling to/from Vienna international airport'''

==== Metro ====

==== Suburban Rail ====

==== Bus Services ====

==== Taxi ====

== Project Plans ==
(i.e what do you wish/want/plan to work on during the sprint ?)

* '''OSGeoLive''':
** Work towards 16.0 release

* '''Pangeo community''':
** [https://github.com/pangeo-data/bids2023_codesprint Pangeo project ideas], incl. Alexander Kmoch & DGGS

* '''STAC BoF / European Community Show of Hands''':
** We (EOX) would like to better get to know the European scene of STAC users and contributors. For this reason we'd like to organize a Birds of a Feather session, where we talk about the use and development of STAC specification, tools and resources. If there is a reasonable interest, we could expand this to a session actually dedicated towards actual work on STAC related items.

* '''GRASS GIS''':
** Review lidar binning code for large point clouds (''r.in.pdal'' tool)

== Participants ==

Please add your name and the projects you are planning to sprint and note the likeliness of your attendance.

{| border="1" cellpadding="2" class="wikitable sortable"
!width="25"|No
!width="250"|Name
!width="100"|Country
!width="250"|Email
!width="250"|Organisation
!width="250"|Projects
!width="25"|Mon
!width="25"|Tue
!width="25"|Wed
!width="25"|Thu
!width="60"|Accommodation
!width="60"|Likelihood
!width="30"|Food Restrictions
!width="60"|social event
|-
| 1 ||[[User:kalxas|Angelos Tzotsos]] || GR || tzotsos(at)osgeo.org || OSGeo || pycsw, OSGeoLive, GeoNode, UbuntuGIS, pygeoapi, OTB || x || x || x || x || || Certain || No || x ||
|-
| 2 ||[[User:Tomkralidis|Tom Kralidis]] || CA || tomkralidis(at)gmail.com || OSGeo || pycsw, OWSLib, pygeoapi, GeoHealthCheck, MapServer, other geopython projects || x || x || x || x || booked || Certain || No || x ||
|-
| 3 ||[[User:msmitherdc|Michael Smith]] || US || michael.smith.erdc(at)gmail.com || OSGeo || pdal, mapserver, other geopython projects || x || x || x || x || || Certain || No || x ||
|-
| 4 ||[[User:Schpidi|Stephan Meißl]] || AT || stephan.meissl(at)eox.at || EOX || MapServer, View Server/EOxServer, various || x || x || x || x || local || Certain || No || x ||
|-
| 5 ||[[User:Allixender|Alexander Kmoch]] || EE || alexander.kmoch(at)ut.ee || Univ. Tartu, Pangeo || DGGS, DGGRID, pygeoapi, xarray, various || x || x || x || x || || Certain || No || x ||
|-
| 6 ||[[User:hobu|Howard Butler]] || US || howard(at)hobu.co || Hobu, Inc. || PDAL, GDAL, point clouds || x || x || x || x || || Certain || No || x ||
|-
| 7 ||[[User:darkblueb|Brian M Hamlin]] || US || maplabs(at)light42.com || CalOpenData || OSGeoLive, Open Data Cube || x || x || x || x || || Certain || Vegetarian || x ||
|-
| 8 ||[[User:mbernasocchi|Marco Bernasocchi]] || CH || marco@opengis.ch || OSGeo, QGIS.org || QGIS || x || x || x || x || || Certain || NOne || x ||
|-
| 9 ||[[User:Sethg|Seth Girvin]] || FR || sethg@geographika.net || OSGeo || MapServer, OSGeoLive, GeoStyler, mappyfile|| x || x || x || x || booked || Certain || None || x ||
|-
| 10 ||[[User:Pirmin_Kalberer|Pirmin Kalberer]] || CH || pka (at) sourcepole.com || Sourcepole || OGC APIs, BBOX, GeoRust, various|| x || x || x || - || || Very likely || None || x ||
|-
| 11 ||[[User:Anita_Graser|Anita Graser]] || AT || anita@qgis.orgm || AIT || QGIS, MobilityDB, MovingPandas || x || x || x || x || local || Certain || None || x ||
|-
| 12 ||[[User:chambbj|Brad Chambers]] || US || brad.chambers(at)gmail.com || Grover Consulting Services || PDAL, point clouds || x || x || x || x || || Certain || No || x ||
|-
| 13 ||[[User:jef|Jürgen Fischer]] || DE || jef(at)norbit.de || norBIT GmbH || QGIS, OSGeo4W || x || x || x || x || tbd || Likely || None || x ||
|-
| 14 ||[[User:Fschindler|Fabian Schindler]] || AT || fabian.schindler(at)eox.at || EOX || MapServer, View Server/EOxServer || x || x || x || x || local || Certain || Vegetarian || x ||
|-
| 15 ||[[User:Djay|Gérald Fenoy]] || FR || gerald.fenoy(at)Geolabs.fr || GeoLabs || ZOO-Project, MapServer || x || x || - || - || local || Very likely || None || x ||
|-
| 16 ||[[User:Fschindler|Léa Vauchier]] || FR || lea.vauchier(at)ign.fr|| IGN || pdal, point clouds || x || x || x || x || tbd || Very Likely || Vegetarian || x ||
|-
| 17 ||[[User:Fschindler|Antoine Lavenant]] || FR || antoine.lavenant(at)ign.fr|| IGN || pdal, point clouds || x || x || x || x || tbd || Very Likely || No || x ||
|}

Remote: Vaclav (Vashek) Petras (US, wenzeslaus gmail com, NC State University, GRASS GIS, asynchronous, 6 hours behind)

== Communication ==

* Please join the mailing list: https://lists.osgeo.org/mailman/listinfo/tosprint
* IRC chat during the event: #tosprint Server: irc.freenode.net
* Gitter channel: https://gitter.im/OSGeo/Sprint

== Costs ==

Participants should plan for the following costs:

* Travel to Vienna
* Accommodation for x nights

== Individual preparation ==

* Bring your own laptop
* Bring [https://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] if needed. See also http://www.power-plugs-sockets.com/
* Install Git and compiler tools, and come with a working development environment

== Sponsoring ==

The Open Source Geospatial Foundation (OSGeo) has a long tradition of organizing code sprints for developers of Open Source GIS software.
(https://wiki.osgeo.org/wiki/Category:Code_Sprints).

An international community/code sprint for OSGeo will take place Nov 6-9, 2023.

We expect about 80 developers from all over the world to come from various [https://www.osgeo.org/, OSGeo] projects. Whether desktop application, geospatial library, metadata catalog or web mapping: be sure to find products in the list that you use. The sprint is also an opportunity for your developers to meet with the core developers of the projects, get a deeper insight into the software and participate in the development.

This years' sprint will take place in Vienna and will be hosted by [https://www.bigdatafromspace2023.org/, Big Data From Space '23] and organized by members of the local OSGeo chapter.

In addition to the costs of providing the technical infrastructure and space, food and drink for the developers represents the main cost. Morning/afternoon meals and drinks during the day are planned. In addition, we hope to provide several evening meals and social events.

In order to cover these costs we would be overjoyed to accept offers of sponsorship!

What we can offer:
* Your logo on top of the [https://www.osgeo.org/events/OSGeo_Community_Sprint_2023/ community sprint website] as well as on all official documents used during the sprint
* Acknowledgement in all sprint related emails
* Our undying gratitude, which comes in handy when you least expect it (remember that feature you wanted?)

Our sponsorship levels:
* Gold: >= 2500 USD
* Silver: 1500 USD
* Bronze: 750 USD

So...
* get your company talking to the top project developers.
* encourage your GIS developers to take advantage of this opportunity, there is no better opportunity to learn!
* support the software you use - you benefit immediately.

Thank you very much!

Contact: To sponsor, please contact tzotsos@osgeo.org directly.

== Event Owner ==
* [[User:kalxas|Angelos Tzotsos]]

== Press Release ==

We are looking forward to the next OSGeo Code Sprint!

[[Category:Code_Sprints]]
[[Category:C Tribe Code Sprint]]

OSGeo Community Sprint 2023

2023-08-07T17:02:45Z

Wenzeslaus: /* Participants */ Add myself as a remote participant

Annual Code Sprint comes to Vienna (Austria) in 2023!

Powered by [[Image:Osgeo-logo.png|250px|link=https://www.osgeo.org]]

== Purpose ==

Bring together project members to make decisions and tackle larger geospatial
problems as in previous years:
* [[OSGeo_Virtual_Community_Sprint_2020|Virtual Event]] (2020)
* [[OSGeo_Community_Sprint_2019|Minnesota]] (2019)
* [[OSGeo Code Sprint 2018|Bonn]] (2018)
* [[Daytona Beach Code Sprint 2017|Daytona_Beach]] (2017)
* [[Paris Code Sprint 2016|Paris]] (2016)
* [[Philadelphia Code Sprint 2015|Philadelphia]] (2015)
* [[Vienna Code Sprint 2014|Vienna]] (2014)
* [[Boston Code Sprint 2013|Boston]] (2013)
* [[IslandWood Code Sprint 2012|Island Wood (Seattle)]] (2012)
* [[Montreal Code Sprint 2011|Montreal]] (2011)
* [[New York Code Sprint 2010|New York City]] (2010)
* [[Toronto Code Sprint 2009|Toronto]] (2009)

== Sponsors ==

'''Sponsoring ''' Find out about [[OSGeo_Community_Sprint_2023#Sponsoring |Sponsoring the Event]].

; <big>Venue Sponsor</big>
{| border=0 cellspacing=15 cellpadding=10
||
[[File:BIDS23.jpg|340px|Big Data from Space 2023 (BiDS)|link=https://www.bigdatafromspace2023.org/]]
 
https://www.bigdatafromspace2023.org/
|}

; <big>Gold Sponsors</big>
{| border=0 cellspacing=15 cellpadding=10
||
[[File:GC-Group logo.png|220px|GeoCue|link=http://www.geocue.com/]]
 
http://www.geocue.com/
||
[[File:safe-software-logo.png|220px|Safe Software|link=https://www.safe.com/]]
 
https://www.safe.com/
||
[[File:RIEGL.png|310px|RIEGL|link=http://www.riegl.com/]]
 
http://www.riegl.com/
|}

; <big>Silver Sponsors</big>
{| border=0 cellspacing=15 cellpadding=10
||
[[File:Hobulogo.png|160px|Hobu|link=https://hobu.co/]]
 
https://hobu.co/
||
[[File:Bh-logo.jpg|300px|link=https://www.bhinc.com/]]
 
[https://www.bhinc.com/ https://www.bhinc.com/]
||
[[File:Crunchydata.png|160px|CrunchyData||link=http://www.crunchydata.com/]]
 
[http://www.crunchydata.com/ http://www.crunchydata.com/]
|}
{| border=0 cellspacing=15 cellpadding=10
||
[[File:Gaia3D.png|240px|Gaia3D||link=https://gaia3d.com/en/]]
 
[https://gaia3d.com/en/ https://gaia3d.com/en/]
|}

; <big>Bronze Sponsors</big>
{| border=0 cellspacing=15 cellpadding=10
||
[[File:CoordinateSolutions_TRANS.png|210px|link=http://www.coordinatesolutions.com/]]
 
[http://www.coordinatesolutions.com/ http://www.coordinatesolutions.com/]
||
[[File:Logo-EOX.png|140px|EOX IT Services GmbH|link=http://eox.at]]
 
[http://eox.at http://eox.at]
||
[[File:Pixel8_logo_full.png|140px|link=https://www.pixel8.earth/]]
 
[https://www.pixel8.earth/ https://www.pixel8.earth/]
|}
{| border=0 cellspacing=15 cellpadding=10
||
[[File:Azavea-logo.png|160px|link=https://www.azavea.com/]]
 
[https://www.azavea.com/ https://www.azavea.com/]
||
[[File:Greenwood_logo.png|210px|link=https://greenwoodmap.com/]]
 
[https://greenwoodmap.com/ https://greenwoodmap.com/]
|}

== Dates and Times ==

* Date: November 6 to November 9
* Time: 9:00am to 1:30pm each day

== Other Events in Q4 2023 ==

* ''please add your event''

== Location ==

* [https://en.wikipedia.org/wiki/Vienna Vienna], Austria

=== BIDS23 ===
The OSGeo Community Sprint 2023 will be hosted by the Big Data from Space 2023 (BiDS) event.

BiDS brings together key actors from industry, academia, EU entities and government to reveal user needs, exchange ideas and showcase latest technical solutions and applications touching all aspects of space and big data technologies, providing a unique opportunity to discuss and present the most recent innovations and challenges encountered in the context of big data from space. The 2023 edition of BiDS will focus not only technologies enabling insight and foresight inferable from big data from space. Together, we want to emphasize how breakthrough space data driven technologies impact on society’s grand challenges, such as climate change and the green transition.

The event, organized by the [https://www.esa.int/ European Space Agency] (ESA) together with the [https://www.satcen.europa.eu/ European Union Satellite Center] (SatCen) and the [https://commission.europa.eu/about-european-commission/departments-and-executive-agencies/joint-research-centre_en Joint Research Center] (JRC), will take place at the [https://www.acv.at/en/ Austria Center Vienna], and counts with the support of the partners [https://www.ffg.at/en FFG], [https://austria-in-space.at/en/ Austria in Space] and the [https://www.bmk.gv.at/en.html Federal Ministry Republic of Austria].

=== Coding Venue ===
* The Austria Center Vienna will be the host of BIDS '23.
* As Austria's largest conference center, it opened in 1987 and has 19 halls, 180 meeting rooms, and 26,000 square meters of exhibition and networking space with a capacity of up to 22,800 guests.
* It is a popular destination in the international conference circuit and is located next to a UN headquarters, making it a unique location for the latest edition of Big Data from Space.
* [https://www.acv.at/en/ Austria Center Vienna], Bruno-Kreisky-Platz 1, 1220 Wien, Austria
* [https://www.openstreetmap.org/#map=16/48.2343/16.4144 OpenStreetMap]

=== Parking ===
* Austria Center Vienna provides parking space

=== Accommodation ===
Several hotels and apartments are close to the venue. You will be able to find lots of options within walking distance.
Here are a few options:

{|border=1
|-
| '''Hotel Name''' || '''Price Range (Euros)''' || '''Distance''' || '''Notes'''
|-
|}

=== How to get there ===

'''Travelling to/from Vienna international airport'''

==== Metro ====

==== Suburban Rail ====

==== Bus Services ====

==== Taxi ====

== Project Plans ==
(i.e what do you wish/want/plan to work on during the sprint ?)

* '''OSGeoLive''':
** Work towards 16.0 release

* '''Pangeo community''':
** [https://github.com/pangeo-data/bids2023_codesprint Pangeo project ideas], incl. Alexander Kmoch & DGGS

== Participants ==

Please add your name and the projects you are planning to sprint and note the likeliness of your attendance.

{| border="1" cellpadding="2" class="wikitable sortable"
!width="25"|No
!width="250"|Name
!width="100"|Country
!width="250"|Email
!width="250"|Organisation
!width="250"|Projects
!width="25"|Mon
!width="25"|Tue
!width="25"|Wed
!width="25"|Thu
!width="60"|Accommodation
!width="60"|Likelihood
!width="30"|Food Restrictions
!width="60"|social event
|-
| 1 ||[[User:kalxas|Angelos Tzotsos]] || GR || tzotsos(at)osgeo.org || OSGeo || pycsw, OSGeoLive, GeoNode, UbuntuGIS, pygeoapi, OTB || x || x || x || x || booked || Organizer :) || No || x ||
|-
| 2 ||[[User:Tomkralidis|Tom Kralidis]] || CA || tomkralidis(at)gmail.com || OSGeo || pycsw, OWSLib, pygeoapi, GeoHealthCheck, MapServer, other geopython projects || x || x || x || x || booked || Certain || No || x ||
|-
| 3 ||[[User:msmitherdc|Michael Smith]] || US || michael.smith.erdc(at)gmail.com || OSGeo || pdal, mapserver, other geopython projects || x || x || x || x || || Certain || No || x ||
|-
| 4 ||[[User:Schpidi|Stephan Meißl]] || AT || stephan.meissl(at)eox.at || EOX || MapServer, View Server/EOxServer, various || x || x || x || x || local || Certain || No || x ||
|-
| 5 ||[[User:Allixender|Alexander Kmoch]] || EE || alexander.kmoch(at)ut.ee || Univ. Tartu, Pangeo || DGGS, DGGRID, pygeoapi, xarray, various || x || x || x || x || || Certain || No || x ||
|-
| 6 ||[[User:hobu|Howard Butler]] || US || howard(at)hobu.co || Hobu, Inc. || PDAL, GDAL, point clouds || x || x || x || x || || Certain || No || x ||
|-
| 7 ||[[User:darkblueb|Brian M Hamlin]] || US || maplabs(at)light42.com || CalOpenData || OSGeoLive, Open Data Cube || x || x || x || x || || Certain || Vegetarian || x ||
|-
| 8 ||[[User:mbernasocchi|Marco Bernasocchi]] || CH || marco@opengis.ch || OSGeo, QGIS.org || QGIS || x || x || x || x || || Certain || NOne || x ||
|-
| 9 ||[[User:Sethg|Seth Girvin]] || FR || sethg@geographika.net || OSGeo || MapServer, OSGeoLive, GeoStyler, mappyfile|| x || x || x || x || booked || Certain || None || x ||
|}

Remote: Vaclav (Vashek) Petras (US, wenzeslaus gmail com, NC State University, GRASS GIS, asynchronous, 6 hours behind)

== Communication ==

* Please join the mailing list: https://lists.osgeo.org/mailman/listinfo/tosprint
* IRC chat during the event: #tosprint Server: irc.freenode.net
* Gitter channel: https://gitter.im/OSGeo/Sprint

== Costs ==

Participants should plan for the following costs:

* Travel to Vienna
* Accommodation for x nights

== Individual preparation ==

* Bring your own laptop
* Bring [https://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] if needed. See also http://www.power-plugs-sockets.com/
* Install Git and compiler tools, and come with a working development environment

== Sponsoring ==

The Open Source Geospatial Foundation (OSGeo) has a long tradition of organizing code sprints for developers of Open Source GIS software.
(https://wiki.osgeo.org/wiki/Category:Code_Sprints).

An international community/code sprint for OSGeo will take place Nov 6-9, 2023.

We expect about 80 developers from all over the world to come from various [https://www.osgeo.org/, OSGeo] projects. Whether desktop application, geospatial library, metadata catalog or web mapping: be sure to find products in the list that you use. The sprint is also an opportunity for your developers to meet with the core developers of the projects, get a deeper insight into the software and participate in the development.

This years' sprint will take place in Vienna and will be hosted by [https://www.bigdatafromspace2023.org/, Big Data From Space '23] and organized by members of the local OSGeo chapter.

In addition to the costs of providing the technical infrastructure and space, food and drink for the developers represents the main cost. Morning/afternoon meals and drinks during the day are planned. In addition, we hope to provide several evening meals and social events.

In order to cover these costs we would be overjoyed to accept offers of sponsorship!

What we can offer:
* Your logo on top of the [https://www.osgeo.org/events/OSGeo_Community_Sprint_2023/ community sprint website] as well as on all official documents used during the sprint
* Acknowledgement in all sprint related emails
* Our undying gratitude, which comes in handy when you least expect it (remember that feature you wanted?)

Our sponsorship levels:
* Gold: >= 2500 USD
* Silver: 1500 USD
* Bronze: 750 USD

So...
* get your company talking to the top project developers.
* encourage your GIS developers to take advantage of this opportunity, there is no better opportunity to learn!
* support the software you use - you benefit immediately.

Thank you very much!

Contact: To sponsor, please contact tzotsos@osgeo.org directly.

== Event Owner ==
* [[User:kalxas|Angelos Tzotsos]]

== Press Release ==

We are looking forward to the next OSGeo Code Sprint!

[[Category:Code_Sprints]]
[[Category:C Tribe Code Sprint]]

FOSS4G 2022/BirdsOfAFeather

2022-08-13T19:48:17Z

Wenzeslaus: Add GRASS GIS BoF

= Introduction =

Birds of a Feather (BoF) sessions are unstructured timeslots where people can self-organise themselves to discuss topics of interest.

== General Information ==

At the [[FOSS4G 2022]] conference in Firenze, a number of spaces have been reserved for people to flock together in Birds of a Feather sessions.

For reference, an overview of the FOSS4G [https://2022.foss4g.org/program-outline.php schedule is available at here].

=== How to organize a BOF ===

BoF sessions are informal gatherings of people around a specific topic. BoF's can be held in: BoF rooms or taken off-site for breakfast, lunch or dinner!

The FOSS4G conference provides the spaces, but the setup of the bird-of-feather meetup is done informally using this wiki.

=== Capacities ===

The BoF sessions rooms used are the ones in which the conference takes place, right after the last presentation:

* Room Verde
* Room Limonaia
* Room Onice
* Room 4
* Room 6
* Room 9
* Room 12 (available all the times, no video projector)
* Room Modulo 3A
* Room Hall 3A
* Room Hall 3B (available all the times, no video projector)

We will also put a BoF organizing board on site for better organization.

= Thursday 25 August (8:00 - 9:00) =

== TODO: Room name ==

=== TODO: BoF title ===

* Description: TODO
* Person to contact: TODO

Who is coming:
* TODO

== Onice Room ==

=== Italian Remote sensing workshops program ===
* Description:
* Person to contact: Alessandro Frigeri, Paolo Dabove

Who is coming
* Alessandro Frigeri
* Paolo Dabove
* Luca Delucchi (maybe)

= Thursday 25 August (18:15 - 19:15) =

== Room 9 ==

=== Charter members F2F ===

* Description: Get to know each other and talk about our duties.
* Person to contact: Vicky Vergara

Who is coming:
* Vicky Vergara
* Zoltan Siki
* Luca Delucchi (maybe)

== Room Verde ==

=== GRASS GIS ===

* Description: Talk about priorities and use cases
* Person to contact: [[User:Wenzeslaus|Vaclav (Vashek) Petras (User:Wenzeslaus)]]
* The same room as the ''State of GRASS GIS talk'' in the morning.

Who is coming:
* Vaclav (Vashek) Petras
* Anna Petrasova

== TODO: Room name ==

=== TODO: BoF title ===

* Description: TODO
* Person to contact: TODO

Who is coming:
* TODO

= Friday 26 August (8:00 - 9:00) =

== TODO: Room name ==

=== TODO: BoF title ===

* Description: TODO
* Person to contact: TODO

Who is coming:
* TODO

[[Category:FOSS4G2022]]

FOSS4G 2022/Community sprint

2022-08-13T19:45:23Z

Wenzeslaus: /* Participation at an hour with the developer */ Link my user page

== Code Sprint ==

Also this year, after the online conference, there will be the '''OSGeo community sprint'''.

Participation is free of charge and anyone involved or interested in getting involved in OSGeo community projects is welcome.

This year we will try to offer the format '''an hour with the developer''', where we ask seasoned community members to donate time for welcoming new members and introduce them to different projects or guide them through the setup of the development environment or translation tools and get started on the Foss4G journey.

You can choose to contribute to one or more projects. The sky is the limit. There’s always plenty to do – and it’s not all about programming. Translation, documentation, feedback, discussions, and testing are very important for projects! Conference registration is not a prerequisite for participation in the code sprint.

=== When ===

The code sprint will be held on 27-28 of August.

=== Where ===

The codesprint will be hosted at the University of Florence.

More information about the rooms and social channels for the codesprint will be notified later.

== Registered Attendees ==

The code sprint is free of charge but we kindly ask you to write down your name for better planning.

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|No
!width="250"|Name
!width="250"|Email
!width="250"|Projects
!width="250"|Registered to FOSS4G conference
!width="250"|Present on Sat 27th
!width="250"|Present on Sun 28th
|-
|1 || Andrea Antonello || andrea.antonello at gmail || Codesprint Org, [https://www.geopaparazzi.org/smash/index.html SMASH], [https://integratedmodelling.org/getting-started/ k.LAB] || x || x || x
|-
|2 || Jody Garnett || jody.garnett at gmail.com || geotools.org, geoserver.org || x || ||
|-
|3 || Vicky Vergara || vicky at georepublic.de || pgRoutig, OSGeoLive, OSGeo Website || x || || x
|-
|4 || Markus Neteler || neteler at osgeo.org || GRASS GIS, actinia, GRASS Website || x || ||
|-
|5 || Howard Butler || howard at hobu.co || PDAL, GDAL, and PROJ || x || ||
|-
|6 || Akin Kuye || t_kuye@yahoo.com || Codesprint Org, SMASH || x || ||
|-
|7 || Emmanuel Dubois || emmanuel.dubois@cnes.fr || OTB and 3D CNES tools: CARS, pandora, demcompare || x || ||
|-
|8 || Anna Petrasova || wenzeslaus gmail com || GRASS GIS || x || x || x
|-
|9 || Vaclav Petras || kratochanna gmail com || GRASS GIS || x || x || x
|-
|10 || Tom Kralidis || tomkralidis gmail com || Geopython (pygeoapi, pycsw, pygeometa, OWSLib, etc.) || x || || x
|-
|11 || Veronica Andreo || veroandreo gmail com || GRASS GIS || x || x ||
|-
|12 || [user:astrid_emde|Astrid Emde] || astrid dot emde at wheregroup dot com || Mapbender / OSGeoLive || x || x || -
|-
|13 || Silvia Franceschi || silvia.franceschi at gmail || Codesprint Org, [https://www.geopaparazzi.org/smash/index.html SMASH], [https://integratedmodelling.org/getting-started/ k.LAB] || x || x || x
|-
|14 || Luca Delucchi || lucadeluge gmail com || GRASS GIS, OSGeoLive || x || x || x
|-
|15 || Laura Mugeha || mugeha dot okole at gmail dot com || OSGeoLive || x || x || x
|-
|16 || Caitlin Haedrich || caitlin dot haedrich gmail com || GRASS GIS || x || x || x
|-
|17 || Linda Kladivova || lindakladivova gmail com || GRASS GIS || x || x ||
|-
|18 || Torsten Friebe || friebe AT lat-lon DOT de || deegree || x || x || x
|-
|19 || Luigi Ponti || quartese at gmail.com || GRASS GIS || || x || ?
|-
|20 || Carmen Tawalika || tawalika at mundialis dot de || actinia || x || x || ?
|-
|21 || my name || my email || projects I will work on || x || x || x
|}

== Workgroups ==

=== Project-name ===

To participate, copy this project skeleton and start a section below (alphabetically) for your project.

==== Attending ====

*user
*user

==== Goals ====

*your goals

==== Participation at '''an hour with the developer''' ====

* name of the developer - time/day of availability

=== GeoServer ===

Working on GeoServer community goals, Java 17 LTS proposed.

==== Attending ====

* jody.garentt

==== Goals ====

* Java 17 LTS (proposed)

==== Participation at '''an hour with the developer''' ====

* Jody Garnett, standing offer to help new developers checkout and build GeoServer during sprint

=== GRASS GIS ===

[[Image:Grasslogo_vector_small.png|right]]

==== Attending ====

* Markus Neteler
* Anna Petrasova
* Vaclav Petras
* Veronica Andreo
* Luca Delucchi

==== Goals ====

* Help starting contributors.
* Python and command line usability issues.
* Discuss hard-to-finish PRs.
* Sync with the PDAL project.

==== Participation at '''an hour with the developer''' ====

* Vaclav (Vashek) Petras - times: find me, ask me ([[User:Wenzeslaus]])

=== SMASH ===

Working on SMASH digital field mapping app enhancements.

==== Attending ====

* Andrea Antonello
* Silvia Franceschi
* Akin Kuye

==== Goals ====

* bugfixing
* server-app enhancements

==== Participation at '''an hour with the developer''' ====

* Andrea Antonello - time to be defined, based on organization issues

=== pgRouting ===

* Working on tasks for becoming an OSGeo project
* Release of v3.3.2

==== Attending ====

* vicky Vergara

==== Goals ====

* Work on tasks to become an OSGeo project

==== Participation at '''an hour with the developer''' ====

* Vicky Vergara - Sunday all day

=== deegree ===

Working on [https://github.com/deegree/deegree3/issues open issues] for deegree 3.5.

==== Attending ====

* Torsten Friebe [[User:Tfr42]]

==== Goals ====

* improvements for 3.4 and 3.5

==== Participation at '''an hour with the developer''' ====

* Torsten Friebe - Saturday, time to be defined, find & ask me or join the IRC channel [https://web.libera.chat/#deegree #deegree] and get in contact.

=== pygeoapi ===

The pygeoapi team will be working on the [issue backlog](https://github.com/geopython/pygeoapi/issues).

==== Attending ====

* Tom Kralidis (day 2 [Sunday])

==== Goals ====

* 0.13 release

==== Participation at '''an hour with the developer''' ====

* Tom Kralidis, standing offer to help new developers with pygeoapi (please contact me to setup time)

[[Category:FOSS4G2022]] [[Category:FOSS4G]] [[Category:Code_Sprints]]

User:Wenzeslaus

2022-08-13T19:41:20Z

Wenzeslaus:

{{OSGeo Member
|Name=Vaclav Petras
|JobTitle=Geospatial Research Software Engineer
|Company=North Carolina State University
|Country=USA
|State=NC
|City=Raleigh
|Coordinate=35.784811, -78.681698
|LocalChapter=North America
|Email=wenzeslaus gmail com
|SocialMedia=@vaclavpetras
|Website=http://wenzeslaus.github.io/
|Languages=Czech; English
}}
{{OSGeo Experience
|User=Yes
|Committee=No
|Board=No
|Coder=Yes
|Translate=No
|PSC=Yes
|ExBoard=No
|Charter=Yes
|Chair=No
|SolKatz=No
|Committer=Yes
}}
=== Vaclav Petras ===

* Member of [https://geospatial.ncsu.edu/geoforall/ NCSU GeoForAll Lab]
* Former member of [http://geomatics.fsv.cvut.cz/research/geoforall/ GeoForAll Lab at FCE CTU in Prague]
* [http://grass.osgeo.org/ GRASS GIS] user, developer (http://grasswiki.osgeo.org/wiki/User:Wenzeslaus) and PSC member
** participated in GSoC [https://trac.osgeo.org/grass/wiki/GSoC/2014/TestingFrameworkForGRASS 2014] as student and in GSoC 2016, 2017, 2018, 2020, and 2021 as a mentor
** development [https://www.openhub.net/accounts/wenzeslaus statistics]
*Previous location: Prague, Czech Republic

* Twitter: http://twitter.com/vaclavpetras
* LinkedIn: https://www.linkedin.com/in/vaclav-petras-a24a1b114/

;Profile last updated: August 2018

[[Category:OSGeo Advocate]]

FOSS4G 2022/Community sprint

2022-06-16T17:39:45Z

Wenzeslaus: /* GRASS GIS */

== Code Sprint ==

Also this year, after the online conference, there will be the '''OSGeo community sprint'''.

Participation is free of charge and anyone involved or interested in getting involved in OSGeo community projects is welcome.

This year we will try to offer the format '''an hour with the developer''', where we ask seasoned community members to donate time for welcoming new members and introduce them to different projects or guide them through the setup of the development environment or translation tools and get started on the Foss4G journey.

You can choose to contribute to one or more projects. The sky is the limit. There’s always plenty to do – and it’s not all about programming. Translation, documentation, feedback, discussions, and testing are very important for projects! Conference registration is not a prerequisite for participation in the code sprint.

=== When ===

The code sprint will be held on 27-28 of August.

=== Where ===

The codesprint will be hosted at the University of Florence.

More information about the rooms and social channels for the codesprint will be notified later.

== Registered Attendees ==

The code sprint is free of charge but we kindly ask you to write down your name for better planning.

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|No
!width="250"|Name
!width="250"|Email
!width="250"|Projects
!width="250"|Registered to FOSS4G conference
!width="250"|Present on Sat 27th
!width="250"|Present on Sun 28th
|-
|1 || Andrea Antonello || andrea.antonello at gmail || Codesprint Org, [https://www.geopaparazzi.org/smash/index.html SMASH], [https://integratedmodelling.org/getting-started/ k.LAB] || x || x || x
|-
|2 || Jody Garnett || jody.garnett at gmail.com || geotools.org, geoserver.org || x || ||
|-
|3 || Vicky Vergara || vicky at georepublic.de || pgRoutig, OSGeoLive, OSGeo Website || x || ||
|-
|4 || Markus Neteler || neteler at osgeo.org || GRASS GIS, actinia, GRASS Website || x || ||
|-
|5 || Howard Butler || howard at hobu.co || PDAL, GDAL, and PROJ || x || ||
|-
|6 || Akin Kuye || t_kuye@yahoo.com || Codesprint Org, SMASH || x || ||
|-
|7 || Emmanuel Dubois || emmanuel.dubois@cnes.fr || OTB and 3D CNES tools: CARS, pandora, demcompare || x || ||
|-
|8 || Anna Petrasova || wenzeslaus gmail com || GRASS GIS || x || x || x
|-
|9 || Vaclav Petras || kratochanna gmail com || GRASS GIS || x || x || x
|-
|10 || Tom Kralidis || tomkralidis gmail com || Geopython (pygeoapi, pycsw, pygeometa, OWSLib, etc.) || x || x || x
|-
|11 || my name || my email || projects I will work on || x || x || x
|-
|}

== Workgroups ==

=== Project-name ===

To participate, copy this project skeleton and start a section below (alphabetically) for your project.

==== Attending ====

*user
*user

==== Goals ====

*your goals

==== Participation at '''an hour with the developer''' ====

* name of the developer - time/day of availability

=== GeoServer ===

Working on GeoServer community goals, Java 17 LTS proposed.

==== Attending ====

* jody.garentt

==== Goals ====

* Java 17 LTS (proposed)

==== Participation at '''an hour with the developer''' ====

* Jody Garnett, standing offer to help new developers checkout and build GeoServer during sprint

=== GRASS GIS ===

[[Image:Grasslogo_vector_small.png|right]]

==== Attending ====

* Markus Neteler
* Anna Petrasova
* Vaclav Petras

==== Goals ====

* Help starting contributors.
* Python and command line usability issues.
* Discuss hard-to-finish PRs.
* Sync with the PDAL project.

==== Participation at '''an hour with the developer''' ====

* Vaclav (Vashek) Petras - times: TBD, find me, ask me

=== SMASH ===

Working on SMASH digital field mapping app enhancements.

==== Attending ====

* Andrea Antonello
* Silvia Franceschi
* Luca Delucchi
* Akin Kuye

==== Goals ====

* bugfixing
* server-app enhancements

==== Participation at '''an hour with the developer''' ====

* Andrea Antonello - time to be defined, based on organization issues

=== pgRouting ===

Working on tasks for becoming an OSGeo project

==== Attending ====

* vicky Vergara

==== Goals ====

* Work on tasks to become an OSGeo project

==== Participation at '''an hour with the developer''' ====

* Vicky Vergara - time to be defined, based on organization issues

[[Category:FOSS4G2022]] [[Category:FOSS4G]] [[Category:Code_Sprints]]

FOSS4G 2022/Community sprint

2022-06-16T13:00:11Z

Wenzeslaus: /* Registered Attendees */ added presence for VP & AP, use more common day of week abbrev

FOSS4G 2022/Community sprint

2022-06-14T21:04:32Z

Wenzeslaus: /* GRASS GIS */ add people and goals

FOSS4G 2022/Community sprint

2022-06-10T14:00:51Z

Wenzeslaus: Add GRASS GIS section from template

FOSS4G 2022/Community sprint

2022-06-10T13:58:58Z

Wenzeslaus: Add VP and AP

FOSS4G 2021/Community sprint

2021-10-02T07:16:03Z

Wenzeslaus: at conference

== Code Sprint ==

Also this year, after the online conference, there will be the '''OSGeo community sprint'''.

Participation is free of charge and anyone involved or interested in getting involved in OSGeo community projects is welcome.

You can choose to contribute to one or more projects. The sky is the limit. There’s always plenty to do – and it’s not all about programming. Translation, documentation, feedback, discussions, and testing are very important for projects! Conference registration is not a prerequisite for participation in the code sprint.


=== When ===
The code sprint will be held on Saturday October 2nd, 2021.

=== Where ===
Online, we will use [https://workadventu.re/ WorkAdventu.re] plus a bounce of Jitsi channels for each project. You can joint the WorkAdventu.re [https://play.workadventu.re/@/osgeo/foss4g/codesprint here]

== Registered Attendees ==

The code sprint is free of charge but we kindly ask you to write down your name for better planning.

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|No
!width="250"|Name
!width="250"|Email
!width="250"|Projects
!width="250"|Registered to FOSS4G conference
|-
|1 || [[User:Lucadelu|Luca Delucchi]] || lucadeluge gmail com || GRASS GIS, pyModis, OSGeoLive (code sprint organizer) || x
|-
|2 || [[User:Cvvergara|Vicky Vergara]] || vicky at georepublic de || Contributions with Translations|| x
|-
|3 || [[User:Astrid_emde|Astrid Emde]] || astrid_emde at osgeo dot org || OSGeoLive, Mapbender, OSGeo || x
|-
|4 || [[User:Veroandreo|Vero Andreo]] || veroandreo at gmail dot com || GRASS GIS || x
|-
|5 || [[User:Tomkralidis|Tom Kralidis]] || tomkralidis at gmail dot com || Geopython, MapServer, QGIS, go-spatial || x
|-
|6 || Shubham|Shubham Kumar || 2020kucp1062@iiitkota.ac.in || Project ||
|-
|7 || [[User:kalxas|Angelos Tzotsos]] || tzotsos at osgeo dot org || pycsw, OSGeoLive, Geopython || x
|-
|8 || Carmen Tawalika || carmen.tawalika at gmail dot com || actinia || x
|-
|9 || [[User:Neteler|Markus Neteler]] || neteler at osgeo dot org || GRASS GIS, actinia || x
|-
|10 || Anika Weinmann || weinmann at mundialis dot de || GRASS GIS, actinia || x
|-
|11 || Guido Riembauer || riembauer at mundialis dot de || GRASS GIS, actinia || x
|-
|12 || [[User:mmetz|Markus Metz]] || metz at mundialis dot de || GRASS GIS, actinia ||
|-
|13 || [[User:Robe|Regina Obe]] || lr at pcorp dot us || PostGIS, pgRouting, Translations || x
|-
|14 || [[User:Bakaniko|Nicolas Roelandt]] || roelandtn.pro at gmail dot com || OSGeoLive || x)
|-
|15 || [[User:Chrismarx|Chris Marx]] || chrismarx at gmail dot com || Unaffiliated || x
|-
|16 || [[User:Pkopparla|Pushkar Kopparla]] || pushkarkopparla at gmail dot com || Unaffiliated ||
|-
|17 || [[User:LauraMugeha|Laura Mugeha]] || mugeha dot okole at gmail dot com || Unaffiliated || x
|-
|18 || [[User:Felipebarros|Felipe Barros]] || felipe.b4rros at gmail dot com || Unaffiliated || x
|-
|19 || [[User:Jive|Jody Garnett]] || jody.garnett@gmail.com || GeoTools, GeoServer, OSGeo || x
|-
|20 || [[User:Wolf|Wolf Bergenheim]] || wolf _at_ bergenheim.net || Unaffiliated (GRASS and GDAL in the past) || x
|-
|21 || Peter Smythe || gs at smythe.co.za || GeoServer || x
|-
|22 || [[User:Aanthieni|Ariel Anthieni]] || aanthieni@kan.com.ar || Geonode || x
|-
|23 || Walter Shilman || wshilman@kan.com.ar || Geonode || x
|-
|24 || [[User:Pesekon2|Ondrej Pesek]] || pesej.ondrek at gmail.com || GRASS GIS ||
|-
|25 || [[User:Wenzeslaus|Vaclav Petras]] || wenzeslaus at gmail.com || GRASS GIS || x
|-
|}

== Workgroups ==

=== Project-name ===
To participate, copy this project skeleton and start a section below for your project.

'''Attending:'''
*user
*user

'''Goals:'''
*your goals

=== GRASS GIS ===
''' Attending:'''
* [[User:Lucadelu|Luca Delucchi]]
* [[User:Veroandreo|Vero Andreo]]
* [[User:Neteler|Markus Neteler]]
* Anika Weinmann
* Guido Riembauer
* [[User:mmetz|Markus Metz]]
* [[User:Wolf|Wolf Bergenheim]]
* [[User:Wenzeslaus|Vaclav Petras]]
* ...

'''Goals:'''
* Release GRASS 7.8.6 RC3 (?)
* Branch GRASS 8.0
* https://github.com/OSGeo/grass/milestone/4

=== Contributions with translations ===
Translations on transifex
Please register to any of your favorite projects:
* OSGeoLive: https://www.transifex.com/osgeo/osgeolive
* pgRouting: https://www.transifex.com/pgrouting/pgrouting
* PostGIS: https://www.transifex.com/postgis/postgis
''' Attending:'''
* [[User:Cvvergara|Vicky Vergara]]
* [[User:robe|Regina Obe]]

'''Goals:'''
* Translations

=== actinia ===
''' Attending:'''
* Carmen Tawalika
* [[User:Neteler|Markus Neteler]]
* Anika Weinmann
* Guido Riembauer
* ...

'''Goals:'''
* see https://github.com/mundialis/actinia_core/projects/2

=== OSGeoLive ===

'''Attending:'''
* [[User:Bakaniko|Nicolas Roelandt]]
* [[User:astrid_emde|Astrid Emde]]

'''Goals:'''
* Update translations
* Work on translations
* Discuss Version 15 and upcoming milestones
* Work on tickets and define new ones ;)

=== GeoServer ===

'''Attending:'''
* [[User:Jive|Jody Garnett]]
* Peter Smythe

'''Goals:'''
* User interface layout improvements

=== Geonode ===
''' Attending:'''
* [[User:Aanthieni|Ariel Anthieni]]
* Walter Shilman
* ...

'''Goals:'''
* Translation: see the possibility of making multi language the help of Geonode

[[Category:FOSS4G2021]] [[Category:FOSS4G]] [[Category:Code_Sprints]]

FOSS4G 2021/Community sprint

2021-10-02T07:15:27Z

Wenzeslaus: add myself

== Code Sprint ==

Also this year, after the online conference, there will be the '''OSGeo community sprint'''.

Participation is free of charge and anyone involved or interested in getting involved in OSGeo community projects is welcome.

You can choose to contribute to one or more projects. The sky is the limit. There’s always plenty to do – and it’s not all about programming. Translation, documentation, feedback, discussions, and testing are very important for projects! Conference registration is not a prerequisite for participation in the code sprint.


=== When ===
The code sprint will be held on Saturday October 2nd, 2021.

=== Where ===
Online, we will use [https://workadventu.re/ WorkAdventu.re] plus a bounce of Jitsi channels for each project. You can joint the WorkAdventu.re [https://play.workadventu.re/@/osgeo/foss4g/codesprint here]

== Registered Attendees ==

The code sprint is free of charge but we kindly ask you to write down your name for better planning.

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|No
!width="250"|Name
!width="250"|Email
!width="250"|Projects
!width="250"|Registered to FOSS4G conference
|-
|1 || [[User:Lucadelu|Luca Delucchi]] || lucadeluge gmail com || GRASS GIS, pyModis, OSGeoLive (code sprint organizer) || x
|-
|2 || [[User:Cvvergara|Vicky Vergara]] || vicky at georepublic de || Contributions with Translations|| x
|-
|3 || [[User:Astrid_emde|Astrid Emde]] || astrid_emde at osgeo dot org || OSGeoLive, Mapbender, OSGeo || x
|-
|4 || [[User:Veroandreo|Vero Andreo]] || veroandreo at gmail dot com || GRASS GIS || x
|-
|5 || [[User:Tomkralidis|Tom Kralidis]] || tomkralidis at gmail dot com || Geopython, MapServer, QGIS, go-spatial || x
|-
|6 || Shubham|Shubham Kumar || 2020kucp1062@iiitkota.ac.in || Project ||
|-
|7 || [[User:kalxas|Angelos Tzotsos]] || tzotsos at osgeo dot org || pycsw, OSGeoLive, Geopython || x
|-
|8 || Carmen Tawalika || carmen.tawalika at gmail dot com || actinia || x
|-
|9 || [[User:Neteler|Markus Neteler]] || neteler at osgeo dot org || GRASS GIS, actinia || x
|-
|10 || Anika Weinmann || weinmann at mundialis dot de || GRASS GIS, actinia || x
|-
|11 || Guido Riembauer || riembauer at mundialis dot de || GRASS GIS, actinia || x
|-
|12 || [[User:mmetz|Markus Metz]] || metz at mundialis dot de || GRASS GIS, actinia ||
|-
|13 || [[User:Robe|Regina Obe]] || lr at pcorp dot us || PostGIS, pgRouting, Translations || x
|-
|14 || [[User:Bakaniko|Nicolas Roelandt]] || roelandtn.pro at gmail dot com || OSGeoLive || x)
|-
|15 || [[User:Chrismarx|Chris Marx]] || chrismarx at gmail dot com || Unaffiliated || x
|-
|16 || [[User:Pkopparla|Pushkar Kopparla]] || pushkarkopparla at gmail dot com || Unaffiliated ||
|-
|17 || [[User:LauraMugeha|Laura Mugeha]] || mugeha dot okole at gmail dot com || Unaffiliated || x
|-
|18 || [[User:Felipebarros|Felipe Barros]] || felipe.b4rros at gmail dot com || Unaffiliated || x
|-
|19 || [[User:Jive|Jody Garnett]] || jody.garnett@gmail.com || GeoTools, GeoServer, OSGeo || x
|-
|20 || [[User:Wolf|Wolf Bergenheim]] || wolf _at_ bergenheim.net || Unaffiliated (GRASS and GDAL in the past) || x
|-
|21 || Peter Smythe || gs at smythe.co.za || GeoServer || x
|-
|22 || [[User:Aanthieni|Ariel Anthieni]] || aanthieni@kan.com.ar || Geonode || x
|-
|23 || Walter Shilman || wshilman@kan.com.ar || Geonode || x
|-
|24 || [[User:Pesekon2|Ondrej Pesek]] || pesej.ondrek at gmail.com || GRASS GIS ||
|-
|25 || [[User:Wenzeslaus|Vaclav Petras]] || wenzeslaus at gmail.com || GRASS GIS ||
|-
|}

== Workgroups ==

=== Project-name ===
To participate, copy this project skeleton and start a section below for your project.

'''Attending:'''
*user
*user

'''Goals:'''
*your goals

=== GRASS GIS ===
''' Attending:'''
* [[User:Lucadelu|Luca Delucchi]]
* [[User:Veroandreo|Vero Andreo]]
* [[User:Neteler|Markus Neteler]]
* Anika Weinmann
* Guido Riembauer
* [[User:mmetz|Markus Metz]]
* [[User:Wolf|Wolf Bergenheim]]
* [[User:Wenzeslaus|Vaclav Petras]]
* ...

'''Goals:'''
* Release GRASS 7.8.6 RC3 (?)
* Branch GRASS 8.0
* https://github.com/OSGeo/grass/milestone/4

=== Contributions with translations ===
Translations on transifex
Please register to any of your favorite projects:
* OSGeoLive: https://www.transifex.com/osgeo/osgeolive
* pgRouting: https://www.transifex.com/pgrouting/pgrouting
* PostGIS: https://www.transifex.com/postgis/postgis
''' Attending:'''
* [[User:Cvvergara|Vicky Vergara]]
* [[User:robe|Regina Obe]]

'''Goals:'''
* Translations

=== actinia ===
''' Attending:'''
* Carmen Tawalika
* [[User:Neteler|Markus Neteler]]
* Anika Weinmann
* Guido Riembauer
* ...

'''Goals:'''
* see https://github.com/mundialis/actinia_core/projects/2

=== OSGeoLive ===

'''Attending:'''
* [[User:Bakaniko|Nicolas Roelandt]]
* [[User:astrid_emde|Astrid Emde]]

'''Goals:'''
* Update translations
* Work on translations
* Discuss Version 15 and upcoming milestones
* Work on tickets and define new ones ;)

=== GeoServer ===

'''Attending:'''
* [[User:Jive|Jody Garnett]]
* Peter Smythe

'''Goals:'''
* User interface layout improvements

=== Geonode ===
''' Attending:'''
* [[User:Aanthieni|Ariel Anthieni]]
* Walter Shilman
* ...

'''Goals:'''
* Translation: see the possibility of making multi language the help of Geonode

[[Category:FOSS4G2021]] [[Category:FOSS4G]] [[Category:Code_Sprints]]

Google Summer of Code Recommendations for Students

2021-03-30T19:00:23Z

Wenzeslaus: /* 6. GSoC participation */ participated to/in GSoC

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

== How to get in contact with your potential mentors ==

Since OSGeo is an umbrella organisation for multiple project communities, each community has their own discussion and development [[Mailing Lists]].

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

:* OSGeo SoC Mentors and Students - soc@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/soc): subscribe right away to this mailing list, and introduce yourself and your idea.
:* OSGeo Wide Discussion List - discuss@lists.osgeo.org (http://lists.osgeo.org/mailman/listinfo/discuss)
:* The dedicated dev mailing list of the software you intend to develop for (Browse http://lists.osgeo.org)

* To contact OSGeo's GSoC admin team directly (only for private matters that can't be shared in SoC ML):
** send an email to [mailto:gsoc-admin@osgeo.org gsoc-admin@osgeo.org]

== How to increase your chances of being selected ==

If you put yourself in the shoes of the mentor that should select the student, you'll immediately realize that there are some behaviours that are usually rewarded. Here's some examples.

=== Be proactive ===

* Mentors are more likely to select students that openly discuss the existing ideas and / or propose their own. It is a '''bad idea''' to just submit your idea only in the Google web site without discussing it, because it won't be noticed. Mentors and developers discuss ideas mostly in [[Google_Summer_of_Code_Recommendations_for_Students#How_to_get_in_contact_via_mailing_lists | mailing lists]].
* It is a '''bad idea''' just listing your programming skills and waiting for the mentors to guide you towards next steps. Mentors reward students that show genuine interest in the projects they are willing to develop, propose improvements on their own and make pertinent questions. Remember that it is up to you, and not to the mentor, decide the software you want to work on and the idea to develop. It is not the mentor's job to do that for you.

=== Discuss your idea in public channels ===

* Even if you have had some contact with a potential mentor, remember that the proposals discussion must happen in public channels, as it is always the case in open source communities.
* It is a '''good idea''' to engage the individual dev lists and find a community that you are interested in working with and start building a relationship with that community. It is the community that decides which of the candidates they want to back, based on the value of the project, and whether or not they think the student will be successful.

=== Demonstrate your skills ===

Consider that mentors are being contacted by several students that apply for the same project. A way to show that you are the best candidate, is to demonstrate that you are familiar with the software and you can code. How? Browse the bug tracker, fix some bugs and propose your patch in mailing list, and/or ask mentors to challenge you! Moreover, bug fixes are a great way to get familiar with the code.

Former contributions to open source might be an asset and increase your chances of being selected.

=== Demonstrate your intention to stay ===

Students that are likely to disappear after GSoC are less likely to be selected. This is because there is no point in developing something that won't be maintained. And moreover, one scope of GSoC is to bring new developers to the community.

=== [http://xkcd.com/293/ RTFM] ===

Read the relevant information about GSoC in the wiki / web pages before asking. Most FAQs have been answered already!
* OSGeo Wiki pages related to GSoC can be browsed from [http://wiki.osgeo.org/wiki/Category:Google_Summer_of_Code Category:Google Summer of Code].
* [https://developers.google.com/open-source/gsoc/resources/ Full documentation about GSoC on official website].
* [https://developers.google.com/open-source/gsoc/faq FAQ from GSoC web site].
* [https://summerofcode.withgoogle.com/rules/ Google Summer of Code program rules].
* [https://google.github.io/gsocguides/student/ The student's manual].

* If you are new to OSGeo, take the time to familiarize with the [https://www.osgeo.org/about/ Open Source Geospatial Foundation]
* Here is a [https://docs.google.com/presentation/d/16R52y5Jr0YNfrEzWv0C74ol9te4wWWo_0Qc5VQpeqqI/edit?usp=sharing presentation]
* [https://www.youtube.com/watch?v=Pb5N6mD5cbg&list=PLRHB_6bPp2blWWhQ14TVlFPQ0m7VqzbPa Videos playlist]

== Application instructions ==

We welcome students to contact relevant developer communities within OSGeo umbrella before submitting their application into GSoC official website. If in doubt for which project(s) to contact, send the mail to both soc and discuss mailing lists.

We recommend browsing past years' ideas pages, to look for ready-to-use projects, and to get an idea of the expected amount of work for a valid GSoC proposal. Read [https://google.github.io/gsocguides/student/writing-a-proposal here] how to write a nice proposals.

Remember to use the template below. The same template, for your convenience, can be downloaded also from [https://github.com/OSGeo/gsoc/blob/master/proposal_template.md github]. After filling the template and detailing the proposal, you must follow the guidelines given by Google to submit it. Remember to submit your proposal well in advance, so that you can make the most out of the feedback from mentors and the community at large and refine your proposal until final deadline.

Developers will give feedback and prepare a small coding test (programming exercise or bug fix). See [https://developers.google.com/open-source/gsoc/help/responsibilities GSoC Roles and Responsibilities] to understand a successful teamwork and interplay of project, mentors and students.

As a general remark, we know that late submissions are not our best shot, as we usually find them incomplete, so be aware that the sooner you submit your proposals, the better chances you have to adjust them to mentors' requirements, and in the end, better chances to be selected.

If you submit your proposal as "final", mentors cannot access it until deadline. So, unless you also share the google docs as public, we don't have a way to give you feedback and we will be evaluating your final proposal as it is, so you have less chances, or none at all if your proposals hasn't been discussed anywhere in public channels.

IMPORTANT: When you share your proposal, always allow comments! If you share it in view only, mentors can't give you feedback.

Remember that GSoC is a highly competitive program, we prioritize quality over quantity, this means that we only accept excellent proposals. Submitting a sloppy proposal it's just a useless waste of time for you and for mentors.

-----

=== Template ===

==== 1. Contact details ====
* Name and surname:
* Nickname:
* Country:
* Email:
* Phone (we will not call you, unless you will become unreachable by email/IM for more than a week without warning):
* Public repository/ies:
* Personal blog (optional):
* Twitter/Identica/LinkedIn/others:

==== 2. Your idea ====
* OSGeo or guest software:
* Title: (please include the name of the member project as part of the title, for example: "Gee Whiz Foobar 2001 for QGIS")
* Brief description of the idea. e.g. "My project will focus on xxx".
* The state of the software BEFORE your GSoC. For example, if you want to make a GUI, you can say: "In the software XYZ, when I want to use the tool xxx, I have to manually edit the file yyy. "
* The addition that your project will bring to the software. In the same example: "With the GUI that I intend to create, it will be possible to use the tool xxx via graphical user interface".
* Future developments. How can your project be expanded or maintained after GSoC is over.

==== 3. Timeline ====
* Now split your project idea in smaller tasks. Quantify the time you think each task needs. Finally, draw a detailed project plan (timeline) including the dates covering all period of GSoC. Don’t forget to include also the days in which you don’t plan to code, because of exams, holidays etc.
* The workload should be split in weekly chunks.
* Your timeline should contain actual dates, not "week 1", "week 2", etc.
* Note that by the start of the official coding period, students should be ready to start coding right away. Activities such as: initial research, set up working environment, choose tools to be used in the project, set up repository, familiarize with the code base and with the mentors, etc must be carried out during [[Google_Summer_of_Code_Recommendations_for_Students#Bonding_period | bonding period]]. In your timeline, please add also activities that you will be carry out during the bonding period.
* Do you understand this is a serious commitment, equivalent to a full-time paid summer internship or summer job?
* Do you have any known time conflicts during the official coding period? (Jobs, vacations, etc.)

==== 4. Studies ====
* What is your School and degree?
* Would your application contribute to your ongoing studies/degree? If so, how?

==== 5. Programming and GIS ====
* Computing experience: operating systems you use on a daily basis, known programming languages, hardware, ecc.
* GIS experience as a user
* GIS programming and other software programming
* Briefly mention and link to former open source contributions

==== 6. GSoC participation ====
* Have you participated in GSoC before?
* How many times, which year, which project?
* Have you applied but were not selected? When?
* Have you submitted/will you submit another proposal for this year's GSoC to a different org? Which one?

== What to expect after application ==

Now that you have submitted your application, it's time for you to set up your development environment and get familiar with the code of the software you want to develop for. Ask the developers to test you with a small coding task, or browse the bug tracker and submit a patch for a bug.

=== Bonding period ===

Bonding period does not mean relax. During bonding period, you are supposed to do all preparation in order to be able to start coding immediately the first week of actual coding period. These activities entail:
* set up your dev environment: compile the source code, etc;
* getting familiar with the source code, the dev documentation, programming manual and all the material that your mentors suggest;
* start coding for bug fixes not necessarily related to your project;
* scratching and pseudocoding your project;
* set up your repository, familiarize with version control systems such as git / svn etc;
* set up your wiki page, where you will describe your project and keep track of your weekly progresses;
* get in touch with the community: introduce yourself in soc and dev mailing list, introduce your project and receive feedback.

== What to expect during the summer ==

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

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

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

=== Weekly reports ===

Every week, by Sunday, we expect to see your weekly progress report posted to the soc@osgeo and the developer mailing list of your project. You are requested to send the report even if you didn't code because of exams or holidays, or any other reason. The report should to contain the title of the project in the subject, the link to your wiki page, the link to the public repository of your weekly commits and at least the answers to these 3 questions:

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

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

If you want, feel free to expand your report, however this is the minimum required.

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

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

=== Code repository and documentation ===

Publishing your progress online and publicly is a GSoC requirement. Therefore, all students have to decide, before GSoC coding period starts, where to publish the code they will write. We ask students to give the link to the public repository in the first weekly report.

The possibilities are:
* get a sandbox in your software project's repository (your mentor will tell you how to get write access)
* work on a branch of the main code repository (for centralized versioning systems like SVN)
* work on a fork of the code repository (for DCVS like Mercurial and Git)
* work on an independent codebase (if you are developing a plugin or some other extra functionality that is not yet part of main codebase)

Your mentor is the best guide regarding this choice. Please discuss it as soon as possible, and learn how to use the related version control tool well before GSoC coding starts.

Documentation of your code is important! Don't leave all documentation writing to the last weeks of GSoC. It makes sense to outline it at the beginning of coding period, then refine it while you code. It is an important support to coding, as it is a mirror of the overall plan for the summer, and an essential source of information for who will use your code.

=== Wiki page and blogs ===

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

Wiki and/or blog space can and will be provided by OSGeo if your project doesn't have anything already set up for this. Alternatives may be code repositories with wiki/blog functionality like [https://github.com/ GitHub], [https://about.gitlab.com/ GitLab] or [https://bitbucket.org/ Bitbucket].

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

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

== How to get in contact via IRC ==

Primary channel:

* '''#osgeo''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=osgeo browser])

GSoC @ OSGeo inter-project discussions:

* '''#osgeo-soc''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=osgeo-soc browser])

Project irc channels:

* '''#gdal''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=gdal browser])
* '''#geoserver''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=geoserver browser])
* '''#geotools''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=geotools browser])
* '''#grass''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=grass browser])
* '''#gvsig''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=gvsig browser])
* '''#mapguide''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=mapguide browser])
* '''#mapnik''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=mapnik browser])
* '''#mapserver''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=mapserver browser])
* '''#openlayers''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=openlayers browser])
* '''#opticks''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=opticks browser])
* '''#osgeolive''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=osgeolive browser])
* '''#ossimplanet''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=ossimplanet browser])
* '''#ossimplanet''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=ossimplanet browser])
* https://gitter.im/pgRouting/pgrouting
* '''#postgis''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=postgis browser])
* '''#qgis''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=qgis browser])
* '''#udig''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=udig browser])
* '''#geonode''' on freenode.net (connect directly in your [http://webchat.freenode.net/?channels=geonode browser])

[[Category: Google Summer of Code]]

Joint OGC OSGeo ASF Sprint 2021

2021-02-17T14:52:05Z

Wenzeslaus: /* Participants */

== Purpose ==
Document/track/coordinate FOSS4G project participation at the virtual [https://github.com/opengeospatial/joint-ogc-osgeo-asf-sprint-2021 Joint OGC OSGeo ASF Code Sprint 2021]. The virtual event will run on 17/18/19 February 2021. The sprint will begin at 07:00am EST on the first day, and end at 05:30pm EST on the last day.

== Event Details ==

All information, logistics for participants is coordinated at https://github.com/opengeospatial/joint-ogc-osgeo-asf-sprint-2021

There is an OGC registration page (https://portal.ogc.org/public_ogc/register/20210217_code_sprint.php) if you wish to be invited to kick-off meetings.

== Participants ==
{| class="wikitable"
|-
! No !! Name !! Country !! Email !! Organization !! Project(s) || Standard (s)
|-
| 1 || Tom Kralidis || Canada || tomkralidis at gmail.com || Meteorological Service of Canada || pygeoapi, pycsw, OWSLib and the Geopython stack || ogc-api-records
|-
| 2 || Angelos Tzotsos || Greece || tzotsos at gmail.com || OSGeo || OSGeoLive, pycsw, pygeoapi, GeoNode, OWSLib ||
|-
| 3 || Steve Lime || USA/MN || sdlime at gmail.com || MNIT Services || MapServer || OGCAPI support
|-
| 4 || Astrid Emde || Germany || astrid_emde at osgeo.org || OSGeo || OSGeoLive, OSGeo ||
|-
| 5 || Andrea Aime || Italy || andrea.aime at gmail.com || GeoSolutions || GeoServer || ogc-api-features
|-
| 6 || Jody Garnett || Canada|| jody.garnett at gmail.com || GeoCat || GeoServer || ogc-api-features
|-
| 7 || Paul van Genuchten || NL|| genuchten at yahoo.com || GeoCat || GeoNetwork / pygeoapi || ogc-api-features
|-
| 8 || Just van den Broecke || NL|| justb4 at gmail.com || Just Objects || pygeoapi, stetl, GeoHealthCheck and the GeoPython stack || ogc-api-features
|-
| 9 || Peter Rushforth || Canada || peter.rushforth at gmail.com || Natural Resources Canada || GeoServer || Map Markup Language
|-
| 10 || Ahmad Ayubi || Canada || ahmad.ayubi at canada.ca || Natural Resources Canada || GeoServer MapML Community Module Viewer || Map Markup Language
|-
| 11 || Massimo Di Stefano || Norway || massimods at met.no || Norwegian Meteorological Institute || pycsw || CSW
|-
| 12 || Anna Petrasova || USA || kratochanna gmail com || North Carolina State University || GRASS GIS ||
|-
| 13 || Vaclav Petras || USA || wenzeslaus gmail com || North Carolina State University || GRASS GIS ||
|}

== Updates ==

[[Category:Code Sprints]]
[[Category:OGC]]

OSGeo Virtual Community Sprint 2020

2020-11-06T21:28:16Z

Wenzeslaus: /* Participants */ add myself

Due to COVID-19 the Annual OSGeo Code Sprint will happen online in 2020.

Powered by [[Image:Osgeo-logo.png|250px|link=https://www.osgeo.org]]

== Purpose ==

Bring together project members to make decisions and tackle larger geospatial
problems as in previous years:
* [[OSGeo_Community_Sprint_2019|Minnesota]] (2019)
* [[OSGeo Code Sprint 2018|Bonn]] (2018)
* [[Daytona Beach Code Sprint 2017|Daytona_Beach]] (2017)
* [[Paris Code Sprint 2016|Paris]] (2016)
* [[Philadelphia Code Sprint 2015|Philadelphia]] (2015)
* [[Vienna Code Sprint 2014|Vienna]] (2014)
* [[Boston Code Sprint 2013|Boston]] (2013)
* [[IslandWood Code Sprint 2012|Island Wood (Seattle)]] (2012)
* [[Montreal Code Sprint 2011|Montreal]] (2011)
* [[New York Code Sprint 2010|New York City]] (2010)
* [[Toronto Code Sprint 2009|Toronto]] (2009)

== Sponsors ==

'''Sponsoring ''' Find out about [[OSGeo_Virtual_Community_Sprint_2020#Sponsoring |Sponsoring the Event]].

; <big>Gold Sponsors</big>
{| border=0 cellspacing=15 cellpadding=10
||
[[File:GC-Group logo.png|220px|GeoCue|link=http://www.geocue.com/]]
 
http://www.geocue.com/
||
[[File:safe-software-logo.png|220px|Safe Software|link=https://www.safe.com/]]
 
https://www.safe.com/
||
[[File:RIEGL.png|310px|RIEGL|link=http://www.riegl.com/]]
 
http://www.riegl.com/
|}

; <big>Silver Sponsors</big>
{| border=0 cellspacing=15 cellpadding=10
||
[[File:Hobulogo.png|160px|Hobu|link=https://hobu.co/]]
 
https://hobu.co/
||
[[File:Bh-logo.jpg|300px|link=https://www.bhinc.com/]]
 
[https://www.bhinc.com/ https://www.bhinc.com/]
||
[[File:Crunchydata.png|160px|CrunchyData||link=http://www.crunchydata.com/]]
 
[http://www.crunchydata.com/ http://www.crunchydata.com/]
|}
{| border=0 cellspacing=15 cellpadding=10
||
[[File:Gaia3D.png|240px|Gaia3D||link=https://gaia3d.com/en/]]
 
[https://gaia3d.com/en/ https://gaia3d.com/en/]
|}

; <big>Bronze Sponsors</big>
{| border=0 cellspacing=15 cellpadding=10
||
[[File:CoordinateSolutions_TRANS.png|210px|link=http://www.coordinatesolutions.com/]]
 
[http://www.coordinatesolutions.com/ http://www.coordinatesolutions.com/]
||
[[File:Logo-EOX.png|140px|EOX IT Services GmbH|link=http://eox.at]]
 
[http://eox.at http://eox.at]
||
[[File:Pixel8_logo_full.png|140px|link=https://www.pixel8.earth/]]
 
[https://www.pixel8.earth/ https://www.pixel8.earth/]
|}
{| border=0 cellspacing=15 cellpadding=10
||
[[File:Azavea-logo.png|160px|link=https://www.azavea.com/]]
 
[https://www.azavea.com/ https://www.azavea.com/]
||
[[File:Greenwood_logo.png|210px|link=https://greenwoodmap.com/]]
 
[https://greenwoodmap.com/ https://greenwoodmap.com/]
|}

== Dates and Times ==

* Date: 2020 November 17-18-19
* Time: all day

== Other Events in November 2020 ==

* ''please add your event''

== Location ==

* Main zoom channel for kick off and closing event (TBD)
* Jitsi channels will be listed here by projects

== Project Plans ==
(i.e what do you wish/want/plan to work on during the sprint ?)

* '''OSGeoLive''':
** Work towards 14.0 release

* '''PostGIS''':
** Work towards PostGIS 3.1.0 in Sept/Oct

* '''GEOS''':
** Work towards 3.9.0 release

* '''GeoServer MapML Community Module''':
** Validate / socialize concepts, work toward extension module status

== Participants ==

Please add your name and the projects you are planning to sprint and note the likeliness of your attendance.

{| border="1" cellpadding="2" class="wikitable sortable"
!width="25"|No
!width="250"|Name
!width="100"|Country
!width="250"|Email
!width="250"|Organisation
!width="250"|Projects
!width="25"|Tue
!width="25"|Wed
!width="25"|Thu
|-
| 1 ||[[User:kalxas|Angelos Tzotsos]] || GR || tzotsos(at)osgeo.org || OSGeo || pycsw, OSGeoLive, GeoNode, UbuntuGIS, pygeoapi, OTB || x || x || x ||
|-
| 2 || [[User:msmitherdc|Michael Smith]] || US || Michael.smith.erdc(at)gmail.com || USACE || pdal, gdal, mapserver || x || x || x ||
|-
| 3 ||[[User:prushforth|Peter Rushforth]] || CA || peter.rushforth(at)gmail.com || W3C Maps for HTML Community Group|| GeoServer MapML Community Module || x || x || x ||
|-
| 4 || [[User:Lucadelu|Luca Delucchi]] || IT || lucadeluge@gmail.com || Fondazione Edmund Mach || GRASS GIS, pyModis, OSGeoLive || x || x || x ||
|-
| 5 || [[User:Wenzeslaus|Vaclav Petras]] || US || wenzeslaus(at)gmail.com || North Carolina State University || GRASS GIS || x || x || x ||
|-
| 6 ||Add your details here || || || || || || || ||
|}

== Communication ==

* Please join the mailing list: https://lists.osgeo.org/mailman/listinfo/tosprint
* IRC chat during the event: #tosprint Server: irc.freenode.net
* Gitter channel: https://gitter.im/OSGeo/Sprint

== Sponsoring ==

The Open Source Geospatial Foundation (OSGeo) has a long tradition of organizing code sprints for developers of Open Source GIS software.
(https://wiki.osgeo.org/wiki/Category:Code_Sprints).

An international community/code sprint for OSGeo will take place Nov 17-19, 2020.

We expect about 80 developers from all over the world to come from various [https://www.osgeo.org/, OSGeo] projects. Whether desktop application, geospatial library, metadata catalog or web mapping: be sure to find products in the list that you use. The sprint is also an opportunity for your developers to meet with the core developers of the projects, get a deeper insight into the software and participate in the development.

This years' sprint will take place online.

In addition to the costs of providing the technical infrastructure and space, food and drink for the developers represents the main cost. Morning/afternoon meals and drinks during the day are planned. In addition, we hope to provide several evening meals and social events.

In order to cover these costs we would be overjoyed to accept offers of sponsorship!

What we can offer:
* Your logo on top of the [https://www.osgeo.org/events/OSGeo_Community_Sprint_2020/ community sprint website] as well as on all official documents used during the sprint
* Acknowledgement in all sprint related emails
* Our undying gratitude, which comes in handy when you least expect it (remember that feature you wanted?)

Our sponsorship levels:
* Gold: >= 2500 USD
* Silver: 1500 USD
* Bronze: 750 USD

So...
* get your company talking to the top project developers.
* encourage your GIS developers to take advantage of this opportunity, there is no better opportunity to learn!
* support the software you use - you benefit immediately.

Thank you very much!

Contact: To sponsor, please contact tzotsos@osgeo.org directly.

== Event Owner ==
* OSGeo Board

== Press Release ==

We are looking forward to the next OSGeo Code Sprint!

[[Category:Code_Sprints]]
[[Category:C Tribe Code Sprint]]

OSGeo Community Sprint 2019

2019-04-10T13:19:25Z

Wenzeslaus: /* Project Plans */

Annual Community Sprint comes to Minnesota in 2019!

Powered by [[Image:Osgeo-logo.png|250px|link=https://www.osgeo.org]]

== Purpose ==

Bring together project members to make decisions and tackle larger geospatial
problems as in previous years:
* [[OSGeo Code Sprint 2018|Bonn]] (2018)
* [[Daytona Beach Code Sprint 2017|Daytona_Beach]] (2017)
* [[Paris Code Sprint 2016|Paris]] (2016)
* [[Philadelphia Code Sprint 2015|Philadelphia]] (2015)
* [[Vienna Code Sprint 2014|Vienna]] (2014)
* [[Boston Code Sprint 2013|Boston]] (2013)
* [[IslandWood Code Sprint 2012|Island Wood (Seattle)]] (2012)
* [[Montreal Code Sprint 2011|Montreal]] (2011)
* [[New York Code Sprint 2010|New York City]] (2010)
* [[Toronto Code Sprint 2009|Toronto]] (2009)

== Sponsors ==

'''Sponsoring ''' Find out about [[OSGeo_Code_Sprint_2019#Sponsoring |Sponsoring the Event]].

; <big>Venue Sponsor</big>
{| border=0 cellspacing=15 cellpadding=10
||
[[File:Umn_logo.png|131px|University of Minnesota|link=https://twin-cities.umn.edu/]]
 
https://twin-cities.umn.edu/

|}

; <big>Gold Sponsors</big>
{| border=0 cellspacing=15 cellpadding=10

||
[[File:GC-Group logo.png|220px|GeoCue|link=http://www.geocue.com/]]
 
http://www.geocue.com/

||
[[File:safe-software-logo.png|220px|Safe Software|link=https://www.safe.com/]]
 
https://www.safe.com/
||
[[File:RIEGL.png|310px|RIEGL|link=http://www.riegl.com/]]
 
http://www.riegl.com/
|}

; <big>Silver Sponsors</big>
{| border=0 cellspacing=15 cellpadding=10
||
[[File:Hobulogo.png|160px|Hobu|link=https://hobu.co/]]
 
https://hobu.co/
||
[[File:Logo-EOX.png|160px|EOX IT Services GmbH|link=http://eox.at]]
 
[http://eox.at http://eox.at]
||
[[Image:Logo-TYDAC.png|160px|Tydac|link=http://www.tydac.ch/]]
 
[http://www.tydac.ch/ http://www.tydac.ch/]
||
[[File:Crunchydata.png|160px|CrunchyData||link=http://www.crunchydata.com/]]
 
[http://www.crunchydata.com/ http://www.crunchydata.com/]
|}

; <big>Bronze Sponsors</big>
{| border=0 cellspacing=15 cellpadding=10
||
[[File:CoordinateSolutions_TRANS.png|210px|link=http://www.coordinatesolutions.com/]]
 
[http://www.coordinatesolutions.com/ http://www.coordinatesolutions.com/]
||
[[File:sharedgeo_logo.png|170px|link=https://www.sharedgeo.org/]]
 
[https://www.sharedgeo.org/ https://www.sharedgeo.org/]
||
[[File:Greenwood_logo.png|210px|link=https://greenwoodmap.com/]]
 
[https://greenwoodmap.com/ https://greenwoodmap.com/]
|}
{| border=0 cellspacing=15 cellpadding=10
||
[[File:Azavea-logo.png|190px|link=https://www.azavea.com/]]
 
[https://www.azavea.com/ https://www.azavea.com/]
||
[[File:Bh-logo.jpg|320px|link=https://www.bhinc.com/]]
 
[https://www.bhinc.com/ https://www.bhinc.com/]
||
[[File:Logo-extensis.png|190px|link=https://www.extensis.com/]]
 
[https://www.extensis.com/ https://www.extensis.com/]
|}

== Dates and Times ==

* Date: May 14-17 (4 days)
* Time: 8:30am to 4:30pm each day

== Other Events from January to May 2019 ==

* ''OSGeo's 13th birthday Feb 4''
* ''[http://2019.foss4g-na.org/ FOSS4G-NA 2019], April 16-19 in San Diego, CA''
* ''please add your event''

== Location ==

* University of Minnesota - Twin Cities

=== Coding Venue ===
* Wilson Research Collaboration Studio: https://www.lib.umn.edu/wilsonstudio
* Wilson Library, West Bank
* [https://www.openstreetmap.org/#map=19/44.97095/-93.24392| OpenStreetMap]

=== Accommodations ===
Several hotels are within walking distance of the venue. Here are a few options:
{|border=1
|-
| '''Hotel Name''' || '''Price Range (USD)''' || '''Distance''' || '''Notes'''
|-
| [https://www.marriott.com/hotels/travel/mspdc-courtyard-minneapolis-downtown/?scid=bb1a189a-fec3-4d19-a255-54ba596febe2 Courtyard by Marriott Minneapolis] || 175$+ || .5 mile || Walking distance to Wilson Library, University Campus
|-
| [https://www.graduatehotels.com/minneapolis/ Graduate Minneapolis] || 185$+ || 1.9 miles || On University Campus and Light Rail transportation
|-
| [https://hamptoninn3.hilton.com/en/hotels/minnesota/hampton-inn-and-suites-minneapolis-university-area-MSPUAHX/index.html Hampton Inn & Suites Minneapolis] || 152$+ || 2.2 miles || On Light Rail transportation
|}

=== How to get there ===

'''Flights''' - [https://www.mspairport.com/flights-and-airlines Minneapolis-St. Paul International Airport (MSP)]

Sixteen commercial passenger airlines service the Minneapolis-St. Paul International Airport (MSP); 11 are located at Terminal 1 - Lindbergh and 5 are located at the Terminal 2 - Humphrey.

'''Light Rail Transit''' - [https://www.mspairport.com/directions/ground-transportation/light-rail-transit Light rail transit (LRT)] trains stop at both Terminal 1-Lindbergh and Terminal 2-Humphrey and connect travelers to 17 other destinations, including downtown Minneapolis to the north and Mall of America to the south.

[https://www.metrotransit.org/blue-line-map Metro Transit Map of LRT Stations] shows the light rail stops; take the Blue Line to the Cedar-Riverside stop for the Wilson Library, University of Minnesota venue.

== Schedule ==
* breakfast each day around 8:30am
* lunch every day around 12:30pm

== Social Events ==
* Monday (5/13) - Welcome Gathering at [http://www.townhallbrewery.com/ Town Hall Brewery] (time TBD)
* Tuesday (5/14) - Pizza at [http://surlybrewing.com/ Surly Brewing] (time TBD)
* Wednesday (5/15) - Free Portrait Photos (10:00am - 3:00pm) by [https://www.billadams.photo/ Bill Adams Photography]
* Wednesday (5/15) - Food, beverages and lawn bowling at [https://britspub.com/ Brits Pub] (time TBD)
* Thursday (5/16) - Appetizers and beverages with MN GIS/LIS at [http://republicmn.com/ Republic] (time TBD)

== Project Plans ==
(i.e what do you wish/want/plan to work on during the sprint ?)

* '''MapServer''':
** MapServer 8.0 Roadmap
** new Proj.4 API support
* '''GRASS GIS''':
** re-working PDAL connection
** improving OpenDroneMap/WebODM connection
** finalizing Python 3 support
** Git and GitHub best practices
* add your project

== Participants ==

Please add your name and the projects you are planning to sprint and note the likeliness of your attendance.

{| border="1" cellpadding="2" class="wikitable sortable"
!width="25"|No
!width="250"|Name
!width="100"|Country
!width="250"|Email
!width="250"|Organisation
!width="250"|Projects
!width="25"|Sun
!width="25"|Mon
!width="25"|Tue
!width="25"|Wed
!width="25"|Thu
!width="25"|Fri
!width="25"|Sat
!width="25"|Sun
!width="60"|Likelihood
!width="30"|Food Restrictions
|-
| 1 ||[[Steve Lime]] || US || steve.lime@state.mn.us || State of Minnesota || MapServer || x || x || x || x || x || x || x || x || Certain ||
|-
| 2||[[Howard Butler]] || US || howard@hobu.co || Hobu, Inc. || PROJ, GDAL, PDAL || || x || x || x || x || x || x || || Certain ||
|-
| 3||[[Connor Manning]] || US || connor@hobu.co || Hobu, Inc. || Entinwe, PDAL || || x || x || x || x || x || x || || Certain ||
|-
| 4||[[User:jimk|Jim Klassen]] || US || jklassen@sharedgeo.org || SharedGeo || MapServer, GDAL, GeoMoose || || x || x || x || x || x || x || || Certain ||
|-
| 5||[[User:blammo|Bob Basques]] || US || bbasques@sharedgeo.org || SharedGeo || MapServer, GeoMoose || x || x || x || x || x || x || x || || Certain ||
|-
| 6||[[User:pwramsey3|Paul Ramsey]] || CA || pramsey@cleverelephant.ca || Crunchy Data || PostGIS, GEOS || || || x || x || x || x || || || Certain ||
|-
| 7||[[User:theduckylittle|Dan "Ducky" Little]] || US || theduckylittle@gmail.com || || MapServer, GeoMoose || || x || x || x || x || x || x || || Certain || No pref
|-
| 8||[[User:Dmorissette|Daniel Morissette]] || CA || dmorissette@mapgears.com || Mapgears || MapServer, GDAL/OGR || || x || x || x || x || x || x || || Certain ||
|-
| 9 ||[[Kari Geurts]] || US || kari.geurts@state.mn.us || State of Minnesota || || x || x || x || x || x || x || x || x || Certain ||
|-
| 10 ||[[Even Rouault]] || France || even.rouault at spatialys.com || Spatialys || GDAL/OGR, PROJ, Mapserver || || x || x || x || x || x || || || Certain ||
|-
| 11 ||[[Piero Toffanin]] || US || pt at masseranolabs.com || MasseranoLabs || OpenDroneMap || || || x || x || x || x || || || Certain ||
|-
| 12 ||[[User:Schpidi|Stephan Meißl]] || AT || stephan.meissl@eox.at || EOX || MapServer, EOxServer || || x || x || x || x || || || || 50% ||
|-
| 13 ||[[User:normanb|Norman Barker]] || US || norman@tiledb.io || TileDB || GDAL || || || x || x || x || x || || || Certain ||
|-
| 14 ||[[User:kirk|Kirk McKelvey]] || US || kmckelvey@extensis.com || Extensis (was LizardTech) || || || || x || x || x || x || || || Very Likely ||
|-
| 15 ||Martin Davis || CA || martin.davis@crunchydata.ca || Crunchy Data || PostGIS, GEOS || || || x || x || x || x || || || Certain ||
|-
| 16 ||Jody Garnett || CA || jody.garnett@gmail.com || OSGeo || || || || x || x || x || x || || || Certain ||
|-
| 17 ||Andrew Bell || US || andew@hobu.co || Hobu || || || || x || x || x || x || || || Certain ||
|-
| 18 ||[[User:greenwood|Rich Greenwood]] || US || rich@greenwoodmap.com || Greenwood Mapping, Inc. || || || || x || x || x || x || || || Certain || veg
|-
| 19 ||[[Michael Smith]] || US || michael.smith.erdc@gmail.com || US Army Corps || PDAL,Proj,GDAL,MapServer || || x || x || x || x || x || x || || Certain ||
|-
| 20 ||[[User:Jhughes|Jim Hughes]] || US || jhughes@ccri.com || CCRi || GeoMesa, JTS, GeoTools, GeoServer || || x || x || x || x || x || x || || Certain ||
|-
| 21 ||[[Tom Kralidis]] || CA|| tomkralidis at gmail.com || self || pycsw, OWSLib, pygeoapi, GeoHealthCheck, MapServer, other geopython projects || || x || x || x || x || x || || || Certain ||
|-
| 22 ||[[David Bitner]] || US|| bitner@dbspatial.com || SolSpec || OpenDroneMap, Serverless Geospatial Projects || || x || x || x || x || x || || || Very Likely ||
|-
| 23 ||[[Nathan Casler]] || US|| ncasler@solspec.solutions || SolSpec || OpenDroneMap || || x || x || x || x || x || || || Very Likely ||
|-
| 24 ||[[Dan Baston]] || US|| dbaston@gmail.com || ISciences LLC || GEOS et al || || || x || x || x || x || || || Certain ||
|-
| 25 ||[[Jérôme Boué]] || FR|| jbo-ads at laposte.net || Airbus / Akka || MapServer, MapCache || || x || x || x || x || x || || || Certain ||
|-
| 26 ||[[Dominik Nussbaumer ]] || AT || dnussbaumer@riegl.com || RIEGL || PDAL, PROJ, GDAL || || x || x || x || x || x || || || Certain ||
|-
| 27 || [[User:jjesus|Jorge de Jesus ]] || NL || jorge.dejesus@geocat.net || GeoCat B.V || Geohealthcheck, pygeapi || || || || x || x || || || || Remotely ||
|-
| 28 || Paul van Genuchten || NL || paul.vangenuchten@geocat.net || GeoCat B.V || Geonetwork, Geohealthcheck, pygeoapi || || || || x || x || || || || Remotely ||
|-
| 29 || Stephen Mather || US || mather.stephen@gmail.com || Clevland Metroparks || OpenDroneMap, PDAL, PostGIS || || ||x || x || x || x || || || Very Likely ||
|-
| 30 || India Johnson || US || mather.stephen@gmail.com || Clevland Metroparks || OpenDroneMap, PDAL, PostGIS || || ||x || x || x || x || || || Very Likely ||
|-
| 31||[[Mateusz Loskot]] || PL/UK || mateusz@loskot.net || Cadcorp, UK || GDAL, GEOS, PDAL, PostGIS || || x || x || x || x || x || || || Certain || veg pref
|-
| 32|| [[User:Wenzeslaus|Vaclav (Vashek) Petras]]|| US/CZ || wenzeslaus@gmail.com || NC State University || GRASS GIS || || || x || x || x || x || || || Certain ||
|-
| 33|| [[User:Annakrat|Anna Petrasova]] || US/CZ || kratochanna@gmail.com || NC State University || GRASS GIS || || || x || x || x || x || || || Certain ||
|-
|}

== Communication ==

* Please join the mailing list: https://lists.osgeo.org/mailman/listinfo/tosprint
* IRC chat during the event: #tosprint Server: irc.freenode.net

== Costs ==

Participants should plan for the following costs:

* Travel to Minneapolis/St. Paul
* Accommodation for x nights

== Individual preparation ==

* Bring your own laptop
* Bring [https://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] if needed (photo: [https://en.wikipedia.org/wiki/File:B_plug.jpg]). See also http://www.power-plugs-sockets.com/
* Install Git and compiler tools, and come with a working development environment

== Sponsoring ==

The Open Source Geospatial Foundation (OSGeo) has a long tradition of organizing code sprints for developers of Open Source GIS software.
(https://wiki.osgeo.org/wiki/Category:Code_Sprints).

An international community/code sprint for OSGeo will take place May 14-17, 2019.

We expect about 50 developers from all over the world to come from various [https://www.osgeo.org/, OSGeo] projects. Whether desktop application, geospatial library, metadata catalog or web mapping: be sure to find products in the list that you use. The sprint is also an opportunity for your developers to meet with the core developers of the projects, get a deeper insight into the software and participate in the development.

This years' sprint will take place at the University of Minnesota - Twin Cities in Minneapolis and will be hosted by [https://research.umn.edu/units/uspatial, U-Spatial] and organized by [https://www.sharedgeo.org/, SharedGeo] and members of the local OSGeo user group (TCMUG).

In addition to the costs of providing the technical infrastructure and space, food and drink for the developers represents the main cost. Morning/afternoon meals and drinks during the day are planned. In addition, we hope to provide several evening meals and social events.

In order to cover these costs we would be overjoyed to accept offers of sponsorship!

What we can offer:
* Your logo on top of the [https://www.osgeo.org/events/OSGeo_Community_Sprint_2019/ community sprint website] as well as on all official documents used during the sprint
* Acknowledgement in all sprint related emails
* Our undying gratitude, which comes in handy when you least expect it (remember that feature you wanted?)

Our sponsorship levels:
* Gold: >= 2500 USD
* Silver: 1500 USD
* Bronze: 750 USD

So...
* get your company talking to the top project developers.
* encourage your GIS developers to take advantage of this opportunity, there is no better opportunity to learn!
* support the software you use - you benefit immediately.

Thank you very much!

Contact: To sponsor, please contact tosprint@lists.osgeo.org directly.

== Event Owner ==
* SharedGeo
* U-Spatial
* [[User:Sdlime|Steve Lime]]
* [[User:Kaguerts|Kari Geurts]]

== Press Release ==

We are looking forward to the next OSGeo Code Sprint!
[[Category:Code Sprints]]
[[Category:C Tribe Code Sprint]]

OSGeo Community Sprint 2019

2019-04-09T18:59:14Z

Wenzeslaus: /* Project Plans */ add GRASS GIS

Annual Community Sprint comes to Minnesota in 2019!

Powered by [[Image:Osgeo-logo.png|250px|link=https://www.osgeo.org]]

== Purpose ==

Bring together project members to make decisions and tackle larger geospatial
problems as in previous years:
* [[OSGeo Code Sprint 2018|Bonn]] (2018)
* [[Daytona Beach Code Sprint 2017|Daytona_Beach]] (2017)
* [[Paris Code Sprint 2016|Paris]] (2016)
* [[Philadelphia Code Sprint 2015|Philadelphia]] (2015)
* [[Vienna Code Sprint 2014|Vienna]] (2014)
* [[Boston Code Sprint 2013|Boston]] (2013)
* [[IslandWood Code Sprint 2012|Island Wood (Seattle)]] (2012)
* [[Montreal Code Sprint 2011|Montreal]] (2011)
* [[New York Code Sprint 2010|New York City]] (2010)
* [[Toronto Code Sprint 2009|Toronto]] (2009)

== Sponsors ==

'''Sponsoring ''' Find out about [[OSGeo_Code_Sprint_2019#Sponsoring |Sponsoring the Event]].

; <big>Venue Sponsor</big>
{| border=0 cellspacing=15 cellpadding=10
||
[[File:Umn_logo.png|131px|University of Minnesota|link=https://twin-cities.umn.edu/]]
 
https://twin-cities.umn.edu/

|}

; <big>Gold Sponsors</big>
{| border=0 cellspacing=15 cellpadding=10

||
[[File:GC-Group logo.png|220px|GeoCue|link=http://www.geocue.com/]]
 
http://www.geocue.com/

||
[[File:safe-software-logo.png|220px|Safe Software|link=https://www.safe.com/]]
 
https://www.safe.com/
||
[[File:RIEGL.png|310px|RIEGL|link=http://www.riegl.com/]]
 
http://www.riegl.com/
|}

; <big>Silver Sponsors</big>
{| border=0 cellspacing=15 cellpadding=10
||
[[File:Hobulogo.png|160px|Hobu|link=https://hobu.co/]]
 
https://hobu.co/
||
[[File:Logo-EOX.png|160px|EOX IT Services GmbH|link=http://eox.at]]
 
[http://eox.at http://eox.at]
||
[[Image:Logo-TYDAC.png|160px|Tydac|link=http://www.tydac.ch/]]
 
[http://www.tydac.ch/ http://www.tydac.ch/]
||
[[File:Crunchydata.png|160px|CrunchyData||link=http://www.crunchydata.com/]]
 
[http://www.crunchydata.com/ http://www.crunchydata.com/]
|}

; <big>Bronze Sponsors</big>
{| border=0 cellspacing=15 cellpadding=10
||
[[File:CoordinateSolutions_TRANS.png|210px|link=http://www.coordinatesolutions.com/]]
 
[http://www.coordinatesolutions.com/ http://www.coordinatesolutions.com/]
||
[[File:sharedgeo_logo.png|170px|link=https://www.sharedgeo.org/]]
 
[https://www.sharedgeo.org/ https://www.sharedgeo.org/]
||
[[File:Greenwood_logo.png|210px|link=https://greenwoodmap.com/]]
 
[https://greenwoodmap.com/ https://greenwoodmap.com/]
|}
{| border=0 cellspacing=15 cellpadding=10
||
[[File:Azavea-logo.png|190px|link=https://www.azavea.com/]]
 
[https://www.azavea.com/ https://www.azavea.com/]
||
[[File:Bh-logo.jpg|320px|link=https://www.bhinc.com/]]
 
[https://www.bhinc.com/ https://www.bhinc.com/]
||
[[File:Logo-extensis.png|190px|link=https://www.extensis.com/]]
 
[https://www.extensis.com/ https://www.extensis.com/]
|}

== Dates and Times ==

* Date: May 14-17 (4 days)
* Time: 8:30am to 4:30pm each day

== Other Events from January to May 2019 ==

* ''OSGeo's 13th birthday Feb 4''
* ''[http://2019.foss4g-na.org/ FOSS4G-NA 2019], April 16-19 in San Diego, CA''
* ''please add your event''

== Location ==

* University of Minnesota - Twin Cities

=== Coding Venue ===
* Wilson Research Collaboration Studio: https://www.lib.umn.edu/wilsonstudio
* Wilson Library, West Bank
* [https://www.openstreetmap.org/#map=19/44.97095/-93.24392| OpenStreetMap]

=== Accommodations ===
Several hotels are within walking distance of the venue. Here are a few options:
{|border=1
|-
| '''Hotel Name''' || '''Price Range (USD)''' || '''Distance''' || '''Notes'''
|-
| [https://www.marriott.com/hotels/travel/mspdc-courtyard-minneapolis-downtown/?scid=bb1a189a-fec3-4d19-a255-54ba596febe2 Courtyard by Marriott Minneapolis] || 175$+ || .5 mile || Walking distance to Wilson Library, University Campus
|-
| [https://www.graduatehotels.com/minneapolis/ Graduate Minneapolis] || 185$+ || 1.9 miles || On University Campus and Light Rail transportation
|-
| [https://hamptoninn3.hilton.com/en/hotels/minnesota/hampton-inn-and-suites-minneapolis-university-area-MSPUAHX/index.html Hampton Inn & Suites Minneapolis] || 152$+ || 2.2 miles || On Light Rail transportation
|}

=== How to get there ===

'''Flights''' - [https://www.mspairport.com/flights-and-airlines Minneapolis-St. Paul International Airport (MSP)]

Sixteen commercial passenger airlines service the Minneapolis-St. Paul International Airport (MSP); 11 are located at Terminal 1 - Lindbergh and 5 are located at the Terminal 2 - Humphrey.

'''Light Rail Transit''' - [https://www.mspairport.com/directions/ground-transportation/light-rail-transit Light rail transit (LRT)] trains stop at both Terminal 1-Lindbergh and Terminal 2-Humphrey and connect travelers to 17 other destinations, including downtown Minneapolis to the north and Mall of America to the south.

[https://www.metrotransit.org/blue-line-map Metro Transit Map of LRT Stations] shows the light rail stops; take the Blue Line to the Cedar-Riverside stop for the Wilson Library, University of Minnesota venue.

== Schedule ==
* breakfast each day around 8:30am
* lunch every day around 12:30pm

== Social Events ==
* Monday (5/13) - Welcome Gathering at [http://www.townhallbrewery.com/ Town Hall Brewery] (time TBD)
* Tuesday (5/14) - Pizza at [http://surlybrewing.com/ Surly Brewing] (time TBD)
* Wednesday (5/15) - Free Portrait Photos (10:00am - 3:00pm) by [https://www.billadams.photo/ Bill Adams Photography]
* Wednesday (5/15) - Food, beverages and lawn bowling at [https://britspub.com/ Brits Pub] (time TBD)

== Project Plans ==
(i.e what do you wish/want/plan to work on during the sprint ?)

* '''MapServer''':
** MapServer 8.0 Roadmap
** new Proj.4 API support
* '''GRASS GIS''':
** re-working PDAL connection
** finalizing Python 3 support
** Git and GitHub best practices
* add your project

== Participants ==

Please add your name and the projects you are planning to sprint and note the likeliness of your attendance.

{| border="1" cellpadding="2" class="wikitable sortable"
!width="25"|No
!width="250"|Name
!width="100"|Country
!width="250"|Email
!width="250"|Organisation
!width="250"|Projects
!width="25"|Sun
!width="25"|Mon
!width="25"|Tue
!width="25"|Wed
!width="25"|Thu
!width="25"|Fri
!width="25"|Sat
!width="25"|Sun
!width="60"|Likelihood
!width="30"|Food Restrictions
|-
| 1 ||[[Steve Lime]] || US || steve.lime@state.mn.us || State of Minnesota || MapServer || x || x || x || x || x || x || x || x || Certain ||
|-
| 2||[[Howard Butler]] || US || howard@hobu.co || Hobu, Inc. || PROJ, GDAL, PDAL || || x || x || x || x || x || x || || Certain ||
|-
| 3||[[Connor Manning]] || US || connor@hobu.co || Hobu, Inc. || Entinwe, PDAL || || x || x || x || x || x || x || || Certain ||
|-
| 4||[[User:jimk|Jim Klassen]] || US || jklassen@sharedgeo.org || SharedGeo || MapServer, GDAL, GeoMoose || || x || x || x || x || x || x || || Certain ||
|-
| 5||[[User:blammo|Bob Basques]] || US || bbasques@sharedgeo.org || SharedGeo || MapServer, GeoMoose || x || x || x || x || x || x || x || || Certain ||
|-
| 6||[[User:pwramsey3|Paul Ramsey]] || CA || pramsey@cleverelephant.ca || Crunchy Data || PostGIS, GEOS || || || x || x || x || x || || || Certain ||
|-
| 7||[[User:theduckylittle|Dan "Ducky" Little]] || US || theduckylittle@gmail.com || || MapServer, GeoMoose || || x || x || x || x || x || x || || Certain || No pref
|-
| 8||[[User:Dmorissette|Daniel Morissette]] || CA || dmorissette@mapgears.com || Mapgears || MapServer, GDAL/OGR || || x || x || x || x || x || x || || Certain ||
|-
| 9 ||[[Kari Geurts]] || US || kari.geurts@state.mn.us || State of Minnesota || || x || x || x || x || x || x || x || x || Certain ||
|-
| 10 ||[[Even Rouault]] || France || even.rouault at spatialys.com || Spatialys || GDAL/OGR, PROJ, Mapserver || || x || x || x || x || x || || || Certain ||
|-
| 11 ||[[Piero Toffanin]] || US || pt at masseranolabs.com || MasseranoLabs || OpenDroneMap || || || x || x || x || x || || || Certain ||
|-
| 12 ||[[User:Schpidi|Stephan Meißl]] || AT || stephan.meissl@eox.at || EOX || MapServer, EOxServer || || x || x || x || x || || || || 50% ||
|-
| 13 ||[[User:normanb|Norman Barker]] || US || norman@tiledb.io || TileDB || GDAL || || || x || x || x || x || || || Certain ||
|-
| 14 ||[[User:kirk|Kirk McKelvey]] || US || kmckelvey@extensis.com || Extensis (was LizardTech) || || || || x || x || x || x || || || Very Likely ||
|-
| 15 ||Martin Davis || CA || martin.davis@crunchydata.ca || Crunchy Data || PostGIS, GEOS || || || x || x || x || x || || || Certain ||
|-
| 16 ||Jody Garnett || CA || jody.garnett@gmail.com || OSGeo || || || || x || x || x || x || || || Certain ||
|-
| 17 ||Andrew Bell || US || andew@hobu.co || Hobu || || || || x || x || x || x || || || Certain ||
|-
| 18 ||[[User:greenwood|Rich Greenwood]] || US || rich@greenwoodmap.com || Greenwood Mapping, Inc. || || || || x || x || x || x || || || Certain || veg
|-
| 19 ||[[Michael Smith]] || US || michael.smith.erdc@gmail.com || US Army Corps || PDAL,Proj,GDAL,MapServer || || x || x || x || x || x || x || || Certain ||
|-
| 20 ||[[User:Jhughes|Jim Hughes]] || US || jhughes@ccri.com || CCRi || GeoMesa, JTS, GeoTools, GeoServer || || x || x || x || x || x || x || || Certain ||
|-
| 21 ||[[Tom Kralidis]] || CA|| tomkralidis at gmail.com || self || pycsw, OWSLib, pygeoapi, GeoHealthCheck, MapServer, other geopython projects || || x || x || x || x || x || || || Certain ||
|-
| 22 ||[[David Bitner]] || US|| bitner@dbspatial.com || SolSpec || OpenDroneMap, Serverless Geospatial Projects || || x || x || x || x || x || || || Very Likely ||
|-
| 23 ||[[Nathan Casler]] || US|| ncasler@solspec.solutions || SolSpec || OpenDroneMap || || x || x || x || x || x || || || Very Likely ||
|-
| 24 ||[[Dan Baston]] || US|| dbaston@gmail.com || ISciences LLC || GEOS et al || || || x || x || x || x || || || Certain ||
|-
| 25 ||[[Jérôme Boué]] || FR|| jbo-ads at laposte.net || Airbus / Akka || MapServer, MapCache || || x || x || x || x || x || || || Certain ||
|-
| 26 ||[[Dominik Nussbaumer ]] || AT || dnussbaumer@riegl.com || RIEGL || PDAL, PROJ, GDAL || || x || x || x || x || x || || || Certain ||
|-
| 27 || [[User:jjesus|Jorge de Jesus ]] || NL || jorge.dejesus@geocat.net || GeoCat B.V || Geohealthcheck, pygeapi || || || || x || x || || || || Remotely ||
|-
| 28 || Paul van Genuchten || NL || paul.vangenuchten@geocat.net || GeoCat B.V || Geonetwork, Geohealthcheck, pygeoapi || || || || x || x || || || || Remotely ||
|-
| 29 || Stephen Mather || US || mather.stephen@gmail.com || Clevland Metroparks || OpenDroneMap, PDAL, PostGIS || || ||x || x || x || x || || || Very Likely ||
|-
| 30 || India Johnson || US || mather.stephen@gmail.com || Clevland Metroparks || OpenDroneMap, PDAL, PostGIS || || ||x || x || x || x || || || Very Likely ||
|-
| 31||[[Mateusz Loskot]] || PL/UK || mateusz@loskot.net || Cadcorp, UK || GDAL, GEOS, PDAL, PostGIS || || x || x || x || x || x || || || Certain || veg pref
|-
| 32|| [[User:Wenzeslaus|Vaclav (Vashek) Petras]]|| US/CZ || wenzeslaus@gmail.com || NC State University || GRASS GIS || || || x || x || x || x || || || Certain ||
|-
| 33|| [[User:Annakrat|Anna Petrasova]] || US/CZ || kratochanna@gmail.com || NC State University || GRASS GIS || || || x || x || x || x || || || Certain ||
|-
|}

== Communication ==

* Please join the mailing list: https://lists.osgeo.org/mailman/listinfo/tosprint
* IRC chat during the event: #tosprint Server: irc.freenode.net

== Costs ==

Participants should plan for the following costs:

* Travel to Minneapolis/St. Paul
* Accommodation for x nights

== Individual preparation ==

* Bring your own laptop
* Bring [https://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] if needed (photo: [https://en.wikipedia.org/wiki/File:B_plug.jpg]). See also http://www.power-plugs-sockets.com/
* Install Git and compiler tools, and come with a working development environment

== Sponsoring ==

The Open Source Geospatial Foundation (OSGeo) has a long tradition of organizing code sprints for developers of Open Source GIS software.
(https://wiki.osgeo.org/wiki/Category:Code_Sprints).

An international community/code sprint for OSGeo will take place May 14-17, 2019.

We expect about 50 developers from all over the world to come from various [https://www.osgeo.org/, OSGeo] projects. Whether desktop application, geospatial library, metadata catalog or web mapping: be sure to find products in the list that you use. The sprint is also an opportunity for your developers to meet with the core developers of the projects, get a deeper insight into the software and participate in the development.

This years' sprint will take place at the University of Minnesota - Twin Cities in Minneapolis and will be hosted by [https://research.umn.edu/units/uspatial, U-Spatial] and organized by [https://www.sharedgeo.org/, SharedGeo] and members of the local OSGeo user group (TCMUG).

In addition to the costs of providing the technical infrastructure and space, food and drink for the developers represents the main cost. Morning/afternoon meals and drinks during the day are planned. In addition, we hope to provide several evening meals and social events.

In order to cover these costs we would be overjoyed to accept offers of sponsorship!

What we can offer:
* Your logo on top of the [https://www.osgeo.org/events/OSGeo_Community_Sprint_2019/ community sprint website] as well as on all official documents used during the sprint
* Acknowledgement in all sprint related emails
* Our undying gratitude, which comes in handy when you least expect it (remember that feature you wanted?)

Our sponsorship levels:
* Gold: >= 2500 USD
* Silver: 1500 USD
* Bronze: 750 USD

So...
* get your company talking to the top project developers.
* encourage your GIS developers to take advantage of this opportunity, there is no better opportunity to learn!
* support the software you use - you benefit immediately.

Thank you very much!

Contact: To sponsor, please contact tosprint@lists.osgeo.org directly.

== Event Owner ==
* SharedGeo
* U-Spatial
* [[User:Sdlime|Steve Lime]]
* [[User:Kaguerts|Kari Geurts]]

== Press Release ==

We are looking forward to the next OSGeo Code Sprint!
[[Category:Code Sprints]]
[[Category:C Tribe Code Sprint]]

OSGeo Community Sprint 2019

2019-04-09T18:56:58Z

Wenzeslaus: /* Participants */

Annual Community Sprint comes to Minnesota in 2019!

Powered by [[Image:Osgeo-logo.png|250px|link=https://www.osgeo.org]]

== Purpose ==

Bring together project members to make decisions and tackle larger geospatial
problems as in previous years:
* [[OSGeo Code Sprint 2018|Bonn]] (2018)
* [[Daytona Beach Code Sprint 2017|Daytona_Beach]] (2017)
* [[Paris Code Sprint 2016|Paris]] (2016)
* [[Philadelphia Code Sprint 2015|Philadelphia]] (2015)
* [[Vienna Code Sprint 2014|Vienna]] (2014)
* [[Boston Code Sprint 2013|Boston]] (2013)
* [[IslandWood Code Sprint 2012|Island Wood (Seattle)]] (2012)
* [[Montreal Code Sprint 2011|Montreal]] (2011)
* [[New York Code Sprint 2010|New York City]] (2010)
* [[Toronto Code Sprint 2009|Toronto]] (2009)

== Sponsors ==

'''Sponsoring ''' Find out about [[OSGeo_Code_Sprint_2019#Sponsoring |Sponsoring the Event]].

; <big>Venue Sponsor</big>
{| border=0 cellspacing=15 cellpadding=10
||
[[File:Umn_logo.png|131px|University of Minnesota|link=https://twin-cities.umn.edu/]]
 
https://twin-cities.umn.edu/

|}

; <big>Gold Sponsors</big>
{| border=0 cellspacing=15 cellpadding=10

||
[[File:GC-Group logo.png|220px|GeoCue|link=http://www.geocue.com/]]
 
http://www.geocue.com/

||
[[File:safe-software-logo.png|220px|Safe Software|link=https://www.safe.com/]]
 
https://www.safe.com/
||
[[File:RIEGL.png|310px|RIEGL|link=http://www.riegl.com/]]
 
http://www.riegl.com/
|}

; <big>Silver Sponsors</big>
{| border=0 cellspacing=15 cellpadding=10
||
[[File:Hobulogo.png|160px|Hobu|link=https://hobu.co/]]
 
https://hobu.co/
||
[[File:Logo-EOX.png|160px|EOX IT Services GmbH|link=http://eox.at]]
 
[http://eox.at http://eox.at]
||
[[Image:Logo-TYDAC.png|160px|Tydac|link=http://www.tydac.ch/]]
 
[http://www.tydac.ch/ http://www.tydac.ch/]
||
[[File:Crunchydata.png|160px|CrunchyData||link=http://www.crunchydata.com/]]
 
[http://www.crunchydata.com/ http://www.crunchydata.com/]
|}

; <big>Bronze Sponsors</big>
{| border=0 cellspacing=15 cellpadding=10
||
[[File:CoordinateSolutions_TRANS.png|210px|link=http://www.coordinatesolutions.com/]]
 
[http://www.coordinatesolutions.com/ http://www.coordinatesolutions.com/]
||
[[File:sharedgeo_logo.png|170px|link=https://www.sharedgeo.org/]]
 
[https://www.sharedgeo.org/ https://www.sharedgeo.org/]
||
[[File:Greenwood_logo.png|210px|link=https://greenwoodmap.com/]]
 
[https://greenwoodmap.com/ https://greenwoodmap.com/]
|}
{| border=0 cellspacing=15 cellpadding=10
||
[[File:Azavea-logo.png|190px|link=https://www.azavea.com/]]
 
[https://www.azavea.com/ https://www.azavea.com/]
||
[[File:Bh-logo.jpg|320px|link=https://www.bhinc.com/]]
 
[https://www.bhinc.com/ https://www.bhinc.com/]
||
[[File:Logo-extensis.png|190px|link=https://www.extensis.com/]]
 
[https://www.extensis.com/ https://www.extensis.com/]
|}

== Dates and Times ==

* Date: May 14-17 (4 days)
* Time: 8:30am to 4:30pm each day

== Other Events from January to May 2019 ==

* ''OSGeo's 13th birthday Feb 4''
* ''[http://2019.foss4g-na.org/ FOSS4G-NA 2019], April 16-19 in San Diego, CA''
* ''please add your event''

== Location ==

* University of Minnesota - Twin Cities

=== Coding Venue ===
* Wilson Research Collaboration Studio: https://www.lib.umn.edu/wilsonstudio
* Wilson Library, West Bank
* [https://www.openstreetmap.org/#map=19/44.97095/-93.24392| OpenStreetMap]

=== Accommodations ===
Several hotels are within walking distance of the venue. Here are a few options:
{|border=1
|-
| '''Hotel Name''' || '''Price Range (USD)''' || '''Distance''' || '''Notes'''
|-
| [https://www.marriott.com/hotels/travel/mspdc-courtyard-minneapolis-downtown/?scid=bb1a189a-fec3-4d19-a255-54ba596febe2 Courtyard by Marriott Minneapolis] || 175$+ || .5 mile || Walking distance to Wilson Library, University Campus
|-
| [https://www.graduatehotels.com/minneapolis/ Graduate Minneapolis] || 185$+ || 1.9 miles || On University Campus and Light Rail transportation
|-
| [https://hamptoninn3.hilton.com/en/hotels/minnesota/hampton-inn-and-suites-minneapolis-university-area-MSPUAHX/index.html Hampton Inn & Suites Minneapolis] || 152$+ || 2.2 miles || On Light Rail transportation
|}

=== How to get there ===

'''Flights''' - [https://www.mspairport.com/flights-and-airlines Minneapolis-St. Paul International Airport (MSP)]

Sixteen commercial passenger airlines service the Minneapolis-St. Paul International Airport (MSP); 11 are located at Terminal 1 - Lindbergh and 5 are located at the Terminal 2 - Humphrey.

'''Light Rail Transit''' - [https://www.mspairport.com/directions/ground-transportation/light-rail-transit Light rail transit (LRT)] trains stop at both Terminal 1-Lindbergh and Terminal 2-Humphrey and connect travelers to 17 other destinations, including downtown Minneapolis to the north and Mall of America to the south.

[https://www.metrotransit.org/blue-line-map Metro Transit Map of LRT Stations] shows the light rail stops; take the Blue Line to the Cedar-Riverside stop for the Wilson Library, University of Minnesota venue.

== Schedule ==
* breakfast each day around 8:30am
* lunch every day around 12:30pm

== Social Events ==
* Monday (5/13) - Welcome Gathering at [http://www.townhallbrewery.com/ Town Hall Brewery] (time TBD)
* Tuesday (5/14) - Pizza at [http://surlybrewing.com/ Surly Brewing] (time TBD)
* Wednesday (5/15) - Free Portrait Photos (10:00am - 3:00pm) by [https://www.billadams.photo/ Bill Adams Photography]
* Wednesday (5/15) - Food, beverages and lawn bowling at [https://britspub.com/ Brits Pub] (time TBD)

== Project Plans ==
(i.e what do you wish/want/plan to work on during the sprint ?)

* '''MapServer''':
** MapServer 8.0 Roadmap
** new Proj.4 API support
* add your project

== Participants ==

Please add your name and the projects you are planning to sprint and note the likeliness of your attendance.

{| border="1" cellpadding="2" class="wikitable sortable"
!width="25"|No
!width="250"|Name
!width="100"|Country
!width="250"|Email
!width="250"|Organisation
!width="250"|Projects
!width="25"|Sun
!width="25"|Mon
!width="25"|Tue
!width="25"|Wed
!width="25"|Thu
!width="25"|Fri
!width="25"|Sat
!width="25"|Sun
!width="60"|Likelihood
!width="30"|Food Restrictions
|-
| 1 ||[[Steve Lime]] || US || steve.lime@state.mn.us || State of Minnesota || MapServer || x || x || x || x || x || x || x || x || Certain ||
|-
| 2||[[Howard Butler]] || US || howard@hobu.co || Hobu, Inc. || PROJ, GDAL, PDAL || || x || x || x || x || x || x || || Certain ||
|-
| 3||[[Connor Manning]] || US || connor@hobu.co || Hobu, Inc. || Entinwe, PDAL || || x || x || x || x || x || x || || Certain ||
|-
| 4||[[User:jimk|Jim Klassen]] || US || jklassen@sharedgeo.org || SharedGeo || MapServer, GDAL, GeoMoose || || x || x || x || x || x || x || || Certain ||
|-
| 5||[[User:blammo|Bob Basques]] || US || bbasques@sharedgeo.org || SharedGeo || MapServer, GeoMoose || x || x || x || x || x || x || x || || Certain ||
|-
| 6||[[User:pwramsey3|Paul Ramsey]] || CA || pramsey@cleverelephant.ca || Crunchy Data || PostGIS, GEOS || || || x || x || x || x || || || Certain ||
|-
| 7||[[User:theduckylittle|Dan "Ducky" Little]] || US || theduckylittle@gmail.com || || MapServer, GeoMoose || || x || x || x || x || x || x || || Certain || No pref
|-
| 8||[[User:Dmorissette|Daniel Morissette]] || CA || dmorissette@mapgears.com || Mapgears || MapServer, GDAL/OGR || || x || x || x || x || x || x || || Certain ||
|-
| 9 ||[[Kari Geurts]] || US || kari.geurts@state.mn.us || State of Minnesota || || x || x || x || x || x || x || x || x || Certain ||
|-
| 10 ||[[Even Rouault]] || France || even.rouault at spatialys.com || Spatialys || GDAL/OGR, PROJ, Mapserver || || x || x || x || x || x || || || Certain ||
|-
| 11 ||[[Piero Toffanin]] || US || pt at masseranolabs.com || MasseranoLabs || OpenDroneMap || || || x || x || x || x || || || Certain ||
|-
| 12 ||[[User:Schpidi|Stephan Meißl]] || AT || stephan.meissl@eox.at || EOX || MapServer, EOxServer || || x || x || x || x || || || || 50% ||
|-
| 13 ||[[User:normanb|Norman Barker]] || US || norman@tiledb.io || TileDB || GDAL || || || x || x || x || x || || || Certain ||
|-
| 14 ||[[User:kirk|Kirk McKelvey]] || US || kmckelvey@extensis.com || Extensis (was LizardTech) || || || || x || x || x || x || || || Very Likely ||
|-
| 15 ||Martin Davis || CA || martin.davis@crunchydata.ca || Crunchy Data || PostGIS, GEOS || || || x || x || x || x || || || Certain ||
|-
| 16 ||Jody Garnett || CA || jody.garnett@gmail.com || OSGeo || || || || x || x || x || x || || || Certain ||
|-
| 17 ||Andrew Bell || US || andew@hobu.co || Hobu || || || || x || x || x || x || || || Certain ||
|-
| 18 ||[[User:greenwood|Rich Greenwood]] || US || rich@greenwoodmap.com || Greenwood Mapping, Inc. || || || || x || x || x || x || || || Certain || veg
|-
| 19 ||[[Michael Smith]] || US || michael.smith.erdc@gmail.com || US Army Corps || PDAL,Proj,GDAL,MapServer || || x || x || x || x || x || x || || Certain ||
|-
| 20 ||[[User:Jhughes|Jim Hughes]] || US || jhughes@ccri.com || CCRi || GeoMesa, JTS, GeoTools, GeoServer || || x || x || x || x || x || x || || Certain ||
|-
| 21 ||[[Tom Kralidis]] || CA|| tomkralidis at gmail.com || self || pycsw, OWSLib, pygeoapi, GeoHealthCheck, MapServer, other geopython projects || || x || x || x || x || x || || || Certain ||
|-
| 22 ||[[David Bitner]] || US|| bitner@dbspatial.com || SolSpec || OpenDroneMap, Serverless Geospatial Projects || || x || x || x || x || x || || || Very Likely ||
|-
| 23 ||[[Nathan Casler]] || US|| ncasler@solspec.solutions || SolSpec || OpenDroneMap || || x || x || x || x || x || || || Very Likely ||
|-
| 24 ||[[Dan Baston]] || US|| dbaston@gmail.com || ISciences LLC || GEOS et al || || || x || x || x || x || || || Certain ||
|-
| 25 ||[[Jérôme Boué]] || FR|| jbo-ads at laposte.net || Airbus / Akka || MapServer, MapCache || || x || x || x || x || x || || || Certain ||
|-
| 26 ||[[Dominik Nussbaumer ]] || AT || dnussbaumer@riegl.com || RIEGL || PDAL, PROJ, GDAL || || x || x || x || x || x || || || Certain ||
|-
| 27 || [[User:jjesus|Jorge de Jesus ]] || NL || jorge.dejesus@geocat.net || GeoCat B.V || Geohealthcheck, pygeapi || || || || x || x || || || || Remotely ||
|-
| 28 || Paul van Genuchten || NL || paul.vangenuchten@geocat.net || GeoCat B.V || Geonetwork, Geohealthcheck, pygeoapi || || || || x || x || || || || Remotely ||
|-
| 29 || Stephen Mather || US || mather.stephen@gmail.com || Clevland Metroparks || OpenDroneMap, PDAL, PostGIS || || ||x || x || x || x || || || Very Likely ||
|-
| 30 || India Johnson || US || mather.stephen@gmail.com || Clevland Metroparks || OpenDroneMap, PDAL, PostGIS || || ||x || x || x || x || || || Very Likely ||
|-
| 31||[[Mateusz Loskot]] || PL/UK || mateusz@loskot.net || Cadcorp, UK || GDAL, GEOS, PDAL, PostGIS || || x || x || x || x || x || || || Certain || veg pref
|-
| 32|| [[User:Wenzeslaus|Vaclav (Vashek) Petras]]|| US/CZ || wenzeslaus@gmail.com || NC State University || GRASS GIS || || || x || x || x || x || || || Certain ||
|-
| 33|| [[User:Annakrat|Anna Petrasova]] || US/CZ || kratochanna@gmail.com || NC State University || GRASS GIS || || || x || x || x || x || || || Certain ||
|-
|}

== Communication ==

* Please join the mailing list: https://lists.osgeo.org/mailman/listinfo/tosprint
* IRC chat during the event: #tosprint Server: irc.freenode.net

== Costs ==

Participants should plan for the following costs:

* Travel to Minneapolis/St. Paul
* Accommodation for x nights

== Individual preparation ==

* Bring your own laptop
* Bring [https://en.wikipedia.org/wiki/Mains_electricity_by_country your power connector adapter] if needed (photo: [https://en.wikipedia.org/wiki/File:B_plug.jpg]). See also http://www.power-plugs-sockets.com/
* Install Git and compiler tools, and come with a working development environment

== Sponsoring ==

The Open Source Geospatial Foundation (OSGeo) has a long tradition of organizing code sprints for developers of Open Source GIS software.
(https://wiki.osgeo.org/wiki/Category:Code_Sprints).

An international community/code sprint for OSGeo will take place May 14-17, 2019.

We expect about 50 developers from all over the world to come from various [https://www.osgeo.org/, OSGeo] projects. Whether desktop application, geospatial library, metadata catalog or web mapping: be sure to find products in the list that you use. The sprint is also an opportunity for your developers to meet with the core developers of the projects, get a deeper insight into the software and participate in the development.

This years' sprint will take place at the University of Minnesota - Twin Cities in Minneapolis and will be hosted by [https://research.umn.edu/units/uspatial, U-Spatial] and organized by [https://www.sharedgeo.org/, SharedGeo] and members of the local OSGeo user group (TCMUG).

In addition to the costs of providing the technical infrastructure and space, food and drink for the developers represents the main cost. Morning/afternoon meals and drinks during the day are planned. In addition, we hope to provide several evening meals and social events.

In order to cover these costs we would be overjoyed to accept offers of sponsorship!

What we can offer:
* Your logo on top of the [https://www.osgeo.org/events/OSGeo_Community_Sprint_2019/ community sprint website] as well as on all official documents used during the sprint
* Acknowledgement in all sprint related emails
* Our undying gratitude, which comes in handy when you least expect it (remember that feature you wanted?)

Our sponsorship levels:
* Gold: >= 2500 USD
* Silver: 1500 USD
* Bronze: 750 USD

So...
* get your company talking to the top project developers.
* encourage your GIS developers to take advantage of this opportunity, there is no better opportunity to learn!
* support the software you use - you benefit immediately.

Thank you very much!

Contact: To sponsor, please contact tosprint@lists.osgeo.org directly.

== Event Owner ==
* SharedGeo
* U-Spatial
* [[User:Sdlime|Steve Lime]]
* [[User:Kaguerts|Kari Geurts]]

== Press Release ==

We are looking forward to the next OSGeo Code Sprint!
[[Category:Code Sprints]]
[[Category:C Tribe Code Sprint]]

User:Wenzeslaus

2018-08-02T01:34:00Z

Wenzeslaus:

{{OSGeo Member
|Name=Vaclav Petras
|JobTitle=Postdoctoral Researcher
|Company=North Carolina State University
|Country=USA
|State=NC
|City=Raleigh
|Coordinate=35.784811, -78.681698
|LocalChapter=North America
|Email=wenzeslaus gmail com
|SocialMedia=@vaclavpetras;
|Website=http://wenzeslaus.github.io/
|Languages=Czech; English;
}}
{{OSGeo Experience
|User=Yes
|Committee=No
|Board=No
|Coder=Yes
|Translate=No
|PSC=Yes
|ExBoard=No
|Charter=Yes
|Chair=No
|SolKatz=No
|Committer=Yes
}}
=== Vaclav Petras ===

* Member of [https://geospatial.ncsu.edu/geoforall/ NCSU GeoForAll Lab]
* Former member of [http://geomatics.fsv.cvut.cz/research/geoforall/ GeoForAll Lab at FCE CTU in Prague]
* [http://grass.osgeo.org/ GRASS GIS] user, developer (http://grasswiki.osgeo.org/wiki/User:Wenzeslaus) and PSC member
** participated in GSoC [https://trac.osgeo.org/grass/wiki/GSoC/2014/TestingFrameworkForGRASS 2014] as student and in GSoC 2016, 2017, and 2018 as a mentor
** development [https://www.openhub.net/accounts/wenzeslaus statistics]
*Previous location: Prague, Czech Republic

* Twitter: http://twitter.com/vaclavpetras
* LinkedIn: https://www.linkedin.com/in/vaclav-petras-a24a1b114/

;Profile last updated: August 2018

[[Category:OSGeo Advocate]]

User:Wenzeslaus

2018-08-02T01:30:59Z

Wenzeslaus: /* Vaclav Petras */

{{OSGeo Member
|Name=Vaclav Petras
|JobTitle=Postdoctoral Researcher
|Company=North Carolina State University
|Country=USA
|State=NC
|City=Raleigh
|Coordinate=35.784811, -78.681698
|LocalChapter=North America
|Email=wenzeslaus gmail com
|SocialMedia=@vaclavpetras;
|Website=http://wenzeslaus.github.io/
|Languages=Czech; English;
}}
{{OSGeo Experience
|User=Yes
|Committee=No
|Board=No
|Coder=Yes
|Translate=No
|PSC=Yes
|ExBoard=No
|Charter=Yes
|Chair=No
|SolKatz=No
|Committer=Yes
}}
=== Vaclav Petras ===

* Member of [https://geospatial.ncsu.edu/geoforall/ NCSU GeoForAll Lab]
* Former member of [http://geomatics.fsv.cvut.cz/research/geoforall/ GeoForAll Lab at FCE CTU in Prague]
* [http://grass.osgeo.org/ GRASS GIS] user, developer (http://grasswiki.osgeo.org/wiki/User:Wenzeslaus) and PSC member
** participated in GSoC [https://trac.osgeo.org/grass/wiki/GSoC/2014/TestingFrameworkForGRASS 2014] as student and in GSoC 2016, 2017, and 2018 as a mentor
** development [https://www.openhub.net/accounts/wenzeslaus statistics]
*Previous location: Prague, Czech Republic

;Profile last updated: August 2018

[[Category:OSGeo Advocate]]