Difference between revisions of "OSGeo Budget 2020"
Line 73: | Line 73: | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
− | | | + | | |
|- | |- | ||
| Open GeoScience | | Open GeoScience | ||
Line 79: | Line 79: | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
− | | | + | | |
|- | |- | ||
| Conference | | Conference | ||
− | |||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
− | | | + | | style="text-align:right;" | 0 |
+ | | | ||
|- | |- | ||
| Marketing | | Marketing | ||
Line 91: | Line 91: | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
− | | | + | | |
|- | |- | ||
| GeoForAll | | GeoForAll | ||
Line 97: | Line 97: | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
− | | | + | | |
|- | |- | ||
| UN Committee | | UN Committee | ||
Line 103: | Line 103: | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
− | | | + | | |
|- | |- | ||
| Incubation Committee | | Incubation Committee | ||
Line 109: | Line 109: | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
− | | | + | | |
|} | |} | ||
Line 141: | Line 141: | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
− | | Managed by Conference Committee. Seed money for | + | | Managed by Conference Committee. Seed money for 2020 will be allocated by the board when estimate numbers become available. |
|- | |- | ||
| Local Chapters | | Local Chapters | ||
Line 153: | Line 153: | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
− | | TGP, 50- | + | | TGP, 50-50% for global event, rest for regional events (Previous years had a component of matching sponsor donations) |
|- | |- | ||
| Events and Code Sprints | | Events and Code Sprints | ||
Line 165: | Line 165: | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
| 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 | + | | Managed by the board since community projects do not have an assigned officer to handle their budget. We have around 15-20 projects expected in 2020 (see list bellow). Budgeted 1000$ for each project. |
|} | |} | ||
Line 180: | Line 180: | ||
Notes: | Notes: | ||
− | * We have reached out to the projects mailing list with a default suggestion of 2000 for any project that responds | + | * 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 | * Projects with a plan may of course ask for increased funding | ||
− | * This is a budget, representing planned spending in | + | * 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 | * If a project did not respond (or runs into an unforeseen expense) please contact the board throughout the year as budgets can be amended | ||
Line 197: | Line 197: | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
− | | | + | | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
| GDAL/OGR | | GDAL/OGR | ||
Line 209: | Line 203: | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
− | | | + | | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
| GeoMOOSE | | GeoMOOSE | ||
Line 221: | Line 209: | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
− | | | + | | |
|- | |- | ||
| GeoNetwork | | GeoNetwork | ||
Line 227: | Line 215: | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
− | | | + | | |
|- | |- | ||
| GeoNode | | GeoNode | ||
Line 233: | Line 221: | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
− | | | + | | |
|- | |- | ||
| GEOS | | GEOS | ||
Line 239: | Line 227: | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
− | | | + | | |
|- | |- | ||
| GeoServer | | GeoServer | ||
Line 245: | Line 233: | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
− | | | + | | |
|- | |- | ||
| GeoTools | | GeoTools | ||
Line 251: | Line 239: | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
− | | | + | | |
|- | |- | ||
| GRASS GIS | | GRASS GIS | ||
Line 257: | Line 245: | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
− | | | + | | |
|- | |- | ||
| gvSIG | | gvSIG | ||
Line 263: | Line 251: | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
− | | | + | | |
|- | |- | ||
| Mapbender | | Mapbender | ||
Line 269: | Line 257: | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
− | | | + | | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
| MapServer | | MapServer | ||
Line 287: | Line 263: | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
− | | | + | | |
|- | |- | ||
| Marble | | Marble | ||
Line 293: | Line 269: | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
− | | | + | | |
|- | |- | ||
| OpenLayers | | OpenLayers | ||
Line 299: | Line 275: | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
− | | | + | | |
|- | |- | ||
− | | | + | | OTB |
+ | | style="text-align:right;" | 2,000 | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
− | | | + | | |
− | |||
|- | |- | ||
− | | | + | | OSGeoLive |
− | | style="text-align:right;" | | + | | style="text-align:right;" | 2,000 |
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
− | | | + | | |
|- | |- | ||
− | | | + | | PostGIS |
| style="text-align:right;" | 3,000 | | style="text-align:right;" | 3,000 | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
− | | | + | | |
|- | |- | ||
− | | | + | | PROJ |
− | | style="text-align:right;" | | + | | style="text-align:right;" | N/A |
− | | style="text-align:right;" | | + | | style="text-align:right;" | N/A |
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
− | | | + | | |
|- | |- | ||
− | | | + | | pycsw |
− | | style="text-align:right;" | | + | | style="text-align:right;" | 3,000 |
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
− | | | + | | |
|- | |- | ||
| PyWPS | | PyWPS | ||
Line 335: | Line 311: | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
− | | | + | | |
|- | |- | ||
− | | | + | | QGIS |
− | | style="text-align:right;" | | + | | style="text-align:right;" | 8,000 |
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
− | | | + | | |
|} | |} | ||
Revision as of 14:24, 3 December 2019
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.
Board | 2019 | 2019 Actual | 2020 | Notes |
---|---|---|---|---|
Admin | 3,000 | 0 | 0 | Operational expenses including liability insurance, tax filing fees, accountant, bank fees. |
Travel | 22,000 | 0 | 0 | Travel to main FOSS4G and F2F meeting (15k), and regional/representative events (7k) |
Partners | 2,000 | 0 | 0 | Relationship building, attending b2b functions, foss4g/foss4ge/foss4gna/foss4g-asia breakfast meetings |
Sponsors | 2,000 | 0 | 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
OSGeo Committees | 2019 | 2019 Actual | 2020 | Notes |
---|---|---|---|---|
SAC | 23,750 | 0 | 0 | |
Open GeoScience | 6,100 | 0 | 0 | |
Conference | 0 | 0 | 0 | |
Marketing | 22,600 | 0 | 0 | |
GeoForAll | 3,000 | 0 | 0 | |
UN Committee | 11,000 | 0 | 0 | |
Incubation Committee | 10,000 | 0 | 0 |
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
OSGeo Initiatives | 2019 | 2019 Actual | 2020 | Notes |
---|---|---|---|---|
FOSS4G | 0 | 0 | 0 | Managed by Conference Committee. Seed money for 2020 will be allocated by the board when estimate numbers become available. |
Local Chapters | 5,000 | 0 | 0 | Managed by board, considering putting aside money to help establish local chapters (for logistics, legal advise, kickoff meetings rather than any sponsorship or direct funding) |
Travel Grant Program | 25.000 | 0 | 0 | TGP, 50-50% for global event, rest for regional events (Previous years had a component of matching sponsor donations) |
Events and Code Sprints | 15,000 | 0 | 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 | 15,000 | 0 | 0 | Managed by the board since community projects do not have an assigned officer to handle their budget. We have around 15-20 projects expected in 2020 (see list bellow). Budgeted 1000$ for each project. |
Total Initiatives Budget for 2019: $60,000 USD
Total Initiatives Budget for 2020: $TBD USD
Projects
OSGeo Projects
OSGeo Projects each have a project steering committee, the chair of which is acknowledged as a foundation officer with spending authority on behalf of their committee.
Notes:
- We have reached out (2019) to the projects mailing list with a default suggestion of 2000 for any project that responds
- Projects with a plan may of course ask for increased funding
- This is a budget, representing planned spending in 2020 - actual balance available to each PSC (from fundraising, donations and sponsorship) may be considered when planning.
- If a project did not respond (or runs into an unforeseen expense) please contact the board throughout the year as budgets can be amended
OSGeo Project | 2019 | 2019 Actual | 2020 | Notes |
---|---|---|---|---|
deegree | 2,000 | 0 | 0 | |
GDAL/OGR | 5,000 | 0 | 0 | |
GeoMOOSE | 2,000 | 0 | 0 | |
GeoNetwork | 2,000 | 0 | 0 | |
GeoNode | 2,000 | 0 | 0 | |
GEOS | 1,000 | 0 | 0 | |
GeoServer | 7,000 | 0 | 0 | |
GeoTools | 2,000 | 0 | 0 | |
GRASS GIS | 9,000 | 0 | 0 | |
gvSIG | 3,000 | 0 | 0 | |
Mapbender | 2,000 | 0 | 0 | |
MapServer | 2,500 | 0 | 0 | |
Marble | 1,000 | 0 | 0 | |
OpenLayers | 3,000 | 0 | 0 | |
OTB | 2,000 | 0 | 0 | |
OSGeoLive | 2,000 | 0 | 0 | |
PostGIS | 3,000 | 0 | 0 | |
PROJ | N/A | N/A | 0 | |
pycsw | 3,000 | 0 | 0 | |
PyWPS | 3,200 | 0 | 0 | |
QGIS | 8,000 | 0 | 0 |
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 $1000 for each project (see Community Projects Initiative above)
- OSGeo4W
- Optics *
- Pronto Raster
- Porgy
- pgRouting
- GeoHealthCheck
- Portable GIS
- TEAM Engine *
- GC2/Vidi
- GeoWebCache
- ZOO-Project *
- istSOS *
Some incubation projects are not yet set up as part of OSGeo community:
- Oskar
- PROJ - MetaCRS changed to an initiative
Some guidance is offered by individual projects below:
Community Project | 2019 | 2019 Actual | 2020 | Notes |
---|---|---|---|---|
ZOO-Project | up to 4,000 (need specific requests to board and incubation committee) | 0 | 0 | ZOO-Project_Budget_2019. Board approved up to 3,000 for incubation tasks and 1,000 as a community project |
pgRouting | up to 4,000 (need specific requests to board and incubation committee) | 0 | 0 | Board approved up to 3,000 for Incubation tasks and 1,000 as a community project. Project asked 2,000 travel expenses to FOSS4G 2019. |
istSOS | up to 4,000 (need specific requests to board and incubation committee) | 0 | 0 | Istsos_Budget_2019. Board approved up to 3,000 for incubation tasks and 1,000 as a community project. |
Events
Community Events
We are considering setting aside a budget for community events in 2019:
- 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
Event Request | 2019 | 2019 Actual | 2020 | Notes |
---|---|---|---|---|
QGIS Developer Meeting and User Conference | 3,000 | 0 | 0 | in March in A Coruna, Spain |
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.
Sprint Request | 2019 | 2019 Actual | 2020 | Notes |
---|---|---|---|---|
OSGeo Code Sprint | 0 | 0 | No financial request made, event planning is well under way. | |
GeoServer | 2,000 | 0 | 0 | Considering a CITE compliance sprint in Europe |
PostGIS Code Sprint | - | 0 | 0 | (included in project request above) |
GRASS GIS Community Sprint | - | 0 | 0 | (included in project request above) |
Small Code Sprints | 10,000 | 0 | 0 |
Approval and Amendments
- Budget Meeting: Board Meeting 2019-01-21
- Loomio Motion: [1]
- Amendments: TBD