OSGeo - User contributions [en]

OSGeo Budget 2023

2023-01-05T08:21:30Z

Kbevers: Added PROJ 2023 budget

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

Total Approved Budget for 2022: $213,346 USD

Total spending for 2022: TBD

Total Approved Budget for 2023: TBD

== OSGeo Board ==

OSGeo board operates according to our bylaws providing vision and direction for our foundation. The board has also taken on responsibility setting for an annual budget, building partner relationships, sponsorship program and code sprints.

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

Total Board Budget for 2022: $21,000 USD

Total Board spending for 2022: TBD

Total Board Budget for 2023: TBD

== OSGeo Committees ==

The following committees have been formed to fulfill out goals as an organization, each committee is provided a mandate, with the chair of the committee represented as an officer of our organization.

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

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! OSGeo Committees
! 2022 Approved [Requested]
! 2022 Actual
! 2023 Draft [Requested]
! Notes
|-
| SAC
| style="text-align:right;" | 32,550 [32,550]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| [[SAC:Budget#2022]], [[SAC:Budget#2023]]
|-
| OpenGeoScience
| style="text-align:right;" | 2,500 [3,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Please contact marketing committee for marketing materials (500$)
|-
| Conference
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| Marketing
| style="text-align:right;" | 7,500 [7,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|[[Marketing Committee Budget 2022]]. Extra 500$ for OpenGeoScience material.
|-
| GeoForAll
| style="text-align:right;" | 4,000 [4,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| style="text-align:left;" |$2000 for South American student event as requested by Sergio Acosta y Lara $2000 for Global GeoforAll competition and request by labs.
|-
| UN Committee
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| No UN challenge this year
|-
| Incubation Committee
| style="text-align:right;" | 6,000 [8,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|}

Total Committees Budget for 2022: $52,550 USD

Total Committees spending for 2022: TBD

Total Committees Budget for 2023: TBD

== OSGeo Initiatives ==

OSGeo initiatives have formed to pursue a specific short term, or long term goal. Initiatives maybe formed by a committee or the board as required. Initiatives are a great way to collaborate with projects, committees and partners.

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

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! OSGeo Initiatives
! 2022 Approved
! 2022 Actual
! 2023 Draft
! Notes
|-
| FOSS4G
| style="text-align:right;" | 66,796
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Seed money for 2022.
|-
| Local Chapters
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Managed by board, considering putting aside money to help establish local chapters (for logistics, legal advise, kickoff meetings rather than any sponsorship or direct funding)
|-
| GSoC
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Managed by board.
|-
| Travel Grant Program
| style="text-align:right;" | 15,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Managed by Conference Committee. FOSS4G 2022 asked for 10k in conference mailing list, 5k proposed by board for local events.
|-
| Events and Code Sprints
| style="text-align:right;" | 20,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Managed by the board. Funding to help organize OSGeo Code Sprint and other events (e.g. QGIS User Conference, PostGIS Code Sprint, GRASS GIS Community Sprint etc.) Board note: This budget reflects the 15,000 sponsorship we got for the postponed Athens Code Sprint.
|-
| Community Projects
| style="text-align:right;" | 5,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Managed by the board since community projects do not have an assigned officer to handle their budget. We have around 30 projects expected in 2022. Board note: Budgeted 300$ for each project. To be amended if we hit the ceiling of the budget.
|
|}

Total Initiatives Budget for 2022: $106,796 USD

Total Initiatives spending for 2022: TBD

Total Initiatives Budget for 2023: TBD

= Projects =

== OSGeo Projects ==

OSGeo Projects each have a project steering committee, the chair of which is acknowledged as a foundation officer with spending authority on behalf of their committee.

Notes:

* We have reached out (2022) to the projects mailing list.
* Board decided to assign a default budget of $500 for any project that has reported to the board within the year.
* Projects with a plan may of course ask for increased funding
* This is a budget, representing planned spending in 2022 - actual balance available to each PSC (from fundraising, donations and sponsorship) may be considered when planning.
* If a project did not respond (or runs into an unforeseen expense) please contact the board throughout the year as budgets can be amended

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! OSGeo Project
! 2022 Approved [Requested]
! 2022 Actual
! 2023 Draft [Requested]
! Notes
|-
| deegree
| style="text-align:right;" | 2,000 [2,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| https://github.com/deegree/deegree3/wiki/deegree-budget-2022
|-
| GDAL/OGR
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| 2021 spending includes Travis CI subscription.
|-
| GeoMOOSE
| style="text-align:right;" | 2,500 [2,500]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| https://github.com/geomoose/geomoose/wiki/PSC-Meeting-2021-10-15
|-
| GeoNetwork
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoNode
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GEOS
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoServer
| style="text-align:right;" | 3,000 [3,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| [[GeoServer Budget 2022]]
|-
| GeoTools
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GRASS GIS
| style="text-align:right;" | 4,000 [3964.49]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| [[GRASS GIS Budget 2022]]
|-
| gvSIG
| style="text-align:right;" | 5,000 [5,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD [5,000]
| [[GvSIG Budget 2023]]
|-
| Mapbender
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| MapServer
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| Marble
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Need to report to the board to get a budget
|-
| OpenLayers
| style="text-align:right;" | 3,000 [3,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| [[OpenLayers Budget 2022]]
|-
| OTB
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| OSGeoLive
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| PostGIS
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| PROJ
| style="text-align:right;" | 500
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| The project has previously never used it's allocated budget. That is expected to continue for now.
|-
| pycsw
| style="text-align:right;" | 2,500 [2,500]
| style="text-align:right;" | 0
| style="text-align:right;" | TBD [2,500]
| https://github.com/geopython/pycsw/wiki/OSGeo-Budget-2023
|-
| pygeoapi
| style="text-align:right;" | 300
| style="text-align:right;" | 0
| style="text-align:right;" | TBD [3,000]
| https://github.com/geopython/pygeoapi/wiki/OSGeo-Budget-2023
|-
| PyWPS
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| QGIS
| style="text-align:right;" | 5,000 [5,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| for website work https://www.qgis.org/en/_downloads/1545388ea396bf7e83de68df47f8cf0b/QGISBudget2022.pdf
|}

Total Projects Budget for 2022: $33,000 USD

Total Projects spending for 2022: TBD

Total Projects Budget for 2023: TBD

== Community Projects ==

Community projects act through the board as they do not have a project officer. Board approved $300 for each project (see Community Projects Initiative above)

Some guidance is offered by individual projects below.

Please note that this table records budget requests, not approved budgets. Community Projects can ask the Board for spending approval (since they do not have a Project Officer) from the approved Community Projects budget. Projects that are also in incubation can ask the Incubation Committee for spending approval from the Incubation Committee approved budget. See notes column for actual budget approval per project.

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! Community Project
! 2022 Approved [Requested]
! 2022 Actual
! 2023 Draft [Requested]
! Notes
|-
| pgRouting
| style="text-align:right;" | 300
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| 2022 Board note: 300 USD approved from Community Projects budget. For more budget the project has to ask incubation committee.
|-
| istSOS
| style="text-align:right;" | 300
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| 2022 Board note: 300 USD approved from Community Projects budget. For more budget the project has to ask incubation committee.
|-
|}

= Events =

== Community Events ==

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

* Supporting community building events is distinct from the development focused code-sprints below
* We are inviting community members to contact us about events (rather than try and adjust their event to fit into our code sprint guidelines)
* OSGeo is is focused on our outreach goals as an organization as such our primary contribution to events is free software and enthusiasm rather than finical, we use funding to enable our members rather than for sponsorship and visibility.
* Please note our [https://github.com/OSGeo/osgeo/blob/master/board/documents/osgeo_financial_guidance.pdf financial guidance document]

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

== Code Sprints ==

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

* Please note our [https://github.com/OSGeo/osgeo/blob/master/board/documents/osgeo_financial_guidance.pdf financial guidance document] ask for event details, budget and fundraising on your part.
* Out priority is to share the risk with organizers allowing access to funds early to book facilities as required
* Code sprint budget is structured carry funds from one event to the next allowing us to hold more code-sprints with a smaller annual budget.

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

= Approval and Amendments =

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

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

OSGeo Budget 2020

2020-01-13T11:22:54Z

Kbevers: Added PROJ budget

'''DRAFT'''

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

Total Approved Budget for 2019: $230,150 USD

Total Approved Budget for 2020: $TBD USD

== OSGeo Board ==

OSGeo board operates according to our bylaws providing vision and direction for our foundation. The board has also taken on responsibility setting for an annual budget, building partner relationships, sponsorship program and code sprints.

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

Total Board Budget for 2019: $29,000 USD

Total Board Budget for 2020: $TBD USD

== OSGeo Committees ==

The following committees have been formed to fulfill out goals as an organization, each committee is provided a mandate, with the chair of the committee represented as an officer of our organization.

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

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

Total Committees Budget for 2019: $76,450 USD

Total Committees Budget for 2020: $TBD USD

== OSGeo Initiatives ==

OSGeo initiatives have formed to pursue a specific short term, or long term goal. Initiatives maybe formed by a committee or the board as required. Initiatives are a great way to collaborate with projects, committees and partners.

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

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! OSGeo Initiatives
! 2019
! 2019 Actual
! 2020
! Notes
|-
| FOSS4G
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| Managed by Conference Committee. Seed money for 2020 will be allocated by the board when estimate numbers become available.
|-
| Local Chapters
| style="text-align:right;" | 5,000
| style="text-align:right;" | 2,000
| style="text-align:right;" | 0
| Managed by board, considering putting aside money to help establish local chapters (for logistics, legal advise, kickoff meetings rather than any sponsorship or direct funding)
|-
| GSoC
| style="text-align:right;" | 0
| style="text-align:right;" | 3,909
| style="text-align:right;" | 0
| Managed by board.
|-
| Travel Grant Program
| style="text-align:right;" | 25.000
| style="text-align:right;" | 14,813
| style="text-align:right;" | 25,000
| TGP, 50-60% for global event, rest for regional events. LOC's are expected to raise matching funding from sponsors or delegates and provide free conference passes.
|-
| Events and Code Sprints
| style="text-align:right;" | 15,000
| style="text-align:right;" | 4,087
| style="text-align:right;" | 0
| Managed by the board. Funding to help organize OSGeo Code Sprint and other events (e.g. QGIS User Conference, PostGIS Code Sprint, GRASS GIS Community Sprint etc.)
|-
| Community Projects
| style="text-align:right;" | 15,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| Managed by the board since community projects do not have an assigned officer to handle their budget. We have around 23-25 projects expected in 2020 (see list below). Budgeted 500$ for each project.
|}

Total Initiatives Budget for 2019: $60,000 USD

Total Initiatives Budget for 2020: $TBD USD

= Projects =

== OSGeo Projects ==

OSGeo Projects each have a project steering committee, the chair of which is acknowledged as a foundation officer with spending authority on behalf of their committee.

Notes:

* We have reached out (2019) to the projects mailing list with a default suggestion of 2000 for any project that responds
* Projects with a plan may of course ask for increased funding
* This is a budget, representing planned spending in 2020 - actual balance available to each PSC (from fundraising, donations and sponsorship) may be considered when planning.
* If a project did not respond (or runs into an unforeseen expense) please contact the board throughout the year as budgets can be amended

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! OSGeo Project
! 2019
! 2019 Actual
! 2020
! Notes
|-
| deegree
| style="text-align:right;" | 2,000
| style="text-align:right;" | 0
| style="text-align:right;" | 2,000
|
|-
| GDAL/OGR
| style="text-align:right;" | 5,000
| style="text-align:right;" | 3,765
| style="text-align:right;" | 2,000
|
|-
| GeoMOOSE
| style="text-align:right;" | 2,000
| style="text-align:right;" | 0
| style="text-align:right;" | 2,000
|
|-
| GeoNetwork
| style="text-align:right;" | 2,000
| style="text-align:right;" | 550
| style="text-align:right;" | 2,000
|
|-
| GeoNode
| style="text-align:right;" | 2,000
| style="text-align:right;" | 2,000
| style="text-align:right;" | 2,000
| [[GeoNode_Budget_2020]]
|-
| GEOS
| style="text-align:right;" | 1,000
| style="text-align:right;" | 0
| style="text-align:right;" | 2,000
|
|-
| GeoServer
| style="text-align:right;" | 7,000
| style="text-align:right;" | 7,000
| style="text-align:right;" | 5,000
| [[GeoServer Budget 2020]]
|-
| GeoTools
| style="text-align:right;" | 2,000
| style="text-align:right;" | 2,000
| style="text-align:right;" | 5,000
| [https://github.com/geotools/geotools/wiki/GeoTools-Budget-Request-2020 GeoTools Budget Request 2020]
|-
| GRASS GIS
| style="text-align:right;" | 9,000
| style="text-align:right;" | 1,728
| style="text-align:right;" | 9,000
| 6,000 to be shifted from 2019 to 2020, details at [https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2020 GRASS GIS Budget 2020]
|-
| gvSIG
| style="text-align:right;" | 5,000
| style="text-align:right;" | 3,000
| style="text-align:right;" | 5,000
| Details of the budget at [[GvSIG Budget 2020]]
|-
| Mapbender
| style="text-align:right;" | 2,000
| style="text-align:right;" | 1,691
| style="text-align:right;" | 2,000
| we are fine with the $ 2.000 for 2020 and we plan to use it for our Community Meeting and Marketing
|-
| MapServer
| style="text-align:right;" | 2,500
| style="text-align:right;" | 0
| style="text-align:right;" | 2,000
|
|-
| Marble
| style="text-align:right;" | 1,000
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| Has not reported to the board for 2019
|-
| OpenLayers
| style="text-align:right;" | 3,000
| style="text-align:right;" | 2,674
| style="text-align:right;" | 3,000
| [[OpenLayers_Budget_2020]]
|-
| OTB
| style="text-align:right;" | 2,000
| style="text-align:right;" | 0
| style="text-align:right;" | 2,000
|
|-
| OSGeoLive
| style="text-align:right;" | 2,000
| style="text-align:right;" | 0
| style="text-align:right;" | 2,000
|
|-
| PostGIS
| style="text-align:right;" | 3,000
| style="text-align:right;" | 0
| style="text-align:right;" | 2,000
|
|-
| PROJ
| style="text-align:right;" | N/A
| style="text-align:right;" | N/A
| style="text-align:right;" | 1,000
| [https://github.com/OSGeo/PROJ/wiki/Budget-2020 PROJ 2020 budget]
|-
| pycsw
| style="text-align:right;" | 3,000
| style="text-align:right;" | 3,074
| style="text-align:right;" | 3,200
| [[Pycsw_budget_2020]]
|-
| PyWPS
| style="text-align:right;" | 3,200
| style="text-align:right;" | 0
| style="text-align:right;" | 2,000
|
|-
| QGIS
| style="text-align:right;" | 8,000
| style="text-align:right;" | 11,000
| style="text-align:right;" | 10,000
| for QGIS bug fixing and WFS compliance work; the request for 2020 equals a "large sustaining membership" (€9,000 or $10,000 - equal to the larger QGIS user groups, like Germany, Denmark, Sweden and Switzerland)
|}

Total Projects Budget for 2019: $64,700 USD

Total Projects Budget for 2020: $TBD USD

== Community Projects ==

Community projects act through the board as they do not have a project officer. Board approved $TBD for each project (see Community Projects Initiative above)

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

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

* Oskari

Some guidance is offered by individual projects below:

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! Community Project
! 2019
! 2019 Actual
! 2020
! Notes
|-
| ZOO-Project
| style="text-align:right;"| up to 4,000 (need specific requests to board and incubation committee)
| style="text-align:right;" | 0
| style="text-align:right;" | 0
|
|-
| pgRouting
| style="text-align:right;"| up to 4,000 (need specific requests to board and incubation committee)
| style="text-align:right;" | 1,238
| style="text-align:right;" | 4,000
| For incubation expenses (code sprint to refine details)
|-
| istSOS
| style="text-align:right;" | up to 4,000 (need specific requests to board and incubation committee)
| style="text-align:right;" | 0
| style="text-align:right;" | 5,800
| see: [http://osgeo-org.1560.x6.nabble.com/istSOS-budget-2020-incubation-sprints-marketing-td5426010.html istSOS budget 2020]
|-
| OSGeo4W
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| style="text-align:right;" | 4,000
| proposed by the QGIS board for keeping OSGeo4W up to date
|-
| pygeoapi
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| style="text-align:right;" | 500
| stickers
|-
| GeoHealthCheck
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| style="text-align:right;" | 500
| stickers and logo
|-
|-
| OWSLib
| style="text-align:right;" | 0
| style="text-align:right;" | 0
| style="text-align:right;" | 1000
| attending OSGeo Code Sprint
|-
|}

= Events =

== Community Events ==

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

* Supporting community building events is distinct from the development focused code-sprints below
* We are inviting community members to contact us about events (rather than try and adjust their event to fit into our code sprint guidelines)
* OSGeo is is focused on our outreach goals as an organization as such our primary contribution to events is free software and enthusiasm rather than finical, we use funding to enable our members rather than for sponsorship and visibility.
* Previously we have had requests to fund a "community day" or "community sprints" as part a larger event as distinct from sponsorship, the have been funded to the best of our ability

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

== Code Sprints ==

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

* Please note our [[Code Sprint Guidelines]] ask for event details, budget and fundraising on your part.
* Out priority is to share the risk with organizers allowing access to funds early to book facilities as required
* Code sprint budget is structured carry funds from one event to the next allowing us to hold more code-sprints with a smaller annual budget.

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

= Approval and Amendments =

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

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

Code Provenance Review

2019-08-31T09:58:19Z

Kbevers: Fixed formatting of a FAQ question

=Code Provenance Review Process=

'''The official version of this document lives at: http://www.osgeo.org/incubator/process/project_graduation_checklist.html'''

==Document Status==

'''Version:''' 1.1

'''Status:''' draft

'''Last Edited:''' TBD

==Purpose==

The purpose of Code Provenance Review is to establish a reasonable comfort level that an Incubation Project does not have improperly contributed code, and that the code is all under the Project license.

A code provenance review is desirable because it reduces the risk to the foundation, to the project developers and to the software users becoming involved in a legal action or having their use of the software disrupted by sudden removal of improperly contributed code. In particular, many enterprises will not build on open source software projects without some degree of assurance that care is being taken to avoid improper contributions.

It is not the goal to be able to prove that every source file, and every contribution to those files, was contributed properly. The onus is not on the IncCom to prove there are no problems. However, IncCom does need to ensure that OSGeo does not officially endorse code with provenance issues that could have identified and corrected with a reasonable effort.

==Process==

The Code Provenance Review is separated into two sections, each with a slightly different process:
# Create a Provenance Review Document by copying the [[Provenance Review Template]].
# Complete the Library/Component Review Process.
# Complete the Code Copyright Review.
# Submit the completed Provenance Review Document to the Project Mentor for review.

==Library/Component Review Process==

For the overall project, document potential Library/Component issues by:
# Listing any external components that are included "in the source tree" for the project. For instance, GDAL includes a copy of libtiff, libjpeg, etc in the source tree. It is necessary to be able to identify things like that in the source tree that are under their own distinct license, and are not explicitly vetted by the project team. If practical, it is desirable to remove these internal components and treat them as external dependencies. If kept internal, notes on the licenses of the components should be documented using the Provenance Review Template.
# Listing all external dependencies with:
## Potentially problematic license terms (all non-free libraries, for instance).
## All libraries with licenses that might conflict (for instance GDAL's use of GPL'ed GRASS libraries in the non-GPL GDAL).

==Code Copyright Review==

For each project source file, perform the following:
# Does the file include the license information? If not, add it if there there is no ambiguity about whether the standard project license applies. If that is not obvious, make notes in the review document.
# Is the file under the normal project license? If not, make notes in the review document.
# Is there anything obviously unusual about the origin of the code? Does this pose any conflicts? Is the issue properly described in the source file? For instance, in GDAL, the gdal/port/cpl_strtod.cpp file is closely derived from external code that was placed in the public domain. cpl_strtod.cpp is placed under the normal GDAL MIT/X license, but detailed notes are kept in the header text on it's origin, the fact that this was public domain and so the fact that it is ok to relicense it. Oddities should be noted in the source file itself and in the review document.
# Maintain a list of all copyright holders identified in the Provenance Review Document. This list is essentially everyone who would need to agree to relicense the project. It may be desirable to seek copyright assignment to a "project lead", or to the foundation to reduce the number of copyright holders for the project, although this is not required.

==Frequently Asked Questions==

;Do we need to ensure there is a copyright and licence headers in every file?
:Projects are expected to embed a copyright and license header in every source file (.cpp and .h for instance). Machine generated files (such as lex or yacc output for instance) does not require a header if it is inconvenient to embed one, but then an effort should be made to embed a header in the original source file (ie. .l or .y). There is no need to embed copyright and license headers in build files (ie. Makefiles, Visual Studio project files), nor in small documentation fragments (like READMEs). Copyright/license headers should be included in substantial bodies of documentation if it can be done in such a way that it doesn't interfere with the document.

;Do I really need to embed the whole license agreement in every file?
:No, it is sufficient to refer to a single copy of the license agreement for the project, but each file should include an indication of what the license is, and the location of the full license document. For example:
/*
* Copyright (C) 2004-2005 Autodesk, Inc.
*
* This library is free software; you can redistribute it and/or
* modify it under the terms of version 2.1 of the GNU Lesser
* General Public License as published by the Free Software Foundation.
*
* This library is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
* Lesser General Public License for more details.
*
* You should have received a copy of the GNU Lesser General Public
* License along with this library; if not, write to the Free Software
* Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
*/

or:

* COPYRIGHT: (C) 2001 by the GRASS Development Team
*
* This program is free software under the GNU General Public
* License (>=v2). Read the file COPYING that comes with GRASS
* for details.

;Can I just write a script to check everything?
:No. The point of a human review is to ensure that human eyes have looked at the header of each file, looking for any anomalies. For instance it is not uncommon to have additional messages written in headers about the original source of particular code, but not necessarily in a way that a script could recognise.

; But I just did a review similar to this a few months ago, do I really need to do it again?
: If you believe you have already met or exceeded the rigor described in this review document, then you can present the results of your previous analysis along with an explanation of why you think it still applies. You will need to manually review additions since that earlier review. It will be up to the Incubator (and ultimately the foundation board) to determine if they are satisfied with any review.

;Do I need to track down every contributor and ask for permission to use their code?
:No. As long as code was knowingly provided by contributors to the project while it was under a clear licensing policy then it is reasonable to assume the project licensing arrangements are accepted unless there is some reason to have doubts. If code was brought into the project from outside sources under ambiguous circumstances then it may be necessary to contact the copyright holder for a legal release, or at least a statement of permission.

;Some project code was adapted from other sources with ambiguous copyrights, what do I do?
:First, document such concerns in the review document and within the source files themselves. Second, try to obtain a release to use the provide code. An email statement of permission should be sufficient, but pertinant details of such an email should be included in the source file in questions (eg. date, identification of releasing person, text of the release). If no release is possible, but the code isn't very necessary, consider removing or replacing it to simplify things. Otherwise the issue will need to be discussed in the incubator to assess risk.

; Should I be looking for patent problems?
: No. However, if the code review turns up notes about patent issues - or if there are known patent issues for the project, then these should be noted in the review document. Generally speaking a proper patent review is very difficult and may increase, rather than decrease, legal liability.

; Should I be looking for trademark conflicts?
: Possibly. It may be prudent to check for trademark conflicts for the project name, or the name of public packages within the project. If issues are found they should be noted in the review document.

User:Kbevers

2018-07-20T07:09:18Z

Kbevers:

== Kristian Evers ==

Geophysicist at the [http://www.sdfe.dk/ Danish National Mapping Authority]. Professional interests include point cloud data and coordinate system transformation (PROJ).

[https://github.com/kbevers My GitHub profile]

FOSS4G-Europe 2018 Code sprint

2018-07-17T21:22:08Z

Kbevers: Added myself to the list

== Code Sprint ==

Venue: Universidade do Minho, Guimarães, Portugal

We are following the tradition of hosting a code sprint right after [https://foss4g-europe.osgeopt.pt FOSS4G-Europe 2018].

The code sprint will be held on Friday and Saturday, 20 and 21 of July, 2018 at the University of Minho, in Guimarães, Portugal.

Participation in the code sprint is free of charge and all folks currently involved or interested in getting involved in OSGeo community projects are welcome.

If you plan to attend, please signup in the table below. '''If you are unable to sign up, send us a message to [mailto:foss4g-europe@osgeopt.pt foss4g-europe@osgeopt.pt]'''.

The Codesprint Organizing Team is looking forward to your coming!

'''In summary:'''

===When ===

* Friday, 20 of July, 2018 (9am to 17h00)
* Saturday, 21 of July, 2018 (9am to 17h00)

=== Where===

* Departamento de Sistemas de Informação, Universidade do Minho, Guimarães. [[https://www.openstreetmap.org/#map=19/41.45336/-8.28881 Show on OpenStreetMap]]

== Registered Attendees ==

{| border="1" cellpadding="2" class="wikitable sortable"
!width="30"|No
!width="250"|Name
!width="250"|Email
!width="250"|Projects
|-
| 1 || [[User:Jgrocha|Jorge Gustavo Rocha]] || jgr geomaster pt || QGIS, OpenDroneMap
|-
| 2 || [[User:Astrid Emde|Astrid Emde]] || astrid_emde@osgeo.org || Mapbender, OSGeoLive, OSGeo
|-
| 3 || [[User:Ginetto|Luigi Pirelli]] || luipir gmail com || QGIS
|-
| 4 || [[User:Raymondnijssen|Raymond Nijssen]] || rnijssen terglobo nl || QGIS
|-
| 5 || [[User:Jachym|Jachym Cepicky]] || jachym.cepicky gmail || PyWPS
|-
| 6 || [[User:kbevers|Kristian Evers]] || kreve@sdfe.dk || PROJ (only friday)
|-
| 7 || Add you name here || email || projet(s)
|+
|}

== Projects ==

=== Add your project here ===

Add some tasks to work on the code sprint.

=== OpenDroneMap ===

For those interested in drone imagery, we will have a drone available to fly on Friday and Saturday. The goal is to get an orthophoto and a point cloud from the images taken by the drone.

If someone can bring a decent GPS, we can use ground control points and add them to the processing workflow.

User:Kbevers

2016-12-20T12:11:59Z

Kbevers:

== Kristian Evers ==

Geophysicist at the [http://www.sdfe.dk/ Danish National Mapping Authority]. Professional interests include point cloud data and coordinate system transformation (proj.4).

[https://github.com/kbevers My GitHub profile]

User:Kbevers

2016-12-20T12:09:30Z

Kbevers:

Geophysicist at the [http://www.sdfe.dk/ Danish National Mapping Authority]. Professional interests include point cloud data and coordinate system transformation (proj.4).

[https://github.com/kbevers My GitHub profile]