OSGeo - User contributions [en]

OSGeo Budget 2026

2025-12-21T04:59:33Z

Elil: /* OSGeo Projects */

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

Total Approved Budget for 2025: $79,875 USD

Total spending for 2025: TBD

Total Approved Budget for 2026: 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
! 2025 Approved
! 2025 Actual
! 2026 Draft
! Notes
|-
| Admin
| style="text-align:right;" | 4,500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Operational expenses including liability insurance, tax filing fees, quickbooks, mail, IRS, bank fees, bank interest, accounting software, Delaware taxes.
|-
| Travel
| style="text-align:right;" | 2,500
| 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;" | 0
| 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 2025: $7,000 USD

Total Board spending for 2025: TBD

Total Board Budget for 2026: 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
! 2025 Approved [Requested]
! 2025 Actual
! 2026 Draft [Requested]
! Notes
|-
| SAC
| style="text-align:right;" | 16,000 [55,850]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| https://wiki.osgeo.org/wiki/SAC:Budget#2025 Board Note: We can only pay for 120h for contracts, we will provide a priority list of items to work. The board will consider a 4k budget increase in case of emergency. The board will also plan a survey between projects to prioritize usage of current services (e.g. trac, gitea, etc) to decide which services to maintain. For this year we will not approve donations to external OS projects due to budget limitations. Budget for initiatives like "OSGeo ID Creation" will be considered if changes in revenue happen.
|-
| OpenGeoScience
| style="text-align:right;" | 2,000 [3,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| https://wiki.osgeo.org/wiki/Open_Geoscience_Committee/budget_2025 Board Note: Marketing material should be asked from Marketing committee. 1k for workshop, 1k for event
|-
| Conference
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| Marketing
| style="text-align:right;" | 2,000 [25,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| [[Marketing_Committee_Budget_2025]] Board Note: 1500$ for materials, 500$ for podcast. The "OSGeo UserID Creation" is discussed in the SAC budget. Please also see website initiative budget bellow.
|-
| GeoForAll
| style="text-align:right;" | 0
| 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;" | 1,500 [0]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Board Note: budget for GeoStyler
|}

Total Committees Budget for 2025: $21,500 USD

Total Committees spending for 2025: TBD

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

* Website updates

{|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
! 2025 Approved
! 2025 Actual
! 2026 Draft [Requested]
! Notes
|-
| FOSS4G
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Seed money for 2026.
|-
| 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;" | 12,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Managed by Conference Committee. Board Note: (10k for FOSS4G, 2k for local events)
|-
| Events and Code Sprints
| style="text-align:right;" | 5,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.
|-
| Website updates
| style="text-align:right;" | 7,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| For the website the board will match sponsor amount up to 7000
|-
| 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.
|}

Total Initiatives Budget for 2025: $27,000 USD

Total Initiatives spending for 2025: TBD

Total Initiatives Budget for 2026: 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 $2,000 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
! 2025 Approved [Requested]
! 2025 Actual
! 2026 Draft [Requested]
! Notes
|-
| deegree
| style="text-align:right;" | 0
| 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;" | 0 [4,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | ##### [4,000]
| [https://github.com/geomoose/geomoose/wiki/2025-Annual-Report Annual Report] [https://lists.osgeo.org/pipermail/geomoose-psc/2025-December/001188.html Budget] 
|-
| GeoNetwork
| style="text-align:right;" | 0
| 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;" | TBD
| [https://github.com/geoserver/geoserver/wiki/GeoServer-2025-Sponsorship-Opportunities GeoServer 2025 sponsorship opportunities]
|-
| GeoTools
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GRASS GIS
| style="text-align:right;" | 2,000 [5,002]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| [[GRASS GIS Budget 2025]]
|-
| gvSIG
| style="text-align:right;" | 2,000 [5,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| 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,000 [5,000]
| 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,000 [3,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| [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
|
|-
| pgrouting
| style="text-align:right;" | 2,000 [2,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| https://wiki.osgeo.org/wiki/PgRouting_Budget#2025
|-
| 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,000 [3,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| style="text-align:right;" | https://github.com/geopython/pycsw/wiki/OSGeo-Budget-2025
|
|-
| pygeoapi
| style="text-align:right;" | 2,000 [4,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| 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;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| ZOO-Project
| style="text-align:right;" | 2,000 [6,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| https://github.com/ZOO-Project/ZOO-Project/wiki/ZOO-Project-Budget-2025
|-
|}

Total Projects Budget for 2025: $18,000 USD

Total Projects spending for 2025: TBD

Total Projects Budget for 2026: TBD

== Community Projects ==

Community projects act through the board as they do not have a project officer.

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

= 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
! 2025 Approved
! 2025 Actual
! 2026 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
! 2025 Approved
! 2025 Actual
! 2026 Draft [Requested]
! Notes
|-
| OSGeo Code Sprint
| style="text-align:right;" | 4,395
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| 4,395 surplus from Vienna.
|-
| GeoStyler Code Sprint
| style="text-align:right;" | 2,000 [3,675]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| https://lists.osgeo.org/pipermail/board/2024-December/013598.html
|-
|}

= Approval and Amendments =

* Budget Meeting: TBD
* Loomio Motion: TBD
* Amendments:

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

Conference Committee

2025-09-16T14:38:51Z

Elil: /* Past Members */

The Conference Committee is the official committee of OSGeo responsible for operating the annual [[FOSS4G]] conferences.

= Noteworthy Documents =

* [[FOSS4G Handbook]] (provides guidance to future FOSS4G and related events, based upon the collective wisdom gained during prior events)
* [http://lists.osgeo.org/mailman/listinfo/conference_dev Conference Committee email list]
* [http://www.osgeo.org/conference OSGeo Conference Committee main page] (includes RFP, proposals, and archived files from past conferences)
* Past conference reports are detailed at [[Past FOSS4G Reports]]
* [[Conference website management]]
* [[Motion to form Conference Committee]]
* [[Conference Committee Budget 2017 | Conference Committee Budget 2017 (draft)]]

= Goals =
The conference committee have the responsibility to:
* Run the selection process and voting for the global FOSS4G
* Vote on conference related proposals submitted to the committee
* Retain the [[FOSS4G Handbook | collected wisdom]] for FOSS4G and related events
* Advise the board, Local Organising Committees (LOC), and related events organisors, ideally referencing the [[FOSS4G Handbook]]
* Ensure OSGeo foundation principles are applied to global FOSS4G conferences
* Manage the FOSS4G Travel Grant Programme for FOSS4G and regional events

See also: '''2016 priorities are summarised in [[Conference Committee 2016 Priorities]]'''

=Housekeeping Procedures=
The Conference Committee uses the following procedures to make decisions.

==Decisions==

[[consideration for new selection methods]]

# Anyone may contribute to conference committee discussions. All votes will be noted, but only conference committee member votes count toward decisions.
# Voting will use convention of:
#* +1 : For
#* +0: Mildly for
#* 0: Indifferent
#* -0: Mildly against
#* -1 : Strongly against. This is expected to be accompanied by a reason and alternative proposal.
# Everyday topics will be decided by an open vote of all members in a clearly designated separate mail thread over a minimum of 2 business days with a minimum participation of 3 votes.
# For major decisions, such as conference venue selection, a minimum of one week shall be allocated to try and ensure at least 50% voter participation.
# The committee aims for consensus, and will specifically attempt to address all -1 votes, but will revert to a majority vote where necessary.
# The result will be clearly declared afterwards.
# Secret voting, when required, will use an online voting service or use an email to an independent teller appointed by CC Chair.

==FOSS4G Selection==

# All Letters of Intent and subsequent proposals will be posted to the list for open comment by all.
# The selection of the winning proposal is by secret vote of conference committee members.
# The OSGeo Board will be requested to ratify the conference committee’s recommendation.
# Any committee member who has a potential conflict of interest is expected to withdraw from voting. A member of the committee who is part of a bidding team, intends to become part of the LOC or is employed by a company playing an active part in a bid should exclude themselves from voting in the selection process. In the event of a disagreement regarding a potential conflict of interest the committee chair has the authority to make a decision.

=== Changes in RfP Document for 2021 ===
* At least at the letters-of-intent stage there should always be a voting option of "None of the above". Otherwise there's no point in having a vote if there's only one letter, also this allows for the (unlikely) event of all letters being rubbish.
* Bids should be scored based on various pre-defined criterion. Current voting by the committee seems to include a "where I want to go on holiday" component which has no place in a process like this. This is in keeping with the "openness" goal of OSGeo as compared to the current Star Chamber-like voting.
* Further to the above, a list of objective mandatory criterion can be specified as required. I.e. "Venue must be able to host X people", "must be at least Y tracks", "Must be accessible via both local and national public transport", etc.

==FOSS4G Travel Grant Programme==

The FOSS4G TGP was started in 2017 with funding from the OSGeo Board and a crowd funding initiative. The Conference Committee is tasked with managing this grant programme for the Global FOSS4G and for any Regional FOSS4G's that request assistance

* [[FOSS4G Travel Grant Programme 2017 | 2017]]
* [[FOSS4G Travel Grant Programme 2018 | 2018]]

=== Setting up a FOSS4G TGP ===

Some guidance notes are available in the [[FOSS4G Travel Grant Programme Cookbook | FOSS4G Travel Grant Programme Cookbook]]

==Membership==

# To ensure voting control for key decisions remains with experienced people, the committee aims for more than 50% of members to be chairs (or vice chairs) of past FOSS4G global events. The chair of the most recent FOSS4G event will automatically be invited to become a member but still requires a motion and vote.
# The conference committee aims to retain a chair or vice-chair from the 5 most recent global FOSS4G conferences.
# The remaining membership, less than 50% of members, is open, ideally attracting chairs or LOC members from past Global or Regional FOSS4G or related conferences.
# Each year, prior to releasing the Global FOSS4G RfP, the membership list shall be re-visited.
## Existing members shall be asked whether they wish to continue on the committee. If a member doesn't respond, after a number of attempts to contact them, they shall be retired.
## Interested people may be suggested, or request to be voted onto the conference committee.
## If less than 50% of membership would be past global FOSS4G chair/vice chairs, then non global FOSS4G chair/vice chair positions shall be up for re-election.
## Election of conference committee members is by secret vote by the existing conference committee and board members who are not already members of the conference committee. Voters will vote Yes/No/Abstain for each candidate. Voters may select "Yes" for up to the number of positions available.
# Votes will be secret either using an online voting system or by email to a designated teller who is not a voter. The mechanism will be selected by the committee chair.

== Current Members ==

# [[User:pmbatty | Peter Batty]] - member since 2011 (chair of Global FOSS4G 2011)
# [[User:Bitner | David Bitner]] (chair of the 2013 FOSS4GNA)
# [[User:Maria | Maria Brovelli]] - member since March 2016 (Chair FOSS4G Europe 2015)
# [[User:Vasile | Vasile Craciunescu]] - '''Co-Chair''' - member since July 2013 (chair of FOSS4G Central and Eastern Europe 2013)
# David Fawcett (Programme Team FOSS4GNA 2013)
# [[User:GFleming |Gavin Fleming]] - (chair of Global FOSS4G 2008)
# Darrell Fuhriman (chair of Global FOSS4G 2014)
# Claude Philipona - (chair of Global FOSS4G 2006)
# [[User:Venkat | Venkatesh Raghavan]] - member since Oct. 2006 (Chair FOSS4G-2004, FOSS4G-Asia 2014)
# [[User:Pwramsey3 | Paul Ramsey]] - Chair of global FOSS4G 2007
# [[User:Gsteinmon | Guido Stein]] - member since February 2018 (chair of Global FOSS4G 2017)
# [[User:MichaelTerner | Michael Terner]] - member since February 2018 (chair of Global FOSS4G 2017)
# Msilikale Msilanga - '''Co-Chair''' - member since September 2018 (co-chair of Global FOSS4G 2018)
# Mark Iliffe - member since September 2018 (co-chair of Global FOSS4G 2018)
# [[User:Delawen | María Arias de Reyna Domínguez]] - member since November 2021 (chair of Global FOSS4G 2021)
# [[User:Lucadelu | Luca Delucchi]] - member since October 2022 (chair of Global FOSS4G 2022)
* [https://lists.osgeo.org/pipermail/conference_dev/2019-December/005411.html Motion for co-chairs]

== Past Members ==

# Lorenzo Becchi
# Allan Doyle
# Olivier Ertz
# Alain Grignon
# Luc Maurer
# Daniel Rappo
# Dave Patton
# Rafael Medeiros Sperb
# Arnulf Christl
# [[Markus Neteler]]
# Steve Lime
# Frank Warmerdam
# [[User:Davemac | Dave McIlhagga]] (resigned August 2016)
# [[User:Ticheler | Jeroen Ticheler]] (resigned September 2016)
# [[User:Thierry Badard | Thierry Badard]] (resigned September 2016)
# [[User:Helena | Helena Mitasova]] (resigned September 2016)
# [[User:Camerons | Cameron Shorter]] - member from 2009 to Oct 2017 (chair of Global FOSS4G 2009)
# [[User:Jachym | Jachym Cepicky]] - (resigned August 2019)
# [[User:Till Adams | Till Adams]] - resigned October 2022 / member since September 2016 (chair of Global FOSS4G 2016)
# [[User:Stevenfeldman | Steven Feldman]] - resigned October 2022 / member since October 2013 (chair of Global FOSS4G 2013)
# [[User:EliL | Eli Adam]] - resigned [https://lists.osgeo.org/pipermail/conference_dev/2022-October/005859.html October 2022] / member since [https://lists.osgeo.org/pipermail/conference_dev/2015-January/002811.html January 2015] (1 of 4 co-chairs of Global FOSS4G 2014)
# [[User:Sanghee | Sanghee Shin]] - member since 2015 (chair of Global FOSS4G 2015)

= Meetings =

* Meetings occur in IRC in the #foss4g channel (on irc.freenode.net) or by other means organized on the email list. Meetings are infrequent.
* <s>As of 2016 the [[Conference_Committee_Meetings | Conference Committee Meetings]] page was not being maintained any more.</s>

=2025 Pages=
* [[FOSS4G_2025_Bid_Process | 2025 RFP schedule]]

=2024 Pages=
* [[FOSS4G_2024_Bid_Process | 2024 RFP schedule]]

=2023 Pages=
* [[FOSS4G_2023_Bid_Process | 2023 RFP schedule]]

=2022 Pages=

* [[FOSS4G_2022_Bid_Process | 2022 RFP schedule]]

=2021 Pages=

* [[FOSS4G_2021_Bid_Process | 2021 RFP schedue]]

=2020 Pages=

* [[FOSS4G_2020_Bid_Process | 2020 RFP schedue]]

=2019 Pages=

* [[FOSS4G_2019_Bid_Process | 2019 RFP schedule]]

=2018 Pages=

* [[FOSS4G_2018_Bid_Process | 2018 RFP schedule]]
* [[Conference_Committee_F2F_2016 | Conference Committee Face to Face meeting in Bonn, 2016]]

= 2017 Pages =

* [[FOSS4G_2017_Bid_Process | 2017 RFP schedule]]
* [[FOSS4G_Travel_Grant_Programme_2017 | 2017 Travel Grant Programme]]

= 2016 Pages =

* [http://www.osgeo.org/conference/rfp/ 2016 RFP schedule]

= 2015 Pages =

* [[FOSS4G 2015 Bid Process]]

= 2014 Pages =

* [[FOSS4G 2014 Bid Process]]
* [[FOSS4G 2014]]
* [[FOSS4G Europe 2014]]

= 2013 Pages =

* Main page: [[FOSS4G_2013]]
* [http://svn.osgeo.org/osgeo/foss4g/2013/documents/FOSS4G_2013_UK_Proposal-Final_version.pdf 2013 Proposal]
* Reflections on the event by the LOC (includes lessons learnt and supersedes the old Lessons Learned page): [[FOSS4G2013_Reflections_by_the_LOC]]

= 2012 Pages =
Main page: [[FOSS4G 2012]]
* RFP ([http://svn.osgeo.org/osgeo/foss4g/rfp/2012/osgeo-conference-2012-request-for-proposal.odt OpenOffice], [http://svn.osgeo.org/osgeo/foss4g/rfp/2012/osgeo-conference-2012-request-for-proposal.pdf pdf])
* budget template ([http://svn.osgeo.org/osgeo/foss4g/rfp/2012/osgeo-conference-budget-template.ods OpenOffice])
* Important dates:
** Letters of Intent (Stage 1) due: 2011-06-30 ([http://www.timeanddate.com/worldclock/fixedtime.html?year=2011&month=06&day=30&hour=23&min=0&sec=0 23:00 UTC])
** Stage 1 question period: 2011-06-30 to 2011-07-07
** Stage 1 decision: 2011-07-07
** Proposals (Stage 2) due: 2011-08-01 ([http://www.timeanddate.com/worldclock/fixedtime.html?year=2011&month=08&day=01&hour=23&min=0&sec=0 23:00 UTC])
** Stage 2 question period: 2011-08-01 to 2011-08-05
** Final decision: 2011-08-05

= 2011 Pages =

* [http://www.osgeo.org/conference/rfp RFP and Letters of Intent]
* [[FOSS4G_2011_Bid_Process | 2011 Bid Process]]
* [[FOSS4G Reboot 2011 | Initial thoughts on 2011 required changes]]

= 2010 Pages =

* [http://www.osgeo.org/conference/rfp RFP and Proposals]
* [[Conference_Committee_2010_Bid_Questions | Bid Questions]]
* [[Conference_Committee_2010_Voting_Process | Voting Process]]

= 2009 Pages =

* [[FOSS4G 2009 Governance]]
* All [http://wiki.osgeo.org/wiki/Category:FOSS4G2009 FOSS4G 2009] pages.

= 2008 Pages =

* [http://www.osgeo.org/conference/rfp RFP and Proposals]
* [http://lists.osgeo.org/pipermail/conference_dev/2007-July/000355.html Voting Process]
* [[FOSS4G 2008 Governance]]
* [[FOSS4GLOC matters]]
* [http://spreadsheets.google.com/pub?key=p6mc38S7PA8lHWRQuIgExDA Workshop and lab evaluations]

= 2007 Pages =

* [http://wiki.osgeo.org/index.php/Category:FOSS4G2007 Pages in category "FOSS4G2007"]
* [[FOSS4G2007]] - wiki page
* http://www.foss4g2007.org/ - Conference Site
* [http://www.osgeo.org/conference/rfp Proposals and RFP]
* [[OSGeo_Conference_RFP_2007#RFP_Response_Requirements | requirements Wiki page]]
* [[OSGeo_Conference_Naming_Results | Naming results]]
* [http://www.foss4g2007.org/bid_site/ Victoria 2007 Proposal]
* [[FOSS4G 2007 Governance]]
* [[FOSS4G2007 Lessons Learned]]

= 2006 Pages =

* [http://wiki.osgeo.org/index.php/Category:FOSS4G2006 Pages in category "FOSS4G2006"]
* http://www.foss4g2006.org/ - Conference Site
* [[FOSS4G2006]] information

= Event Policy Pages =

* [[Official_OSGeo_Event_Policy | OSGeo Event policy]] (in review)
* [[OSGeo_Conference_Policy | Board notes]] regarding event policy
* [http://www.osgeo.org/code_of_conduct OSGeo Code of Conduct]

[[Category:FOSS4G]]
[[Category:Committees]]
[[Category:Conference Committee]]

OSGeo Budget 2024

2024-01-23T18:11:17Z

Elil: /* OSGeo Projects */ updated budget per PSC

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;" | [53,450]
| [[SAC:Budget#2024|SAC:Budget 2024]]
|-
| OpenGeoScience
| style="text-align:right;" | 1,500 [3,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | [3,000]
| https://lists.osgeo.org/pipermail/board/2023-December/013429.html
|-
| 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:

* no new initiatives proposed for 2024

{|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;" | 10,000?
| style="text-align:right;" | none
| Activity completed
|}

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;" | [2,000]
| [https://github.com/deegree/deegree3/wiki/deegree-budget-2024 deegree 2024 Sponsorship Opportunities and Budget]
|-
| GDAL/OGR
| style="text-align:right;" | 1,000
| 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;" | [4,000]
| [https://github.com/geomoose/geomoose/wiki/PSC-Meeting-2023-12-08#Vote-on-Budget-proposal-for-2024 PSC budget meeting ]
|-
| GeoNetwork
| style="text-align:right;" | 1,000
| style="text-align:right;" | TBD
| style="text-align:right;" | [2,000]
| [https://github.com/geonetwork/core-geonetwork/wiki/GeoNetwork-2024-Sponsorship-Opportunities GeoNetwork 2024 Sponsorship Opportunities]
|-
| 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;" | 2,000 [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;" | [3,000]
| https://github.com/openlayers/openlayers/wiki/OpenLayers-2024-Sponsorship-Opportunities
|-
| 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;" | 2,393
| style="text-align:right;" | [3,000]
| https://github.com/geopython/pycsw/wiki/OSGeo-Budget-2024
|-
| pygeoapi
| style="text-align:right;" | 4,000 [4,000]
| style="text-align:right;" | 0
| style="text-align:right;" | [4,000]
| https://github.com/geopython/pygeoapi/wiki/OSGeo-Budget-2024
|-
| 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 Draft [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;" | none
| 2023 Activity covered by opengis initiative
|-
|}

= 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 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
! 2023 Approved
! 2023 Actual
! 2024 Draft [Requested]
! 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]
| [[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-27T04:29:10Z

Elil: /* 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;" | [4250]
| [https://github.com/geomoose/geomoose/wiki/PSC-Meeting-2023-11-17#budget-plan-for-2024 PSC budget meeting (used 1750 for sprint estimate)]
|-
| 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;" | 2,393
| style="text-align:right;" | [3,000]
| https://github.com/geopython/pycsw/wiki/OSGeo-Budget-2024
|-
| pygeoapi
| style="text-align:right;" | 4,000 [4,000]
| style="text-align:right;" | 0
| style="text-align:right;" | [4,000]
| https://github.com/geopython/pygeoapi/wiki/OSGeo-Budget-2024
|-
| 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 Draft [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 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
! 2023 Approved
! 2023 Actual
! 2024 Draft [Requested]
! 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]
| [[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 2023

2023-01-09T19:53:39Z

Elil: /* OSGeo Projects */ update 2022 and 2023 request for 1,500 project expenses, 500 doc writing, and 500 group work session/code sprint/conference

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

Total Approved Budget for 2022: $213,346 USD

Total spending for 2022: TBD

Total Approved Budget for 2023: TBD

== OSGeo Board ==

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

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

Total Board Budget for 2022: $21,000 USD

Total Board spending for 2022: TBD

Total Board Budget for 2023: TBD

== OSGeo Committees ==

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

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

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! OSGeo Committees
! 2022 Approved [Requested]
! 2022 Actual
! 2023 Draft [Requested]
! Notes
|-
| SAC
| style="text-align:right;" | 32,550 [32,550]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| [[SAC:Budget#2023]]
|-
| OpenGeoScience
| style="text-align:right;" | 2,500 [3,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | 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
|
|-
| GeoForAll
| style="text-align:right;" | 4,000 [4,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| UN Committee
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| No UN challenge this year
|-
| Incubation Committee
| style="text-align:right;" | 6,000 [8,000]
| style="text-align:right;" | 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
|
|-
| GDAL/OGR
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoMOOSE
| style="text-align:right;" | 2,500 [2,500]
| style="text-align:right;" | 2,500 (in process)
| style="text-align:right;" | TBD [2,500]
| https://github.com/geomoose/geomoose/wiki/PSC-Meeting-2022-10-21
|-
| GeoNetwork
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoNode
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GEOS
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoServer
| style="text-align:right;" | 3,000 [3,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| 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
|
|-
| 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
|
|-
| 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
|
|-
| 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
|
|}

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

Conference Committee

2022-10-31T18:59:38Z

Elil: resign from Conference Committee

The Conference Committee is the official committee of OSGeo responsible for operating the annual [[FOSS4G]] conferences.

= Noteworthy Documents =

* [[FOSS4G Handbook]] (provides guidance to future FOSS4G and related events, based upon the collective wisdom gained during prior events)
* [http://lists.osgeo.org/mailman/listinfo/conference_dev Conference Committee email list]
* [http://www.osgeo.org/conference OSGeo Conference Committee main page] (includes RFP, proposals, and archived files from past conferences)
* Past conference reports are detailed at [[Past FOSS4G Reports]]
* [[Conference website management]]
* [[Motion to form Conference Committee]]
* [[Conference Committee Budget 2017 | Conference Committee Budget 2017 (draft)]]

= Goals =
The conference committee have the responsibility to:
* Run the selection process and voting for the global FOSS4G
* Vote on conference related proposals submitted to the committee
* Retain the [[FOSS4G Handbook | collected wisdom]] for FOSS4G and related events
* Advise the board, Local Organising Committees (LOC), and related events organisors, ideally referencing the [[FOSS4G Handbook]]
* Ensure OSGeo foundation principles are applied to global FOSS4G conferences
* Manage the FOSS4G Travel Grant Programme for FOSS4G and regional events

See also: '''2016 priorities are summarised in [[Conference Committee 2016 Priorities]]'''

=Housekeeping Procedures=
The Conference Committee uses the following procedures to make decisions.

==Decisions==

[[consideration for new selection methods]]

# Anyone may contribute to conference committee discussions. All votes will be noted, but only conference committee member votes count toward decisions.
# Voting will use convention of:
#* +1 : For
#* +0: Mildly for
#* 0: Indifferent
#* -0: Mildly against
#* -1 : Strongly against. This is expected to be accompanied by a reason and alternative proposal.
# Everyday topics will be decided by an open vote of all members in a clearly designated separate mail thread over a minimum of 2 business days with a minimum participation of 3 votes.
# For major decisions, such as conference venue selection, a minimum of one week shall be allocated to try and ensure at least 50% voter participation.
# The committee aims for consensus, and will specifically attempt to address all -1 votes, but will revert to a majority vote where necessary.
# The result will be clearly declared afterwards.
# Secret voting, when required, will use an online voting service or use an email to an independent teller appointed by CC Chair.

==FOSS4G Selection==

# All Letters of Intent and subsequent proposals will be posted to the list for open comment by all.
# The selection of the winning proposal is by secret vote of conference committee members.
# The OSGeo Board will be requested to ratify the conference committee’s recommendation.
# Any committee member who has a potential conflict of interest is expected to withdraw from voting. A member of the committee who is part of a bidding team, intends to become part of the LOC or is employed by a company playing an active part in a bid should exclude themselves from voting in the selection process. In the event of a disagreement regarding a potential conflict of interest the committee chair has the authority to make a decision.

=== Changes in RfP Document for 2021 ===
* At least at the letters-of-intent stage there should always be a voting option of "None of the above". Otherwise there's no point in having a vote if there's only one letter, also this allows for the (unlikely) event of all letters being rubbish.
* Bids should be scored based on various pre-defined criterion. Current voting by the committee seems to include a "where I want to go on holiday" component which has no place in a process like this. This is in keeping with the "openness" goal of OSGeo as compared to the current Star Chamber-like voting.
* Further to the above, a list of objective mandatory criterion can be specified as required. I.e. "Venue must be able to host X people", "must be at least Y tracks", "Must be accessible via both local and national public transport", etc.

==FOSS4G Travel Grant Programme==

The FOSS4G TGP was started in 2017 with funding from the OSGeo Board and a crowd funding initiative. The Conference Committee is tasked with managing this grant programme for the Global FOSS4G and for any Regional FOSS4G's that request assistance

* [[FOSS4G Travel Grant Programme 2017 | 2017]]
* [[FOSS4G Travel Grant Programme 2018 | 2018]]

=== Setting up a FOSS4G TGP ===

Some guidance notes are available in the [[FOSS4G Travel Grant Programme Cookbook | FOSS4G Travel Grant Programme Cookbook]]

==Membership==

# To ensure voting control for key decisions remains with experienced people, the committee aims for more than 50% of members to be chairs (or vice chairs) of past FOSS4G global events. The chair of the most recent FOSS4G event will automatically be invited to become a member but still requires a motion and vote.
# The conference committee aims to retain a chair or vice-chair from the 5 most recent global FOSS4G conferences.
# The remaining membership, less than 50% of members, is open, ideally attracting chairs or LOC members from past Global or Regional FOSS4G or related conferences.
# Each year, prior to releasing the Global FOSS4G RfP, the membership list shall be re-visited.
## Existing members shall be asked whether they wish to continue on the committee. If a member doesn't respond, after a number of attempts to contact them, they shall be retired.
## Interested people may be suggested, or request to be voted onto the conference committee.
## If less than 50% of membership would be past global FOSS4G chair/vice chairs, then non global FOSS4G chair/vice chair positions shall be up for re-election.
## Election of conference committee members is by secret vote by the existing conference committee and board members who are not already members of the conference committee. Voters will vote Yes/No/Abstain for each candidate. Voters may select "Yes" for up to the number of positions available.
# Votes will be secret either using an online voting system or by email to a designated teller who is not a voter. The mechanism will be selected by the committee chair.

== Current Members ==

# [[User:pmbatty | Peter Batty]] - member since 2011 (chair of Global FOSS4G 2011)
# [[User:Bitner | David Bitner]] (chair of the 2013 FOSS4GNA)
# [[User:Maria | Maria Brovelli]] - member since March 2016 (Chair FOSS4G Europe 2015)
# [[User:Vasile | Vasile Craciunescu]] - '''Co-Chair''' - member since July 2013 (chair of FOSS4G Central and Eastern Europe 2013)
# David Fawcett (Programme Team FOSS4GNA 2013)
# [[User:GFleming |Gavin Fleming]] - (chair of Global FOSS4G 2008)
# Darrell Fuhriman (chair of Global FOSS4G 2014)
# Claude Philipona - (chair of Global FOSS4G 2006)
# [[User:Venkat | Venkatesh Raghavan]] - member since Oct. 2006 (Chair FOSS4G-2004, FOSS4G-Asia 2014)
# [[User:Pwramsey3 | Paul Ramsey]] - Chair of global FOSS4G 2007
# [[User:Sanghee | Sanghee Shin]] - member since 2015 (chair of Global FOSS4G 2015)
# [[User:Gsteinmon | Guido Stein]] - member since February 2018 (chair of Global FOSS4G 2017)
# [[User:MichaelTerner | Michael Terner]] - member since February 2018 (chair of Global FOSS4G 2017)
# Msilikale Msilanga - '''Co-Chair''' - member since September 2018 (co-chair of Global FOSS4G 2018)
# Mark Iliffe - member since September 2018 (co-chair of Global FOSS4G 2018)
# [[User:Delawen | María Arias de Reyna Domínguez]] - member since November 2021 (chair of Global FOSS4G 2021)
# [[User:Lucadelu | Luca Delucchi]] - member since October 2022 (chair of Global FOSS4G 2022)
* [https://lists.osgeo.org/pipermail/conference_dev/2019-December/005411.html Motion for co-chairs]

== Past Members ==

# Jeff McKenna
# Lorenzo Becchi
# Allan Doyle
# Olivier Ertz
# Alain Grignon
# Luc Maurer
# Daniel Rappo
# Dave Patton
# Rafael Medeiros Sperb
# Arnulf Christl
# [[Markus Neteler]]
# Steve Lime
# Frank Warmerdam
# [[User:Davemac | Dave McIlhagga]] (resigned August 2016)
# [[User:Ticheler | Jeroen Ticheler]] (resigned September 2016)
# [[User:Thierry Badard | Thierry Badard]] (resigned September 2016)
# [[User:Helena | Helena Mitasova]] (resigned September 2016)
# [[User:Camerons | Cameron Shorter]] - member from 2009 to Oct 2017 (chair of Global FOSS4G 2009)
# [[User:Jachym | Jachym Cepicky]] - (resigned August 2019)
# [[User:Till Adams | Till Adams]] - resigned October 2022 / member since September 2016 (chair of Global FOSS4G 2016)
# [[User:Stevenfeldman | Steven Feldman]] - resigned October 2022 / member since October 2013 (chair of Global FOSS4G 2013)
# [[User:EliL | Eli Adam]] - resigned [https://lists.osgeo.org/pipermail/conference_dev/2022-October/005859.html October 2022] / member since [https://lists.osgeo.org/pipermail/conference_dev/2015-January/002811.html January 2015] (1 of 4 co-chairs of Global FOSS4G 2014)

= Meetings =

* Meetings occur in IRC in the #foss4g channel (on irc.freenode.net) or by other means organized on the email list. Meetings are infrequent.
* <s>As of 2016 the [[Conference_Committee_Meetings | Conference Committee Meetings]] page was not being maintained any more.</s>

=2023 Pages=
* [[FOSS4G_2023_Bid_Process | 2023 RFP schedule]]

=2022 Pages=

* [[FOSS4G_2022_Bid_Process | 2022 RFP schedule]]

=2021 Pages=

* [[FOSS4G_2021_Bid_Process | 2021 RFP schedue]]

=2020 Pages=

* [[FOSS4G_2020_Bid_Process | 2020 RFP schedue]]

=2019 Pages=

* [[FOSS4G_2019_Bid_Process | 2019 RFP schedule]]

=2018 Pages=

* [[FOSS4G_2018_Bid_Process | 2018 RFP schedule]]
* [[Conference_Committee_F2F_2016 | Conference Committee Face to Face meeting in Bonn, 2016]]

= 2017 Pages =

* [[FOSS4G_2017_Bid_Process | 2017 RFP schedule]]
* [[FOSS4G_Travel_Grant_Programme_2017 | 2017 Travel Grant Programme]]

= 2016 Pages =

* [http://www.osgeo.org/conference/rfp/ 2016 RFP schedule]

= 2015 Pages =

* [[FOSS4G 2015 Bid Process]]

= 2014 Pages =

* [[FOSS4G 2014 Bid Process]]
* [[FOSS4G 2014]]
* [[FOSS4G Europe 2014]]

= 2013 Pages =

* Main page: [[FOSS4G_2013]]
* [http://svn.osgeo.org/osgeo/foss4g/2013/documents/FOSS4G_2013_UK_Proposal-Final_version.pdf 2013 Proposal]
* Reflections on the event by the LOC (includes lessons learnt and supersedes the old Lessons Learned page): [[FOSS4G2013_Reflections_by_the_LOC]]

= 2012 Pages =
Main page: [[FOSS4G 2012]]
* RFP ([http://svn.osgeo.org/osgeo/foss4g/rfp/2012/osgeo-conference-2012-request-for-proposal.odt OpenOffice], [http://svn.osgeo.org/osgeo/foss4g/rfp/2012/osgeo-conference-2012-request-for-proposal.pdf pdf])
* budget template ([http://svn.osgeo.org/osgeo/foss4g/rfp/2012/osgeo-conference-budget-template.ods OpenOffice])
* Important dates:
** Letters of Intent (Stage 1) due: 2011-06-30 ([http://www.timeanddate.com/worldclock/fixedtime.html?year=2011&month=06&day=30&hour=23&min=0&sec=0 23:00 UTC])
** Stage 1 question period: 2011-06-30 to 2011-07-07
** Stage 1 decision: 2011-07-07
** Proposals (Stage 2) due: 2011-08-01 ([http://www.timeanddate.com/worldclock/fixedtime.html?year=2011&month=08&day=01&hour=23&min=0&sec=0 23:00 UTC])
** Stage 2 question period: 2011-08-01 to 2011-08-05
** Final decision: 2011-08-05

= 2011 Pages =

* [http://www.osgeo.org/conference/rfp RFP and Letters of Intent]
* [[FOSS4G_2011_Bid_Process | 2011 Bid Process]]
* [[FOSS4G Reboot 2011 | Initial thoughts on 2011 required changes]]

= 2010 Pages =

* [http://www.osgeo.org/conference/rfp RFP and Proposals]
* [[Conference_Committee_2010_Bid_Questions | Bid Questions]]
* [[Conference_Committee_2010_Voting_Process | Voting Process]]

= 2009 Pages =

* [[FOSS4G 2009 Governance]]
* All [http://wiki.osgeo.org/wiki/Category:FOSS4G2009 FOSS4G 2009] pages.

= 2008 Pages =

* [http://www.osgeo.org/conference/rfp RFP and Proposals]
* [http://lists.osgeo.org/pipermail/conference_dev/2007-July/000355.html Voting Process]
* [[FOSS4G 2008 Governance]]
* [[FOSS4GLOC matters]]
* [http://spreadsheets.google.com/pub?key=p6mc38S7PA8lHWRQuIgExDA Workshop and lab evaluations]

= 2007 Pages =

* [http://wiki.osgeo.org/index.php/Category:FOSS4G2007 Pages in category "FOSS4G2007"]
* [[FOSS4G2007]] - wiki page
* http://www.foss4g2007.org/ - Conference Site
* [http://www.osgeo.org/conference/rfp Proposals and RFP]
* [[OSGeo_Conference_RFP_2007#RFP_Response_Requirements | requirements Wiki page]]
* [[OSGeo_Conference_Naming_Results | Naming results]]
* [http://www.foss4g2007.org/bid_site/ Victoria 2007 Proposal]
* [[FOSS4G 2007 Governance]]
* [[FOSS4G2007 Lessons Learned]]

= 2006 Pages =

* [http://wiki.osgeo.org/index.php/Category:FOSS4G2006 Pages in category "FOSS4G2006"]
* http://www.foss4g2006.org/ - Conference Site
* [[FOSS4G2006]] information

= Event Policy Pages =

* [[Official_OSGeo_Event_Policy | OSGeo Event policy]] (in review)
* [[OSGeo_Conference_Policy | Board notes]] regarding event policy
* [http://www.osgeo.org/code_of_conduct OSGeo Code of Conduct]

[[Category:FOSS4G]]
[[Category:Committees]]
[[Category:Conference Committee]]

Conference Committee

2022-02-02T18:39:09Z

Elil: /* 2022 Pages */ add link to 2023 pages

The Conference Committee is the official committee of OSGeo responsible for operating the annual [[FOSS4G]] conferences.

= Noteworthy Documents =

* [[FOSS4G Handbook]] (provides guidance to future FOSS4G and related events, based upon the collective wisdom gained during prior events)
* [http://lists.osgeo.org/mailman/listinfo/conference_dev Conference Committee email list]
* [http://www.osgeo.org/conference OSGeo Conference Committee main page] (includes RFP, proposals, and archived files from past conferences)
* Past conference reports are detailed at [[Past FOSS4G Reports]]
* [[Conference website management]]
* [[Motion to form Conference Committee]]
* [[Conference Committee Budget 2017 | Conference Committee Budget 2017 (draft)]]

= Goals =
The conference committee have the responsibility to:
* Run the selection process and voting for the global FOSS4G
* Vote on conference related proposals submitted to the committee
* Retain the [[FOSS4G Handbook | collected wisdom]] for FOSS4G and related events
* Advise the board, Local Organising Committees (LOC), and related events organisors, ideally referencing the [[FOSS4G Handbook]]
* Ensure OSGeo foundation principles are applied to global FOSS4G conferences
* Manage the FOSS4G Travel Grant Programme for FOSS4G and regional events

See also: '''2016 priorities are summarised in [[Conference Committee 2016 Priorities]]'''

=Housekeeping Procedures=
The Conference Committee uses the following procedures to make decisions.

==Decisions==

[[consideration for new selection methods]]

# Anyone may contribute to conference committee discussions. All votes will be noted, but only conference committee member votes count toward decisions.
# Voting will use convention of:
#* +1 : For
#* +0: Mildly for
#* 0: Indifferent
#* -0: Mildly against
#* -1 : Strongly against. This is expected to be accompanied by a reason and alternative proposal.
# Everyday topics will be decided by an open vote of all members in a clearly designated separate mail thread over a minimum of 2 business days with a minimum participation of 3 votes.
# For major decisions, such as conference venue selection, a minimum of one week shall be allocated to try and ensure at least 50% voter participation.
# The committee aims for consensus, and will specifically attempt to address all -1 votes, but will revert to a majority vote where necessary.
# The result will be clearly declared afterwards.
# Secret voting, when required, will use an online voting service or use an email to an independent teller appointed by CC Chair.

==FOSS4G Selection==

# All Letters of Intent and subsequent proposals will be posted to the list for open comment by all.
# The selection of the winning proposal is by secret vote of conference committee members.
# The OSGeo Board will be requested to ratify the conference committee’s recommendation.
# Any committee member who has a potential conflict of interest is expected to withdraw from voting. A member of the committee who is part of a bidding team, intends to become part of the LOC or is employed by a company playing an active part in a bid should exclude themselves from voting in the selection process. In the event of a disagreement regarding a potential conflict of interest the committee chair has the authority to make a decision.

=== Changes in RfP Document for 2021 ===
* At least at the letters-of-intent stage there should always be a voting option of "None of the above". Otherwise there's no point in having a vote if there's only one letter, also this allows for the (unlikely) event of all letters being rubbish.
* Bids should be scored based on various pre-defined criterion. Current voting by the committee seems to include a "where I want to go on holiday" component which has no place in a process like this. This is in keeping with the "openness" goal of OSGeo as compared to the current Star Chamber-like voting.
* Further to the above, a list of objective mandatory criterion can be specified as required. I.e. "Venue must be able to host X people", "must be at least Y tracks", "Must be accessible via both local and national public transport", etc.

==FOSS4G Travel Grant Programme==

The FOSS4G TGP was started in 2017 with funding from the OSGeo Board and a crowd funding initiative. The Conference Committee is tasked with managing this grant programme for the Global FOSS4G and for any Regional FOSS4G's that request assistance

* [[FOSS4G Travel Grant Programme 2017 | 2017]]
* [[FOSS4G Travel Grant Programme 2018 | 2018]]

=== Setting up a FOSS4G TGP ===

Some guidance notes are available in the [[FOSS4G Travel Grant Programme Cookbook | FOSS4G Travel Grant Programme Cookbook]]

==Membership==

# To ensure voting control for key decisions remains with experienced people, the committee aims for more than 50% of members to be chairs (or vice chairs) of past FOSS4G global events. The chair of the most recent FOSS4G event will automatically be invited to become a member but still requires a motion and vote.
# The conference committee aims to retain a chair or vice-chair from the 5 most recent global FOSS4G conferences.
# The remaining membership, less than 50% of members, is open, ideally attracting chairs or LOC members from past Global or Regional FOSS4G or related conferences.
# Each year, prior to releasing the Global FOSS4G RfP, the membership list shall be re-visited.
## Existing members shall be asked whether they wish to continue on the committee. If a member doesn't respond, after a number of attempts to contact them, they shall be retired.
## Interested people may be suggested, or request to be voted onto the conference committee.
## If less than 50% of membership would be past global FOSS4G chair/vice chairs, then non global FOSS4G chair/vice chair positions shall be up for re-election.
## Election of conference committee members is by secret vote by the existing conference committee and board members who are not already members of the conference committee. Voters will vote Yes/No/Abstain for each candidate. Voters may select "Yes" for up to the number of positions available.
# Votes will be secret either using an online voting system or by email to a designated teller who is not a voter. The mechanism will be selected by the committee chair.

== Current Members ==

# [[User:EliL | Eli Adam]] - member since [https://lists.osgeo.org/pipermail/conference_dev/2015-January/002811.html January 2015] (1 of 4 co-chairs of Global FOSS4G 2014)
# [[User:Till Adams | Till Adams]] - member since September 2016 (chair of Global FOSS4G 2016)
# [[User:pmbatty | Peter Batty]] - member since 2011 (chair of Global FOSS4G 2011)
# [[User:Bitner | David Bitner]] (chair of the 2013 FOSS4GNA)
# [[User:Maria | Maria Brovelli]] - member since March 2016 (Chair FOSS4G Europe 2015)
# [[User:Vasile | Vasile Craciunescu]] - '''Co-Chair''' - member since July 2013 (chair of FOSS4G Central and Eastern Europe 2013)
# David Fawcett (Programme Team FOSS4GNA 2013)
# [[User:Stevenfeldman | Steven Feldman]] - member since October 2013 (chair of Global FOSS4G 2013)
# [[User:GFleming |Gavin Fleming]] - (chair of Global FOSS4G 2008)
# Darrell Fuhriman (chair of Global FOSS4G 2014)
# Claude Philipona - (chair of Global FOSS4G 2006)
# [[User:Venkat | Venkatesh Raghavan]] - member since Oct. 2006 (Chair FOSS4G-2004, FOSS4G-Asia 2014)
# [[User:Pwramsey3 | Paul Ramsey]] - Chair of global FOSS4G 2007
# [[User:Sanghee | Sanghee Shin]] - member since 2015 (chair of Global FOSS4G 2015)
# [[User:Gsteinmon | Guido Stein]] - member since February 2018 (chair of Global FOSS4G 2017)
# [[User:MichaelTerner | Michael Terner]] - member since February 2018 (chair of Global FOSS4G 2017)
# Msilikale Msilanga - '''Co-Chair''' - member since September 2018 (co-chair of Global FOSS4G 2018)
# Mark Iliffe - member since September 2018 (co-chair of Global FOSS4G 2018)
# [[User:Delawen | María Arias de Reyna Domínguez]] - member since November 2021 (chair of Global FOSS4G 2021)
* [https://lists.osgeo.org/pipermail/conference_dev/2019-December/005411.html Motion for co-chairs]

== Past Members ==

# Lorenzo Becchi
# Allan Doyle
# Olivier Ertz
# Alain Grignon
# Luc Maurer
# Daniel Rappo
# Dave Patton
# Rafael Medeiros Sperb
# [[Jeff McKenna]]
# Arnulf Christl
# [[Markus Neteler]]
# Steve Lime
# Frank Warmerdam
# [[User:Davemac | Dave McIlhagga]] (resigned August 2016)
# [[User:Ticheler | Jeroen Ticheler]] (resigned September 2016)
# [[User:Thierry Badard | Thierry Badard]] (resigned September 2016)
# [[User:Helena | Helena Mitasova]] (resigned September 2016)
# [[User:Camerons | Cameron Shorter]] - member from 2009 to Oct 2017 (chair of Global FOSS4G 2009)
# [[User:Jachym | Jachym Cepicky]] - (resigned August 2019)

= Meetings =

* Meetings occur in IRC in the #foss4g channel (on irc.freenode.net) or by other means organized on the email list. Meetings are infrequent.
* <s>As of 2016 the [[Conference_Committee_Meetings | Conference Committee Meetings]] page was not being maintained any more.</s>

=2023 Pages=
* [[FOSS4G_2023_Bid_Process | 2023 RFP schedule]]

=2022 Pages=

* [[FOSS4G_2022_Bid_Process | 2022 RFP schedule]]

=2021 Pages=

* [[FOSS4G_2021_Bid_Process | 2021 RFP schedue]]

=2020 Pages=

* [[FOSS4G_2020_Bid_Process | 2020 RFP schedue]]

=2019 Pages=

* [[FOSS4G_2019_Bid_Process | 2019 RFP schedule]]

=2018 Pages=

* [[FOSS4G_2018_Bid_Process | 2018 RFP schedule]]
* [[Conference_Committee_F2F_2016 | Conference Committee Face to Face meeting in Bonn, 2016]]

= 2017 Pages =

* [[FOSS4G_2017_Bid_Process | 2017 RFP schedule]]
* [[FOSS4G_Travel_Grant_Programme_2017 | 2017 Travel Grant Programme]]

= 2016 Pages =

* [http://www.osgeo.org/conference/rfp/ 2016 RFP schedule]

= 2015 Pages =

* [[FOSS4G 2015 Bid Process]]

= 2014 Pages =

* [[FOSS4G 2014 Bid Process]]
* [[FOSS4G 2014]]
* [[FOSS4G Europe 2014]]

= 2013 Pages =

* Main page: [[FOSS4G_2013]]
* [http://svn.osgeo.org/osgeo/foss4g/2013/documents/FOSS4G_2013_UK_Proposal-Final_version.pdf 2013 Proposal]
* Reflections on the event by the LOC (includes lessons learnt and supersedes the old Lessons Learned page): [[FOSS4G2013_Reflections_by_the_LOC]]

= 2012 Pages =
Main page: [[FOSS4G 2012]]
* RFP ([http://svn.osgeo.org/osgeo/foss4g/rfp/2012/osgeo-conference-2012-request-for-proposal.odt OpenOffice], [http://svn.osgeo.org/osgeo/foss4g/rfp/2012/osgeo-conference-2012-request-for-proposal.pdf pdf])
* budget template ([http://svn.osgeo.org/osgeo/foss4g/rfp/2012/osgeo-conference-budget-template.ods OpenOffice])
* Important dates:
** Letters of Intent (Stage 1) due: 2011-06-30 ([http://www.timeanddate.com/worldclock/fixedtime.html?year=2011&month=06&day=30&hour=23&min=0&sec=0 23:00 UTC])
** Stage 1 question period: 2011-06-30 to 2011-07-07
** Stage 1 decision: 2011-07-07
** Proposals (Stage 2) due: 2011-08-01 ([http://www.timeanddate.com/worldclock/fixedtime.html?year=2011&month=08&day=01&hour=23&min=0&sec=0 23:00 UTC])
** Stage 2 question period: 2011-08-01 to 2011-08-05
** Final decision: 2011-08-05

= 2011 Pages =

* [http://www.osgeo.org/conference/rfp RFP and Letters of Intent]
* [[FOSS4G_2011_Bid_Process | 2011 Bid Process]]
* [[FOSS4G Reboot 2011 | Initial thoughts on 2011 required changes]]

= 2010 Pages =

* [http://www.osgeo.org/conference/rfp RFP and Proposals]
* [[Conference_Committee_2010_Bid_Questions | Bid Questions]]
* [[Conference_Committee_2010_Voting_Process | Voting Process]]

= 2009 Pages =

* [[FOSS4G 2009 Governance]]
* All [http://wiki.osgeo.org/wiki/Category:FOSS4G2009 FOSS4G 2009] pages.

= 2008 Pages =

* [http://www.osgeo.org/conference/rfp RFP and Proposals]
* [http://lists.osgeo.org/pipermail/conference_dev/2007-July/000355.html Voting Process]
* [[FOSS4G 2008 Governance]]
* [[FOSS4GLOC matters]]
* [http://spreadsheets.google.com/pub?key=p6mc38S7PA8lHWRQuIgExDA Workshop and lab evaluations]

= 2007 Pages =

* [http://wiki.osgeo.org/index.php/Category:FOSS4G2007 Pages in category "FOSS4G2007"]
* [[FOSS4G2007]] - wiki page
* http://www.foss4g2007.org/ - Conference Site
* [http://www.osgeo.org/conference/rfp Proposals and RFP]
* [[OSGeo_Conference_RFP_2007#RFP_Response_Requirements | requirements Wiki page]]
* [[OSGeo_Conference_Naming_Results | Naming results]]
* [http://www.foss4g2007.org/bid_site/ Victoria 2007 Proposal]
* [[FOSS4G 2007 Governance]]
* [[FOSS4G2007 Lessons Learned]]

= 2006 Pages =

* [http://wiki.osgeo.org/index.php/Category:FOSS4G2006 Pages in category "FOSS4G2006"]
* http://www.foss4g2006.org/ - Conference Site
* [[FOSS4G2006]] information

= Event Policy Pages =

* [[Official_OSGeo_Event_Policy | OSGeo Event policy]] (in review)
* [[OSGeo_Conference_Policy | Board notes]] regarding event policy
* [http://www.osgeo.org/code_of_conduct OSGeo Code of Conduct]

[[Category:FOSS4G]]
[[Category:Committees]]
[[Category:Conference Committee]]

OSGeo Budget 2022

2021-12-30T15:11:46Z

Elil: /* OSGeo Projects */ GeoMoose 2022 budget request

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

Total Approved Budget for 2022: $126,700 USD

Total spending for 2021: TBD

Total Approved Budget for 2022: 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
! 2021 Approved
! 2021 Actual
! 2022 Approved
! 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;" | 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 2020: $16,000 USD

Total Board spending for 2020: TBD

Total Board Budget for 2021: TBD

== OSGeo Committees ==

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

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

{|class="wikitable" border="2" cellspacing="0" cellpadding="6" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;"
|-
! OSGeo Committees
! 2021 Approved [Requested]
! 2021 Actual
! 2022 Approved [Requested]
! Notes
|-
| SAC
| style="text-align:right;" | 30,700 [35,100]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| Open GeoScience
| style="text-align:right;" | 2,500 [5,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;" | 10,000 [15,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoForAll
| style="text-align:right;" | 3,000 [3,140]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| UN Committee
| style="text-align:right;" | 6,000 [9,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| Incubation Committee
| style="text-align:right;" | 5,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|}

Total Committees Budget for 2021: $57,200 USD

Total Committees spending for 2021: TBD

Total Committees Budget for 2022: 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
! 2021 Approved
! 2021 Actual
! 2022 Approved
! Notes
|-
| FOSS4G
| style="text-align:right;" | 0
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Managed by Conference Committee. Seed money for 2022 will be allocated by the board when estimate numbers become available.
|-
| Local Chapters
| style="text-align:right;" | 2,000
| 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;" | 5,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| Managed by Conference Committee. TGP, 50-60% for global event, rest for regional events. LOC's are expected to raise matching funding from sponsors or delegates and provide free conference passes. Board note: gvSIG can apply for Travel grant here for their event.
|-
| Events and Code Sprints
| style="text-align:right;" | 15,000
| style="text-align:right;" | 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 23-25 projects expected in 2021 (see list below). Board note: Budgeted approx. 300$ for each project. To be amended if we hit the ceiling of the budget.
|
|}

Total Initiatives Budget for 2021: $27,000 USD

Total Initiatives spending for 2021: TBD

Total Initiatives Budget for 2022: 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 (2021) 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 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
! 2021 Approved [Requested]
! 2021 Actual
! 2022 Approved [Requested]
! Notes
|-
| deegree
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GDAL/OGR
| style="text-align:right;" | 2,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoMOOSE
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | [2,500]
| https://github.com/geomoose/geomoose/wiki/PSC-Meeting-2021-10-15
|-
| GeoNetwork
| style="text-align:right;" | 2,000 [2,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;" | 2,000 [3,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GeoTools
| style="text-align:right;" | 2,000 [5,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| GRASS GIS
| style="text-align:right;" | 2,000 [2,500]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| gvSIG
| style="text-align:right;" | 2,000 [4,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| Mapbender
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| MapServer
| style="text-align:right;" | 2,000
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| Marble
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| OpenLayers
| style="text-align:right;" | 2,000 [3,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| 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;" | TBD
| style="text-align:right;" | TBD
|
|-
| pycsw
| style="text-align:right;" | 2,000
| style="text-align:right;" | 1,950
| style="text-align:right;" | TBD
| https://github.com/geopython/pycsw/wiki/OSGeo-Budget-2022
|-
| PyWPS
| style="text-align:right;" | 500
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|-
| QGIS
| style="text-align:right;" | 3,000 [10,000]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
|
|}

Total Projects Budget for 2021: $26,500 USD

Total Projects spending for 2022: TBD

Total Projects Budget for 2022: 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
! 2021 Approved [Requested]
! 2021 Actual
! 2022 Approved [Requested]
! Notes
|-
| pgRouting
| style="text-align:right;" | 300 [4,500]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| ([https://wiki.osgeo.org/wiki/PgRouting_Budget#2021 link]) 2021 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 [4,500]
| style="text-align:right;" | TBD
| style="text-align:right;" | TBD
| ([https://wiki.osgeo.org/wiki/Istsos_Budget_2021 link]) 2021 Board note: 300 USD approved from Community Projects budget. For more budget the project has to ask incubation committee.
|-
| pygeoapi
| style="text-align:right;" | 300
| style="text-align:right;" | 132
| style="text-align:right;" | TBD
| https://github.com/geopython/pygeoapi/wiki/OSGeo-Budget-2022
|-
|}

= Events =

== Community Events ==

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

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

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

== Code Sprints ==

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

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

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

= Approval and Amendments =

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

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

IRC

2021-06-18T15:57:50Z

Elil: /* Projects */ update geomoose to libera

Much OSGeo related communication happens in IRC (Internet Relay Chat), an instant messaging protocol. Lots of general information on IRC is available in [http://en.wikipedia.org/wiki/Internet_Relay_Chat Wikipedia].

== Clients ==

IRC requires IRC client software. There are a wide variety of clients available:

=== Desktop IRC clients ===

* A nice IRC client is for example https://hexchat.github.io/
* Thunderbird (email client) has a great IRC client that is included in the default installation: see https://support.mozilla.org/en-US/kb/instant-messaging-and-chat

=== Browser IRC plugins ===

* Chrome has several IRC apps/extensions, including [https://chrome.google.com/webstore/detail/circ/bebigdkelppomhhjaaianniiifjbgocn CIRC]
* <del>The [https://addons.mozilla.org/en-US/firefox/addon/chatzilla/ ChatZilla] client is available for Firefox users on all platforms.</del> (not supported as of Firefox Quantum version in 2017)

=== Web based IRC ===
IRC uses a TCP/IP port which is often blocked in environments with strictly managed internet access. In these environments it is still possible to use http based clients such as:

* https://web.libera.chat/ - For Libera.Chat channels
* http://webchat.freenode.net/ - For Freenode channels (being migrated over Libera.Chat)
* https://kiwiirc.com/client/

=== Matrix bridges ===
Many IRC channels are also bridged to [[Matrix]] rooms

IRC ops may find the following document useful to make life easier for Matrix users:
https://github.com/matrix-org/matrix-appservice-irc/wiki/End-user-FAQ#i-am-a-chanop-and-have-a-spam-problem-how-can-i-fix-it-without-affecting-matrix-users

== Channels ==

The primary OSGeo IRC channel is [irc://irc.libera.chat/#osgeo #osgeo] on the Libera.Chat network.

Other channels of interest:

=== Infrastructure ===

* [irc://irc.libera.chat/#osgeo-sac #osgeo-sac] - [[SAC|OSGeo system administrator committee]]

=== Projects ===

* [irc://irc.freenode.net/#drupal-geo #drupal-geo] - [http://groups.drupal.org/location-and-mapping Drupal GEO]
* [irc://irc.freenode.net/#fdo #fdo] - [http://fdo.osgeo.org/ Feature Data Objects]
* [irc://irc.freenode.net/#featureserver #featureserver] - [http://featureserver.org/ FeatureServer]
* [irc://irc.freenode.net/#gdal #gdal] - [http://www.gdal.org GDAL/OGR] project (as well as FWTools, PROJ.4)
* [irc://irc.libera.chat/#geomoose #geomoose] - [https://www.geomoose.org/ GeoMOOSE]
* [irc://irc.freenode.net/#geonetwork #geonetwork] - [http://geonetwork-opensource.org/ Geonetwork Open Source]
* [irc://irc.freenode.net/#geotools #geotools] - [http://www.geotools.org GeoTools] (also to some extent GeoServer, uDig)
* [irc://irc.freenode.net/#grass #grass] - [http://grass.osgeo.org/ GRASS GIS]
* [irc://irc.freenode.net/#mapbender #mapbender] - [http://www.osgeo.org/mapbender Mapbender]
* [irc://irc.freenode.net/#mapguide #mapguide] - [http://mapguide.osgeo.org/ MapGuide Open Source] (and Enterprise)
* [irc://irc.freenode.net/#mapserver #mapserver] - [http://www.osgeo.org/mapserver MapServer] and some MapServer based frameworks
* [irc://irc.freenode.net/#openlayers #openlayers] - [http://www.osgeo.org/openlayers OpenLayers]
* [irc://irc.freenode.net/#osgeolive #osgeolive] - [[Live GIS Disc]]
* [irc://irc.freenode.net/#ossimplanet #ossimplanet] - [http://www.osgeo.org/ossim OSSIM] project
* [irc://irc.libera.chat/#postgis #postgis] - [http://postgis.net/ PostGIS]
* [irc://irc.libera.chat/#osgeo-geos #osgeo-geos] - [http://geos.osgeo.org/ GEOS]
* [irc://irc.freenode.net/#pycsw #pycsw] - [http://pycsw.org/ pycsw]
* [irc://irc.libera.chat/#qgis #qgis] - [http://www.qgis.org/ QGIS]
* [irc://irc.freenode.net/#zoo-project #zoo-project] - [http://www.zoo-project.org/ ZOO-Project]

=== Local Chapters ===

* [irc://irc.freenode.net/#osgeo-es #osgeo-es] - Capítulo Local de la comunidad [[Español|hispano-hablante]]
* [irc://irc.freenode.net/#cugos #cugos] - [[Cascadia|Cascadia Users of Geospatial Open Source]]
* [irc://irc.freenode.net/#osgeo-europe #osgeo-europe] - [[Europe| Europe OSGeo Chapter]]
* [irc://irc.freenode.net/#fossgis #fossgis] - [[D-A-CH|German language]] OSGeo chapter ([http://logs.qgis.org/fossgis logs])
* [irc://irc.freenode.net/#osgeo-fr #osgeo-fr] - [[Francophone OSGeo Chapter]]
* [irc://irc.freenode.net/#osgeo-it #osgeo-it] (former #gfoss) - [[Italiano|Italian language]] OSGeo Chapter
* [irc://irc.freenode.net/#osgeo-phl #osgeo-phl] - [[Philadelphia|Philadelphia area]] OSGeo Chapter
* [irc://irc.freenode.net/#osgeo-pdx #osgeo-pdx] [[PDX-OSGEO|Portland Chapter]]
* [irc://irc.freenode.net/#osgeo-pt #osgeo-pt] - [[Portugal]] OSGeo Chapter (use [http://webchat.freenode.net webchat] se não tiver um cliente IRC, e preencha o nome e o canal '''#osgeo-pt''')
* [irc://irc.freenode.net/#osgeo-qc #osgeo-qc] - [[Quebec| Quebec OSGeo Chapter]]
* [irc://irc.freenode.net/#osgeo-ro #osgeo-ro] - [[Romanian| Romanian OSGeo Chapter]]
* [irc://irc.freenode.net/#geoinquietos #geoinquietos] - [[:Category:Iniciativas_Locales| Spanish OSGeo micro chapters]]

=== Initiatives ===

* [irc://irc.freenode.net/#osgeo-gci #osgeo-gci] Google Code-In (GCI) discussions ''(connect through [http://webchat.freenode.net/?channels=osgeo-gci Webchat])''
* [irc://irc.freenode.net/#osgeo-gsoc #osgeo-gsoc] Summer of Code (GSoC) discussions ''(connect through [http://webchat.freenode.net/?channels=osgeo-gsoc Webchat])''

=== Events ===

* [irc://irc.freenode.net/#foss4g #foss4g] - [http://foss4g.org FOSS4G] conference organization & discussions
* [irc://irc.freenode.net/#tosprint #tosprint] OSGeo Code Sprint

=== Other ===

* [irc://irc.freenode.net/#geojson #geojson]
* [irc://irc.freenode.net/#kml #kml]
* [irc://irc.freenode.net/#moss4g #moss4g]

== NickServ ==

Due to spam the FreeNode channels now require you to identify a nickname with the "NickServ" bot before you are able to post any messages.

* https://freenode.net/kb/answer/registration

== Etiquette ==

* Don't ask to ask, just go ahead and ask your question.
* Don't paste large chunks of text into IRC channels. If you want to present a code or configuration file snippet to others to look at use a "pasting service" like http://codepad.org/ or http://osgeo.pastebin.com/ to host the snippet, and then paste the url to it into the IRC channel.
* If you want the attention of a particular person, include their nick in the message and they will generally be alerted (flashed, bell rung, etc).
* Give folks a while to respond. They are usually multi-tasking and might not look at IRC for a while.
* If an active conversation is going on, wait for a lull to raise a different topic (a minute of inactivity for instance)

== Logs ==

Many popular OSGeo related channels are logged. The #osgeo channel logs are at:

http://irclogs.geoapt.com/osgeo

Other logs may also be found under:

http://irclogs.geoapt.com/<add project name>

<del>Some channels (ie. #mapserver and #osgeo) are also logged on IRSeek (http://www.irseek.com), an IRC search engine.</del>

== Administration and Ops ==

The "osgeo" group on freenode now has Mateusz, Angelos, jmckenna, and strk as primary contacts and co-founder of all of the currently registered channels [https://lists.osgeo.org/pipermail/sac/2017-February/008037.html [1<nowiki>]</nowiki>]:

#osgeo
#osgeo-commits
#osgeo-fr
#osgeo-gr
#osgeo-gsoc
#osgeo-it
#osgeo-kansai
#osgeo-ro
#osgeo-sac
#osgeo-uk

== See also ==

* [[How to use irc fr]]

[[Category:Infrastructure]]

Finance Operational Notes

2021-04-26T17:44:57Z

Elil: /* Historical Overview */ update to other regions

This documented is intended to document various aspects of OSGeo's financial operations, to provide rough information on how things are setup to the treasurer, finance committee, and board.

== General ==

* Tyler as ED is responsible for day to day financial operation of OSGeo. He makes payments, issues invoices, cashes cheques, and enters transaction details into the accounting system (Quickbooks online).
* The [[Finance Committee]] is responsible for auditing financial reports, developing financial management policy, and preparing a budget for the board.
* The Treasurer chairs the Finance committee, and is responsible for operational financial decisions within the framework of the budget.
* The [[Board of Directors]] is responsible for approving a budget.

== Quick Books Online ==

OSGeo keeps detailed accounts using Quick Books Online. Currently Tyler (ED) and the Treasurer have accounts with update access for the OSGeo Quick Books instance. The rest of the finance committee has access to a read-only reporting account (contact Tyler or the Treasurer for details).

== Accounts ==
== PEO ==

== Processes ==
On monthly basis:
# Download account data, import to Quickbooks
## Include three bank accounts, paypal
# Enter credit charge charges, invoices, bill pays
# Review wire transfers, confirm sources
# Reconcile account data with cash accounts
# Pay credit card bill
# Quick summary report to Finance Committee (cash, outlook)

Quarterly:
# Reviewing sponsorship status
# Issue new or follow up on outstanding sponsor invoices
# Produce quarterly reports - income/expenses, balance sheet, summaries by class
# Submit reports to Finance Committee

Ongoing:
# Pay marketing and office bills

Annually:
# Prepare annual budget for approval by the board
# File Delaware state franchise tax
## http://corp.delaware.gov/frtax.shtml
## includes "annual report" that lists current directors
# British Columbia provincial annual report
## Filed with Pat @ Oliver & Co., Williams Lake BC
# Directors & Officers Liability insurance renewal
## Current broker: Chapman (chapmanins.com)
## Renewal date: May 13, Fill application in March/April
# Internal year end finance report
## Prepare any final invoices for the year
## Hunt down FOSS4G funds
## Reconcile to statements
# Submit report to Finance Committe
# Include official report in Annual Report
# Write Finance Committee report

== Historical Overview ==
* This section might belong somewhere else in the Finance category but this was a good place to start.
* This focuses on revenue, not expenses. Someone else could certainly fill that in since it is an important part of the finances.
* This is an overview, minor aspects are omitted. (For example GSOC is both a small income --and maybe equal expense, not sure but either way it is minor and this is a general overview.)
* This focuses on 2007-2016/7.
* The FOSS4G "years" mean nothing in the current data portrayal. FOSS4G funds coming back to OSGeo come in multiple payments over multiple years. This does show that OSGeo needs to be able to float a substantial period of time before funds return. This data should probably be sorted out and possibly analyzed on a regional (i.e. every third year) basis for Europe, North America, other Regions.

=== Data ===
* This summary comes from the help of OSGeo Treasurers. It is the source that was further generalized and used to subsequently derive these graphs.

=== Revenue Graphs ===
[[File:OSGeo_sponsorship_2007-2017.png|thumbnail|center|OSGeo Sponsorship 2007-2017]]
[[File:OSGeo_FOSS4G_2007-2017.png|thumbnail|center|OSGeo FOSS4G 2007-2017]]
[[File:FOSS4G Surpluses and Direct OSGeo Sponsorship 2.png|thumb|center|FOSS4G Surpluses and Direct OSGeo Sponsorship]]

=== Observations ===
* OSGeo sponsorship has declined to an insignificant portion of the OSGeo budget. With effort, it might be possible to increase OSGeo sponsorship again.
* FOSS4G is now essentially the sole source of OSGeo's financial existence which exerts financial pressure on FOSS4G. However, that has not always historically been the case.
* Further analysis of the FOSS4G numbers are needed to see if anything can be determined from the regions and rotation.
* The FOSS4G average is ~$81,587 from ~791 attendees (excluding 2012 for attendance) or ~$103/attendee.

==== Annual proportions 2007-2017 ====
* Blue = FOSS4G Global Surpluses
* Green = Direct sponsorship of OSGeo
<gallery>
File:OSGeo_2007.png|OSGeo proportions 2007
File:OSGeo_2008.png|OSGeo proportions 2008
File:OSGeo_2009.png|OSGeo proportions 2009
File:OSGeo_2010.png|OSGeo proportions 2010
File:OSGeo_2011.png|OSGeo proportions 2011
File:OSGeo_2012.png|OSGeo proportions 2012
File:OSGeo_2013.png|OSGeo proportions 2013
File:OSGeo_2014.png|OSGeo proportions 2014
File:OSGeo_2015.png|OSGeo proportions 2015
File:OSGeo_2016.png|OSGeo proportions 2016
File:OSGeo_2017.png|OSGeo proportions 2017
</gallery>

[[Category: Finance]]

Q&A Stage 1 Florence

2021-03-02T17:17:18Z

Elil: Clarification of dates and coordination with other conferences

Questions to LoI of the Florence Team:

Eli Adam:

# Please clarify the August 24 to 26 dates or how dates might work with other conferences. Would SotM work in that venue on the 27th (without the auditorium) and 28th? Would the price of the venue work for SotM? When would the code sprint be scheduled?

Conference Committee

2021-03-02T16:49:24Z

Elil: Add 2022

The Conference Committee is the official committee of OSGeo responsible for operating the annual [[FOSS4G]] conferences.

= Noteworthy Documents =

* [[FOSS4G Handbook]] (provides guidance to future FOSS4G and related events, based upon the collective wisdom gained during prior events)
* [http://lists.osgeo.org/mailman/listinfo/conference_dev Conference Committee email list]
* [http://www.osgeo.org/conference OSGeo Conference Committee main page] (includes RFP, proposals, and archived files from past conferences)
* Past conference reports are detailed at [[Past FOSS4G Reports]]
* [[Conference website management]]
* [[Motion to form Conference Committee]]
* [[Conference Committee Budget 2017 | Conference Committee Budget 2017 (draft)]]

= Goals =
The conference committee have the responsibility to:
* Run the selection process and voting for the global FOSS4G
* Vote on conference related proposals submitted to the committee
* Retain the [[FOSS4G Handbook | collected wisdom]] for FOSS4G and related events
* Advise the board, Local Organising Committees (LOC), and related events organisors, ideally referencing the [[FOSS4G Handbook]]
* Ensure OSGeo foundation principles are applied to global FOSS4G conferences
* Manage the FOSS4G Travel Grant Programme for FOSS4G and regional events

See also: '''2016 priorities are summarised in [[Conference Committee 2016 Priorities]]'''

=Housekeeping Procedures=
The Conference Committee uses the following procedures to make decisions.

==Decisions==

[[consideration for new selection methods]]

# Anyone may contribute to conference committee discussions. All votes will be noted, but only conference committee member votes count toward decisions.
# Voting will use convention of:
#* +1 : For
#* +0: Mildly for
#* 0: Indifferent
#* -0: Mildly against
#* -1 : Strongly against. This is expected to be accompanied by a reason and alternative proposal.
# Everyday topics will be decided by an open vote of all members in a clearly designated separate mail thread over a minimum of 2 business days with a minimum participation of 3 votes.
# For major decisions, such as conference venue selection, a minimum of one week shall be allocated to try and ensure at least 50% voter participation.
# The committee aims for consensus, and will specifically attempt to address all -1 votes, but will revert to a majority vote where necessary.
# The result will be clearly declared afterwards.
# Secret voting, when required, will use an online voting service or use an email to an independent teller appointed by CC Chair.

==FOSS4G Selection==

# All Letters of Intent and subsequent proposals will be posted to the list for open comment by all.
# The selection of the winning proposal is by secret vote of conference committee members.
# The OSGeo Board will be requested to ratify the conference committee’s recommendation.
# Any committee member who has a potential conflict of interest is expected to withdraw from voting. A member of the committee who is part of a bidding team, intends to become part of the LOC or is employed by a company playing an active part in a bid should exclude themselves from voting in the selection process. In the event of a disagreement regarding a potential conflict of interest the committee chair has the authority to make a decision.

=== Changes in RfP Document for 2021 ===
* At least at the letters-of-intent stage there should always be a voting option of "None of the above". Otherwise there's no point in having a vote if there's only one letter, also this allows for the (unlikely) event of all letters being rubbish.
* Bids should be scored based on various pre-defined criterion. Current voting by the committee seems to include a "where I want to go on holiday" component which has no place in a process like this. This is in keeping with the "openness" goal of OSGeo as compared to the current Star Chamber-like voting.
* Further to the above, a list of objective mandatory criterion can be specified as required. I.e. "Venue must be able to host X people", "must be at least Y tracks", "Must be accessible via both local and national public transport", etc.

==FOSS4G Travel Grant Programme==

The FOSS4G TGP was started in 2017 with funding from the OSGeo Board and a crowd funding initiative. The Conference Committee is tasked with managing this grant programme for the Global FOSS4G and for any Regional FOSS4G's that request assistance

* [[FOSS4G Travel Grant Programme 2017 | 2017]]
* [[FOSS4G Travel Grant Programme 2018 | 2018]]

=== Setting up a FOSS4G TGP ===

Some guidance notes are available in the [[FOSS4G Travel Grant Programme Cookbook | FOSS4G Travel Grant Programme Cookbook]]

==Membership==

# To ensure voting control for key decisions remains with experienced people, the committee aims for more than 50% of members to be chairs (or vice chairs) of past FOSS4G global events. The chair of the most recent FOSS4G event will automatically be invited to become a member but still requires a motion and vote.
# The conference committee aims to retain a chair or vice-chair from the 5 most recent global FOSS4G conferences.
# The remaining membership, less than 50% of members, is open, ideally attracting chairs or LOC members from past Global or Regional FOSS4G or related conferences.
# Each year, prior to releasing the Global FOSS4G RfP, the membership list shall be re-visited.
## Existing members shall be asked whether they wish to continue on the committee. If a member doesn't respond, after a number of attempts to contact them, they shall be retired.
## Interested people may be suggested, or request to be voted onto the conference committee.
## If less than 50% of membership would be past global FOSS4G chair/vice chairs, then non global FOSS4G chair/vice chair positions shall be up for re-election.
## Election of conference committee members is by secret vote by the existing conference committee and board members who are not already members of the conference committee. Voters will vote Yes/No/Abstain for each candidate. Voters may select "Yes" for up to the number of positions available.
# Votes will be secret either using an online voting system or by email to a designated teller who is not a voter. The mechanism will be selected by the committee chair.

== Current Members ==

# [[User:EliL | Eli Adam]] - member since [https://lists.osgeo.org/pipermail/conference_dev/2015-January/002811.html January 2015] (1 of 4 co-chairs of Global FOSS4G 2014)
# [[User:Till Adams | Till Adams]] - member since September 2016 (chair of Global FOSS4G 2016)
# [[User:pmbatty | Peter Batty]] - member since 2011 (chair of Global FOSS4G 2011)
# [[User:Bitner | David Bitner]] (chair of the 2013 FOSS4GNA)
# [[User:Maria | Maria Brovelli]] - member since March 2016 (Chair FOSS4G Europe 2015)
# [[User:Vasile | Vasile Craciunescu]] - '''Co-Chair''' - member since July 2013 (chair of FOSS4G Central and Eastern Europe 2013)
# David Fawcett (Programme Team FOSS4GNA 2013)
# [[User:Stevenfeldman | Steven Feldman]] - member since October 2013 (chair of Global FOSS4G 2013)
# [[User:GFleming |Gavin Fleming]] - (chair of Global FOSS4G 2008)
# Darrell Fuhriman (chair of Global FOSS4G 2014)
# Claude Philipona - (chair of Global FOSS4G 2006)
# [[User:Venkat | Venkatesh Raghavan]] - member since Oct. 2006 (Chair FOSS4G-2004, FOSS4G-Asia 2014)
# [[User:Pwramsey3 | Paul Ramsey]] - Chair of global FOSS4G 2007
# [[User:Sanghee | Sanghee Shin]] - member since 2015 (chair of Global FOSS4G 2015)
# [[User:Gsteinmon | Guido Stein]] - member since February 2018 (chair of Global FOSS4G 2017)
# [[User:MichaelTerner | Michael Terner]] - member since February 2018 (chair of Global FOSS4G 2017)
# Msilikale Msilanga - '''Co-Chair''' - member since September 2018 (co-chair of Global FOSS4G 2018)
# Mark Iliffe - member since September 2018 (co-chair of Global FOSS4G 2018)
* [https://lists.osgeo.org/pipermail/conference_dev/2019-December/005411.html Motion for co-chairs]

== Past Members ==

# Lorenzo Becchi
# Allan Doyle
# Olivier Ertz
# Alain Grignon
# Luc Maurer
# Daniel Rappo
# Dave Patton
# Rafael Medeiros Sperb
# [[Jeff McKenna]]
# Arnulf Christl
# [[Markus Neteler]]
# Steve Lime
# Frank Warmerdam
# [[User:Davemac | Dave McIlhagga]] (resigned August 2016)
# [[User:Ticheler | Jeroen Ticheler]] (resigned September 2016)
# [[User:Thierry Badard | Thierry Badard]] (resigned September 2016)
# [[User:Helena | Helena Mitasova]] (resigned September 2016)
# [[User:Camerons | Cameron Shorter]] - member from 2009 to Oct 2017 (chair of Global FOSS4G 2009)
# [[User:Jachym | Jachym Cepicky]] - (resigned August 2019)

= Meetings =

* Meetings occur in IRC in the #foss4g channel (on irc.freenode.net) or by other means organized on the email list. Meetings are infrequent.
* <s>As of 2016 the [[Conference_Committee_Meetings | Conference Committee Meetings]] page was not being maintained any more.</s>

=2022 Pages=

* [[FOSS4G_2022_Bid_Process | 2022 RFP schedue]]

=2021 Pages=

* [[FOSS4G_2021_Bid_Process | 2021 RFP schedue]]

=2020 Pages=

* [[FOSS4G_2020_Bid_Process | 2020 RFP schedue]]

=2019 Pages=

* [[FOSS4G_2019_Bid_Process | 2019 RFP schedule]]

=2018 Pages=

* [[FOSS4G_2018_Bid_Process | 2018 RFP schedule]]
* [[Conference_Committee_F2F_2016 | Conference Committee Face to Face meeting in Bonn, 2016]]

= 2017 Pages =

* [[FOSS4G_2017_Bid_Process | 2017 RFP schedule]]
* [[FOSS4G_Travel_Grant_Programme_2017 | 2017 Travel Grant Programme]]

= 2016 Pages =

* [http://www.osgeo.org/conference/rfp/ 2016 RFP schedule]

= 2015 Pages =

* [[FOSS4G 2015 Bid Process]]

= 2014 Pages =

* [[FOSS4G 2014 Bid Process]]
* [[FOSS4G 2014]]
* [[FOSS4G Europe 2014]]

= 2013 Pages =

* Main page: [[FOSS4G_2013]]
* [http://svn.osgeo.org/osgeo/foss4g/2013/documents/FOSS4G_2013_UK_Proposal-Final_version.pdf 2013 Proposal]
* Reflections on the event by the LOC (includes lessons learnt and supersedes the old Lessons Learned page): [[FOSS4G2013_Reflections_by_the_LOC]]

= 2012 Pages =
Main page: [[FOSS4G 2012]]
* RFP ([http://svn.osgeo.org/osgeo/foss4g/rfp/2012/osgeo-conference-2012-request-for-proposal.odt OpenOffice], [http://svn.osgeo.org/osgeo/foss4g/rfp/2012/osgeo-conference-2012-request-for-proposal.pdf pdf])
* budget template ([http://svn.osgeo.org/osgeo/foss4g/rfp/2012/osgeo-conference-budget-template.ods OpenOffice])
* Important dates:
** Letters of Intent (Stage 1) due: 2011-06-30 ([http://www.timeanddate.com/worldclock/fixedtime.html?year=2011&month=06&day=30&hour=23&min=0&sec=0 23:00 UTC])
** Stage 1 question period: 2011-06-30 to 2011-07-07
** Stage 1 decision: 2011-07-07
** Proposals (Stage 2) due: 2011-08-01 ([http://www.timeanddate.com/worldclock/fixedtime.html?year=2011&month=08&day=01&hour=23&min=0&sec=0 23:00 UTC])
** Stage 2 question period: 2011-08-01 to 2011-08-05
** Final decision: 2011-08-05

= 2011 Pages =

* [http://www.osgeo.org/conference/rfp RFP and Letters of Intent]
* [[FOSS4G_2011_Bid_Process | 2011 Bid Process]]
* [[FOSS4G Reboot 2011 | Initial thoughts on 2011 required changes]]

= 2010 Pages =

* [http://www.osgeo.org/conference/rfp RFP and Proposals]
* [[Conference_Committee_2010_Bid_Questions | Bid Questions]]
* [[Conference_Committee_2010_Voting_Process | Voting Process]]

= 2009 Pages =

* [[FOSS4G 2009 Governance]]
* All [http://wiki.osgeo.org/wiki/Category:FOSS4G2009 FOSS4G 2009] pages.

= 2008 Pages =

* [http://www.osgeo.org/conference/rfp RFP and Proposals]
* [http://lists.osgeo.org/pipermail/conference_dev/2007-July/000355.html Voting Process]
* [[FOSS4G 2008 Governance]]
* [[FOSS4GLOC matters]]
* [http://spreadsheets.google.com/pub?key=p6mc38S7PA8lHWRQuIgExDA Workshop and lab evaluations]

= 2007 Pages =

* [http://wiki.osgeo.org/index.php/Category:FOSS4G2007 Pages in category "FOSS4G2007"]
* [[FOSS4G2007]] - wiki page
* http://www.foss4g2007.org/ - Conference Site
* [http://www.osgeo.org/conference/rfp Proposals and RFP]
* [[OSGeo_Conference_RFP_2007#RFP_Response_Requirements | requirements Wiki page]]
* [[OSGeo_Conference_Naming_Results | Naming results]]
* [http://www.foss4g2007.org/bid_site/ Victoria 2007 Proposal]
* [[FOSS4G 2007 Governance]]
* [[FOSS4G2007 Lessons Learned]]

= 2006 Pages =

* [http://wiki.osgeo.org/index.php/Category:FOSS4G2006 Pages in category "FOSS4G2006"]
* http://www.foss4g2006.org/ - Conference Site
* [[FOSS4G2006]] information

= Event Policy Pages =

* [[Official_OSGeo_Event_Policy | OSGeo Event policy]] (in review)
* [[OSGeo_Conference_Policy | Board notes]] regarding event policy
* [http://www.osgeo.org/code_of_conduct OSGeo Code of Conduct]

[[Category:FOSS4G]]
[[Category:Committees]]
[[Category:Conference Committee]]

Finance Operational Notes

2020-06-12T16:56:28Z

Elil: /* Historical Overview */ rearrange and add details to pie charts

This documented is intended to document various aspects of OSGeo's financial operations, to provide rough information on how things are setup to the treasurer, finance committee, and board.

== General ==

* Tyler as ED is responsible for day to day financial operation of OSGeo. He makes payments, issues invoices, cashes cheques, and enters transaction details into the accounting system (Quickbooks online).
* The [[Finance Committee]] is responsible for auditing financial reports, developing financial management policy, and preparing a budget for the board.
* The Treasurer chairs the Finance committee, and is responsible for operational financial decisions within the framework of the budget.
* The [[Board of Directors]] is responsible for approving a budget.

== Quick Books Online ==

OSGeo keeps detailed accounts using Quick Books Online. Currently Tyler (ED) and the Treasurer have accounts with update access for the OSGeo Quick Books instance. The rest of the finance committee has access to a read-only reporting account (contact Tyler or the Treasurer for details).

== Accounts ==
== PEO ==

== Processes ==
On monthly basis:
# Download account data, import to Quickbooks
## Include three bank accounts, paypal
# Enter credit charge charges, invoices, bill pays
# Review wire transfers, confirm sources
# Reconcile account data with cash accounts
# Pay credit card bill
# Quick summary report to Finance Committee (cash, outlook)

Quarterly:
# Reviewing sponsorship status
# Issue new or follow up on outstanding sponsor invoices
# Produce quarterly reports - income/expenses, balance sheet, summaries by class
# Submit reports to Finance Committee

Ongoing:
# Pay marketing and office bills

Annually:
# Prepare annual budget for approval by the board
# File Delaware state franchise tax
## http://corp.delaware.gov/frtax.shtml
## includes "annual report" that lists current directors
# British Columbia provincial annual report
## Filed with Pat @ Oliver & Co., Williams Lake BC
# Directors & Officers Liability insurance renewal
## Current broker: Chapman (chapmanins.com)
## Renewal date: May 13, Fill application in March/April
# Internal year end finance report
## Prepare any final invoices for the year
## Hunt down FOSS4G funds
## Reconcile to statements
# Submit report to Finance Committe
# Include official report in Annual Report
# Write Finance Committee report

== Historical Overview ==
* This section might belong somewhere else in the Finance category but this was a good place to start.
* This focuses on revenue, not expenses. Someone else could certainly fill that in since it is an important part of the finances.
* This is an overview, minor aspects are omitted. (For example GSOC is both a small income --and maybe equal expense, not sure but either way it is minor and this is a general overview.)
* This focuses on 2007-2016/7.
* The FOSS4G "years" mean nothing in the current data portrayal. FOSS4G funds coming back to OSGeo come in multiple payments over multiple years. This does show that OSGeo needs to be able to float a substantial period of time before funds return. This data should probably be sorted out and possibly analyzed on a regional (i.e. every third year) basis for Europe, North America, Rest of World.

=== Data ===
* This summary comes from the help of OSGeo Treasurers. It is the source that was further generalized and used to subsequently derive these graphs.

=== Revenue Graphs ===
[[File:OSGeo_sponsorship_2007-2017.png|thumbnail|center|OSGeo Sponsorship 2007-2017]]
[[File:OSGeo_FOSS4G_2007-2017.png|thumbnail|center|OSGeo FOSS4G 2007-2017]]
[[File:FOSS4G Surpluses and Direct OSGeo Sponsorship 2.png|thumb|center|FOSS4G Surpluses and Direct OSGeo Sponsorship]]

=== Observations ===
* OSGeo sponsorship has declined to an insignificant portion of the OSGeo budget. With effort, it might be possible to increase OSGeo sponsorship again.
* FOSS4G is now essentially the sole source of OSGeo's financial existence which exerts financial pressure on FOSS4G. However, that has not always historically been the case.
* Further analysis of the FOSS4G numbers are needed to see if anything can be determined from the regions and rotation.
* The FOSS4G average is ~$81,587 from ~791 attendees (excluding 2012 for attendance) or ~$103/attendee.

==== Annual proportions 2007-2017 ====
* Blue = FOSS4G Global Surpluses
* Green = Direct sponsorship of OSGeo
<gallery>
File:OSGeo_2007.png|OSGeo proportions 2007
File:OSGeo_2008.png|OSGeo proportions 2008
File:OSGeo_2009.png|OSGeo proportions 2009
File:OSGeo_2010.png|OSGeo proportions 2010
File:OSGeo_2011.png|OSGeo proportions 2011
File:OSGeo_2012.png|OSGeo proportions 2012
File:OSGeo_2013.png|OSGeo proportions 2013
File:OSGeo_2014.png|OSGeo proportions 2014
File:OSGeo_2015.png|OSGeo proportions 2015
File:OSGeo_2016.png|OSGeo proportions 2016
File:OSGeo_2017.png|OSGeo proportions 2017
</gallery>

[[Category: Finance]]

File:FOSS4G Surpluses and Direct OSGeo Sponsorship 2.png

2020-06-12T16:22:14Z

Elil:

Finance Operational Notes

2020-06-12T16:21:55Z

Elil: /* Revenue Graphs */ update graph

This documented is intended to document various aspects of OSGeo's financial operations, to provide rough information on how things are setup to the treasurer, finance committee, and board.

== General ==

* Tyler as ED is responsible for day to day financial operation of OSGeo. He makes payments, issues invoices, cashes cheques, and enters transaction details into the accounting system (Quickbooks online).
* The [[Finance Committee]] is responsible for auditing financial reports, developing financial management policy, and preparing a budget for the board.
* The Treasurer chairs the Finance committee, and is responsible for operational financial decisions within the framework of the budget.
* The [[Board of Directors]] is responsible for approving a budget.

== Quick Books Online ==

OSGeo keeps detailed accounts using Quick Books Online. Currently Tyler (ED) and the Treasurer have accounts with update access for the OSGeo Quick Books instance. The rest of the finance committee has access to a read-only reporting account (contact Tyler or the Treasurer for details).

== Accounts ==
== PEO ==

== Processes ==
On monthly basis:
# Download account data, import to Quickbooks
## Include three bank accounts, paypal
# Enter credit charge charges, invoices, bill pays
# Review wire transfers, confirm sources
# Reconcile account data with cash accounts
# Pay credit card bill
# Quick summary report to Finance Committee (cash, outlook)

Quarterly:
# Reviewing sponsorship status
# Issue new or follow up on outstanding sponsor invoices
# Produce quarterly reports - income/expenses, balance sheet, summaries by class
# Submit reports to Finance Committee

Ongoing:
# Pay marketing and office bills

Annually:
# Prepare annual budget for approval by the board
# File Delaware state franchise tax
## http://corp.delaware.gov/frtax.shtml
## includes "annual report" that lists current directors
# British Columbia provincial annual report
## Filed with Pat @ Oliver & Co., Williams Lake BC
# Directors & Officers Liability insurance renewal
## Current broker: Chapman (chapmanins.com)
## Renewal date: May 13, Fill application in March/April
# Internal year end finance report
## Prepare any final invoices for the year
## Hunt down FOSS4G funds
## Reconcile to statements
# Submit report to Finance Committe
# Include official report in Annual Report
# Write Finance Committee report

== Historical Overview ==
* This section might belong somewhere else in the Finance category but this was a good place to start.
* This focuses on revenue, not expenses. Someone else could certainly fill that in since it is an important part of the finances.
* This is an overview, minor aspects are omitted. (For example GSOC is both a small income --and maybe equal expense, not sure but either way it is minor and this is a general overview.)
* This focuses on 2007-2016/7.
* The FOSS4G "years" mean nothing in the current data portrayal. FOSS4G funds coming back to OSGeo come in multiple payments over multiple years. This does show that OSGeo needs to be able to float a substantial period of time before funds return. This data should probably be sorted out and possibly analyzed on a regional (i.e. every third year) basis for Europe, North America, Rest of World.

=== Data ===
* This summary comes from the help of OSGeo Treasurers. It is the source that was further generalized and used to subsequently derive these graphs.

=== Revenue Graphs ===
[[File:OSGeo_sponsorship_2007-2017.png|thumbnail|center|OSGeo Sponsorship 2007-2017]]
[[File:OSGeo_FOSS4G_2007-2017.png|thumbnail|center|OSGeo FOSS4G 2007-2017]]
[[File:FOSS4G Surpluses and Direct OSGeo Sponsorship 2.png|thumb|center|FOSS4G Surpluses and Direct OSGeo Sponsorship]]

==== Annual proportions ====
[[File:OSGeo_2007.png|thumbnail|center|OSGeo proportions 2007]]
[[File:OSGeo_2008.png|thumbnail|center|OSGeo proportions 2008]]
[[File:OSGeo_2009.png|thumbnail|center|OSGeo proportions 2009]]
[[File:OSGeo_2010.png|thumbnail|center|OSGeo proportions 2010]]
[[File:OSGeo_2011.png|thumbnail|center|OSGeo proportions 2011]]
[[File:OSGeo_2012.png|thumbnail|center|OSGeo proportions 2012]]
[[File:OSGeo_2013.png|thumbnail|center|OSGeo proportions 2013]]
[[File:OSGeo_2014.png|thumbnail|center|OSGeo proportions 2014]]
[[File:OSGeo_2015.png|thumbnail|center|OSGeo proportions 2015]]
[[File:OSGeo_2016.png|thumbnail|center|OSGeo proportions 2016]]
[[File:OSGeo_2017.png|thumbnail|center|OSGeo proportions 2017]]

=== Observations ===
* OSGeo sponsorship has declined to an insignificant portion of the OSGeo budget. With effort, it might be possible to increase OSGeo sponsorship again.
* FOSS4G is now essentially the sole source of OSGeo's financial existence which exerts financial pressure on FOSS4G. However, that has not always historically been the case.
* Further analysis of the FOSS4G numbers are needed to see if anything can be determined from the regions and rotation.
* The FOSS4G average is ~$81,587 from ~791 attendees (excluding 2012 for attendance) or ~$103/attendee.

[[Category: Finance]]

Finance Operational Notes

2020-06-11T21:41:45Z

Elil: /* Revenue Graphs */ Added graph from Steven

This documented is intended to document various aspects of OSGeo's financial operations, to provide rough information on how things are setup to the treasurer, finance committee, and board.

== General ==

* Tyler as ED is responsible for day to day financial operation of OSGeo. He makes payments, issues invoices, cashes cheques, and enters transaction details into the accounting system (Quickbooks online).
* The [[Finance Committee]] is responsible for auditing financial reports, developing financial management policy, and preparing a budget for the board.
* The Treasurer chairs the Finance committee, and is responsible for operational financial decisions within the framework of the budget.
* The [[Board of Directors]] is responsible for approving a budget.

== Quick Books Online ==

OSGeo keeps detailed accounts using Quick Books Online. Currently Tyler (ED) and the Treasurer have accounts with update access for the OSGeo Quick Books instance. The rest of the finance committee has access to a read-only reporting account (contact Tyler or the Treasurer for details).

== Accounts ==
== PEO ==

== Processes ==
On monthly basis:
# Download account data, import to Quickbooks
## Include three bank accounts, paypal
# Enter credit charge charges, invoices, bill pays
# Review wire transfers, confirm sources
# Reconcile account data with cash accounts
# Pay credit card bill
# Quick summary report to Finance Committee (cash, outlook)

Quarterly:
# Reviewing sponsorship status
# Issue new or follow up on outstanding sponsor invoices
# Produce quarterly reports - income/expenses, balance sheet, summaries by class
# Submit reports to Finance Committee

Ongoing:
# Pay marketing and office bills

Annually:
# Prepare annual budget for approval by the board
# File Delaware state franchise tax
## http://corp.delaware.gov/frtax.shtml
## includes "annual report" that lists current directors
# British Columbia provincial annual report
## Filed with Pat @ Oliver & Co., Williams Lake BC
# Directors & Officers Liability insurance renewal
## Current broker: Chapman (chapmanins.com)
## Renewal date: May 13, Fill application in March/April
# Internal year end finance report
## Prepare any final invoices for the year
## Hunt down FOSS4G funds
## Reconcile to statements
# Submit report to Finance Committe
# Include official report in Annual Report
# Write Finance Committee report

== Historical Overview ==
* This section might belong somewhere else in the Finance category but this was a good place to start.
* This focuses on revenue, not expenses. Someone else could certainly fill that in since it is an important part of the finances.
* This is an overview, minor aspects are omitted. (For example GSOC is both a small income --and maybe equal expense, not sure but either way it is minor and this is a general overview.)
* This focuses on 2007-2016/7.
* The FOSS4G "years" mean nothing in the current data portrayal. FOSS4G funds coming back to OSGeo come in multiple payments over multiple years. This does show that OSGeo needs to be able to float a substantial period of time before funds return. This data should probably be sorted out and possibly analyzed on a regional (i.e. every third year) basis for Europe, North America, Rest of World.

=== Data ===
* This summary comes from the help of OSGeo Treasurers. It is the source that was further generalized and used to subsequently derive these graphs.

=== Revenue Graphs ===
[[File:OSGeo_sponsorship_2007-2017.png|thumbnail|center|OSGeo Sponsorship 2007-2017]]
[[File:OSGeo_FOSS4G_2007-2017.png|thumbnail|center|OSGeo FOSS4G 2007-2017]]
[[File:FOSS4G Surpluses and Direct OSGeo Sponsorship.png|thumb|center|FOSS4G Surpluses and Direct OSGeo Sponsorship]]

[[File:OSGeo_2007.png|thumbnail|center|OSGeo proportions 2007]]
[[File:OSGeo_2008.png|thumbnail|center|OSGeo proportions 2008]]
[[File:OSGeo_2009.png|thumbnail|center|OSGeo proportions 2009]]
[[File:OSGeo_2010.png|thumbnail|center|OSGeo proportions 2010]]
[[File:OSGeo_2011.png|thumbnail|center|OSGeo proportions 2011]]
[[File:OSGeo_2012.png|thumbnail|center|OSGeo proportions 2012]]
[[File:OSGeo_2013.png|thumbnail|center|OSGeo proportions 2013]]
[[File:OSGeo_2014.png|thumbnail|center|OSGeo proportions 2014]]
[[File:OSGeo_2015.png|thumbnail|center|OSGeo proportions 2015]]
[[File:OSGeo_2016.png|thumbnail|center|OSGeo proportions 2016]]
[[File:OSGeo_2017.png|thumbnail|center|OSGeo proportions 2017]]

=== Observations ===
* OSGeo sponsorship has declined to an insignificant portion of the OSGeo budget. With effort, it might be possible to increase OSGeo sponsorship again.
* FOSS4G is now essentially the sole source of OSGeo's financial existence which exerts financial pressure on FOSS4G. However, that has not always historically been the case.
* Further analysis of the FOSS4G numbers are needed to see if anything can be determined from the regions and rotation.
* The FOSS4G average is ~$81,587 from ~791 attendees (excluding 2012 for attendance) or ~$103/attendee.

[[Category: Finance]]

File:FOSS4G Surpluses and Direct OSGeo Sponsorship.png

2020-06-11T21:39:10Z

Elil:

FOSS4G Surpluses and Direct OSGeo Sponsorship graph from Steven Feldman

Conference Committee

2020-05-29T15:19:15Z

Elil: /* Current Members */

The Conference Committee is the official committee of OSGeo responsible for operating the annual [[FOSS4G]] conferences.

= Noteworthy Documents =

* [[FOSS4G Handbook]] (provides guidance to future FOSS4G and related events, based upon the collective wisdom gained during prior events)
* [http://lists.osgeo.org/mailman/listinfo/conference_dev Conference Committee email list]
* [http://www.osgeo.org/conference OSGeo Conference Committee main page] (includes RFP, proposals, and archived files from past conferences)
* Past conference reports are detailed at [[Past FOSS4G Reports]]
* [[Conference website management]]
* [[Motion to form Conference Committee]]
* [[Conference Committee Budget 2017 | Conference Committee Budget 2017 (draft)]]

= Goals =
The conference committee have the responsibility to:
* Run the selection process and voting for the global FOSS4G
* Vote on conference related proposals submitted to the committee
* Retain the [[FOSS4G Handbook | collected wisdom]] for FOSS4G and related events
* Advise the board, Local Organising Committees (LOC), and related events organisors, ideally referencing the [[FOSS4G Handbook]]
* Ensure OSGeo foundation principles are applied to global FOSS4G conferences
* Manage the FOSS4G Travel Grant Programme for FOSS4G and regional events

See also: '''2016 priorities are summarised in [[Conference Committee 2016 Priorities]]'''

=Housekeeping Procedures=
The Conference Committee uses the following procedures to make decisions.

==Decisions==

[[consideration for new selection methods]]

# Anyone may contribute to conference committee discussions. All votes will be noted, but only conference committee member votes count toward decisions.
# Voting will use convention of:
#* +1 : For
#* +0: Mildly for
#* 0: Indifferent
#* -0: Mildly against
#* -1 : Strongly against. This is expected to be accompanied by a reason and alternative proposal.
# Everyday topics will be decided by an open vote of all members in a clearly designated separate mail thread over a minimum of 2 business days with a minimum participation of 3 votes.
# For major decisions, such as conference venue selection, a minimum of one week shall be allocated to try and ensure at least 50% voter participation.
# The committee aims for consensus, and will specifically attempt to address all -1 votes, but will revert to a majority vote where necessary.
# The result will be clearly declared afterwards.
# Secret voting, when required, will use an online voting service or use an email to an independent teller appointed by CC Chair.

==FOSS4G Selection==

# All Letters of Intent and subsequent proposals will be posted to the list for open comment by all.
# The selection of the winning proposal is by secret vote of conference committee members.
# The OSGeo Board will be requested to ratify the conference committee’s recommendation.
# Any committee member who has a potential conflict of interest is expected to withdraw from voting. A member of the committee who is part of a bidding team, intends to become part of the LOC or is employed by a company playing an active part in a bid should exclude themselves from voting in the selection process. In the event of a disagreement regarding a potential conflict of interest the committee chair has the authority to make a decision.

=== Changes in RfP Document for 2021 ===
* At least at the letters-of-intent stage there should always be a voting option of "None of the above". Otherwise there's no point in having a vote if there's only one letter, also this allows for the (unlikely) event of all letters being rubbish.
* Bids should be scored based on various pre-defined criterion. Current voting by the committee seems to include a "where I want to go on holiday" component which has no place in a process like this. This is in keeping with the "openness" goal of OSGeo as compared to the current Star Chamber-like voting.
* Further to the above, a list of objective mandatory criterion can be specified as required. I.e. "Venue must be able to host X people", "must be at least Y tracks", "Must be accessible via both local and national public transport", etc.

==FOSS4G Travel Grant Programme==

The FOSS4G TGP was started in 2017 with funding from the OSGeo Board and a crowd funding initiative. The Conference Committee is tasked with managing this grant programme for the Global FOSS4G and for any Regional FOSS4G's that request assistance

* [[FOSS4G Travel Grant Programme 2017 | 2017]]
* [[FOSS4G Travel Grant Programme 2018 | 2018]]

=== Setting up a FOSS4G TGP ===

Some guidance notes are available in the [[FOSS4G Travel Grant Programme Cookbook | FOSS4G Travel Grant Programme Cookbook]]

==Membership==

# To ensure voting control for key decisions remains with experienced people, the committee aims for more than 50% of members to be chairs (or vice chairs) of past FOSS4G global events. The chair of the most recent FOSS4G event will automatically be invited to become a member but still requires a motion and vote.
# The conference committee aims to retain a chair or vice-chair from the 5 most recent global FOSS4G conferences.
# The remaining membership, less than 50% of members, is open, ideally attracting chairs or LOC members from past Global or Regional FOSS4G or related conferences.
# Each year, prior to releasing the Global FOSS4G RfP, the membership list shall be re-visited.
## Existing members shall be asked whether they wish to continue on the committee. If a member doesn't respond, after a number of attempts to contact them, they shall be retired.
## Interested people may be suggested, or request to be voted onto the conference committee.
## If less than 50% of membership would be past global FOSS4G chair/vice chairs, then non global FOSS4G chair/vice chair positions shall be up for re-election.
## Election of conference committee members is by secret vote by the existing conference committee and board members who are not already members of the conference committee. Voters will vote Yes/No/Abstain for each candidate. Voters may select "Yes" for up to the number of positions available.
# Votes will be secret either using an online voting system or by email to a designated teller who is not a voter. The mechanism will be selected by the committee chair.

== Current Members ==

# [[User:EliL | Eli Adam]] - member since [https://lists.osgeo.org/pipermail/conference_dev/2015-January/002811.html January 2015] (1 of 4 co-chairs of Global FOSS4G 2014)
# [[User:Till Adams | Till Adams]] - member since September 2016 (chair of Global FOSS4G 2016)
# [[User:pmbatty | Peter Batty]] - member since 2011 (chair of Global FOSS4G 2011)
# [[User:Bitner | David Bitner]] (chair of the 2013 FOSS4GNA)
# [[User:Maria | Maria Brovelli]] - member since March 2016 (Chair FOSS4G Europe 2015)
# [[User:Vasile | Vasile Craciunescu]] - '''Co-Chair''' - member since July 2013 (chair of FOSS4G Central and Eastern Europe 2013)
# David Fawcett (Programme Team FOSS4GNA 2013)
# [[User:Stevenfeldman | Steven Feldman]] - member since October 2013 (chair of Global FOSS4G 2013)
# [[User:GFleming |Gavin Fleming]] - (chair of Global FOSS4G 2008)
# Darrell Fuhriman (chair of Global FOSS4G 2014)
# Claude Philipona - (chair of Global FOSS4G 2006)
# [[User:Venkat | Venkatesh Raghavan]] - member since Oct. 2006 (Chair FOSS4G-2004, FOSS4G-Asia 2014)
# [[User:Pwramsey3 | Paul Ramsey]] - Chair of global FOSS4G 2007
# [[User:Sanghee | Sanghee Shin]] - member since 2015 (chair of Global FOSS4G 2015)
# [[User:Gsteinmon | Guido Stein]] - member since February 2018 (chair of Global FOSS4G 2017)
# [[User:MichaelTerner | Michael Terner]] - member since February 2018 (chair of Global FOSS4G 2017)
# Msilikale Msilanga - '''Co-Chair''' - member since September 2018 (co-chair of Global FOSS4G 2018)
# Mark Iliffe - member since September 2018 (co-chair of Global FOSS4G 2018)
* [https://lists.osgeo.org/pipermail/conference_dev/2019-December/005411.html Motion for co-chairs]

== Past Members ==

# Lorenzo Becchi
# Allan Doyle
# Olivier Ertz
# Alain Grignon
# Luc Maurer
# Daniel Rappo
# Dave Patton
# Rafael Medeiros Sperb
# [[Jeff McKenna]]
# Arnulf Christl
# [[Markus Neteler]]
# Steve Lime
# Frank Warmerdam
# [[User:Davemac | Dave McIlhagga]] (resigned August 2016)
# [[User:Ticheler | Jeroen Ticheler]] (resigned September 2016)
# [[User:Thierry Badard | Thierry Badard]] (resigned September 2016)
# [[User:Helena | Helena Mitasova]] (resigned September 2016)
# [[User:Camerons | Cameron Shorter]] - member from 2009 to Oct 2017 (chair of Global FOSS4G 2009)
# [[User:Jachym | Jachym Cepicky]] - (resigned August 2019)

= Meetings =

* Meetings occur in IRC in the #foss4g channel (on irc.freenode.net) or by other means organized on the email list. Meetings are infrequent.
* <s>As of 2016 the [[Conference_Committee_Meetings | Conference Committee Meetings]] page was not being maintained any more.</s>

=2021 Pages=

* [[FOSS4G_2021_Bid_Process | 2021 RFP schedue]]

=2020 Pages=

* [[FOSS4G_2020_Bid_Process | 2020 RFP schedue]]

=2019 Pages=

* [[FOSS4G_2019_Bid_Process | 2019 RFP schedule]]

=2018 Pages=

* [[FOSS4G_2018_Bid_Process | 2018 RFP schedule]]
* [[Conference_Committee_F2F_2016 | Conference Committee Face to Face meeting in Bonn, 2016]]

= 2017 Pages =

* [[FOSS4G_2017_Bid_Process | 2017 RFP schedule]]
* [[FOSS4G_Travel_Grant_Programme_2017 | 2017 Travel Grant Programme]]

= 2016 Pages =

* [http://www.osgeo.org/conference/rfp/ 2016 RFP schedule]

= 2015 Pages =

* [[FOSS4G 2015 Bid Process]]

= 2014 Pages =

* [[FOSS4G 2014 Bid Process]]
* [[FOSS4G 2014]]
* [[FOSS4G Europe 2014]]

= 2013 Pages =

* Main page: [[FOSS4G_2013]]
* [http://svn.osgeo.org/osgeo/foss4g/2013/documents/FOSS4G_2013_UK_Proposal-Final_version.pdf 2013 Proposal]
* Reflections on the event by the LOC (includes lessons learnt and supersedes the old Lessons Learned page): [[FOSS4G2013_Reflections_by_the_LOC]]

= 2012 Pages =
Main page: [[FOSS4G 2012]]
* RFP ([http://svn.osgeo.org/osgeo/foss4g/rfp/2012/osgeo-conference-2012-request-for-proposal.odt OpenOffice], [http://svn.osgeo.org/osgeo/foss4g/rfp/2012/osgeo-conference-2012-request-for-proposal.pdf pdf])
* budget template ([http://svn.osgeo.org/osgeo/foss4g/rfp/2012/osgeo-conference-budget-template.ods OpenOffice])
* Important dates:
** Letters of Intent (Stage 1) due: 2011-06-30 ([http://www.timeanddate.com/worldclock/fixedtime.html?year=2011&month=06&day=30&hour=23&min=0&sec=0 23:00 UTC])
** Stage 1 question period: 2011-06-30 to 2011-07-07
** Stage 1 decision: 2011-07-07
** Proposals (Stage 2) due: 2011-08-01 ([http://www.timeanddate.com/worldclock/fixedtime.html?year=2011&month=08&day=01&hour=23&min=0&sec=0 23:00 UTC])
** Stage 2 question period: 2011-08-01 to 2011-08-05
** Final decision: 2011-08-05

= 2011 Pages =

* [http://www.osgeo.org/conference/rfp RFP and Letters of Intent]
* [[FOSS4G_2011_Bid_Process | 2011 Bid Process]]
* [[FOSS4G Reboot 2011 | Initial thoughts on 2011 required changes]]

= 2010 Pages =

* [http://www.osgeo.org/conference/rfp RFP and Proposals]
* [[Conference_Committee_2010_Bid_Questions | Bid Questions]]
* [[Conference_Committee_2010_Voting_Process | Voting Process]]

= 2009 Pages =

* [[FOSS4G 2009 Governance]]
* All [http://wiki.osgeo.org/wiki/Category:FOSS4G2009 FOSS4G 2009] pages.

= 2008 Pages =

* [http://www.osgeo.org/conference/rfp RFP and Proposals]
* [http://lists.osgeo.org/pipermail/conference_dev/2007-July/000355.html Voting Process]
* [[FOSS4G 2008 Governance]]
* [[FOSS4GLOC matters]]
* [http://spreadsheets.google.com/pub?key=p6mc38S7PA8lHWRQuIgExDA Workshop and lab evaluations]

= 2007 Pages =

* [http://wiki.osgeo.org/index.php/Category:FOSS4G2007 Pages in category "FOSS4G2007"]
* [[FOSS4G2007]] - wiki page
* http://www.foss4g2007.org/ - Conference Site
* [http://www.osgeo.org/conference/rfp Proposals and RFP]
* [[OSGeo_Conference_RFP_2007#RFP_Response_Requirements | requirements Wiki page]]
* [[OSGeo_Conference_Naming_Results | Naming results]]
* [http://www.foss4g2007.org/bid_site/ Victoria 2007 Proposal]
* [[FOSS4G 2007 Governance]]
* [[FOSS4G2007 Lessons Learned]]

= 2006 Pages =

* [http://wiki.osgeo.org/index.php/Category:FOSS4G2006 Pages in category "FOSS4G2006"]
* http://www.foss4g2006.org/ - Conference Site
* [[FOSS4G2006]] information

= Event Policy Pages =

* [[Official_OSGeo_Event_Policy | OSGeo Event policy]] (in review)
* [[OSGeo_Conference_Policy | Board notes]] regarding event policy
* [http://www.osgeo.org/code_of_conduct OSGeo Code of Conduct]

[[Category:FOSS4G]]
[[Category:Committees]]
[[Category:Conference Committee]]

Consideration for new selection methods

2020-04-13T22:14:06Z

Elil: /* Pre */

==== Pre ====
After the vote on RfP 2020 there have been some ideas on changing the selection process on global FOSS4G events.
This page is open to everybody to bring down his/hers ideas, so that we can start a discussion and, if agreed by CC members, change the selection process.

Here is the [https://lists.osgeo.org/pipermail/conference_dev/2018-December/005036.html Email list thread] (or at least one of them that has occured over the years).

[[Category:FOSS4G]]
[[Category:Committees]]
[[Category:Conference Committee]]

Board of Directors

2019-12-17T18:06:24Z

Elil: /* Previous meetings */

== OSGeo Foundation Board of Directors ==

The board is elected by the [http://www.osgeo.org/charter_members Charter members] as outlined in the [[Board Election Procedure]].

Period: November 2019 - October 2021

* [https://www.osgeo.org/member/astrid-emde/ Astrid Emde] - Cologne, Germany (Central European Time Zone UTC +1h)
* [https://www.osgeo.org/member/codrina-maria-ilie/ Codrina Maria Ilie] - Bucharest, Romania (Central European Time Zone UTC +1h)
* [https://www.osgeo.org/member/Aeylinen/ Helena Mitasova] - Raleigh, USA (Eastern Time UTC -5h)
* [https://www.osgeo.org/member/till-adams/ Till Adams] - Bonn, Germany (Central European Time Zone UTC +1h)
* [https://www.osgeo.org/member/vicky-vergara/ Vicky Vergara] - Naucalpan, Mexico (Central Standard Time UTC -6h)

Period: November 2018 - October 2020

* [[Victoria Rautenbach]] - Pretoria, South Africa, (South Africa Standard Time UTC+2)
* [[Michael Smith]] - Hanover, New Hampshire, USA (Eastern Time UTC -5h) [[Treasurer]]
* [[Angelos Tzotsos]] - Athens, Greece (Central European Time UTC +2h) [[Executive_Positions|Vice-President]]
* [[Tom Kralidis]] - Toronto, Canada (Eastern Time UTC -5h)



More detailed information is available in the [[Board Member Profiles]].

= Board Activities and Meetings =

== Board Activities ==

=== Motions ===

The board is using Loomio to track motions and facilitate voting (see [[Board Voting Procedure]]):

* https://www.loomio.org/g/kdSmIwxu/osgeo-board

=== Actions ===

The board is an issue tracker for actions:

* https://git.osgeo.org/gitea/osgeo/todo/issues

== Board Meetings ==

In general the OSGeo board meets on IRC the last Monday of the month from [http://www.timeanddate.com/worldclock/meetingdetails.html?hour=16&min=0&sec=0&p1=43&p2=49&p3=1234&p4=286&p5=157&p6=671&p7=207&p8=1091&p9=259 16.00 UTC]

Upcoming board meetings:

; IRC Meeting: [[IRC|Internet Rely Chat]] meetings are held on FreeNode [irc://irc.freenode.net/osgeo OSGeo channe]], please note that due to spam you are now required to register with the FreeNode "NickServ" bot to verify your identity prior to posting messages on IRC. The FreeNode OSGeo channel is [http://irclogs.geoapt.com/osgeo logged] providing a great record of IRC meetings.

* [[Board_Meeting_2019-11-25]] at [https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191125T1600 16:00 UTC]

; Face to Face Meeting: board will get together in person and work through discussions and tasks that are not easily handled in a 1 hour IRC meeting or via e-mail. For face to face meetings travel costs will be covered by the foundation.

* none scheduled

; Video call: board will get together for a video call and work through discussions and tasks that are not easily handled in 1 hour IRC meeting or via e-mail. May also consist of an informal "work party" of board members and officers to work on tasks and collaboration not easily handled in IRC meeting / email.

* none scheduled

; Member meeting: board meeting with OSGeo members at OSGeo events providing a chance to listen and discuss our community. May also consist of informal "party" to celebrate our community, members, and what we accomplish together

* none scheduled

=== Previous meetings ===

* [[Board_Meeting_2019-12-09]]
* [[Board_Meeting_2019-11-25]] at [https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191125T1600 16:00 UTC]
* [[Board_Meeting_2019-11-04]] at [https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191104T1600 16:00 UTC]
* [[Board_Meeting_2019-10-28]] at [https://www.timeanddate.com/worldclock/fixedtime.html?iso=20191028T1600 16:00 UTC]
* [[Board_Meeting_2019-09-30]] at [https://www.timeanddate.com/worldclock/fixedtime.html?iso=20190930T1600 16:00 UTC]
* [[Board_Meeting_2019-09-09]] at [https://www.timeanddate.com/worldclock/fixedtime.html?iso=20190909T1600 16:00 UTC] breakout meeting to appoint CRO for 2019 elections
* [[Board Meeting_2019-08-24]] 24.-25.8.2019 two days face to face meeting, prior to foss4g conference.
* [[Board_Meeting_2019-07-29]] at [https://www.timeanddate.com/worldclock/fixedtime.html?iso=20190729T1600 16:00 UTC]
* [[Board_Meeting_2019-06-24]] at [https://www.timeanddate.com/worldclock/fixedtime.html?iso=20190624T1600 16:00 UTC]
* [[Board Meeting_2019-05-27]] at [https://www.timeanddate.com/worldclock/fixedtime.html?iso=20190527T1600 16:00 UTC]
* [[Board Meeting_2019-04-29]] at [https://www.timeanddate.com/worldclock/fixedtime.html?iso=20190429T1600 16:00 UTC]
* [[Board Meeting_2019-03-25]] [https://www.timeanddate.com/worldclock/meetingdetails.html?year=2019&month=3&day=25&hour=16&min=0&sec=0&p1=256&p2=286&p3=141&p4=269 14:00 UTC] (4 hour video f2v session scheduled)
* [[Board Meeting_2019-02-26]] [https://www.timeanddate.com/worldclock/meetingdetails.html?year=2019&month=2&day=26&hour=16&min=0&sec=0&p1=256&p2=286&p3=141&p4=269 16:00 UTC]
* Budget Meeting 2019-02-01 at [https://www.timeanddate.com/worldclock/fixedtime.html?iso=20190201T1500 15:00 - 16:00 UTC] budget breakout meeting on [https://meet.jit.si/osgeo meet.jit.si/osgeo] chat.
* [[Board Meeting_2019-01-21]] at [https://www.timeanddate.com/worldclock/fixedtime.html?iso=20190121T1600 16:00 UTC]
* [[Board_Meeting_2018-12-20]] [https://www.timeanddate.com/worldclock/meetingdetails.html?year=2018&month=12&day=20&hour=20&min=0&sec=0&p1=256&p2=286&p3=141&p4=49&p5=71&p6=152 20.00 - 22:00 UTC] Draft Budget
* [[Board_Meeting_2018-12-17]] [https://www.timeanddate.com/worldclock/meetingdetails.html?year=2018&month=12&day=17&hour=19&min=0&sec=0&p1=256&p2=286&p3=141&p4=49&p5=71&p6=152 19.00 - 21:00 UTC] initial board monthly meting, focus on "on boarding"
* [[Board_Meeting_2018-11-07]] [https://www.timeanddate.com/worldclock/meetingdetails.html?year=2018&month=11&day=7&hour=16&min=0&sec=0&p1=256&p2=286&p3=141&p4=49&p5=71&p6=152 16.00 UTC]
* [[Board_Meeting_2018-10-13]] 16.00 UTC
* [[Board_Meeting_2018-09-08]] 15.00 UTC
* [[Face to Face Meeting Dar es Salaam 2018]] 31. August 2018 Dar 19:00-21:00 (would mean 16 UTC as Dar is UTC+3)
* [[Member Meeting FOSS4G 2018]] 2018 August 28th evening (Dar Es Salaam, Tansania)
* [[Board_Meeting_2018-08-01]] 15.00 UTC
* [[Member Meeting FOSS4G-Europe 2018]] 2018 July 19th at 18:00 in FOSS4G-Europe Hostel (Pousada da Juventude de Guimarães)
* [[Board_Meeting_2018-07-05]] 16.00 UTC
* [[Board_Meeting_2018-06-06]] 16.00 UTC
* [[Member Meeting FOSS4GNA 2018]] May 14th in St. Louis, Missouri during [http://www.osgeo.org/events/foss4g-north-america-2018/ FOSS4G North America 2018]
* [[Board_Meeting_2018-05-01]] 16.00 UTC
* [[Board Meeting 2018-04-11]] 16.00 UTC
* [[Board Meeting 2018-04-05]] 15.00 UTC - canceled lack of attendance
* [[Member Meeting Bonn 2018]] 2018 March 19th at 18:00 in Bonn BaseCamp during [[OSGeo Code Sprint 2018]]
* [[Face to Face Meeting Bonn 2018]] 17.-18. March 2018
* [[Board Meeting 2018-03-01]] 15.00 UTC
* [[Board Meeting 2018-02-01]] 14.00 UTC
* [[Board Meeting 2018-01-17]] 15.00 UTC Video Call Executive Positions

[[:Category:Board_Meetings_2018|2018]] - [[:Category:Board_Meetings_2017|2017]] - [[:Category:Board_Meetings_2016|2016]] - [[:Category:Board_Meetings_2015|2015]] - [[:Category:Board_Meetings_2014|2014]] - [[:Category:Board_Meetings_2013|2013]] - [[:Category:Board_Meetings_2012|2012]] - [[:Category:Board_Meetings_2011|2011]] - [[:Category:Board_Meetings_2010|2010]] - [[:Category:Board_Meetings_2009|2009]] - [[Board Meetings 2008|2008]] - [[Board Meetings 2007|2007]] - [[Board Meetings 2006|2006]] - [http://www.osgeo.org/content/foundation/meetings/board/board_meetings.html Earlier].

= Working Groups =

While the board is focused on decision making occasionally there is a call for action. The following working groups are focused on accomplishing a specific 2-3 week objective and will report back to the board list when completed. This is in contrast to long term activities handled by committees.

== 2018 Working Groups ==

* none at present

== 2015 Working Groups ==

* [[2015 Sponsorship Drive Working Group]] - contact prior sponsors, blog post inviting new sponsors
* [[GeoForAll OSGeo Relationship]]: Revised Education Committee mandate pending clarification of relationship with Geo4All advisory board (our GeoForAll representatives are Venkatesh Raghavan and Jeff McKenna)

= Planning =

== 2019 Planning ==

Documents:

* [https://github.com/OSGeo/osgeo/blob/master/board/documents/osgeo_financial_guidence.pdf OSGeo Financial Guidance]

=== Operational Budget for 2019 ===

The board is dividing this years budget up by committee, initiative and project!

* [[OSGeo Budget 2019]]

== 2018 Planning ==

=== Operational Budget for 2018 ===

The board is dividing this years budget up by committee, initiative and project!

* [[OSGeo Budget 2018]]

=== Sponsorship Opportunities for 2018 ===

OSGeo maintains a sponsorship program recognizing financial contributions to our projects, initiatives and events.

* [[OSGeo Sponsorship Opportunities 2018]]

== 2017 Planning ==

=== Operational Budget for 2017 ===

The board is dividing this years budget up by committee:

* [[OSGeo Budget 2017]]

=== Sponsorship Opportunities for 2017 ===

The foundation recognizes sponsors who financially support our events, initiatives and open source projects.

* [[Sponsorship Opportunities for 2017]]

The following has been published as the following [http://www.osgeo.org/node/1755 blog post] and [http://www.osgeo.org/sponsorship how to sponsor page].

== 2016 Planning ==

=== Operational Budget for 2016 ===

Thanks to our sponsors, and a series of successful events, OSGeo does has an operational budget for 2016.

* [[OSGeo Budget 2016]]

The Board has divided the above budget up according to our priority as an organization. Please keep in mind that prior boards have taken this approach - and spent nothing due to lack of volunteers willing to lead the charge. The following is budget and does not provide a commitment to spend money on the actives listed - to do that we need your commitment as a volunteer!

=== Strategic Plan 2016 ===

''From Anne'': See the parallel Skate-Boarding of Fedora at http://fedoramagazine.org/lets-talk-about-fedora-project-objectives/ - I really like the idea of having 18 months goals, that are measurable, backed up by community agreement. Let's discuss this at the first Sprint. There are also [http://www.jonobacon.org/2014/11/14/ubuntu-governance-reboot/ some thoughts on Ubuntu governance] that can inspire us, but I haven't gone through the whole discussion yet, and there are many differences between OSGeo and Ubuntu; so I'm not sure on how much we can learn from it.

This section outlines OSGeo strategic plan for 2016 - this is a result of the [http://www.osgeo.org/about vision, mission and goals] established at the [[Board_Face_to_Face_Meeting_2016|2016 face to face meeting]].

Strategic objectives for 2016:

* S01: showcasing excellence in our communities
* S02: proactively engage with external partners
* S03: Fostering our mission, vision and goals
* S04: Empowering our communities and extending our reach

These objectives were taken to the community for concrete / measurable actions volunteers were interested in tackling over the course of 2016.

Update: We did not receive enough feedback to form a strategic plan.

== 2013 Planning ==

* [[OSGeo Board : Board Priorities 2013]] - establish OSGeo as a low capital, volunteer focused organization focused supporting communities and initiatives which support themselves

= Reference =

* Please see foundation [https://www.osgeo.org/about/bylaws/ bylaws] for official responsibilities
* Arnulf Christl's [http://arnulf.us/sevendipity/archives/49-OSGeo-Director-Retrospective.html OSGeo Director Retrospective]. Arnulf was an OSGeo Board member and President of OSGeo.
* for incoming Board members [[Board_of_Directors/OnboardingChecklist|OnboardingChecklist]]

== Documents ==
* [[https://github.com/OSGeo/osgeo/blob/master/board/documents/osgeo_financial_guidance.pdf OSGeo Financial Guidance]]
* [[Executive Positions]] and [[Director Responsibilities]]
* [[Board Election Procedure]]
* [[Election 2019]]
* Election 2018: [[Board_Election_2018_Results]] [[Election 2018 Candidate Manifestos]]
* Election 2017: [[Board_Election_2017_Results]] [[Election 2017 Candidate Manifestos]]
* Election 2016: [[Board_Election_2016_Results]] [[Election 2016 Candidate Manifestos]]
* Election 2015: [[Board_Election_2015_Results]] [[Election 2015 Candidate Manifestos]]
* Election 2014: [[Board Election 2014 Results]]
* Election 2013: [[Board Election 2013 Results]]
* Election 2012: [[Board Election 2012 Results]]
* Election 2011: [[Board Election 2011 Results]]
* Election 2010: [[Board Election 2010 Results]]
* Election 2009: [[Board Election 2009]], see 2009 section of [[Proposed Board Election Procedure]]
* Election 2008: [[Board Election 2008]], see 2008 section of [[Proposed Board Election Procedure]]
* Election 2007: [[Board Election 2007]], see 2007 section of [[Proposed Board Election Procedure]]
* [[Foundation Sponsorship]] (adopted), [[Project Sponsorship]] (adopted), [[Local Chapter Sponsorship]] (idea)
* [[Conflict Of Interest Policy]]

== Mailing list ==

The http://lists.osgeo.org/mailman/listinfo/board mailing list is used for most public board discussions. There is also a private board mailing list used only for matters that are considered needful to be kept private.

== History of OSGeo Foundation Boards of Directors ==

* [[Board_Election_2018_Results|Board of Directors 2018]] (Nov. 2018 - Oct. 2019)
* [[Board Election 2017 Results|Board of Directors 2017]] (Nov. 2017 - Oct. 2018)
* [[Board Election 2016 Results|Board of Directors 2016]] (Aug. 2016 - Aug. 2017)
* [[Board Election 2015 Results|Board of Directors 2015]] (Aug. 2015 - Aug. 2016)
* [[Board Election 2014 Results|Board of Directors 2014]] (Aug. 2014 - Aug. 2015)
* [[Board Election 2013 Results|Board of Directors 2013]] (Aug. 2013 - Aug. 2014)
* [[Board Election 2012 Results|Board of Directors 2012]] (Aug. 2012 - Aug. 2013)
* [[Board Election 2011 Results|Board of Directors 2011]] (Aug. 2011 - Aug. 2012)
* [[Board Election 2010 Results|Board of Directors 2010]] (Aug. 2010 - Aug. 2011)
* [[Board Election 2009 Results|Board of Directors 2009]] (Sept. 2009 - Aug. 2010)
* [[Board Election 2008 Results|Board of Directors 2008]] (July 2008 - Sept. 2009)
* [[Board Election 2007 Results|Board of Directors 2007]] (Aug. 2007 - July 2008)
* [[Interim Board of Directors 2006]] (Feb. 2006 - July 2007)

An interim Board of Directors with 5 members was elected on February 4th, 2006, by the initial members of the [http://www.osgeo.org Open Source Geospatial Foundation]. On March 18th, 2006, the board has been completed to now total nine members:

Q&A Stage 2 Buenos Aires

2019-11-29T17:49:04Z

Elil: Add questions by Eli

= Questions to the BALOC from CC =

== name of the questioner ==
** '''question 1'''

** '''question 2'''

== Steven Feldman ==

Great proposal, thanks very much. Lot's of exciting ideas which I welcome. I'd like to focus on the financial stuff (as usual for me)

*'''You have asked for a $60k advance from OSGeo, normally we have limited our advance to $40k, can you provide some more detail on why you need a larger advance and the timing of the cash outflows?'''

''The CEC building’s rent (still being negotiated) is US$70.266. We have been asked to give half of it (US$35.133) in advance to book the place.
The Law Faculty’s rent is US$16.500 if we finally reach close to 1.150 attendees. They also ask half of it in advance ( US$8.250). If we finally don’t need both spaces, we will be able to pay a lower amount, but we want to book the full 1150 attendees space just in case.
So, venue advanced payment totals US$43.383. We are asking for US$60.000 to make sure we have also some cash flow while we get the first tickets sold.
We won’t need the full $60.000 right away, just enough to book the venues and secure the dates.''

* '''Are you also seeking any further guarantees or underwriting from OSGeo?'''

''We have a generously estimated budget with items that can be opt-out if needed, so we don’t expect any financial issues. For example, if we have to escalate the event down we can cut big expenses like the CEC building and make the social events simpler. In case we don’t get enough tickets sold (below 550), we will contact the OSGeo Board to decide how to proceed.
We don’t need any written warranty from OSGeo.''

* '''If you request an advance from OSGeo the norm is that at least 80% of the surplus from your event is returned to OSGeo, your proposal only returns 30% to OSGeo. This is a substantial change which would need to be approved by the Board if recommended by CC, can you explain why such a low %age should be accepted?'''

''We understood that the 80% surplus for OSGeo was the suggested amount for NA and european events.
We can adjust the numbers and give a higher percentage of the surplus to OSGeo, although we think that “leaving” part of that surplus on the local organization can help the development and further outreach of the OSGeo community on the region.''

* '''Your projected surpluses are on the low side, whilst I appreciate your low ticket prices, I wonder whether you can afford to charge a little more and possibly reduce the early bird discount to a consistent 20% (particularly for what you define as International) as a way of increasing your surplus and providing a safety net?
'''
''The budget is generously estimated (we are still negotiating some contracts to get a lower price) and we have the “open price ticket” which should give us more margin. The budget is using amounts we consider “safe” to be cut if things go wrong. (Although the minimum attendance described on the budget is 650, we can lower that even more if we remove venue space and non-essential items).
We could increase the international price and still do that 20% discount on the early bird. But if we increase the ticket price for regional (especially local) tickets that could impact on our estimates of attendance.Trying to reach a consistent 20% discount could mean we have to lower the normal price for local and regional which could be even worse for the income.
We are confident that, while the surplus doesn’t look good, it will get better once we start signing contracts, even if we don’t change ticket prices.''

* '''I love the low prices that you are proposing and the option to top up pricing for those who can afford more, perhaps you could phrase this in a slightly different way by quoting higher prices and allowing those who need to self declare for a discount with the lowest price being your current rates? This could work well for corporates who may not respond well to a request to top up but could voluntarily exclude from an "in need" discount.'''

''We will be careful on how to phrase this, as we also don’t want locals to think we are thinking less of them. We can add some note for sponsors as you mention.''

* '''I did not see any explicit mention of video recording or streaming. What are your plans and are they fully costed in your budget?'''

''We plan to record all sessions. The cost is already included in the budget (sent privately). There is no plan for streaming because that will mean increasing the cost too much as we will need to add a much higher bandwidth on the venue along with more technicians on site.
''

== Jonathan Moules ==

* '''I didn't see anything about sustainability (of the eco-friendly variety) in there apart from the venue itself being sustainable. What are your sustainability aims? Thoughts:'''

''The BALOC is committed to set up a Sustainability and Social Responsibility Plan for our conference based on the resources available in our country.
On the following questions we will answer part of our currently planned strategy towards this.''

* '''Will you be sourcing your "conference swag" sustainably (i.e., not from sources that exploit Indiginous People?)'''

''One of our goals is to reduce the swag as much as possible as it generally ends up being waste. We are going to provide reusable water bottles to avoid the usage of one use plastic bottles during the conference and other possible useful objects to use during the conference.
About explotation, see next question.''

* '''Will you be sourcing your Tea/Coffee/Chocolate sustainably (i.e., not from sources that exploit Indiginous People & children?)'''

''Of course as part of this sustainability effort we will check that we don’t buy goods or use services provided by an exploiting company.''

* '''Will your caterers source food locally by preference?'''

''Most food in the city already comes from horticulture producers in the near rural towns. Buenos Aires province is one of the largest meat and dairy producers in the country. We plan to have as many sources of local, small and family producers and organically produced food as possible.''

* '''Does your travel grant prioritise sustainable travel over flying?'''

''Whenever possible, we will try to use sustainable transport. But we understand that the Travel Grant should also apply to nearby countries, which may not be reachable unless by plane. See answer about regional travel.''

* '''Will you be providing bottled water or some re-usable cups (FOSS4G UK did this for 2019 - worked well)?'''

''We will provide each attendee with a reusable water bottle and there will be water fountains all over the venue, including hot water for those who want to drink tea or mate.
We are aiming for local and regional products to minimize the carbon footprint of transport. We will also use as much recycled materials as possible. Non-expendable material used on the conference will be either sold after the conference or reused by the BALOC in future events.''

* '''Will the food lean away from carbon-intensive foodstuffs?'''

''We will balance the diet (unless special needs are required) with fresh non-processed food.
The food that’s not eaten each day will be sent to a local organization that delivers to people living on the streets or community kitchens.''

* '''How do you anticipate regional participants to travel there? (I'm guessing Local = public transit and International = flying)'''.

''Extending the question regarding sustainability of the TGP transport:
For distances less than 400km, bus is the preferred transport near Buenos Aires. On some exceptional cases, we may even extend this distance if there is a direct road.
On the regional context, considering Latin America, it is unlikely to use any other method of transport than by plane, since distances make it difficult to use other means of transport. Bear in mind that the rail network is not as extended in the rest of the world as it is in Europe. ''

* '''Will you default to opt-out for the t-shirt?'''

''We want to reduce the amount of useless swag as possible to reduce waste. We are aware that t-shirts are very appreciated by a big part of our attendees, so we will offer them optionally to those who have a special interest, along with other optional swag. This also helps reducing the ticket price and allows us to operate on a lower budget.''

* '''Will you provide any sort of carbon-credit offset as part of the conference fee for those who choose to fly?'''

''On the proposal we focused on the things the BALOC could directly impact to reduce the carbon footprint and waste. We didn’t plan yet for what attendees can do to reduce their pollution.
But it is in the schedule to contact in the future some association like Vida Silvestre (https://www.vidasilvestre.org.ar/) and add an optional donation to compensate for carbon footprint.''

* '''Will you cater to various dietary requirements?'''

''The catering will serve food for people with special requirements such as celiac disease, vegan diet, food allergies or intolerances. We will ask in advance to make sure all attendees have food adapted to their needs.
The menu will be healthy and varied, covering nutritional needs.''

* '''Travel Grant - Have you considered other potentially under-represented groups - those with disabilities for instance (about 18% of the UK population - https://www.gov.uk/government/publications/disability-facts-and-figures/disability-facts-and-figures - alas I couldn't quickly find the stats for Argentina). This is far more than the ~0.4% (UK again) who identify as Non-Binary ( http://www.allabouttrans.org.uk/wp-content/uploads/2014/05/non-binary-gender-factsheet.pdf )'''

''As in FOSS4G 2018, there will be two rounds of Travel Grants. The first edition will cover under-represented groups in general, with no restrictions.
The second round will focus on groups that are greatly under-represented (women and non-binary people as they represent half the population but are not as present on our events) and local under-represented groups (native americans).
We care about people with limited mobility, that’s why, along with the help of the first Travel Grant, the venue is completely adapted and is located on a completely adapted neighbourhood with adapted access to the metro.''

* '''GeoChicas - I'm not sure what a "geochica" is, but what's the logic to arbitrarily splitting it by gender? This seems the exact opposite of the stated "inclusive".'''

''The GeoChicas event has taken place in FOSS4G 2018 and 2019 already. Although now it also includes Women in GeoSpatial (focused on geospatial technologies) and other Women in Tech associations besides GeoChicas (focused on OpenStreetMap), we decided to keep the name as an easy reference to attendees of previous FOSS4G.
The concept of safe spaces is well known in communities that work to leverage gaps on under-represented communities. Those safe spaces help in the networking, empowering and reinforcing the presence of the targeted groups in conferences, thus making the event more inclusive. In the last two years we have already seen the effects of this safe space in our community and we want to continue on this line.''

'''* You state in regards to local sourcing: "Buenos Aires province is one of the largest meat and dairy producers in the country." suggesting you plan to provision a fair amount of this. But then in response to carbon-intensive foodstuffs you say: ```"We will balance the diet (unless special needs are required) with fresh non-processed food." ``` Unfortunately these seem to be diametrically opposed notions. I think it's worth pointing out that beef and dairy are pretty much the most carbon intensive foodstuffs in their classes (beef = worst meat; dairy = worse than plant milks (https://www.bbc.co.uk/news/science-environment-46654042) ). Will you be seeking to reduce use of these? (Suggestion: A few seconds googling for "Food emissions" will find plenty of articles with suggestions for what's good/bad.)'''

''Our food providers are committed to lower our carbon footprint as much as possible, while considering the local diet and available products in the process. Using a local diet is important to ensure we don’t add carbon footprint on transport.''

'''* My question regarding the travel grant's second round - I was wondering whether you would consider disability as being suitable for this. As noted in my question, there are *far* more disabled people than non-binary. Plus of course disabled people by the very nature of their disability may have physiological and/or logistical problems travelling, not something the other groups customarily face, so the disabled would proportionately benefit the most from the grant. Would you consider including disability in this second round?'''

''To build the best TGP possible, we will consult with previous TGP coordinators (such as Steven Feldman and the Oceania LOC), on how to build an inclusive program.''

'''* Geochicas - you call this a "safe space". I was under the impression these were spaces that are hostility free (i.e. https://equal.org/safe-space-program/ ), and they were open to all (a sound notion). To me at least it seems that by disallowing a certain group of people in you're saying that group of people are not safe, something that's definitely exclusionary. Plus it could be read that other minority groups (disabled, GBTQ, etc) aren't worth a safe space, only women and non-binary are. Would you consider making this more inclusive?'''

''The full conference itself is already a safe space, according to your definition, with a CoC as a safeguard. The social event we are discussing is a safe space according to the definition usually used by feminist and people of color groups.''

''Safe spaces are not treated as a response to something negative like fighting an existing hostility; but a way to generate the confidence needed to participate in mixed spaces. It is an extra step to help networking and empower people that otherwise will tend to be isolated and therefore be at a disadvantageous position.''

== Paul Ramsey ==

*'''Your plan to scale back facilities in the event of shortfall in registrations is wise. A question on that: what are the deadlines for cancellations? How much of the deposit will they retain? Unfortunately you will not have a clear feel for potential attendance until the early bird registration period closes, which can be only a few months before the final date. At some point, the venue will ask for full payment. Do your schedule points for things like early bird line up with your decision points for things like venues?'''

If we don’t use the building, the deposit will be lost.

But we are still in negotiations to lower the seed amount. We don’t want to disclose our estimated numbers in public because that may impact the negotiation. Part of that negotiation may be lowering the amount of booked rooms and add them at a later stage when we have some more income. Considering the Law School has many classrooms and the risk of not being able to book more rooms at a later stage is lower, that may be a possibility, even if we lose part of the CEC.
On the worst case, it may mean reducing the social spaces so activities will have to share spaces or maybe move them to the park, if weather permits.

The rest of the services will charge based on the attendees number, so we don’t foresee much impact here.

*''' If you'll excuse my language, the facility prices you quote seem very "international", that is, they would be not surprising in any other major global city. At the same time, the entry fees seem very low, compared to the general foss4g trend. I see that the A/B and food costs are lower than I would "expect", have those been validated in the marketplace? Generally expensive venues have exclusive catering arrangements with firms that are equally expensive, are you allowed to use your quoted catering in the venues you have chosen?'''

You are right: the venue prices in Buenos Aires are on the high side, we were very surprised (appalled more like) by this. Buenos Aires is a central city on the region, attracting many international events, thus making prices similar to other big cities around the world.

Every price has been checked with the provider by our professional events organizer, who already knows all of them and is negotiating each contract. There were some alternative venues we discarded for being too small, not being able to offer basic services (like internet), and/or outside the city and not well connected.

About the catering, the main venue (CEC) has a variety of exclusive companies from which to choose the catering from. The one we asked to budget all the meals is the cheapest but also the one the events organizer knows to be most reliable and with high quality.

Our events organizer checked also with other companies to see if the prices were sensible and it is similar to what would cost to hire an external company for it. Even when the venues are expensive, food in Argentina is cheaper.

*'''How much of your $122K in budgeted sponsorship is "sure" already? That is, have the government corporate sponsors of this proposal made some kind of non-binding statement of interest in sponsorship?'''

We don’t want to disclose much of this because nothing is signed yet and some companies may step back if they think we are going too fast.

We have the non-signed understandment of some government entities to help us find sponsors, which may attract new players. Although most of those players will probably fall on the local category. We haven’t included those new players to the list.

Actively looking for sponsorship for 2021 when it wasn’t sure and 2020 is currently looking for sponsors seemed to us a bit aggressive, so we contacted mostly companies we understood are not that interested in Canada but may be interested in Argentina. That prevented us from contacting many tentative sponsors.

We have estimated based on what we have asked around, plus the average sponsorship levels from previous FOSS4G (with lowered percentages as this depends on the “commercial” effort of each team, which we can’t measure this properly, but also the interest on the region, which also depends on many factors).

As a very very gross estimate, between a third and a half of that sponsorship is “sure”.

*'''Not a question, but one way of squaring the "can afford it" pricing problem is an "individual" rate vs a "corporate" rate. The community pgcon.org conference in Ottawa uses this construction.'''

It’s a good idea to consider. We will study it before releasing the early bird release. In any case, separation based on regions (or economic capacity) is something we think is important.

== Eli Adam ==
* '''Before eliminating the separate-day code spint, can you poll this, [https://lists.osgeo.org/mailman/listinfo/tosprint tosprint list] ?'''

* '''Is the large venue being used for more than Opening, Closing, AGM, and Lunch?'''

[[Category:Conference Committee]]
[[Category:FOSS4G]]
[[Category:FOSS4G2021]]

FOSS4G 2021 Bid Process

2019-11-24T20:18:31Z

Elil: /* Bid Process Stage Two */

= Basics =

* FOSS4G 2021 will most likely be held in "Other Regions".
** [http://2019.foss4g.org FOSS4G 2019] was in Bucharest, Romania
** [http://2020.foss4g.org FOSS4G 2020] will be in Calgary, Canada
** FOSS4G 2021 will be ... ?

* "Letters of Intent" will be accepted from potential Local Organizing Committees (LOC) from "Other Regions" - these are all parts of the world excluding Europe and North America. If there are no submissions from groups outside Europe and North America, letters from these regions will then be solicited.
* Regardless whether one or more letter(s) of intent are received, the Conference Committee members will vote. The vote procedure for 2021 is as follows: Every member of CC votes on every LoI. LoI's that receive more than 50% of "thumbs up"-votes will pass stage 1.
* Selected letters will be invited to prepare a full bid based on the usual RFP process.
* A proposal outlining budget, potential sponsors, LOC members, and venue costs will be required, even if only one letter is received.
* Based on experiences from the past years, we would like to stress the following tasks:
** OSGeo anticipates a Travel Grant program. There is a budget from OSGeo, but we expect the bidder to further collect money for TGP and to offer free or at least reduced passes for grantees.
** The bid should stress the alignment with OSGeo values as given in OSGeo's CoC and contain hints on a conference CoC

== Voters on RfP 2021 ==

# Maria Brovelli
# Till Adams
# Steven Feldman
# David Bitner
# Paul Ramsey
# Eli Adam
# Vasile Craciunescu
# Michael Terner
# Peter Batty
# Sanghee Shin
# Mark Iliffe
# Darrell Fuhriman
# Gavin Fleming
# Claude Philipona
# Msilikale Msilanga

== CRO's on RfP 2021 ==
CRO's will receive the votes for both stages and send the final results (but no counts!) to the chair of the committee. This year we are happy to have Arnulf and Codrina on board.

* [[User:Arnulf Christl | Arnulf Christl]]
* [[User:Codrina | Codrina Maria Ilie]]

= Summary of Important Dates ([https://en.wikipedia.org/wiki/Anywhere_on_Earth AoE]) =

{|
|-
! Release RFP:
| 2019 September 6.
|-
! Letters of Intent (Stage 1) due:
| 2019 September 27.
|-
! Stage 1 question period:
| 2019 September 28. to 2018 October 4.
|-
! Stage 1 polling Period:
| 2019 October 05. to 2019 October 10.
|-
! Stage 1 decision announcement:
| 2019 October 11.
|-
! Proposals (Stage 2) due:
| 2019 November 22.
|-
! Stage 2 question period:
| 2019 November 23. to 2019 December 06.
|-
! Voting Period:
| 2019 December 07. to 2019 December 13.
|-
! Selection of host city announced
| 2019 December 18.
|}

= Letters of Intent =

* Accepted until September 27, 2019
* Limited to two pages
* Read the RFP document (below) and answer the following questions:
1. Who is your conference chair?

2. Who is on your local organizing committee (LOC)?

3. What is the experience of your committee members with similar events?

4. What is your proposed venue? (include access to Internet, room sizes, maximum attendees)

5. What are your provisional dates for the conference?

6. Early thoughts on prices of conference attendance? (indicative estimates)

7. What is the price range and general location of your proposed accommodations? (hotels)

8. Are you partnering with other organizations? (e.g. local entities or other events like HOT OSM
Summit)

9. What makes FOSS4G in your proposed location and with your team compelling?

=== RFP Documents ===

* RFP containing updated process ([https://svn.osgeo.org/osgeo/foss4g/rfp/2021/FOSS4G2021-request-for-proposal.pdf RFP])
* Budget template ([https://svn.osgeo.org/osgeo/foss4g/rfp/2021/osgeo-conference-budget-template.ods file])

= Letter of Intent Review =

* Letters of Intent were received from the following local committees:
** [https://svn.osgeo.org/osgeo/foss4g/proposals/2021/FOSS4G_2021_LOI_Istanbul.pdf FOSS4G 2021 Letter of Intent for Istanbul] [[Q&A Stage 1 Istanbul]]
** [https://svn.osgeo.org/osgeo/foss4g/proposals/2021/FOSS4G_2021_LOI_Buenos_Aires.pdf FOSS4G 2021 Letter of Intent for Buenos Aires] [[Q&A Stage 1 Buenos Aires]]
** ...

* Questions will be asked of LOCs on conference_dev 2019 September 28 to 2018 October 4 - be prepared to answer the questions ASAP!
* Conference committee will vote and results announced on 2019 October 11.
** Letters with more than 50% thumbs up will be passed on to the proposal stage.
** If there are no qualified letters from the priority region, then additional regions will be considered or solicited.

= Results Stage One =

* Both proposals passed stage 1.

== Bid Process Stage Two ==
Proposals were received from the following local committees:
* FOSS4G 2021 [https://svn.osgeo.org/osgeo/foss4g/proposals/2021/FOSS4G_2021_proposal_Buenos_Aires.pdf proposal] and [https://svn.osgeo.org/osgeo/foss4g/proposals/2021/FOSS4G_2021_proposal_Buenos_Aires_Annex.pdf Annex] for stage 2 from the Buenos Aires Team. [[Q&A Stage 2 Buenos Aires]]

= Result for Stage Two =

= Decision =

[[Category:Conference Committee]]
[[Category:FOSS4G]]
[[Category:FOSS4G2020]]

FOSS4G 2021 Bid Process

2019-09-27T05:10:15Z

Elil: /* Letter of Intent Review */ Add FOSS4G 2021 LOI for Buenos Aires

= Basics =

* FOSS4G 2021 will most likely be held in "Other Regions".
** [http://2019.foss4g.org FOSS4G 2019] was in Bucharest, Romania
** [http://2020.foss4g.org FOSS4G 2020] will be in Calgary, Canada
** FOSS4G 2021 will be ... ?

* "Letters of Intent" will be accepted from potential Local Organizing Committees (LOC) from "Other Regions" - these are all parts of the world excluding Europe and North America. If there are no submissions from groups outside Europe and North America, letters from these regions will then be solicited.
* Regardless whether one or more letter(s) of intent are received, the Conference Committee members will vote. The vote procedure for 2021 is as follows: Every member of CC votes on every LoI. LoI's that receive more than 50% of "thumbs up"-votes will pass stage 1.
* Selected letters will be invited to prepare a full bid based on the usual RFP process.
* A proposal outlining budget, potential sponsors, LOC members, and venue costs will be required, even if only one letter is received.
* Based on experiences from the past years, we would like to stress the following tasks:
** OSGeo anticipates a Travel Grant program. There is a budget from OSGeo, but we expect the bidder to further collect money for TGP and to offer free or at least reduced passes for grantees.
** The bid should stress the alignment with OSGeo values as given in OSGeo's CoC and contain hints on a conference CoC

== Voters on RfP 2021 ==

# Maria Brovelli
# Till Adams
# Steven Feldman
# David Bitner
# Paul Ramsey
# Eli Adam
# Vasile Craciunescu
# Michael Terner
# Peter Batty
# Sanghee Shin
# Mark Iliffe
# Darrell Fuhriman
# Gavin Fleming
# Claude Philipona

== CRO's on RfP 2021 ==
CRO's will receive the votes for both stages and send the final results (but no counts!) to the chair of the committee. This year we are happy to have Arnulf and Codrina on board.

* [[User:Arnulf Christl | Arnulf Christl]]
* [[User:Codrina | Codrina Maria Ilie]]

= Summary of Important Dates ([https://en.wikipedia.org/wiki/Anywhere_on_Earth AoE]) =

{|
|-
! Release RFP:
| 2019 September 6.
|-
! Letters of Intent (Stage 1) due:
| 2019 September 27.
|-
! Stage 1 question period:
| 2019 September 28. to 2018 October 4.
|-
! Stage 1 polling Period:
| 2019 October 05. to 2019 October 10.
|-
! Stage 1 decision announcement:
| 2019 October 11.
|-
! Proposals (Stage 2) due:
| 2019 November 22.
|-
! Stage 2 question period:
| 2019 November 23. to 2019 December 06.
|-
! Voting Period:
| 2019 December 07. to 2019 December 13.
|-
! Selection of host city announced
| 2019 December 18.
|}

= Letters of Intent =

* Accepted until September 27, 2019
* Limited to two pages
* Read the RFP document (below) and answer the following questions:
** Who is your conference chair?
** Who else is on your LOC?
** What is your venue?
** What makes FOSS4G in your proposed location compelling?

=== RFP Documents ===

* RFP containing updated process ([https://svn.osgeo.org/osgeo/foss4g/rfp/2021/FOSS4G2021-request-for-proposal.pdf RFP])
* Budget template ([https://svn.osgeo.org/osgeo/foss4g/rfp/2021/osgeo-conference-budget-template.ods file])

= Letter of Intent Review =

* Letters of Intent were received from the following local committees:
** [https://svn.osgeo.org/osgeo/foss4g/proposals/2021/FOSS4G_2021_LOI_Istanbul.pdf FOSS4G 2021 Letter of Intent for Istanbul]
** [https://svn.osgeo.org/osgeo/foss4g/proposals/2021/FOSS4G_2021_LOI_Buenos_Aires.pdf FOSS4G 2021 Letter of Intent for Buenos Aires]
** ...

* Questions will be asked of LOCs on conference_dev 2019 September 28 to 2018 October 4 - be prepared to answer the questions ASAP!
* Conference committee will vote and results announced on 2019 October 11.
** Letters with more than 50% thumbs up will be passed on to the proposal stage.
** If there are no qualified letters from the priority region, then additional regions will be considered or solicited.

= Stage One =

== Bid Process Stage One ==

== List of voters for Stage One ==

= Result for Stage One =

Proposals were received from the following local committees:

= Decision =

[[Category:Conference Committee]]
[[Category:FOSS4G]]
[[Category:FOSS4G2020]]

FOSS4G 2021 Bid Process

2019-09-26T15:50:57Z

Elil: /* Letter of Intent Review */ Add Istanbul

= Basics =

* FOSS4G 2021 will most likely be held in "Other Regions".
** [http://2019.foss4g.org FOSS4G 2019] was in Bucharest, Romania
** [http://2020.foss4g.org FOSS4G 2020] will be in Calgary, Canada
** FOSS4G 2021 will be ... ?

* "Letters of Intent" will be accepted from potential Local Organizing Committees (LOC) from "Other Regions" - these are all parts of the world excluding Europe and North America. If there are no submissions from groups outside Europe and North America, letters from these regions will then be solicited.
* Regardless whether one or more letter(s) of intent are received, the Conference Committee members will vote. The vote procedure for 2021 is as follows: Every member of CC votes on every LoI. LoI's that receive more than 50% of "thumbs up"-votes will pass stage 1.
* Selected letters will be invited to prepare a full bid based on the usual RFP process.
* A proposal outlining budget, potential sponsors, LOC members, and venue costs will be required, even if only one letter is received.
* Based on experiences from the past years, we would like to stress the following tasks:
** OSGeo anticipates a Travel Grant program. There is a budget from OSGeo, but we expect the bidder to further collect money for TGP and to offer free or at least reduced passes for grantees.
** The bid should stress the alignment with OSGeo values as given in OSGeo's CoC and contain hints on a conference CoC

== Voters on RfP 2021 ==

# Maria Brovelli
# Till Adams
# Steven Feldman
# David Bitner
# Paul Ramsey
# Eli Adam
# Vasile Craciunescu
# Michael Terner
# Peter Batty
# Sanghee Shin
# Mark Iliffe
# Darrell Fuhriman
# Gavin Fleming
# Claude Philipona

== CRO's on RfP 2021 ==
CRO's will receive the votes for both stages and send the final results (but no counts!) to the chair of the committee. This year we are happy to have Arnulf and Codrina on board.

* [[User:Arnulf Christl | Arnulf Christl]]
* [[User:Codrina | Codrina Maria Ilie]]

= Summary of Important Dates ([https://en.wikipedia.org/wiki/Anywhere_on_Earth AoE]) =

{|
|-
! Release RFP:
| 2019 September 6.
|-
! Letters of Intent (Stage 1) due:
| 2019 September 27.
|-
! Stage 1 question period:
| 2019 September 28. to 2018 October 4.
|-
! Stage 1 polling Period:
| 2019 October 05. to 2019 October 10.
|-
! Stage 1 decision announcement:
| 2019 October 11.
|-
! Proposals (Stage 2) due:
| 2019 November 22.
|-
! Stage 2 question period:
| 2019 November 23. to 2019 December 06.
|-
! Voting Period:
| 2019 December 07. to 2019 December 13.
|-
! Selection of host city announced
| 2019 December 18.
|}

= Letters of Intent =

* Accepted until September 27, 2019
* Limited to two pages
* Read the RFP document (below) and answer the following questions:
** Who is your conference chair?
** Who else is on your LOC?
** What is your venue?
** What makes FOSS4G in your proposed location compelling?

=== RFP Documents ===

* RFP containing updated process ([https://svn.osgeo.org/osgeo/foss4g/rfp/2021/FOSS4G2021-request-for-proposal.pdf RFP])
* Budget template ([https://svn.osgeo.org/osgeo/foss4g/rfp/2021/osgeo-conference-budget-template.ods file])

= Letter of Intent Review =

* Letters of Intent were received from the following local committees:
** [https://svn.osgeo.org/osgeo/foss4g/proposals/2021/FOSS4G_2021_LOI_Istanbul.pdf FOSS4G 2021 Letter of Intent for Istanbul]
** ...

* Questions will be asked of LOCs on conference_dev 2019 September 28 to 2018 October 4 - be prepared to answer the questions ASAP!
* Conference committee will vote and results announced on 2019 October 11.
** Letters with more than 50% thumbs up will be passed on to the proposal stage.
** If there are no qualified letters from the priority region, then additional regions will be considered or solicited.

= Stage One =

== Bid Process Stage One ==

== List of voters for Stage One ==

= Result for Stage One =

Proposals were received from the following local committees:

= Decision =

[[Category:Conference Committee]]
[[Category:FOSS4G]]
[[Category:FOSS4G2020]]

FOSS4G 2021 Bid Process

2019-06-05T14:48:16Z

Elil: /* Summary of Important Dates (AoE) */ add stage 1 polling period

'''!!! THIS IS THE FIRST DRAFT AND NOT READY FOR RELEASE! PLEASE WAIT UNTIL OSGEO's CONFERENCE COMMITTEE SENDS OUT THE OFFICIAL CALL FOR 2021 !!!'''

= Basics =

* FOSS4G 2021 will most likely be held in "Other Regions".
** [http://2019.foss4g.org FOSS4G 2019] will be in Bucharest, Romania
** [http://2020.foss4g.org FOSS4G 2020] will be in Calgary, Canada

* "Letters of Intent" will be accepted from potential Local Organizing Committees (LOC) from "Other Regions" - these are all parts of the world excluding Europe and North America. If there are no submissions from groups outside Europe and North America, letters from these regions will then be solicited.
* Regardless whether one or more letter(s) of intent are received, the Conference Committee members will vote. The vote procedure for 2021 is as follows: Every member of CC votes on every LoI. LoI's that receive more than 50% of "thumbs up"-votes will pass stage 1.
* Selected letters will be invited to prepare a full bid based on the usual RFP process.
* A proposal outlining budget, potential sponsors, LOC members, and venue costs will be required, even if only one letter is received.
* Based on experiences from the past years, we would like to stress the following tasks:
** OSGeo anticiates a Travel Grant program. For this there is a budget from OSGeo, but we expect the bidder to further collect money for TGP and to offer free or at least reduced passes for grantees.
** The bid should stress the alignment with OSGeo values as given in OSGeo's CoC and contain hints on a conference CoC

= Summary of Important Dates ([https://en.wikipedia.org/wiki/Anywhere_on_Earth AoE]) =

{|
|-
! Release RFP:
| 2019 September 6.
|-
! Letters of Intent (Stage 1) due:
| 2019 September 27.
|-
! Stage 1 question period:
| 2019 September 28. to 2018 October 4.
|-
! Stage 1 polling Period:
| 2019 October 05. to 2019 October 10.
|-
! Stage 1 decision announcement:
| 2019 October 11.
|-
! Proposals (Stage 2) due:
| 2019 November 22.
|-
! Stage 2 question period:
| 2019 November 23. to 2019 December 06.
|-
! Voting Period:
| 2019 December 07. to 2019 December 13.
|-
! Selection of host city announced
| 2019 December 18.
|}

= Letters of Intent =

* Accepted until September 27., 2019
* Limited to two pages
* Read the RFP document (below) and answer the following questions:
** Who is your conference chair?
** Who else is on your LOC?
** What is your venue?
** What makes FOSS4G in your proposed location compelling?

=== RFP Documents ===

* RFP containing updated process ([https://svn.osgeo.org/osgeo/foss4g/rfp/2021/FOSS4G2021-request-for-proposal.pdf RFP]) (NOT YET FINISHED!)
* Budget template ([https://svn.osgeo.org/osgeo/foss4g/rfp/2021/osgeo-conference-budget-template.ods file]) (NOT YET FINISHED!)

= Letter of Intent Review =

* Letters of Intent were received from the following local committees:

* Questions will be asked of LOCs on conference_dev 2019 September 28. to 2018 October 4. - be prepared to answer the questions ASAP!
* Conference committee will vote and results announced on 2019 October 11.
** Letters with more than 50% thumbs up will be passed on to the proposal stage.
** If there are no qualified letters from the priority region, then additional regions will be considered or solicited.

= Stage One =
== Bid Process Stage One ==

[1] https://wiki.osgeo.org/wiki/FOSS4G_2020_Bid_Process

== List of voters for Stage One ==
* Eli Adam
* Till Adams
* Peter Batty
* David Bitner
* Maria Brovelli
* Vasile Craciunescu
* Steven Feldman
* Gavin Fleming
* Darrell Fuhriman
* Claude Philipona
* Venkatesh Raghavan
* Paul Ramsey
* Sanghee Shin
* Guido Stein
* Michael Terner
* Msilikale Msilanga
* Mark Iliffle
* NN (potential new member from BLOC 2019)

= Result for Stage One =

Proposals were received from the following local committees:

= Decision =

[[Category:Conference Committee]]
[[Category:FOSS4G]]
[[Category:FOSS4G2020]]

FOSS4G 2020 Bid Process

2018-12-18T17:07:39Z

Elil: /* Result for Stage One */

= Basics =

* FOSS4G 2020 will most likely be held in North America.
** [http://2018.foss4g.org FOSS4G 2018] took place in Dar es Salam, Tanzania
** [http://2019.foss4g.org FOSS4G 2019] will be in Bucharest, Romania

* "Letters of Intent" will be accepted from potential Local Organizing Committees (LOC) from North America. If there are no submissions from groups in North America, letters from other regions will then be solicited.
* Regardless whether one or more letter(s) of intent are received, the Conference Committee members will vote. The vote procedure for 2020 is as follows: Every member of CC votes on every LoI. LoI's that receive more than 50% of "thumbs up"-votes will pass stage 1.
* Selected letters will be invited to prepare a full bid based on the usual RFP process.
* A proposal outlining budget, potential sponsors, LOC members, and venue costs will be required, even if only one letter is received.
* Based on experiences from the past years, we would like to stress the following tasks:
** OSGeo anticiates a Travel Grant program. For this there is a budget from OSGeo, but we expect the bidder to further collect money for TGP and to offer free or at least reduced passes for grantees.
** The bid should stress the alignment with OSGeo values as given in OSGeo's CoC and contain hints on a conference CoC

= Summary of Important Dates ([https://en.wikipedia.org/wiki/Anywhere_on_Earth AoE]) =

{|
|-
! Release RFP:
| 2018 September 14.
|-
! Letters of Intent (Stage 1) due:
| 2018 October 5.
|-
! Stage 1 question period:
| 2018 October 6. to 2018 October 12.
|-
! Stage 1 decision:
| 2018 October 19.
|-
! Proposals (Stage 2) due:
| 2018 November 23.
|-
! Stage 2 question period:
| 2018 November 24. to 2018 December 05.
|-
! Voting Period:
| 2018 December 06. to December 12.
|-
! Selection of host city announced
| 2018 December 19.
|}

= Letters of Intent =

* Accepted until October 5, 2018
* Limited to two pages
* Read the RFP document (below) and answer the following questions:
** Who is your conference chair?
** Who else is on your LOC?
** What is your venue?
** What makes FOSS4G in your proposed location compelling?

=== RFP Documents ===

* RFP containing updated process ([https://svn.osgeo.org/osgeo/foss4g/rfp/2020/FOSS4G2020-request-for-proposal.pdf RFP])
* Budget template ([https://svn.osgeo.org/osgeo/foss4g/rfp/2020/osgeo-conference-budget-template.ods file])

= Letter of Intent Review =

* Letters of Intent were received from the following local committees:
** [https://svn.osgeo.org/osgeo/foss4g/proposals/2020/FOSS4G_2020_LOI_Halifax.pdf FOSS4G 2020 Letter of Intent for Halifax] [[FOSS4G2020_Q&A_Halifax]]
** [https://svn.osgeo.org/osgeo/foss4g/proposals/2020/FOSS4G_2020_LOI_Calgary.pdf FOSS4G 2020 Letter of Intent for Calgary] [[FOSS4G2020_Q&A_Calgary]]
** [http://svn.osgeo.org/osgeo/foss4g/proposals/2020/FOSS4G_2020_LOI_Niagara_Falls.pdf FOSS4G 2020 Letter of Intent for Niagara Falls] [[FOSS4G2020_Q&A_Niagara]]

* Questions will be asked of LOCs on conference_dev 2018 October 6 to 2018 October 12 - be prepared to answer the questions ASAP!
* Conference committee will vote and results announced on 2018 October 19.
** Letters with more than 50% thumbs up will be passed on to the proposal stage.
** If there are no qualified letters from the priority region, then additional regions will be considered or solicited.

= Stage One =
== Bid Process Stage One ==
Dear Voting Members of OSGeo's Conference Committee,

I know, it's still some time left today, but as I am on my way back from Barcelona home tomorrow, I herewith send out the call on voting on the three fantastic LoI's for hosting FOSS4G 2020, that we received. Due to our timetable in [1] the voting period on the LoI's lasts from 13th to 18th of October (last possible time).

So please send your votes to:

Arnulf Christl and Cameron Shorter

The voting mechanism for stage 1 is as follows: Please vote on every single LoI with one thumb up / thumb down each and send your *three* votes to the two guys mentioned above - no of the mails to me, neither CC, nor BCC.

Your Email can look as follows:

Halifax +1

Calgary +1

Niagara Falls +1

(Of course only in case, that you vote *thumbs up* for all tree ;-). BTW: A vote against can be a "-1" and this is not comparable with the "-1" we know from OSgeo discussions, because here it does not require any reason and/or alternative, it just means "thumb down".... )

Please find all relevant information on the WIKI [1]. The teams that receive more +1's than -1's LoI's will pass stage 1.

I hope, that ALL of us will send their voting emails to Arnulf and Cameron before the last possibe time on 18th of October 2018 passed - as said, we need a strong quorum, especially when there are three teams from one country bidding for the same conference.

Regards, Till

[1] https://wiki.osgeo.org/wiki/FOSS4G_2020_Bid_Process

== List of voters for Stage One ==
* Eli Adam
* Till Adams
* Peter Batty
* David Bitner
* Maria Brovelli
* Vasile Craciunescu
* Steven Feldman
* Gavin Fleming
* Darrell Fuhriman
* Claude Philipona
* Venkatesh Raghavan
* <del>Paul Ramsey </del> -> member of Calgary LOC
* Sanghee Shin
* Guido Stein
* Michael Terner
* Msilikale Msilanga
* Mark Iliffle

= Result for Stage One =
Halifax and Calgary were selected to move to stage two. Email list [https://lists.osgeo.org/pipermail/conference_dev/2018-October/004967.html announcement] and [https://lists.osgeo.org/pipermail/conference_dev/2018-October/004972.html confirmation].

Proposals were received from the following local committees:
* FOSS4G 2020 [https://drive.google.com/file/d/1cP3udoGddR68d3znwHkPmaT8-MpbS7Kz/view Proposal] for Halifax [[FOSS4G2020_Q&A_2_Halifax]]
* FOSS4G 2020 [https://drive.google.com/file/d/1Tz9USpNY4S6iqljw1BmnWyM8RfuSISw9/view Proposal] for Calgary [[FOSS4G2020_Q&A_2_Calgary]]

= Decision =
We, OSGeo's CC, advise the board to select *Calgary* as the winning team. Email list [https://lists.osgeo.org/pipermail/conference_dev/2018-December/005017.html announcement] with CRO [https://lists.osgeo.org/pipermail/conference_dev/2018-December/005020.html confirmation] and the other CRO [https://lists.osgeo.org/pipermail/conference_dev/2018-December/005023.html confirmation].

[[Category:Conference Committee]]
[[Category:FOSS4G]]
[[Category:FOSS4G2020]]

FOSS4G 2020 Bid Process

2018-12-18T17:02:37Z

Elil: Fix typo, add links.

= Basics =

* FOSS4G 2020 will most likely be held in North America.
** [http://2018.foss4g.org FOSS4G 2018] took place in Dar es Salam, Tanzania
** [http://2019.foss4g.org FOSS4G 2019] will be in Bucharest, Romania

* "Letters of Intent" will be accepted from potential Local Organizing Committees (LOC) from North America. If there are no submissions from groups in North America, letters from other regions will then be solicited.
* Regardless whether one or more letter(s) of intent are received, the Conference Committee members will vote. The vote procedure for 2020 is as follows: Every member of CC votes on every LoI. LoI's that receive more than 50% of "thumbs up"-votes will pass stage 1.
* Selected letters will be invited to prepare a full bid based on the usual RFP process.
* A proposal outlining budget, potential sponsors, LOC members, and venue costs will be required, even if only one letter is received.
* Based on experiences from the past years, we would like to stress the following tasks:
** OSGeo anticiates a Travel Grant program. For this there is a budget from OSGeo, but we expect the bidder to further collect money for TGP and to offer free or at least reduced passes for grantees.
** The bid should stress the alignment with OSGeo values as given in OSGeo's CoC and contain hints on a conference CoC

= Summary of Important Dates ([https://en.wikipedia.org/wiki/Anywhere_on_Earth AoE]) =

{|
|-
! Release RFP:
| 2018 September 14.
|-
! Letters of Intent (Stage 1) due:
| 2018 October 5.
|-
! Stage 1 question period:
| 2018 October 6. to 2018 October 12.
|-
! Stage 1 decision:
| 2018 October 19.
|-
! Proposals (Stage 2) due:
| 2018 November 23.
|-
! Stage 2 question period:
| 2018 November 24. to 2018 December 05.
|-
! Voting Period:
| 2018 December 06. to December 12.
|-
! Selection of host city announced
| 2018 December 19.
|}

= Letters of Intent =

* Accepted until October 5, 2018
* Limited to two pages
* Read the RFP document (below) and answer the following questions:
** Who is your conference chair?
** Who else is on your LOC?
** What is your venue?
** What makes FOSS4G in your proposed location compelling?

=== RFP Documents ===

* RFP containing updated process ([https://svn.osgeo.org/osgeo/foss4g/rfp/2020/FOSS4G2020-request-for-proposal.pdf RFP])
* Budget template ([https://svn.osgeo.org/osgeo/foss4g/rfp/2020/osgeo-conference-budget-template.ods file])

= Letter of Intent Review =

* Letters of Intent were received from the following local committees:
** [https://svn.osgeo.org/osgeo/foss4g/proposals/2020/FOSS4G_2020_LOI_Halifax.pdf FOSS4G 2020 Letter of Intent for Halifax] [[FOSS4G2020_Q&A_Halifax]]
** [https://svn.osgeo.org/osgeo/foss4g/proposals/2020/FOSS4G_2020_LOI_Calgary.pdf FOSS4G 2020 Letter of Intent for Calgary] [[FOSS4G2020_Q&A_Calgary]]
** [http://svn.osgeo.org/osgeo/foss4g/proposals/2020/FOSS4G_2020_LOI_Niagara_Falls.pdf FOSS4G 2020 Letter of Intent for Niagara Falls] [[FOSS4G2020_Q&A_Niagara]]

* Questions will be asked of LOCs on conference_dev 2018 October 6 to 2018 October 12 - be prepared to answer the questions ASAP!
* Conference committee will vote and results announced on 2018 October 19.
** Letters with more than 50% thumbs up will be passed on to the proposal stage.
** If there are no qualified letters from the priority region, then additional regions will be considered or solicited.

= Stage One =
== Bid Process Stage One ==
Dear Voting Members of OSGeo's Conference Committee,

I know, it's still some time left today, but as I am on my way back from Barcelona home tomorrow, I herewith send out the call on voting on the three fantastic LoI's for hosting FOSS4G 2020, that we received. Due to our timetable in [1] the voting period on the LoI's lasts from 13th to 18th of October (last possible time).

So please send your votes to:

Arnulf Christl and Cameron Shorter

The voting mechanism for stage 1 is as follows: Please vote on every single LoI with one thumb up / thumb down each and send your *three* votes to the two guys mentioned above - no of the mails to me, neither CC, nor BCC.

Your Email can look as follows:

Halifax +1

Calgary +1

Niagara Falls +1

(Of course only in case, that you vote *thumbs up* for all tree ;-). BTW: A vote against can be a "-1" and this is not comparable with the "-1" we know from OSgeo discussions, because here it does not require any reason and/or alternative, it just means "thumb down".... )

Please find all relevant information on the WIKI [1]. The teams that receive more +1's than -1's LoI's will pass stage 1.

I hope, that ALL of us will send their voting emails to Arnulf and Cameron before the last possibe time on 18th of October 2018 passed - as said, we need a strong quorum, especially when there are three teams from one country bidding for the same conference.

Regards, Till

[1] https://wiki.osgeo.org/wiki/FOSS4G_2020_Bid_Process

== List of voters for Stage One ==
* Eli Adam
* Till Adams
* Peter Batty
* David Bitner
* Maria Brovelli
* Vasile Craciunescu
* Steven Feldman
* Gavin Fleming
* Darrell Fuhriman
* Claude Philipona
* Venkatesh Raghavan
* <del>Paul Ramsey </del> -> member of Calgary LOC
* Sanghee Shin
* Guido Stein
* Michael Terner
* Msilikale Msilanga
* Mark Iliffle

= Result for Stage One =
Halifax and Calgary were selected to move to stage two.

Proposals were received from the following local committees:
* FOSS4G 2020 [https://drive.google.com/file/d/1cP3udoGddR68d3znwHkPmaT8-MpbS7Kz/view Proposal] for Halifax [[FOSS4G2020_Q&A_2_Halifax]]
* FOSS4G 2020 [https://drive.google.com/file/d/1Tz9USpNY4S6iqljw1BmnWyM8RfuSISw9/view Proposal] for Calgary [[FOSS4G2020_Q&A_2_Calgary]]

= Decision =
We, OSGeo's CC, advise the board to select *Calgary* as the winning team. Email list [https://lists.osgeo.org/pipermail/conference_dev/2018-December/005017.html announcement] with CRO [https://lists.osgeo.org/pipermail/conference_dev/2018-December/005020.html confirmation] and the other CRO [https://lists.osgeo.org/pipermail/conference_dev/2018-December/005023.html confirmation].

[[Category:Conference Committee]]
[[Category:FOSS4G]]
[[Category:FOSS4G2020]]

FOSS4G2020 Q&A Calgary

2018-10-09T00:33:54Z

Elil: Add wifi fee question from Eli

'''Questions Mark I.:'''

* '''What is the mission of your respective FOSS4G?'''
* '''Answer:'''

* '''What is your commitment to inclusivity, diversity, and ensuring that FOSS4G 2020 is as inclusive and as diverse as possible?'''
* '''Answer:'''

'''Questions Steven F.:'''

* '''early bird registration will be approximately $650.00 US while regular conference fee would be $800.00 US” there has been a lot of discussion about making FOSS4G more affordable, do you have any thoughts on this?'''
* '''Answer:'''

'''Questions Till A.:'''
* '''I would like to stress the point about costs. In the call we say "We hope to keep cost per participant under $650 USD for the conference (plus workshops).". As former chair I know about the difficulties FOSS4G teams have finding the right price for the conference. But can you tell something on how you are planning to enable people, who can not afford the conference fee and/or accommodation costs, to attend to your conference?'''
* '''Answer:'''

'''Questions Eli A.:'''
* '''It seems that the venue might be charging a fee for wifi, is that fee to the attendees or the LOC when renting the venue? "Wifi and hardwired internet will be available to attendees for a fee." In past years, wifi without a fee has been critically important and the wifi has to be able to handle lots of traffic (major project releases that everyone downloads at once) and not block ports for IRC or other non-http(s) protocols. Can you clarify the wifi?'''
* '''Answer:'''

FOSS4G 2020 Bid Process

2018-10-06T06:08:12Z

Elil: /* Letter of Intent Review */ Add Niagara Falls

= Basics =

* FOSS4G 2020 will most likely be held in North America.
** [http://2018.foss4g.org FOSS4G 2018] took place in Dar es Salam, Tansania
** [http://2019.foss4g.org FOSS4G 2019] will be in Bucarest, Romania

* "Letters of Intent" will be accepted from potential Local Organizing Committees (LOC) from North America. If there are no submissions from groups in North America, letters from other regions will then be solicited.
* Regardless whether one or more letter(s) of intent are received, the Conference Committee members will vote. The vote procedure for 2020 is as follows: Every member of CC votes on every LoI. LoI's that receive more than 50% of "thumbs up"-votes will pass stage 1.
* Selected letters will be invited to prepare a full bid based on the usual RFP process.
* A proposal outlining budget, potential sponsors, LOC members, and venue costs will be required, even if only one letter is received.
* Based on experiences from the past years, we would like to stress the following tasks:
** OSGeo anticiates a Travel Grant program. For this there is a budget from OSGeo, but we expect the bidder to further collect money for TGP and to offer free or at least reduced passes for grantees.
** The bid should stress the alignment with OSGeo values as given in OSGeo's CoC and contain hints on a conference CoC

= Summary of Important Dates ([https://en.wikipedia.org/wiki/Anywhere_on_Earth AoE]) =

{|
|-
! Release RFP:
| 2018 September 14.
|-
! Letters of Intent (Stage 1) due:
| 2018 October 5.
|-
! Stage 1 question period:
| 2018 October 6. to 2018 October 12.
|-
! Stage 1 decision:
| 2018 October 19.
|-
! Proposals (Stage 2) due:
| 2018 November 23.
|-
! Stage 2 question period:
| 2018 November 24. to 2018 November 30.
|-
! Voting Period:
| 2018 December 06. to December 12.
|-
! Selection of host city announced
| 2018 December 19.
|}

= Letters of Intent =

* Accepted until October 5, 2018
* Limited to two pages
* Read the RFP document (below) and answer the following questions:
** Who is your conference chair?
** Who else is on your LOC?
** What is your venue?
** What makes FOSS4G in your proposed location compelling?

=== RFP Documents ===

* RFP containing updated process ([https://svn.osgeo.org/osgeo/foss4g/rfp/2020/FOSS4G2020-request-for-proposal.pdf RFP])
* Budget template ([https://svn.osgeo.org/osgeo/foss4g/rfp/2020/osgeo-conference-budget-template.ods file])

= Letter of Intent Review =

* Letters of Intent were received from the following local committees:
** [https://svn.osgeo.org/osgeo/foss4g/proposals/2020/FOSS4G_2020_LOI_Halifax.pdf FOSS4G 2020 Letter of Intent for Halifax] [[FOSS4G2020_Q&A_Halifax]]
** [https://svn.osgeo.org/osgeo/foss4g/proposals/2020/FOSS4G_2020_LOI_Calgary.pdf FOSS4G 2020 Letter of Intent for Calgary] [[FOSS4G2020_Q&A_Calgary]]
** [http://svn.osgeo.org/osgeo/foss4g/proposals/2020/FOSS4G_2020_LOI_Niagara_Falls.pdf FOSS4G 2020 Letter of Intent for Niagara Falls] [[FOSS4G2020_Q&A_Niagara]]

* Questions will be asked of LOCs on conference_dev 2018 October 6 to 2018 October 12 - be prepared to answer the questions ASAP!
* Conference committee will vote and results announced on 2018 October 19.
** Letters with more than 50% thumbs up will be passed on to the proposal stage.
** If there are no qualified letters from the priority region, then additional regions will be considered or solicited.

= Bid Process =

= Decision =

[[Category:Conference Committee]]
[[Category:FOSS4G]]
[[Category:FOSS4G2020]]

FOSS4G 2020 Bid Process

2018-10-05T22:05:57Z

Elil: Add LOI review section outline

= Basics =

* FOSS4G 2020 will most likely be held in North America.
** [http://2018.foss4g.org FOSS4G 2018] took place in Dar es Salam, Tansania
** [http://2019.foss4g.org FOSS4G 2019] will be in Bucarest, Romania

* "Letters of Intent" will be accepted from potential Local Organizing Committees (LOC) from North America. If there are no submissions from groups in North America, letters from other regions will then be solicited.
* Regardless whether one or more letter(s) of intent are received, the Conference Committee members will vote. The vote procedure for 2020 is as follows: Every member of CC votes on every LoI. LoI's that receive more than 50% of "thumbs up"-votes will pass stage 1.
* Selected letters will be invited to prepare a full bid based on the usual RFP process.
* A proposal outlining budget, potential sponsors, LOC members, and venue costs will be required, even if only one letter is received.
* Based on experiences from the past years, we would like to stress the following tasks:
** OSGeo anticiates a Travel Grant program. For this there is a budget from OSGeo, but we expect the bidder to further collect money for TGP and to offer free or at least reduced passes for grantees.
** The bid should stress the alignment with OSGeo values as given in OSGeo's CoC and contain hints on a conference CoC

= Summary of Important Dates ([https://en.wikipedia.org/wiki/Anywhere_on_Earth AoE]) =

{|
|-
! Release RFP:
| 2018 September 14.
|-
! Letters of Intent (Stage 1) due:
| 2018 October 5.
|-
! Stage 1 question period:
| 2018 October 6. to 2018 October 12.
|-
! Stage 1 decision:
| 2018 October 19.
|-
! Proposals (Stage 2) due:
| 2018 November 23.
|-
! Stage 2 question period:
| 2018 November 24. to 2018 November 30.
|-
! Voting Period:
| 2018 December 06. to December 12.
|-
! Selection of host city announced
| 2018 December 19.
|}

= Letters of Intent =

* Accepted until October 5, 2018
* Limited to two pages
* Read the RFP document (below) and answer the following questions:
** Who is your conference chair?
** Who else is on your LOC?
** What is your venue?
** What makes FOSS4G in your proposed location compelling?

=== RFP Documents ===

* RFP containing updated process ([https://svn.osgeo.org/osgeo/foss4g/rfp/2020/FOSS4G2020-request-for-proposal.pdf RFP])
* Budget template ([https://svn.osgeo.org/osgeo/foss4g/rfp/2020/osgeo-conference-budget-template.ods file])

= Letter of Intent Review =

* Letters of Intent were received from the following local committees:
** [https://svn.osgeo.org/osgeo/foss4g/proposals/2020/FOSS4G_2020_LOI_Halifax.pdf FOSS4G 2019 Letter of Intent for Halifax] [[FOSS4G2020_Q&A_Halifax]]
** [https://svn.osgeo.org/osgeo/foss4g/proposals/2020/FOSS4G_2020_LOI_Calgary.pdf FOSS4G 2019 Letter of Intent for Calgary] [[FOSS4G2020_Q&A_Calgary]]

* Questions will be asked of LOCs on conference_dev 2018 October 6 to 2018 October 12 - be prepared to answer the questions ASAP!
* Conference committee will vote and results announced on 2018 October 19.
** Letters with more than 50% thumbs up will be passed on to the proposal stage.
** If there are no qualified letters from the priority region, then additional regions will be considered or solicited.

= Bid Process =

= Decision =

[[Category:Conference Committee]]
[[Category:FOSS4G]]
[[Category:FOSS4G2020]]

FOSS4G Handbook

2018-09-14T23:48:03Z

Elil: /* Vimeo */ update external link brackets []

This FOSS4G Handbook aims to provide guidance to future FOSS4G and FOSS4G related events, based upon the collective wisdom gained during prior events. It is a continuous work in progress and is a '''guide''' rather than a '''rulebook'''. Feel free to modify any aspect. If in doubt, ask the community what they think. This event is designed for the OSGeo community. We encourage all FOSS4G organizers to contribute to and enhance this Handbook.

= About FOSS4G =
Free and Open Source for Geospatial (FOSS4G) conferences refer to a series of events which provides presentations, workshops, and networking opportunities based around Free and Open Source Software for Geospatial.

FOSS4G includes one annual global event which rotates around the world, as well as a number of regional events which follow similar principles.

;See Also
: [https://wiki.osgeo.org/wiki/FOSS4G FOSS4G History]
: [https://docs.google.com/spreadsheets/d/1BpkO5WOFQ_DZEWNMLj_hAhEre0m0io_j-JGf7geAW5Y/edit?hl=en_GB#gid=57 FOSS4G Metrics]

= Editing this document =

This FOSS4G Handbook aims to be concise, so that it is easy to read and follow. We also aim to collaboratively edit and continuously build this document based upon our collective experience running conferences. As such, we will need to continuously update and delete old text as new ideas come to hand.

The process to follow in updating this wiki is:
* Feel free to make trivial tweaks to grammar and syntax.
* If you would like to introduce a new idea, maybe add a new section, or improve an old section:
** Raise your suggestion on the [http://lists.osgeo.org/mailman/listinfo/conference_dev OSGeo Conference] email list.
** Once a rough consensus has been reached on the list, you may then update the Handbook with the collective wisdom of the list.
** If writing a new section, consider starting the section with: Draft, awaiting review
** After updating your text, notify the list again to give others the opportunity to review and tweak.

= Section Writing Guide =
Draft, awaiting review

The first sentence(s) of a section should describe the meaning of the heading. Eg, if this section is on "Birds of a Feather", then the first sentence should start with: ''Birds of a Feather sessions refer to semi-formal gatherings of like minded delegates to discuss a topic of interest.''

; Relevance:
: International FOSS4G: [Mandatory, Recommended, Optional, Not Relevant]
: Regional FOSS4G: [Mandatory, Recommended, Optional, Not Relevant]
: FOSS4G stream / Local Event: [Mandatory, Recommended, Optional, Not Relevant]

Following paragraphs provide specific details. They might hyperlink to more details from an external Lessons Learned type doc. It will likely cover some of the following topics:
* Key success factors
* Things that can go wrong, with optional brief examples
* List of considerations and why choose one consideration over another
* List of steps to follow
* Organizations or people to contact to coordinate with
* Links to external documents, such as a Google Docs spreadsheet

; See Also:
:* Where relevant, finish with a list of links to web pages for further reading. E.g.
:* [http://wiki.osgeo.org/wiki/FOSS4G_2009_Lessons_Learned#Birds_of_a_Feather FOSS4G 2009 Birds of Feather Lessons Learned]

=Preparing FOSS4G RFP=
Draft, awaiting review

Selection of the international FOSS4G venue, involves two stages, a "Letter of Intent" (LOI) followed by a full "Request for Proposal" (RFQ). Only cities which attract two or more committee member votes from the LOI move onto the RFQ.

; Relevance:
: International FOSS4G: Mandatory
: Regional FOSS4G: Optional
: FOSS4G stream / Local Event: Usually Not Relevant

The process for preparing an RFP for the annual FOSS4G is:
* Copy the previous year's FOSS4G RFP directory to the next year, as per: http://svn.osgeo.org/osgeo/foss4g/rfp/
* Choose a set of dates for submission deadlines and review periods and very very carefully go through the document making sure they are all reflected in the right places.
* Get in touch with the conference_dev and teams from previous year or two and get their feedback on the process for RFP changes
* Do a quick search of the conference_dev archives and see if there's other RFP process / info concerns to be addressed (like Board Face ot Face Meeting, OSGeo Annual Gathering, other requirements that are assumed but not articulated)
* Update doc appropriately
* Stub out Wiki pages using the skeletons from previous years and the dates you already put into the doc
* Get someone to review your changes
* Announce

; See Also:
:* http://svn.osgeo.org/osgeo/foss4g/rfp/

= Lessons Learned =
Draft, awaiting review

It is highly valuable to future conferences to collect the wisdom gained from prior conferences.

; Relevance:
: International FOSS4G: StronglyRecommended
: Regional FOSS4G: Recommended
: FOSS4G stream / Local Event: Optional

In FOSS4G 2009 (Sydney, Australia), we wrote down our Lessons Learned throughout the planning period, while ideas were still fresh. The FOSS4G 2013 (Nottingham, UK) LOC came together after the conference to brainstorm their lessons learned.

*[[https://wiki.osgeo.org/wiki/Past_FOSS4G_Reports|Past FOSS4G Conference Reports]] provides the attendance, sponsorship and financial reports for each FOSS4G. This is a valuable resource for anyone considering submitting a proposal for a FOSS4G events

; See Also:
*[[FOSS4G 2016 Lessons Learned|2016]]
*[[FOSS4G 2015 Lessons Learned|2015]]
*[[FOSS4G 2014 Lessons Learned|2014]]
*[[FOSS4G2013_Reflections_by_the_LOC|2013]]
*[[FOSS4G 2012 Lessons Learned|2012]]
*[[FOSS4G 2011 Lessons Learned|2011]]
*[[FOSS4G 2010 Lessons Learned|2010]]
*[[FOSS4G 2009 Lessons Learned|2009]]
*[[FOSS4G2008 Lessons Learned|2008]]
*[[FOSS4G2007 Lessons Learned|2007]]

= Marketing =

== Press Releases ==
Draft, awaiting review

You should send out public announcements about your conference, especially around conference milestones.

; Relevance:
: International FOSS4G: Required
: Regional FOSS4G: Recommended
: FOSS4G stream / Local Event: Recommended

Make regular use the OSGeo News feed:
* initial announcement
* Call for Papers
* Start of registration, end of early booking approaching
* Program published
* etc.

Publish an official press release for the initial announcement of the conference and when the program is stable and published. Coordinate this with high level sponsors i.e. let them know when it will happen so that they can react accordingly! Get a quote form the highest available sponsor.

You will likely want to collaboratively edit press releases in a wiki page. The wiki then becomes an archive which can be handed down to future events.

Work out where you will send your announcements. It should include:
* You should submit to [http://www.osgeo.org/content/news/submit_news.html OSGeo Announcements] for inclusion on the OSGeo web site
* [http://lists.osgeo.org/mailman/listinfo/discuss OSGeo Discuss]
* Twitter
* A blog feed into [http://planet.osgeo.org/ Planet OSGeo]

; See Also:
:* http://wiki.osgeo.org/wiki/FOSS4G_2009_Press_Releases
:* http://wiki.osgeo.org/wiki/FOSS4G_2009_Lessons_Learned#Press_Releases

== twitter ==
* FOSS4G runs the [[https://twitter.com/foss4g FOSS4G twitter account]]
* The account will be passed to the new LOC each year after the conference
* Use #FOSS4G or #FOSS4G201x in your tweets (maybe also #FOSS4G?????????????)
* [[https://tweetdeck.twitter.com/ Tweetdeck]] can be used to get a better overview about tweets, notifications, retweets...
* [[http://buffer.com Buffer]] can be used to define tweets in advance and let them be posted at a defined time
* NodeXL shows you the tweet statistics in a graph

== Photos ==
FOSS4G runs a flickr group called FOSS4G. You can provide images from FOSS4G conferences to this group. You can get a member of this group and share your photos.
If you run the next FOSS4G conference you can ask to become an admin to change the configuration (ask [https://wiki.osgeo.org/wiki/User:Stevenfeldman Steven Feldman] or [https://wiki.osgeo.org/wiki/User:Astrid_Emde Astrid Emde])

* [https://www.flickr.com/groups/foss4g/ FOSS4G Group] on Flickr

==Event Listings==
Draft, awaiting review

The event should be added to event listings.

; Relevance:
: International FOSS4G: [Mandatory]
: Regional FOSS4G: [Recommended]
: FOSS4G stream / Local Event: [Recommended]

Relevant Lists include:
* http://www.osgeo.org/events
* http://wiki.osgeo.org/wiki/Global_conferences_overview
* https://wiki.osgeo.org/wiki/Live_GIS_History

; See Also:
:*

==FOSS4G Branding==
Draft, awaiting review

FOSS4G is the acronym used to describe events which are predominantly about "Free and Open Source Software for Geospatial".

; Relevance:
: International FOSS4G: [Mandatory]
: Regional FOSS4G: [Mandatory]
: FOSS4G stream / Local Event: [Mandatory]

FOSS4G is not registered as a trademark but has a long tradition of being used in the context of Free and Open Source Software for Geospatial. The domain was [[FOSS4G#History_of_the_Acronym|originally]] registered by Venkatesh Raghavan (Venka) who later graciously donated it to OSGeo - under the condition that using the name should stay open to anybody who does something reasonably related to Free and Open Source Geospatial.

A FOSS4G event can be the main international FOSS4G conference, as well as a regional event such as FOSS4G-North America. It can also be a local FOSS4G seminar drawing from one city, a FOSS4G stream in a bigger conference, a workshop or a code sprint. The number of participants can vary from ten people (code sprint) up to 1000+ people (global FOSS4G).

Use of the name "FOSS4G" is managed by the [http://wiki.osgeo.org/wiki/Conference_Committee OSGeo Conference Committee]. As a courtesy, events which wish to make use of the "FOSS4G" name should request permission to do so from the conference committee. Permission will be granted if the event being described is predominantly (say >90%) about Free and Open Source Software for Geospatial and promotes OSGeo.

; See Also:
:* http://wiki.osgeo.org/wiki/FOSS4G
:* http://wiki.osgeo.org/wiki/FOSS4G#Using_the_Name_FOSS4G
:* [[FOSS4G_Handbook#Regional_and_Local_FOSS4G_selection]]
:* http://wiki.osgeo.org/wiki/Official_OSGeo_Event_Policy

==OSGeo Branding==
Draft, awaiting review

FOSS4G events should suitably acknowledge the OSGeo foundation in promotion material.
This would typically include:
* the OSGeo logo being included on the website with words similar to "presented by OSGeo" and a link back to the OSGeo web site.
* presentation(s) by organisers (and others) should reference OSGeo

For larger events e.g. the annual international event and any event receiving OSGeo financial assistance, there should be an OSGeo booth of reasonable size and prominence provided at no charge to the foundation

; Relevance:
: International FOSS4G: [Mandatory]
: Regional FOSS4G: [Mandatory]
: FOSS4G stream / Local Event: [Recommended]

== Logo ==
[[File:OSGeo-Ribbon.jpg|thumb|right|alt=OSgeo Ribbon|OSgeo Ribbon.]]

The FOSS4G logo for the international conference has to include elements of the OSGeo / FOSS4G "ribbon" as can be seen in all previous conference logos: http://foss4g.org/, and should also include themes for the location of the current event.

; Relevance:
: International FOSS4G: [Mandatory]
: Regional FOSS4G: [Optional]
: FOSS4G stream / Local Event: [Not Applicable]

FOSS4G 2013 used a competition to design the logo. FOSS4G 2011 used [http://www.crowdspring.com crowdspring] and were very pleased with the way it worked.

Start on the logo asap as you need it for other early stage documents like the sponsorship prospectus.

=City and Date Selection=

== International FOSS4G Rotation ==
The International FOSS4G event rotates around the world, and cities compete to be selected to host the event, as described in the RFP process.

; Relevance:
: International FOSS4G: Mandatory
: Regional FOSS4G: Not Relevant
: FOSS4G stream / Local Event: Not Relevant

The regions FOSS4G rotates through are:
* Europe
* North America
* Rest of world
This is caveatted by the OSGeo Conference committee feeling confident that the proposed city/region will attract the majority of the international FOSS4G audience.

So our rotation policy is:

# Strong preference is given to the region which hasn't had FOSS4G for 2 years
# We next consider the region which had FOSS4G 2 years ago
# Only as a last resort would we consider a region which had FOSS4G last year

Prior International FOSS4G event locations have been:
* [http://2018.foss4g.org/ 2018]: Dar es Salaam, Tanzania
* [http://2017.foss4g.org/ 2017]: Boston, MA, USA
* [http://2016.foss4g.org/ 2016]: Bonn, Germany
* [http://2015.foss4g.org/ 2015]: Seoul, South Korea
* [http://2014.foss4g.org/ 2014]: Portland, Oregon, USA
* [http://2013.foss4g.org/ 2013]: Nottingham, United Kingdom
* <s>[http://2012.foss4g.org/ 2012]: Beijing, China (cancelled)</s>
* [http://2011.foss4g.org/ 2011]: Denver, United States
* [http://2010.foss4g.org/ 2010]: Barcelona, Spain
* [http://2009.foss4g.org/ 2009]: Sydney, Australia
* [http://2008.foss4g.org/ 2008]: Cape Town, South Africa
* [http://2007.foss4g.org/ 2007]: Victoria, Canada
* [http://2006.foss4g.org/ 2006]: Lausanne, Switzerland
* 2005: Minneapolis, United States
* [http://www.ces.iisc.ernet.in/energy/water/paper/fossgrdss/conference.htm 2004]: Bangkok, Thailand

; See Also:
:* http://www.osgeo.org/conference/rfp
:* http://svn.osgeo.org/osgeo/foss4g/
:* Many FOSS4G regional and related conferences are listed at: http://wiki.osgeo.org/wiki/Live_GIS_History
:* Conference committee approval of this rotation policy: http://lists.osgeo.org/pipermail/conference_dev/2013-May/002107.html

== Selecting locations which align with OSGeo principles ==

We should select locations where OSGeo principles and [https://www.osgeo.org/code_of_conduct/ Code of Conduct] align with the laws and practices of the location where the conference is being held.

; Relevance:
: International FOSS4G: Recommended
: Regional FOSS4G: Recommended
: FOSS4G stream / Local Event: Not Relevant

At FOSS4G 2018 in Tanzania we discovered that local laws decree that [https://en.wikipedia.org/wiki/LGBT_rights_in_Tanzania same-sex sexual acts are crimes punishable by the state]. This is contrary to the OSGeo Code of Conduct and is something we should try to avoid when selecting future conference venues.

; See Also:
:* [https://www.osgeo.org/code_of_conduct/ Code of Conduct]

==Regional and Local FOSS4G selection==
Draft, awaiting review

Location and date selection of FOSS4G regional and local events should be coordinated with other FOSS4G events.

Regional and Local FOSS4G events are encouraged
; Relevance:
: International FOSS4G: Not Relevant
: Regional FOSS4G: Recommended
: FOSS4G stream / Local Event: Recommended

There is a tension between supplying sufficient FOSS4G related conferences to meet demand, verses over-supply as multiple conferences potentially compete for the same speakers, sponsors and delegates. FOSS4G History, starting from around 2012 has demonstrated that there is sufficient demand to support both an international conference, as well as multiple regional conferences in the same year. This is in keeping with review of [https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdEZoOUtSeVZRVWtKQzV6R2N5ekdSdlE#gid=57 FOSS4G attendee profiles], which show over half of FOSS4G attendees tend to be drawn from the local region.
As such, OSGeo is supportive of multiple FOSS4G events being run in a year. However, OSGeo recommends scheduling FOSS4G events such that they don't overlap, and such that there is limited direct competition within regions between events.

Coordination between FOSS4G events is provided via the [http://lists.osgeo.org/mailman/listinfo/conference_dev OSGeo Conference email list]. All FOSS4G Conference Organising Committees should:
* Have at least one representative subscribe the the conference_dev email list.
* Announce intent of running a FOSS4G conference on the email list, including brief description of proposed event, proposed date(s), location, language, request to use FOSS4G name (if relevant).
* Network with others within the region. Discuss options of merging potential FOSS4G events and/or ensuring dates and locations don't conflict.
* Once location and date have been selected, list the event at http://www.osgeo.org/events.
* Also list at [http://wiki.osgeo.org/wiki/Live_GIS_History OSGeo-Live History] if making use of [http://live.osgeo.org OSGeo-Live] DVDs and/or presentation, to ensure DVDs are ready for your conference, and describe breadth of reach of OSGeo-Live to contributors and sponsors.

; See Also:
:* http://wiki.osgeo.org/wiki/FOSS4G_2012_Lessons_Learned#Competing_regional_conferences

=Schedule=
All successful events should be planned, and to help with the plan, we have a generic FOSS4G Planning Schedule which can be used as a starting point.

; Relevance
: International FOSS4G: Mandatory
: Regional FOSS4G: Mandatory
: FOSS4G stream / Local Event: Highly Recommended

When planning an event:
* Copy the [https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGdIbnY3SEZNUHp3NHdTZnlLZC1rbWc#gid=0 Generic FOSS4G Planning Schedule] into your own spreadsheet, probably onto a Google Drive so that it can be collaboratively viewed and edited.
* Tailor the plan such that it aligns with the goals for your event
* Feed improvements back into the [https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGdIbnY3SEZNUHp3NHdTZnlLZC1rbWc#gid=0 Generic FOSS4G Planning Schedule]. Non-trivial improvements should be discussed on the [http://lists.osgeo.org/mailman/listinfo/conference_dev OSGeo Conference email list] before applying.

; See Also:
:* [https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGdIbnY3SEZNUHp3NHdTZnlLZC1rbWc#gid=0 Generic FOSS4G Planning Schedule]

= Infrastructure and archiving =
Draft, awaiting review

Background:
* FOSS4G requires the establishment of various infrastructure relevant to a conference. This includes a conference website, registration website, community voting, credit card processing, LOC email list, archiving of these systems for future reference, etc.
* There may be some opportunity to reuse some of these systems.
* There should be some way to archive these for reference. In the case of the websites see the year subdomain, i.e. http://2009.foss4g.org/

; Relevance:
: International FOSS4G: Mandatory
: Regional FOSS4G: Optional?
: FOSS4G stream / Local Event: Optional?

== LOC email list ==
Draft, awaiting review

Much of the organizing and communication for the LOC happens via email. It is easy (and consistent with past practice) to use an OSGeo email list. Archiving happens automatically. There can be a list for both public and private communication, usually named foss4gyyyy and foss4gyyyy-private

; Relevance:
: International FOSS4G: Mandatory
: Regional FOSS4G: Recommended
: FOSS4G stream / Local Event: Optional/Not Relevant

; See Also:
:* Requesting an OSGeo email list: http://wiki.osgeo.org/wiki/SAC:Mailing_Lists#Requesting_a_new_list or i.e. http://trac.osgeo.org/osgeo/ticket/1202

== Website ==
Draft, awaiting review

Background:
* This is just a start at the archiving portion. More needs to be added about the requirements for selection, use, etc
* FOSS4G websites are archived in a basic form at yyyy.foss4g.org
* Some website platforms might have export options
* wget could be an archiving method too, perhaps something along the lines of:
wget --mirror --convert-links --backup-converted --html-extension
* HTTrack may be the preferred tool

; Relevance:
: International FOSS4G: Mandatory
: Regional FOSS4G: Optional?
: FOSS4G stream / Local Event: Optional?

= Diversity =
== Code of Conduct ==
Draft, awaiting review

Events should reference a Code of Conduct, probably the [http://www.osgeo.org/code_of_conduct OSGeo Code of Conduct], but you can choose one of the many other options.

; Relevance:
: International FOSS4G: Mandatory.
: Regional FOSS4G: Highly recommended.
: FOSS4G stream / Local Event: Recommended if not already covered by the main conference.
== Child Friendly Policy ==

Making a conference child friendly makes it easier for primary care givers (often mothers), the opportunity to present.

; Relevance:
: International FOSS4G: Optional
: Regional FOSS4G: Optional
: FOSS4G stream / Local Event: Optional

This requires managing an effective balance between the competing priorities of:

* High cost of dedicated childcare.
* Variability and unpredictability of different aged children.
* Retaining a professional conference environment.
* Respecting needs of children, parents, and conference participants.
* Making our conference accessible to a diverse audience, which includes those responsible for children.

FOSS4G Oceania introduced a Child Friendly Policy in 2018 which can be used as inspiration.

; See Also:
:* https://foss4g-oceania.org/child-friendly-conference
:* http://cameronshorter.blogspot.com/2018/09/child-friendly-conferences.html

= Streaming and archiving presentations and keynotes =
Draft, awaiting review
* Most FOSS4G's since 2011 (needs checking) have recorded presentations and made them available after the event.
*Since 2014 (needs checking) the proceedings have been live streamed as well as recorded which enables people who are unable to travel to a global FOSS4G to participate online and even ask questions of speakers.
* Recording and publishing helps to spread knowledge and awareness of OSGeo software

== Videos ==
Draft, awaiting review

Videoing presentations extends the reach of conference presentations to a much wider audience, but is logistically challenging, and/or expensive.

; Relevance:
: International FOSS4G: Strongly Recommended
: Regional FOSS4G: Recommended
: FOSS4G stream / Local Event: Optional

Videoing is not easy, nor inexpensive. It adds great value to OSGeo in being able to keep the presentations in perpetuity and to use them in a marketing and educational context. Equally, OSGeo has a broader mandate than an LOC to widen the reach of a FOSS4G conference to people who are unable to attend. However, the primary goal of an Organising Committee is to provide the best possible experience for those who attend the event. Hosting a FOSS4G is first and foremost for the visitors to your city and your paying customers and sponsors. Is it fair to have the Organising Committee (or rather, the paying attendees) pay for it?

There are also "scrappy" alternatives to get cheaper, poor quality content. Potentially ask attendees to record with mobile phones are upload to a central source.

As for September 2018, there have been a range of opinions on this topic, and the conference committee is yet to provide clear guidance on a path forward.

; See Also:
:* [https://lists.osgeo.org/pipermail/conference_dev/2018-September/004890.html Email list thread on videoing]

=== Vimeo ===
Foss4G runs a vimeo account. Where you can upload 20GB per week. Some conference where uploaded here. A full FOSS4G will produce more than 20GB of material..
* the account will be passed every year after the conference to the next team
* [https://vimeo.com/foss4g FOSS4G Vimeo account]
* Make sure, that you add enough metadata when you publish your video

There is a video landing page which refers to all videos from the last conferences at [http://video.foss4g.org http://video.foss4g.org]

An example of a specific landing page for [http://video.foss4g.org/foss4g2016/videos/index.html FOSS4G 2016] is managed separately by the LOC or their video team. The code for the landing page is in [https://git.osgeo.org/gitea/foss4g/video.foss4g.org OSGeo git]. You can request access and build your own landing page. FOSS4G 2014 PDX video index is indeed part of the [http://2014.foss4g.org/schedule/sessions/index.html website schedule].

=== TIB ===
* [[TIB]] in Hannover is happy to publish our videos from FOSS4G. [[User:Peter Loewe|Peter Loewe]] and [[User:Bastian|Bastian Drees]] are contact persons, see also [[Peter Loewe Videoquotes|Video Quotes]] by Peter
* Read [[FOSS for GIS video tutorials and screencasts|how to publish videos at TIB]].

=Finances=
==Guarantees==
Draft, awaiting review

The OSGeo foundation can be approached to provide financial guarantees for major FOSS4G events.

; Relevance:
: International FOSS4G: Recommended
: Regional FOSS4G: Optional
: FOSS4G stream / Local Event: Not Relevant

As per our board priorities:

Conferences are financially risky events. They need to be planned well in advance, and you are never sure how many people will turn up, or whether some global event will have a substantial impact on registrations. Consequently, conferences such as FOSS4G require financial advances up front in order to secure a venue and possibly a guarantee to underwrite potential losses or liabilities additional to the advance.

To support and enable these conferences, OSGeo will endevour to retain sufficient capital to offer such guarantees for any FOSS4G event requesting it. August 2015: The Board has been requested to determine the the extent of reserves that it will set aside for this purpose, could be a % or a minimum absolute some or some other formula.

If OSGeo's support is requested, then OSGeo would require a legal body, such as the Local Organising Committee (LOC), or Professional Conference Organisor (PCO), or similar, to enter into an agreement with OSGeo that commits both parties. Cameron Shorter: Noted that legal body need not be the LOC. For FOSS4G 2009, OSGeo signed a contract directly with the PCO.

What follows is a draft set of conditions suggested by [[User:Stevenfeldman | Steven Feldman]] for further comment:

#Any FOSS4G seeking OSGeo’s financial backing should provide a financial plan, which includes:
## Initial advance(s) required and timing
## Potential loss through cancellation at different stages
## Potential loss if conference goes ahead but attendance is less than target
## Cameron Shorter added: Financial reporting schedule, noting how often reports will be provided, and by who (typically by a PCO).
## Cameron Shorter added: Mitigation actions which will be initiated should financial targets not be reached. Eg: If we have not received $XXX funds by YYY date, we will cancel the conference, which will result in loosing $ZZZ.
#OSGeo will confirm the maximum level that it will underwrite
#OSGeo will need to set aside a reserve to cover the maximum underwritten losses of all FOSS4G events that it is supporting. This will probably limit OSGeo's ability to underwrite multiple events and may require the Conference Committee to select between competing regional events if there are several applications
#The Conference Committee will require a member to join the LOC with financial oversight of expenditure, forecasts and risks. This relies on Conference Committee members volunteering for a very high level of effort joining a LOC and keeping close track of finances and the volume of email. [[User:EliL | - Eli Adam]] 
#The Conference Committee will need to continuously review financial risk and may require changes to the financial and operational plans of an event. Likewise requires the Conference Committee to be very engaged and deeply aware of the details of potentially two or more conferences. [[User:EliL | - Eli Adam]] 
#The LOC recognises and understands that OSGeo will not accept unlimited financial liability for their event, any losses exceeding the maximum level underwritten will need to be borne by the LOC or insured locally.
#The LOC agrees to remit xx% of any surplus to OSGeo to support future events and other OSGeo activities (I would suggest at least 85% but no doubt this could be a subject for discussion across the community but it should be standard for all events)
#OSGeo will need to draft a legal agreement with the LOC that sets out these terms

; See Also:
:* Board priorities: http://wiki.osgeo.org/wiki/Board_Meeting_2013-02-26#Conferences_and_related_events

==FOSS4G nonprofit tax status==
Draft, awaiting review

While The OSGeo foundation continues to pursue nonprofit status, partnering with other like-minded qualifying nonprofit organizations to make FOSS4G a tax exempt event may be desirable.

; Relevance:
: International FOSS4G:
: Regional FOSS4G:
: FOSS4G stream / Local Event:

; This is just a place holder to be filled out later once things are determined, see Also:
:* Conference list: http://lists.osgeo.org/pipermail/conference_dev/2013-July/002303.html

== Budget ==
; See Also
:* [https://docs.google.com/spreadsheets/d/1YdFNuBNaJK2XeA-bs1vU24VA1Qv9HpN8rLs30D9_0zg/edit#gid=1040179171 FOSS4G 2013 final accounts]

=Metrics=
Draft, awaiting review

Past FOSS4G metrics are very valuable for planning future FOSS4G events, and should be collected for all events.

; Relevance:
: International FOSS4G: Mandatory
: Regional FOSS4G: Recommended
: FOSS4G stream / Local Event: Optional

Key questions that we wish to ask of our metrics:
# How many people are likely to come from a future FOSS4G event in region X?
# In the lead up to FOSS4G how many more people are likely to sign up? Eg: 200 people registered by Early Bird, will we reach our predicted 300 attendees?
# In lead up, when do sponsors sign up?
# Schedule and workshop planners wish to understand the technical expertise of participants. What is the percentage of OSGeo newbies (requiring "Introduction to ..." presentation/workshop).
# Schedule and workshop planners wish to understand which presenters and topics were popular.
# When considering whether to sponsor, and how to target spsonsorship messages, FOSS4G sponsors wish to understand the makeup of FOSS4G attendees. In particular, are attendees likely to influence decisions to purchase future software systems.
# How much sponsorship should we expect? Where in the world did previous sponsors come from?
# What is the most effective way to market FOSS4G? How did people hear about FOSS4G?

Key metrics we wish to collect from attendees:
# Registration date
# City, State, Country
# Sponsor name, amount, sign up date
# Information Source: Past attendee,Friend/colleague,E-mail list,Web badge on open source site,Grapevine,Internet Search,Web advertisement,Magazine advertisement
# Job Description 1:C-Level Executive,Manager,Consultant,Programmer,Scientist,Educator,Mysterious
#Job Responsibility 1: If I Told You I'D Have To Kill You ($1,000,000s),Heaps Of Money ($100,000s),Piles Of Money ($10,000s),Stacks Of Money ($1000s),No Money At All
# Reason For Attending: The Technical Networking,The Workshops & Technical Sessions,The Beer,The Sales Networking,Something Else Altogether

Metrics to collect about presentations:
# How many people were in the room of each presentation?
# Optional: How interesting was the topic?
# Optional: How good was the speaker?

; See Also:
:* Collated metrics from past global FOSS4G events: https://docs.google.com/spreadsheets/d/1ux_hFq-C165140ZD48RRImPTHSpXj42OG3nBr9cyZYo/edit#gid=1782600951
* Older version of the same metrics: https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdEZoOUtSeVZRVWtKQzV6R2N5ekdSdlE#gid=57
:* Peter Batty's analysis to determine if FOSS4G-NA would impact FOSS4G Global, in Oct 2011: http://osgeo-org.1560.x6.nabble.com/Re-OSGeo-Conf-North-American-FOSS4G-conference-tp3714127p3714128.html
:* FOSS4G 2013 Metrics: http://2013.foss4g.org/Surveys/delegate.html

=Travel Grants=
The travel grant programme is run by FOSs4G's Conference committee. The first TGP was run in 2017, see [[FOSS4G_Travel_Grant_Programme_2017]]

This is the old draft, the procedure was based on: [[Draft FOSS4G Travel Grants]]

=OSGeo Branding=
Draft, awaiting review

FOSS4G conferences are expected to promote the OSGeo Foundation at events.

; Relevance:
: International FOSS4G: Mandatory
: Regional FOSS4G: Recommeded
: FOSS4G stream / Local Event: Recommended

There is a symbiotic relationship between the OSGeo Foundation, OSGeo projects and FOSS4G conferences around branding. The Foundation and projects maintain valuable promotional material for FOSS4G conferences, and in return the FOSS4G conferences provides a valuable marketing pipeline.

The extent and nature of OSGeo promotion is dependent upon the size and nature of the event, and availability of volunteers to support the promotional activities. Activities which should be considered are:

* Include a presentation on an OSGeo topic, often as a keynote. You can find good local presenters at [[OSGeo_Advocate]].
* Provide a free OSGeo booth or stand. Refer to your OSGeo Local Chapter and/or [[OSGeo_Advocate]] list to source volunteer(s) to man the stand. Local Chapters can approach the OSGeo Marketing committee for an [[Exhibition_Pack]].
* Include an OSGeo logo included in the program and on the conference website.
* Make use of OSGeo-Live, either handing out a USB or DVD to delegates, using OSGeo-Live Virtual Machine in workshops, making use of the OSGeo-Live presentation, displaying the OSGeo-Live Poster. Options listed here: http://wiki.osgeo.org/wiki/Live_GIS_Disc#Including_OSGeo-Live_at_your_event

; See Also:
:* [[OSGeo_Advocate]]
:* http://wiki.osgeo.org/wiki/Live_GIS_Disc#Including_OSGeo-Live_at_your_event
:* [[Exhibition_Pack]]

=Time Frame=

=Program=

Previous global FOSS4G conferences have had a program similar to the following (regional and local events typically have a similar structure, reduced to match the size of the audience):
* One to two days of workshops. Workshops are generally 3.5 hour instructional sessions, in a computer lab setting. Workshop instructors provide software, data, and materials in exchange for free conference admission. Attended by 200 to 300 people, depending on facilities.
* An “ice breaker” event on the evening before the first day. Usually held in a large bar or restaurant, but could be in any venue that allowed for easy mixing and mingling.
* Three days of Main Conference
** Opening and closing plenary sessions with all attendees at the start and end. Sometimes additional plenary sessions at the start and/or end of conference days.
** Approximately five parallel tracks of presentations, with each presentation consisting of a 20-25 minute talk, 5 minutes of Q&A, and 5 minutes of transition time between talks. Attended by 500-900 people, depending on conference attendance.
** Make the schedule simple. It is far easier to have the lunch break from 12:30 to 14:00 than from 12:20 to 13.50. Try to schedule in no less than half hour slots.
** A “banquet” event on the evening of the second day. Usually held in a “showcase” venue, examples have included: art museum, castle, harbor cruise, cultural restaurant. This '''does not have to be''' a "Gala Dinner" but can be quite informal.
** [Global FOSS4G only] The Sol Katz Award, presented during the closing plenary session. The award is selected and presented by the Sol Katz committee, the conference organizers need only include 15 minutes in the closing plenary schedule for the presentation.
** The OSGeo Annual General Meeting. Interested OSGeo members hear from local chapters, the board, and other speakers on the state of OSGeo. It is up to the Local Committee how to place and organize this (maybe exchange ideas with the [[Board of Directors]]). This could be made into one of the most central events of the conference. So far it was usually places at either end of the conference and up to 200 people showed up.
** Birds of a Feather Sessions. Held after the days presentations, groups self-organize to discuss topics of common interest.
** A lunch time allocated for poster creators to stand next to their posters and talk about them.
* OSGeo Directors Face-to-Face Meeting. Held before or after the conference, in a board room or meeting room provided by the conference organizers.

; Relevance:
: International FOSS4G: Recommended
: Regional FOSS4G: Recommended
: FOSS4G stream / Local Event: Optional

; See Also:
:* RFP: http://svn.osgeo.org/osgeo/foss4g/rfp/
:* http://2013.foss4g.org/programme/
:* http://2011.foss4g.org/program

== Workshops ==

Draft, awaiting review

Workshops are an valuable component of every FOSS4G conference. They require a lot of preparation for both presenters and conference organizers! As such, be sure to have a dedicated team manage everything around workshops.

Workshops are generally 3.5 hour instructional sessions, in a computer lab setting. Workshop instructors provide software, data, and materials in exchange for free conference admission. Attended by 200 to 300 people, depending on facilities.

; Relevance:
: International FOSS4G: Mandatory
: Regional FOSS4G: Recommended
: FOSS4G stream / Local Event: Optional

; Workshop Call for Proposal
The Call for Proposal can be aligned with the regular presentation Call for Papers (see below).

; Workshop Selection
The workshops selection starts with a Call for Proposal. Anybody can submit a workshop proposal. The selection follows a few clear rules:
* Graduated OSGeo projects get precedence over incubating projects over others.
* Each graduated OSGeo project will receive one slot provided there are enough in total. If not first come first serve.
** Graduated OSGeo projects have to submit a workshop proposal just like anybody else.
** The Local Organizing Committee can decide to not accept a workshop but has to provide valid reasons to the submitting party. This should not be done on public mailing lists. In case of bitter resentment include the board of directors.
** If a graduated project does not convincingly confirm their participation slots are filled up by other active projects.
** Workshop leader/s have to register until x weeks before the conference.
* Individuals and organizations are encouraged to collaborate on joint workshops.
* Ideally a few slots should be reserved for workshops that may be not tech related for example for the Education and Data committees.

Final adjudication lies with the LOC!!!

=== Workshop Venue ===
The workshop venue requires careful planning! The computer lab systems need to be able to boot from USB. Internet connectivity is a must, both broad and fast. Ports need to be open, besides regular HTTP and HTTPS especially SSH but also "strange" manually configured ports. In general this should not pose a threat to the surrounding network or hardware because we boot from a self contained environment. All the same this must be communicated to the system admins of the host systems so that they are comfortable.

=== Software Environment ===
It is recommended to prepare USB memory sticks with the most recent OSGeo Live Environment. Ideally everything should already equipped with workshop specific software and data. This requires some pushing and nudging of the workshop teacher who may in some cases be very hard to get.

== Presentations ==
Presentations are the heart and soul of the conference and form a large part of the attractiveness. A lot of time and energy will go into making a good program. There are at least as many opinions on how a program should look like as there are people in the community. There is no silver bullet that will solve every problem and insure that everybody will be happy. Therefore it is good practice to make the Program Committee have the last say.

=== Call for Papers ===
The Call for Papers typically starts x months before the conference and runs for x weeks. The exact dates depend on local conditions, time of the years, size of the program committee and so on. It should be as late as possible to allow up-to-date information. The program should be published as soon as possible to attract local attendees who will only come if the program is attractive.

The LOC has to expect that more than half of the submissions are submitted within last two days of the CfP and that up to 30% are submitted with '''the last hours''' of the call. Relax, there have always been enough submission. Still, many conferences extend the CfP. If the LOC does '''not''' plan to extend the CfP it should be very vocal about this.

=== Submission of papers ===
Abstracts for talks are usually submitted via an online system. This can be based on the system developed over the past years by OSGeo community members or something new, this is entirely up to the LOC. Successful submission of an abstract should be acknowledged, preferably automatically.

=== Strategic Talks ===
The Program Committee should make sure that the program is balanced and that specific topics are not left out. One topic that is easily forgotten is a general introduction to Open Source development, licensing and associated business models. Both the actively voting community and the program committee members are usually deeply involved with Open Source and want to learn about the "bleeding edge" and are bored by annually recurring talks about things well known. But the FOSS4G conference also attracts a large group of "Open Source Newbies" who have no or very little understanding of the Open Source geospatial environment and ecosystem.

Other topics of strategic interest may be geared towards the specific region, remember that typically more than 50% of the attendees come from region where the conference takes place.

=== Selection and Evaluation of the Presentations ===
'''WARNING: ''' ''The selection process has lead to some unhappiness in the community in past iterations of the conference. The most important take away from related discussions appears to be that the process has to be communicated openly. Having said that it has always been OSGeo policy to give the Local Organizing Committee the final say and fully support its decisions. ''

==== Step 1: Community Voting ====
The selection process has '''so far''' been to allow the community (that is anybody) a chance to read the abstracts and make a positive vote:
* 0 = no interest
* 1 = medium interest
* 2 = high interest

==== Step 2: Program Committee Voting ====
After community voting the Program Committee goes through the list and checks for duplicates, both in content and also to make sure that presenter / submitting organization are not over represented, skewed. Presentation which miss the point of the conference (for example not related to Free and Open Source and Geo) are usually filtered out reliably. Then the Program Committee votes on

==== Step 3: Program Compilation ====
One topic that is easily forgotten is a general introduction to Open Source development, licensing and associated business models (see also "Strategic Talks"). Another topic that might be underrepresented if it is only compiled by involved experts are Use Cases with Open Source. In general the program should cater for the following areas of interest:
# Introduction to Open source and the OSGeo Foundation
# Business models and the "way of Open Source"
# Tech talks
# Use cases

===Classification of Papers in Sessions===
===Details about Speakers and Publication of the Program===

== Academic Track ==
[[FOSS4G Notes on Academic Track]]
==Community Sessions==
==Birds of a Feather Sessions (BoF)==
Draft, awaiting review

FOSS4G conferences provide a great opportunity for like minded people to network and brainstorm ideas, and "Birds of a Feather" meetings provide a good forum for this.

Conference organisers can delegate specific timeslots. Breakfasts and dinners are often good for these events.

Typically you create a wiki page for participants to define a "Birds of a Feather" session which are available for participants to choose. The wiki typically includes:
* Title
* Proposed topics
* Timeslot
* People (people self register by adding their names)
These sessions can also be written on butcher paper or white boards on walls around the conference somewhere.

Sessions can take any structure participants choose to select, but are typically informal and unstructured. A good number of participants for such an event is 4 to 8, which is small enough for all to participate in a conversation without splitting into multiple groups. Bigger does work, but typically requires more structured control of the conversation.

People wishing to set up a Birds of a Feather session should consider inviting specific people they wish to join the event and ensure you get a critical mass.

; Relevance:
: International FOSS4G: Recommended
: Regional FOSS4G: Recommeded
: FOSS4G stream / Local Event: Optional

==Posters==
==Conference Opening==
== Keynotes ==
Keynotes are selected by the LOC and Program Committee at their own discretion. Typically one keynote is given by a high ranking OSGeo officer, for example the president or a board representative and reflects on OSGeo, addresses the community and invites Newbies to join the party.

== Closing Session ==
It is a good habit to have a drawing with prizes (often donated by sponsors) at the end of the conference. It is also a good habit to have a prominent speaker or well known guest close the conference with a keynote. Both will help to have a captivate and keep attendees until the end of the event.

=== Drawing ===
Feedback from attendees is invaluable. Therefore the conference package should include a feedback form (potentially also as an online version?). Returned feedback forms participate in the drawing and can win a prize at the end of the conference.

=Social Events=
==Unofficial start==
==Social Event==
==Members' Meeting==
=Exhibition=
* Event should provide an OSGeo booth - read more at [[Operate OSGeo Booth]]
* Event should include [[OSGeo Advocate]] speaker who would present on an aspect of OSGeo
* The OSGeo advocate(s) are expected to coordinate and man the OSGeo booth
* The OSGeo [[Local Chapters]] are strongly encouraged to hang out at the OSGeo booth

=Sponsors=
=Media Sponsors=
=Participant Involvement=

== Privacy Statement ==
Please consider adding something along the lines of:

'' by submitting your email address you consent to us sharing your details ''
'' for the purpose of keeping you informed of future similar events. You can ''
'' unsubscribe from these communications at anytime using the unsubscribe links provided.''

==Visa and invitation letter==

Some countries require visa. To ease the immigration formalities to enter the respective host countries, an invitation letter ([http://www.cic.gc.ca/english/visit/business-letter.asp example]) smooth the visa request.

==Registration==
==Printed Program==
==Bags==
==T Shirt==
== OSGeo-Live ==
* [http://live.osgeo.org OSGeo Live]
* The OSGeo-Live team that provides an image of a collection of over 50 software projects and data and tutorials every 6 months
* The OSGeo-live team prepares a version before FOSS4G that can be used at the conference in the workshops, at presentation notebooks & and can be given away to the delegates as bootable USB drives. This is a great opportunity to spread OSGeo software and promote OSGeo!
* The OSGeo-Live team adds OSM data from the region where FOSS4G takes place (e.g. data from Bonn was added in 2016)
* The OSGeo-live team can add your FOSS4G-Logo or material on the image
* The OSGeo-Live team will help you with USB and image - please contact them on the mailing list
* Get information about the OSGeo-Live team [https://wiki.osgeo.org/wiki/Live_GIS_Disc here]
* Workshops with OSGeo-Live: trainer can refer to Workshop material [[https://trac.osgeo.org/osgeo/wiki/Live_GIS_Workshop_Install here]] (there is a link on the desktop of OSGeo-Live which will open the url)

==Location, Directions==
==Hotels==
==Other local information==
== Internet Access ==
Most venues do not have enough bandwidth or access points, so consider paying for extra if you can and start early in working with the venue! It can take a lot of planning simply to upgrade the access at the site, even after convincing the venue of the requirements. Be aware that conference venues may be used to large events, but may not realize that "tech-events" have a much larger bandwidth requirement per delegate than other conferences. Delegates are likely to have more than one device, may require non-default ports to be opened (for committing code and so on) and may wish to download large files such as new software during the event.

=== Ports ===
All ports should be open. This includes the lower levels for SSH, FTP, etc. but also "odd" ports like 6667 and neighboring for IRC, etc.
* FTP (20 and 21)
* SSH (22)
* TELNET (23)
* SMTP (25)
* IMAP (143, 456, 465, 587, 993, ++)
* SSL (443) and HTTP (80)
* TCP ports 6660–6669, 7000

You may need to work quite hard to convince the conference venue of your requirements, but success or failure with connectivity can make or break an event. Past FOSS4G Local Teams suggested a penalty clause in the contract in the case of WiFi underperformance and an action plan to agree the provision. Apparently this was then never done but it may be an idea to make sure that things work.

==Cloakroom==
==Proceedings==

=On Site: Avoid waste and CO2 footprint=
Draft, awaiting review

As an open community, that targets on improving our society, we strongly recommend LOC's to plan, how to avoid waste and offer possibilities to the participants to reduce their CO2 footprint. This includes all levels of material. For instance you can:

* avoid single way dishes and silverware and other one-way stuff like drinking bottles
* think about having a non-printed program
* ask sponsors not to bring too much material and/or only material printed on recycled material in an ecological manner
* offer a link to a CO2-compensating company, e.g. atmosfair, oeko-fair
* verify to buy T-Shirts based on fair-trade with ecological backgrounds
* reduce cooling down by air-conditioners
* .. (more proposals here)

If possible, inform your attendees about your means to avoid CO2 emission and reduction of waste and ask them to co-ordinate.

=Premises=

=survey participants=
=See Also=
*[[https://wiki.osgeo.org/wiki/Past_FOSS4G_Reports Past FOSS4G Conference Reports]] provides the attendance, sponsorship and financial reports for each FOSS4G. This is a valuable resource for anyone considering submitting a proposal for a FOSS4G events
*[[FOSS4G 2016 Lessons Learned|2016]]
*[[FOSS4G 2015 Lessons Learned|2015]]
*[[FOSS4G 2014 Lessons Learned|2014]]
*[[FOSS4G2013_Reflections_by_the_LOC|2013]]
*[[FOSS4G 2012 Lessons Learned|2012]]
*[[FOSS4G 2011 Lessons Learned|2011]]
*[[FOSS4G 2010 Lessons Learned|2010]]
*[[FOSS4G 2009 Lessons Learned|2009]]
*[[FOSS4G2008 Lessons Learned|2008]]
*[[FOSS4G2007 Lessons Learned|2007]]
* [http://www.fossgis.de/wiki/Handbuch German FOSSGIS Handbook in German], and an [http://arnulf.us/publications/fossgis_handbook.html English translation]
* FOSS4G Request for Proposal (RFP) documents: http://svn.osgeo.org/osgeo/foss4g/

Howtos from related conferences:
* [http://wiki.linux.org.au/LCA_HOWTO Linux Australia Conference Howto]
* [http://www.ecoop.org/resources/HowTo.pdf ECOOP Conference Howto]

[[Category:FOSS4G]]
[[Category:Events]]

FOSS4G Handbook

2018-09-14T23:46:04Z

Elil: /* Vimeo */ Add 2014 index link

This FOSS4G Handbook aims to provide guidance to future FOSS4G and FOSS4G related events, based upon the collective wisdom gained during prior events. It is a continuous work in progress and is a '''guide''' rather than a '''rulebook'''. Feel free to modify any aspect. If in doubt, ask the community what they think. This event is designed for the OSGeo community. We encourage all FOSS4G organizers to contribute to and enhance this Handbook.

= About FOSS4G =
Free and Open Source for Geospatial (FOSS4G) conferences refer to a series of events which provides presentations, workshops, and networking opportunities based around Free and Open Source Software for Geospatial.

FOSS4G includes one annual global event which rotates around the world, as well as a number of regional events which follow similar principles.

;See Also
: [https://wiki.osgeo.org/wiki/FOSS4G FOSS4G History]
: [https://docs.google.com/spreadsheets/d/1BpkO5WOFQ_DZEWNMLj_hAhEre0m0io_j-JGf7geAW5Y/edit?hl=en_GB#gid=57 FOSS4G Metrics]

= Editing this document =

This FOSS4G Handbook aims to be concise, so that it is easy to read and follow. We also aim to collaboratively edit and continuously build this document based upon our collective experience running conferences. As such, we will need to continuously update and delete old text as new ideas come to hand.

The process to follow in updating this wiki is:
* Feel free to make trivial tweaks to grammar and syntax.
* If you would like to introduce a new idea, maybe add a new section, or improve an old section:
** Raise your suggestion on the [http://lists.osgeo.org/mailman/listinfo/conference_dev OSGeo Conference] email list.
** Once a rough consensus has been reached on the list, you may then update the Handbook with the collective wisdom of the list.
** If writing a new section, consider starting the section with: Draft, awaiting review
** After updating your text, notify the list again to give others the opportunity to review and tweak.

= Section Writing Guide =
Draft, awaiting review

The first sentence(s) of a section should describe the meaning of the heading. Eg, if this section is on "Birds of a Feather", then the first sentence should start with: ''Birds of a Feather sessions refer to semi-formal gatherings of like minded delegates to discuss a topic of interest.''

; Relevance:
: International FOSS4G: [Mandatory, Recommended, Optional, Not Relevant]
: Regional FOSS4G: [Mandatory, Recommended, Optional, Not Relevant]
: FOSS4G stream / Local Event: [Mandatory, Recommended, Optional, Not Relevant]

Following paragraphs provide specific details. They might hyperlink to more details from an external Lessons Learned type doc. It will likely cover some of the following topics:
* Key success factors
* Things that can go wrong, with optional brief examples
* List of considerations and why choose one consideration over another
* List of steps to follow
* Organizations or people to contact to coordinate with
* Links to external documents, such as a Google Docs spreadsheet

; See Also:
:* Where relevant, finish with a list of links to web pages for further reading. E.g.
:* [http://wiki.osgeo.org/wiki/FOSS4G_2009_Lessons_Learned#Birds_of_a_Feather FOSS4G 2009 Birds of Feather Lessons Learned]

=Preparing FOSS4G RFP=
Draft, awaiting review

Selection of the international FOSS4G venue, involves two stages, a "Letter of Intent" (LOI) followed by a full "Request for Proposal" (RFQ). Only cities which attract two or more committee member votes from the LOI move onto the RFQ.

; Relevance:
: International FOSS4G: Mandatory
: Regional FOSS4G: Optional
: FOSS4G stream / Local Event: Usually Not Relevant

The process for preparing an RFP for the annual FOSS4G is:
* Copy the previous year's FOSS4G RFP directory to the next year, as per: http://svn.osgeo.org/osgeo/foss4g/rfp/
* Choose a set of dates for submission deadlines and review periods and very very carefully go through the document making sure they are all reflected in the right places.
* Get in touch with the conference_dev and teams from previous year or two and get their feedback on the process for RFP changes
* Do a quick search of the conference_dev archives and see if there's other RFP process / info concerns to be addressed (like Board Face ot Face Meeting, OSGeo Annual Gathering, other requirements that are assumed but not articulated)
* Update doc appropriately
* Stub out Wiki pages using the skeletons from previous years and the dates you already put into the doc
* Get someone to review your changes
* Announce

; See Also:
:* http://svn.osgeo.org/osgeo/foss4g/rfp/

= Lessons Learned =
Draft, awaiting review

It is highly valuable to future conferences to collect the wisdom gained from prior conferences.

; Relevance:
: International FOSS4G: StronglyRecommended
: Regional FOSS4G: Recommended
: FOSS4G stream / Local Event: Optional

In FOSS4G 2009 (Sydney, Australia), we wrote down our Lessons Learned throughout the planning period, while ideas were still fresh. The FOSS4G 2013 (Nottingham, UK) LOC came together after the conference to brainstorm their lessons learned.

*[[https://wiki.osgeo.org/wiki/Past_FOSS4G_Reports|Past FOSS4G Conference Reports]] provides the attendance, sponsorship and financial reports for each FOSS4G. This is a valuable resource for anyone considering submitting a proposal for a FOSS4G events

; See Also:
*[[FOSS4G 2016 Lessons Learned|2016]]
*[[FOSS4G 2015 Lessons Learned|2015]]
*[[FOSS4G 2014 Lessons Learned|2014]]
*[[FOSS4G2013_Reflections_by_the_LOC|2013]]
*[[FOSS4G 2012 Lessons Learned|2012]]
*[[FOSS4G 2011 Lessons Learned|2011]]
*[[FOSS4G 2010 Lessons Learned|2010]]
*[[FOSS4G 2009 Lessons Learned|2009]]
*[[FOSS4G2008 Lessons Learned|2008]]
*[[FOSS4G2007 Lessons Learned|2007]]

= Marketing =

== Press Releases ==
Draft, awaiting review

You should send out public announcements about your conference, especially around conference milestones.

; Relevance:
: International FOSS4G: Required
: Regional FOSS4G: Recommended
: FOSS4G stream / Local Event: Recommended

Make regular use the OSGeo News feed:
* initial announcement
* Call for Papers
* Start of registration, end of early booking approaching
* Program published
* etc.

Publish an official press release for the initial announcement of the conference and when the program is stable and published. Coordinate this with high level sponsors i.e. let them know when it will happen so that they can react accordingly! Get a quote form the highest available sponsor.

You will likely want to collaboratively edit press releases in a wiki page. The wiki then becomes an archive which can be handed down to future events.

Work out where you will send your announcements. It should include:
* You should submit to [http://www.osgeo.org/content/news/submit_news.html OSGeo Announcements] for inclusion on the OSGeo web site
* [http://lists.osgeo.org/mailman/listinfo/discuss OSGeo Discuss]
* Twitter
* A blog feed into [http://planet.osgeo.org/ Planet OSGeo]

; See Also:
:* http://wiki.osgeo.org/wiki/FOSS4G_2009_Press_Releases
:* http://wiki.osgeo.org/wiki/FOSS4G_2009_Lessons_Learned#Press_Releases

== twitter ==
* FOSS4G runs the [[https://twitter.com/foss4g FOSS4G twitter account]]
* The account will be passed to the new LOC each year after the conference
* Use #FOSS4G or #FOSS4G201x in your tweets (maybe also #FOSS4G?????????????)
* [[https://tweetdeck.twitter.com/ Tweetdeck]] can be used to get a better overview about tweets, notifications, retweets...
* [[http://buffer.com Buffer]] can be used to define tweets in advance and let them be posted at a defined time
* NodeXL shows you the tweet statistics in a graph

== Photos ==
FOSS4G runs a flickr group called FOSS4G. You can provide images from FOSS4G conferences to this group. You can get a member of this group and share your photos.
If you run the next FOSS4G conference you can ask to become an admin to change the configuration (ask [https://wiki.osgeo.org/wiki/User:Stevenfeldman Steven Feldman] or [https://wiki.osgeo.org/wiki/User:Astrid_Emde Astrid Emde])

* [https://www.flickr.com/groups/foss4g/ FOSS4G Group] on Flickr

==Event Listings==
Draft, awaiting review

The event should be added to event listings.

; Relevance:
: International FOSS4G: [Mandatory]
: Regional FOSS4G: [Recommended]
: FOSS4G stream / Local Event: [Recommended]

Relevant Lists include:
* http://www.osgeo.org/events
* http://wiki.osgeo.org/wiki/Global_conferences_overview
* https://wiki.osgeo.org/wiki/Live_GIS_History

; See Also:
:*

==FOSS4G Branding==
Draft, awaiting review

FOSS4G is the acronym used to describe events which are predominantly about "Free and Open Source Software for Geospatial".

; Relevance:
: International FOSS4G: [Mandatory]
: Regional FOSS4G: [Mandatory]
: FOSS4G stream / Local Event: [Mandatory]

FOSS4G is not registered as a trademark but has a long tradition of being used in the context of Free and Open Source Software for Geospatial. The domain was [[FOSS4G#History_of_the_Acronym|originally]] registered by Venkatesh Raghavan (Venka) who later graciously donated it to OSGeo - under the condition that using the name should stay open to anybody who does something reasonably related to Free and Open Source Geospatial.

A FOSS4G event can be the main international FOSS4G conference, as well as a regional event such as FOSS4G-North America. It can also be a local FOSS4G seminar drawing from one city, a FOSS4G stream in a bigger conference, a workshop or a code sprint. The number of participants can vary from ten people (code sprint) up to 1000+ people (global FOSS4G).

Use of the name "FOSS4G" is managed by the [http://wiki.osgeo.org/wiki/Conference_Committee OSGeo Conference Committee]. As a courtesy, events which wish to make use of the "FOSS4G" name should request permission to do so from the conference committee. Permission will be granted if the event being described is predominantly (say >90%) about Free and Open Source Software for Geospatial and promotes OSGeo.

; See Also:
:* http://wiki.osgeo.org/wiki/FOSS4G
:* http://wiki.osgeo.org/wiki/FOSS4G#Using_the_Name_FOSS4G
:* [[FOSS4G_Handbook#Regional_and_Local_FOSS4G_selection]]
:* http://wiki.osgeo.org/wiki/Official_OSGeo_Event_Policy

==OSGeo Branding==
Draft, awaiting review

FOSS4G events should suitably acknowledge the OSGeo foundation in promotion material.
This would typically include:
* the OSGeo logo being included on the website with words similar to "presented by OSGeo" and a link back to the OSGeo web site.
* presentation(s) by organisers (and others) should reference OSGeo

For larger events e.g. the annual international event and any event receiving OSGeo financial assistance, there should be an OSGeo booth of reasonable size and prominence provided at no charge to the foundation

; Relevance:
: International FOSS4G: [Mandatory]
: Regional FOSS4G: [Mandatory]
: FOSS4G stream / Local Event: [Recommended]

== Logo ==
[[File:OSGeo-Ribbon.jpg|thumb|right|alt=OSgeo Ribbon|OSgeo Ribbon.]]

The FOSS4G logo for the international conference has to include elements of the OSGeo / FOSS4G "ribbon" as can be seen in all previous conference logos: http://foss4g.org/, and should also include themes for the location of the current event.

; Relevance:
: International FOSS4G: [Mandatory]
: Regional FOSS4G: [Optional]
: FOSS4G stream / Local Event: [Not Applicable]

FOSS4G 2013 used a competition to design the logo. FOSS4G 2011 used [http://www.crowdspring.com crowdspring] and were very pleased with the way it worked.

Start on the logo asap as you need it for other early stage documents like the sponsorship prospectus.

=City and Date Selection=

== International FOSS4G Rotation ==
The International FOSS4G event rotates around the world, and cities compete to be selected to host the event, as described in the RFP process.

; Relevance:
: International FOSS4G: Mandatory
: Regional FOSS4G: Not Relevant
: FOSS4G stream / Local Event: Not Relevant

The regions FOSS4G rotates through are:
* Europe
* North America
* Rest of world
This is caveatted by the OSGeo Conference committee feeling confident that the proposed city/region will attract the majority of the international FOSS4G audience.

So our rotation policy is:

# Strong preference is given to the region which hasn't had FOSS4G for 2 years
# We next consider the region which had FOSS4G 2 years ago
# Only as a last resort would we consider a region which had FOSS4G last year

Prior International FOSS4G event locations have been:
* [http://2018.foss4g.org/ 2018]: Dar es Salaam, Tanzania
* [http://2017.foss4g.org/ 2017]: Boston, MA, USA
* [http://2016.foss4g.org/ 2016]: Bonn, Germany
* [http://2015.foss4g.org/ 2015]: Seoul, South Korea
* [http://2014.foss4g.org/ 2014]: Portland, Oregon, USA
* [http://2013.foss4g.org/ 2013]: Nottingham, United Kingdom
* <s>[http://2012.foss4g.org/ 2012]: Beijing, China (cancelled)</s>
* [http://2011.foss4g.org/ 2011]: Denver, United States
* [http://2010.foss4g.org/ 2010]: Barcelona, Spain
* [http://2009.foss4g.org/ 2009]: Sydney, Australia
* [http://2008.foss4g.org/ 2008]: Cape Town, South Africa
* [http://2007.foss4g.org/ 2007]: Victoria, Canada
* [http://2006.foss4g.org/ 2006]: Lausanne, Switzerland
* 2005: Minneapolis, United States
* [http://www.ces.iisc.ernet.in/energy/water/paper/fossgrdss/conference.htm 2004]: Bangkok, Thailand

; See Also:
:* http://www.osgeo.org/conference/rfp
:* http://svn.osgeo.org/osgeo/foss4g/
:* Many FOSS4G regional and related conferences are listed at: http://wiki.osgeo.org/wiki/Live_GIS_History
:* Conference committee approval of this rotation policy: http://lists.osgeo.org/pipermail/conference_dev/2013-May/002107.html

== Selecting locations which align with OSGeo principles ==

We should select locations where OSGeo principles and [https://www.osgeo.org/code_of_conduct/ Code of Conduct] align with the laws and practices of the location where the conference is being held.

; Relevance:
: International FOSS4G: Recommended
: Regional FOSS4G: Recommended
: FOSS4G stream / Local Event: Not Relevant

At FOSS4G 2018 in Tanzania we discovered that local laws decree that [https://en.wikipedia.org/wiki/LGBT_rights_in_Tanzania same-sex sexual acts are crimes punishable by the state]. This is contrary to the OSGeo Code of Conduct and is something we should try to avoid when selecting future conference venues.

; See Also:
:* [https://www.osgeo.org/code_of_conduct/ Code of Conduct]

==Regional and Local FOSS4G selection==
Draft, awaiting review

Location and date selection of FOSS4G regional and local events should be coordinated with other FOSS4G events.

Regional and Local FOSS4G events are encouraged
; Relevance:
: International FOSS4G: Not Relevant
: Regional FOSS4G: Recommended
: FOSS4G stream / Local Event: Recommended

There is a tension between supplying sufficient FOSS4G related conferences to meet demand, verses over-supply as multiple conferences potentially compete for the same speakers, sponsors and delegates. FOSS4G History, starting from around 2012 has demonstrated that there is sufficient demand to support both an international conference, as well as multiple regional conferences in the same year. This is in keeping with review of [https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdEZoOUtSeVZRVWtKQzV6R2N5ekdSdlE#gid=57 FOSS4G attendee profiles], which show over half of FOSS4G attendees tend to be drawn from the local region.
As such, OSGeo is supportive of multiple FOSS4G events being run in a year. However, OSGeo recommends scheduling FOSS4G events such that they don't overlap, and such that there is limited direct competition within regions between events.

Coordination between FOSS4G events is provided via the [http://lists.osgeo.org/mailman/listinfo/conference_dev OSGeo Conference email list]. All FOSS4G Conference Organising Committees should:
* Have at least one representative subscribe the the conference_dev email list.
* Announce intent of running a FOSS4G conference on the email list, including brief description of proposed event, proposed date(s), location, language, request to use FOSS4G name (if relevant).
* Network with others within the region. Discuss options of merging potential FOSS4G events and/or ensuring dates and locations don't conflict.
* Once location and date have been selected, list the event at http://www.osgeo.org/events.
* Also list at [http://wiki.osgeo.org/wiki/Live_GIS_History OSGeo-Live History] if making use of [http://live.osgeo.org OSGeo-Live] DVDs and/or presentation, to ensure DVDs are ready for your conference, and describe breadth of reach of OSGeo-Live to contributors and sponsors.

; See Also:
:* http://wiki.osgeo.org/wiki/FOSS4G_2012_Lessons_Learned#Competing_regional_conferences

=Schedule=
All successful events should be planned, and to help with the plan, we have a generic FOSS4G Planning Schedule which can be used as a starting point.

; Relevance
: International FOSS4G: Mandatory
: Regional FOSS4G: Mandatory
: FOSS4G stream / Local Event: Highly Recommended

When planning an event:
* Copy the [https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGdIbnY3SEZNUHp3NHdTZnlLZC1rbWc#gid=0 Generic FOSS4G Planning Schedule] into your own spreadsheet, probably onto a Google Drive so that it can be collaboratively viewed and edited.
* Tailor the plan such that it aligns with the goals for your event
* Feed improvements back into the [https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGdIbnY3SEZNUHp3NHdTZnlLZC1rbWc#gid=0 Generic FOSS4G Planning Schedule]. Non-trivial improvements should be discussed on the [http://lists.osgeo.org/mailman/listinfo/conference_dev OSGeo Conference email list] before applying.

; See Also:
:* [https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGdIbnY3SEZNUHp3NHdTZnlLZC1rbWc#gid=0 Generic FOSS4G Planning Schedule]

= Infrastructure and archiving =
Draft, awaiting review

Background:
* FOSS4G requires the establishment of various infrastructure relevant to a conference. This includes a conference website, registration website, community voting, credit card processing, LOC email list, archiving of these systems for future reference, etc.
* There may be some opportunity to reuse some of these systems.
* There should be some way to archive these for reference. In the case of the websites see the year subdomain, i.e. http://2009.foss4g.org/

; Relevance:
: International FOSS4G: Mandatory
: Regional FOSS4G: Optional?
: FOSS4G stream / Local Event: Optional?

== LOC email list ==
Draft, awaiting review

Much of the organizing and communication for the LOC happens via email. It is easy (and consistent with past practice) to use an OSGeo email list. Archiving happens automatically. There can be a list for both public and private communication, usually named foss4gyyyy and foss4gyyyy-private

; Relevance:
: International FOSS4G: Mandatory
: Regional FOSS4G: Recommended
: FOSS4G stream / Local Event: Optional/Not Relevant

; See Also:
:* Requesting an OSGeo email list: http://wiki.osgeo.org/wiki/SAC:Mailing_Lists#Requesting_a_new_list or i.e. http://trac.osgeo.org/osgeo/ticket/1202

== Website ==
Draft, awaiting review

Background:
* This is just a start at the archiving portion. More needs to be added about the requirements for selection, use, etc
* FOSS4G websites are archived in a basic form at yyyy.foss4g.org
* Some website platforms might have export options
* wget could be an archiving method too, perhaps something along the lines of:
wget --mirror --convert-links --backup-converted --html-extension
* HTTrack may be the preferred tool

; Relevance:
: International FOSS4G: Mandatory
: Regional FOSS4G: Optional?
: FOSS4G stream / Local Event: Optional?

= Diversity =
== Code of Conduct ==
Draft, awaiting review

Events should reference a Code of Conduct, probably the [http://www.osgeo.org/code_of_conduct OSGeo Code of Conduct], but you can choose one of the many other options.

; Relevance:
: International FOSS4G: Mandatory.
: Regional FOSS4G: Highly recommended.
: FOSS4G stream / Local Event: Recommended if not already covered by the main conference.
== Child Friendly Policy ==

Making a conference child friendly makes it easier for primary care givers (often mothers), the opportunity to present.

; Relevance:
: International FOSS4G: Optional
: Regional FOSS4G: Optional
: FOSS4G stream / Local Event: Optional

This requires managing an effective balance between the competing priorities of:

* High cost of dedicated childcare.
* Variability and unpredictability of different aged children.
* Retaining a professional conference environment.
* Respecting needs of children, parents, and conference participants.
* Making our conference accessible to a diverse audience, which includes those responsible for children.

FOSS4G Oceania introduced a Child Friendly Policy in 2018 which can be used as inspiration.

; See Also:
:* https://foss4g-oceania.org/child-friendly-conference
:* http://cameronshorter.blogspot.com/2018/09/child-friendly-conferences.html

= Streaming and archiving presentations and keynotes =
Draft, awaiting review
* Most FOSS4G's since 2011 (needs checking) have recorded presentations and made them available after the event.
*Since 2014 (needs checking) the proceedings have been live streamed as well as recorded which enables people who are unable to travel to a global FOSS4G to participate online and even ask questions of speakers.
* Recording and publishing helps to spread knowledge and awareness of OSGeo software

== Videos ==
Draft, awaiting review

Videoing presentations extends the reach of conference presentations to a much wider audience, but is logistically challenging, and/or expensive.

; Relevance:
: International FOSS4G: Strongly Recommended
: Regional FOSS4G: Recommended
: FOSS4G stream / Local Event: Optional

Videoing is not easy, nor inexpensive. It adds great value to OSGeo in being able to keep the presentations in perpetuity and to use them in a marketing and educational context. Equally, OSGeo has a broader mandate than an LOC to widen the reach of a FOSS4G conference to people who are unable to attend. However, the primary goal of an Organising Committee is to provide the best possible experience for those who attend the event. Hosting a FOSS4G is first and foremost for the visitors to your city and your paying customers and sponsors. Is it fair to have the Organising Committee (or rather, the paying attendees) pay for it?

There are also "scrappy" alternatives to get cheaper, poor quality content. Potentially ask attendees to record with mobile phones are upload to a central source.

As for September 2018, there have been a range of opinions on this topic, and the conference committee is yet to provide clear guidance on a path forward.

; See Also:
:* [https://lists.osgeo.org/pipermail/conference_dev/2018-September/004890.html Email list thread on videoing]

=== Vimeo ===
Foss4G runs a vimeo account. Where you can upload 20GB per week. Some conference where uploaded here. A full FOSS4G will produce more than 20GB of material..
* the account will be passed every year after the conference to the next team
* [[https://vimeo.com/foss4g FOSS4G Vimeo account]]
* Make sure, that you add enough metadata when you publish your video

There is a video landing page which refers to all videos from the last conferences. at [[http://video.foss4g.org]]

An example of a specific landing page for [[http://video.foss4g.org/foss4g2016/videos/index.html FOSS4G 2016]] is managed separately by the LOC or their video team. The code for the landing page is in [[https://git.osgeo.org/gitea/foss4g/video.foss4g.org OSGeo git]]. You can request access and build your own landing page. FOSS4G 2014 PDX video index is indeed part of the [[http://2014.foss4g.org/schedule/sessions/index.html website schedule]].

=== TIB ===
* [[TIB]] in Hannover is happy to publish our videos from FOSS4G. [[User:Peter Loewe|Peter Loewe]] and [[User:Bastian|Bastian Drees]] are contact persons, see also [[Peter Loewe Videoquotes|Video Quotes]] by Peter
* Read [[FOSS for GIS video tutorials and screencasts|how to publish videos at TIB]].

=Finances=
==Guarantees==
Draft, awaiting review

The OSGeo foundation can be approached to provide financial guarantees for major FOSS4G events.

; Relevance:
: International FOSS4G: Recommended
: Regional FOSS4G: Optional
: FOSS4G stream / Local Event: Not Relevant

As per our board priorities:

Conferences are financially risky events. They need to be planned well in advance, and you are never sure how many people will turn up, or whether some global event will have a substantial impact on registrations. Consequently, conferences such as FOSS4G require financial advances up front in order to secure a venue and possibly a guarantee to underwrite potential losses or liabilities additional to the advance.

To support and enable these conferences, OSGeo will endevour to retain sufficient capital to offer such guarantees for any FOSS4G event requesting it. August 2015: The Board has been requested to determine the the extent of reserves that it will set aside for this purpose, could be a % or a minimum absolute some or some other formula.

If OSGeo's support is requested, then OSGeo would require a legal body, such as the Local Organising Committee (LOC), or Professional Conference Organisor (PCO), or similar, to enter into an agreement with OSGeo that commits both parties. Cameron Shorter: Noted that legal body need not be the LOC. For FOSS4G 2009, OSGeo signed a contract directly with the PCO.

What follows is a draft set of conditions suggested by [[User:Stevenfeldman | Steven Feldman]] for further comment:

#Any FOSS4G seeking OSGeo’s financial backing should provide a financial plan, which includes:
## Initial advance(s) required and timing
## Potential loss through cancellation at different stages
## Potential loss if conference goes ahead but attendance is less than target
## Cameron Shorter added: Financial reporting schedule, noting how often reports will be provided, and by who (typically by a PCO).
## Cameron Shorter added: Mitigation actions which will be initiated should financial targets not be reached. Eg: If we have not received $XXX funds by YYY date, we will cancel the conference, which will result in loosing $ZZZ.
#OSGeo will confirm the maximum level that it will underwrite
#OSGeo will need to set aside a reserve to cover the maximum underwritten losses of all FOSS4G events that it is supporting. This will probably limit OSGeo's ability to underwrite multiple events and may require the Conference Committee to select between competing regional events if there are several applications
#The Conference Committee will require a member to join the LOC with financial oversight of expenditure, forecasts and risks. This relies on Conference Committee members volunteering for a very high level of effort joining a LOC and keeping close track of finances and the volume of email. [[User:EliL | - Eli Adam]] 
#The Conference Committee will need to continuously review financial risk and may require changes to the financial and operational plans of an event. Likewise requires the Conference Committee to be very engaged and deeply aware of the details of potentially two or more conferences. [[User:EliL | - Eli Adam]] 
#The LOC recognises and understands that OSGeo will not accept unlimited financial liability for their event, any losses exceeding the maximum level underwritten will need to be borne by the LOC or insured locally.
#The LOC agrees to remit xx% of any surplus to OSGeo to support future events and other OSGeo activities (I would suggest at least 85% but no doubt this could be a subject for discussion across the community but it should be standard for all events)
#OSGeo will need to draft a legal agreement with the LOC that sets out these terms

; See Also:
:* Board priorities: http://wiki.osgeo.org/wiki/Board_Meeting_2013-02-26#Conferences_and_related_events

==FOSS4G nonprofit tax status==
Draft, awaiting review

While The OSGeo foundation continues to pursue nonprofit status, partnering with other like-minded qualifying nonprofit organizations to make FOSS4G a tax exempt event may be desirable.

; Relevance:
: International FOSS4G:
: Regional FOSS4G:
: FOSS4G stream / Local Event:

; This is just a place holder to be filled out later once things are determined, see Also:
:* Conference list: http://lists.osgeo.org/pipermail/conference_dev/2013-July/002303.html

== Budget ==
; See Also
:* [https://docs.google.com/spreadsheets/d/1YdFNuBNaJK2XeA-bs1vU24VA1Qv9HpN8rLs30D9_0zg/edit#gid=1040179171 FOSS4G 2013 final accounts]

=Metrics=
Draft, awaiting review

Past FOSS4G metrics are very valuable for planning future FOSS4G events, and should be collected for all events.

; Relevance:
: International FOSS4G: Mandatory
: Regional FOSS4G: Recommended
: FOSS4G stream / Local Event: Optional

Key questions that we wish to ask of our metrics:
# How many people are likely to come from a future FOSS4G event in region X?
# In the lead up to FOSS4G how many more people are likely to sign up? Eg: 200 people registered by Early Bird, will we reach our predicted 300 attendees?
# In lead up, when do sponsors sign up?
# Schedule and workshop planners wish to understand the technical expertise of participants. What is the percentage of OSGeo newbies (requiring "Introduction to ..." presentation/workshop).
# Schedule and workshop planners wish to understand which presenters and topics were popular.
# When considering whether to sponsor, and how to target spsonsorship messages, FOSS4G sponsors wish to understand the makeup of FOSS4G attendees. In particular, are attendees likely to influence decisions to purchase future software systems.
# How much sponsorship should we expect? Where in the world did previous sponsors come from?
# What is the most effective way to market FOSS4G? How did people hear about FOSS4G?

Key metrics we wish to collect from attendees:
# Registration date
# City, State, Country
# Sponsor name, amount, sign up date
# Information Source: Past attendee,Friend/colleague,E-mail list,Web badge on open source site,Grapevine,Internet Search,Web advertisement,Magazine advertisement
# Job Description 1:C-Level Executive,Manager,Consultant,Programmer,Scientist,Educator,Mysterious
#Job Responsibility 1: If I Told You I'D Have To Kill You ($1,000,000s),Heaps Of Money ($100,000s),Piles Of Money ($10,000s),Stacks Of Money ($1000s),No Money At All
# Reason For Attending: The Technical Networking,The Workshops & Technical Sessions,The Beer,The Sales Networking,Something Else Altogether

Metrics to collect about presentations:
# How many people were in the room of each presentation?
# Optional: How interesting was the topic?
# Optional: How good was the speaker?

; See Also:
:* Collated metrics from past global FOSS4G events: https://docs.google.com/spreadsheets/d/1ux_hFq-C165140ZD48RRImPTHSpXj42OG3nBr9cyZYo/edit#gid=1782600951
* Older version of the same metrics: https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdEZoOUtSeVZRVWtKQzV6R2N5ekdSdlE#gid=57
:* Peter Batty's analysis to determine if FOSS4G-NA would impact FOSS4G Global, in Oct 2011: http://osgeo-org.1560.x6.nabble.com/Re-OSGeo-Conf-North-American-FOSS4G-conference-tp3714127p3714128.html
:* FOSS4G 2013 Metrics: http://2013.foss4g.org/Surveys/delegate.html

=Travel Grants=
The travel grant programme is run by FOSs4G's Conference committee. The first TGP was run in 2017, see [[FOSS4G_Travel_Grant_Programme_2017]]

This is the old draft, the procedure was based on: [[Draft FOSS4G Travel Grants]]

=OSGeo Branding=
Draft, awaiting review

FOSS4G conferences are expected to promote the OSGeo Foundation at events.

; Relevance:
: International FOSS4G: Mandatory
: Regional FOSS4G: Recommeded
: FOSS4G stream / Local Event: Recommended

There is a symbiotic relationship between the OSGeo Foundation, OSGeo projects and FOSS4G conferences around branding. The Foundation and projects maintain valuable promotional material for FOSS4G conferences, and in return the FOSS4G conferences provides a valuable marketing pipeline.

The extent and nature of OSGeo promotion is dependent upon the size and nature of the event, and availability of volunteers to support the promotional activities. Activities which should be considered are:

* Include a presentation on an OSGeo topic, often as a keynote. You can find good local presenters at [[OSGeo_Advocate]].
* Provide a free OSGeo booth or stand. Refer to your OSGeo Local Chapter and/or [[OSGeo_Advocate]] list to source volunteer(s) to man the stand. Local Chapters can approach the OSGeo Marketing committee for an [[Exhibition_Pack]].
* Include an OSGeo logo included in the program and on the conference website.
* Make use of OSGeo-Live, either handing out a USB or DVD to delegates, using OSGeo-Live Virtual Machine in workshops, making use of the OSGeo-Live presentation, displaying the OSGeo-Live Poster. Options listed here: http://wiki.osgeo.org/wiki/Live_GIS_Disc#Including_OSGeo-Live_at_your_event

; See Also:
:* [[OSGeo_Advocate]]
:* http://wiki.osgeo.org/wiki/Live_GIS_Disc#Including_OSGeo-Live_at_your_event
:* [[Exhibition_Pack]]

=Time Frame=

=Program=

Previous global FOSS4G conferences have had a program similar to the following (regional and local events typically have a similar structure, reduced to match the size of the audience):
* One to two days of workshops. Workshops are generally 3.5 hour instructional sessions, in a computer lab setting. Workshop instructors provide software, data, and materials in exchange for free conference admission. Attended by 200 to 300 people, depending on facilities.
* An “ice breaker” event on the evening before the first day. Usually held in a large bar or restaurant, but could be in any venue that allowed for easy mixing and mingling.
* Three days of Main Conference
** Opening and closing plenary sessions with all attendees at the start and end. Sometimes additional plenary sessions at the start and/or end of conference days.
** Approximately five parallel tracks of presentations, with each presentation consisting of a 20-25 minute talk, 5 minutes of Q&A, and 5 minutes of transition time between talks. Attended by 500-900 people, depending on conference attendance.
** Make the schedule simple. It is far easier to have the lunch break from 12:30 to 14:00 than from 12:20 to 13.50. Try to schedule in no less than half hour slots.
** A “banquet” event on the evening of the second day. Usually held in a “showcase” venue, examples have included: art museum, castle, harbor cruise, cultural restaurant. This '''does not have to be''' a "Gala Dinner" but can be quite informal.
** [Global FOSS4G only] The Sol Katz Award, presented during the closing plenary session. The award is selected and presented by the Sol Katz committee, the conference organizers need only include 15 minutes in the closing plenary schedule for the presentation.
** The OSGeo Annual General Meeting. Interested OSGeo members hear from local chapters, the board, and other speakers on the state of OSGeo. It is up to the Local Committee how to place and organize this (maybe exchange ideas with the [[Board of Directors]]). This could be made into one of the most central events of the conference. So far it was usually places at either end of the conference and up to 200 people showed up.
** Birds of a Feather Sessions. Held after the days presentations, groups self-organize to discuss topics of common interest.
** A lunch time allocated for poster creators to stand next to their posters and talk about them.
* OSGeo Directors Face-to-Face Meeting. Held before or after the conference, in a board room or meeting room provided by the conference organizers.

; Relevance:
: International FOSS4G: Recommended
: Regional FOSS4G: Recommended
: FOSS4G stream / Local Event: Optional

; See Also:
:* RFP: http://svn.osgeo.org/osgeo/foss4g/rfp/
:* http://2013.foss4g.org/programme/
:* http://2011.foss4g.org/program

== Workshops ==

Draft, awaiting review

Workshops are an valuable component of every FOSS4G conference. They require a lot of preparation for both presenters and conference organizers! As such, be sure to have a dedicated team manage everything around workshops.

Workshops are generally 3.5 hour instructional sessions, in a computer lab setting. Workshop instructors provide software, data, and materials in exchange for free conference admission. Attended by 200 to 300 people, depending on facilities.

; Relevance:
: International FOSS4G: Mandatory
: Regional FOSS4G: Recommended
: FOSS4G stream / Local Event: Optional

; Workshop Call for Proposal
The Call for Proposal can be aligned with the regular presentation Call for Papers (see below).

; Workshop Selection
The workshops selection starts with a Call for Proposal. Anybody can submit a workshop proposal. The selection follows a few clear rules:
* Graduated OSGeo projects get precedence over incubating projects over others.
* Each graduated OSGeo project will receive one slot provided there are enough in total. If not first come first serve.
** Graduated OSGeo projects have to submit a workshop proposal just like anybody else.
** The Local Organizing Committee can decide to not accept a workshop but has to provide valid reasons to the submitting party. This should not be done on public mailing lists. In case of bitter resentment include the board of directors.
** If a graduated project does not convincingly confirm their participation slots are filled up by other active projects.
** Workshop leader/s have to register until x weeks before the conference.
* Individuals and organizations are encouraged to collaborate on joint workshops.
* Ideally a few slots should be reserved for workshops that may be not tech related for example for the Education and Data committees.

Final adjudication lies with the LOC!!!

=== Workshop Venue ===
The workshop venue requires careful planning! The computer lab systems need to be able to boot from USB. Internet connectivity is a must, both broad and fast. Ports need to be open, besides regular HTTP and HTTPS especially SSH but also "strange" manually configured ports. In general this should not pose a threat to the surrounding network or hardware because we boot from a self contained environment. All the same this must be communicated to the system admins of the host systems so that they are comfortable.

=== Software Environment ===
It is recommended to prepare USB memory sticks with the most recent OSGeo Live Environment. Ideally everything should already equipped with workshop specific software and data. This requires some pushing and nudging of the workshop teacher who may in some cases be very hard to get.

== Presentations ==
Presentations are the heart and soul of the conference and form a large part of the attractiveness. A lot of time and energy will go into making a good program. There are at least as many opinions on how a program should look like as there are people in the community. There is no silver bullet that will solve every problem and insure that everybody will be happy. Therefore it is good practice to make the Program Committee have the last say.

=== Call for Papers ===
The Call for Papers typically starts x months before the conference and runs for x weeks. The exact dates depend on local conditions, time of the years, size of the program committee and so on. It should be as late as possible to allow up-to-date information. The program should be published as soon as possible to attract local attendees who will only come if the program is attractive.

The LOC has to expect that more than half of the submissions are submitted within last two days of the CfP and that up to 30% are submitted with '''the last hours''' of the call. Relax, there have always been enough submission. Still, many conferences extend the CfP. If the LOC does '''not''' plan to extend the CfP it should be very vocal about this.

=== Submission of papers ===
Abstracts for talks are usually submitted via an online system. This can be based on the system developed over the past years by OSGeo community members or something new, this is entirely up to the LOC. Successful submission of an abstract should be acknowledged, preferably automatically.

=== Strategic Talks ===
The Program Committee should make sure that the program is balanced and that specific topics are not left out. One topic that is easily forgotten is a general introduction to Open Source development, licensing and associated business models. Both the actively voting community and the program committee members are usually deeply involved with Open Source and want to learn about the "bleeding edge" and are bored by annually recurring talks about things well known. But the FOSS4G conference also attracts a large group of "Open Source Newbies" who have no or very little understanding of the Open Source geospatial environment and ecosystem.

Other topics of strategic interest may be geared towards the specific region, remember that typically more than 50% of the attendees come from region where the conference takes place.

=== Selection and Evaluation of the Presentations ===
'''WARNING: ''' ''The selection process has lead to some unhappiness in the community in past iterations of the conference. The most important take away from related discussions appears to be that the process has to be communicated openly. Having said that it has always been OSGeo policy to give the Local Organizing Committee the final say and fully support its decisions. ''

==== Step 1: Community Voting ====
The selection process has '''so far''' been to allow the community (that is anybody) a chance to read the abstracts and make a positive vote:
* 0 = no interest
* 1 = medium interest
* 2 = high interest

==== Step 2: Program Committee Voting ====
After community voting the Program Committee goes through the list and checks for duplicates, both in content and also to make sure that presenter / submitting organization are not over represented, skewed. Presentation which miss the point of the conference (for example not related to Free and Open Source and Geo) are usually filtered out reliably. Then the Program Committee votes on

==== Step 3: Program Compilation ====
One topic that is easily forgotten is a general introduction to Open Source development, licensing and associated business models (see also "Strategic Talks"). Another topic that might be underrepresented if it is only compiled by involved experts are Use Cases with Open Source. In general the program should cater for the following areas of interest:
# Introduction to Open source and the OSGeo Foundation
# Business models and the "way of Open Source"
# Tech talks
# Use cases

===Classification of Papers in Sessions===
===Details about Speakers and Publication of the Program===

== Academic Track ==
[[FOSS4G Notes on Academic Track]]
==Community Sessions==
==Birds of a Feather Sessions (BoF)==
Draft, awaiting review

FOSS4G conferences provide a great opportunity for like minded people to network and brainstorm ideas, and "Birds of a Feather" meetings provide a good forum for this.

Conference organisers can delegate specific timeslots. Breakfasts and dinners are often good for these events.

Typically you create a wiki page for participants to define a "Birds of a Feather" session which are available for participants to choose. The wiki typically includes:
* Title
* Proposed topics
* Timeslot
* People (people self register by adding their names)
These sessions can also be written on butcher paper or white boards on walls around the conference somewhere.

Sessions can take any structure participants choose to select, but are typically informal and unstructured. A good number of participants for such an event is 4 to 8, which is small enough for all to participate in a conversation without splitting into multiple groups. Bigger does work, but typically requires more structured control of the conversation.

People wishing to set up a Birds of a Feather session should consider inviting specific people they wish to join the event and ensure you get a critical mass.

; Relevance:
: International FOSS4G: Recommended
: Regional FOSS4G: Recommeded
: FOSS4G stream / Local Event: Optional

==Posters==
==Conference Opening==
== Keynotes ==
Keynotes are selected by the LOC and Program Committee at their own discretion. Typically one keynote is given by a high ranking OSGeo officer, for example the president or a board representative and reflects on OSGeo, addresses the community and invites Newbies to join the party.

== Closing Session ==
It is a good habit to have a drawing with prizes (often donated by sponsors) at the end of the conference. It is also a good habit to have a prominent speaker or well known guest close the conference with a keynote. Both will help to have a captivate and keep attendees until the end of the event.

=== Drawing ===
Feedback from attendees is invaluable. Therefore the conference package should include a feedback form (potentially also as an online version?). Returned feedback forms participate in the drawing and can win a prize at the end of the conference.

=Social Events=
==Unofficial start==
==Social Event==
==Members' Meeting==
=Exhibition=
* Event should provide an OSGeo booth - read more at [[Operate OSGeo Booth]]
* Event should include [[OSGeo Advocate]] speaker who would present on an aspect of OSGeo
* The OSGeo advocate(s) are expected to coordinate and man the OSGeo booth
* The OSGeo [[Local Chapters]] are strongly encouraged to hang out at the OSGeo booth

=Sponsors=
=Media Sponsors=
=Participant Involvement=

== Privacy Statement ==
Please consider adding something along the lines of:

'' by submitting your email address you consent to us sharing your details ''
'' for the purpose of keeping you informed of future similar events. You can ''
'' unsubscribe from these communications at anytime using the unsubscribe links provided.''

==Visa and invitation letter==

Some countries require visa. To ease the immigration formalities to enter the respective host countries, an invitation letter ([http://www.cic.gc.ca/english/visit/business-letter.asp example]) smooth the visa request.

==Registration==
==Printed Program==
==Bags==
==T Shirt==
== OSGeo-Live ==
* [http://live.osgeo.org OSGeo Live]
* The OSGeo-Live team that provides an image of a collection of over 50 software projects and data and tutorials every 6 months
* The OSGeo-live team prepares a version before FOSS4G that can be used at the conference in the workshops, at presentation notebooks & and can be given away to the delegates as bootable USB drives. This is a great opportunity to spread OSGeo software and promote OSGeo!
* The OSGeo-Live team adds OSM data from the region where FOSS4G takes place (e.g. data from Bonn was added in 2016)
* The OSGeo-live team can add your FOSS4G-Logo or material on the image
* The OSGeo-Live team will help you with USB and image - please contact them on the mailing list
* Get information about the OSGeo-Live team [https://wiki.osgeo.org/wiki/Live_GIS_Disc here]
* Workshops with OSGeo-Live: trainer can refer to Workshop material [[https://trac.osgeo.org/osgeo/wiki/Live_GIS_Workshop_Install here]] (there is a link on the desktop of OSGeo-Live which will open the url)

==Location, Directions==
==Hotels==
==Other local information==
== Internet Access ==
Most venues do not have enough bandwidth or access points, so consider paying for extra if you can and start early in working with the venue! It can take a lot of planning simply to upgrade the access at the site, even after convincing the venue of the requirements. Be aware that conference venues may be used to large events, but may not realize that "tech-events" have a much larger bandwidth requirement per delegate than other conferences. Delegates are likely to have more than one device, may require non-default ports to be opened (for committing code and so on) and may wish to download large files such as new software during the event.

=== Ports ===
All ports should be open. This includes the lower levels for SSH, FTP, etc. but also "odd" ports like 6667 and neighboring for IRC, etc.
* FTP (20 and 21)
* SSH (22)
* TELNET (23)
* SMTP (25)
* IMAP (143, 456, 465, 587, 993, ++)
* SSL (443) and HTTP (80)
* TCP ports 6660–6669, 7000

You may need to work quite hard to convince the conference venue of your requirements, but success or failure with connectivity can make or break an event. Past FOSS4G Local Teams suggested a penalty clause in the contract in the case of WiFi underperformance and an action plan to agree the provision. Apparently this was then never done but it may be an idea to make sure that things work.

==Cloakroom==
==Proceedings==

=On Site: Avoid waste and CO2 footprint=
Draft, awaiting review

As an open community, that targets on improving our society, we strongly recommend LOC's to plan, how to avoid waste and offer possibilities to the participants to reduce their CO2 footprint. This includes all levels of material. For instance you can:

* avoid single way dishes and silverware and other one-way stuff like drinking bottles
* think about having a non-printed program
* ask sponsors not to bring too much material and/or only material printed on recycled material in an ecological manner
* offer a link to a CO2-compensating company, e.g. atmosfair, oeko-fair
* verify to buy T-Shirts based on fair-trade with ecological backgrounds
* reduce cooling down by air-conditioners
* .. (more proposals here)

If possible, inform your attendees about your means to avoid CO2 emission and reduction of waste and ask them to co-ordinate.

=Premises=

=survey participants=
=See Also=
*[[https://wiki.osgeo.org/wiki/Past_FOSS4G_Reports Past FOSS4G Conference Reports]] provides the attendance, sponsorship and financial reports for each FOSS4G. This is a valuable resource for anyone considering submitting a proposal for a FOSS4G events
*[[FOSS4G 2016 Lessons Learned|2016]]
*[[FOSS4G 2015 Lessons Learned|2015]]
*[[FOSS4G 2014 Lessons Learned|2014]]
*[[FOSS4G2013_Reflections_by_the_LOC|2013]]
*[[FOSS4G 2012 Lessons Learned|2012]]
*[[FOSS4G 2011 Lessons Learned|2011]]
*[[FOSS4G 2010 Lessons Learned|2010]]
*[[FOSS4G 2009 Lessons Learned|2009]]
*[[FOSS4G2008 Lessons Learned|2008]]
*[[FOSS4G2007 Lessons Learned|2007]]
* [http://www.fossgis.de/wiki/Handbuch German FOSSGIS Handbook in German], and an [http://arnulf.us/publications/fossgis_handbook.html English translation]
* FOSS4G Request for Proposal (RFP) documents: http://svn.osgeo.org/osgeo/foss4g/

Howtos from related conferences:
* [http://wiki.linux.org.au/LCA_HOWTO Linux Australia Conference Howto]
* [http://www.ecoop.org/resources/HowTo.pdf ECOOP Conference Howto]

[[Category:FOSS4G]]
[[Category:Events]]

PDX-OSGEO

2018-01-27T00:50:52Z

Elil: Add pointer link to current page

'''Welcome to the Portland, OR Chapter of OSGEO - serving Oregon and SW Washington!'''

'''This wiki page is mostly historical at this point, head over to our current [https://www.osgeo.org/local-chapters/pdxosgeo/ website]

== News ==
* We now meet on the 3th Wednesday of every month from 6:00-7:30 PM at various locations.

=== Meetings ===

We don't seem to update the Meetings portion of the website. Checking [http://calagator.org/events/search?utf8=%E2%9C%93&query=osgeo Caligator] for "OSGeo" is probably the best route.

[[PDX_OSGEO_Meeting_Notes | Past Meeting Notes]]

[[PDX_OSGEO_Meeting_Planning | How to plan a meeting]]

{| class="wikitable"
|+ '''PDX-OSGEO Meetings, third Wednesdays, for 2015, 6:00-7:30 PM'''
|-
! Date
! Location
! Speakers, Topics
|-
| January 21
| Cramer
| QGIS and InkScape - Producing great cartography with open source tools by Dave Mangold.
|-
| Feb 18
| Cramer
| CartoCSS and UTFGrids for collaborative mapping by Nick Martinelli.
|-
| March 17
| Cramer
| Vector Tiles, Justin Miller [[http://justinmiller.io/posts/2015/01/20/anatomy-of-a-travel-map/ | http://justinmiller.io/posts/2015/01/20/anatomy-of-a-travel-map/ ]]
|-
| April 15
| Cramer
| Katie Urey, Ryan Peterson [[http://spiderosm.org| http://spiderosm.org ]]update
|-
| May 20
| location
| tbd
|-
| June 17
| location
| tbd
|-
| July 15
| location
| tbd
|-
| August 19
| location
| tbd
|-
| September 16
| location
| tbd
|-
| October 21
| location
| tbd
|-
| November 18
| location
| tbd
|-
| December 16
| location
| tbd
|-
|}

== Events ==

[[FOSS4G_2014 | links for various FOSS4G 2014 pages]]

=== Upcoming Events ===
[[Category:Events]]

2015 Summer Outdoor Mapathons, tentative schedule.

*Monday July 6 - 6PM The Portland Building under Portlandia statue. Gab for 10 minutes, divvy up quadrants- head out.

*Monday July 13 - Along Orange TriMet MAX line, N Killingsworth St MAX Station Stop ID 11512, Morning or noonish to work with Babies and strollers.

*Monday July 20 - Evening, Eastside... MAX Orange Line?

*Monday July 27 - noonish, – 82nd Ave and Division? Other ideas?

=== Past Events ===

2014
* Sep. 8-13 (Mon-Sat) [http://2014.foss4g.org/ FOSS4G 2014] (Portland, Oregon, USA, Earth, Sol, Milky)

2013
* Mar. 21 (Thu) GPS, Geodesy and the Ghost in the Machine: A Workshop for Surveyors and GIS Professionals [http://www.ogug.net/PDF%20files/Dennis%20GPS.pdf (PDF)] (Salem, Oregon)

* Apr. 30 - May 1 (Tue-Wed) [http://www.orurisa.org/GIS_In_Action GIS In Action 2013] (PDX)

* May 2 (Thurs) [[PDX-OSGeo_2013_Unconference|2013 Unconference]] (PDX)

* Aug. 27-29 (Tue-Thu) [http://geog.uvic.ca/CSRS2013/CSRS_2013/Home.html 34th Canadian Symposium on Remote Sensing] (Victoria, B. C., Canada)

* Sep. 4 (Wed) [http://www.orurisa.org/Events?eventId=702687&EventViewMode=EventDetails Central Oregon GIS - Cartography Outside of ESRI] (Bend, Oregon)

* Sep. 21 (Sat) [http://www.orurisa.org/Default.aspx?pageId=507168 Willamette Valley GIS Users Group Summer 2013 Quarterly Meeting] (Salem, Oregon)

* Sep. 23-25 (Mon-Wed) [http://gisgig.com/gisevents/2013-geoalberta-conference/ 2013 GeoAlberta Conference] (Edmonton, Alberta, Canada)

* Sep. 27-29 (Fri-Sun) {http://wherecamppdx.org/ WhereCampPDX 6] (Portland, Oregon)

* Oct. 14-18 (Mon-Fri) [http://sunriver2013.nwgis.org/ NWGIS Sunriver 2013] (Central Oregon)

* Oct 19 [http://calagator.org/events/1250464914 OpenStreetMap Fall Editathon] (Portland)

* Oct. 16 (Wed) [http://cugos.org/events/2013/10/16/fall-fling/ CUGOS 2013 Fall Fling] (Seattle, Washington)

* Oct. 23 (Wed) Randal Schwartz interviews Tim Sutton and Gary Sherman of [http://qgis.org QGIS] on [http://twit.tv/show/floss-weekly FLOSS Weekly TV] (internet)

* Oct. 25 (Fri) American Society for Photogrammetry and Remote Sensing (ASPRS) Columbia River & Puget Sound Regions [http://columbia.asprs.org/CRR/index.html 17th Annual Technical Exchange] (Vancouver, Washington)

* Nov. 8 (Fri) [http://www.christinafriedle.com/1/post/2013/09/save-the-date-2013-portland-cartography-symposium.html 2013 Portland Cartography Symposium] (Portland, Oregon)

2012

* Presentation for PLSO/ORURISA GIS in Action Conference 2012 - [https://docs.google.com/presentation/d/1JlmI9S6ZHYtW2pEwe4VtVYw1rehxbqdgkutoWbKjAw4/edit Open Source Smackdown - Web Mapping Clients Edition]

2011

* Details on '''[[PDX-OSGEO#Unconference_March_31st_and_April_1st.2C_2011 | 2011 Open Source GIS unconference]]'''

[[PDX_OSGEO_Past_events | More past events ]]

== About the PDX-OSGeo Local Chapter ==
=== Introduction ===
PDX-OSGeo is a Local Chapter of OSGeo. PDX-OSGeo has a catchment area equal to the PDX airport, Oregon and SW Washington (Vancouver, WA / Clark County, WA). Monthly meetings are held in Portland.

=== History ===
PDX-OSGeo has been around and meeting in one form or another since before February 2009 under various names. Since September 2010, we have been recognized as an Oregon-URISA [http://orurisa.org/PDXOSGIS Special Interest Group (SIG)]. Since 2010, the local chapter has coordinated an open source unconference with ORURISA and [http://orurisa.org/GIS_In_Action GIS In Action]. There are also deep roots with our sister OSGeo Local Chapter, [http://cugos.org CUGOS]. In August, 2012, we became an official OSGeo local chapter by action of the OSGeo [[Board_Meeting_2012-08-09 | August, 2012 board meeting]].

=== Mission ===
The PDX-OSGeo Chapter strives to promote the local use of Open Source Geospatial software, particularly new users in the Oregon/SW Washington area. The group hosts monthly meetings providing presentation, discussion, and educational opportunities and focuses on materializing an annual Open Source GIS unconference.

=== Objectives ===
Monthly Meetings, usually totaling 10/year:
* Presentations (Application and Technical)
* Chapter business
* Social gathering

Regional Events:
* Open Source GIS unconference
* Conference participation

Communication:
* Mailing List
* Wiki Development
* Monthly meetings

Legal Status:
* No real independent legal structure.
* No real capacity to independently hold funds in other than ad hoc informal manner.
* Affiliations with OSGeo and ORURISA help us with some of the tasks that require legal recognition as an independent entity.
* There are currently no plans to seek any independent legal structure in the future.

=== Annual Reports ===
* [[PDX_OSGeo_Chapter_Annual_Report_2013 | 2013]]
* [[PDX_OSGeo_Chapter_Annual_Report_2012 | 2012]]
* [[PDX_OSGEO_Chapter_Annual_Report_2011 | 2011]]
* [[PDX_OSGEO_Chapter_Annual_Report_2010 | 2010]]

== Getting Involved ==
The PDX-OSGeo Local Chapter is a flexible organization, join us and help steer.

=== Membership ===
Anyone who wants to help support our mission is free to become a member.
'''List yourself on the [[PDX_Member | PDX-OSGEO Member Page]] and you're in!'''

=== Mailing List ===
Please join our mailing list to make sure that you know what's going on. Sign up and participate (or just lurk for a while). We have two main lists:

* For general discussion and announcements: http://groups.google.com/group/pdx-osgeo You do need to answer the questions (what is your favorite map and something else I think) to the extent needed to demonstrate that you are a person and have the minimal amount of GEO knowledge to not be a random spammer.
* For planning upcoming meetings (open to all participants): http://lists.pdxosgeo.org/sympa/info/planners

=== IRC ===
We can be found on irc://irc.freenode.net/#osgeo-pdx when there is something to discuss.

=== Leadership ===
To the extent that we think that we need leadership, it is [[User:Percyd | Percy]]. Mostly we expect everyone to step up and help on most tasks resulting in a light load for all.

=== This Wiki ===
==== How To Write WIKI ====
Check out WikiPedia, where else. This is a great resource for many wiki writing tips
* [http://en.wikipedia.org/wiki/Help:Editing#Organizing_your_writing How to Write Wiki]

=== Event Set Up ===
[[Event set up]] notes.

== Geo Resources ==
=== SPRING GIS ===
[http://www.dpi.inpe.br/spring/english/index.html SPRING] is a state-of-the-art GIS and remote sensing image processing system with an object-oriented data model which provides for the integration of raster and vector data representations in a single environment. SPRING is a product of Brazil's National Institute for Space Research (INPE/DPI (Image Processing Division)[http://www.dpi.inpe.br/spring/english/index.html ...]

[[SPRING GIS documentation]]

=== USDA - NRCS SSURGO Soil Database Migration to PostgreSQL ===
An example of how to get SURGO soils data into a PostgreSQL database on a GNU/Linux-based OS.

[[File:SSURGO_to_PostgreSQL.odt]]|USDA - NRCS SSURGO Soil Database Migration to PostgreSQL

===The top seven alternatives to the Google Maps API===
Wm Leler of the PDX-OSGeo presented this topic and Net Magazine requested that he write it up at http://www.netmagazine.com/features/top-seven-alternatives-google-maps-api Article date: 2012-06-18.

=== Other useful links===
* [http://gis.stackexchange.com/ GIS Stack Exchange] for any GIS question for any software
* [http://slashgeo.org/ Slash Geo]
* [http://planet.osgeo.org/ Planet OSGeo]

== Acknowledgments ==
Thanks to various OSGeo local chapters and other wiki contributors whose work we borrowed and particularly CUGOS.

[[Category:Local Chapters]]
[[Category:PDX-OSGeo]]

FOSS4G2019 Q&A Full Proposal Bucharest

2017-12-04T23:21:53Z

Elil: Created page with " Category:Conference Committee Category:FOSS4G Category:FOSS4G2019"

[[Category:Conference Committee]]
[[Category:FOSS4G]]
[[Category:FOSS4G2019]]

FOSS4G 2019 Bid Process

2017-12-04T23:20:55Z

Elil: /* Bid Process */

= Basics =

* FOSS4G 2019 will most likely be held in Europe.
** [http://2018.foss4g.org FOSS4G 2018] will be in Dar es Salam, Tansania
* "Letters of Intent" will be accepted from potential Local Organizing Committees (LOC) in Europe. If there are no submissions from groups in Europe, letters from other regions will then be solicited.
* If more than one letter of intent is received, the Conference Committee members will vote. The vote procedure for 2019 changed, from this year on, every member of CC votes on every LoI. LoI's that receive more than 50% of "thumbs up"-votes will pass stage 1.
* Selected letters will be invited to prepare a full bid based on the usual RFP process.
* A proposal outlining budget, potential sponsors, LOC members, and venue costs will be required even if only one letter is received.

= Summary of Important Dates ([https://en.wikipedia.org/wiki/Anywhere_on_Earth AoE]) =

{|
|-
! Release RFP:
| 2017 September 08
|-
! Letters of Intent (Stage 1) due:
| 2017 September 29
|-
! Stage 1 question period:
| 2017 September 30 to 2017 October 13
|-
! Stage 1 decision:
| 2017 October 16
|-
! Proposals (Stage 2) due:
| 2017 December 4
|-
! Stage 2 question period:
| 2017 December 5 to 2017 December 15
|-
! Final decision by Conference Committee:
| 2017 December 18
|}

= Letters of Intent =

* Accepted until September 29, 2017
* Limited to two pages
* Read the RFP document (below) and answer the following questions:
** Who is your conference chair?
** Who else is on your LOC?
** What is your venue?
** What makes FOSS4G in your proposed location compelling?

Cameron Shorter, Chair of [[FOSS4G 2009]] suggests also addressing the following questions:
* Historically, half to three quarters of delegates come from the hosting country / region. Hence it is very valuable to have links with the regional geospatial industries.
* How do you propose to engage the regional communities in order to attract delegates and sponsors.
* The more recent conferences have all worked with a professional conference organizer. If you plan to make use of one, please mention them.

Till Adams, Chair of [[FOSS4G 2016]] also suggests to adress the following questions:
* Give a rough overview about potential costs (conference fees, accommodation, averaged prices for meal/drinks)

=== RFP Documents ===

* RFP containing updated process ([https://svn.osgeo.org/osgeo/foss4g/rfp/2019/FOSS4G2019-request-for-proposal.pdf RFP])
* Budget template ([https://svn.osgeo.org/osgeo/foss4g/rfp/2019/osgeo-conference-budget-template.ods file])

= Letter of Intent Review =

* Letters of Intent were received from the following local committees:
** [[https://svn.osgeo.org/osgeo/foss4g/proposals/2019/FOSS4G%202019%20Letter%20of%20Intent%20for%20Sevilla.pdf]] FOSS4G 2019 Letter of Intent for Sevilla [[FOSS4G2019_Q&A_Sevilla]]
** [[https://svn.osgeo.org/osgeo/foss4g/proposals/2019/FOSS4G_2019_LOI_Bucharest.pdf]] FOSS4G 2019 Letter of Intent for Bucarest]] [[FOSS4G2019_Q&A_Bucarest]]

* Questions will be asked of LOCs on conference_dev 2017-09-30 to 2017-10-13 - be prepared to answer the questions ASAP!
* Conference committee will vote and results announced on October 16th.
** Letters with 2 votes will be passed on to the proposal stage.
** If there are no qualified letters from the priority region, then additional regions will be considered or solicited.

= Bid Process =

* Bids will be required for selected applicants, due by November 27, 2017.
* Bids were received from:
** [[https://svn.osgeo.org/osgeo/foss4g/proposals/2019/FOSS4G_2019_Proposal_Sevilla.pdf Full proposal]] of Sevilla (SLOC) [[FOSS4G2019_Q&A_Full_Proposal_Sevilla]]
** [[https://svn.osgeo.org/osgeo/foss4g/proposals/2019/FOSS4G_2019_proposal_Bucharest.pdf Full proposal]] of Bucharest (BLOC) [[FOSS4G2019_Q&A_Full_Proposal_Bucharest]]
* Questions will be asked of bidders on conference_dev 2017-11-28 to 2017-12-12 - be prepared to answer the questions ASAP!
* A conference committee teleconference or IRC meeting might be held sometime between December 5 and December 12.
* Conference committee will vote and convey results to the OSGeo Board of Directors for approval on December 15, 2017.

[[Category:Conference Committee]]
[[Category:FOSS4G]]
[[Category:FOSS4G2019]]

FOSS4G 2019 Bid Process

2017-12-04T16:35:38Z

Elil: /* Bid Process */ Change link to SVN source

= Basics =

* FOSS4G 2019 will most likely be held in Europe.
** [http://2018.foss4g.org FOSS4G 2018] will be in Dar es Salam, Tansania
* "Letters of Intent" will be accepted from potential Local Organizing Committees (LOC) in Europe. If there are no submissions from groups in Europe, letters from other regions will then be solicited.
* If more than one letter of intent is received, the Conference Committee members will vote. The vote procedure for 2019 changed, from this year on, every member of CC votes on every LoI. LoI's that receive more than 50% of "thumbs up"-votes will pass stage 1.
* Selected letters will be invited to prepare a full bid based on the usual RFP process.
* A proposal outlining budget, potential sponsors, LOC members, and venue costs will be required even if only one letter is received.

= Summary of Important Dates ([https://en.wikipedia.org/wiki/Anywhere_on_Earth AoE]) =

{|
|-
! Release RFP:
| 2017 September 08
|-
! Letters of Intent (Stage 1) due:
| 2017 September 29
|-
! Stage 1 question period:
| 2017 September 30 to 2017 October 13
|-
! Stage 1 decision:
| 2017 October 16
|-
! Proposals (Stage 2) due:
| 2017 December 4
|-
! Stage 2 question period:
| 2017 December 5 to 2017 December 15
|-
! Final decision by Conference Committee:
| 2017 December 18
|}

= Letters of Intent =

* Accepted until September 29, 2017
* Limited to two pages
* Read the RFP document (below) and answer the following questions:
** Who is your conference chair?
** Who else is on your LOC?
** What is your venue?
** What makes FOSS4G in your proposed location compelling?

Cameron Shorter, Chair of [[FOSS4G 2009]] suggests also addressing the following questions:
* Historically, half to three quarters of delegates come from the hosting country / region. Hence it is very valuable to have links with the regional geospatial industries.
* How do you propose to engage the regional communities in order to attract delegates and sponsors.
* The more recent conferences have all worked with a professional conference organizer. If you plan to make use of one, please mention them.

Till Adams, Chair of [[FOSS4G 2016]] also suggests to adress the following questions:
* Give a rough overview about potential costs (conference fees, accommodation, averaged prices for meal/drinks)

=== RFP Documents ===

* RFP containing updated process ([https://svn.osgeo.org/osgeo/foss4g/rfp/2019/FOSS4G2019-request-for-proposal.pdf RFP])
* Budget template ([https://svn.osgeo.org/osgeo/foss4g/rfp/2019/osgeo-conference-budget-template.ods file])

= Letter of Intent Review =

* Letters of Intent were received from the following local committees:
** [[https://svn.osgeo.org/osgeo/foss4g/proposals/2019/FOSS4G%202019%20Letter%20of%20Intent%20for%20Sevilla.pdf]] FOSS4G 2019 Letter of Intent for Sevilla [[FOSS4G2019_Q&A_Sevilla]]
** [[https://svn.osgeo.org/osgeo/foss4g/proposals/2019/FOSS4G_2019_LOI_Bucharest.pdf]] FOSS4G 2019 Letter of Intent for Bucarest]] [[FOSS4G2019_Q&A_Bucarest]]

* Questions will be asked of LOCs on conference_dev 2017-09-30 to 2017-10-13 - be prepared to answer the questions ASAP!
* Conference committee will vote and results announced on October 16th.
** Letters with 2 votes will be passed on to the proposal stage.
** If there are no qualified letters from the priority region, then additional regions will be considered or solicited.

= Bid Process =

* Bids will be required for selected applicants, due by November 27, 2017.
* Bids were received from:
** [[https://svn.osgeo.org/osgeo/foss4g/proposals/2019/FOSS4G_2019_Proposal_Sevilla.pdf Full proposal]] of Sevilla (SLOC) [[FOSS4G2019_Q&A_Full_Proposal_Sevilla]]
* Questions will be asked of bidders on conference_dev 2017-11-28 to 2017-12-12 - be prepared to answer the questions ASAP!
* A conference committee teleconference or IRC meeting might be held sometime between December 5 and December 12.
* Conference committee will vote and convey results to the OSGeo Board of Directors for approval on December 15, 2017.

[[Category:Conference Committee]]
[[Category:FOSS4G]]
[[Category:FOSS4G2019]]

FOSS4G Travel Grant Programme 2017

2017-09-20T14:57:14Z

Elil: /* Procedure 2017 */ added Christopher to selection committee

=== Status ===
* Draft edited by Steven on 2017-06-21
* Final version, last edited by Till on 2017-06-22
* Crowdfunding section added by Eli on 2017-07-20

=== About ===
The FOSS4G Travel Grant Program for 2017 is administered by the Conference Committee.

This page sets out the process for applying for an OSGeo Travel Grant to attend FOSS4G 2017 and the process and criteria by which applicants will be selected.

* The OSGeo foundation has made an amount of US $10,000 available to fund a travel grant program

=== Details of the Travel Grant ===
* The TG covers a Full Conference Pass and an allowance for accommodation and meals/expenses
* It is anticipated that a TG will not normally exceed $1,000 (the Conference Committee can vary this guideline at their discretion in exceptional circumstances)
* Workshop attendance is not included in the Conference Pass, reduced rate fees for attendance at workshops will be available to grantees
* Applicants must be able to fund the direct costs of travel to FOSS4G and any booking deposits for accommodation
* Applicants must be in possession of a valid entry visa (if required).
* Successful applicants will receive a conference pass and become eligible for reimbursement of expenses up to the limit of the Travel Grant when they check-in at the conference registration desk. The reimbursement will arrive via mail weeks or months later after coordination with the OSGeo Treasurer.

=== Application & Deadline ===
Applications should be submitted on the [[https://docs.google.com/forms/d/1rIL7a9v5op8c0KNZLPOecuoEewflJTzfEW8T3JC2kiI TGP Application Form]] by '''2017-07-07 CET'''

=== Crowdfunding ===
There have been many great applications and we have limited funds. With a little more funds we are able to stretch our funds to include more recipients. We are looking to raise $1,500. Please donate to the Travel Grant Programme so that FOSS4G will have more great attendees.

* [https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=BHVFTPSGFS99W Donate to the OSGeo Travel Grant Programme].

=== Selection Process ===
We expect, that the money for the TGP will be less than the number of people wanting to get sponsorship for FOSS4G attendance

* The Selection process is partly based on [https://datahelpdesk.worldbank.org/knowledgebase/articles/906519 World Bank's Country Ranking] that group countries into these groups:
** LOW-INCOME ECONOMIES ($1,025 OR LESS)
** LOWER-MIDDLE-INCOME ECONOMIES ($1,026 TO $4,035)
** UPPER-MIDDLE-INCOME ECONOMIES ($4,036 TO $12,475)
** HIGH-INCOME ECONOMIES ($12,476 OR MORE)
* Priority is given to applicants from the first three groups above

* Additional selection criteria may include
** Gender
** Minority status
** Student
** Accepted talk

* Every applicant will be 'blind evaluated' in a secret table, after a calculation between money/costs per applicant travel grants are assigned to the top ranked applicants
* Applicants will be notified of the result of their application by '''2017-07-14''' at the latest
* The decision of the Conference Committee selection group is final and not subject to any appeal

=== Procedure 2017 ===
* We had 10k US$ from OSGeo plus some (~1k) donations from BLOC and some minor donations from private people
* Attendees could apply for TGP using the Google Form above and claimed for their needed sum
* 5 people (Till, Steven, Eli from CC & David and Christopher from BLOC) discussed the whole procedure and did the decision in the end by voting people on their own on a point system, top people were granted
* TGP paid for conference pass, overnight & local costs, not for travel, BLOC offered reduced fees for workshop participation

FOSS4G 2019 Bid Process

2017-08-31T23:01:28Z

Elil: Add note about draft

= Draft =
* This is a draft 
* Remove when ready 

= Basics =

* FOSS4G 2019 will most likely be held in Europe.
** [http://2018.foss4g.org FOSS4G 2018] will be in Dar es Salam, Tansania
* "Letters of Intent" will be accepted from potential Local Organizing Committees (LOC) in Europe. If there are no submissions from groups in Europe, letters from other regions will then be solicited.
* If more than one letter of intent is received, the Conference Committee members will vote by each selecting a single letter as their choice. A letter must receive the backing of at least two members to move on to the bid stage. [Steven Feldman suggests increasing minimum votes to 3 as we have 12+ voting members. Also suggest confirming that LoI votes should be made public after voting]
* Selected letters will be invited to prepare a full bid based on the usual RFP process.
* A proposal outlining budget, potential sponsors, LOC members, and venue costs will be required even if only one letter is received.

= Summary of Important Dates ([https://en.wikipedia.org/wiki/Anywhere_on_Earth AoE]) =

{|
|-
! Release RFP:
| 2017 September 08
|-
! Letters of Intent (Stage 1) due:
| 2017 September 29
|-
! Stage 1 question period:
| 2017 September 30 to 2017 October 13
|-
! Stage 1 decision:
| 2017 October 16
|-
! Proposals (Stage 2) due:
| 2017 November 27
|-
! Stage 2 question period:
| 2017 November 28 to 2017 December 12
|-
! Final decision:
| 2017 December 15
|}

= Letters of Intent =

* Accepted until September 29, 2017
* Limited to two pages
* Read the RFP document (below) and answer the following questions:
** Who is your conference chair?
** Who else is on your LOC?
** What is your venue?
** What makes FOSS4G in your proposed location compelling?

Cameron Shorter, Chair of [[FOSS4G 2009]] suggests also addressing the following questions:
* Historically, half to three quarters of delegates come from the hosting country / region. Hence it is very valuable to have links with the regional geospatial industries.
* How do you propose to engage the regional communities in order to attract delegates and sponsors.
* The more recent conferences have all worked with a professional conference organizer. If you plan to make use of one, please mention them.

Till Adams, Chair of [[FOSS4G 2016]] also suggests to adress the following questions:
* Give a rough overview about potential costs (conference fees, accommodation, averaged prices for meal/drinks)

=== RFP Documents ===

* RFP containing updated process ([https://svn.osgeo.org/osgeo/foss4g/rfp/2019/osgeo-conference-2019-request-for-proposal.pdf RFP]) NOT YET CREATED!
* Budget template ([http://svn.osgeo.org/osgeo/foss4g/rfp/2017/osgeo-conference-budget-template.ods file]) CAN WE USE THE OLD ONE HERE?

= Letter of Intent Review =

* Letters of Intent were received from the following local committees:
** ...

* Questions will be asked of LOCs on conference_dev 2017-09-30 to 2017-10-13 - be prepared to answer the questions ASAP!
* Conference committee will vote and results announced on October 16th.
** Letters with 2 votes will be passed on to the proposal stage.
** If there are no qualified letters from the priority region, then additional regions will be considered or solicited.

= Bid Process =

* Bids will be required for selected applicants, due by November 27, 2017.
* Bids were received from:
** ...
* Questions will be asked of bidders on conference_dev 2017-11-28 to 2017-12-12 - be prepared to answer the questions ASAP!
* A conference committee teleconference or IRC meeting might be held sometime between December 5 and December 12.
* Conference committee will vote and convey results to the OSGeo Board of Directors for approval on December 15, 2017.

[[Category:Conference Committee]]
[[Category:FOSS4G]]
[[Category:FOSS4G2019]]

FOSS4G 2019 Bid Process

2017-08-31T15:26:09Z

Elil: /* Bid Process */ The conference committee doesn't really officially select the LOC and FOSS4G location, we make a preliminary decision that is passed to the Board for approval

= Basics =

* FOSS4G 2019 will most likely be held in Europe.
** [http://2018.foss4g.org FOSS4G 2018] will be in Dar es Salam, Tansania
* "Letters of Intent" will be accepted from potential Local Organizing Committees (LOC) in Europe. If there are no submissions from groups in Europe, letters from other regions will then be solicited.
* If more than one letter of intent is received, the Conference Committee members will vote by each selecting a single letter as their choice. A letter must receive the backing of at least two members to move on to the bid stage. [Steven Feldman suggests increasing minimum votes to 3 as we have 12+ voting members. Also suggest confirming that LoI votes should be made public after voting]
* Selected letters will be invited to prepare a full bid based on the usual RFP process.
* A proposal outlining budget, potential sponsors, LOC members, and venue costs will be required even if only one letter is received.

= Summary of Important Dates ([https://en.wikipedia.org/wiki/Anywhere_on_Earth AoE]) =

{|
|-
! Release RFP:
| 2017 September 08
|-
! Letters of Intent (Stage 1) due:
| 2017 September 29
|-
! Stage 1 question period:
| 2017 September 30 to 2017 October 13
|-
! Stage 1 decision:
| 2017 October 16
|-
! Proposals (Stage 2) due:
| 2017 November 27
|-
! Stage 2 question period:
| 2017 November 28 to 2017 December 12
|-
! Final decision:
| 2017 December 15
|}

= Letters of Intent =

* Accepted until September 29, 2017
* Limited to two pages
* Read the RFP document (below) and answer the following questions:
** Who is your conference chair?
** Who else is on your LOC?
** What is your venue?
** What makes FOSS4G in your proposed location compelling?

Cameron Shorter, Chair of [[FOSS4G 2009]] suggests also addressing the following questions:
* Historically, half to three quarters of delegates come from the hosting country / region. Hence it is very valuable to have links with the regional geospatial industries.
* How do you propose to engage the regional communities in order to attract delegates and sponsors.
* The more recent conferences have all worked with a professional conference organizer. If you plan to make use of one, please mention them.

Till Adams, Chair of [[FOSS4G 2016]] also suggests to adress the following questions:
* Give a rough overview about potential costs (conference fees, accommodation, averaged prices for meal/drinks)

=== RFP Documents ===

* RFP containing updated process ([https://svn.osgeo.org/osgeo/foss4g/rfp/2019/osgeo-conference-2019-request-for-proposal.pdf RFP]) NOT YET CREATED!
* Budget template ([http://svn.osgeo.org/osgeo/foss4g/rfp/2017/osgeo-conference-budget-template.ods file]) CAN WE USE THE OLD ONE HERE?

= Letter of Intent Review =

* Letters of Intent were received from the following local committees:
** ...

* Questions will be asked of LOCs on conference_dev 2017-09-30 to 2017-10-13 - be prepared to answer the questions ASAP!
* Conference committee will vote and results announced on October 16th.
** Letters with 2 votes will be passed on to the proposal stage.
** If there are no qualified letters from the priority region, then additional regions will be considered or solicited.

= Bid Process =

* Bids will be required for selected applicants, due by November 27, 2017.
* Bids were received from:
** ...
* Questions will be asked of bidders on conference_dev 2017-11-28 to 2017-12-12 - be prepared to answer the questions ASAP!
* A conference committee teleconference or IRC meeting might be held sometime between December 5 and December 12.
* Conference committee will vote and convey results to the OSGeo Board of Directors for approval on December 15, 2017.

[[Category:Conference Committee]]
[[Category:FOSS4G]]
[[Category:FOSS4G2019]]

FOSS4G 2019 Bid Process

2017-08-31T15:22:12Z

Elil: /* Letters of Intent */ bout-->about typo

= Basics =

* FOSS4G 2019 will most likely be held in Europe.
** [http://2018.foss4g.org FOSS4G 2018] will be in Dar es Salam, Tansania
* "Letters of Intent" will be accepted from potential Local Organizing Committees (LOC) in Europe. If there are no submissions from groups in Europe, letters from other regions will then be solicited.
* If more than one letter of intent is received, the Conference Committee members will vote by each selecting a single letter as their choice. A letter must receive the backing of at least two members to move on to the bid stage. [Steven Feldman suggests increasing minimum votes to 3 as we have 12+ voting members. Also suggest confirming that LoI votes should be made public after voting]
* Selected letters will be invited to prepare a full bid based on the usual RFP process.
* A proposal outlining budget, potential sponsors, LOC members, and venue costs will be required even if only one letter is received.

= Summary of Important Dates ([https://en.wikipedia.org/wiki/Anywhere_on_Earth AoE]) =

{|
|-
! Release RFP:
| 2017 September 08
|-
! Letters of Intent (Stage 1) due:
| 2017 September 29
|-
! Stage 1 question period:
| 2017 September 30 to 2017 October 13
|-
! Stage 1 decision:
| 2017 October 16
|-
! Proposals (Stage 2) due:
| 2017 November 27
|-
! Stage 2 question period:
| 2017 November 28 to 2017 December 12
|-
! Final decision:
| 2017 December 15
|}

= Letters of Intent =

* Accepted until September 29, 2017
* Limited to two pages
* Read the RFP document (below) and answer the following questions:
** Who is your conference chair?
** Who else is on your LOC?
** What is your venue?
** What makes FOSS4G in your proposed location compelling?

Cameron Shorter, Chair of [[FOSS4G 2009]] suggests also addressing the following questions:
* Historically, half to three quarters of delegates come from the hosting country / region. Hence it is very valuable to have links with the regional geospatial industries.
* How do you propose to engage the regional communities in order to attract delegates and sponsors.
* The more recent conferences have all worked with a professional conference organizer. If you plan to make use of one, please mention them.

Till Adams, Chair of [[FOSS4G 2016]] also suggests to adress the following questions:
* Give a rough overview about potential costs (conference fees, accommodation, averaged prices for meal/drinks)

=== RFP Documents ===

* RFP containing updated process ([https://svn.osgeo.org/osgeo/foss4g/rfp/2019/osgeo-conference-2019-request-for-proposal.pdf RFP]) NOT YET CREATED!
* Budget template ([http://svn.osgeo.org/osgeo/foss4g/rfp/2017/osgeo-conference-budget-template.ods file]) CAN WE USE THE OLD ONE HERE?

= Letter of Intent Review =

* Letters of Intent were received from the following local committees:
** ...

* Questions will be asked of LOCs on conference_dev 2017-09-30 to 2017-10-13 - be prepared to answer the questions ASAP!
* Conference committee will vote and results announced on October 16th.
** Letters with 2 votes will be passed on to the proposal stage.
** If there are no qualified letters from the priority region, then additional regions will be considered or solicited.

= Bid Process =

* Bids will be required for selected applicants, due by November 27, 2017.
* Bids were received from:
** ...
* Questions will be asked of bidders on conference_dev 2017-11-28 to 2017-12-12 - be prepared to answer the questions ASAP!
* A conference committee teleconference or IRC meeting might be held sometime between December 5 and December 12.
* Conference committee will vote and results announced on December 15, 2017.

[[Category:Conference Committee]]
[[Category:FOSS4G]]
[[Category:FOSS4G2019]]

FOSS4G 2019 Bid Process

2017-08-31T15:21:06Z

Elil: /* Basics */ booting-->voting typo

= Basics =

* FOSS4G 2019 will most likely be held in Europe.
** [http://2018.foss4g.org FOSS4G 2018] will be in Dar es Salam, Tansania
* "Letters of Intent" will be accepted from potential Local Organizing Committees (LOC) in Europe. If there are no submissions from groups in Europe, letters from other regions will then be solicited.
* If more than one letter of intent is received, the Conference Committee members will vote by each selecting a single letter as their choice. A letter must receive the backing of at least two members to move on to the bid stage. [Steven Feldman suggests increasing minimum votes to 3 as we have 12+ voting members. Also suggest confirming that LoI votes should be made public after voting]
* Selected letters will be invited to prepare a full bid based on the usual RFP process.
* A proposal outlining budget, potential sponsors, LOC members, and venue costs will be required even if only one letter is received.

= Summary of Important Dates ([https://en.wikipedia.org/wiki/Anywhere_on_Earth AoE]) =

{|
|-
! Release RFP:
| 2017 September 08
|-
! Letters of Intent (Stage 1) due:
| 2017 September 29
|-
! Stage 1 question period:
| 2017 September 30 to 2017 October 13
|-
! Stage 1 decision:
| 2017 October 16
|-
! Proposals (Stage 2) due:
| 2017 November 27
|-
! Stage 2 question period:
| 2017 November 28 to 2017 December 12
|-
! Final decision:
| 2017 December 15
|}

= Letters of Intent =

* Accepted until September 29, 2017
* Limited to two pages
* Read the RFP document (below) and answer the following questions:
** Who is your conference chair?
** Who else is on your LOC?
** What is your venue?
** What makes FOSS4G in your proposed location compelling?

Cameron Shorter, Chair of [[FOSS4G 2009]] suggests also addressing the following questions:
* Historically, half to three quarters of delegates come from the hosting country / region. Hence it is very valuable to have links with the regional geospatial industries.
* How do you propose to engage the regional communities in order to attract delegates and sponsors.
* The more recent conferences have all worked with a professional conference organizer. If you plan to make use of one, please mention them.

Till Adams, Chair of [[FOSS4G 2016]] also suggests to adress the following questions:
* Give a rough overview bout potential costs (conference fees, accommodation, averaged prices for meal/drinks)

=== RFP Documents ===

* RFP containing updated process ([https://svn.osgeo.org/osgeo/foss4g/rfp/2019/osgeo-conference-2019-request-for-proposal.pdf RFP]) NOT YET CREATED!
* Budget template ([http://svn.osgeo.org/osgeo/foss4g/rfp/2017/osgeo-conference-budget-template.ods file]) CAN WE USE THE OLD ONE HERE?

= Letter of Intent Review =

* Letters of Intent were received from the following local committees:
** ...

* Questions will be asked of LOCs on conference_dev 2017-09-30 to 2017-10-13 - be prepared to answer the questions ASAP!
* Conference committee will vote and results announced on October 16th.
** Letters with 2 votes will be passed on to the proposal stage.
** If there are no qualified letters from the priority region, then additional regions will be considered or solicited.

= Bid Process =

* Bids will be required for selected applicants, due by November 27, 2017.
* Bids were received from:
** ...
* Questions will be asked of bidders on conference_dev 2017-11-28 to 2017-12-12 - be prepared to answer the questions ASAP!
* A conference committee teleconference or IRC meeting might be held sometime between December 5 and December 12.
* Conference committee will vote and results announced on December 15, 2017.

[[Category:Conference Committee]]
[[Category:FOSS4G]]
[[Category:FOSS4G2019]]

Face to Face Meeting Boston 2017

2017-08-14T06:34:21Z

Elil: Add link to Historical overview of OSGeo finances, providing OSGeo and FOSS4G context to discussion

== Meeting ==

Face-to-face meeting during FOSS4G 2017 in Boston.

=== When and Where ===

* Monday August 14, 18:00
* location: Flagship B Room at the Seaport Hotel

=== Attendees ===

Board members:
# [[Maria Brovelli]]
# [[Vasile Craciunescu]]
# [[Helena Mitasova]]
# [[User:Jive|Jody Garnett]]
# [[User:endofcap| Sanghee]]
# [[User:msmitherdc| Mike]]
# [[Angelos Tzotsos]] (remotely)
# add yourself

=== Agenda ===
# Brief report from FOSS4G2017 LOC (important for the "future of foss4g" discussion item)
# Discuss and approve pending MoUs and CLA
#* approve [[MOU_IGU|IGU-OSGeo MoU]]
#* approve [[MOU_GSDI|GSDI-OSGeo MoU]]
#* discuss [[MOU_DOI|DOI-OSGeo MoU]] (waiting for the DoI legal review)
#* discuss LocationTech MoU
# Vote on funding requests
#* OSGeo Journal issue with FOSS4G Bonn papers: $1200 for layout and proofing
# OSGeo and FOSS4G Conferences
#* cost: Vasile report, discussion
#* scheduling
#* See also [[Finance_Operational_Notes#Historical_Overview]] ''(I'm not able to attend the meeting or conference but that would be my input. -Eli)''
# OSGeo Project Status
#* Report from Maxi and Jeff, Jeff invited to present
#* Project by project recommendations
#* Project categories, see [[OSGeo_Community_Projects#Comparison_with_Incubation|Comparison]]
# System admin committee coordination - invitation extended to Alex Mandel
# 2017 elections

=== Goal ===

We invite board members not present at the [[Face to Face Meeting Paris 2017|Paris F2F Meeting]] to revisit their initial goals at elected representatives (to provide context for the days discussion).

The overall goal of the meeting is to coordinate two "hot topics" for the OSGeo community: event attendance costs and OSGeo project health.

We should leave this meeting with clear guidance for the subsequent board and affected committees on these two issues.

== Meeting Minutes ==

[[Category: Board]]
[[Category: Board Meetings 2017]]
[[Category: FOSS4G 2017]]

Finance Operational Notes

2017-08-14T06:26:44Z

Elil: /* Observations */

This documented is intended to document various aspects of OSGeo's financial operations, to provide rough information on how things are setup to the treasurer, finance committee, and board.

== General ==

* Tyler as ED is responsible for day to day financial operation of OSGeo. He makes payments, issues invoices, cashes cheques, and enters transaction details into the accounting system (Quickbooks online).
* The [[Finance Committee]] is responsible for auditing financial reports, developing financial management policy, and preparing a budget for the board.
* The Treasurer chairs the Finance committee, and is responsible for operational financial decisions within the framework of the budget.
* The [[Board of Directors]] is responsible for approving a budget.

== Quick Books Online ==

OSGeo keeps detailed accounts using Quick Books Online. Currently Tyler (ED) and the Treasurer have accounts with update access for the OSGeo Quick Books instance. The rest of the finance committee has access to a read-only reporting account (contact Tyler or the Treasurer for details).

== Accounts ==
== PEO ==

== Processes ==
On monthly basis:
# Download account data, import to Quickbooks
## Include three bank accounts, paypal
# Enter credit charge charges, invoices, bill pays
# Review wire transfers, confirm sources
# Reconcile account data with cash accounts
# Pay credit card bill
# Quick summary report to Finance Committee (cash, outlook)

Quarterly:
# Reviewing sponsorship status
# Issue new or follow up on outstanding sponsor invoices
# Produce quarterly reports - income/expenses, balance sheet, summaries by class
# Submit reports to Finance Committee

Ongoing:
# Pay marketing and office bills

Annually:
# Prepare annual budget for approval by the board
# File Delaware state franchise tax
## http://corp.delaware.gov/frtax.shtml
## includes "annual report" that lists current directors
# British Columbia provincial annual report
## Filed with Pat @ Oliver & Co., Williams Lake BC
# Directors & Officers Liability insurance renewal
## Current broker: Chapman (chapmanins.com)
## Renewal date: May 13, Fill application in March/April
# Internal year end finance report
## Prepare any final invoices for the year
## Hunt down FOSS4G funds
## Reconcile to statements
# Submit report to Finance Committe
# Include official report in Annual Report
# Write Finance Committee report

== Historical Overview ==
* This section might belong somewhere else in the Finance category but this was a good place to start.
* This focuses on revenue, not expenses. Someone else could certainly fill that in since it is an important part of the finances.
* This is an overview, minor aspects are omitted. (For example GSOC is both a small income --and maybe equal expense, not sure but either way it is minor and this is a general overview.)
* This focuses on 2007-2016/7.
* The FOSS4G "years" mean nothing in the current data portrayal. FOSS4G funds coming back to OSGeo come in multiple payments over multiple years. This does show that OSGeo needs to be able to float a substantial period of time before funds return. This data should probably be sorted out and possibly analyzed on a regional (i.e. every third year) basis for Europe, North America, Rest of World.

=== Data ===
* This summary comes from the help of OSGeo Treasurers. It is the source that was further generalized and used to subsequently derive these graphs.

=== Revenue Graphs ===
[[File:OSGeo_sponsorship_2007-2017.png|thumbnail|center|OSGeo Sponsorship 2007-2017]]
[[File:OSGeo_FOSS4G_2007-2017.png|thumbnail|center|OSGeo FOSS4G 2007-2017]]

[[File:OSGeo_2007.png|thumbnail|center|OSGeo proportions 2007]]
[[File:OSGeo_2008.png|thumbnail|center|OSGeo proportions 2008]]
[[File:OSGeo_2009.png|thumbnail|center|OSGeo proportions 2009]]
[[File:OSGeo_2010.png|thumbnail|center|OSGeo proportions 2010]]
[[File:OSGeo_2011.png|thumbnail|center|OSGeo proportions 2011]]
[[File:OSGeo_2012.png|thumbnail|center|OSGeo proportions 2012]]
[[File:OSGeo_2013.png|thumbnail|center|OSGeo proportions 2013]]
[[File:OSGeo_2014.png|thumbnail|center|OSGeo proportions 2014]]
[[File:OSGeo_2015.png|thumbnail|center|OSGeo proportions 2015]]
[[File:OSGeo_2016.png|thumbnail|center|OSGeo proportions 2016]]
[[File:OSGeo_2017.png|thumbnail|center|OSGeo proportions 2017]]

=== Observations ===
* OSGeo sponsorship has declined to an insignificant portion of the OSGeo budget. With effort, it might be possible to increase OSGeo sponsorship again.
* FOSS4G is now essentially the sole source of OSGeo's financial existence which exerts financial pressure on FOSS4G. However, that has not always historically been the case.
* Further analysis of the FOSS4G numbers are needed to see if anything can be determined from the regions and rotation.
* The FOSS4G average is ~$81,587 from ~791 attendees (excluding 2012 for attendance) or ~$103/attendee.

[[Category: Finance]]

Finance Operational Notes

2017-08-14T06:16:25Z

Elil: /* Revenue Graphs */

This documented is intended to document various aspects of OSGeo's financial operations, to provide rough information on how things are setup to the treasurer, finance committee, and board.

== General ==

* Tyler as ED is responsible for day to day financial operation of OSGeo. He makes payments, issues invoices, cashes cheques, and enters transaction details into the accounting system (Quickbooks online).
* The [[Finance Committee]] is responsible for auditing financial reports, developing financial management policy, and preparing a budget for the board.
* The Treasurer chairs the Finance committee, and is responsible for operational financial decisions within the framework of the budget.
* The [[Board of Directors]] is responsible for approving a budget.

== Quick Books Online ==

OSGeo keeps detailed accounts using Quick Books Online. Currently Tyler (ED) and the Treasurer have accounts with update access for the OSGeo Quick Books instance. The rest of the finance committee has access to a read-only reporting account (contact Tyler or the Treasurer for details).

== Accounts ==
== PEO ==

== Processes ==
On monthly basis:
# Download account data, import to Quickbooks
## Include three bank accounts, paypal
# Enter credit charge charges, invoices, bill pays
# Review wire transfers, confirm sources
# Reconcile account data with cash accounts
# Pay credit card bill
# Quick summary report to Finance Committee (cash, outlook)

Quarterly:
# Reviewing sponsorship status
# Issue new or follow up on outstanding sponsor invoices
# Produce quarterly reports - income/expenses, balance sheet, summaries by class
# Submit reports to Finance Committee

Ongoing:
# Pay marketing and office bills

Annually:
# Prepare annual budget for approval by the board
# File Delaware state franchise tax
## http://corp.delaware.gov/frtax.shtml
## includes "annual report" that lists current directors
# British Columbia provincial annual report
## Filed with Pat @ Oliver & Co., Williams Lake BC
# Directors & Officers Liability insurance renewal
## Current broker: Chapman (chapmanins.com)
## Renewal date: May 13, Fill application in March/April
# Internal year end finance report
## Prepare any final invoices for the year
## Hunt down FOSS4G funds
## Reconcile to statements
# Submit report to Finance Committe
# Include official report in Annual Report
# Write Finance Committee report

== Historical Overview ==
* This section might belong somewhere else in the Finance category but this was a good place to start.
* This focuses on revenue, not expenses. Someone else could certainly fill that in since it is an important part of the finances.
* This is an overview, minor aspects are omitted. (For example GSOC is both a small income --and maybe equal expense, not sure but either way it is minor and this is a general overview.)
* This focuses on 2007-2016/7.
* The FOSS4G "years" mean nothing in the current data portrayal. FOSS4G funds coming back to OSGeo come in multiple payments over multiple years. This does show that OSGeo needs to be able to float a substantial period of time before funds return. This data should probably be sorted out and possibly analyzed on a regional (i.e. every third year) basis for Europe, North America, Rest of World.

=== Data ===
* This summary comes from the help of OSGeo Treasurers. It is the source that was further generalized and used to subsequently derive these graphs.

=== Revenue Graphs ===
[[File:OSGeo_sponsorship_2007-2017.png|thumbnail|center|OSGeo Sponsorship 2007-2017]]
[[File:OSGeo_FOSS4G_2007-2017.png|thumbnail|center|OSGeo FOSS4G 2007-2017]]

[[File:OSGeo_2007.png|thumbnail|center|OSGeo proportions 2007]]
[[File:OSGeo_2008.png|thumbnail|center|OSGeo proportions 2008]]
[[File:OSGeo_2009.png|thumbnail|center|OSGeo proportions 2009]]
[[File:OSGeo_2010.png|thumbnail|center|OSGeo proportions 2010]]
[[File:OSGeo_2011.png|thumbnail|center|OSGeo proportions 2011]]
[[File:OSGeo_2012.png|thumbnail|center|OSGeo proportions 2012]]
[[File:OSGeo_2013.png|thumbnail|center|OSGeo proportions 2013]]
[[File:OSGeo_2014.png|thumbnail|center|OSGeo proportions 2014]]
[[File:OSGeo_2015.png|thumbnail|center|OSGeo proportions 2015]]
[[File:OSGeo_2016.png|thumbnail|center|OSGeo proportions 2016]]
[[File:OSGeo_2017.png|thumbnail|center|OSGeo proportions 2017]]

=== Observations ===
* OSGeo sponsorship has declined to an insignificant portion of the OSGeo budget. With effort, it might be possible to increase OSGeo sponsorship again.
* FOSS4G is now essentially the sole source of OSGeo's financial existence which exerts financial pressure on FOSS4G. However, that has not always historically been the case.
* Further analysis of the FOSS4G numbers are needed to see if anything can be determined from the regions and rotation.
* The FOSS4G average is ~$81,587 from ~791 attendees (excluding 2012 for attendance) or ~103/attendee.

[[Category: Finance]]

File:OSGeo 2017.png

2017-08-14T06:15:07Z

Elil:

File:OSGeo 2016.png

2017-08-14T06:14:56Z

Elil:

File:OSGeo 2015.png

2017-08-14T06:14:45Z

Elil:

File:OSGeo 2014.png

2017-08-14T06:14:29Z

Elil:

File:OSGeo 2013.png

2017-08-14T06:14:21Z

Elil:

File:OSGeo 2012.png

2017-08-14T06:14:09Z

Elil: