Difference between revisions of "OSGeo Budget 2018"
| Line 212: | Line 212: | ||
|- | |- | ||
! OSGeo Project | ! OSGeo Project | ||
| − | ! 2017 | + | ! 2016 |
| + | ! 2017 | ||
! 2017 Actual | ! 2017 Actual | ||
! 2018 Draft | ! 2018 Draft | ||
| Line 218: | Line 219: | ||
|- | |- | ||
| GRASS | | GRASS | ||
| + | | style="text-align:right;" | | ||
| style="text-align:right;" | 1,500 | | style="text-align:right;" | 1,500 | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
| Line 225: | Line 227: | ||
|- | |- | ||
| QGIS | | QGIS | ||
| + | | style="text-align:right;" | | ||
| style="text-align:right;" | 3,000 | | style="text-align:right;" | 3,000 | ||
| style="text-align:right;" | 3,500 | | style="text-align:right;" | 3,500 | ||
| Line 232: | Line 235: | ||
|- | |- | ||
| GeoServer | | GeoServer | ||
| − | |||
| style="text-align:right;" | | | style="text-align:right;" | | ||
| style="text-align:right;" | | | style="text-align:right;" | | ||
| − | | | + | | style="text-align:right;" | |
| − | + | | style="text-align:right;" | 500 | |
| + | | Planning was focused on sprint, $500 used for developer travel | ||
|- | |- | ||
| ZOO-Project | | ZOO-Project | ||
| + | | style="text-align:right;" | | ||
| style="text-align:right;" | 2,000 | | style="text-align:right;" | 2,000 | ||
| style="text-align:right;" | | | style="text-align:right;" | | ||
| style="text-align:right;" | | | style="text-align:right;" | | ||
| Spending 2017: TODO | | Spending 2017: TODO | ||
| − | + | 2018: Guidance: coordinate with incubation committee | |
|- | |- | ||
| OpenLayers | | OpenLayers | ||
| + | | style="text-align:right;" | | ||
| style="text-align:right;" | 2,000 | | style="text-align:right;" | 2,000 | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
| Line 253: | Line 258: | ||
|- | |- | ||
| MapServer | | MapServer | ||
| − | |||
| style="text-align:right;" | | | style="text-align:right;" | | ||
| style="text-align:right;" | | | style="text-align:right;" | | ||
| − | | | + | | style="text-align:right;" | |
| − | + | | style="text-align:right;" | | |
| + | | 2017: Focused on code sprint, see next section | ||
| + | 2018: TODO | ||
|- | |- | ||
| PostGIS | | PostGIS | ||
| + | | style="text-align:right;" | | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
| style="text-align:right;" | 0 | | style="text-align:right;" | 0 | ||
| Line 267: | Line 274: | ||
|- | |- | ||
| PyWPS | | PyWPS | ||
| + | | style="text-align:right;" | | ||
| style="text-align:right;" | | | style="text-align:right;" | | ||
| style="text-align:right;" | | | style="text-align:right;" | | ||
| Line 274: | Line 282: | ||
|- | |- | ||
| GeoMOOSE | | GeoMOOSE | ||
| + | | style="text-align:right;" | | ||
| style="text-align:right;" | 3,000 | | style="text-align:right;" | 3,000 | ||
| style="text-align:right;" | | | style="text-align:right;" | | ||
| Line 281: | Line 290: | ||
|- | |- | ||
| pycsw | | pycsw | ||
| + | | style="text-align:right;" | | ||
| style="text-align:right;" | 2,000 | | style="text-align:right;" | 2,000 | ||
| style="text-align:right;" | | | style="text-align:right;" | | ||
Revision as of 12:52, 8 November 2017
DRAFT - budget subject to approval in december board meet ing, see OSGeo Budget 2017 and Finance Committee#Documents for prior years.
OSGeo Board
OSGeo board operates according to our bylaws providing vision and direction for our foundation. The board has also taken on responsibility setting an annual budget, building partner relationships and a sponsorship program.
| Board | 2016 | 2017 | 2017 Actual | 2018 Draft | Notes |
|---|---|---|---|---|---|
| Admin | 12,000 | 5000 | (pending) | 5000 | Operational expenses including insurance, tax filing fees, accountant, bank fees |
| Travel | 10,000 | 10,000 | (pending) | 10,000 | Outreach focus
2017: reduced travel costs, some money redirected to rebranding, individual committees picked up a lot of partner travel 2018: no guidance |
| Internal Events | 15,000 | 0 | 0 | 0 | budget moved to committees, travel grants and PSC budgets |
| Outreach Events | 5,000 | 0 | 0 | 0 | budget moved to marketing committee, geoforall, others, ... |
The board is also responsible for handling code sprint requests, covered in the OSGeo Projects section below.
OSGeo Comittees
The following committees have been formed to fufill 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
- Open GeoScience Committee
- System Administration Committee - foundation infrastructure
- UN Committee - committee responsible for our participation in the UN Open GIS program
| OSGeo Committees | 2016 | 2017 | 2017 Actual | 2018 Draft | Notes |
|---|---|---|---|---|---|
| SAC | 13,000 | 15,000 | (pending) | (pending) | (pending) |
| Open GeoScience | 0 | 6,000 | (pending) | (pending) | Need: to ask the committee for current chair to act as officer |
| Marketing | 12,000 | 7,000 | (pending) | (pending) | 2017: budget redirected to website initiative (agreement reached w/ board and marketing comittee)
2018: expect return to prior levels to meet demand for new promotional material and increased presence at partner events |
| GeoForAll | 3,000 | 3,000 | (pending) | (pending) | notes:
2017: moved stuident sponsorship here last year, not sure how it worked out 2018: TBD |
| UN Committee | 5,000 | 6,000 | 3,000? | (pending) | notes:
2017: hackathon fundraising unsuccessful leaving UN Committee unable to use allocated budget 2018: TBD |
| OSGeo Incubation | n/a | n/a | 3,000 | notes:
2017: Budget was not organized for incubating or community projects. 2018: Expect to coordinate a request with participating projects |
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. Iniativies a great way to collaborate with projects, committees and partners.
- GeoForAll - education and research program produced in collaboration with our partners
- FOSS4G - event series produced in collaboration with the conference committee and local chapters
- Local Chapters - outreach initiative establishing regional OSGeo groups for direct grassroots advoacacy
- Open GeoScience - outreach and advocacy geoscience community
- GSOC - coordinate participation in google-summer-of-code and code-in activities
- OSGeo-Live - outreach initiative providing
- Meta CRS - interoperability initiative promoting data sharing with cross project spatial reference system compatibility
- Trave Grant Program - provides assistance for attending OSGeo events
| OSGeo Initiatives | 2016 | 2017 | 2017 Actual | 2018 Draft | Notes |
|---|---|---|---|---|---|
| FOSS4G | Managed by Conference Committee | ||||
| Local Chapters | Managed by board, no direct funding requests | ||||
| Open GeoScience | Managed by Open Geo Science Committee | ||||
| GSOC | notes:
2017: some questions on handling of money raised, additional code-in activity added 2018: guidance: ask if budget is useful, or if committee can be formed | ||||
| OSGeo Live | notes:
2016: budget request made for printing USB sticks, OSGeo Live / Marketing / Board unable to handle 2017: continues to be unclear who can print USB sticks 2018: Guidance: As OSGeo Live if they can take responsibility for these requests? | ||||
| Meta CRS | Long standing initiative, formed as a project to take advantage of early OSGeo infrastructure
2018: Critical group for our interoperability goal, ask participants if they need any assistance | ||||
| Trave Grant Program | 20,000 | 10,000 | New initiative taken on by the conference committee:
- 2017: Travel grant program for foss4g a success, global travel grant program as 6k remaining funds to use in 2017 - 2018: Guidance: Ask conference chair for update, unclear how to handle funds raised across annual budget |
OSGeo Projects
OSGeo Projects each have a project steering committee, the chair of which is acknowledged as a foundation officer.
Notes:
- Note this is a budget, representing planned spending in 2018 - actual balance available to each PSC (from fundraising, donations and sponsorship) should be considered when planning.
- Anita has organized initial to collect feedback from all PSCs concerning planned event sponsorship requests:
| OSGeo Project | 2016 | 2017 | 2017 Actual | 2018 Draft | Notes |
|---|---|---|---|---|---|
| GRASS | 1,500 | 0 | 3,500 | Spending 2017: 0
Plans 2018: 3,500 (sprints and possibly assist in travel) | |
| QGIS | 3,000 | 3,500 | 3,500 | Spending 2017: User Conference and Developer Meeting (Voting) Plans 2018: TODO | |
| GeoServer | 500 | Planning was focused on sprint, $500 used for developer travel | |||
| ZOO-Project | 2,000 | Spending 2017: TODO
2018: Guidance: coordinate with incubation committee | |||
| OpenLayers | 2,000 | 0 | 2,000 | Spending 2017: TODO
Plans 2018: TODO | |
| MapServer | 2017: Focused on code sprint, see next section
2018: TODO | ||||
| PostGIS | 0 | 0 | 5,000 | Spending 2017:
Plans 2018: TODO Code Sprint, Developer Meeting | |
| PyWPS | Spending 2017: TODO
Plans 2018: TODO | ||||
| GeoMOOSE | 3,000 | Spending 2017: TODO
Plans 2018: TODO | |||
| pycsw | 2,000 | Spending 2017: TODO
Plans 2018: TODO |
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.
- Code sprint funding is setup to help carry funds from one event to the next allowing us to hold more code-sprints with a smaller annual budget.
- Out priority is to share the risk with organizers allowing access to funds early to book facilities as required.
| Sprint Request | 2016 | 2017 | Actual | 2018 Draft | Notes |
|---|---|---|---|---|---|
| MapServer | 5,000 | Spending 2017: C Tribe Code Sprint (Voting)
Plans 2018: TODO | |||
| GeoServer | 2,000 | 2,000 | 3,000 | 2,000 | Spending 2016: GeoServer_Code_Sprint_2016 Spending 2017: Java Tribe Code Sprint (Voting) |
| GLTN Sprint | 3,000 | Request from our strategic partnership with UN global land tools network: (Voting) Since it was not budgeted for up front expenses were split between outreach (because partnership) and code-sprint budget |