<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.osgeo.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Stevenfeldman</id>
	<title>OSGeo - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.osgeo.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Stevenfeldman"/>
	<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/wiki/Special:Contributions/Stevenfeldman"/>
	<updated>2026-04-11T22:53:35Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.35.9</generator>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Conference_Committee&amp;diff=129455</id>
		<title>Conference Committee</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Conference_Committee&amp;diff=129455"/>
		<updated>2022-10-29T12:54:31Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: Resigned from CC&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The Conference Committee is the official committee of OSGeo responsible for operating the annual [[FOSS4G]] conferences.&lt;br /&gt;
&lt;br /&gt;
= Noteworthy Documents = &lt;br /&gt;
&lt;br /&gt;
* [[FOSS4G Handbook]] (provides guidance to future FOSS4G and related events, based upon the collective wisdom gained during prior events)&lt;br /&gt;
* [http://lists.osgeo.org/mailman/listinfo/conference_dev Conference Committee email list]&lt;br /&gt;
* [http://www.osgeo.org/conference OSGeo Conference Committee main page] (includes RFP, proposals, and archived files from past conferences)&lt;br /&gt;
* Past conference reports are detailed at [[Past FOSS4G Reports]]&lt;br /&gt;
* [[Conference website management]]&lt;br /&gt;
* [[Motion to form Conference Committee]]&lt;br /&gt;
* [[Conference Committee Budget 2017 | Conference Committee Budget 2017 (draft)]]&lt;br /&gt;
&lt;br /&gt;
= Goals =&lt;br /&gt;
The conference committee have the responsibility to:&lt;br /&gt;
* Run the selection process and voting for the global FOSS4G&lt;br /&gt;
* Vote on conference related proposals submitted to the committee&lt;br /&gt;
* Retain the [[FOSS4G Handbook | collected wisdom]] for FOSS4G and related events&lt;br /&gt;
* Advise the board, Local Organising Committees (LOC), and related events organisors, ideally referencing the [[FOSS4G Handbook]]&lt;br /&gt;
* Ensure OSGeo foundation principles are applied to global FOSS4G conferences&lt;br /&gt;
* Manage the FOSS4G Travel Grant Programme for FOSS4G and regional events&lt;br /&gt;
&lt;br /&gt;
See also: '''2016 priorities are summarised in [[Conference Committee 2016 Priorities]]'''&lt;br /&gt;
&lt;br /&gt;
=Housekeeping Procedures=&lt;br /&gt;
The Conference Committee uses the following procedures to make decisions.&lt;br /&gt;
&lt;br /&gt;
==Decisions==&lt;br /&gt;
&lt;br /&gt;
[[consideration for new selection methods]]&lt;br /&gt;
&lt;br /&gt;
# Anyone may contribute to conference committee discussions. All votes will be noted, but only conference committee member votes count toward decisions.&lt;br /&gt;
# Voting will use convention of:&lt;br /&gt;
#* +1 : For&lt;br /&gt;
#* +0: Mildly for&lt;br /&gt;
#* 0: Indifferent&lt;br /&gt;
#* -0: Mildly against&lt;br /&gt;
#* -1 : Strongly against. This is expected to be accompanied by a reason and alternative proposal.&lt;br /&gt;
# 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.&lt;br /&gt;
# 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.&lt;br /&gt;
# The committee aims for consensus, and will specifically attempt to address all -1 votes, but will revert to a majority vote where necessary.&lt;br /&gt;
# The result will be clearly declared afterwards.&lt;br /&gt;
# Secret voting, when required, will use an online voting service or use an email to an independent teller appointed by CC Chair.&lt;br /&gt;
&lt;br /&gt;
==FOSS4G Selection==&lt;br /&gt;
&lt;br /&gt;
# All Letters of Intent and subsequent proposals will be posted to the list for open comment by all. &lt;br /&gt;
# The selection of the winning proposal is by secret vote of conference committee members.&lt;br /&gt;
# The OSGeo Board will be requested to ratify the conference committee’s recommendation.&lt;br /&gt;
# 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.&lt;br /&gt;
&lt;br /&gt;
=== Changes in RfP Document for 2021 ===&lt;br /&gt;
* At least at the letters-of-intent stage there should always be a voting option of &amp;quot;None of the above&amp;quot;. 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.&lt;br /&gt;
* Bids should be scored based on various pre-defined criterion. Current voting by the committee seems to include a &amp;quot;where I want to go on holiday&amp;quot; component which has no place in a process like this. This is in keeping with the &amp;quot;openness&amp;quot; goal of OSGeo as compared to the current Star Chamber-like voting.&lt;br /&gt;
* Further to the above, a list of objective mandatory criterion can be specified as required. I.e. &amp;quot;Venue must be able to host X people&amp;quot;, &amp;quot;must be at least Y tracks&amp;quot;, &amp;quot;Must be accessible via both local and national public transport&amp;quot;, etc.&lt;br /&gt;
&lt;br /&gt;
==FOSS4G Travel Grant Programme==&lt;br /&gt;
&lt;br /&gt;
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&lt;br /&gt;
&lt;br /&gt;
* [[FOSS4G Travel Grant Programme 2017 | 2017]] &lt;br /&gt;
* [[FOSS4G Travel Grant Programme 2018 | 2018]]&lt;br /&gt;
&lt;br /&gt;
=== Setting up a FOSS4G TGP ===&lt;br /&gt;
&lt;br /&gt;
Some guidance notes are available in the [[FOSS4G Travel Grant Programme Cookbook | FOSS4G Travel Grant Programme Cookbook]]&lt;br /&gt;
&lt;br /&gt;
==Membership==&lt;br /&gt;
&lt;br /&gt;
# 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.&lt;br /&gt;
# The conference committee aims to retain a chair or vice-chair from the 5 most recent global FOSS4G conferences.&lt;br /&gt;
# 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.&lt;br /&gt;
# Each year, prior to releasing the Global FOSS4G RfP, the membership list shall be re-visited.&lt;br /&gt;
## 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.&lt;br /&gt;
## Interested people may be suggested, or request to be voted onto the conference committee.&lt;br /&gt;
## 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.&lt;br /&gt;
## 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 &amp;quot;Yes&amp;quot; for up to the number of positions available.&lt;br /&gt;
# 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.&lt;br /&gt;
&lt;br /&gt;
== Current Members == &lt;br /&gt;
&lt;br /&gt;
# [[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)&lt;br /&gt;
# [[User:pmbatty | Peter Batty]] - member since 2011 (chair of Global FOSS4G 2011)&lt;br /&gt;
# [[User:Bitner | David Bitner]] (chair of the 2013 FOSS4GNA)&lt;br /&gt;
# [[User:Maria | Maria Brovelli]] - member since March 2016 (Chair FOSS4G Europe 2015)&lt;br /&gt;
# [[User:Vasile | Vasile Craciunescu]]  - '''Co-Chair''' - member since July 2013 (chair of FOSS4G Central and Eastern Europe 2013)&lt;br /&gt;
# David Fawcett (Programme Team FOSS4GNA 2013)&lt;br /&gt;
# [[User:GFleming |Gavin Fleming]] - (chair of Global FOSS4G 2008)&lt;br /&gt;
# Darrell Fuhriman (chair of Global FOSS4G 2014)&lt;br /&gt;
# Claude Philipona - (chair of Global FOSS4G 2006)&lt;br /&gt;
# [[User:Venkat | Venkatesh Raghavan]] - member since Oct. 2006 (Chair FOSS4G-2004, FOSS4G-Asia 2014) &lt;br /&gt;
# [[User:Pwramsey3 | Paul Ramsey]] - Chair of global FOSS4G 2007 &lt;br /&gt;
# [[User:Sanghee | Sanghee Shin]] - member since 2015 (chair of Global FOSS4G 2015)&lt;br /&gt;
# [[User:Gsteinmon | Guido Stein]] - member since February 2018 (chair of Global FOSS4G 2017)&lt;br /&gt;
# [[User:MichaelTerner | Michael Terner]] - member since February 2018 (chair of Global FOSS4G 2017)&lt;br /&gt;
# Msilikale Msilanga - '''Co-Chair''' - member since September 2018 (co-chair of Global FOSS4G 2018)&lt;br /&gt;
# Mark Iliffe - member since September 2018 (co-chair of Global FOSS4G 2018)&lt;br /&gt;
# [[User:Delawen | María Arias de Reyna Domínguez]] - member since November 2021 (chair of Global FOSS4G 2021)&lt;br /&gt;
# [[User:Lucadelu | Luca Delucchi]] - member since October 2022 (chair of Global FOSS4G 2022)&lt;br /&gt;
* [https://lists.osgeo.org/pipermail/conference_dev/2019-December/005411.html Motion for co-chairs]&lt;br /&gt;
&lt;br /&gt;
== Past Members ==&lt;br /&gt;
&lt;br /&gt;
# Jeff McKenna&lt;br /&gt;
# Lorenzo Becchi&lt;br /&gt;
# Allan Doyle&lt;br /&gt;
# Olivier Ertz&lt;br /&gt;
# Alain Grignon&lt;br /&gt;
# Luc Maurer&lt;br /&gt;
# Daniel Rappo&lt;br /&gt;
# Dave Patton&lt;br /&gt;
# Rafael Medeiros Sperb&lt;br /&gt;
# Arnulf Christl&lt;br /&gt;
# [[Markus Neteler]]&lt;br /&gt;
# Steve Lime&lt;br /&gt;
# Frank Warmerdam&lt;br /&gt;
# [[User:Davemac | Dave McIlhagga]] (resigned August 2016)&lt;br /&gt;
# [[User:Ticheler | Jeroen Ticheler]] (resigned September 2016)&lt;br /&gt;
# [[User:Thierry Badard | Thierry Badard]] (resigned September 2016)&lt;br /&gt;
# [[User:Helena | Helena Mitasova]] (resigned September 2016)&lt;br /&gt;
# [[User:Camerons | Cameron Shorter]] - member from 2009 to Oct 2017 (chair of Global FOSS4G 2009)&lt;br /&gt;
# [[User:Jachym | Jachym Cepicky]] - (resigned August 2019)&lt;br /&gt;
# [[User:Till Adams | Till Adams]]  - resigned October 2022 / member since September 2016 (chair of Global FOSS4G 2016)&lt;br /&gt;
# [[User:Stevenfeldman | Steven Feldman]] - resigned October 2022 / member since October 2013 (chair of Global FOSS4G 2013)&lt;br /&gt;
&lt;br /&gt;
= Meetings =&lt;br /&gt;
&lt;br /&gt;
* Meetings occur in IRC in the #foss4g channel (on irc.freenode.net) or by other means organized on the email list.  Meetings are infrequent.&lt;br /&gt;
* &amp;lt;s&amp;gt;As of 2016 the [[Conference_Committee_Meetings | Conference Committee Meetings]] page was not being maintained any more.&amp;lt;/s&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=2023 Pages=&lt;br /&gt;
* [[FOSS4G_2023_Bid_Process | 2023 RFP schedule]]&lt;br /&gt;
&lt;br /&gt;
=2022 Pages=&lt;br /&gt;
&lt;br /&gt;
* [[FOSS4G_2022_Bid_Process | 2022 RFP schedule]]&lt;br /&gt;
&lt;br /&gt;
=2021 Pages=&lt;br /&gt;
&lt;br /&gt;
* [[FOSS4G_2021_Bid_Process | 2021 RFP schedue]]&lt;br /&gt;
&lt;br /&gt;
=2020 Pages=&lt;br /&gt;
&lt;br /&gt;
* [[FOSS4G_2020_Bid_Process | 2020 RFP schedue]]&lt;br /&gt;
&lt;br /&gt;
=2019 Pages=&lt;br /&gt;
&lt;br /&gt;
* [[FOSS4G_2019_Bid_Process | 2019 RFP schedule]]&lt;br /&gt;
&lt;br /&gt;
=2018 Pages=&lt;br /&gt;
&lt;br /&gt;
* [[FOSS4G_2018_Bid_Process | 2018 RFP schedule]]&lt;br /&gt;
* [[Conference_Committee_F2F_2016 | Conference Committee Face to Face meeting in Bonn, 2016]]&lt;br /&gt;
&lt;br /&gt;
= 2017 Pages =&lt;br /&gt;
&lt;br /&gt;
* [[FOSS4G_2017_Bid_Process | 2017 RFP schedule]]&lt;br /&gt;
* [[FOSS4G_Travel_Grant_Programme_2017 | 2017 Travel Grant Programme]]&lt;br /&gt;
&lt;br /&gt;
= 2016 Pages =&lt;br /&gt;
&lt;br /&gt;
* [http://www.osgeo.org/conference/rfp/ 2016 RFP schedule]&lt;br /&gt;
&lt;br /&gt;
= 2015 Pages =&lt;br /&gt;
&lt;br /&gt;
* [[FOSS4G 2015 Bid Process]]&lt;br /&gt;
&lt;br /&gt;
= 2014 Pages =&lt;br /&gt;
&lt;br /&gt;
* [[FOSS4G 2014 Bid Process]]&lt;br /&gt;
* [[FOSS4G 2014]]&lt;br /&gt;
* [[FOSS4G Europe 2014]]&lt;br /&gt;
&lt;br /&gt;
= 2013 Pages =&lt;br /&gt;
&lt;br /&gt;
* Main page: [[FOSS4G_2013]]&lt;br /&gt;
* [http://svn.osgeo.org/osgeo/foss4g/2013/documents/FOSS4G_2013_UK_Proposal-Final_version.pdf 2013 Proposal]&lt;br /&gt;
* Reflections on the event by the LOC (includes lessons learnt and supersedes the old Lessons Learned page): [[FOSS4G2013_Reflections_by_the_LOC]]&lt;br /&gt;
&lt;br /&gt;
= 2012 Pages =&lt;br /&gt;
Main page: [[FOSS4G 2012]]&lt;br /&gt;
* 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])&lt;br /&gt;
* budget template ([http://svn.osgeo.org/osgeo/foss4g/rfp/2012/osgeo-conference-budget-template.ods OpenOffice])&lt;br /&gt;
* Important dates:&lt;br /&gt;
** Letters of Intent (Stage 1) due: 2011-06-30 ([http://www.timeanddate.com/worldclock/fixedtime.html?year=2011&amp;amp;month=06&amp;amp;day=30&amp;amp;hour=23&amp;amp;min=0&amp;amp;sec=0 23:00 UTC])&lt;br /&gt;
** Stage 1 question period: 2011-06-30 to 2011-07-07&lt;br /&gt;
** Stage 1 decision: 2011-07-07&lt;br /&gt;
** Proposals (Stage 2) due: 2011-08-01 ([http://www.timeanddate.com/worldclock/fixedtime.html?year=2011&amp;amp;month=08&amp;amp;day=01&amp;amp;hour=23&amp;amp;min=0&amp;amp;sec=0 23:00 UTC])&lt;br /&gt;
** Stage 2 question period: 2011-08-01 to 2011-08-05&lt;br /&gt;
** Final decision: 2011-08-05&lt;br /&gt;
&lt;br /&gt;
= 2011 Pages = &lt;br /&gt;
&lt;br /&gt;
* [http://www.osgeo.org/conference/rfp RFP and Letters of Intent]&lt;br /&gt;
* [[FOSS4G_2011_Bid_Process | 2011 Bid Process]]&lt;br /&gt;
* [[FOSS4G Reboot 2011 | Initial thoughts on 2011 required changes]]&lt;br /&gt;
&lt;br /&gt;
= 2010 Pages = &lt;br /&gt;
&lt;br /&gt;
* [http://www.osgeo.org/conference/rfp RFP and Proposals]&lt;br /&gt;
* [[Conference_Committee_2010_Bid_Questions | Bid Questions]]&lt;br /&gt;
* [[Conference_Committee_2010_Voting_Process | Voting Process]]&lt;br /&gt;
&lt;br /&gt;
= 2009 Pages = &lt;br /&gt;
&lt;br /&gt;
* [[FOSS4G 2009 Governance]]&lt;br /&gt;
* All [http://wiki.osgeo.org/wiki/Category:FOSS4G2009 FOSS4G 2009] pages.&lt;br /&gt;
&lt;br /&gt;
= 2008 Pages =&lt;br /&gt;
&lt;br /&gt;
* [http://www.osgeo.org/conference/rfp RFP and Proposals]&lt;br /&gt;
* [http://lists.osgeo.org/pipermail/conference_dev/2007-July/000355.html Voting Process]&lt;br /&gt;
* [[FOSS4G 2008 Governance]]&lt;br /&gt;
* [[FOSS4GLOC matters]]&lt;br /&gt;
* [http://spreadsheets.google.com/pub?key=p6mc38S7PA8lHWRQuIgExDA Workshop and lab evaluations]&lt;br /&gt;
&lt;br /&gt;
= 2007 Pages =&lt;br /&gt;
&lt;br /&gt;
* [http://wiki.osgeo.org/index.php/Category:FOSS4G2007 Pages in category &amp;quot;FOSS4G2007&amp;quot;]&lt;br /&gt;
* [[FOSS4G2007]] - wiki page&lt;br /&gt;
* http://www.foss4g2007.org/ - Conference Site &lt;br /&gt;
* [http://www.osgeo.org/conference/rfp Proposals and RFP]&lt;br /&gt;
* [[OSGeo_Conference_RFP_2007#RFP_Response_Requirements | requirements Wiki page]]&lt;br /&gt;
* [[OSGeo_Conference_Naming_Results | Naming results]]&lt;br /&gt;
* [http://www.foss4g2007.org/bid_site/ Victoria 2007 Proposal]&lt;br /&gt;
* [[FOSS4G 2007 Governance]]&lt;br /&gt;
* [[FOSS4G2007 Lessons Learned]]&lt;br /&gt;
&lt;br /&gt;
= 2006 Pages =&lt;br /&gt;
&lt;br /&gt;
* [http://wiki.osgeo.org/index.php/Category:FOSS4G2006 Pages in category &amp;quot;FOSS4G2006&amp;quot;]&lt;br /&gt;
* http://www.foss4g2006.org/ - Conference Site&lt;br /&gt;
* [[FOSS4G2006]] information&lt;br /&gt;
&lt;br /&gt;
= Event Policy Pages =&lt;br /&gt;
&lt;br /&gt;
* [[Official_OSGeo_Event_Policy | OSGeo Event policy]] (in review)&lt;br /&gt;
* [[OSGeo_Conference_Policy | Board notes]] regarding event policy&lt;br /&gt;
* [http://www.osgeo.org/code_of_conduct OSGeo Code of Conduct]&lt;br /&gt;
&lt;br /&gt;
[[Category:FOSS4G]]&lt;br /&gt;
[[Category:Committees]]&lt;br /&gt;
[[Category:Conference Committee]]&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=User:Stevenfeldman&amp;diff=126454</id>
		<title>User:Stevenfeldman</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=User:Stevenfeldman&amp;diff=126454"/>
		<updated>2021-04-07T09:46:46Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{OSGeo Member&lt;br /&gt;
|Name=Steven Feldman&lt;br /&gt;
|JobTitle=Principal&lt;br /&gt;
|Company=KnowWhere Consulting&lt;br /&gt;
|Country=UK&lt;br /&gt;
|City=London&lt;br /&gt;
|Coordinate=51.5073219, -0.1276474&lt;br /&gt;
|LocalChapter= [http://uk.osgeo.org OSGeo:UK]&lt;br /&gt;
|Website=https://www.knowwhereconsulting.co.uk/&lt;br /&gt;
|Photo=StevenFeldmanPic.jpg&lt;br /&gt;
|Info=Steven Feldman was Managing Director of GDC, a UK local government specialist and subsequently of MapInfo UK. He now mentors startups and advises businesses in the location space while focussing his spare time on Open Data and Open Source projects including the [http://www.osmgb.org.uk OSM-GB] project at the Nottingham Geospatial Institute.&lt;br /&gt;
&lt;br /&gt;
Steven is currently a strategic advisor to [https://astuntechnology.com Astun Technology], chairman of [https://geo.me geo.me Solutions], past chairman of [https://exprodat.com Exprodat Consulting] and  a board advisor at [https://www.opencagedata.com OpenCage Data].&lt;br /&gt;
&lt;br /&gt;
Steven was the Chair of the LOC for [http://2013.foss4g.org/ FOSS4G 2013]. He is a recent past chair the Conference Committee and is active in [http://uk.osgeo.org OSGeo:UK, the UK local chapter]&lt;br /&gt;
&lt;br /&gt;
Steven is a regular presenter on geo and open topics, some slide decks are [https://drive.google.com/drive/folders/18FLUY_t9VdQLGpwkYXabIh2y62aXDfX1?usp=sharing here]. He tends to tweet too much as [http://twitter.com/stevenfeldman @stevenfeldman]&lt;br /&gt;
}}&lt;br /&gt;
{{OSGeo Experience&lt;br /&gt;
|User=Yes&lt;br /&gt;
|Committee=Yes&lt;br /&gt;
|Board=No&lt;br /&gt;
|Coder=No&lt;br /&gt;
|Translate=No&lt;br /&gt;
|PSC=No&lt;br /&gt;
|ExBoard=No&lt;br /&gt;
|Charter=Yes&lt;br /&gt;
|Chair=No&lt;br /&gt;
|SolKatz=No&lt;br /&gt;
|Committer=No&lt;br /&gt;
}}&lt;br /&gt;
;Contact:&lt;br /&gt;
: Email: [https://knowwhereconsulting.co.uk/contact/ via KnowWhere]&lt;br /&gt;
: via [https://twitter.com/stevenfeldman twitter]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
;Spoken Language: English&lt;br /&gt;
&lt;br /&gt;
;Profile last updated: 7th April 2021&lt;br /&gt;
&lt;br /&gt;
[[Category:OSGeo Charter Member]]&lt;br /&gt;
&lt;br /&gt;
[[Category:OSGeo Advocate]]&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=User:Stevenfeldman&amp;diff=126453</id>
		<title>User:Stevenfeldman</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=User:Stevenfeldman&amp;diff=126453"/>
		<updated>2021-04-07T09:46:02Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{OSGeo Member&lt;br /&gt;
|Name=Steven Feldman&lt;br /&gt;
|JobTitle=Principal&lt;br /&gt;
|Company=KnowWhere Consulting&lt;br /&gt;
|Country=UK&lt;br /&gt;
|City=London&lt;br /&gt;
|Coordinate=51.5073219, -0.1276474&lt;br /&gt;
|LocalChapter= [http://uk.osgeo.org OSGeo:UK]&lt;br /&gt;
|Website=https://www.knowwhereconsulting.co.uk/&lt;br /&gt;
|Photo=StevenFeldmanPic.jpg&lt;br /&gt;
|Info=Steven Feldman was Managing Director of GDC, a UK local government specialist and subsequently of MapInfo UK. He now mentors startups and advises businesses in the location space while focussing his spare time on Open Data and Open Source projects including the [http://www.osmgb.org.uk OSM-GB] project at the Nottingham Geospatial Institute.&lt;br /&gt;
&lt;br /&gt;
Steven is currently a strategic advisor to [https://astuntechnology.com Astun Technology], chairman of [https://geo.me geo.me Solutions], past chairman of [https://exprodat.com Exprodat Consulting] and  a board advisor at [https://www.opencagedata.com OpenCage Data].&lt;br /&gt;
&lt;br /&gt;
Steven was the Chair of the LOC for [http://2013.foss4g.org/ FOSS4G 2013]. He is a recent past chair the Conference Committee and is active in [http://uk.osgeo.org OSGeo:UK, the UK local chapter]&lt;br /&gt;
&lt;br /&gt;
Steven is a regular presenter on geo and open topics, some slide decks are [https://drive.google.com/drive/folders/18FLUY_t9VdQLGpwkYXabIh2y62aXDfX1?usp=sharing here]. He tends to tweet too much as [http://twitter.com/stevenfeldman @stevenfeldman]&lt;br /&gt;
}}&lt;br /&gt;
{{OSGeo Experience&lt;br /&gt;
|User=Yes&lt;br /&gt;
|Committee=Yes&lt;br /&gt;
|Board=No&lt;br /&gt;
|Coder=No&lt;br /&gt;
|Translate=No&lt;br /&gt;
|PSC=No&lt;br /&gt;
|ExBoard=No&lt;br /&gt;
|Charter=Yes&lt;br /&gt;
|Chair=No&lt;br /&gt;
|SolKatz=No&lt;br /&gt;
|Committer=No&lt;br /&gt;
}}&lt;br /&gt;
;Contact:&lt;br /&gt;
: Email: [https://knowwhereconsulting.co.uk/contact/ via KnowWhere]&lt;br /&gt;
: [https://twitter.com/stevenfeldman twitter]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
;Spoken Language: English&lt;br /&gt;
&lt;br /&gt;
;Profile last updated: 7th April 2021&lt;br /&gt;
&lt;br /&gt;
[[Category:OSGeo Charter Member]]&lt;br /&gt;
&lt;br /&gt;
[[Category:OSGeo Advocate]]&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=User:Stevenfeldman&amp;diff=126452</id>
		<title>User:Stevenfeldman</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=User:Stevenfeldman&amp;diff=126452"/>
		<updated>2021-04-07T09:43:37Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{OSGeo Member&lt;br /&gt;
|Name=Steven Feldman&lt;br /&gt;
|JobTitle=Principal&lt;br /&gt;
|Company=KnowWhere Consulting&lt;br /&gt;
|Country=UK&lt;br /&gt;
|City=London&lt;br /&gt;
|Coordinate=51.5073219, -0.1276474&lt;br /&gt;
|LocalChapter= [http://uk.osgeo.org OSGeo:UK]&lt;br /&gt;
|Website=https://www.knowwhereconsulting.co.uk/&lt;br /&gt;
|Photo=StevenFeldmanPic.jpg&lt;br /&gt;
|Info=Steven Feldman was Managing Director of GDC, a UK local government specialist and subsequently of MapInfo UK. He now mentors startups and advises businesses in the location space while focussing his spare time on Open Data and Open Source projects including the [http://www.osmgb.org.uk OSM-GB] project at the Nottingham Geospatial Institute.&lt;br /&gt;
&lt;br /&gt;
Steven is currently a strategic advisor to [https://astuntechnology.com Astun Technology], chairman of [https://geo.me geo.me Solutions], past chairman of [https://exprodat.com Exprodat Consulting] and  a board advisor at [https://www.opencagedata.com OpenCage Data].&lt;br /&gt;
&lt;br /&gt;
Steven was the Chair of the LOC for [http://2013.foss4g.org/ FOSS4G 2013]. He is a recent past chair the Conference Committee and is active in [http://uk.osgeo.org OSGeo:UK, the UK local chapter]&lt;br /&gt;
&lt;br /&gt;
Steven is a regular presenter on geo and open topics, some slide decks are [https://drive.google.com/drive/folders/18FLUY_t9VdQLGpwkYXabIh2y62aXDfX1?usp=sharing here]. He tends to tweet too much as [http://twitter.com/stevenfeldman @stevenfeldman]&lt;br /&gt;
}}&lt;br /&gt;
{{OSGeo Experience&lt;br /&gt;
|User=Yes&lt;br /&gt;
|Committee=Yes&lt;br /&gt;
|Board=No&lt;br /&gt;
|Coder=No&lt;br /&gt;
|Translate=No&lt;br /&gt;
|PSC=No&lt;br /&gt;
|ExBoard=No&lt;br /&gt;
|Charter=Yes&lt;br /&gt;
|Chair=No&lt;br /&gt;
|SolKatz=No&lt;br /&gt;
|Committer=No&lt;br /&gt;
}}&lt;br /&gt;
;Contact:&lt;br /&gt;
: Email: [https://knowwhereconsulting.co.uk/contact/ via KnowWhere]&lt;br /&gt;
: https://twitter.com/stevenfeldman twitter]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
;Spoken Language: English&lt;br /&gt;
&lt;br /&gt;
;Profile last updated: 7th April 2021&lt;br /&gt;
&lt;br /&gt;
[[Category:OSGeo Charter Member]]&lt;br /&gt;
&lt;br /&gt;
[[Category:OSGeo Advocate]]&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=User:Stevenfeldman&amp;diff=126451</id>
		<title>User:Stevenfeldman</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=User:Stevenfeldman&amp;diff=126451"/>
		<updated>2021-04-07T09:41:13Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{OSGeo Member&lt;br /&gt;
|Name=Steven Feldman&lt;br /&gt;
|JobTitle=Principal&lt;br /&gt;
|Company=KnowWhere Consulting&lt;br /&gt;
|Country=UK&lt;br /&gt;
|City=London&lt;br /&gt;
|Coordinate=51.5073219, -0.1276474&lt;br /&gt;
|LocalChapter= [http://uk.osgeo.org OSGeo:UK]&lt;br /&gt;
|Website=https://www.knowwhereconsulting.co.uk/&lt;br /&gt;
|Photo=StevenFeldmanPic.jpg&lt;br /&gt;
|Info=Steven Feldman was Managing Director of GDC, a UK local government specialist and subsequently of MapInfo UK. He now mentors startups and advises businesses in the location space while focussing his spare time on Open Data and Open Source projects including the [http://www.osmgb.org.uk OSM-GB] project at the Nottingham Geospatial Institute.&lt;br /&gt;
&lt;br /&gt;
Steven is currently a strategic advisor to [https://astuntechnology.com Astun Technology], chairman of [https://geo.me geo.me Solutions], past chairman of[https://exprodat.com Exprodat Consulting] and  a board advisor at [https://www.opencagedata.com OpenCage Data].&lt;br /&gt;
&lt;br /&gt;
Steven was the Chair of the LOC for [http://2013.foss4g.org/ FOSS4G 2013]. He is a recent past chair the Conference Committee and is treasurer of [http://uk.osgeo.org OSGeo:UK, the UK local chapter]&lt;br /&gt;
&lt;br /&gt;
Steven is a regular presenter on geo and open topics, some slide decks are [http://www.slideshare.net/stevenfeldman here]. He tends to tweet too much as [http://twitter.com/stevenfeldman @stevenfeldman]&lt;br /&gt;
}}&lt;br /&gt;
{{OSGeo Experience&lt;br /&gt;
|User=Yes&lt;br /&gt;
|Committee=Yes&lt;br /&gt;
|Board=No&lt;br /&gt;
|Coder=No&lt;br /&gt;
|Translate=No&lt;br /&gt;
|PSC=No&lt;br /&gt;
|ExBoard=No&lt;br /&gt;
|Charter=Yes&lt;br /&gt;
|Chair=No&lt;br /&gt;
|SolKatz=No&lt;br /&gt;
|Committer=No&lt;br /&gt;
}}&lt;br /&gt;
;Contact:&lt;br /&gt;
: Email: [https://knowwhereconsulting.co.uk/contact/ via KnowWhere]&lt;br /&gt;
: https://twitter.com/stevenfeldman twitter]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
;Spoken Language: English&lt;br /&gt;
&lt;br /&gt;
;Profile last updated: 7th April 2021&lt;br /&gt;
&lt;br /&gt;
[[Category:OSGeo Charter Member]]&lt;br /&gt;
&lt;br /&gt;
[[Category:OSGeo Advocate]]&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=User:Stevenfeldman&amp;diff=126450</id>
		<title>User:Stevenfeldman</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=User:Stevenfeldman&amp;diff=126450"/>
		<updated>2021-04-07T07:36:35Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{OSGeo Member&lt;br /&gt;
|Name=Steven Feldman&lt;br /&gt;
|JobTitle=Principal&lt;br /&gt;
|Company=KnowWhere Consulting&lt;br /&gt;
|Country=UK&lt;br /&gt;
|City=London&lt;br /&gt;
|Coordinate=51.5073219, -0.1276474&lt;br /&gt;
|LocalChapter= [http://uk.osgeo.org OSGeo:UK]&lt;br /&gt;
|Website=http://www.knowwhereconsulting.co.uk/&lt;br /&gt;
|Photo=StevenFeldmanPic.jpg&lt;br /&gt;
|Info=Steven Feldman was Managing Director of GDC, a UK local government specialist and subsequently of MapInfo UK. He now mentors startups and advises businesses in the location space while focussing his spare time on Open Data and Open Source projects including the [http://www.osmgb.org.uk OSM-GB] project at the Nottingham Geospatial Institute.&lt;br /&gt;
&lt;br /&gt;
Steven is currently a strategic advisor to [http://astuntechnology.com Astun Technology], chairman of [http://geo.me geo.me Solutions], past chairman of[http://exprodat.com Exprodat Consulting] and  a board advisor at [http://www.opencagedata.com OpenCage Data].&lt;br /&gt;
&lt;br /&gt;
Steven was the Chair of the LOC for [http://2013.foss4g.org/ FOSS4G 2013]. He is a recent past chair the Conference Committee and is treasurer of [http://uk.osgeo.org OSGeo:UK, the UK local chapter]&lt;br /&gt;
&lt;br /&gt;
Steven is a regular presenter on geo and open topics, some slide decks are [http://www.slideshare.net/stevenfeldman here]. He tends to tweet too much as [http://twitter.com/stevenfeldman @stevenfeldman]&lt;br /&gt;
}}&lt;br /&gt;
{{OSGeo Experience&lt;br /&gt;
|User=Yes&lt;br /&gt;
|Committee=Yes&lt;br /&gt;
|Board=No&lt;br /&gt;
|Coder=No&lt;br /&gt;
|Translate=No&lt;br /&gt;
|PSC=No&lt;br /&gt;
|ExBoard=No&lt;br /&gt;
|Charter=Yes&lt;br /&gt;
|Chair=No&lt;br /&gt;
|SolKatz=No&lt;br /&gt;
|Committer=No&lt;br /&gt;
}}&lt;br /&gt;
;Contact:&lt;br /&gt;
: Email: [http://knowwhereconsulting.co.uk/contact/ via KnowWhere]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
;Spoken Language: English&lt;br /&gt;
&lt;br /&gt;
;Profile last updated: 7th April 2021&lt;br /&gt;
&lt;br /&gt;
[[Category:OSGeo Charter Member]]&lt;br /&gt;
&lt;br /&gt;
[[Category:OSGeo Advocate]]&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=User:Stevenfeldman&amp;diff=126449</id>
		<title>User:Stevenfeldman</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=User:Stevenfeldman&amp;diff=126449"/>
		<updated>2021-04-07T07:35:07Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{OSGeo Member&lt;br /&gt;
|Name=Steven Feldman&lt;br /&gt;
|JobTitle=Principal&lt;br /&gt;
|Company=KnowWhere Consulting&lt;br /&gt;
|Country=UK&lt;br /&gt;
|City=London&lt;br /&gt;
|Coordinate=51.5073219, -0.1276474&lt;br /&gt;
|LocalChapter= [http://uk.osgeo.org OSGeo:UK]&lt;br /&gt;
|Website=http://www.knowwhereconsulting.co.uk/&lt;br /&gt;
|Photo=StevenFeldmanPic.jpg&lt;br /&gt;
|Info=Steven Feldman was Managing Director of GDC, a UK local government specialist and subsequently of MapInfo UK. He now mentors startups and advises businesses in the location space while focussing his spare time on Open Data and Open Source projects including the [http://www.osmgb.org.uk OSM-GB] project at the Nottingham Geospatial Institute.&lt;br /&gt;
&lt;br /&gt;
Steven is currently a strategic advisor to [http://astuntechnology.com Astun Technology], chairman of [http://geo.me geo.me Solutions], past chairman of[http://exprodat.com Exprodat Consulting] and  a board advisor at [http://www.opencagedata.com OpenCage Data].&lt;br /&gt;
&lt;br /&gt;
Steven was the Chair of the LOC for [http://2013.foss4g.org/ FOSS4G 2013]. He is a recent past chair the Conference Committee and is treasurer of [http://uk.osgeo.org OSGeo:UK, the UK local chapter]&lt;br /&gt;
&lt;br /&gt;
Steven is a regular presenter on geo and open topics, some slide decks are [http://www.slideshare.net/stevenfeldman here]. He tends to tweet too much as [http://twitter.com/stevenfeldman @stevenfeldman]&lt;br /&gt;
}}&lt;br /&gt;
{{OSGeo Experience&lt;br /&gt;
|User=Yes&lt;br /&gt;
|Committee=Yes&lt;br /&gt;
|Board=No&lt;br /&gt;
|Coder=No&lt;br /&gt;
|Translate=No&lt;br /&gt;
|PSC=No&lt;br /&gt;
|ExBoard=No&lt;br /&gt;
|Charter=Yes&lt;br /&gt;
|Chair=No&lt;br /&gt;
|SolKatz=No&lt;br /&gt;
|Committer=No&lt;br /&gt;
}}&lt;br /&gt;
;Contact:&lt;br /&gt;
: Email: [http://knowwhereconsulting.co.uk/contact/ via KnowWhere]&lt;br /&gt;
: Skype: stevenfeldman2638&lt;br /&gt;
&lt;br /&gt;
;Spoken Language: English&lt;br /&gt;
&lt;br /&gt;
;Profile last updated: 12th August, 2014&lt;br /&gt;
&lt;br /&gt;
[[Category:OSGeo Charter Member]]&lt;br /&gt;
&lt;br /&gt;
[[Category:OSGeo Advocate]]&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=User:Stevenfeldman&amp;diff=126448</id>
		<title>User:Stevenfeldman</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=User:Stevenfeldman&amp;diff=126448"/>
		<updated>2021-04-07T07:34:19Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{OSGeo Member&lt;br /&gt;
|Name=Steven Feldman&lt;br /&gt;
|JobTitle=Principal&lt;br /&gt;
|Company=KnowWhere Consulting&lt;br /&gt;
|Country=UK&lt;br /&gt;
|City=London&lt;br /&gt;
|Coordinate=51.5073219, -0.1276474&lt;br /&gt;
|LocalChapter= [http://uk.osgeo.org OSGeo:UK]&lt;br /&gt;
|Website=http://www.knowwhereconsulting.co.uk/&lt;br /&gt;
|Photo=StevenFeldmanPic.jpg&lt;br /&gt;
|Info=Steven Feldman was Managing Director of GDC, a UK local government specialist and subsequently of MapInfo UK. He now mentors startups and advises businesses in the location space while focussing his spare time on Open Data and Open Source projects including the [http://www.osmgb.org.uk OSM-GB] project at the Nottingham Geospatial Institute and [http://www.taarifa.org Taarifa]. &lt;br /&gt;
&lt;br /&gt;
Steven is currently a strategic advisor to [http://astuntechnology.com Astun Technology], chairman of [http://geo.me geo.me Solutions], past chairman of[http://exprodat.com Exprodat Consulting] and  a board advisor at [http://www.opencagedata.com OpenCage Data].&lt;br /&gt;
&lt;br /&gt;
Steven was the Chair of the LOC for [http://2013.foss4g.org/ FOSS4G 2013]. He is a recent past chair the Conference Committee and is treasurer of [http://uk.osgeo.org OSGeo:UK, the UK local chapter]&lt;br /&gt;
&lt;br /&gt;
Steven is a regular presenter on geo and open topics, some slide decks are [http://www.slideshare.net/stevenfeldman here]. He tends to tweet too much as [http://twitter.com/stevenfeldman @stevenfeldman]&lt;br /&gt;
}}&lt;br /&gt;
{{OSGeo Experience&lt;br /&gt;
|User=Yes&lt;br /&gt;
|Committee=Yes&lt;br /&gt;
|Board=No&lt;br /&gt;
|Coder=No&lt;br /&gt;
|Translate=No&lt;br /&gt;
|PSC=No&lt;br /&gt;
|ExBoard=No&lt;br /&gt;
|Charter=Yes&lt;br /&gt;
|Chair=No&lt;br /&gt;
|SolKatz=No&lt;br /&gt;
|Committer=No&lt;br /&gt;
}}&lt;br /&gt;
;Contact:&lt;br /&gt;
: Email: [http://knowwhereconsulting.co.uk/contact/ via KnowWhere]&lt;br /&gt;
: Skype: stevenfeldman2638&lt;br /&gt;
&lt;br /&gt;
;Spoken Language: English&lt;br /&gt;
&lt;br /&gt;
;Profile last updated: 12th August, 2014&lt;br /&gt;
&lt;br /&gt;
[[Category:OSGeo Charter Member]]&lt;br /&gt;
&lt;br /&gt;
[[Category:OSGeo Advocate]]&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Board_Meeting_2021-03-29&amp;diff=126389</id>
		<title>Board Meeting 2021-03-29</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Board_Meeting_2021-03-29&amp;diff=126389"/>
		<updated>2021-03-28T17:11:45Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This board meeting is '''scheduled Monday 29 March 2021''' at [https://www.timeanddate.com/worldclock/meetingdetails.html?year=2021&amp;amp;month=03&amp;amp;day=29&amp;amp;hour=16&amp;amp;min=0&amp;amp;sec=0&amp;amp;p1=250&amp;amp;p2=26&amp;amp;p3=49&amp;amp;p4=155&amp;amp;p5=217&amp;amp;p6=312 16:00 UTC] through [https://meet.jit.si/OsgeoBoard Jitsi], a record of motions is preserved on [https://www.loomio.org/g/kdSmIwxu/osgeo-board loomio] and actions on [https://git.osgeo.org/gitea/osgeo/todo/issues osgeo todo] issue tracker.&lt;br /&gt;
&lt;br /&gt;
== Agenda ==&lt;br /&gt;
&lt;br /&gt;
=== Current items ===&lt;br /&gt;
&lt;br /&gt;
# ''roll call''&lt;br /&gt;
#* ''appoint meeting chair, meeting scribe/secretary''&lt;br /&gt;
# ''Review and approve past minutes''&lt;br /&gt;
#* [[Board_Meeting_2021-02-22]]&lt;br /&gt;
# Markettig Committee Astrid Contact board about communication with Partners from MOUs&lt;br /&gt;
# Set up [https://opencollective.com/become-a-host OpenCollective] fiscal host for projects to facilitate donations&lt;br /&gt;
# other fiscal alternatives (gdal)&lt;br /&gt;
# proposal to become a Participating Organisation with the [https://www.earthobservations.org/pos.php Group on Earth Observation] (Steven Feldman)&lt;br /&gt;
# add your topic here&lt;br /&gt;
== Minutes ==&lt;br /&gt;
&lt;br /&gt;
* Presiding:&lt;br /&gt;
* Scribing:&lt;br /&gt;
* Attending:&lt;br /&gt;
&lt;br /&gt;
== Actions ==&lt;br /&gt;
* https://git.osgeo.org/gitea/osgeo/todo/issues/&lt;br /&gt;
&lt;br /&gt;
== IRC Log ==&lt;br /&gt;
&lt;br /&gt;
* http://irclogs.geoapt.com/osgeo/%23osgeo.2021-03-22.log&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Board]]&lt;br /&gt;
[[Category:Board Meetings 2021]]&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Board_Meeting_2021-03-29&amp;diff=126387</id>
		<title>Board Meeting 2021-03-29</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Board_Meeting_2021-03-29&amp;diff=126387"/>
		<updated>2021-03-27T14:07:36Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This board meeting is '''scheduled Monday 29 March 2021''' at [https://www.timeanddate.com/worldclock/meetingdetails.html?year=2021&amp;amp;month=03&amp;amp;day=29&amp;amp;hour=16&amp;amp;min=0&amp;amp;sec=0&amp;amp;p1=250&amp;amp;p2=26&amp;amp;p3=49&amp;amp;p4=155&amp;amp;p5=217&amp;amp;p6=312 16:00 UTC] through [https://meet.jit.si/OsgeoBoard Jitsi], a record of motions is preserved on [https://www.loomio.org/g/kdSmIwxu/osgeo-board loomio] and actions on [https://git.osgeo.org/gitea/osgeo/todo/issues osgeo todo] issue tracker.&lt;br /&gt;
&lt;br /&gt;
== Agenda ==&lt;br /&gt;
&lt;br /&gt;
=== Current items ===&lt;br /&gt;
&lt;br /&gt;
# ''roll call''&lt;br /&gt;
#* ''appoint meeting chair, meeting scribe/secretary''&lt;br /&gt;
# ''Review and approve past minutes''&lt;br /&gt;
#* [[Board_Meeting_2021-02-22]]&lt;br /&gt;
# Markettig Committee Astrid Contact board about communication with Partners from MOUs&lt;br /&gt;
# Set up [https://opencollective.com/become-a-host OpenCollective] fiscal host for projects to facilitate donations&lt;br /&gt;
# other fiscal alternatives (gdal)&lt;br /&gt;
# proposal to become a Participating Organisation with the [https://www.earthobservations.org/pos.php Group on Earth Observation]&lt;br /&gt;
# add your topic here&lt;br /&gt;
== Minutes ==&lt;br /&gt;
&lt;br /&gt;
* Presiding:&lt;br /&gt;
* Scribing:&lt;br /&gt;
* Attending:&lt;br /&gt;
&lt;br /&gt;
== Actions ==&lt;br /&gt;
* https://git.osgeo.org/gitea/osgeo/todo/issues/&lt;br /&gt;
&lt;br /&gt;
== IRC Log ==&lt;br /&gt;
&lt;br /&gt;
* http://irclogs.geoapt.com/osgeo/%23osgeo.2021-03-22.log&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Board]]&lt;br /&gt;
[[Category:Board Meetings 2021]]&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Board_Meeting_2021-03-29&amp;diff=126386</id>
		<title>Board Meeting 2021-03-29</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Board_Meeting_2021-03-29&amp;diff=126386"/>
		<updated>2021-03-27T13:20:23Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This board meeting is '''scheduled Monday 29 March 2021''' at [https://www.timeanddate.com/worldclock/meetingdetails.html?year=2021&amp;amp;month=03&amp;amp;day=29&amp;amp;hour=16&amp;amp;min=0&amp;amp;sec=0&amp;amp;p1=250&amp;amp;p2=26&amp;amp;p3=49&amp;amp;p4=155&amp;amp;p5=217&amp;amp;p6=312 16:00 UTC] through [https://meet.jit.si/OsgeoBoard Jitsi], a record of motions is preserved on [https://www.loomio.org/g/kdSmIwxu/osgeo-board loomio] and actions on [https://git.osgeo.org/gitea/osgeo/todo/issues osgeo todo] issue tracker.&lt;br /&gt;
&lt;br /&gt;
== Agenda ==&lt;br /&gt;
&lt;br /&gt;
=== Current items ===&lt;br /&gt;
&lt;br /&gt;
# ''roll call''&lt;br /&gt;
#* ''appoint meeting chair, meeting scribe/secretary''&lt;br /&gt;
# ''Review and approve past minutes''&lt;br /&gt;
#* [[Board_Meeting_2021-02-22]]&lt;br /&gt;
# Markettig Committee Astrid Contact board about communication with Partners from MOUs&lt;br /&gt;
# Set up [https://opencollective.com/become-a-host OpenCollective] fiscal host for projects to facilitate donations&lt;br /&gt;
# other fiscal alternatives (gdal)&lt;br /&gt;
# add your topic here&lt;br /&gt;
# proposal to become a Participating Organisation with the [https://www.earthobservations.org/pos.php Group on Earth Observation]&lt;br /&gt;
&lt;br /&gt;
== Minutes ==&lt;br /&gt;
&lt;br /&gt;
* Presiding:&lt;br /&gt;
* Scribing:&lt;br /&gt;
* Attending:&lt;br /&gt;
&lt;br /&gt;
== Actions ==&lt;br /&gt;
* https://git.osgeo.org/gitea/osgeo/todo/issues/&lt;br /&gt;
&lt;br /&gt;
== IRC Log ==&lt;br /&gt;
&lt;br /&gt;
* http://irclogs.geoapt.com/osgeo/%23osgeo.2021-03-22.log&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Board]]&lt;br /&gt;
[[Category:Board Meetings 2021]]&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Board_Meeting_2021-03-29&amp;diff=126385</id>
		<title>Board Meeting 2021-03-29</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Board_Meeting_2021-03-29&amp;diff=126385"/>
		<updated>2021-03-27T13:18:52Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This board meeting is '''scheduled Monday 29 March 2021''' at [https://www.timeanddate.com/worldclock/meetingdetails.html?year=2021&amp;amp;month=03&amp;amp;day=29&amp;amp;hour=16&amp;amp;min=0&amp;amp;sec=0&amp;amp;p1=250&amp;amp;p2=26&amp;amp;p3=49&amp;amp;p4=155&amp;amp;p5=217&amp;amp;p6=312 16:00 UTC] through [https://meet.jit.si/OsgeoBoard Jitsi], a record of motions is preserved on [https://www.loomio.org/g/kdSmIwxu/osgeo-board loomio] and actions on [https://git.osgeo.org/gitea/osgeo/todo/issues osgeo todo] issue tracker.&lt;br /&gt;
&lt;br /&gt;
== Agenda ==&lt;br /&gt;
&lt;br /&gt;
=== Current items ===&lt;br /&gt;
&lt;br /&gt;
# ''roll call''&lt;br /&gt;
#* ''appoint meeting chair, meeting scribe/secretary''&lt;br /&gt;
# ''Review and approve past minutes''&lt;br /&gt;
#* [[Board_Meeting_2021-02-22]]&lt;br /&gt;
# Markettig Committee Astrid Contact board about communication with Partners from MOUs&lt;br /&gt;
# Set up [https://opencollective.com/become-a-host OpenCollective] fiscal host for projects to facilitate donations&lt;br /&gt;
# other fiscal alternatives (gdal)&lt;br /&gt;
# add your topic here&lt;br /&gt;
# proposal to become a Participating Organisation with the Group on Earth Observation (GEO) [https://www.earthobservations.org/pos.php GEO]&lt;br /&gt;
&lt;br /&gt;
== Minutes ==&lt;br /&gt;
&lt;br /&gt;
* Presiding:&lt;br /&gt;
* Scribing:&lt;br /&gt;
* Attending:&lt;br /&gt;
&lt;br /&gt;
== Actions ==&lt;br /&gt;
* https://git.osgeo.org/gitea/osgeo/todo/issues/&lt;br /&gt;
&lt;br /&gt;
== IRC Log ==&lt;br /&gt;
&lt;br /&gt;
* http://irclogs.geoapt.com/osgeo/%23osgeo.2021-03-22.log&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Board]]&lt;br /&gt;
[[Category:Board Meetings 2021]]&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Board_Meeting_2021-03-29&amp;diff=126384</id>
		<title>Board Meeting 2021-03-29</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Board_Meeting_2021-03-29&amp;diff=126384"/>
		<updated>2021-03-27T13:17:28Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This board meeting is '''scheduled Monday 29 March 2021''' at [https://www.timeanddate.com/worldclock/meetingdetails.html?year=2021&amp;amp;month=03&amp;amp;day=29&amp;amp;hour=16&amp;amp;min=0&amp;amp;sec=0&amp;amp;p1=250&amp;amp;p2=26&amp;amp;p3=49&amp;amp;p4=155&amp;amp;p5=217&amp;amp;p6=312 16:00 UTC] through [https://meet.jit.si/OsgeoBoard Jitsi], a record of motions is preserved on [https://www.loomio.org/g/kdSmIwxu/osgeo-board loomio] and actions on [https://git.osgeo.org/gitea/osgeo/todo/issues osgeo todo] issue tracker.&lt;br /&gt;
&lt;br /&gt;
== Agenda ==&lt;br /&gt;
&lt;br /&gt;
=== Current items ===&lt;br /&gt;
&lt;br /&gt;
# ''roll call''&lt;br /&gt;
#* ''appoint meeting chair, meeting scribe/secretary''&lt;br /&gt;
# ''Review and approve past minutes''&lt;br /&gt;
#* [[Board_Meeting_2021-02-22]]&lt;br /&gt;
# Markettig Committee Astrid Contact board about communication with Partners from MOUs&lt;br /&gt;
# Set up [https://opencollective.com/become-a-host OpenCollective] fiscal host for projects to facilitate donations&lt;br /&gt;
# other fiscal alternatives (gdal)&lt;br /&gt;
# add your topic here&lt;br /&gt;
# proposal to become a Participating Organisation with the Group on Earth Observation (GEO) [https://www.earthobservations.org/pos.php]&lt;br /&gt;
&lt;br /&gt;
== Minutes ==&lt;br /&gt;
&lt;br /&gt;
* Presiding:&lt;br /&gt;
* Scribing:&lt;br /&gt;
* Attending:&lt;br /&gt;
&lt;br /&gt;
== Actions ==&lt;br /&gt;
* https://git.osgeo.org/gitea/osgeo/todo/issues/&lt;br /&gt;
&lt;br /&gt;
== IRC Log ==&lt;br /&gt;
&lt;br /&gt;
* http://irclogs.geoapt.com/osgeo/%23osgeo.2021-03-22.log&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Board]]&lt;br /&gt;
[[Category:Board Meetings 2021]]&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Board_Meeting_2020-07-29&amp;diff=125120</id>
		<title>Board Meeting 2020-07-29</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Board_Meeting_2020-07-29&amp;diff=125120"/>
		<updated>2020-07-28T17:00:55Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: added FOSS4G 2022 CfP&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This board meeting is '''scheduled Wednesday 29 July 2020''' at [https://www.timeanddate.com/worldclock/meetingdetails.html?year=2020&amp;amp;month=07&amp;amp;day=29&amp;amp;hour=16&amp;amp;min=0&amp;amp;sec=0&amp;amp;p1=256&amp;amp;p2=286&amp;amp;p3=49&amp;amp;p4=269&amp;amp;p5=250&amp;amp;p6=37 16:00 UTC] through [https://meet.jit.si/OsgeoBoard Jitsi], a record of motions is preserved on [https://www.loomio.org/g/kdSmIwxu/osgeo-board loomio] and actions on [https://git.osgeo.org/gitea/osgeo/todo/issues osgeo todo] issue tracker.&lt;br /&gt;
&lt;br /&gt;
== Agenda ==&lt;br /&gt;
&lt;br /&gt;
=== Current items ===&lt;br /&gt;
&lt;br /&gt;
# ''roll call''&lt;br /&gt;
#* ''appoint meeting chair, meeting scribe/secretary''&lt;br /&gt;
# Feedback from FOSS4GUK 2020 [https://lists.osgeo.org/pipermail/board/2020-July/012714.html]&lt;br /&gt;
# Feedback from FOSS4G Calgary 2020 LOC [https://lists.osgeo.org/pipermail/board/2020-June/012706.html]&lt;br /&gt;
# Discussion on content for Call for Proposals for FOSS4G 2022&lt;br /&gt;
&lt;br /&gt;
== Minutes ==&lt;br /&gt;
&lt;br /&gt;
* Presiding:&lt;br /&gt;
* Scribing:&lt;br /&gt;
* Attending:&lt;br /&gt;
* Guests:&lt;br /&gt;
&lt;br /&gt;
[[Category:Board]]&lt;br /&gt;
[[Category:Board Meetings 2020]]&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=FOSS4G_Handbook&amp;diff=124963</id>
		<title>FOSS4G Handbook</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=FOSS4G_Handbook&amp;diff=124963"/>
		<updated>2020-07-04T12:31:14Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: /* Lessons Learned */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;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.&lt;br /&gt;
&lt;br /&gt;
= About FOSS4G =&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
FOSS4G includes one annual global event which rotates around the world, as well as a number of regional events which follow similar principles.&lt;br /&gt;
&lt;br /&gt;
;See Also&lt;br /&gt;
: [https://wiki.osgeo.org/wiki/FOSS4G FOSS4G History]&lt;br /&gt;
: [https://docs.google.com/spreadsheets/d/1BpkO5WOFQ_DZEWNMLj_hAhEre0m0io_j-JGf7geAW5Y/edit?hl=en_GB#gid=57 FOSS4G Metrics]&lt;br /&gt;
&lt;br /&gt;
= Editing this document =&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
The process to follow in updating this wiki is:&lt;br /&gt;
* Feel free to make trivial tweaks to grammar and syntax.&lt;br /&gt;
* If you would like to introduce a new idea, maybe add a new section, or improve an old section:&lt;br /&gt;
** Raise your suggestion on the [http://lists.osgeo.org/mailman/listinfo/conference_dev OSGeo Conference] email list.&lt;br /&gt;
** Once a rough consensus has been reached on the list, you may then update the Handbook with the collective wisdom of the list.&lt;br /&gt;
** If writing a new section, consider starting the section with: &amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;Draft, awaiting review&amp;lt;/font&amp;gt;&lt;br /&gt;
** After updating your text, notify the list again to give others the opportunity to review and tweak.&lt;br /&gt;
&lt;br /&gt;
= Section Writing Guide =&lt;br /&gt;
&amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;Draft, awaiting review&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The first sentence(s) of a section should describe the meaning of the heading. Eg, if this section is on &amp;quot;Birds of a Feather&amp;quot;, 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.''&lt;br /&gt;
&lt;br /&gt;
; Relevance:&lt;br /&gt;
: International FOSS4G: [Mandatory, Recommended, Optional, Not Relevant]&lt;br /&gt;
: Regional FOSS4G: [Mandatory, Recommended, Optional, Not Relevant]&lt;br /&gt;
: FOSS4G stream / Local Event: [Mandatory, Recommended, Optional, Not Relevant]&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
* Key success factors&lt;br /&gt;
* Things that can go wrong, with optional brief examples&lt;br /&gt;
* List of considerations and why choose one consideration over another&lt;br /&gt;
* List of steps to follow&lt;br /&gt;
* Organizations or people to contact to coordinate with&lt;br /&gt;
* Links to external documents, such as a Google Docs spreadsheet&lt;br /&gt;
&lt;br /&gt;
; See Also:&lt;br /&gt;
:* Where relevant, finish with a list of links to web pages for further reading. E.g.&lt;br /&gt;
:* [http://wiki.osgeo.org/wiki/FOSS4G_2009_Lessons_Learned#Birds_of_a_Feather FOSS4G 2009 Birds of Feather Lessons Learned]&lt;br /&gt;
&lt;br /&gt;
=Preparing FOSS4G RFP=&lt;br /&gt;
&amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;Draft, awaiting review&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Selection of the international FOSS4G venue, involves two stages, a &amp;quot;Letter of Intent&amp;quot; (LOI) followed by a full &amp;quot;Request for Proposal&amp;quot; (RFQ). Only cities which attract two or more committee member votes from the LOI move onto the RFQ.&lt;br /&gt;
&lt;br /&gt;
; Relevance:&lt;br /&gt;
: International FOSS4G: Mandatory&lt;br /&gt;
: Regional FOSS4G: Optional&lt;br /&gt;
: FOSS4G stream / Local Event: Usually Not Relevant&lt;br /&gt;
&lt;br /&gt;
The process for preparing an RFP for the annual FOSS4G is:&lt;br /&gt;
* Copy the previous year's FOSS4G RFP directory to the next year, as per: http://svn.osgeo.org/osgeo/foss4g/rfp/&lt;br /&gt;
* 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.&lt;br /&gt;
* Get in touch with the conference_dev and teams from previous year or two and get their feedback on the process for RFP changes&lt;br /&gt;
* 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)&lt;br /&gt;
* Update doc appropriately&lt;br /&gt;
* Stub out Wiki pages using the skeletons from previous years and the dates you already put into the doc&lt;br /&gt;
* Get someone to review your changes&lt;br /&gt;
* Announce&lt;br /&gt;
&lt;br /&gt;
; See Also:&lt;br /&gt;
:* http://svn.osgeo.org/osgeo/foss4g/rfp/&lt;br /&gt;
&lt;br /&gt;
= Lessons Learned =&lt;br /&gt;
&amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;Draft, awaiting review&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
It is highly valuable to future conferences to collect the wisdom gained from prior conferences. &lt;br /&gt;
&lt;br /&gt;
; Relevance:&lt;br /&gt;
: International FOSS4G: StronglyRecommended&lt;br /&gt;
: Regional FOSS4G: Recommended&lt;br /&gt;
: FOSS4G stream / Local Event: Optional&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
In 2020 after the cancellation of the global FOSS4G in Calgary and the European FOSS4G in Valmiera, the OSGeo:UK chapter hosted a global one day online event. Their lessons learnt from this first online FOSS4G are [[FOSS4GUK 2020 Online - Lessons Learnt|here]]&lt;br /&gt;
&lt;br /&gt;
*[[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&lt;br /&gt;
&lt;br /&gt;
; See Also:&lt;br /&gt;
*[[FOSS4G 2016 Lessons Learned|2016]]&lt;br /&gt;
*[[FOSS4G 2015 Lessons Learned|2015]] &lt;br /&gt;
*[[FOSS4G 2014 Lessons Learned|2014]] &lt;br /&gt;
*[[FOSS4G2013_Reflections_by_the_LOC|2013]] &lt;br /&gt;
*[[FOSS4G 2012 Lessons Learned|2012]] &lt;br /&gt;
*[[FOSS4G 2011 Lessons Learned|2011]] &lt;br /&gt;
*[[FOSS4G 2010 Lessons Learned|2010]] &lt;br /&gt;
*[[FOSS4G 2009 Lessons Learned|2009]] &lt;br /&gt;
*[[FOSS4G2008 Lessons Learned|2008]] &lt;br /&gt;
*[[FOSS4G2007 Lessons Learned|2007]]&lt;br /&gt;
&lt;br /&gt;
= Marketing =&lt;br /&gt;
&lt;br /&gt;
== Press Releases ==&lt;br /&gt;
&amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;Draft, awaiting review&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You should send out public announcements about your conference, especially around conference milestones. &lt;br /&gt;
&lt;br /&gt;
; Relevance:&lt;br /&gt;
: International FOSS4G: Required&lt;br /&gt;
: Regional FOSS4G: Recommended&lt;br /&gt;
: FOSS4G stream / Local Event: Recommended&lt;br /&gt;
&lt;br /&gt;
Make regular use the OSGeo News feed: &lt;br /&gt;
* initial announcement&lt;br /&gt;
* Call for Papers&lt;br /&gt;
* Start of registration, end of early booking approaching &lt;br /&gt;
* Program published&lt;br /&gt;
* etc.&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Work out where you will send your announcements. It should include:&lt;br /&gt;
* You should submit to [http://www.osgeo.org/content/news/submit_news.html OSGeo Announcements] for inclusion on the OSGeo web site &lt;br /&gt;
* [http://lists.osgeo.org/mailman/listinfo/discuss OSGeo Discuss]&lt;br /&gt;
* Twitter&lt;br /&gt;
* A blog feed into [http://planet.osgeo.org/ Planet OSGeo]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
; See Also:&lt;br /&gt;
:* http://wiki.osgeo.org/wiki/FOSS4G_2009_Press_Releases&lt;br /&gt;
:* http://wiki.osgeo.org/wiki/FOSS4G_2009_Lessons_Learned#Press_Releases&lt;br /&gt;
&lt;br /&gt;
== twitter ==&lt;br /&gt;
* FOSS4G runs the [[https://twitter.com/foss4g FOSS4G twitter account]]&lt;br /&gt;
* The account will be passed to the new LOC each year after the conference&lt;br /&gt;
* Use #FOSS4G or #FOSS4G201x in your tweets (maybe also #FOSS4G?????????????)&lt;br /&gt;
* [[https://tweetdeck.twitter.com/ Tweetdeck]] can be used to get a better overview about tweets, notifications, retweets... &lt;br /&gt;
* [[http://buffer.com Buffer]] can be used to define tweets in advance and let them be posted at a defined time&lt;br /&gt;
* NodeXL shows you the tweet statistics in a graph&lt;br /&gt;
&lt;br /&gt;
== Photos ==&lt;br /&gt;
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.&lt;br /&gt;
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])&lt;br /&gt;
&lt;br /&gt;
* [https://www.flickr.com/groups/foss4g/ FOSS4G Group] on Flickr&lt;br /&gt;
&lt;br /&gt;
==Event Listings==&lt;br /&gt;
&amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;Draft, awaiting review&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The event should be added to event listings.&lt;br /&gt;
&lt;br /&gt;
; Relevance:&lt;br /&gt;
: International FOSS4G: [Mandatory]&lt;br /&gt;
: Regional FOSS4G: [Recommended]&lt;br /&gt;
: FOSS4G stream / Local Event: [Recommended]&lt;br /&gt;
&lt;br /&gt;
Relevant Lists include:&lt;br /&gt;
* http://www.osgeo.org/events&lt;br /&gt;
* http://wiki.osgeo.org/wiki/Global_conferences_overview&lt;br /&gt;
* https://wiki.osgeo.org/wiki/Live_GIS_History&lt;br /&gt;
&lt;br /&gt;
; See Also:&lt;br /&gt;
:* &lt;br /&gt;
&lt;br /&gt;
==FOSS4G Branding==&lt;br /&gt;
&amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;Draft, awaiting review&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
FOSS4G is the acronym used to describe events which are predominantly about &amp;quot;Free and Open Source Software for Geospatial&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
; Relevance:&lt;br /&gt;
: International FOSS4G: [Mandatory]&lt;br /&gt;
: Regional FOSS4G: [Mandatory]&lt;br /&gt;
: FOSS4G stream / Local Event: [Mandatory]&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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).&lt;br /&gt;
&lt;br /&gt;
Use of the name &amp;quot;FOSS4G&amp;quot; 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 &amp;quot;FOSS4G&amp;quot; name should request permission to do so from the conference committee. Permission will be granted if the event being described is predominantly (say &amp;gt;90%) about Free and Open Source Software for Geospatial and promotes OSGeo.&lt;br /&gt;
&lt;br /&gt;
; See Also:&lt;br /&gt;
:* http://wiki.osgeo.org/wiki/FOSS4G&lt;br /&gt;
:* http://wiki.osgeo.org/wiki/FOSS4G#Using_the_Name_FOSS4G&lt;br /&gt;
:* [[FOSS4G_Handbook#Regional_and_Local_FOSS4G_selection]]&lt;br /&gt;
:* http://wiki.osgeo.org/wiki/Official_OSGeo_Event_Policy&lt;br /&gt;
&lt;br /&gt;
==OSGeo Branding==&lt;br /&gt;
&amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;Draft, awaiting review&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
FOSS4G events should suitably acknowledge the OSGeo foundation in promotion material.&lt;br /&gt;
This would typically include:&lt;br /&gt;
* the OSGeo logo being included on the website with words similar to &amp;quot;presented by OSGeo&amp;quot; and a link back to the OSGeo web site.&lt;br /&gt;
* presentation(s) by organisers (and others) should reference OSGeo&lt;br /&gt;
&lt;br /&gt;
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&lt;br /&gt;
&lt;br /&gt;
; Relevance:&lt;br /&gt;
: International FOSS4G: [Mandatory]&lt;br /&gt;
: Regional FOSS4G: [Mandatory]&lt;br /&gt;
: FOSS4G stream / Local Event: [Recommended]&lt;br /&gt;
&lt;br /&gt;
== Logo ==&lt;br /&gt;
[[File:OSGeo-Ribbon.jpg|thumb|right|alt=OSgeo Ribbon|OSgeo Ribbon.]]&lt;br /&gt;
&lt;br /&gt;
The FOSS4G logo for the international conference has to include elements of the OSGeo / FOSS4G &amp;quot;ribbon&amp;quot; as can be seen in all previous conference logos: http://foss4g.org/, and should also include themes for the location of the current event.&lt;br /&gt;
&lt;br /&gt;
; Relevance:&lt;br /&gt;
: International FOSS4G: [Mandatory]&lt;br /&gt;
: Regional FOSS4G: [Optional]&lt;br /&gt;
: FOSS4G stream / Local Event: [Not Applicable]&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
Start on the logo asap as you need it for other early stage documents like the sponsorship prospectus.&lt;br /&gt;
&lt;br /&gt;
=City and Date Selection=&lt;br /&gt;
&lt;br /&gt;
== International FOSS4G Rotation ==&lt;br /&gt;
The International FOSS4G event rotates around the world, and cities compete to be selected to host the event, as described in the RFP process.&lt;br /&gt;
&lt;br /&gt;
; Relevance:&lt;br /&gt;
: International FOSS4G: Mandatory&lt;br /&gt;
: Regional FOSS4G: Not Relevant&lt;br /&gt;
: FOSS4G stream / Local Event: Not Relevant&lt;br /&gt;
&lt;br /&gt;
The regions FOSS4G rotates through are:&lt;br /&gt;
* Europe&lt;br /&gt;
* North America&lt;br /&gt;
* Rest of world&lt;br /&gt;
This is caveatted by the OSGeo Conference committee feeling confident that the proposed city/region will attract the majority of the international FOSS4G audience.&lt;br /&gt;
&lt;br /&gt;
So our rotation policy is:&lt;br /&gt;
&lt;br /&gt;
# Strong preference is given to the region which hasn't had FOSS4G for 2 years&lt;br /&gt;
# We next consider the region which had FOSS4G 2 years ago&lt;br /&gt;
# Only as a last resort would we consider a region which had FOSS4G last year&lt;br /&gt;
&lt;br /&gt;
Prior International FOSS4G event locations have been:&lt;br /&gt;
* [http://2020.foss4g.org/ 2020]: Calgary, Alberta, Canada&lt;br /&gt;
* [http://2019.foss4g.org/ 2019]: Bucharest, Romania&lt;br /&gt;
* [http://2018.foss4g.org/ 2018]: Dar es Salaam, Tanzania, Africa&lt;br /&gt;
* [http://2017.foss4g.org/ 2017]: Boston, MA, USA&lt;br /&gt;
* [http://2016.foss4g.org/ 2016]: Bonn, Germany&lt;br /&gt;
* [http://2015.foss4g.org/ 2015]: Seoul, South Korea&lt;br /&gt;
* [http://2014.foss4g.org/ 2014]: Portland, Oregon, USA&lt;br /&gt;
* [http://2013.foss4g.org/ 2013]: Nottingham, United Kingdom&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://2012.foss4g.org/ 2012]: Beijing, China (cancelled)&amp;lt;/s&amp;gt;&lt;br /&gt;
* [http://2011.foss4g.org/ 2011]: Denver, United States&lt;br /&gt;
* [http://2010.foss4g.org/ 2010]: Barcelona, Spain&lt;br /&gt;
* [http://2009.foss4g.org/ 2009]: Sydney, Australia&lt;br /&gt;
* [http://2008.foss4g.org/ 2008]: Cape Town, South Africa&lt;br /&gt;
* [http://2007.foss4g.org/ 2007]: Victoria, Canada&lt;br /&gt;
* [http://2006.foss4g.org/ 2006]: Lausanne, Switzerland&lt;br /&gt;
* 2005: Minneapolis, United States&lt;br /&gt;
* [http://www.ces.iisc.ernet.in/energy/water/paper/fossgrdss/conference.htm 2004]: Bangkok, Thailand&lt;br /&gt;
&lt;br /&gt;
; See Also:&lt;br /&gt;
:* http://www.osgeo.org/conference/rfp&lt;br /&gt;
:* http://svn.osgeo.org/osgeo/foss4g/&lt;br /&gt;
:* Many FOSS4G regional and related conferences are listed at: http://wiki.osgeo.org/wiki/Live_GIS_History&lt;br /&gt;
:* Conference committee approval of this rotation policy: http://lists.osgeo.org/pipermail/conference_dev/2013-May/002107.html&lt;br /&gt;
&lt;br /&gt;
== Selecting locations which align with OSGeo principles ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
; Relevance:&lt;br /&gt;
: International FOSS4G: Recommended&lt;br /&gt;
: Regional FOSS4G: Recommended&lt;br /&gt;
: FOSS4G stream / Local Event: Not Relevant&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
; See Also:&lt;br /&gt;
:* [https://www.osgeo.org/code_of_conduct/ Code of Conduct]&lt;br /&gt;
&lt;br /&gt;
==Regional and Local FOSS4G selection==&lt;br /&gt;
&amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;Draft, awaiting review&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Location and date selection of FOSS4G regional and local events should be coordinated with other FOSS4G events.&lt;br /&gt;
&lt;br /&gt;
Regional and Local FOSS4G events are encouraged&lt;br /&gt;
; Relevance:&lt;br /&gt;
: International FOSS4G: Not Relevant&lt;br /&gt;
: Regional FOSS4G: Recommended&lt;br /&gt;
: FOSS4G stream / Local Event: Recommended&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
* Have at least one representative subscribe the the conference_dev email list.&lt;br /&gt;
* 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).&lt;br /&gt;
* Network with others within the region. Discuss options of merging potential FOSS4G events and/or ensuring dates and locations don't conflict.&lt;br /&gt;
* Once location and date have been selected, list the event at http://www.osgeo.org/events.&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
; See Also:&lt;br /&gt;
:* http://wiki.osgeo.org/wiki/FOSS4G_2012_Lessons_Learned#Competing_regional_conferences&lt;br /&gt;
&lt;br /&gt;
=Schedule=&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
; Relevance&lt;br /&gt;
: International FOSS4G: Mandatory&lt;br /&gt;
: Regional FOSS4G: Mandatory&lt;br /&gt;
: FOSS4G stream / Local Event: Highly Recommended&lt;br /&gt;
&lt;br /&gt;
When planning an event:&lt;br /&gt;
* 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.&lt;br /&gt;
* Tailor the plan such that it aligns with the goals for your event&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
; See Also:&lt;br /&gt;
:* [https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdGdIbnY3SEZNUHp3NHdTZnlLZC1rbWc#gid=0 Generic FOSS4G Planning Schedule]&lt;br /&gt;
&lt;br /&gt;
= Infrastructure and archiving =&lt;br /&gt;
&amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;Draft, awaiting review&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Background:&lt;br /&gt;
* 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.&lt;br /&gt;
* There may be some opportunity to reuse some of these systems.&lt;br /&gt;
* 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/&lt;br /&gt;
&lt;br /&gt;
; Relevance:&lt;br /&gt;
: International FOSS4G: Mandatory&lt;br /&gt;
: Regional FOSS4G: Optional?&lt;br /&gt;
: FOSS4G stream / Local Event: Optional?&lt;br /&gt;
&lt;br /&gt;
== LOC email list ==&lt;br /&gt;
&amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;Draft, awaiting review&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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&lt;br /&gt;
&lt;br /&gt;
; Relevance:&lt;br /&gt;
: International FOSS4G: Mandatory&lt;br /&gt;
: Regional FOSS4G: Recommended&lt;br /&gt;
: FOSS4G stream / Local Event: Optional/Not Relevant&lt;br /&gt;
&lt;br /&gt;
; See Also:&lt;br /&gt;
:* 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&lt;br /&gt;
&lt;br /&gt;
== Website ==&lt;br /&gt;
&amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;Draft, awaiting review&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Background:&lt;br /&gt;
* This is just a start at the archiving portion.  More needs to be added about the requirements for selection, use, etc&lt;br /&gt;
* FOSS4G websites are archived in a basic form at yyyy.foss4g.org&lt;br /&gt;
* Some website platforms might have export options&lt;br /&gt;
* wget could be an archiving method too, perhaps something along the lines of:&lt;br /&gt;
 wget --mirror --convert-links --backup-converted --html-extension&lt;br /&gt;
* HTTrack may be the preferred tool&lt;br /&gt;
&lt;br /&gt;
; Relevance:&lt;br /&gt;
: International FOSS4G: Mandatory&lt;br /&gt;
: Regional FOSS4G: Optional?&lt;br /&gt;
: FOSS4G stream / Local Event: Optional?&lt;br /&gt;
&lt;br /&gt;
= Diversity =&lt;br /&gt;
== Code of Conduct ==&lt;br /&gt;
&amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;Draft, awaiting review&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
; Relevance:&lt;br /&gt;
: International FOSS4G: Mandatory.&lt;br /&gt;
: Regional FOSS4G: Highly recommended.&lt;br /&gt;
: FOSS4G stream / Local Event: Recommended if not already covered by the main conference.&lt;br /&gt;
== Child Friendly Policy ==&lt;br /&gt;
&lt;br /&gt;
Making a conference child friendly makes it easier for primary care givers (often mothers), the opportunity to present.&lt;br /&gt;
&lt;br /&gt;
; Relevance:&lt;br /&gt;
: International FOSS4G: Optional&lt;br /&gt;
: Regional FOSS4G: Optional&lt;br /&gt;
: FOSS4G stream / Local Event: Optional&lt;br /&gt;
&lt;br /&gt;
This requires managing an effective balance between the competing priorities of:&lt;br /&gt;
&lt;br /&gt;
* High cost of dedicated childcare.&lt;br /&gt;
* Variability and unpredictability of different aged children.&lt;br /&gt;
* Retaining a professional conference environment.&lt;br /&gt;
* Respecting needs of children, parents, and conference participants.&lt;br /&gt;
* Making our conference accessible to a diverse audience, which includes those responsible for children.&lt;br /&gt;
&lt;br /&gt;
FOSS4G Oceania introduced a Child Friendly Policy in 2018 which can be used as inspiration.&lt;br /&gt;
&lt;br /&gt;
; See Also:&lt;br /&gt;
:* https://foss4g-oceania.org/child-friendly-conference&lt;br /&gt;
:* http://cameronshorter.blogspot.com/2018/09/child-friendly-conferences.html&lt;br /&gt;
&lt;br /&gt;
= Streaming and archiving presentations and keynotes =&lt;br /&gt;
&amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;Draft, awaiting review&amp;lt;/font&amp;gt;&lt;br /&gt;
* Most FOSS4G's since 2011 (needs checking) have recorded presentations and made them available after the event. &lt;br /&gt;
*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.&lt;br /&gt;
* Recording and publishing helps to spread knowledge and awareness of OSGeo software&lt;br /&gt;
&lt;br /&gt;
== Videos ==&lt;br /&gt;
&amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;Draft, awaiting review&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Videoing presentations extends the reach of conference presentations to a much wider audience, but is logistically challenging, and/or expensive.&lt;br /&gt;
&lt;br /&gt;
; Relevance:&lt;br /&gt;
: International FOSS4G: Strongly Recommended&lt;br /&gt;
: Regional FOSS4G: Recommended&lt;br /&gt;
: FOSS4G stream / Local Event: Optional&lt;br /&gt;
&lt;br /&gt;
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?&lt;br /&gt;
&lt;br /&gt;
There are also &amp;quot;scrappy&amp;quot; alternatives to get cheaper, poor quality content. Potentially ask attendees to record with mobile phones are upload to a central source.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
; See Also:&lt;br /&gt;
:* [https://lists.osgeo.org/pipermail/conference_dev/2018-September/004890.html Email list thread on videoing]&lt;br /&gt;
&lt;br /&gt;
=== Vimeo ===&lt;br /&gt;
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..&lt;br /&gt;
* the account will be passed every year after the conference to the next team&lt;br /&gt;
* [https://vimeo.com/foss4g FOSS4G Vimeo account]&lt;br /&gt;
* Make sure, that you add enough metadata when you publish your video&lt;br /&gt;
&lt;br /&gt;
There is a video landing page which refers to all videos from the last conferences at [http://video.foss4g.org http://video.foss4g.org]&lt;br /&gt;
&lt;br /&gt;
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].&lt;br /&gt;
&lt;br /&gt;
=== TIB ===&lt;br /&gt;
* [[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&lt;br /&gt;
* Read [[FOSS for GIS video tutorials and screencasts|how to publish videos at TIB]].&lt;br /&gt;
&lt;br /&gt;
=Finances=&lt;br /&gt;
==Guarantees==&lt;br /&gt;
&amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;Draft, awaiting review&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The OSGeo foundation can be approached to provide financial guarantees for major FOSS4G events.&lt;br /&gt;
&lt;br /&gt;
; Relevance:&lt;br /&gt;
: International FOSS4G: Recommended&lt;br /&gt;
: Regional FOSS4G: Optional&lt;br /&gt;
: FOSS4G stream / Local Event: Not Relevant&lt;br /&gt;
&lt;br /&gt;
As per our board priorities:&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
To support and enable these conferences, OSGeo will endevour to retain sufficient capital to offer such guarantees for any FOSS4G event requesting it. &amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;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.&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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. &amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;Cameron Shorter: Noted that legal body need not be the LOC. For FOSS4G 2009, OSGeo signed a contract directly with the PCO.&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;What follows is a draft set of conditions suggested by [[User:Stevenfeldman | Steven Feldman]] for further comment:&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#Any FOSS4G seeking OSGeo’s financial backing should provide a financial plan, which includes:&lt;br /&gt;
## Initial advance(s) required and timing&lt;br /&gt;
## Potential loss through cancellation at different stages&lt;br /&gt;
## Potential loss if conference goes ahead but attendance is less than target&lt;br /&gt;
## &amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;Cameron Shorter added: Financial reporting schedule, noting how often reports will be provided, and by who (typically by a PCO).&amp;lt;/font&amp;gt;&lt;br /&gt;
## &amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;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.&amp;lt;/font&amp;gt;&lt;br /&gt;
#OSGeo will confirm the maximum level that it will underwrite&lt;br /&gt;
#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&lt;br /&gt;
#The Conference Committee will require a member to join the LOC with financial oversight of expenditure, forecasts and risks. &amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;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]] &amp;lt;/font&amp;gt;&lt;br /&gt;
#The Conference Committee will need to continuously review financial risk and may require changes to the financial and operational plans of an event. &amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;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]] &amp;lt;/font&amp;gt;&lt;br /&gt;
#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.&lt;br /&gt;
#The LOC agrees to remit xx% of any surplus to OSGeo to support future events and other OSGeo activities &amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;(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)&amp;lt;/font&amp;gt;&lt;br /&gt;
#OSGeo will need to draft a legal agreement with the LOC that sets out these terms&lt;br /&gt;
&lt;br /&gt;
; See Also:&lt;br /&gt;
:* Board priorities: http://wiki.osgeo.org/wiki/Board_Meeting_2013-02-26#Conferences_and_related_events&lt;br /&gt;
&lt;br /&gt;
==FOSS4G nonprofit tax status==&lt;br /&gt;
&amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;Draft, awaiting review&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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.  &lt;br /&gt;
&lt;br /&gt;
; Relevance:&lt;br /&gt;
: International FOSS4G: &lt;br /&gt;
: Regional FOSS4G: &lt;br /&gt;
: FOSS4G stream / Local Event: &lt;br /&gt;
&lt;br /&gt;
; This is just a place holder to be filled out later once things are determined, see Also:&lt;br /&gt;
:* Conference list: http://lists.osgeo.org/pipermail/conference_dev/2013-July/002303.html&lt;br /&gt;
&lt;br /&gt;
== Budget ==&lt;br /&gt;
; See Also&lt;br /&gt;
:* [https://docs.google.com/spreadsheets/d/1YdFNuBNaJK2XeA-bs1vU24VA1Qv9HpN8rLs30D9_0zg/edit#gid=1040179171 FOSS4G 2013 final accounts]&lt;br /&gt;
&lt;br /&gt;
=Metrics=&lt;br /&gt;
&amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;Draft, awaiting review&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Past FOSS4G metrics are very valuable for planning future FOSS4G events, and should be collected for all events.&lt;br /&gt;
&lt;br /&gt;
; Relevance:&lt;br /&gt;
: International FOSS4G: Mandatory&lt;br /&gt;
: Regional FOSS4G: Recommended&lt;br /&gt;
: FOSS4G stream / Local Event: Optional&lt;br /&gt;
&lt;br /&gt;
Key questions that we wish to ask of our metrics:&lt;br /&gt;
# How many people are likely to come from a future FOSS4G event in region X?&lt;br /&gt;
# 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?&lt;br /&gt;
# In lead up, when do sponsors sign up?&lt;br /&gt;
# Schedule and workshop planners wish to understand the technical expertise of participants. What is the percentage of OSGeo newbies (requiring &amp;quot;Introduction to ...&amp;quot; presentation/workshop).&lt;br /&gt;
# Schedule and workshop planners wish to understand which presenters and topics were popular.&lt;br /&gt;
# 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.&lt;br /&gt;
# How much sponsorship should we expect? Where in the world did previous sponsors come from?&lt;br /&gt;
# What is the most effective way to market FOSS4G? How did people hear about FOSS4G?&lt;br /&gt;
&lt;br /&gt;
Key metrics we wish to collect from attendees:&lt;br /&gt;
# Registration date&lt;br /&gt;
# City, State, Country&lt;br /&gt;
# Sponsor name, amount, sign up date&lt;br /&gt;
# Information Source: Past attendee,Friend/colleague,E-mail list,Web badge on open source site,Grapevine,Internet Search,Web advertisement,Magazine advertisement&lt;br /&gt;
# Job Description 1:C-Level Executive,Manager,Consultant,Programmer,Scientist,Educator,Mysterious&lt;br /&gt;
#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&lt;br /&gt;
# Reason For Attending: The Technical Networking,The Workshops &amp;amp; Technical Sessions,The Beer,The Sales Networking,Something Else Altogether&lt;br /&gt;
&lt;br /&gt;
Metrics to collect about presentations:&lt;br /&gt;
# How many people were in the room of each presentation?&lt;br /&gt;
# Optional: How interesting was the topic?&lt;br /&gt;
# Optional: How good was the speaker?&lt;br /&gt;
&lt;br /&gt;
; See Also:&lt;br /&gt;
:* Collated metrics from past global FOSS4G events: https://docs.google.com/spreadsheets/d/1ux_hFq-C165140ZD48RRImPTHSpXj42OG3nBr9cyZYo/edit#gid=1782600951&lt;br /&gt;
* Older version of the same metrics: https://docs.google.com/spreadsheet/ccc?key=0Al9zh8DjmU_RdEZoOUtSeVZRVWtKQzV6R2N5ekdSdlE#gid=57&lt;br /&gt;
:* 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&lt;br /&gt;
:* FOSS4G 2013 Metrics: http://2013.foss4g.org/Surveys/delegate.html&lt;br /&gt;
&lt;br /&gt;
=Travel Grants=&lt;br /&gt;
The travel grant programme is run by FOSs4G's Conference committee. The first TGP was run in 2017, see [[FOSS4G_Travel_Grant_Programme_2017]]&lt;br /&gt;
&lt;br /&gt;
This is the old draft, the procedure was based on: [[Draft FOSS4G Travel Grants]]&lt;br /&gt;
&lt;br /&gt;
=OSGeo Branding=&lt;br /&gt;
&amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;Draft, awaiting review&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
FOSS4G conferences are expected to promote the OSGeo Foundation at events.&lt;br /&gt;
&lt;br /&gt;
; Relevance:&lt;br /&gt;
: International FOSS4G: Mandatory&lt;br /&gt;
: Regional FOSS4G: Recommeded&lt;br /&gt;
: FOSS4G stream / Local Event: Recommended&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&lt;br /&gt;
* Include a presentation on an OSGeo topic, often as a keynote. You can find good local presenters at [[OSGeo_Advocate]].&lt;br /&gt;
* 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]]. &lt;br /&gt;
* Include an OSGeo logo included in the program and on the conference website.&lt;br /&gt;
* 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&lt;br /&gt;
&lt;br /&gt;
; See Also:&lt;br /&gt;
:* [[OSGeo_Advocate]]&lt;br /&gt;
:* http://wiki.osgeo.org/wiki/Live_GIS_Disc#Including_OSGeo-Live_at_your_event&lt;br /&gt;
:* [[Exhibition_Pack]]&lt;br /&gt;
&lt;br /&gt;
=Time Frame=&lt;br /&gt;
&lt;br /&gt;
=Program=&lt;br /&gt;
&lt;br /&gt;
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):&lt;br /&gt;
* 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.&lt;br /&gt;
* 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.&lt;br /&gt;
* Three days of Main Conference&lt;br /&gt;
** 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.&lt;br /&gt;
** Approximately five parallel tracks of presentations, with each presentation consisting of a 20-25 minute talk, 5 minutes of Q&amp;amp;A, and 5 minutes of transition time between talks. Attended by 500-900 people, depending on conference attendance.&lt;br /&gt;
** 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.  &lt;br /&gt;
** 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 &amp;quot;Gala Dinner&amp;quot; but can be quite informal. &lt;br /&gt;
** [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.&lt;br /&gt;
** 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. &lt;br /&gt;
** Birds of a Feather Sessions. Held after the days presentations, groups self-organize to discuss topics of common interest.&lt;br /&gt;
** A lunch time allocated for poster creators to stand next to their posters and talk about them.&lt;br /&gt;
* OSGeo Directors Face-to-Face Meeting. Held before or after the conference, in a board room or meeting room provided by the conference organizers.&lt;br /&gt;
&lt;br /&gt;
; Relevance:&lt;br /&gt;
: International FOSS4G: Recommended&lt;br /&gt;
: Regional FOSS4G: Recommended&lt;br /&gt;
: FOSS4G stream / Local Event: Optional&lt;br /&gt;
&lt;br /&gt;
; See Also:&lt;br /&gt;
:* RFP: http://svn.osgeo.org/osgeo/foss4g/rfp/&lt;br /&gt;
:* http://2013.foss4g.org/programme/&lt;br /&gt;
:* http://2011.foss4g.org/program&lt;br /&gt;
&lt;br /&gt;
== Workshops ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;Draft, awaiting review&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
; Relevance:&lt;br /&gt;
: International FOSS4G: Mandatory&lt;br /&gt;
: Regional FOSS4G: Recommended&lt;br /&gt;
: FOSS4G stream / Local Event: Optional&lt;br /&gt;
&lt;br /&gt;
; Workshop Call for Proposal&lt;br /&gt;
The Call for Proposal can be aligned with the regular presentation Call for Papers (see below).&lt;br /&gt;
&lt;br /&gt;
; Workshop Selection&lt;br /&gt;
The workshops selection starts with a Call for Proposal. Anybody can submit a workshop proposal. The selection follows a few clear rules: &lt;br /&gt;
* Graduated OSGeo projects get precedence over incubating projects over others. &lt;br /&gt;
* Each graduated OSGeo project will receive one slot provided there are enough in total. If not first come first serve. &lt;br /&gt;
** Graduated OSGeo projects have to submit a workshop proposal just like anybody else. &lt;br /&gt;
** 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. &lt;br /&gt;
** If a graduated project does not convincingly confirm their participation slots are filled up by other active projects.&lt;br /&gt;
** Workshop leader/s have to register until x weeks before the conference.&lt;br /&gt;
* Individuals and organizations are encouraged to collaborate on joint workshops.&lt;br /&gt;
* Ideally a few slots should be reserved for workshops that may be not tech related for example for the Education and Data committees.  &lt;br /&gt;
&lt;br /&gt;
Final adjudication lies with the LOC!!!&lt;br /&gt;
&lt;br /&gt;
=== Workshop Venue ===&lt;br /&gt;
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 &amp;quot;strange&amp;quot; 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. &lt;br /&gt;
&lt;br /&gt;
=== Software Environment ===&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Presentations ==&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
=== Call for Papers ===&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=== Submission of papers ===&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=== Strategic Talks ===&lt;br /&gt;
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 &amp;quot;bleeding edge&amp;quot; and are bored by annually recurring talks about things well known. But the FOSS4G conference also attracts a large group of &amp;quot;Open Source Newbies&amp;quot; who have no or very little understanding of the Open Source geospatial environment and ecosystem. &lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=== Selection and Evaluation of the Presentations ===&lt;br /&gt;
'''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. ''&lt;br /&gt;
&lt;br /&gt;
==== Step 1: Community Voting ====&lt;br /&gt;
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: &lt;br /&gt;
* 0 = no interest&lt;br /&gt;
* 1 = medium interest&lt;br /&gt;
* 2 = high interest&lt;br /&gt;
&lt;br /&gt;
==== Step 2: Program Committee Voting ====&lt;br /&gt;
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 &lt;br /&gt;
&lt;br /&gt;
==== Step 3: Program Compilation ====&lt;br /&gt;
One topic that is easily forgotten is a general introduction to Open Source development, licensing and associated business models (see also &amp;quot;Strategic Talks&amp;quot;). 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: &lt;br /&gt;
# Introduction to Open source and the OSGeo Foundation&lt;br /&gt;
# Business models and the &amp;quot;way of Open Source&amp;quot;&lt;br /&gt;
# Tech talks&lt;br /&gt;
# Use cases&lt;br /&gt;
&lt;br /&gt;
===Classification of Papers in Sessions===&lt;br /&gt;
===Details about Speakers and Publication of the Program===&lt;br /&gt;
&lt;br /&gt;
== Academic Track ==&lt;br /&gt;
[[FOSS4G Notes on Academic Track]]&lt;br /&gt;
==Community Sessions==&lt;br /&gt;
==Birds of a Feather Sessions (BoF)==&lt;br /&gt;
&amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;Draft, awaiting review&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
FOSS4G conferences provide a great opportunity for like minded people to network and brainstorm ideas, and &amp;quot;Birds of a Feather&amp;quot; meetings provide a good forum for this.&lt;br /&gt;
&lt;br /&gt;
Conference organisers can delegate specific timeslots. Breakfasts and dinners are often good for these events.&lt;br /&gt;
&lt;br /&gt;
Typically you create a wiki page for participants to  define a &amp;quot;Birds of a Feather&amp;quot; session which are available for participants to choose. The wiki typically includes:&lt;br /&gt;
* Title&lt;br /&gt;
* Proposed topics&lt;br /&gt;
* Timeslot&lt;br /&gt;
* People (people self register by adding their names)&lt;br /&gt;
These sessions can also be written on butcher paper or white boards on walls around the conference somewhere.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
; Relevance:&lt;br /&gt;
: International FOSS4G: Recommended&lt;br /&gt;
: Regional FOSS4G: Recommeded&lt;br /&gt;
: FOSS4G stream / Local Event: Optional&lt;br /&gt;
&lt;br /&gt;
==Posters==&lt;br /&gt;
==Conference Opening==&lt;br /&gt;
== Keynotes ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
== Closing Session ==&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
=== Drawing ===&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=Social Events=&lt;br /&gt;
==Unofficial start==&lt;br /&gt;
==Social Event==&lt;br /&gt;
==Members' Meeting==&lt;br /&gt;
=Exhibition=&lt;br /&gt;
* Event should provide an OSGeo booth - read more at [[Operate OSGeo Booth]]&lt;br /&gt;
* Event should include [[OSGeo Advocate]] speaker who would present on an aspect of OSGeo&lt;br /&gt;
* The OSGeo advocate(s) are expected to coordinate and man the OSGeo booth&lt;br /&gt;
* The OSGeo [[Local Chapters]] are strongly encouraged to hang out at the OSGeo booth&lt;br /&gt;
&lt;br /&gt;
=Sponsors=&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;font color= &amp;quot;red&amp;quot;&amp;gt; Draft by Steven Feldman 2019-06 needs further discussion &amp;lt;/font color&amp;gt;&lt;br /&gt;
&lt;br /&gt;
It is almost certain that you will need to obtain sponsorship to make your FOSS4G financially viable and affordable for delegates. These tips may help you to generate sponsorship income and to provide a good experience for your sponsors which hopefully will encourage them to sponsor future events.&lt;br /&gt;
&lt;br /&gt;
==Get Sponsors on board early==&lt;br /&gt;
&lt;br /&gt;
The sooner you have your sponsors on board the better, they provide some financial security for your event, early cash flow to cover your deposits etc and a lot of publicity opportunities to promote the event.&lt;br /&gt;
* Plan your sponsorship tiers, charges, what benefits sponsors get at each level (remember to cost in any free conference passes that you are offering)&lt;br /&gt;
* Prepare a sponsorship brochure or page on your web site as early as you can&lt;br /&gt;
* Delegate at least one member of your LOC to be responsible for liaison with sponsors&lt;br /&gt;
* Make a list of sponsor targets and include the sponsors from the previous 2 or 3 FOSS4Gs&lt;br /&gt;
* Start your sponsorship campaign as early as you can, if your event is running in August or September you should aim to start your campaign in October or November of the previous year.&lt;br /&gt;
* Consider offering an early bird discount on your sponsorship rates (say 10% if you confirm and pay by 28th February)&lt;br /&gt;
* Consider asking for a voluntary donation from sponsors to the Travel Grant programme (e.g. give back their early bird discount) and offer extra recognition for this.&lt;br /&gt;
* Wait to announce sponsors or display their logos on your web site until they have paid their sponsorship invoices&lt;br /&gt;
&lt;br /&gt;
==Looking after sponsors==&lt;br /&gt;
&lt;br /&gt;
Your relationship with sponsors does not end when you receive their money! That is just the beginning. Consider your sponsors as customers of your FOSS4G and look after them.&lt;br /&gt;
* Designate a member of the team and possibly someone from your PCO to be the point of contact with sponsors&lt;br /&gt;
* Communicate with sponsors regularly giving them updates on speakers, side events etc&lt;br /&gt;
* Look for win win opportunities with sponsors e.g. facilitating new product launches, competitions and other activities&lt;br /&gt;
* If you are running an exhibition space be clear about what facilities you are providing and what the sponsor must do (and by when!)&lt;br /&gt;
* Consider running a Sponsors reception or breakfast as a way of saying thank you to sponsors. Remember to ask any OSGeo board members who will be at the event to participate.&lt;br /&gt;
&lt;br /&gt;
=Media Sponsors=&lt;br /&gt;
=Participant Involvement=&lt;br /&gt;
&lt;br /&gt;
== Privacy Statement ==&lt;br /&gt;
Please consider adding something along the lines of: &lt;br /&gt;
&lt;br /&gt;
 '' by submitting your email address you consent to us sharing your details ''&lt;br /&gt;
 '' for the purpose of keeping you informed of future similar events. You can  ''&lt;br /&gt;
 '' unsubscribe from these communications at anytime using the unsubscribe links provided.''&lt;br /&gt;
&lt;br /&gt;
==Visa and invitation letter==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Registration==&lt;br /&gt;
==Printed Program==&lt;br /&gt;
==Bags==&lt;br /&gt;
==T Shirt==&lt;br /&gt;
== OSGeo-Live ==&lt;br /&gt;
* [http://live.osgeo.org OSGeo Live]&lt;br /&gt;
* The OSGeo-Live team that provides an image of a collection of over 50 software projects and data and tutorials every 6 months&lt;br /&gt;
* The OSGeo-live team prepares a version before FOSS4G that can be used at the conference in the workshops, at presentation notebooks &amp;amp; and can be given away to the delegates as bootable USB drives. This is a great opportunity to spread OSGeo software and promote OSGeo!&lt;br /&gt;
* The OSGeo-Live team adds OSM data from the region where FOSS4G takes place (e.g. data from Bonn was added in 2016)&lt;br /&gt;
* The OSGeo-live team can add your FOSS4G-Logo or material on the image&lt;br /&gt;
* The OSGeo-Live team will help you with USB and image - please contact them on the mailing list&lt;br /&gt;
* Get information about the OSGeo-Live team [https://wiki.osgeo.org/wiki/Live_GIS_Disc here]&lt;br /&gt;
* 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)&lt;br /&gt;
&lt;br /&gt;
==Location, Directions==&lt;br /&gt;
==Hotels==&lt;br /&gt;
==Other local information==&lt;br /&gt;
== Internet Access ==&lt;br /&gt;
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 &amp;quot;tech-events&amp;quot; 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. &lt;br /&gt;
&lt;br /&gt;
=== Ports ===&lt;br /&gt;
All ports should be open. This includes the lower levels for SSH, FTP, etc. but also &amp;quot;odd&amp;quot; ports like 6667 and neighboring for IRC, etc.&lt;br /&gt;
* FTP (20 and 21)&lt;br /&gt;
* SSH (22)&lt;br /&gt;
* TELNET (23)&lt;br /&gt;
* SMTP (25)&lt;br /&gt;
* IMAP (143, 456, 465, 587, 993, ++)&lt;br /&gt;
* SSL (443) and HTTP (80)&lt;br /&gt;
* TCP ports 6660–6669, 7000&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==Cloakroom==&lt;br /&gt;
==Proceedings==&lt;br /&gt;
&lt;br /&gt;
=On Site: Avoid waste and CO2 footprint=&lt;br /&gt;
&amp;lt;font color=&amp;quot;red&amp;quot;&amp;gt;Draft, awaiting review&amp;lt;/font&amp;gt;&lt;br /&gt;
&lt;br /&gt;
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:&lt;br /&gt;
&lt;br /&gt;
* avoid single way dishes and silverware and other one-way stuff like drinking bottles&lt;br /&gt;
* think about having a non-printed program&lt;br /&gt;
* ask sponsors not to bring too much material and/or only material printed on recycled material in an ecological manner&lt;br /&gt;
* offer a link to a CO2-compensating company, e.g. atmosfair, oeko-fair&lt;br /&gt;
* verify to buy T-Shirts based on fair-trade with ecological backgrounds&lt;br /&gt;
* reduce cooling down by air-conditioners &lt;br /&gt;
* .. (more proposals here)&lt;br /&gt;
&lt;br /&gt;
If possible, inform your attendees about your means to avoid CO2 emission and reduction of waste and ask them to co-ordinate.&lt;br /&gt;
&lt;br /&gt;
=Premises=&lt;br /&gt;
&lt;br /&gt;
=survey participants=&lt;br /&gt;
=See Also=&lt;br /&gt;
*[[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&lt;br /&gt;
*[[FOSS4G 2016 Lessons Learned|2016]]&lt;br /&gt;
*[[FOSS4G 2015 Lessons Learned|2015]] &lt;br /&gt;
*[[FOSS4G 2014 Lessons Learned|2014]] &lt;br /&gt;
*[[FOSS4G2013_Reflections_by_the_LOC|2013]] &lt;br /&gt;
*[[FOSS4G 2012 Lessons Learned|2012]] &lt;br /&gt;
*[[FOSS4G 2011 Lessons Learned|2011]] &lt;br /&gt;
*[[FOSS4G 2010 Lessons Learned|2010]] &lt;br /&gt;
*[[FOSS4G 2009 Lessons Learned|2009]] &lt;br /&gt;
*[[FOSS4G2008 Lessons Learned|2008]] &lt;br /&gt;
*[[FOSS4G2007 Lessons Learned|2007]]&lt;br /&gt;
* [http://www.fossgis.de/wiki/Handbuch German FOSSGIS Handbook in German], and an [http://arnulf.us/publications/fossgis_handbook.html English translation]&lt;br /&gt;
* FOSS4G Request for Proposal (RFP) documents: http://svn.osgeo.org/osgeo/foss4g/&lt;br /&gt;
&lt;br /&gt;
Howtos from related conferences:&lt;br /&gt;
* [http://wiki.linux.org.au/LCA_HOWTO Linux Australia Conference Howto]&lt;br /&gt;
* [http://www.ecoop.org/resources/HowTo.pdf ECOOP Conference Howto]&lt;br /&gt;
&lt;br /&gt;
[[Category:FOSS4G]]&lt;br /&gt;
[[Category:Events]]&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124870</id>
		<title>FOSS4GUK 2020 Online - Lessons Learnt</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124870"/>
		<updated>2020-06-23T16:26:06Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: /* Recording and publishing */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''This is a draft at the moment!'''&lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
&lt;br /&gt;
[https://uk.osgeo.org/foss4gukonline2020/ FOSS4GUK 2020 Online] was hosted by the [https://uk.osgeo.org OSGeo:UK] committee on 17th June 2020 from 9.00am to 17.30pm UTC+1&lt;br /&gt;
&lt;br /&gt;
The event was free to attend with all of the costs (see below) funded from OSGeo:UK reserves. &lt;br /&gt;
&lt;br /&gt;
=== Delegates ===&lt;br /&gt;
&lt;br /&gt;
* 1,000 people registered&lt;br /&gt;
* We estimate that between 500 and 600 attended&lt;br /&gt;
* Maximum number online at any time was 460, minimum was 205&lt;br /&gt;
* Delegates from 77 countries&lt;br /&gt;
** 48% from GB, 8% US, 4% India&lt;br /&gt;
&lt;br /&gt;
[[File:FOSS4GUK Attendee Countries.png|frameless]]&lt;br /&gt;
&lt;br /&gt;
=== [https://uk.osgeo.org/foss4gukonline2020/programme.html Programme] ===&lt;br /&gt;
&lt;br /&gt;
* 3 streams running for the whole day (except during keynotes)&lt;br /&gt;
** 2 keynotes&lt;br /&gt;
** 29 talks and demos&lt;br /&gt;
** 4 Lightning talks&lt;br /&gt;
* 38 Speakers (10 women)&lt;br /&gt;
* Coffee bar stream where delegates could hang out and chat (not heavily used)&lt;br /&gt;
&lt;br /&gt;
=== Finances ===&lt;br /&gt;
* The only costs were the fees for the zoom account for 1 month: £198&lt;br /&gt;
* Delegate donations:&lt;br /&gt;
** OSGeo:UK 63 individual donations - gross £1,810, net after Paypal fees £1,744 (as of 2020-06-20)&lt;br /&gt;
** MapAction ?&lt;br /&gt;
&lt;br /&gt;
== Feedback ==&lt;br /&gt;
&lt;br /&gt;
As of 2020-06-22 we had 210 feedback responses:&lt;br /&gt;
* 95% rated the event experience very good or excellent&lt;br /&gt;
* 93% were happy with the technology platform&lt;br /&gt;
* 27% attended for the whole day, 27% attended 7-11 sessions, 45% attended 2-6 sessions&lt;br /&gt;
* 16% used the coffee bar&lt;br /&gt;
* 47% of respondents (but not attendees) made a donation to OSGeo:UK (34%) or MapAction (13%). The average donation was ca £20&lt;br /&gt;
[[File:FOSS4GUK Satisfaction.png|frameless]]&lt;br /&gt;
[[File:FOSS4GUK Technology satisfaction.png|frameless]]&lt;br /&gt;
[[File:FOSS4GUK No of sessions attended.png|frameless]]&lt;br /&gt;
&lt;br /&gt;
== Tech and tools ==&lt;br /&gt;
&lt;br /&gt;
=== Choice of video conferencing platform ===&lt;br /&gt;
&lt;br /&gt;
==== We considered ====&lt;br /&gt;
&lt;br /&gt;
* webex (we had an offer of a free account from a sponsor) - problems with audio, uncertain linux support, limit on numbers&lt;br /&gt;
* hopin.to - a virtual conference application, unfortunately the demo the we attended was not successful and we did not feel comfortable taking the risk on a new service but it looks promising for the future&lt;br /&gt;
* several other services that did not seem to fit our needs&lt;br /&gt;
* jitsi - our experience of using the free hosted version left us uncomfortable with jitsi as platform for a large event with 3 streams. None of us had the experience or access to hardware and bandwidth to consider running a large self-hosted version of jitsi. We were also concerned about how we could control access or restrict anyone breaching our CoC&lt;br /&gt;
* several of us had experience of running large meetings on zoom and were confident that we could host the event on zoom and leverage it's capabilities.&lt;br /&gt;
&lt;br /&gt;
==== What we learnt ====&lt;br /&gt;
&lt;br /&gt;
* zoom worked as anticipated. We had no major technical problems and as far as we know very few participants experienced problems, zoom offers clients for Linux, Mac and Windows, iOS and Android.&lt;br /&gt;
* we were able to manage participants by muting everyone on entry and restricting chat within the app to messages to one of the hosts and from the hosts to the whole audience.&lt;br /&gt;
* the recording worked well, a co-host was asked to remind the host to start and stop the recording for each session to keep videos at a manageable size&lt;br /&gt;
* we saved all of the chat transcripts as part of our CoC policy (fortunately unnecessary)&lt;br /&gt;
&lt;br /&gt;
We purchased:&lt;br /&gt;
* 1 account for up to 1,000 people for the keynotes&lt;br /&gt;
* 2 accounts for up to 500 people for the other streams&lt;br /&gt;
* 1 account for up to 100 people for the coffee bar&lt;br /&gt;
* An add on for large cloud storage for all of the video recordings&lt;br /&gt;
* '''Total cost £198''' (a month's licenses)&lt;br /&gt;
&lt;br /&gt;
We over-provisioned because we did not know how many people would actually log-in. We could have managed with smaller accounts and saved some money.&lt;br /&gt;
&lt;br /&gt;
It is unclear whether we would have been better off purchasing zoom webinar licenses rather than large meetings.&lt;br /&gt;
&lt;br /&gt;
We were aware that the zoom meetings could have been streamed to youtube but we did not see any significant benefit from doing that.&lt;br /&gt;
&lt;br /&gt;
==== Options for the future ====&lt;br /&gt;
&lt;br /&gt;
We have received some retrospective suggestions for alternative tech approaches to running an online event. Hopefully others will be inspired to run further online FOSS4G events and they will experiment with these.&lt;br /&gt;
&lt;br /&gt;
Our choices were based on a need for a low effort tech approach given our small team and pressures on our time. Despite the poor publicity that zoom had received re security during the COVID crisis we found that the security features available were sufficient for our needs.&lt;br /&gt;
&lt;br /&gt;
=== Eventbrite ===&lt;br /&gt;
&lt;br /&gt;
We used eventbrite for our registration system. &lt;br /&gt;
&lt;br /&gt;
* It was free as the event was a free event, if we had charged £10 per registration we would have incurred cost including credit card fees of about 10%&lt;br /&gt;
* Eventbrite has an online event page which is only accessible to people who have registered, we only exposed the links to the conference streams via this page to minimise the risks of being overloaded or trolled.&lt;br /&gt;
* We added a registration question to request permission to add registrants to the global FOSS4G mailing list (we had a very high acceptance rate). '''This should be highly recommended practice for future FOSS4Gs'''&lt;br /&gt;
* We made the completion of a company address mandatory on registration because it forced people to provide their 2 digit country code which enabled us to analyse the locations of registrants. This will enable future FOSS4G to geographically segment the audience.&lt;br /&gt;
* We used the attendee mailing features to send a a series of emails to participants in the build up and post event. Its a bit clunky but it works fine and avoided having to maintain an alternative email list.&lt;br /&gt;
&lt;br /&gt;
=== WhatsAppp ===&lt;br /&gt;
&lt;br /&gt;
We used WhatsApp for team communications in the build up and on the day. We also had a group for our volunteers and were able to share updates with the volunteers before the event and it was the main channel of communication on the day&lt;br /&gt;
&lt;br /&gt;
We could have considered a speakers group in addition.&lt;br /&gt;
&lt;br /&gt;
=== Twitter ===&lt;br /&gt;
&lt;br /&gt;
We used twitter as our main channel for publicity prior to the event. It is important to recognise that not everyone is on twitter, future events should consider what other channels to use for communication with potential participants.&lt;br /&gt;
&lt;br /&gt;
We used twitter on the day for announcements, publicity and encouraged the participants to chat via twitter.&lt;br /&gt;
&lt;br /&gt;
== Event organisation ==&lt;br /&gt;
&lt;br /&gt;
* The event team was the 6 members of the OSGeo:UK organising committee we held our first call to discuss the event on 2020-04-13.&lt;br /&gt;
* We hosted our event website on the OSGeo:UK site at GitHub.&lt;br /&gt;
* We used Google forms for the call for papers and for a request for volunteers&lt;br /&gt;
&lt;br /&gt;
=== Hosts and co-hosts ===&lt;br /&gt;
&lt;br /&gt;
* For each stream of the event we had a host (one of the organising team + Nick Bearman) and co-host (volunteers).&lt;br /&gt;
* The [https://docs.google.com/document/d/1hlNl1EhbWa4ZjpXvsxz_V9Rid2VpIPmcnKBQ5089Jkg/edit?usp=sharing Host Guide] provided detailed guidance for hosts and co-hosts on how to run the session on zoom, detailed settings and what to do in the event of a code of conduct violation or other issue. This doc evolved as we ran a couple of trial sessions with volunteers.&lt;br /&gt;
&lt;br /&gt;
=== Recording and publishing ===&lt;br /&gt;
&lt;br /&gt;
* We asked hosts to start the recording before introducing the speaker and to stop the recording after questions. This created a separate recording for each speaker and made it a lot easier for the video team.&lt;br /&gt;
* It's easy to forget to start/stop the recordings so we asked the co-hosts to remind the hosts&lt;br /&gt;
* We purchased a large amount of cloud storage for recordings in preference to each host recording locally. This enabled the volunteers post-processing the video to access all of the recordings in one place.&lt;br /&gt;
* Our video volunteers topped and tailed each recording with an intro slide and closing slide&lt;br /&gt;
* Video was uploaded to the [http://www.youtube.com/c/FOSS4GUK FOSS4GUK YouTube] on 2020-06-23 and is linked from the [https://uk.osgeo.org/foss4gukonline2020/sessions.html programme] on the website where we also linked to the slides where provided.&lt;br /&gt;
&lt;br /&gt;
=== What worked ===&lt;br /&gt;
&lt;br /&gt;
* We kept to schedule throughout the day&lt;br /&gt;
* The 10 minute gaps between sessions stopped the day being too frantic&lt;br /&gt;
* We kept the 4 streams open for the whole day and swapped hosts to give everyone a break. This avoided having to share login details and seemed to work well&lt;br /&gt;
* zoom proved to be adequate for our requirements, we had no trolling or security issues&lt;br /&gt;
* speakers seemed happy presenting on zoom although most commented that presenting to a screen was very different to being in front of an audience.&lt;br /&gt;
* restricting the chat to participants to hosts only prevented too much distraction.&lt;br /&gt;
* Hosts received questions via chat and asked them on behalf of participants, this enabled us to get through more questions than if we had virtually &amp;quot;handed the mike&amp;quot; to the questioners. We think it also encouraged some less confident people (and those for whom English is a second language) to ask questions.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== What didn't work so well ===&lt;br /&gt;
&lt;br /&gt;
* A tiny number of people did not get the link info via the eventbrite website for reasons that we don't understand (spam filters possibly) - if they mailed us we provided the link info to them directly.&lt;br /&gt;
* The coffee bar was not heavily used&lt;br /&gt;
* restricting the chat to participants to hosts only prevented interaction between delegates during and after the talk&lt;br /&gt;
* We had a high level of no-shows. A free sign-up encourages no shows but we wanted to make the event as accessible as possible.&lt;br /&gt;
* We had a low proportion of voluntary donations (&amp;lt;20%)&lt;br /&gt;
* Some people would have preferred there to be a lunch break, that might have been an opportunity to encourage people to try out the coffee bar.&lt;br /&gt;
&lt;br /&gt;
== What would we try to do if we ran another event? ==&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124869</id>
		<title>FOSS4GUK 2020 Online - Lessons Learnt</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124869"/>
		<updated>2020-06-23T16:25:05Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: /* What didn't work */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''This is a draft at the moment!'''&lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
&lt;br /&gt;
[https://uk.osgeo.org/foss4gukonline2020/ FOSS4GUK 2020 Online] was hosted by the [https://uk.osgeo.org OSGeo:UK] committee on 17th June 2020 from 9.00am to 17.30pm UTC+1&lt;br /&gt;
&lt;br /&gt;
The event was free to attend with all of the costs (see below) funded from OSGeo:UK reserves. &lt;br /&gt;
&lt;br /&gt;
=== Delegates ===&lt;br /&gt;
&lt;br /&gt;
* 1,000 people registered&lt;br /&gt;
* We estimate that between 500 and 600 attended&lt;br /&gt;
* Maximum number online at any time was 460, minimum was 205&lt;br /&gt;
* Delegates from 77 countries&lt;br /&gt;
** 48% from GB, 8% US, 4% India&lt;br /&gt;
&lt;br /&gt;
[[File:FOSS4GUK Attendee Countries.png|frameless]]&lt;br /&gt;
&lt;br /&gt;
=== [https://uk.osgeo.org/foss4gukonline2020/programme.html Programme] ===&lt;br /&gt;
&lt;br /&gt;
* 3 streams running for the whole day (except during keynotes)&lt;br /&gt;
** 2 keynotes&lt;br /&gt;
** 29 talks and demos&lt;br /&gt;
** 4 Lightning talks&lt;br /&gt;
* 38 Speakers (10 women)&lt;br /&gt;
* Coffee bar stream where delegates could hang out and chat (not heavily used)&lt;br /&gt;
&lt;br /&gt;
=== Finances ===&lt;br /&gt;
* The only costs were the fees for the zoom account for 1 month: £198&lt;br /&gt;
* Delegate donations:&lt;br /&gt;
** OSGeo:UK 63 individual donations - gross £1,810, net after Paypal fees £1,744 (as of 2020-06-20)&lt;br /&gt;
** MapAction ?&lt;br /&gt;
&lt;br /&gt;
== Feedback ==&lt;br /&gt;
&lt;br /&gt;
As of 2020-06-22 we had 210 feedback responses:&lt;br /&gt;
* 95% rated the event experience very good or excellent&lt;br /&gt;
* 93% were happy with the technology platform&lt;br /&gt;
* 27% attended for the whole day, 27% attended 7-11 sessions, 45% attended 2-6 sessions&lt;br /&gt;
* 16% used the coffee bar&lt;br /&gt;
* 47% of respondents (but not attendees) made a donation to OSGeo:UK (34%) or MapAction (13%). The average donation was ca £20&lt;br /&gt;
[[File:FOSS4GUK Satisfaction.png|frameless]]&lt;br /&gt;
[[File:FOSS4GUK Technology satisfaction.png|frameless]]&lt;br /&gt;
[[File:FOSS4GUK No of sessions attended.png|frameless]]&lt;br /&gt;
&lt;br /&gt;
== Tech and tools ==&lt;br /&gt;
&lt;br /&gt;
=== Choice of video conferencing platform ===&lt;br /&gt;
&lt;br /&gt;
==== We considered ====&lt;br /&gt;
&lt;br /&gt;
* webex (we had an offer of a free account from a sponsor) - problems with audio, uncertain linux support, limit on numbers&lt;br /&gt;
* hopin.to - a virtual conference application, unfortunately the demo the we attended was not successful and we did not feel comfortable taking the risk on a new service but it looks promising for the future&lt;br /&gt;
* several other services that did not seem to fit our needs&lt;br /&gt;
* jitsi - our experience of using the free hosted version left us uncomfortable with jitsi as platform for a large event with 3 streams. None of us had the experience or access to hardware and bandwidth to consider running a large self-hosted version of jitsi. We were also concerned about how we could control access or restrict anyone breaching our CoC&lt;br /&gt;
* several of us had experience of running large meetings on zoom and were confident that we could host the event on zoom and leverage it's capabilities.&lt;br /&gt;
&lt;br /&gt;
==== What we learnt ====&lt;br /&gt;
&lt;br /&gt;
* zoom worked as anticipated. We had no major technical problems and as far as we know very few participants experienced problems, zoom offers clients for Linux, Mac and Windows, iOS and Android.&lt;br /&gt;
* we were able to manage participants by muting everyone on entry and restricting chat within the app to messages to one of the hosts and from the hosts to the whole audience.&lt;br /&gt;
* the recording worked well, a co-host was asked to remind the host to start and stop the recording for each session to keep videos at a manageable size&lt;br /&gt;
* we saved all of the chat transcripts as part of our CoC policy (fortunately unnecessary)&lt;br /&gt;
&lt;br /&gt;
We purchased:&lt;br /&gt;
* 1 account for up to 1,000 people for the keynotes&lt;br /&gt;
* 2 accounts for up to 500 people for the other streams&lt;br /&gt;
* 1 account for up to 100 people for the coffee bar&lt;br /&gt;
* An add on for large cloud storage for all of the video recordings&lt;br /&gt;
* '''Total cost £198''' (a month's licenses)&lt;br /&gt;
&lt;br /&gt;
We over-provisioned because we did not know how many people would actually log-in. We could have managed with smaller accounts and saved some money.&lt;br /&gt;
&lt;br /&gt;
It is unclear whether we would have been better off purchasing zoom webinar licenses rather than large meetings.&lt;br /&gt;
&lt;br /&gt;
We were aware that the zoom meetings could have been streamed to youtube but we did not see any significant benefit from doing that.&lt;br /&gt;
&lt;br /&gt;
==== Options for the future ====&lt;br /&gt;
&lt;br /&gt;
We have received some retrospective suggestions for alternative tech approaches to running an online event. Hopefully others will be inspired to run further online FOSS4G events and they will experiment with these.&lt;br /&gt;
&lt;br /&gt;
Our choices were based on a need for a low effort tech approach given our small team and pressures on our time. Despite the poor publicity that zoom had received re security during the COVID crisis we found that the security features available were sufficient for our needs.&lt;br /&gt;
&lt;br /&gt;
=== Eventbrite ===&lt;br /&gt;
&lt;br /&gt;
We used eventbrite for our registration system. &lt;br /&gt;
&lt;br /&gt;
* It was free as the event was a free event, if we had charged £10 per registration we would have incurred cost including credit card fees of about 10%&lt;br /&gt;
* Eventbrite has an online event page which is only accessible to people who have registered, we only exposed the links to the conference streams via this page to minimise the risks of being overloaded or trolled.&lt;br /&gt;
* We added a registration question to request permission to add registrants to the global FOSS4G mailing list (we had a very high acceptance rate). '''This should be highly recommended practice for future FOSS4Gs'''&lt;br /&gt;
* We made the completion of a company address mandatory on registration because it forced people to provide their 2 digit country code which enabled us to analyse the locations of registrants. This will enable future FOSS4G to geographically segment the audience.&lt;br /&gt;
* We used the attendee mailing features to send a a series of emails to participants in the build up and post event. Its a bit clunky but it works fine and avoided having to maintain an alternative email list.&lt;br /&gt;
&lt;br /&gt;
=== WhatsAppp ===&lt;br /&gt;
&lt;br /&gt;
We used WhatsApp for team communications in the build up and on the day. We also had a group for our volunteers and were able to share updates with the volunteers before the event and it was the main channel of communication on the day&lt;br /&gt;
&lt;br /&gt;
We could have considered a speakers group in addition.&lt;br /&gt;
&lt;br /&gt;
=== Twitter ===&lt;br /&gt;
&lt;br /&gt;
We used twitter as our main channel for publicity prior to the event. It is important to recognise that not everyone is on twitter, future events should consider what other channels to use for communication with potential participants.&lt;br /&gt;
&lt;br /&gt;
We used twitter on the day for announcements, publicity and encouraged the participants to chat via twitter.&lt;br /&gt;
&lt;br /&gt;
== Event organisation ==&lt;br /&gt;
&lt;br /&gt;
* The event team was the 6 members of the OSGeo:UK organising committee we held our first call to discuss the event on 2020-04-13.&lt;br /&gt;
* We hosted our event website on the OSGeo:UK site at GitHub.&lt;br /&gt;
* We used Google forms for the call for papers and for a request for volunteers&lt;br /&gt;
&lt;br /&gt;
=== Hosts and co-hosts ===&lt;br /&gt;
&lt;br /&gt;
* For each stream of the event we had a host (one of the organising team + Nick Bearman) and co-host (volunteers).&lt;br /&gt;
* The [https://docs.google.com/document/d/1hlNl1EhbWa4ZjpXvsxz_V9Rid2VpIPmcnKBQ5089Jkg/edit?usp=sharing Host Guide] provided detailed guidance for hosts and co-hosts on how to run the session on zoom, detailed settings and what to do in the event of a code of conduct violation or other issue. This doc evolved as we ran a couple of trial sessions with volunteers.&lt;br /&gt;
&lt;br /&gt;
=== Recording and publishing ===&lt;br /&gt;
&lt;br /&gt;
* We asked hosts to start the recording before introducing the speaker and to stop the recording after questions. This created a separate recording for each speaker and made it a lot easier for the video team.&lt;br /&gt;
* It's easy to forget to start/stop the recordings so we asked the co-hosts to remind the hosts&lt;br /&gt;
* We purchased a large amount of cloud storage for recordings in preference to each host recording locally. This enabled the volunteers post-processing the video to access all of the recordings in one place.&lt;br /&gt;
* Our video volunteers topped and tailed each recording with an intro slide and closing slide&lt;br /&gt;
* Video was uploaded to the [http://www.youtube.com/c/FOSS4GUK FOSS4GUK YouTube] on 2020-06-23 and is linked from the [https://uk.osgeo.org/foss4gukonline2020/sessions.html programme] on the website&lt;br /&gt;
&lt;br /&gt;
=== What worked ===&lt;br /&gt;
&lt;br /&gt;
* We kept to schedule throughout the day&lt;br /&gt;
* The 10 minute gaps between sessions stopped the day being too frantic&lt;br /&gt;
* We kept the 4 streams open for the whole day and swapped hosts to give everyone a break. This avoided having to share login details and seemed to work well&lt;br /&gt;
* zoom proved to be adequate for our requirements, we had no trolling or security issues&lt;br /&gt;
* speakers seemed happy presenting on zoom although most commented that presenting to a screen was very different to being in front of an audience.&lt;br /&gt;
* restricting the chat to participants to hosts only prevented too much distraction.&lt;br /&gt;
* Hosts received questions via chat and asked them on behalf of participants, this enabled us to get through more questions than if we had virtually &amp;quot;handed the mike&amp;quot; to the questioners. We think it also encouraged some less confident people (and those for whom English is a second language) to ask questions.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== What didn't work so well ===&lt;br /&gt;
&lt;br /&gt;
* A tiny number of people did not get the link info via the eventbrite website for reasons that we don't understand (spam filters possibly) - if they mailed us we provided the link info to them directly.&lt;br /&gt;
* The coffee bar was not heavily used&lt;br /&gt;
* restricting the chat to participants to hosts only prevented interaction between delegates during and after the talk&lt;br /&gt;
* We had a high level of no-shows. A free sign-up encourages no shows but we wanted to make the event as accessible as possible.&lt;br /&gt;
* We had a low proportion of voluntary donations (&amp;lt;20%)&lt;br /&gt;
* Some people would have preferred there to be a lunch break, that might have been an opportunity to encourage people to try out the coffee bar.&lt;br /&gt;
&lt;br /&gt;
== What would we try to do if we ran another event? ==&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124868</id>
		<title>FOSS4GUK 2020 Online - Lessons Learnt</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124868"/>
		<updated>2020-06-23T16:24:47Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: /* Event organisation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''This is a draft at the moment!'''&lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
&lt;br /&gt;
[https://uk.osgeo.org/foss4gukonline2020/ FOSS4GUK 2020 Online] was hosted by the [https://uk.osgeo.org OSGeo:UK] committee on 17th June 2020 from 9.00am to 17.30pm UTC+1&lt;br /&gt;
&lt;br /&gt;
The event was free to attend with all of the costs (see below) funded from OSGeo:UK reserves. &lt;br /&gt;
&lt;br /&gt;
=== Delegates ===&lt;br /&gt;
&lt;br /&gt;
* 1,000 people registered&lt;br /&gt;
* We estimate that between 500 and 600 attended&lt;br /&gt;
* Maximum number online at any time was 460, minimum was 205&lt;br /&gt;
* Delegates from 77 countries&lt;br /&gt;
** 48% from GB, 8% US, 4% India&lt;br /&gt;
&lt;br /&gt;
[[File:FOSS4GUK Attendee Countries.png|frameless]]&lt;br /&gt;
&lt;br /&gt;
=== [https://uk.osgeo.org/foss4gukonline2020/programme.html Programme] ===&lt;br /&gt;
&lt;br /&gt;
* 3 streams running for the whole day (except during keynotes)&lt;br /&gt;
** 2 keynotes&lt;br /&gt;
** 29 talks and demos&lt;br /&gt;
** 4 Lightning talks&lt;br /&gt;
* 38 Speakers (10 women)&lt;br /&gt;
* Coffee bar stream where delegates could hang out and chat (not heavily used)&lt;br /&gt;
&lt;br /&gt;
=== Finances ===&lt;br /&gt;
* The only costs were the fees for the zoom account for 1 month: £198&lt;br /&gt;
* Delegate donations:&lt;br /&gt;
** OSGeo:UK 63 individual donations - gross £1,810, net after Paypal fees £1,744 (as of 2020-06-20)&lt;br /&gt;
** MapAction ?&lt;br /&gt;
&lt;br /&gt;
== Feedback ==&lt;br /&gt;
&lt;br /&gt;
As of 2020-06-22 we had 210 feedback responses:&lt;br /&gt;
* 95% rated the event experience very good or excellent&lt;br /&gt;
* 93% were happy with the technology platform&lt;br /&gt;
* 27% attended for the whole day, 27% attended 7-11 sessions, 45% attended 2-6 sessions&lt;br /&gt;
* 16% used the coffee bar&lt;br /&gt;
* 47% of respondents (but not attendees) made a donation to OSGeo:UK (34%) or MapAction (13%). The average donation was ca £20&lt;br /&gt;
[[File:FOSS4GUK Satisfaction.png|frameless]]&lt;br /&gt;
[[File:FOSS4GUK Technology satisfaction.png|frameless]]&lt;br /&gt;
[[File:FOSS4GUK No of sessions attended.png|frameless]]&lt;br /&gt;
&lt;br /&gt;
== Tech and tools ==&lt;br /&gt;
&lt;br /&gt;
=== Choice of video conferencing platform ===&lt;br /&gt;
&lt;br /&gt;
==== We considered ====&lt;br /&gt;
&lt;br /&gt;
* webex (we had an offer of a free account from a sponsor) - problems with audio, uncertain linux support, limit on numbers&lt;br /&gt;
* hopin.to - a virtual conference application, unfortunately the demo the we attended was not successful and we did not feel comfortable taking the risk on a new service but it looks promising for the future&lt;br /&gt;
* several other services that did not seem to fit our needs&lt;br /&gt;
* jitsi - our experience of using the free hosted version left us uncomfortable with jitsi as platform for a large event with 3 streams. None of us had the experience or access to hardware and bandwidth to consider running a large self-hosted version of jitsi. We were also concerned about how we could control access or restrict anyone breaching our CoC&lt;br /&gt;
* several of us had experience of running large meetings on zoom and were confident that we could host the event on zoom and leverage it's capabilities.&lt;br /&gt;
&lt;br /&gt;
==== What we learnt ====&lt;br /&gt;
&lt;br /&gt;
* zoom worked as anticipated. We had no major technical problems and as far as we know very few participants experienced problems, zoom offers clients for Linux, Mac and Windows, iOS and Android.&lt;br /&gt;
* we were able to manage participants by muting everyone on entry and restricting chat within the app to messages to one of the hosts and from the hosts to the whole audience.&lt;br /&gt;
* the recording worked well, a co-host was asked to remind the host to start and stop the recording for each session to keep videos at a manageable size&lt;br /&gt;
* we saved all of the chat transcripts as part of our CoC policy (fortunately unnecessary)&lt;br /&gt;
&lt;br /&gt;
We purchased:&lt;br /&gt;
* 1 account for up to 1,000 people for the keynotes&lt;br /&gt;
* 2 accounts for up to 500 people for the other streams&lt;br /&gt;
* 1 account for up to 100 people for the coffee bar&lt;br /&gt;
* An add on for large cloud storage for all of the video recordings&lt;br /&gt;
* '''Total cost £198''' (a month's licenses)&lt;br /&gt;
&lt;br /&gt;
We over-provisioned because we did not know how many people would actually log-in. We could have managed with smaller accounts and saved some money.&lt;br /&gt;
&lt;br /&gt;
It is unclear whether we would have been better off purchasing zoom webinar licenses rather than large meetings.&lt;br /&gt;
&lt;br /&gt;
We were aware that the zoom meetings could have been streamed to youtube but we did not see any significant benefit from doing that.&lt;br /&gt;
&lt;br /&gt;
==== Options for the future ====&lt;br /&gt;
&lt;br /&gt;
We have received some retrospective suggestions for alternative tech approaches to running an online event. Hopefully others will be inspired to run further online FOSS4G events and they will experiment with these.&lt;br /&gt;
&lt;br /&gt;
Our choices were based on a need for a low effort tech approach given our small team and pressures on our time. Despite the poor publicity that zoom had received re security during the COVID crisis we found that the security features available were sufficient for our needs.&lt;br /&gt;
&lt;br /&gt;
=== Eventbrite ===&lt;br /&gt;
&lt;br /&gt;
We used eventbrite for our registration system. &lt;br /&gt;
&lt;br /&gt;
* It was free as the event was a free event, if we had charged £10 per registration we would have incurred cost including credit card fees of about 10%&lt;br /&gt;
* Eventbrite has an online event page which is only accessible to people who have registered, we only exposed the links to the conference streams via this page to minimise the risks of being overloaded or trolled.&lt;br /&gt;
* We added a registration question to request permission to add registrants to the global FOSS4G mailing list (we had a very high acceptance rate). '''This should be highly recommended practice for future FOSS4Gs'''&lt;br /&gt;
* We made the completion of a company address mandatory on registration because it forced people to provide their 2 digit country code which enabled us to analyse the locations of registrants. This will enable future FOSS4G to geographically segment the audience.&lt;br /&gt;
* We used the attendee mailing features to send a a series of emails to participants in the build up and post event. Its a bit clunky but it works fine and avoided having to maintain an alternative email list.&lt;br /&gt;
&lt;br /&gt;
=== WhatsAppp ===&lt;br /&gt;
&lt;br /&gt;
We used WhatsApp for team communications in the build up and on the day. We also had a group for our volunteers and were able to share updates with the volunteers before the event and it was the main channel of communication on the day&lt;br /&gt;
&lt;br /&gt;
We could have considered a speakers group in addition.&lt;br /&gt;
&lt;br /&gt;
=== Twitter ===&lt;br /&gt;
&lt;br /&gt;
We used twitter as our main channel for publicity prior to the event. It is important to recognise that not everyone is on twitter, future events should consider what other channels to use for communication with potential participants.&lt;br /&gt;
&lt;br /&gt;
We used twitter on the day for announcements, publicity and encouraged the participants to chat via twitter.&lt;br /&gt;
&lt;br /&gt;
== Event organisation ==&lt;br /&gt;
&lt;br /&gt;
* The event team was the 6 members of the OSGeo:UK organising committee we held our first call to discuss the event on 2020-04-13.&lt;br /&gt;
* We hosted our event website on the OSGeo:UK site at GitHub.&lt;br /&gt;
* We used Google forms for the call for papers and for a request for volunteers&lt;br /&gt;
&lt;br /&gt;
=== Hosts and co-hosts ===&lt;br /&gt;
&lt;br /&gt;
* For each stream of the event we had a host (one of the organising team + Nick Bearman) and co-host (volunteers).&lt;br /&gt;
* The [https://docs.google.com/document/d/1hlNl1EhbWa4ZjpXvsxz_V9Rid2VpIPmcnKBQ5089Jkg/edit?usp=sharing Host Guide] provided detailed guidance for hosts and co-hosts on how to run the session on zoom, detailed settings and what to do in the event of a code of conduct violation or other issue. This doc evolved as we ran a couple of trial sessions with volunteers.&lt;br /&gt;
&lt;br /&gt;
=== Recording and publishing ===&lt;br /&gt;
&lt;br /&gt;
* We asked hosts to start the recording before introducing the speaker and to stop the recording after questions. This created a separate recording for each speaker and made it a lot easier for the video team.&lt;br /&gt;
* It's easy to forget to start/stop the recordings so we asked the co-hosts to remind the hosts&lt;br /&gt;
* We purchased a large amount of cloud storage for recordings in preference to each host recording locally. This enabled the volunteers post-processing the video to access all of the recordings in one place.&lt;br /&gt;
* Our video volunteers topped and tailed each recording with an intro slide and closing slide&lt;br /&gt;
* Video was uploaded to the [http://www.youtube.com/c/FOSS4GUK FOSS4GUK YouTube] on 2020-06-23 and is linked from the [https://uk.osgeo.org/foss4gukonline2020/sessions.html programme] on the website&lt;br /&gt;
&lt;br /&gt;
=== What worked ===&lt;br /&gt;
&lt;br /&gt;
* We kept to schedule throughout the day&lt;br /&gt;
* The 10 minute gaps between sessions stopped the day being too frantic&lt;br /&gt;
* We kept the 4 streams open for the whole day and swapped hosts to give everyone a break. This avoided having to share login details and seemed to work well&lt;br /&gt;
* zoom proved to be adequate for our requirements, we had no trolling or security issues&lt;br /&gt;
* speakers seemed happy presenting on zoom although most commented that presenting to a screen was very different to being in front of an audience.&lt;br /&gt;
* restricting the chat to participants to hosts only prevented too much distraction.&lt;br /&gt;
* Hosts received questions via chat and asked them on behalf of participants, this enabled us to get through more questions than if we had virtually &amp;quot;handed the mike&amp;quot; to the questioners. We think it also encouraged some less confident people (and those for whom English is a second language) to ask questions.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== What didn't work ===&lt;br /&gt;
&lt;br /&gt;
* A tiny number of people did not get the link info via the eventbrite website for reasons that we don't understand (spam filters possibly) - if they mailed us we provided the link info to them directly.&lt;br /&gt;
* The coffee bar was not heavily used&lt;br /&gt;
* restricting the chat to participants to hosts only prevented interaction between delegates during and after the talk&lt;br /&gt;
* We had a high level of no-shows. A free sign-up encourages no shows but we wanted to make the event as accessible as possible.&lt;br /&gt;
* We had a low proportion of voluntary donations (&amp;lt;20%)&lt;br /&gt;
* Some people would have preferred there to be a lunch break, that might have been an opportunity to encourage people to try out the coffee bar.&lt;br /&gt;
&lt;br /&gt;
== What would we try to do if we ran another event? ==&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124867</id>
		<title>FOSS4GUK 2020 Online - Lessons Learnt</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124867"/>
		<updated>2020-06-23T16:19:18Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: /* Event organisation */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''This is a draft at the moment!'''&lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
&lt;br /&gt;
[https://uk.osgeo.org/foss4gukonline2020/ FOSS4GUK 2020 Online] was hosted by the [https://uk.osgeo.org OSGeo:UK] committee on 17th June 2020 from 9.00am to 17.30pm UTC+1&lt;br /&gt;
&lt;br /&gt;
The event was free to attend with all of the costs (see below) funded from OSGeo:UK reserves. &lt;br /&gt;
&lt;br /&gt;
=== Delegates ===&lt;br /&gt;
&lt;br /&gt;
* 1,000 people registered&lt;br /&gt;
* We estimate that between 500 and 600 attended&lt;br /&gt;
* Maximum number online at any time was 460, minimum was 205&lt;br /&gt;
* Delegates from 77 countries&lt;br /&gt;
** 48% from GB, 8% US, 4% India&lt;br /&gt;
&lt;br /&gt;
[[File:FOSS4GUK Attendee Countries.png|frameless]]&lt;br /&gt;
&lt;br /&gt;
=== [https://uk.osgeo.org/foss4gukonline2020/programme.html Programme] ===&lt;br /&gt;
&lt;br /&gt;
* 3 streams running for the whole day (except during keynotes)&lt;br /&gt;
** 2 keynotes&lt;br /&gt;
** 29 talks and demos&lt;br /&gt;
** 4 Lightning talks&lt;br /&gt;
* 38 Speakers (10 women)&lt;br /&gt;
* Coffee bar stream where delegates could hang out and chat (not heavily used)&lt;br /&gt;
&lt;br /&gt;
=== Finances ===&lt;br /&gt;
* The only costs were the fees for the zoom account for 1 month: £198&lt;br /&gt;
* Delegate donations:&lt;br /&gt;
** OSGeo:UK 63 individual donations - gross £1,810, net after Paypal fees £1,744 (as of 2020-06-20)&lt;br /&gt;
** MapAction ?&lt;br /&gt;
&lt;br /&gt;
== Feedback ==&lt;br /&gt;
&lt;br /&gt;
As of 2020-06-22 we had 210 feedback responses:&lt;br /&gt;
* 95% rated the event experience very good or excellent&lt;br /&gt;
* 93% were happy with the technology platform&lt;br /&gt;
* 27% attended for the whole day, 27% attended 7-11 sessions, 45% attended 2-6 sessions&lt;br /&gt;
* 16% used the coffee bar&lt;br /&gt;
* 47% of respondents (but not attendees) made a donation to OSGeo:UK (34%) or MapAction (13%). The average donation was ca £20&lt;br /&gt;
[[File:FOSS4GUK Satisfaction.png|frameless]]&lt;br /&gt;
[[File:FOSS4GUK Technology satisfaction.png|frameless]]&lt;br /&gt;
[[File:FOSS4GUK No of sessions attended.png|frameless]]&lt;br /&gt;
&lt;br /&gt;
== Tech and tools ==&lt;br /&gt;
&lt;br /&gt;
=== Choice of video conferencing platform ===&lt;br /&gt;
&lt;br /&gt;
==== We considered ====&lt;br /&gt;
&lt;br /&gt;
* webex (we had an offer of a free account from a sponsor) - problems with audio, uncertain linux support, limit on numbers&lt;br /&gt;
* hopin.to - a virtual conference application, unfortunately the demo the we attended was not successful and we did not feel comfortable taking the risk on a new service but it looks promising for the future&lt;br /&gt;
* several other services that did not seem to fit our needs&lt;br /&gt;
* jitsi - our experience of using the free hosted version left us uncomfortable with jitsi as platform for a large event with 3 streams. None of us had the experience or access to hardware and bandwidth to consider running a large self-hosted version of jitsi. We were also concerned about how we could control access or restrict anyone breaching our CoC&lt;br /&gt;
* several of us had experience of running large meetings on zoom and were confident that we could host the event on zoom and leverage it's capabilities.&lt;br /&gt;
&lt;br /&gt;
==== What we learnt ====&lt;br /&gt;
&lt;br /&gt;
* zoom worked as anticipated. We had no major technical problems and as far as we know very few participants experienced problems, zoom offers clients for Linux, Mac and Windows, iOS and Android.&lt;br /&gt;
* we were able to manage participants by muting everyone on entry and restricting chat within the app to messages to one of the hosts and from the hosts to the whole audience.&lt;br /&gt;
* the recording worked well, a co-host was asked to remind the host to start and stop the recording for each session to keep videos at a manageable size&lt;br /&gt;
* we saved all of the chat transcripts as part of our CoC policy (fortunately unnecessary)&lt;br /&gt;
&lt;br /&gt;
We purchased:&lt;br /&gt;
* 1 account for up to 1,000 people for the keynotes&lt;br /&gt;
* 2 accounts for up to 500 people for the other streams&lt;br /&gt;
* 1 account for up to 100 people for the coffee bar&lt;br /&gt;
* An add on for large cloud storage for all of the video recordings&lt;br /&gt;
* '''Total cost £198''' (a month's licenses)&lt;br /&gt;
&lt;br /&gt;
We over-provisioned because we did not know how many people would actually log-in. We could have managed with smaller accounts and saved some money.&lt;br /&gt;
&lt;br /&gt;
It is unclear whether we would have been better off purchasing zoom webinar licenses rather than large meetings.&lt;br /&gt;
&lt;br /&gt;
We were aware that the zoom meetings could have been streamed to youtube but we did not see any significant benefit from doing that.&lt;br /&gt;
&lt;br /&gt;
==== Options for the future ====&lt;br /&gt;
&lt;br /&gt;
We have received some retrospective suggestions for alternative tech approaches to running an online event. Hopefully others will be inspired to run further online FOSS4G events and they will experiment with these.&lt;br /&gt;
&lt;br /&gt;
Our choices were based on a need for a low effort tech approach given our small team and pressures on our time. Despite the poor publicity that zoom had received re security during the COVID crisis we found that the security features available were sufficient for our needs.&lt;br /&gt;
&lt;br /&gt;
=== Eventbrite ===&lt;br /&gt;
&lt;br /&gt;
We used eventbrite for our registration system. &lt;br /&gt;
&lt;br /&gt;
* It was free as the event was a free event, if we had charged £10 per registration we would have incurred cost including credit card fees of about 10%&lt;br /&gt;
* Eventbrite has an online event page which is only accessible to people who have registered, we only exposed the links to the conference streams via this page to minimise the risks of being overloaded or trolled.&lt;br /&gt;
* We added a registration question to request permission to add registrants to the global FOSS4G mailing list (we had a very high acceptance rate). '''This should be highly recommended practice for future FOSS4Gs'''&lt;br /&gt;
* We made the completion of a company address mandatory on registration because it forced people to provide their 2 digit country code which enabled us to analyse the locations of registrants. This will enable future FOSS4G to geographically segment the audience.&lt;br /&gt;
* We used the attendee mailing features to send a a series of emails to participants in the build up and post event. Its a bit clunky but it works fine and avoided having to maintain an alternative email list.&lt;br /&gt;
&lt;br /&gt;
=== WhatsAppp ===&lt;br /&gt;
&lt;br /&gt;
We used WhatsApp for team communications in the build up and on the day. We also had a group for our volunteers and were able to share updates with the volunteers before the event and it was the main channel of communication on the day&lt;br /&gt;
&lt;br /&gt;
We could have considered a speakers group in addition.&lt;br /&gt;
&lt;br /&gt;
=== Twitter ===&lt;br /&gt;
&lt;br /&gt;
We used twitter as our main channel for publicity prior to the event. It is important to recognise that not everyone is on twitter, future events should consider what other channels to use for communication with potential participants.&lt;br /&gt;
&lt;br /&gt;
We used twitter on the day for announcements, publicity and encouraged the participants to chat via twitter.&lt;br /&gt;
&lt;br /&gt;
== Event organisation ==&lt;br /&gt;
&lt;br /&gt;
* The event team was the 6 members of the OSGeo:UK organising committee we held our first call to discuss the event on 2020-04-13.&lt;br /&gt;
* We hosted our event website on the OSGeo:UK site at GitHub.&lt;br /&gt;
* We used Google forms for the call for papers and for a request for volunteers&lt;br /&gt;
&lt;br /&gt;
=== Hosts and co-hosts ===&lt;br /&gt;
&lt;br /&gt;
* For each stream of the event we had a host (one of the organising team + Nick Bearman) and co-host (volunteers).&lt;br /&gt;
* The [https://docs.google.com/document/d/1hlNl1EhbWa4ZjpXvsxz_V9Rid2VpIPmcnKBQ5089Jkg/edit?usp=sharing Host Guide] provided detailed guidance for hosts and co-hosts on how to run the session on zoom, detailed settings and what to do in the event of a code of conduct violation or other issue. This doc evolved as we ran a couple of trial sessions with volunteers.&lt;br /&gt;
&lt;br /&gt;
=== Recording and publishing ===&lt;br /&gt;
&lt;br /&gt;
* We asked hosts to start the recording before introducing the speaker and to stop the recording after questions. This created a separate recording for each speaker and made it a lot easier for the video team.&lt;br /&gt;
* It's easy to forget to start/stop the recordings so we asked the co-hosts to remind the hosts&lt;br /&gt;
* We purchased a large amount of cloud storage for recordings in preference to each host recording locally. This enabled the volunteers post-processing the video to access all of the recordings in one place.&lt;br /&gt;
* Our video volunteers topped and tailed each recording with an intro slide and closing slide&lt;br /&gt;
* Video was uploaded to the [http://www.youtube.com/c/FOSS4GUK FOSS4GUK YouTube] on 2020-06-23 and is linked from the [https://uk.osgeo.org/foss4gukonline2020/sessions.html programme] on the website&lt;br /&gt;
&lt;br /&gt;
=== What worked ===&lt;br /&gt;
&lt;br /&gt;
* We kept the 4 streams open for the whole day and swapped hosts to give everyone a break. This avoided having to share login details and seemed to work well&lt;br /&gt;
* zoom proved to be adequate for our requirements, we had no trolling or security issues&lt;br /&gt;
* speakers seemed happy presenting on zoom although most commented that presenting to a screen was very different to being in front of an audience.&lt;br /&gt;
* restricting the chat to participants to hosts only prevented too much distraction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== What didn't work ===&lt;br /&gt;
&lt;br /&gt;
* A tiny number of people did not get the link info via the eventbrite website for reasons that we don't understand (spam filters possibly) - if they mailed us we provided the link info to them directly.&lt;br /&gt;
* The coffee bar was not heavily used&lt;br /&gt;
* restricting the chat to participants to hosts only prevented interaction between delegates during and after the talk&lt;br /&gt;
* We had a high level of no-shows. A free sign-up encourages no shows but we wanted to make the event as accessible as possible.&lt;br /&gt;
* We had a low proportion of voluntary donations &lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
== What would we try to do if we ran another event? ==&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124866</id>
		<title>FOSS4GUK 2020 Online - Lessons Learnt</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124866"/>
		<updated>2020-06-23T15:59:54Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: /* Event structure */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''This is a draft at the moment!'''&lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
&lt;br /&gt;
[https://uk.osgeo.org/foss4gukonline2020/ FOSS4GUK 2020 Online] was hosted by the [https://uk.osgeo.org OSGeo:UK] committee on 17th June 2020 from 9.00am to 17.30pm UTC+1&lt;br /&gt;
&lt;br /&gt;
The event was free to attend with all of the costs (see below) funded from OSGeo:UK reserves. &lt;br /&gt;
&lt;br /&gt;
=== Delegates ===&lt;br /&gt;
&lt;br /&gt;
* 1,000 people registered&lt;br /&gt;
* We estimate that between 500 and 600 attended&lt;br /&gt;
* Maximum number online at any time was 460, minimum was 205&lt;br /&gt;
* Delegates from 77 countries&lt;br /&gt;
** 48% from GB, 8% US, 4% India&lt;br /&gt;
&lt;br /&gt;
[[File:FOSS4GUK Attendee Countries.png|frameless]]&lt;br /&gt;
&lt;br /&gt;
=== [https://uk.osgeo.org/foss4gukonline2020/programme.html Programme] ===&lt;br /&gt;
&lt;br /&gt;
* 3 streams running for the whole day (except during keynotes)&lt;br /&gt;
** 2 keynotes&lt;br /&gt;
** 29 talks and demos&lt;br /&gt;
** 4 Lightning talks&lt;br /&gt;
* 38 Speakers (10 women)&lt;br /&gt;
* Coffee bar stream where delegates could hang out and chat (not heavily used)&lt;br /&gt;
&lt;br /&gt;
=== Finances ===&lt;br /&gt;
* The only costs were the fees for the zoom account for 1 month: £198&lt;br /&gt;
* Delegate donations:&lt;br /&gt;
** OSGeo:UK 63 individual donations - gross £1,810, net after Paypal fees £1,744 (as of 2020-06-20)&lt;br /&gt;
** MapAction ?&lt;br /&gt;
&lt;br /&gt;
== Feedback ==&lt;br /&gt;
&lt;br /&gt;
As of 2020-06-22 we had 210 feedback responses:&lt;br /&gt;
* 95% rated the event experience very good or excellent&lt;br /&gt;
* 93% were happy with the technology platform&lt;br /&gt;
* 27% attended for the whole day, 27% attended 7-11 sessions, 45% attended 2-6 sessions&lt;br /&gt;
* 16% used the coffee bar&lt;br /&gt;
* 47% of respondents (but not attendees) made a donation to OSGeo:UK (34%) or MapAction (13%). The average donation was ca £20&lt;br /&gt;
[[File:FOSS4GUK Satisfaction.png|frameless]]&lt;br /&gt;
[[File:FOSS4GUK Technology satisfaction.png|frameless]]&lt;br /&gt;
[[File:FOSS4GUK No of sessions attended.png|frameless]]&lt;br /&gt;
&lt;br /&gt;
== Tech and tools ==&lt;br /&gt;
&lt;br /&gt;
=== Choice of video conferencing platform ===&lt;br /&gt;
&lt;br /&gt;
==== We considered ====&lt;br /&gt;
&lt;br /&gt;
* webex (we had an offer of a free account from a sponsor) - problems with audio, uncertain linux support, limit on numbers&lt;br /&gt;
* hopin.to - a virtual conference application, unfortunately the demo the we attended was not successful and we did not feel comfortable taking the risk on a new service but it looks promising for the future&lt;br /&gt;
* several other services that did not seem to fit our needs&lt;br /&gt;
* jitsi - our experience of using the free hosted version left us uncomfortable with jitsi as platform for a large event with 3 streams. None of us had the experience or access to hardware and bandwidth to consider running a large self-hosted version of jitsi. We were also concerned about how we could control access or restrict anyone breaching our CoC&lt;br /&gt;
* several of us had experience of running large meetings on zoom and were confident that we could host the event on zoom and leverage it's capabilities.&lt;br /&gt;
&lt;br /&gt;
==== What we learnt ====&lt;br /&gt;
&lt;br /&gt;
* zoom worked as anticipated. We had no major technical problems and as far as we know very few participants experienced problems, zoom offers clients for Linux, Mac and Windows, iOS and Android.&lt;br /&gt;
* we were able to manage participants by muting everyone on entry and restricting chat within the app to messages to one of the hosts and from the hosts to the whole audience.&lt;br /&gt;
* the recording worked well, a co-host was asked to remind the host to start and stop the recording for each session to keep videos at a manageable size&lt;br /&gt;
* we saved all of the chat transcripts as part of our CoC policy (fortunately unnecessary)&lt;br /&gt;
&lt;br /&gt;
We purchased:&lt;br /&gt;
* 1 account for up to 1,000 people for the keynotes&lt;br /&gt;
* 2 accounts for up to 500 people for the other streams&lt;br /&gt;
* 1 account for up to 100 people for the coffee bar&lt;br /&gt;
* An add on for large cloud storage for all of the video recordings&lt;br /&gt;
* '''Total cost £198''' (a month's licenses)&lt;br /&gt;
&lt;br /&gt;
We over-provisioned because we did not know how many people would actually log-in. We could have managed with smaller accounts and saved some money.&lt;br /&gt;
&lt;br /&gt;
It is unclear whether we would have been better off purchasing zoom webinar licenses rather than large meetings.&lt;br /&gt;
&lt;br /&gt;
We were aware that the zoom meetings could have been streamed to youtube but we did not see any significant benefit from doing that.&lt;br /&gt;
&lt;br /&gt;
==== Options for the future ====&lt;br /&gt;
&lt;br /&gt;
We have received some retrospective suggestions for alternative tech approaches to running an online event. Hopefully others will be inspired to run further online FOSS4G events and they will experiment with these.&lt;br /&gt;
&lt;br /&gt;
Our choices were based on a need for a low effort tech approach given our small team and pressures on our time. Despite the poor publicity that zoom had received re security during the COVID crisis we found that the security features available were sufficient for our needs.&lt;br /&gt;
&lt;br /&gt;
=== Eventbrite ===&lt;br /&gt;
&lt;br /&gt;
We used eventbrite for our registration system. &lt;br /&gt;
&lt;br /&gt;
* It was free as the event was a free event, if we had charged £10 per registration we would have incurred cost including credit card fees of about 10%&lt;br /&gt;
* Eventbrite has an online event page which is only accessible to people who have registered, we only exposed the links to the conference streams via this page to minimise the risks of being overloaded or trolled.&lt;br /&gt;
* We added a registration question to request permission to add registrants to the global FOSS4G mailing list (we had a very high acceptance rate). '''This should be highly recommended practice for future FOSS4Gs'''&lt;br /&gt;
* We made the completion of a company address mandatory on registration because it forced people to provide their 2 digit country code which enabled us to analyse the locations of registrants. This will enable future FOSS4G to geographically segment the audience.&lt;br /&gt;
* We used the attendee mailing features to send a a series of emails to participants in the build up and post event. Its a bit clunky but it works fine and avoided having to maintain an alternative email list.&lt;br /&gt;
&lt;br /&gt;
=== WhatsAppp ===&lt;br /&gt;
&lt;br /&gt;
We used WhatsApp for team communications in the build up and on the day. We also had a group for our volunteers and were able to share updates with the volunteers before the event and it was the main channel of communication on the day&lt;br /&gt;
&lt;br /&gt;
We could have considered a speakers group in addition.&lt;br /&gt;
&lt;br /&gt;
=== Twitter ===&lt;br /&gt;
&lt;br /&gt;
We used twitter as our main channel for publicity prior to the event. It is important to recognise that not everyone is on twitter, future events should consider what other channels to use for communication with potential participants.&lt;br /&gt;
&lt;br /&gt;
We used twitter on the day for announcements, publicity and encouraged the participants to chat via twitter.&lt;br /&gt;
&lt;br /&gt;
== Event organisation ==&lt;br /&gt;
&lt;br /&gt;
* The event team was the 6 members of the OSGeo:UK organising committee we held our first call to discuss the event on 2020-04-13.&lt;br /&gt;
* We hosted our event website on the OSGeo:UK site at GitHub.&lt;br /&gt;
* We used Google forms for the call for papers and for a request for volunteers&lt;br /&gt;
&lt;br /&gt;
=== Hosts and co-hosts ===&lt;br /&gt;
&lt;br /&gt;
* For each stream of the event we had a host (one of the organising team + Nick Bearman) and co-host (volunteers).&lt;br /&gt;
* The [https://docs.google.com/document/d/1hlNl1EhbWa4ZjpXvsxz_V9Rid2VpIPmcnKBQ5089Jkg/edit?usp=sharing Host Guide] provided detailed guidance for hosts and co-hosts on how to run the session on zoom, detailed settings and what to do in the event of a code of conduct violation or other issue. This doc evolved as we ran a couple of trial sessions with volunteers.&lt;br /&gt;
&lt;br /&gt;
=== Recording and publishing ===&lt;br /&gt;
&lt;br /&gt;
automatic recording helps&lt;br /&gt;
&lt;br /&gt;
=== What worked ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
=== What didn't work ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
== What would we try to do if we ran another event? ==&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124861</id>
		<title>FOSS4GUK 2020 Online - Lessons Learnt</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124861"/>
		<updated>2020-06-23T11:39:45Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: /* Delegates */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''This is a draft at the moment!'''&lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
&lt;br /&gt;
[https://uk.osgeo.org/foss4gukonline2020/ FOSS4GUK 2020 Online] was hosted by the [https://uk.osgeo.org OSGeo:UK] committee on 17th June 2020 from 9.00am to 17.30pm UTC+1&lt;br /&gt;
&lt;br /&gt;
The event was free to attend with all of the costs (see below) funded from OSGeo:UK reserves. &lt;br /&gt;
&lt;br /&gt;
=== Delegates ===&lt;br /&gt;
&lt;br /&gt;
* 1,000 people registered&lt;br /&gt;
* We estimate that between 500 and 600 attended&lt;br /&gt;
* Maximum number online at any time was 460, minimum was 205&lt;br /&gt;
* Delegates from 77 countries&lt;br /&gt;
** 48% from GB, 8% US, 4% India&lt;br /&gt;
&lt;br /&gt;
[[File:FOSS4GUK Attendee Countries.png|frameless]]&lt;br /&gt;
&lt;br /&gt;
=== [https://uk.osgeo.org/foss4gukonline2020/programme.html Programme] ===&lt;br /&gt;
&lt;br /&gt;
* 3 streams running for the whole day (except during keynotes)&lt;br /&gt;
** 2 keynotes&lt;br /&gt;
** 29 talks and demos&lt;br /&gt;
** 4 Lightning talks&lt;br /&gt;
* 38 Speakers (10 women)&lt;br /&gt;
* Coffee bar stream where delegates could hang out and chat (not heavily used)&lt;br /&gt;
&lt;br /&gt;
=== Finances ===&lt;br /&gt;
* The only costs were the fees for the zoom account for 1 month: £198&lt;br /&gt;
* Delegate donations:&lt;br /&gt;
** OSGeo:UK 63 individual donations - gross £1,810, net after Paypal fees £1,744 (as of 2020-06-20)&lt;br /&gt;
** MapAction ?&lt;br /&gt;
&lt;br /&gt;
== Feedback ==&lt;br /&gt;
&lt;br /&gt;
As of 2020-06-22 we had 210 feedback responses:&lt;br /&gt;
* 95% rated the event experience very good or excellent&lt;br /&gt;
* 93% were happy with the technology platform&lt;br /&gt;
* 27% attended for the whole day, 27% attended 7-11 sessions, 45% attended 2-6 sessions&lt;br /&gt;
* 16% used the coffee bar&lt;br /&gt;
* 47% of respondents (but not attendees) made a donation to OSGeo:UK (34%) or MapAction (13%). The average donation was ca £20&lt;br /&gt;
[[File:FOSS4GUK Satisfaction.png|frameless]]&lt;br /&gt;
[[File:FOSS4GUK Technology satisfaction.png|frameless]]&lt;br /&gt;
[[File:FOSS4GUK No of sessions attended.png|frameless]]&lt;br /&gt;
&lt;br /&gt;
== Tech and tools ==&lt;br /&gt;
&lt;br /&gt;
=== Choice of video conferencing platform ===&lt;br /&gt;
&lt;br /&gt;
==== We considered ====&lt;br /&gt;
&lt;br /&gt;
* webex (we had an offer of a free account from a sponsor) - problems with audio, uncertain linux support, limit on numbers&lt;br /&gt;
* hopin.to - a virtual conference application, unfortunately the demo the we attended was not successful and we did not feel comfortable taking the risk on a new service but it looks promising for the future&lt;br /&gt;
* several other services that did not seem to fit our needs&lt;br /&gt;
* jitsi - our experience of using the free hosted version left us uncomfortable with jitsi as platform for a large event with 3 streams. None of us had the experience or access to hardware and bandwidth to consider running a large self-hosted version of jitsi. We were also concerned about how we could control access or restrict anyone breaching our CoC&lt;br /&gt;
* several of us had experience of running large meetings on zoom and were confident that we could host the event on zoom and leverage it's capabilities.&lt;br /&gt;
&lt;br /&gt;
==== What we learnt ====&lt;br /&gt;
&lt;br /&gt;
* zoom worked as anticipated. We had no major technical problems and as far as we know very few participants experienced problems, zoom offers clients for Linux, Mac and Windows, iOS and Android.&lt;br /&gt;
* we were able to manage participants by muting everyone on entry and restricting chat within the app to messages to one of the hosts and from the hosts to the whole audience.&lt;br /&gt;
* the recording worked well, a co-host was asked to remind the host to start and stop the recording for each session to keep videos at a manageable size&lt;br /&gt;
* we saved all of the chat transcripts as part of our CoC policy (fortunately unnecessary)&lt;br /&gt;
&lt;br /&gt;
We purchased:&lt;br /&gt;
* 1 account for up to 1,000 people for the keynotes&lt;br /&gt;
* 2 accounts for up to 500 people for the other streams&lt;br /&gt;
* 1 account for up to 100 people for the coffee bar&lt;br /&gt;
* An add on for large cloud storage for all of the video recordings&lt;br /&gt;
* '''Total cost £198''' (a month's licenses)&lt;br /&gt;
&lt;br /&gt;
We over-provisioned because we did not know how many people would actually log-in. We could have managed with smaller accounts and saved some money.&lt;br /&gt;
&lt;br /&gt;
It is unclear whether we would have been better off purchasing zoom webinar licenses rather than large meetings.&lt;br /&gt;
&lt;br /&gt;
We were aware that the zoom meetings could have been streamed to youtube but we did not see any significant benefit from doing that.&lt;br /&gt;
&lt;br /&gt;
==== Options for the future ====&lt;br /&gt;
&lt;br /&gt;
We have received some retrospective suggestions for alternative tech approaches to running an online event. Hopefully others will be inspired to run further online FOSS4G events and they will experiment with these.&lt;br /&gt;
&lt;br /&gt;
Our choices were based on a need for a low effort tech approach given our small team and pressures on our time. Despite the poor publicity that zoom had received re security during the COVID crisis we found that the security features available were sufficient for our needs.&lt;br /&gt;
&lt;br /&gt;
=== Eventbrite ===&lt;br /&gt;
&lt;br /&gt;
We used eventbrite for our registration system. &lt;br /&gt;
&lt;br /&gt;
* It was free as the event was a free event, if we had charged £10 per registration we would have incurred cost including credit card fees of about 10%&lt;br /&gt;
* Eventbrite has an online event page which is only accessible to people who have registered, we only exposed the links to the conference streams via this page to minimise the risks of being overloaded or trolled.&lt;br /&gt;
* We added a registration question to request permission to add registrants to the global FOSS4G mailing list (we had a very high acceptance rate). '''This should be highly recommended practice for future FOSS4Gs'''&lt;br /&gt;
* We made the completion of a company address mandatory on registration because it forced people to provide their 2 digit country code which enabled us to analyse the locations of registrants. This will enable future FOSS4G to geographically segment the audience.&lt;br /&gt;
* We used the attendee mailing features to send a a series of emails to participants in the build up and post event. Its a bit clunky but it works fine and avoided having to maintain an alternative email list.&lt;br /&gt;
&lt;br /&gt;
=== WhatsAppp ===&lt;br /&gt;
&lt;br /&gt;
We used WhatsApp for team communications in the build up and on the day. We also had a group for our volunteers and were able to share updates with the volunteers before the event and it was the main channel of communication on the day&lt;br /&gt;
&lt;br /&gt;
We could have considered a speakers group in addition.&lt;br /&gt;
&lt;br /&gt;
=== Twitter ===&lt;br /&gt;
&lt;br /&gt;
We used twitter as our main channel for publicity prior to the event. It is important to recognise that not everyone is on twitter, future events should consider what other channels to use for communication with potential participants.&lt;br /&gt;
&lt;br /&gt;
We used twitter on the day for announcements, publicity and encouraged the participants to chat via twitter.&lt;br /&gt;
&lt;br /&gt;
== Event structure ==&lt;br /&gt;
&lt;br /&gt;
3 streams plus coffee bar, describe how it worked&lt;br /&gt;
&lt;br /&gt;
Link to programme&lt;br /&gt;
&lt;br /&gt;
=== Hosts and co-hosts ===&lt;br /&gt;
&lt;br /&gt;
Link to Guide&lt;br /&gt;
&lt;br /&gt;
=== Recording and publishing ===&lt;br /&gt;
&lt;br /&gt;
automatic recording helps&lt;br /&gt;
&lt;br /&gt;
=== What worked ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
=== What didn't work ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
== What would we try to do if we ran another event? ==&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=File:FOSS4GUK_Attendee_Countries.png&amp;diff=124860</id>
		<title>File:FOSS4GUK Attendee Countries.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=File:FOSS4GUK_Attendee_Countries.png&amp;diff=124860"/>
		<updated>2020-06-23T11:39:29Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Feedback survey&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124859</id>
		<title>FOSS4GUK 2020 Online - Lessons Learnt</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124859"/>
		<updated>2020-06-23T11:38:02Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''This is a draft at the moment!'''&lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
&lt;br /&gt;
[https://uk.osgeo.org/foss4gukonline2020/ FOSS4GUK 2020 Online] was hosted by the [https://uk.osgeo.org OSGeo:UK] committee on 17th June 2020 from 9.00am to 17.30pm UTC+1&lt;br /&gt;
&lt;br /&gt;
The event was free to attend with all of the costs (see below) funded from OSGeo:UK reserves. &lt;br /&gt;
&lt;br /&gt;
=== Delegates ===&lt;br /&gt;
&lt;br /&gt;
* 1,000 people registered&lt;br /&gt;
* We estimate that between 500 and 600 attended&lt;br /&gt;
* Maximum number online at any time was 460, minimum was 205&lt;br /&gt;
* Delegates from 77 countries&lt;br /&gt;
** 48% from GB, 8% US, 4% India&lt;br /&gt;
&lt;br /&gt;
=== [https://uk.osgeo.org/foss4gukonline2020/programme.html Programme] ===&lt;br /&gt;
&lt;br /&gt;
* 3 streams running for the whole day (except during keynotes)&lt;br /&gt;
** 2 keynotes&lt;br /&gt;
** 29 talks and demos&lt;br /&gt;
** 4 Lightning talks&lt;br /&gt;
* 38 Speakers (10 women)&lt;br /&gt;
* Coffee bar stream where delegates could hang out and chat (not heavily used)&lt;br /&gt;
&lt;br /&gt;
=== Finances ===&lt;br /&gt;
* The only costs were the fees for the zoom account for 1 month: £198&lt;br /&gt;
* Delegate donations:&lt;br /&gt;
** OSGeo:UK 63 individual donations - gross £1,810, net after Paypal fees £1,744 (as of 2020-06-20)&lt;br /&gt;
** MapAction ?&lt;br /&gt;
&lt;br /&gt;
== Feedback ==&lt;br /&gt;
&lt;br /&gt;
As of 2020-06-22 we had 210 feedback responses:&lt;br /&gt;
* 95% rated the event experience very good or excellent&lt;br /&gt;
* 93% were happy with the technology platform&lt;br /&gt;
* 27% attended for the whole day, 27% attended 7-11 sessions, 45% attended 2-6 sessions&lt;br /&gt;
* 16% used the coffee bar&lt;br /&gt;
* 47% of respondents (but not attendees) made a donation to OSGeo:UK (34%) or MapAction (13%). The average donation was ca £20&lt;br /&gt;
[[File:FOSS4GUK Satisfaction.png|frameless]]&lt;br /&gt;
[[File:FOSS4GUK Technology satisfaction.png|frameless]]&lt;br /&gt;
[[File:FOSS4GUK No of sessions attended.png|frameless]]&lt;br /&gt;
&lt;br /&gt;
== Tech and tools ==&lt;br /&gt;
&lt;br /&gt;
=== Choice of video conferencing platform ===&lt;br /&gt;
&lt;br /&gt;
==== We considered ====&lt;br /&gt;
&lt;br /&gt;
* webex (we had an offer of a free account from a sponsor) - problems with audio, uncertain linux support, limit on numbers&lt;br /&gt;
* hopin.to - a virtual conference application, unfortunately the demo the we attended was not successful and we did not feel comfortable taking the risk on a new service but it looks promising for the future&lt;br /&gt;
* several other services that did not seem to fit our needs&lt;br /&gt;
* jitsi - our experience of using the free hosted version left us uncomfortable with jitsi as platform for a large event with 3 streams. None of us had the experience or access to hardware and bandwidth to consider running a large self-hosted version of jitsi. We were also concerned about how we could control access or restrict anyone breaching our CoC&lt;br /&gt;
* several of us had experience of running large meetings on zoom and were confident that we could host the event on zoom and leverage it's capabilities.&lt;br /&gt;
&lt;br /&gt;
==== What we learnt ====&lt;br /&gt;
&lt;br /&gt;
* zoom worked as anticipated. We had no major technical problems and as far as we know very few participants experienced problems, zoom offers clients for Linux, Mac and Windows, iOS and Android.&lt;br /&gt;
* we were able to manage participants by muting everyone on entry and restricting chat within the app to messages to one of the hosts and from the hosts to the whole audience.&lt;br /&gt;
* the recording worked well, a co-host was asked to remind the host to start and stop the recording for each session to keep videos at a manageable size&lt;br /&gt;
* we saved all of the chat transcripts as part of our CoC policy (fortunately unnecessary)&lt;br /&gt;
&lt;br /&gt;
We purchased:&lt;br /&gt;
* 1 account for up to 1,000 people for the keynotes&lt;br /&gt;
* 2 accounts for up to 500 people for the other streams&lt;br /&gt;
* 1 account for up to 100 people for the coffee bar&lt;br /&gt;
* An add on for large cloud storage for all of the video recordings&lt;br /&gt;
* '''Total cost £198''' (a month's licenses)&lt;br /&gt;
&lt;br /&gt;
We over-provisioned because we did not know how many people would actually log-in. We could have managed with smaller accounts and saved some money.&lt;br /&gt;
&lt;br /&gt;
It is unclear whether we would have been better off purchasing zoom webinar licenses rather than large meetings.&lt;br /&gt;
&lt;br /&gt;
We were aware that the zoom meetings could have been streamed to youtube but we did not see any significant benefit from doing that.&lt;br /&gt;
&lt;br /&gt;
==== Options for the future ====&lt;br /&gt;
&lt;br /&gt;
We have received some retrospective suggestions for alternative tech approaches to running an online event. Hopefully others will be inspired to run further online FOSS4G events and they will experiment with these.&lt;br /&gt;
&lt;br /&gt;
Our choices were based on a need for a low effort tech approach given our small team and pressures on our time. Despite the poor publicity that zoom had received re security during the COVID crisis we found that the security features available were sufficient for our needs.&lt;br /&gt;
&lt;br /&gt;
=== Eventbrite ===&lt;br /&gt;
&lt;br /&gt;
We used eventbrite for our registration system. &lt;br /&gt;
&lt;br /&gt;
* It was free as the event was a free event, if we had charged £10 per registration we would have incurred cost including credit card fees of about 10%&lt;br /&gt;
* Eventbrite has an online event page which is only accessible to people who have registered, we only exposed the links to the conference streams via this page to minimise the risks of being overloaded or trolled.&lt;br /&gt;
* We added a registration question to request permission to add registrants to the global FOSS4G mailing list (we had a very high acceptance rate). '''This should be highly recommended practice for future FOSS4Gs'''&lt;br /&gt;
* We made the completion of a company address mandatory on registration because it forced people to provide their 2 digit country code which enabled us to analyse the locations of registrants. This will enable future FOSS4G to geographically segment the audience.&lt;br /&gt;
* We used the attendee mailing features to send a a series of emails to participants in the build up and post event. Its a bit clunky but it works fine and avoided having to maintain an alternative email list.&lt;br /&gt;
&lt;br /&gt;
=== WhatsAppp ===&lt;br /&gt;
&lt;br /&gt;
We used WhatsApp for team communications in the build up and on the day. We also had a group for our volunteers and were able to share updates with the volunteers before the event and it was the main channel of communication on the day&lt;br /&gt;
&lt;br /&gt;
We could have considered a speakers group in addition.&lt;br /&gt;
&lt;br /&gt;
=== Twitter ===&lt;br /&gt;
&lt;br /&gt;
We used twitter as our main channel for publicity prior to the event. It is important to recognise that not everyone is on twitter, future events should consider what other channels to use for communication with potential participants.&lt;br /&gt;
&lt;br /&gt;
We used twitter on the day for announcements, publicity and encouraged the participants to chat via twitter.&lt;br /&gt;
&lt;br /&gt;
== Event structure ==&lt;br /&gt;
&lt;br /&gt;
3 streams plus coffee bar, describe how it worked&lt;br /&gt;
&lt;br /&gt;
Link to programme&lt;br /&gt;
&lt;br /&gt;
=== Hosts and co-hosts ===&lt;br /&gt;
&lt;br /&gt;
Link to Guide&lt;br /&gt;
&lt;br /&gt;
=== Recording and publishing ===&lt;br /&gt;
&lt;br /&gt;
automatic recording helps&lt;br /&gt;
&lt;br /&gt;
=== What worked ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
=== What didn't work ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
== What would we try to do if we ran another event? ==&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124858</id>
		<title>FOSS4GUK 2020 Online - Lessons Learnt</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124858"/>
		<updated>2020-06-23T11:37:30Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: /* Feedback */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''This is a draft at the moment!'''&lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
&lt;br /&gt;
[https://uk.osgeo.org/foss4gukonline2020/ FOSS4GUK 2020 Online] was hosted by the [https://uk.osgeo.org OSGeo:UK] committee on 17th June 2020 from 9.00am to 17.30pm UTC+1&lt;br /&gt;
&lt;br /&gt;
The event was free to attend with all of the costs (see below) funded from OSGeo:UK reserves. &lt;br /&gt;
&lt;br /&gt;
=== Delegates ===&lt;br /&gt;
&lt;br /&gt;
* 1,000 people registered&lt;br /&gt;
* We estimate that between 500 and 600 attended&lt;br /&gt;
* Maximum number online at any time was 460, minimum was 205&lt;br /&gt;
* Delegates from 77 countries&lt;br /&gt;
** 48% from GB, 8% US, 4% India&lt;br /&gt;
&lt;br /&gt;
=== [https://uk.osgeo.org/foss4gukonline2020/programme.html Programme] ===&lt;br /&gt;
&lt;br /&gt;
* 3 streams running for the whole day (except during keynotes)&lt;br /&gt;
** 2 keynotes&lt;br /&gt;
** 29 talks and demos&lt;br /&gt;
** 4 Lightning talks&lt;br /&gt;
* 38 Speakers (10 women)&lt;br /&gt;
* Coffee bar stream where delegates could hang out and chat (not heavily used)&lt;br /&gt;
&lt;br /&gt;
=== Finances ===&lt;br /&gt;
* The only costs were the fees for the zoom account for 1 month: £198&lt;br /&gt;
* Delegate donations:&lt;br /&gt;
** OSGeo:UK 63 individual donations - gross £1,810, net after Paypal fees £1,744 (as of 2020-06-20)&lt;br /&gt;
** MapAction ?&lt;br /&gt;
&lt;br /&gt;
[[File:FOSS4GUK No of sessions attended.png|frameless]]&lt;br /&gt;
== Feedback ==&lt;br /&gt;
&lt;br /&gt;
As of 2020-06-22 we had 210 feedback responses:&lt;br /&gt;
* 95% rated the event experience very good or excellent&lt;br /&gt;
* 93% were happy with the technology platform&lt;br /&gt;
* 27% attended for the whole day, 27% attended 7-11 sessions, 45% attended 2-6 sessions&lt;br /&gt;
* 16% used the coffee bar&lt;br /&gt;
* 47% of respondents (but not attendees) made a donation to OSGeo:UK (34%) or MapAction (13%). The average donation was ca £20&lt;br /&gt;
[[File:FOSS4GUK Satisfaction.png|frameless]]&lt;br /&gt;
[[File:FOSS4GUK Technology satisfaction.png|frameless]]&lt;br /&gt;
&lt;br /&gt;
== Tech and tools ==&lt;br /&gt;
&lt;br /&gt;
=== Choice of video conferencing platform ===&lt;br /&gt;
&lt;br /&gt;
==== We considered ====&lt;br /&gt;
&lt;br /&gt;
* webex (we had an offer of a free account from a sponsor) - problems with audio, uncertain linux support, limit on numbers&lt;br /&gt;
* hopin.to - a virtual conference application, unfortunately the demo the we attended was not successful and we did not feel comfortable taking the risk on a new service but it looks promising for the future&lt;br /&gt;
* several other services that did not seem to fit our needs&lt;br /&gt;
* jitsi - our experience of using the free hosted version left us uncomfortable with jitsi as platform for a large event with 3 streams. None of us had the experience or access to hardware and bandwidth to consider running a large self-hosted version of jitsi. We were also concerned about how we could control access or restrict anyone breaching our CoC&lt;br /&gt;
* several of us had experience of running large meetings on zoom and were confident that we could host the event on zoom and leverage it's capabilities.&lt;br /&gt;
&lt;br /&gt;
==== What we learnt ====&lt;br /&gt;
&lt;br /&gt;
* zoom worked as anticipated. We had no major technical problems and as far as we know very few participants experienced problems, zoom offers clients for Linux, Mac and Windows, iOS and Android.&lt;br /&gt;
* we were able to manage participants by muting everyone on entry and restricting chat within the app to messages to one of the hosts and from the hosts to the whole audience.&lt;br /&gt;
* the recording worked well, a co-host was asked to remind the host to start and stop the recording for each session to keep videos at a manageable size&lt;br /&gt;
* we saved all of the chat transcripts as part of our CoC policy (fortunately unnecessary)&lt;br /&gt;
&lt;br /&gt;
We purchased:&lt;br /&gt;
* 1 account for up to 1,000 people for the keynotes&lt;br /&gt;
* 2 accounts for up to 500 people for the other streams&lt;br /&gt;
* 1 account for up to 100 people for the coffee bar&lt;br /&gt;
* An add on for large cloud storage for all of the video recordings&lt;br /&gt;
* '''Total cost £198''' (a month's licenses)&lt;br /&gt;
&lt;br /&gt;
We over-provisioned because we did not know how many people would actually log-in. We could have managed with smaller accounts and saved some money.&lt;br /&gt;
&lt;br /&gt;
It is unclear whether we would have been better off purchasing zoom webinar licenses rather than large meetings.&lt;br /&gt;
&lt;br /&gt;
We were aware that the zoom meetings could have been streamed to youtube but we did not see any significant benefit from doing that.&lt;br /&gt;
&lt;br /&gt;
==== Options for the future ====&lt;br /&gt;
&lt;br /&gt;
We have received some retrospective suggestions for alternative tech approaches to running an online event. Hopefully others will be inspired to run further online FOSS4G events and they will experiment with these.&lt;br /&gt;
&lt;br /&gt;
Our choices were based on a need for a low effort tech approach given our small team and pressures on our time. Despite the poor publicity that zoom had received re security during the COVID crisis we found that the security features available were sufficient for our needs.&lt;br /&gt;
&lt;br /&gt;
=== Eventbrite ===&lt;br /&gt;
&lt;br /&gt;
We used eventbrite for our registration system. &lt;br /&gt;
&lt;br /&gt;
* It was free as the event was a free event, if we had charged £10 per registration we would have incurred cost including credit card fees of about 10%&lt;br /&gt;
* Eventbrite has an online event page which is only accessible to people who have registered, we only exposed the links to the conference streams via this page to minimise the risks of being overloaded or trolled.&lt;br /&gt;
* We added a registration question to request permission to add registrants to the global FOSS4G mailing list (we had a very high acceptance rate). '''This should be highly recommended practice for future FOSS4Gs'''&lt;br /&gt;
* We made the completion of a company address mandatory on registration because it forced people to provide their 2 digit country code which enabled us to analyse the locations of registrants. This will enable future FOSS4G to geographically segment the audience.&lt;br /&gt;
* We used the attendee mailing features to send a a series of emails to participants in the build up and post event. Its a bit clunky but it works fine and avoided having to maintain an alternative email list.&lt;br /&gt;
&lt;br /&gt;
=== WhatsAppp ===&lt;br /&gt;
&lt;br /&gt;
We used WhatsApp for team communications in the build up and on the day. We also had a group for our volunteers and were able to share updates with the volunteers before the event and it was the main channel of communication on the day&lt;br /&gt;
&lt;br /&gt;
We could have considered a speakers group in addition.&lt;br /&gt;
&lt;br /&gt;
=== Twitter ===&lt;br /&gt;
&lt;br /&gt;
We used twitter as our main channel for publicity prior to the event. It is important to recognise that not everyone is on twitter, future events should consider what other channels to use for communication with potential participants.&lt;br /&gt;
&lt;br /&gt;
We used twitter on the day for announcements, publicity and encouraged the participants to chat via twitter.&lt;br /&gt;
&lt;br /&gt;
== Event structure ==&lt;br /&gt;
&lt;br /&gt;
3 streams plus coffee bar, describe how it worked&lt;br /&gt;
&lt;br /&gt;
Link to programme&lt;br /&gt;
&lt;br /&gt;
=== Hosts and co-hosts ===&lt;br /&gt;
&lt;br /&gt;
Link to Guide&lt;br /&gt;
&lt;br /&gt;
=== Recording and publishing ===&lt;br /&gt;
&lt;br /&gt;
automatic recording helps&lt;br /&gt;
&lt;br /&gt;
=== What worked ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
=== What didn't work ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
== What would we try to do if we ran another event? ==&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=File:FOSS4GUK_No_of_sessions_attended.png&amp;diff=124857</id>
		<title>File:FOSS4GUK No of sessions attended.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=File:FOSS4GUK_No_of_sessions_attended.png&amp;diff=124857"/>
		<updated>2020-06-23T11:37:14Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Feedback survey&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124856</id>
		<title>FOSS4GUK 2020 Online - Lessons Learnt</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124856"/>
		<updated>2020-06-23T11:35:40Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: /* Feedback */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''This is a draft at the moment!'''&lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
&lt;br /&gt;
[https://uk.osgeo.org/foss4gukonline2020/ FOSS4GUK 2020 Online] was hosted by the [https://uk.osgeo.org OSGeo:UK] committee on 17th June 2020 from 9.00am to 17.30pm UTC+1&lt;br /&gt;
&lt;br /&gt;
The event was free to attend with all of the costs (see below) funded from OSGeo:UK reserves. &lt;br /&gt;
&lt;br /&gt;
=== Delegates ===&lt;br /&gt;
&lt;br /&gt;
* 1,000 people registered&lt;br /&gt;
* We estimate that between 500 and 600 attended&lt;br /&gt;
* Maximum number online at any time was 460, minimum was 205&lt;br /&gt;
* Delegates from 77 countries&lt;br /&gt;
** 48% from GB, 8% US, 4% India&lt;br /&gt;
&lt;br /&gt;
=== [https://uk.osgeo.org/foss4gukonline2020/programme.html Programme] ===&lt;br /&gt;
&lt;br /&gt;
* 3 streams running for the whole day (except during keynotes)&lt;br /&gt;
** 2 keynotes&lt;br /&gt;
** 29 talks and demos&lt;br /&gt;
** 4 Lightning talks&lt;br /&gt;
* 38 Speakers (10 women)&lt;br /&gt;
* Coffee bar stream where delegates could hang out and chat (not heavily used)&lt;br /&gt;
&lt;br /&gt;
=== Finances ===&lt;br /&gt;
* The only costs were the fees for the zoom account for 1 month: £198&lt;br /&gt;
* Delegate donations:&lt;br /&gt;
** OSGeo:UK 63 individual donations - gross £1,810, net after Paypal fees £1,744 (as of 2020-06-20)&lt;br /&gt;
** MapAction ?&lt;br /&gt;
&lt;br /&gt;
== Feedback ==&lt;br /&gt;
&lt;br /&gt;
As of 2020-06-22 we had 210 feedback responses:&lt;br /&gt;
* 95% rated the event experience very good or excellent&lt;br /&gt;
* 93% were happy with the technology platform&lt;br /&gt;
* 27% attended for the whole day, 27% attended 7-11 sessions, 45% attended 2-6 sessions&lt;br /&gt;
* 16% used the coffee bar&lt;br /&gt;
* 47% of respondents (but not attendees) made a donation to OSGeo:UK (34%) or MapAction (13%). The average donation was ca £20&lt;br /&gt;
[[File:FOSS4GUK Satisfaction.png|frameless]]&lt;br /&gt;
[[File:FOSS4GUK Technology satisfaction.png|frameless]]&lt;br /&gt;
&lt;br /&gt;
== Tech and tools ==&lt;br /&gt;
&lt;br /&gt;
=== Choice of video conferencing platform ===&lt;br /&gt;
&lt;br /&gt;
==== We considered ====&lt;br /&gt;
&lt;br /&gt;
* webex (we had an offer of a free account from a sponsor) - problems with audio, uncertain linux support, limit on numbers&lt;br /&gt;
* hopin.to - a virtual conference application, unfortunately the demo the we attended was not successful and we did not feel comfortable taking the risk on a new service but it looks promising for the future&lt;br /&gt;
* several other services that did not seem to fit our needs&lt;br /&gt;
* jitsi - our experience of using the free hosted version left us uncomfortable with jitsi as platform for a large event with 3 streams. None of us had the experience or access to hardware and bandwidth to consider running a large self-hosted version of jitsi. We were also concerned about how we could control access or restrict anyone breaching our CoC&lt;br /&gt;
* several of us had experience of running large meetings on zoom and were confident that we could host the event on zoom and leverage it's capabilities.&lt;br /&gt;
&lt;br /&gt;
==== What we learnt ====&lt;br /&gt;
&lt;br /&gt;
* zoom worked as anticipated. We had no major technical problems and as far as we know very few participants experienced problems, zoom offers clients for Linux, Mac and Windows, iOS and Android.&lt;br /&gt;
* we were able to manage participants by muting everyone on entry and restricting chat within the app to messages to one of the hosts and from the hosts to the whole audience.&lt;br /&gt;
* the recording worked well, a co-host was asked to remind the host to start and stop the recording for each session to keep videos at a manageable size&lt;br /&gt;
* we saved all of the chat transcripts as part of our CoC policy (fortunately unnecessary)&lt;br /&gt;
&lt;br /&gt;
We purchased:&lt;br /&gt;
* 1 account for up to 1,000 people for the keynotes&lt;br /&gt;
* 2 accounts for up to 500 people for the other streams&lt;br /&gt;
* 1 account for up to 100 people for the coffee bar&lt;br /&gt;
* An add on for large cloud storage for all of the video recordings&lt;br /&gt;
* '''Total cost £198''' (a month's licenses)&lt;br /&gt;
&lt;br /&gt;
We over-provisioned because we did not know how many people would actually log-in. We could have managed with smaller accounts and saved some money.&lt;br /&gt;
&lt;br /&gt;
It is unclear whether we would have been better off purchasing zoom webinar licenses rather than large meetings.&lt;br /&gt;
&lt;br /&gt;
We were aware that the zoom meetings could have been streamed to youtube but we did not see any significant benefit from doing that.&lt;br /&gt;
&lt;br /&gt;
==== Options for the future ====&lt;br /&gt;
&lt;br /&gt;
We have received some retrospective suggestions for alternative tech approaches to running an online event. Hopefully others will be inspired to run further online FOSS4G events and they will experiment with these.&lt;br /&gt;
&lt;br /&gt;
Our choices were based on a need for a low effort tech approach given our small team and pressures on our time. Despite the poor publicity that zoom had received re security during the COVID crisis we found that the security features available were sufficient for our needs.&lt;br /&gt;
&lt;br /&gt;
=== Eventbrite ===&lt;br /&gt;
&lt;br /&gt;
We used eventbrite for our registration system. &lt;br /&gt;
&lt;br /&gt;
* It was free as the event was a free event, if we had charged £10 per registration we would have incurred cost including credit card fees of about 10%&lt;br /&gt;
* Eventbrite has an online event page which is only accessible to people who have registered, we only exposed the links to the conference streams via this page to minimise the risks of being overloaded or trolled.&lt;br /&gt;
* We added a registration question to request permission to add registrants to the global FOSS4G mailing list (we had a very high acceptance rate). '''This should be highly recommended practice for future FOSS4Gs'''&lt;br /&gt;
* We made the completion of a company address mandatory on registration because it forced people to provide their 2 digit country code which enabled us to analyse the locations of registrants. This will enable future FOSS4G to geographically segment the audience.&lt;br /&gt;
* We used the attendee mailing features to send a a series of emails to participants in the build up and post event. Its a bit clunky but it works fine and avoided having to maintain an alternative email list.&lt;br /&gt;
&lt;br /&gt;
=== WhatsAppp ===&lt;br /&gt;
&lt;br /&gt;
We used WhatsApp for team communications in the build up and on the day. We also had a group for our volunteers and were able to share updates with the volunteers before the event and it was the main channel of communication on the day&lt;br /&gt;
&lt;br /&gt;
We could have considered a speakers group in addition.&lt;br /&gt;
&lt;br /&gt;
=== Twitter ===&lt;br /&gt;
&lt;br /&gt;
We used twitter as our main channel for publicity prior to the event. It is important to recognise that not everyone is on twitter, future events should consider what other channels to use for communication with potential participants.&lt;br /&gt;
&lt;br /&gt;
We used twitter on the day for announcements, publicity and encouraged the participants to chat via twitter.&lt;br /&gt;
&lt;br /&gt;
== Event structure ==&lt;br /&gt;
&lt;br /&gt;
3 streams plus coffee bar, describe how it worked&lt;br /&gt;
&lt;br /&gt;
Link to programme&lt;br /&gt;
&lt;br /&gt;
=== Hosts and co-hosts ===&lt;br /&gt;
&lt;br /&gt;
Link to Guide&lt;br /&gt;
&lt;br /&gt;
=== Recording and publishing ===&lt;br /&gt;
&lt;br /&gt;
automatic recording helps&lt;br /&gt;
&lt;br /&gt;
=== What worked ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
=== What didn't work ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
== What would we try to do if we ran another event? ==&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=File:FOSS4GUK_Technology_satisfaction.png&amp;diff=124855</id>
		<title>File:FOSS4GUK Technology satisfaction.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=File:FOSS4GUK_Technology_satisfaction.png&amp;diff=124855"/>
		<updated>2020-06-23T11:34:23Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;From feedback survey&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=File:FOSS4GUK_Satisfaction.png&amp;diff=124854</id>
		<title>File:FOSS4GUK Satisfaction.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=File:FOSS4GUK_Satisfaction.png&amp;diff=124854"/>
		<updated>2020-06-23T11:33:14Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;From feedback survey&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124853</id>
		<title>FOSS4GUK 2020 Online - Lessons Learnt</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124853"/>
		<updated>2020-06-22T19:56:49Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: Feedback&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''This is a draft at the moment!'''&lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
&lt;br /&gt;
[https://uk.osgeo.org/foss4gukonline2020/ FOSS4GUK 2020 Online] was hosted by the [https://uk.osgeo.org OSGeo:UK] committee on 17th June 2020 from 9.00am to 17.30pm UTC+1&lt;br /&gt;
&lt;br /&gt;
The event was free to attend with all of the costs (see below) funded from OSGeo:UK reserves. &lt;br /&gt;
&lt;br /&gt;
=== Delegates ===&lt;br /&gt;
&lt;br /&gt;
* 1,000 people registered&lt;br /&gt;
* We estimate that between 500 and 600 attended&lt;br /&gt;
* Maximum number online at any time was 460, minimum was 205&lt;br /&gt;
* Delegates from 77 countries&lt;br /&gt;
** 48% from GB, 8% US, 4% India&lt;br /&gt;
&lt;br /&gt;
=== [https://uk.osgeo.org/foss4gukonline2020/programme.html Programme] ===&lt;br /&gt;
&lt;br /&gt;
* 3 streams running for the whole day (except during keynotes)&lt;br /&gt;
** 2 keynotes&lt;br /&gt;
** 29 talks and demos&lt;br /&gt;
** 4 Lightning talks&lt;br /&gt;
* 38 Speakers (10 women)&lt;br /&gt;
* Coffee bar stream where delegates could hang out and chat (not heavily used)&lt;br /&gt;
&lt;br /&gt;
=== Finances ===&lt;br /&gt;
* The only costs were the fees for the zoom account for 1 month: £198&lt;br /&gt;
* Delegate donations:&lt;br /&gt;
** OSGeo:UK 63 individual donations - gross £1,810, net after Paypal fees £1,744 (as of 2020-06-20)&lt;br /&gt;
** MapAction ?&lt;br /&gt;
&lt;br /&gt;
== Feedback ==&lt;br /&gt;
&lt;br /&gt;
As of 2020-06-22 we had 210 feedback responses:&lt;br /&gt;
* 95% rated the event experience very good or excellent&lt;br /&gt;
* 93% were happy with the technology platform&lt;br /&gt;
* 27% attended for the whole day, 27% attended 7-11 sessions, 45% attended 2-6 sessions&lt;br /&gt;
* 16% used the coffee bar&lt;br /&gt;
* 47% of respondents (but not attendees) made a donation to OSGeo:UK (34%) or MapAction (13%). The average donation was ca £20&lt;br /&gt;
&lt;br /&gt;
== Tech and tools ==&lt;br /&gt;
&lt;br /&gt;
=== Choice of video conferencing platform ===&lt;br /&gt;
&lt;br /&gt;
==== We considered ====&lt;br /&gt;
&lt;br /&gt;
* webex (we had an offer of a free account from a sponsor) - problems with audio, uncertain linux support, limit on numbers&lt;br /&gt;
* hopin.to - a virtual conference application, unfortunately the demo the we attended was not successful and we did not feel comfortable taking the risk on a new service but it looks promising for the future&lt;br /&gt;
* several other services that did not seem to fit our needs&lt;br /&gt;
* jitsi - our experience of using the free hosted version left us uncomfortable with jitsi as platform for a large event with 3 streams. None of us had the experience or access to hardware and bandwidth to consider running a large self-hosted version of jitsi. We were also concerned about how we could control access or restrict anyone breaching our CoC&lt;br /&gt;
* several of us had experience of running large meetings on zoom and were confident that we could host the event on zoom and leverage it's capabilities.&lt;br /&gt;
&lt;br /&gt;
==== What we learnt ====&lt;br /&gt;
&lt;br /&gt;
* zoom worked as anticipated. We had no major technical problems and as far as we know very few participants experienced problems, zoom offers clients for Linux, Mac and Windows, iOS and Android.&lt;br /&gt;
* we were able to manage participants by muting everyone on entry and restricting chat within the app to messages to one of the hosts and from the hosts to the whole audience.&lt;br /&gt;
* the recording worked well, a co-host was asked to remind the host to start and stop the recording for each session to keep videos at a manageable size&lt;br /&gt;
* we saved all of the chat transcripts as part of our CoC policy (fortunately unnecessary)&lt;br /&gt;
&lt;br /&gt;
We purchased:&lt;br /&gt;
* 1 account for up to 1,000 people for the keynotes&lt;br /&gt;
* 2 accounts for up to 500 people for the other streams&lt;br /&gt;
* 1 account for up to 100 people for the coffee bar&lt;br /&gt;
* An add on for large cloud storage for all of the video recordings&lt;br /&gt;
* '''Total cost £198''' (a month's licenses)&lt;br /&gt;
&lt;br /&gt;
We over-provisioned because we did not know how many people would actually log-in. We could have managed with smaller accounts and saved some money.&lt;br /&gt;
&lt;br /&gt;
It is unclear whether we would have been better off purchasing zoom webinar licenses rather than large meetings.&lt;br /&gt;
&lt;br /&gt;
We were aware that the zoom meetings could have been streamed to youtube but we did not see any significant benefit from doing that.&lt;br /&gt;
&lt;br /&gt;
==== Options for the future ====&lt;br /&gt;
&lt;br /&gt;
We have received some retrospective suggestions for alternative tech approaches to running an online event. Hopefully others will be inspired to run further online FOSS4G events and they will experiment with these.&lt;br /&gt;
&lt;br /&gt;
Our choices were based on a need for a low effort tech approach given our small team and pressures on our time. Despite the poor publicity that zoom had received re security during the COVID crisis we found that the security features available were sufficient for our needs.&lt;br /&gt;
&lt;br /&gt;
=== Eventbrite ===&lt;br /&gt;
&lt;br /&gt;
We used eventbrite for our registration system. &lt;br /&gt;
&lt;br /&gt;
* It was free as the event was a free event, if we had charged £10 per registration we would have incurred cost including credit card fees of about 10%&lt;br /&gt;
* Eventbrite has an online event page which is only accessible to people who have registered, we only exposed the links to the conference streams via this page to minimise the risks of being overloaded or trolled.&lt;br /&gt;
* We added a registration question to request permission to add registrants to the global FOSS4G mailing list (we had a very high acceptance rate). '''This should be highly recommended practice for future FOSS4Gs'''&lt;br /&gt;
* We made the completion of a company address mandatory on registration because it forced people to provide their 2 digit country code which enabled us to analyse the locations of registrants. This will enable future FOSS4G to geographically segment the audience.&lt;br /&gt;
* We used the attendee mailing features to send a a series of emails to participants in the build up and post event. Its a bit clunky but it works fine and avoided having to maintain an alternative email list.&lt;br /&gt;
&lt;br /&gt;
=== WhatsAppp ===&lt;br /&gt;
&lt;br /&gt;
We used WhatsApp for team communications in the build up and on the day. We also had a group for our volunteers and were able to share updates with the volunteers before the event and it was the main channel of communication on the day&lt;br /&gt;
&lt;br /&gt;
We could have considered a speakers group in addition.&lt;br /&gt;
&lt;br /&gt;
=== Twitter ===&lt;br /&gt;
&lt;br /&gt;
We used twitter as our main channel for publicity prior to the event. It is important to recognise that not everyone is on twitter, future events should consider what other channels to use for communication with potential participants.&lt;br /&gt;
&lt;br /&gt;
We used twitter on the day for announcements, publicity and encouraged the participants to chat via twitter.&lt;br /&gt;
&lt;br /&gt;
== Event structure ==&lt;br /&gt;
&lt;br /&gt;
3 streams plus coffee bar, describe how it worked&lt;br /&gt;
&lt;br /&gt;
Link to programme&lt;br /&gt;
&lt;br /&gt;
=== Hosts and co-hosts ===&lt;br /&gt;
&lt;br /&gt;
Link to Guide&lt;br /&gt;
&lt;br /&gt;
=== Recording and publishing ===&lt;br /&gt;
&lt;br /&gt;
automatic recording helps&lt;br /&gt;
&lt;br /&gt;
=== What worked ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
=== What didn't work ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
== What would we try to do if we ran another event? ==&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124852</id>
		<title>FOSS4GUK 2020 Online - Lessons Learnt</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124852"/>
		<updated>2020-06-22T19:45:23Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: /* Delegates */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''This is a draft at the moment!'''&lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
&lt;br /&gt;
[https://uk.osgeo.org/foss4gukonline2020/ FOSS4GUK 2020 Online] was hosted by the [https://uk.osgeo.org OSGeo:UK] committee on 17th June 2020 from 9.00am to 17.30pm UTC+1&lt;br /&gt;
&lt;br /&gt;
The event was free to attend with all of the costs (see below) funded from OSGeo:UK reserves. &lt;br /&gt;
&lt;br /&gt;
=== Delegates ===&lt;br /&gt;
&lt;br /&gt;
* 1,000 people registered&lt;br /&gt;
* We estimate that between 500 and 600 attended&lt;br /&gt;
* Maximum number online at any time was 460, minimum was 205&lt;br /&gt;
* Delegates from 77 countries&lt;br /&gt;
** 48% from GB, 8% US, 4% India&lt;br /&gt;
&lt;br /&gt;
=== [https://uk.osgeo.org/foss4gukonline2020/programme.html Programme] ===&lt;br /&gt;
&lt;br /&gt;
* 3 streams running for the whole day (except during keynotes)&lt;br /&gt;
** 2 keynotes&lt;br /&gt;
** 29 talks and demos&lt;br /&gt;
** 4 Lightning talks&lt;br /&gt;
* 38 Speakers (10 women)&lt;br /&gt;
* Coffee bar stream where delegates could hang out and chat (not heavily used)&lt;br /&gt;
&lt;br /&gt;
=== Finances ===&lt;br /&gt;
* The only costs were the fees for the zoom account for 1 month: £198&lt;br /&gt;
* Delegate donations:&lt;br /&gt;
** OSGeo:UK 63 individual donations - gross £1,810, net after Paypal fees £1,744 (as of 2020-06-20)&lt;br /&gt;
** MapAction ?&lt;br /&gt;
&lt;br /&gt;
== Tech and tools ==&lt;br /&gt;
&lt;br /&gt;
=== Choice of video conferencing platform ===&lt;br /&gt;
&lt;br /&gt;
==== We considered ====&lt;br /&gt;
&lt;br /&gt;
* webex (we had an offer of a free account from a sponsor) - problems with audio, uncertain linux support, limit on numbers&lt;br /&gt;
* hopin.to - a virtual conference application, unfortunately the demo the we attended was not successful and we did not feel comfortable taking the risk on a new service but it looks promising for the future&lt;br /&gt;
* several other services that did not seem to fit our needs&lt;br /&gt;
* jitsi - our experience of using the free hosted version left us uncomfortable with jitsi as platform for a large event with 3 streams. None of us had the experience or access to hardware and bandwidth to consider running a large self-hosted version of jitsi. We were also concerned about how we could control access or restrict anyone breaching our CoC&lt;br /&gt;
* several of us had experience of running large meetings on zoom and were confident that we could host the event on zoom and leverage it's capabilities.&lt;br /&gt;
&lt;br /&gt;
==== What we learnt ====&lt;br /&gt;
&lt;br /&gt;
* zoom worked as anticipated. We had no major technical problems and as far as we know very few participants experienced problems, zoom offers clients for Linux, Mac and Windows, iOS and Android.&lt;br /&gt;
* we were able to manage participants by muting everyone on entry and restricting chat within the app to messages to one of the hosts and from the hosts to the whole audience.&lt;br /&gt;
* the recording worked well, a co-host was asked to remind the host to start and stop the recording for each session to keep videos at a manageable size&lt;br /&gt;
* we saved all of the chat transcripts as part of our CoC policy (fortunately unnecessary)&lt;br /&gt;
&lt;br /&gt;
We purchased:&lt;br /&gt;
* 1 account for up to 1,000 people for the keynotes&lt;br /&gt;
* 2 accounts for up to 500 people for the other streams&lt;br /&gt;
* 1 account for up to 100 people for the coffee bar&lt;br /&gt;
* An add on for large cloud storage for all of the video recordings&lt;br /&gt;
* '''Total cost £198''' (a month's licenses)&lt;br /&gt;
&lt;br /&gt;
We over-provisioned because we did not know how many people would actually log-in. We could have managed with smaller accounts and saved some money.&lt;br /&gt;
&lt;br /&gt;
It is unclear whether we would have been better off purchasing zoom webinar licenses rather than large meetings.&lt;br /&gt;
&lt;br /&gt;
We were aware that the zoom meetings could have been streamed to youtube but we did not see any significant benefit from doing that.&lt;br /&gt;
&lt;br /&gt;
==== Options for the future ====&lt;br /&gt;
&lt;br /&gt;
We have received some retrospective suggestions for alternative tech approaches to running an online event. Hopefully others will be inspired to run further online FOSS4G events and they will experiment with these.&lt;br /&gt;
&lt;br /&gt;
Our choices were based on a need for a low effort tech approach given our small team and pressures on our time. Despite the poor publicity that zoom had received re security during the COVID crisis we found that the security features available were sufficient for our needs.&lt;br /&gt;
&lt;br /&gt;
=== Eventbrite ===&lt;br /&gt;
&lt;br /&gt;
We used eventbrite for our registration system. &lt;br /&gt;
&lt;br /&gt;
* It was free as the event was a free event, if we had charged £10 per registration we would have incurred cost including credit card fees of about 10%&lt;br /&gt;
* Eventbrite has an online event page which is only accessible to people who have registered, we only exposed the links to the conference streams via this page to minimise the risks of being overloaded or trolled.&lt;br /&gt;
* We added a registration question to request permission to add registrants to the global FOSS4G mailing list (we had a very high acceptance rate). '''This should be highly recommended practice for future FOSS4Gs'''&lt;br /&gt;
* We made the completion of a company address mandatory on registration because it forced people to provide their 2 digit country code which enabled us to analyse the locations of registrants. This will enable future FOSS4G to geographically segment the audience.&lt;br /&gt;
* We used the attendee mailing features to send a a series of emails to participants in the build up and post event. Its a bit clunky but it works fine and avoided having to maintain an alternative email list.&lt;br /&gt;
&lt;br /&gt;
=== WhatsAppp ===&lt;br /&gt;
&lt;br /&gt;
We used WhatsApp for team communications in the build up and on the day. We also had a group for our volunteers and were able to share updates with the volunteers before the event and it was the main channel of communication on the day&lt;br /&gt;
&lt;br /&gt;
We could have considered a speakers group in addition.&lt;br /&gt;
&lt;br /&gt;
=== Twitter ===&lt;br /&gt;
&lt;br /&gt;
We used twitter as our main channel for publicity prior to the event. It is important to recognise that not everyone is on twitter, future events should consider what other channels to use for communication with potential participants.&lt;br /&gt;
&lt;br /&gt;
We used twitter on the day for announcements, publicity and encouraged the participants to chat via twitter.&lt;br /&gt;
&lt;br /&gt;
== Event structure ==&lt;br /&gt;
&lt;br /&gt;
3 streams plus coffee bar, describe how it worked&lt;br /&gt;
&lt;br /&gt;
Link to programme&lt;br /&gt;
&lt;br /&gt;
=== Hosts and co-hosts ===&lt;br /&gt;
&lt;br /&gt;
Link to Guide&lt;br /&gt;
&lt;br /&gt;
=== Recording and publishing ===&lt;br /&gt;
&lt;br /&gt;
automatic recording helps&lt;br /&gt;
&lt;br /&gt;
=== What worked ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
=== What didn't work ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
== What would we try to do if we ran another event? ==&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124851</id>
		<title>FOSS4GUK 2020 Online - Lessons Learnt</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124851"/>
		<updated>2020-06-22T19:42:41Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: /* Twitter */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''This is a draft at the moment!'''&lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
&lt;br /&gt;
[https://uk.osgeo.org/foss4gukonline2020/ FOSS4GUK 2020 Online] was hosted by the [https://uk.osgeo.org OSGeo:UK] committee on 17th June 2020 from 9.00am to 17.30pm UTC+1&lt;br /&gt;
&lt;br /&gt;
The event was free to attend with all of the costs (see below) funded from OSGeo:UK reserves. &lt;br /&gt;
&lt;br /&gt;
=== Delegates ===&lt;br /&gt;
&lt;br /&gt;
* 1,000 people registered&lt;br /&gt;
* We estimate about 600 attended&lt;br /&gt;
* Maximum number online at any time was 460, minimum was 205&lt;br /&gt;
* Delegates from 77 countries&lt;br /&gt;
** 48% from GB, 8% US, 4% India&lt;br /&gt;
&lt;br /&gt;
=== [https://uk.osgeo.org/foss4gukonline2020/programme.html Programme] ===&lt;br /&gt;
&lt;br /&gt;
* 3 streams running for the whole day (except during keynotes)&lt;br /&gt;
** 2 keynotes&lt;br /&gt;
** 29 talks and demos&lt;br /&gt;
** 4 Lightning talks&lt;br /&gt;
* 38 Speakers (10 women)&lt;br /&gt;
* Coffee bar stream where delegates could hang out and chat (not heavily used)&lt;br /&gt;
&lt;br /&gt;
=== Finances ===&lt;br /&gt;
* The only costs were the fees for the zoom account for 1 month: £198&lt;br /&gt;
* Delegate donations:&lt;br /&gt;
** OSGeo:UK 63 individual donations - gross £1,810, net after Paypal fees £1,744 (as of 2020-06-20)&lt;br /&gt;
** MapAction ?&lt;br /&gt;
&lt;br /&gt;
== Tech and tools ==&lt;br /&gt;
&lt;br /&gt;
=== Choice of video conferencing platform ===&lt;br /&gt;
&lt;br /&gt;
==== We considered ====&lt;br /&gt;
&lt;br /&gt;
* webex (we had an offer of a free account from a sponsor) - problems with audio, uncertain linux support, limit on numbers&lt;br /&gt;
* hopin.to - a virtual conference application, unfortunately the demo the we attended was not successful and we did not feel comfortable taking the risk on a new service but it looks promising for the future&lt;br /&gt;
* several other services that did not seem to fit our needs&lt;br /&gt;
* jitsi - our experience of using the free hosted version left us uncomfortable with jitsi as platform for a large event with 3 streams. None of us had the experience or access to hardware and bandwidth to consider running a large self-hosted version of jitsi. We were also concerned about how we could control access or restrict anyone breaching our CoC&lt;br /&gt;
* several of us had experience of running large meetings on zoom and were confident that we could host the event on zoom and leverage it's capabilities.&lt;br /&gt;
&lt;br /&gt;
==== What we learnt ====&lt;br /&gt;
&lt;br /&gt;
* zoom worked as anticipated. We had no major technical problems and as far as we know very few participants experienced problems, zoom offers clients for Linux, Mac and Windows, iOS and Android.&lt;br /&gt;
* we were able to manage participants by muting everyone on entry and restricting chat within the app to messages to one of the hosts and from the hosts to the whole audience.&lt;br /&gt;
* the recording worked well, a co-host was asked to remind the host to start and stop the recording for each session to keep videos at a manageable size&lt;br /&gt;
* we saved all of the chat transcripts as part of our CoC policy (fortunately unnecessary)&lt;br /&gt;
&lt;br /&gt;
We purchased:&lt;br /&gt;
* 1 account for up to 1,000 people for the keynotes&lt;br /&gt;
* 2 accounts for up to 500 people for the other streams&lt;br /&gt;
* 1 account for up to 100 people for the coffee bar&lt;br /&gt;
* An add on for large cloud storage for all of the video recordings&lt;br /&gt;
* '''Total cost £198''' (a month's licenses)&lt;br /&gt;
&lt;br /&gt;
We over-provisioned because we did not know how many people would actually log-in. We could have managed with smaller accounts and saved some money.&lt;br /&gt;
&lt;br /&gt;
It is unclear whether we would have been better off purchasing zoom webinar licenses rather than large meetings.&lt;br /&gt;
&lt;br /&gt;
We were aware that the zoom meetings could have been streamed to youtube but we did not see any significant benefit from doing that.&lt;br /&gt;
&lt;br /&gt;
==== Options for the future ====&lt;br /&gt;
&lt;br /&gt;
We have received some retrospective suggestions for alternative tech approaches to running an online event. Hopefully others will be inspired to run further online FOSS4G events and they will experiment with these.&lt;br /&gt;
&lt;br /&gt;
Our choices were based on a need for a low effort tech approach given our small team and pressures on our time. Despite the poor publicity that zoom had received re security during the COVID crisis we found that the security features available were sufficient for our needs.&lt;br /&gt;
&lt;br /&gt;
=== Eventbrite ===&lt;br /&gt;
&lt;br /&gt;
We used eventbrite for our registration system. &lt;br /&gt;
&lt;br /&gt;
* It was free as the event was a free event, if we had charged £10 per registration we would have incurred cost including credit card fees of about 10%&lt;br /&gt;
* Eventbrite has an online event page which is only accessible to people who have registered, we only exposed the links to the conference streams via this page to minimise the risks of being overloaded or trolled.&lt;br /&gt;
* We added a registration question to request permission to add registrants to the global FOSS4G mailing list (we had a very high acceptance rate). '''This should be highly recommended practice for future FOSS4Gs'''&lt;br /&gt;
* We made the completion of a company address mandatory on registration because it forced people to provide their 2 digit country code which enabled us to analyse the locations of registrants. This will enable future FOSS4G to geographically segment the audience.&lt;br /&gt;
* We used the attendee mailing features to send a a series of emails to participants in the build up and post event. Its a bit clunky but it works fine and avoided having to maintain an alternative email list.&lt;br /&gt;
&lt;br /&gt;
=== WhatsAppp ===&lt;br /&gt;
&lt;br /&gt;
We used WhatsApp for team communications in the build up and on the day. We also had a group for our volunteers and were able to share updates with the volunteers before the event and it was the main channel of communication on the day&lt;br /&gt;
&lt;br /&gt;
We could have considered a speakers group in addition.&lt;br /&gt;
&lt;br /&gt;
=== Twitter ===&lt;br /&gt;
&lt;br /&gt;
We used twitter as our main channel for publicity prior to the event. It is important to recognise that not everyone is on twitter, future events should consider what other channels to use for communication with potential participants.&lt;br /&gt;
&lt;br /&gt;
We used twitter on the day for announcements, publicity and encouraged the participants to chat via twitter.&lt;br /&gt;
&lt;br /&gt;
== Event structure ==&lt;br /&gt;
&lt;br /&gt;
3 streams plus coffee bar, describe how it worked&lt;br /&gt;
&lt;br /&gt;
Link to programme&lt;br /&gt;
&lt;br /&gt;
=== Hosts and co-hosts ===&lt;br /&gt;
&lt;br /&gt;
Link to Guide&lt;br /&gt;
&lt;br /&gt;
=== Recording and publishing ===&lt;br /&gt;
&lt;br /&gt;
automatic recording helps&lt;br /&gt;
&lt;br /&gt;
=== What worked ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
=== What didn't work ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
== What would we try to do if we ran another event? ==&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124850</id>
		<title>FOSS4GUK 2020 Online - Lessons Learnt</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124850"/>
		<updated>2020-06-22T19:38:59Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: /* WhatsAppp */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''This is a draft at the moment!'''&lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
&lt;br /&gt;
[https://uk.osgeo.org/foss4gukonline2020/ FOSS4GUK 2020 Online] was hosted by the [https://uk.osgeo.org OSGeo:UK] committee on 17th June 2020 from 9.00am to 17.30pm UTC+1&lt;br /&gt;
&lt;br /&gt;
The event was free to attend with all of the costs (see below) funded from OSGeo:UK reserves. &lt;br /&gt;
&lt;br /&gt;
=== Delegates ===&lt;br /&gt;
&lt;br /&gt;
* 1,000 people registered&lt;br /&gt;
* We estimate about 600 attended&lt;br /&gt;
* Maximum number online at any time was 460, minimum was 205&lt;br /&gt;
* Delegates from 77 countries&lt;br /&gt;
** 48% from GB, 8% US, 4% India&lt;br /&gt;
&lt;br /&gt;
=== [https://uk.osgeo.org/foss4gukonline2020/programme.html Programme] ===&lt;br /&gt;
&lt;br /&gt;
* 3 streams running for the whole day (except during keynotes)&lt;br /&gt;
** 2 keynotes&lt;br /&gt;
** 29 talks and demos&lt;br /&gt;
** 4 Lightning talks&lt;br /&gt;
* 38 Speakers (10 women)&lt;br /&gt;
* Coffee bar stream where delegates could hang out and chat (not heavily used)&lt;br /&gt;
&lt;br /&gt;
=== Finances ===&lt;br /&gt;
* The only costs were the fees for the zoom account for 1 month: £198&lt;br /&gt;
* Delegate donations:&lt;br /&gt;
** OSGeo:UK 63 individual donations - gross £1,810, net after Paypal fees £1,744 (as of 2020-06-20)&lt;br /&gt;
** MapAction ?&lt;br /&gt;
&lt;br /&gt;
== Tech and tools ==&lt;br /&gt;
&lt;br /&gt;
=== Choice of video conferencing platform ===&lt;br /&gt;
&lt;br /&gt;
==== We considered ====&lt;br /&gt;
&lt;br /&gt;
* webex (we had an offer of a free account from a sponsor) - problems with audio, uncertain linux support, limit on numbers&lt;br /&gt;
* hopin.to - a virtual conference application, unfortunately the demo the we attended was not successful and we did not feel comfortable taking the risk on a new service but it looks promising for the future&lt;br /&gt;
* several other services that did not seem to fit our needs&lt;br /&gt;
* jitsi - our experience of using the free hosted version left us uncomfortable with jitsi as platform for a large event with 3 streams. None of us had the experience or access to hardware and bandwidth to consider running a large self-hosted version of jitsi. We were also concerned about how we could control access or restrict anyone breaching our CoC&lt;br /&gt;
* several of us had experience of running large meetings on zoom and were confident that we could host the event on zoom and leverage it's capabilities.&lt;br /&gt;
&lt;br /&gt;
==== What we learnt ====&lt;br /&gt;
&lt;br /&gt;
* zoom worked as anticipated. We had no major technical problems and as far as we know very few participants experienced problems, zoom offers clients for Linux, Mac and Windows, iOS and Android.&lt;br /&gt;
* we were able to manage participants by muting everyone on entry and restricting chat within the app to messages to one of the hosts and from the hosts to the whole audience.&lt;br /&gt;
* the recording worked well, a co-host was asked to remind the host to start and stop the recording for each session to keep videos at a manageable size&lt;br /&gt;
* we saved all of the chat transcripts as part of our CoC policy (fortunately unnecessary)&lt;br /&gt;
&lt;br /&gt;
We purchased:&lt;br /&gt;
* 1 account for up to 1,000 people for the keynotes&lt;br /&gt;
* 2 accounts for up to 500 people for the other streams&lt;br /&gt;
* 1 account for up to 100 people for the coffee bar&lt;br /&gt;
* An add on for large cloud storage for all of the video recordings&lt;br /&gt;
* '''Total cost £198''' (a month's licenses)&lt;br /&gt;
&lt;br /&gt;
We over-provisioned because we did not know how many people would actually log-in. We could have managed with smaller accounts and saved some money.&lt;br /&gt;
&lt;br /&gt;
It is unclear whether we would have been better off purchasing zoom webinar licenses rather than large meetings.&lt;br /&gt;
&lt;br /&gt;
We were aware that the zoom meetings could have been streamed to youtube but we did not see any significant benefit from doing that.&lt;br /&gt;
&lt;br /&gt;
==== Options for the future ====&lt;br /&gt;
&lt;br /&gt;
We have received some retrospective suggestions for alternative tech approaches to running an online event. Hopefully others will be inspired to run further online FOSS4G events and they will experiment with these.&lt;br /&gt;
&lt;br /&gt;
Our choices were based on a need for a low effort tech approach given our small team and pressures on our time. Despite the poor publicity that zoom had received re security during the COVID crisis we found that the security features available were sufficient for our needs.&lt;br /&gt;
&lt;br /&gt;
=== Eventbrite ===&lt;br /&gt;
&lt;br /&gt;
We used eventbrite for our registration system. &lt;br /&gt;
&lt;br /&gt;
* It was free as the event was a free event, if we had charged £10 per registration we would have incurred cost including credit card fees of about 10%&lt;br /&gt;
* Eventbrite has an online event page which is only accessible to people who have registered, we only exposed the links to the conference streams via this page to minimise the risks of being overloaded or trolled.&lt;br /&gt;
* We added a registration question to request permission to add registrants to the global FOSS4G mailing list (we had a very high acceptance rate). '''This should be highly recommended practice for future FOSS4Gs'''&lt;br /&gt;
* We made the completion of a company address mandatory on registration because it forced people to provide their 2 digit country code which enabled us to analyse the locations of registrants. This will enable future FOSS4G to geographically segment the audience.&lt;br /&gt;
* We used the attendee mailing features to send a a series of emails to participants in the build up and post event. Its a bit clunky but it works fine and avoided having to maintain an alternative email list.&lt;br /&gt;
&lt;br /&gt;
=== WhatsAppp ===&lt;br /&gt;
&lt;br /&gt;
We used WhatsApp for team communications in the build up and on the day. We also had a group for our volunteers and were able to share updates with the volunteers before the event and it was the main channel of communication on the day&lt;br /&gt;
&lt;br /&gt;
We could have considered a speakers group in addition.&lt;br /&gt;
&lt;br /&gt;
=== Twitter ===&lt;br /&gt;
&lt;br /&gt;
not everyone is on twitter despite what we think&lt;br /&gt;
&lt;br /&gt;
== Event structure ==&lt;br /&gt;
&lt;br /&gt;
3 streams plus coffee bar, describe how it worked&lt;br /&gt;
&lt;br /&gt;
Link to programme&lt;br /&gt;
&lt;br /&gt;
=== Hosts and co-hosts ===&lt;br /&gt;
&lt;br /&gt;
Link to Guide&lt;br /&gt;
&lt;br /&gt;
=== Recording and publishing ===&lt;br /&gt;
&lt;br /&gt;
automatic recording helps&lt;br /&gt;
&lt;br /&gt;
=== What worked ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
=== What didn't work ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
== What would we try to do if we ran another event? ==&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124849</id>
		<title>FOSS4GUK 2020 Online - Lessons Learnt</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124849"/>
		<updated>2020-06-22T19:36:27Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: /* Eventbrite */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''This is a draft at the moment!'''&lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
&lt;br /&gt;
[https://uk.osgeo.org/foss4gukonline2020/ FOSS4GUK 2020 Online] was hosted by the [https://uk.osgeo.org OSGeo:UK] committee on 17th June 2020 from 9.00am to 17.30pm UTC+1&lt;br /&gt;
&lt;br /&gt;
The event was free to attend with all of the costs (see below) funded from OSGeo:UK reserves. &lt;br /&gt;
&lt;br /&gt;
=== Delegates ===&lt;br /&gt;
&lt;br /&gt;
* 1,000 people registered&lt;br /&gt;
* We estimate about 600 attended&lt;br /&gt;
* Maximum number online at any time was 460, minimum was 205&lt;br /&gt;
* Delegates from 77 countries&lt;br /&gt;
** 48% from GB, 8% US, 4% India&lt;br /&gt;
&lt;br /&gt;
=== [https://uk.osgeo.org/foss4gukonline2020/programme.html Programme] ===&lt;br /&gt;
&lt;br /&gt;
* 3 streams running for the whole day (except during keynotes)&lt;br /&gt;
** 2 keynotes&lt;br /&gt;
** 29 talks and demos&lt;br /&gt;
** 4 Lightning talks&lt;br /&gt;
* 38 Speakers (10 women)&lt;br /&gt;
* Coffee bar stream where delegates could hang out and chat (not heavily used)&lt;br /&gt;
&lt;br /&gt;
=== Finances ===&lt;br /&gt;
* The only costs were the fees for the zoom account for 1 month: £198&lt;br /&gt;
* Delegate donations:&lt;br /&gt;
** OSGeo:UK 63 individual donations - gross £1,810, net after Paypal fees £1,744 (as of 2020-06-20)&lt;br /&gt;
** MapAction ?&lt;br /&gt;
&lt;br /&gt;
== Tech and tools ==&lt;br /&gt;
&lt;br /&gt;
=== Choice of video conferencing platform ===&lt;br /&gt;
&lt;br /&gt;
==== We considered ====&lt;br /&gt;
&lt;br /&gt;
* webex (we had an offer of a free account from a sponsor) - problems with audio, uncertain linux support, limit on numbers&lt;br /&gt;
* hopin.to - a virtual conference application, unfortunately the demo the we attended was not successful and we did not feel comfortable taking the risk on a new service but it looks promising for the future&lt;br /&gt;
* several other services that did not seem to fit our needs&lt;br /&gt;
* jitsi - our experience of using the free hosted version left us uncomfortable with jitsi as platform for a large event with 3 streams. None of us had the experience or access to hardware and bandwidth to consider running a large self-hosted version of jitsi. We were also concerned about how we could control access or restrict anyone breaching our CoC&lt;br /&gt;
* several of us had experience of running large meetings on zoom and were confident that we could host the event on zoom and leverage it's capabilities.&lt;br /&gt;
&lt;br /&gt;
==== What we learnt ====&lt;br /&gt;
&lt;br /&gt;
* zoom worked as anticipated. We had no major technical problems and as far as we know very few participants experienced problems, zoom offers clients for Linux, Mac and Windows, iOS and Android.&lt;br /&gt;
* we were able to manage participants by muting everyone on entry and restricting chat within the app to messages to one of the hosts and from the hosts to the whole audience.&lt;br /&gt;
* the recording worked well, a co-host was asked to remind the host to start and stop the recording for each session to keep videos at a manageable size&lt;br /&gt;
* we saved all of the chat transcripts as part of our CoC policy (fortunately unnecessary)&lt;br /&gt;
&lt;br /&gt;
We purchased:&lt;br /&gt;
* 1 account for up to 1,000 people for the keynotes&lt;br /&gt;
* 2 accounts for up to 500 people for the other streams&lt;br /&gt;
* 1 account for up to 100 people for the coffee bar&lt;br /&gt;
* An add on for large cloud storage for all of the video recordings&lt;br /&gt;
* '''Total cost £198''' (a month's licenses)&lt;br /&gt;
&lt;br /&gt;
We over-provisioned because we did not know how many people would actually log-in. We could have managed with smaller accounts and saved some money.&lt;br /&gt;
&lt;br /&gt;
It is unclear whether we would have been better off purchasing zoom webinar licenses rather than large meetings.&lt;br /&gt;
&lt;br /&gt;
We were aware that the zoom meetings could have been streamed to youtube but we did not see any significant benefit from doing that.&lt;br /&gt;
&lt;br /&gt;
==== Options for the future ====&lt;br /&gt;
&lt;br /&gt;
We have received some retrospective suggestions for alternative tech approaches to running an online event. Hopefully others will be inspired to run further online FOSS4G events and they will experiment with these.&lt;br /&gt;
&lt;br /&gt;
Our choices were based on a need for a low effort tech approach given our small team and pressures on our time. Despite the poor publicity that zoom had received re security during the COVID crisis we found that the security features available were sufficient for our needs.&lt;br /&gt;
&lt;br /&gt;
=== Eventbrite ===&lt;br /&gt;
&lt;br /&gt;
We used eventbrite for our registration system. &lt;br /&gt;
&lt;br /&gt;
* It was free as the event was a free event, if we had charged £10 per registration we would have incurred cost including credit card fees of about 10%&lt;br /&gt;
* Eventbrite has an online event page which is only accessible to people who have registered, we only exposed the links to the conference streams via this page to minimise the risks of being overloaded or trolled.&lt;br /&gt;
* We added a registration question to request permission to add registrants to the global FOSS4G mailing list (we had a very high acceptance rate). '''This should be highly recommended practice for future FOSS4Gs'''&lt;br /&gt;
* We made the completion of a company address mandatory on registration because it forced people to provide their 2 digit country code which enabled us to analyse the locations of registrants. This will enable future FOSS4G to geographically segment the audience.&lt;br /&gt;
* We used the attendee mailing features to send a a series of emails to participants in the build up and post event. Its a bit clunky but it works fine and avoided having to maintain an alternative email list.&lt;br /&gt;
&lt;br /&gt;
=== WhatsAppp ===&lt;br /&gt;
&lt;br /&gt;
Team comms&lt;br /&gt;
&lt;br /&gt;
Volunteers Group, could have considered a speakers group&lt;br /&gt;
&lt;br /&gt;
Seems almost everyone uses&lt;br /&gt;
&lt;br /&gt;
=== Twitter ===&lt;br /&gt;
&lt;br /&gt;
not everyone is on twitter despite what we think&lt;br /&gt;
&lt;br /&gt;
== Event structure ==&lt;br /&gt;
&lt;br /&gt;
3 streams plus coffee bar, describe how it worked&lt;br /&gt;
&lt;br /&gt;
Link to programme&lt;br /&gt;
&lt;br /&gt;
=== Hosts and co-hosts ===&lt;br /&gt;
&lt;br /&gt;
Link to Guide&lt;br /&gt;
&lt;br /&gt;
=== Recording and publishing ===&lt;br /&gt;
&lt;br /&gt;
automatic recording helps&lt;br /&gt;
&lt;br /&gt;
=== What worked ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
=== What didn't work ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
== What would we try to do if we ran another event? ==&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124844</id>
		<title>FOSS4GUK 2020 Online - Lessons Learnt</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124844"/>
		<updated>2020-06-22T11:25:22Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: /* What we learnt */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''This is a draft at the moment!'''&lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
&lt;br /&gt;
[https://uk.osgeo.org/foss4gukonline2020/ FOSS4GUK 2020 Online] was hosted by the [https://uk.osgeo.org OSGeo:UK] committee on 17th June 2020 from 9.00am to 17.30pm UTC+1&lt;br /&gt;
&lt;br /&gt;
The event was free to attend with all of the costs (see below) funded from OSGeo:UK reserves. &lt;br /&gt;
&lt;br /&gt;
=== Delegates ===&lt;br /&gt;
&lt;br /&gt;
* 1,000 people registered&lt;br /&gt;
* We estimate about 600 attended&lt;br /&gt;
* Maximum number online at any time was 460, minimum was 205&lt;br /&gt;
* Delegates from 77 countries&lt;br /&gt;
** 48% from GB, 8% US, 4% India&lt;br /&gt;
&lt;br /&gt;
=== [https://uk.osgeo.org/foss4gukonline2020/programme.html Programme] ===&lt;br /&gt;
&lt;br /&gt;
* 3 streams running for the whole day (except during keynotes)&lt;br /&gt;
** 2 keynotes&lt;br /&gt;
** 29 talks and demos&lt;br /&gt;
** 4 Lightning talks&lt;br /&gt;
* 38 Speakers (10 women)&lt;br /&gt;
* Coffee bar stream where delegates could hang out and chat (not heavily used)&lt;br /&gt;
&lt;br /&gt;
=== Finances ===&lt;br /&gt;
* The only costs were the fees for the zoom account for 1 month: £198&lt;br /&gt;
* Delegate donations:&lt;br /&gt;
** OSGeo:UK 63 individual donations - gross £1,810, net after Paypal fees £1,744 (as of 2020-06-20)&lt;br /&gt;
** MapAction ?&lt;br /&gt;
&lt;br /&gt;
== Tech and tools ==&lt;br /&gt;
&lt;br /&gt;
=== Choice of video conferencing platform ===&lt;br /&gt;
&lt;br /&gt;
==== We considered ====&lt;br /&gt;
&lt;br /&gt;
* webex (we had an offer of a free account from a sponsor) - problems with audio, uncertain linux support, limit on numbers&lt;br /&gt;
* hopin.to - a virtual conference application, unfortunately the demo the we attended was not successful and we did not feel comfortable taking the risk on a new service but it looks promising for the future&lt;br /&gt;
* several other services that did not seem to fit our needs&lt;br /&gt;
* jitsi - our experience of using the free hosted version left us uncomfortable with jitsi as platform for a large event with 3 streams. None of us had the experience or access to hardware and bandwidth to consider running a large self-hosted version of jitsi. We were also concerned about how we could control access or restrict anyone breaching our CoC&lt;br /&gt;
* several of us had experience of running large meetings on zoom and were confident that we could host the event on zoom and leverage it's capabilities.&lt;br /&gt;
&lt;br /&gt;
==== What we learnt ====&lt;br /&gt;
&lt;br /&gt;
* zoom worked as anticipated. We had no major technical problems and as far as we know very few participants experienced problems, zoom offers clients for Linux, Mac and Windows, iOS and Android.&lt;br /&gt;
* we were able to manage participants by muting everyone on entry and restricting chat within the app to messages to one of the hosts and from the hosts to the whole audience.&lt;br /&gt;
* the recording worked well, a co-host was asked to remind the host to start and stop the recording for each session to keep videos at a manageable size&lt;br /&gt;
* we saved all of the chat transcripts as part of our CoC policy (fortunately unnecessary)&lt;br /&gt;
&lt;br /&gt;
We purchased:&lt;br /&gt;
* 1 account for up to 1,000 people for the keynotes&lt;br /&gt;
* 2 accounts for up to 500 people for the other streams&lt;br /&gt;
* 1 account for up to 100 people for the coffee bar&lt;br /&gt;
* An add on for large cloud storage for all of the video recordings&lt;br /&gt;
* '''Total cost £198''' (a month's licenses)&lt;br /&gt;
&lt;br /&gt;
We over-provisioned because we did not know how many people would actually log-in. We could have managed with smaller accounts and saved some money.&lt;br /&gt;
&lt;br /&gt;
It is unclear whether we would have been better off purchasing zoom webinar licenses rather than large meetings.&lt;br /&gt;
&lt;br /&gt;
We were aware that the zoom meetings could have been streamed to youtube but we did not see any significant benefit from doing that.&lt;br /&gt;
&lt;br /&gt;
==== Options for the future ====&lt;br /&gt;
&lt;br /&gt;
We have received some retrospective suggestions for alternative tech approaches to running an online event. Hopefully others will be inspired to run further online FOSS4G events and they will experiment with these.&lt;br /&gt;
&lt;br /&gt;
Our choices were based on a need for a low effort tech approach given our small team and pressures on our time. Despite the poor publicity that zoom had received re security during the COVID crisis we found that the security features available were sufficient for our needs.&lt;br /&gt;
&lt;br /&gt;
=== Eventbrite ===&lt;br /&gt;
&lt;br /&gt;
The pros and cons&lt;br /&gt;
&lt;br /&gt;
Free if you don't charge&lt;br /&gt;
&lt;br /&gt;
A bit pricey for low cost tickets&lt;br /&gt;
&lt;br /&gt;
OK email&lt;br /&gt;
&lt;br /&gt;
Easy to capture data like permission for further FOSS4G mailing, country&lt;br /&gt;
&lt;br /&gt;
Alternatives?&lt;br /&gt;
&lt;br /&gt;
=== WhatsAppp ===&lt;br /&gt;
&lt;br /&gt;
Team comms&lt;br /&gt;
&lt;br /&gt;
Volunteers Group, could have considered a speakers group&lt;br /&gt;
&lt;br /&gt;
Seems almost everyone uses&lt;br /&gt;
&lt;br /&gt;
=== Twitter ===&lt;br /&gt;
&lt;br /&gt;
not everyone is on twitter despite what we think&lt;br /&gt;
&lt;br /&gt;
== Event structure ==&lt;br /&gt;
&lt;br /&gt;
3 streams plus coffee bar, describe how it worked&lt;br /&gt;
&lt;br /&gt;
Link to programme&lt;br /&gt;
&lt;br /&gt;
=== Hosts and co-hosts ===&lt;br /&gt;
&lt;br /&gt;
Link to Guide&lt;br /&gt;
&lt;br /&gt;
=== Recording and publishing ===&lt;br /&gt;
&lt;br /&gt;
automatic recording helps&lt;br /&gt;
&lt;br /&gt;
=== What worked ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
=== What didn't work ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
== What would we try to do if we ran another event? ==&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124843</id>
		<title>FOSS4GUK 2020 Online - Lessons Learnt</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124843"/>
		<updated>2020-06-22T11:24:39Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: Tech stuff&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''This is a draft at the moment!'''&lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
&lt;br /&gt;
[https://uk.osgeo.org/foss4gukonline2020/ FOSS4GUK 2020 Online] was hosted by the [https://uk.osgeo.org OSGeo:UK] committee on 17th June 2020 from 9.00am to 17.30pm UTC+1&lt;br /&gt;
&lt;br /&gt;
The event was free to attend with all of the costs (see below) funded from OSGeo:UK reserves. &lt;br /&gt;
&lt;br /&gt;
=== Delegates ===&lt;br /&gt;
&lt;br /&gt;
* 1,000 people registered&lt;br /&gt;
* We estimate about 600 attended&lt;br /&gt;
* Maximum number online at any time was 460, minimum was 205&lt;br /&gt;
* Delegates from 77 countries&lt;br /&gt;
** 48% from GB, 8% US, 4% India&lt;br /&gt;
&lt;br /&gt;
=== [https://uk.osgeo.org/foss4gukonline2020/programme.html Programme] ===&lt;br /&gt;
&lt;br /&gt;
* 3 streams running for the whole day (except during keynotes)&lt;br /&gt;
** 2 keynotes&lt;br /&gt;
** 29 talks and demos&lt;br /&gt;
** 4 Lightning talks&lt;br /&gt;
* 38 Speakers (10 women)&lt;br /&gt;
* Coffee bar stream where delegates could hang out and chat (not heavily used)&lt;br /&gt;
&lt;br /&gt;
=== Finances ===&lt;br /&gt;
* The only costs were the fees for the zoom account for 1 month: £198&lt;br /&gt;
* Delegate donations:&lt;br /&gt;
** OSGeo:UK 63 individual donations - gross £1,810, net after Paypal fees £1,744 (as of 2020-06-20)&lt;br /&gt;
** MapAction ?&lt;br /&gt;
&lt;br /&gt;
== Tech and tools ==&lt;br /&gt;
&lt;br /&gt;
=== Choice of video conferencing platform ===&lt;br /&gt;
&lt;br /&gt;
==== We considered ====&lt;br /&gt;
&lt;br /&gt;
* webex (we had an offer of a free account from a sponsor) - problems with audio, uncertain linux support, limit on numbers&lt;br /&gt;
* hopin.to - a virtual conference application, unfortunately the demo the we attended was not successful and we did not feel comfortable taking the risk on a new service but it looks promising for the future&lt;br /&gt;
* several other services that did not seem to fit our needs&lt;br /&gt;
* jitsi - our experience of using the free hosted version left us uncomfortable with jitsi as platform for a large event with 3 streams. None of us had the experience or access to hardware and bandwidth to consider running a large self-hosted version of jitsi. We were also concerned about how we could control access or restrict anyone breaching our CoC&lt;br /&gt;
* several of us had experience of running large meetings on zoom and were confident that we could host the event on zoom and leverage it's capabilities.&lt;br /&gt;
&lt;br /&gt;
==== What we learnt ====&lt;br /&gt;
&lt;br /&gt;
* zoom worked as anticipated. We had no major technical problems and as far as we know very few participants experienced problems, zoom offers clients for Linux, Mac and Windows, iOS and Android.&lt;br /&gt;
* we were able to manage participants by muting everyone on entry and restricting chat within the app to messages to one of the hosts and from the hosts to the whole audience.&lt;br /&gt;
* the recording worked well, a co-host was asked to remind the host to start and stop the recording for each session to keep videos at a manageable size&lt;br /&gt;
* we saved all of the chat transcripts as part of our CoC policy (fortunately unnecessary)&lt;br /&gt;
&lt;br /&gt;
We purchased:&lt;br /&gt;
* 1 account for up to 1,000 people for the keynotes&lt;br /&gt;
* 2 accounts for up to 500 people for the other streams&lt;br /&gt;
* 1 account for up to 100 people for the coffee bar&lt;br /&gt;
* An add on for large cloud storage for all of the video recordings&lt;br /&gt;
* '''Total cost £178''' (a month's licenses)&lt;br /&gt;
&lt;br /&gt;
We over-provisioned because we did not know how many people would actually log-in. We could have managed with smaller accounts and saved some money.&lt;br /&gt;
&lt;br /&gt;
It is unclear whether we would have been better off purchasing zoom webinar licenses rather than large meetings.&lt;br /&gt;
&lt;br /&gt;
We were aware that the zoom meetings could have been streamed to youtube but we did not see any significant benefit from doing that.&lt;br /&gt;
&lt;br /&gt;
==== Options for the future ====&lt;br /&gt;
&lt;br /&gt;
We have received some retrospective suggestions for alternative tech approaches to running an online event. Hopefully others will be inspired to run further online FOSS4G events and they will experiment with these.&lt;br /&gt;
&lt;br /&gt;
Our choices were based on a need for a low effort tech approach given our small team and pressures on our time. Despite the poor publicity that zoom had received re security during the COVID crisis we found that the security features available were sufficient for our needs.&lt;br /&gt;
&lt;br /&gt;
=== Eventbrite ===&lt;br /&gt;
&lt;br /&gt;
The pros and cons&lt;br /&gt;
&lt;br /&gt;
Free if you don't charge&lt;br /&gt;
&lt;br /&gt;
A bit pricey for low cost tickets&lt;br /&gt;
&lt;br /&gt;
OK email&lt;br /&gt;
&lt;br /&gt;
Easy to capture data like permission for further FOSS4G mailing, country&lt;br /&gt;
&lt;br /&gt;
Alternatives?&lt;br /&gt;
&lt;br /&gt;
=== WhatsAppp ===&lt;br /&gt;
&lt;br /&gt;
Team comms&lt;br /&gt;
&lt;br /&gt;
Volunteers Group, could have considered a speakers group&lt;br /&gt;
&lt;br /&gt;
Seems almost everyone uses&lt;br /&gt;
&lt;br /&gt;
=== Twitter ===&lt;br /&gt;
&lt;br /&gt;
not everyone is on twitter despite what we think&lt;br /&gt;
&lt;br /&gt;
== Event structure ==&lt;br /&gt;
&lt;br /&gt;
3 streams plus coffee bar, describe how it worked&lt;br /&gt;
&lt;br /&gt;
Link to programme&lt;br /&gt;
&lt;br /&gt;
=== Hosts and co-hosts ===&lt;br /&gt;
&lt;br /&gt;
Link to Guide&lt;br /&gt;
&lt;br /&gt;
=== Recording and publishing ===&lt;br /&gt;
&lt;br /&gt;
automatic recording helps&lt;br /&gt;
&lt;br /&gt;
=== What worked ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
=== What didn't work ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
== What would we try to do if we ran another event? ==&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124842</id>
		<title>FOSS4GUK 2020 Online - Lessons Learnt</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124842"/>
		<updated>2020-06-22T10:10:24Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: /* Delegates */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''This is a draft at the moment!'''&lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
&lt;br /&gt;
[https://uk.osgeo.org/foss4gukonline2020/ FOSS4GUK 2020 Online] was hosted by the [https://uk.osgeo.org OSGeo:UK] committee on 17th June 2020 from 9.00am to 17.30pm UTC+1&lt;br /&gt;
&lt;br /&gt;
The event was free to attend with all of the costs (see below) funded from OSGeo:UK reserves. &lt;br /&gt;
&lt;br /&gt;
=== Delegates ===&lt;br /&gt;
&lt;br /&gt;
* 1,000 people registered&lt;br /&gt;
* We estimate about 600 attended&lt;br /&gt;
* Maximum number online at any time was 460, minimum was 205&lt;br /&gt;
* Delegates from 77 countries&lt;br /&gt;
** 48% from GB, 8% US, 4% India&lt;br /&gt;
&lt;br /&gt;
=== [https://uk.osgeo.org/foss4gukonline2020/programme.html Programme] ===&lt;br /&gt;
&lt;br /&gt;
* 3 streams running for the whole day (except during keynotes)&lt;br /&gt;
** 2 keynotes&lt;br /&gt;
** 29 talks and demos&lt;br /&gt;
** 4 Lightning talks&lt;br /&gt;
* 38 Speakers (10 women)&lt;br /&gt;
* Coffee bar stream where delegates could hang out and chat (not heavily used)&lt;br /&gt;
&lt;br /&gt;
=== Finances ===&lt;br /&gt;
* The only costs were the fees for the zoom account for 1 month: £198&lt;br /&gt;
* Delegate donations:&lt;br /&gt;
** OSGeo:UK 63 individual donations - gross £1,810, net after Paypal fees £1,744 (as of 2020-06-20)&lt;br /&gt;
** MapAction ?&lt;br /&gt;
&lt;br /&gt;
== Tech and tools ==&lt;br /&gt;
&lt;br /&gt;
=== Choice of video conferencing platform ===&lt;br /&gt;
&lt;br /&gt;
What we looked at&lt;br /&gt;
&lt;br /&gt;
What we learnt&lt;br /&gt;
&lt;br /&gt;
Why we chose zoom&lt;br /&gt;
&lt;br /&gt;
Tiny number of complaints, no problem on the day&lt;br /&gt;
&lt;br /&gt;
Options for the future&lt;br /&gt;
&lt;br /&gt;
=== Eventbrite ===&lt;br /&gt;
&lt;br /&gt;
The pros and cons&lt;br /&gt;
&lt;br /&gt;
Free if you don't charge&lt;br /&gt;
&lt;br /&gt;
A bit pricey for low cost tickets&lt;br /&gt;
&lt;br /&gt;
OK email&lt;br /&gt;
&lt;br /&gt;
Easy to capture data like permission for further FOSS4G mailing, country&lt;br /&gt;
&lt;br /&gt;
Alternatives?&lt;br /&gt;
&lt;br /&gt;
=== WhatsAppp ===&lt;br /&gt;
&lt;br /&gt;
Team comms&lt;br /&gt;
&lt;br /&gt;
Volunteers Group, could have considered a speakers group&lt;br /&gt;
&lt;br /&gt;
Seems almost everyone uses&lt;br /&gt;
&lt;br /&gt;
=== Twitter ===&lt;br /&gt;
&lt;br /&gt;
not everyone is on twitter despite what we think&lt;br /&gt;
&lt;br /&gt;
== Event structure ==&lt;br /&gt;
&lt;br /&gt;
3 streams plus coffee bar, describe how it worked&lt;br /&gt;
&lt;br /&gt;
Link to programme&lt;br /&gt;
&lt;br /&gt;
=== Hosts and co-hosts ===&lt;br /&gt;
&lt;br /&gt;
Link to Guide&lt;br /&gt;
&lt;br /&gt;
=== Recording and publishing ===&lt;br /&gt;
&lt;br /&gt;
automatic recording helps&lt;br /&gt;
&lt;br /&gt;
=== What worked ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
=== What didn't work ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
== What would we try to do if we ran another event? ==&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124825</id>
		<title>FOSS4GUK 2020 Online - Lessons Learnt</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124825"/>
		<updated>2020-06-20T11:20:53Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: /* Finances */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''This is a draft at the moment!'''&lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
&lt;br /&gt;
[https://uk.osgeo.org/foss4gukonline2020/ FOSS4GUK 2020 Online] was hosted by the [https://uk.osgeo.org OSGeo:UK] committee on 17th June 2020 from 9.00am to 17.30pm UTC+1&lt;br /&gt;
&lt;br /&gt;
The event was free to attend with all of the costs (see below) funded from OSGeo:UK reserves. &lt;br /&gt;
&lt;br /&gt;
=== Delegates ===&lt;br /&gt;
&lt;br /&gt;
* 1,000 people registered&lt;br /&gt;
* We estimate about 600 attended&lt;br /&gt;
* Maximum number online at any time was 460, minimum was 205&lt;br /&gt;
* Delegates from 77 countries&lt;br /&gt;
** 48% from GB, 8% UK, 4% India&lt;br /&gt;
&lt;br /&gt;
=== [https://uk.osgeo.org/foss4gukonline2020/programme.html Programme] ===&lt;br /&gt;
&lt;br /&gt;
* 3 streams running for the whole day (except during keynotes)&lt;br /&gt;
** 2 keynotes&lt;br /&gt;
** 29 talks and demos&lt;br /&gt;
** 4 Lightning talks&lt;br /&gt;
* 38 Speakers (10 women)&lt;br /&gt;
* Coffee bar stream where delegates could hang out and chat (not heavily used)&lt;br /&gt;
&lt;br /&gt;
=== Finances ===&lt;br /&gt;
* The only costs were the fees for the zoom account for 1 month: £198&lt;br /&gt;
* Delegate donations:&lt;br /&gt;
** OSGeo:UK 63 individual donations - gross £1,810, net after Paypal fees £1,744 (as of 2020-06-20)&lt;br /&gt;
** MapAction ?&lt;br /&gt;
&lt;br /&gt;
== Tech and tools ==&lt;br /&gt;
&lt;br /&gt;
=== Choice of video conferencing platform ===&lt;br /&gt;
&lt;br /&gt;
What we looked at&lt;br /&gt;
&lt;br /&gt;
What we learnt&lt;br /&gt;
&lt;br /&gt;
Why we chose zoom&lt;br /&gt;
&lt;br /&gt;
Tiny number of complaints, no problem on the day&lt;br /&gt;
&lt;br /&gt;
Options for the future&lt;br /&gt;
&lt;br /&gt;
=== Eventbrite ===&lt;br /&gt;
&lt;br /&gt;
The pros and cons&lt;br /&gt;
&lt;br /&gt;
Free if you don't charge&lt;br /&gt;
&lt;br /&gt;
A bit pricey for low cost tickets&lt;br /&gt;
&lt;br /&gt;
OK email&lt;br /&gt;
&lt;br /&gt;
Easy to capture data like permission for further FOSS4G mailing, country&lt;br /&gt;
&lt;br /&gt;
Alternatives?&lt;br /&gt;
&lt;br /&gt;
=== WhatsAppp ===&lt;br /&gt;
&lt;br /&gt;
Team comms&lt;br /&gt;
&lt;br /&gt;
Volunteers Group, could have considered a speakers group&lt;br /&gt;
&lt;br /&gt;
Seems almost everyone uses&lt;br /&gt;
&lt;br /&gt;
=== Twitter ===&lt;br /&gt;
&lt;br /&gt;
not everyone is on twitter despite what we think&lt;br /&gt;
&lt;br /&gt;
== Event structure ==&lt;br /&gt;
&lt;br /&gt;
3 streams plus coffee bar, describe how it worked&lt;br /&gt;
&lt;br /&gt;
Link to programme&lt;br /&gt;
&lt;br /&gt;
=== Hosts and co-hosts ===&lt;br /&gt;
&lt;br /&gt;
Link to Guide&lt;br /&gt;
&lt;br /&gt;
=== Recording and publishing ===&lt;br /&gt;
&lt;br /&gt;
automatic recording helps&lt;br /&gt;
&lt;br /&gt;
=== What worked ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
=== What didn't work ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
== What would we try to do if we ran another event? ==&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124824</id>
		<title>FOSS4GUK 2020 Online - Lessons Learnt</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124824"/>
		<updated>2020-06-20T11:15:21Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''This is a draft at the moment!'''&lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
&lt;br /&gt;
[https://uk.osgeo.org/foss4gukonline2020/ FOSS4GUK 2020 Online] was hosted by the [https://uk.osgeo.org OSGeo:UK] committee on 17th June 2020 from 9.00am to 17.30pm UTC+1&lt;br /&gt;
&lt;br /&gt;
The event was free to attend with all of the costs (see below) funded from OSGeo:UK reserves. &lt;br /&gt;
&lt;br /&gt;
=== Delegates ===&lt;br /&gt;
&lt;br /&gt;
* 1,000 people registered&lt;br /&gt;
* We estimate about 600 attended&lt;br /&gt;
* Maximum number online at any time was 460, minimum was 205&lt;br /&gt;
* Delegates from 77 countries&lt;br /&gt;
** 48% from GB, 8% UK, 4% India&lt;br /&gt;
&lt;br /&gt;
=== [https://uk.osgeo.org/foss4gukonline2020/programme.html Programme] ===&lt;br /&gt;
&lt;br /&gt;
* 3 streams running for the whole day (except during keynotes)&lt;br /&gt;
** 2 keynotes&lt;br /&gt;
** 29 talks and demos&lt;br /&gt;
** 4 Lightning talks&lt;br /&gt;
* 38 Speakers (10 women)&lt;br /&gt;
* Coffee bar stream where delegates could hang out and chat (not heavily used)&lt;br /&gt;
&lt;br /&gt;
=== Finances ===&lt;br /&gt;
* The only costs were the fees for the zoom account for 1 month: £198&lt;br /&gt;
* Delegate donations:&lt;br /&gt;
** OSGeo:UK Gross £1,810, Net after Paypal fees £1,744 (as of 2020-06-20)&lt;br /&gt;
** MapAction ?&lt;br /&gt;
&lt;br /&gt;
== Tech and tools ==&lt;br /&gt;
&lt;br /&gt;
=== Choice of video conferencing platform ===&lt;br /&gt;
&lt;br /&gt;
What we looked at&lt;br /&gt;
&lt;br /&gt;
What we learnt&lt;br /&gt;
&lt;br /&gt;
Why we chose zoom&lt;br /&gt;
&lt;br /&gt;
Tiny number of complaints, no problem on the day&lt;br /&gt;
&lt;br /&gt;
Options for the future&lt;br /&gt;
&lt;br /&gt;
=== Eventbrite ===&lt;br /&gt;
&lt;br /&gt;
The pros and cons&lt;br /&gt;
&lt;br /&gt;
Free if you don't charge&lt;br /&gt;
&lt;br /&gt;
A bit pricey for low cost tickets&lt;br /&gt;
&lt;br /&gt;
OK email&lt;br /&gt;
&lt;br /&gt;
Easy to capture data like permission for further FOSS4G mailing, country&lt;br /&gt;
&lt;br /&gt;
Alternatives?&lt;br /&gt;
&lt;br /&gt;
=== WhatsAppp ===&lt;br /&gt;
&lt;br /&gt;
Team comms&lt;br /&gt;
&lt;br /&gt;
Volunteers Group, could have considered a speakers group&lt;br /&gt;
&lt;br /&gt;
Seems almost everyone uses&lt;br /&gt;
&lt;br /&gt;
=== Twitter ===&lt;br /&gt;
&lt;br /&gt;
not everyone is on twitter despite what we think&lt;br /&gt;
&lt;br /&gt;
== Event structure ==&lt;br /&gt;
&lt;br /&gt;
3 streams plus coffee bar, describe how it worked&lt;br /&gt;
&lt;br /&gt;
Link to programme&lt;br /&gt;
&lt;br /&gt;
=== Hosts and co-hosts ===&lt;br /&gt;
&lt;br /&gt;
Link to Guide&lt;br /&gt;
&lt;br /&gt;
=== Recording and publishing ===&lt;br /&gt;
&lt;br /&gt;
automatic recording helps&lt;br /&gt;
&lt;br /&gt;
=== What worked ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
=== What didn't work ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
== What would we try to do if we ran another event? ==&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124823</id>
		<title>FOSS4GUK 2020 Online - Lessons Learnt</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124823"/>
		<updated>2020-06-20T11:13:40Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: Summary section and numbers completed&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''This is a draft at the moment!'''&lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
&lt;br /&gt;
[https://uk.osgeo.org/foss4gukonline2020/ FOSS4GUK 2020 Online] was hosted by the [https://uk.osgeo.org OSGeo:UK] committee on 17th June 2020 from 9.00am to 17.30pm UTC+1&lt;br /&gt;
&lt;br /&gt;
The event was free to attend with all of the costs (see below) funded from OSGeo:UK reserves. &lt;br /&gt;
=== Numbers ===&lt;br /&gt;
&lt;br /&gt;
==== Delegates ====&lt;br /&gt;
&lt;br /&gt;
* 1,000 people registered&lt;br /&gt;
* We estimate about 600 attended&lt;br /&gt;
* Maximum number online at any time was 460, minimum was 205&lt;br /&gt;
* Delegates from 77 countries&lt;br /&gt;
** 48% from GB, 8% UK, 4% India&lt;br /&gt;
&lt;br /&gt;
==== [https://uk.osgeo.org/foss4gukonline2020/programme.html Programme] ====&lt;br /&gt;
&lt;br /&gt;
* 3 streams running for the whole day (except during keynotes)&lt;br /&gt;
** 2 keynotes&lt;br /&gt;
** 29 talks and demos&lt;br /&gt;
** 4 Lightning talks&lt;br /&gt;
* 38 Speakers (10 women)&lt;br /&gt;
* Coffee bar stream where delegates could hang out and chat (not heavily used)&lt;br /&gt;
&lt;br /&gt;
==== Finances ====&lt;br /&gt;
* The only costs were the fees for the zoom account for 1 month: £198&lt;br /&gt;
* Delegate donations:&lt;br /&gt;
** OSGeo:UK Gross £1,810, Net after Paypal fees £1,744 (as of 2020-06-20)&lt;br /&gt;
** MapAction ?&lt;br /&gt;
&lt;br /&gt;
== Tech and tools ==&lt;br /&gt;
&lt;br /&gt;
=== Choice of video conferencing platform ===&lt;br /&gt;
&lt;br /&gt;
What we looked at&lt;br /&gt;
&lt;br /&gt;
What we learnt&lt;br /&gt;
&lt;br /&gt;
Why we chose zoom&lt;br /&gt;
&lt;br /&gt;
Tiny number of complaints, no problem on the day&lt;br /&gt;
&lt;br /&gt;
Options for the future&lt;br /&gt;
&lt;br /&gt;
=== Eventbrite ===&lt;br /&gt;
&lt;br /&gt;
The pros and cons&lt;br /&gt;
&lt;br /&gt;
Free if you don't charge&lt;br /&gt;
&lt;br /&gt;
A bit pricey for low cost tickets&lt;br /&gt;
&lt;br /&gt;
OK email&lt;br /&gt;
&lt;br /&gt;
Easy to capture data like permission for further FOSS4G mailing, country&lt;br /&gt;
&lt;br /&gt;
Alternatives?&lt;br /&gt;
&lt;br /&gt;
=== WhatsAppp ===&lt;br /&gt;
&lt;br /&gt;
Team comms&lt;br /&gt;
&lt;br /&gt;
Volunteers Group, could have considered a speakers group&lt;br /&gt;
&lt;br /&gt;
Seems almost everyone uses&lt;br /&gt;
&lt;br /&gt;
=== Twitter ===&lt;br /&gt;
&lt;br /&gt;
not everyone is on twitter despite what we think&lt;br /&gt;
&lt;br /&gt;
== Event structure ==&lt;br /&gt;
&lt;br /&gt;
3 streams plus coffee bar, describe how it worked&lt;br /&gt;
&lt;br /&gt;
Link to programme&lt;br /&gt;
&lt;br /&gt;
=== Hosts and co-hosts ===&lt;br /&gt;
&lt;br /&gt;
Link to Guide&lt;br /&gt;
&lt;br /&gt;
=== Recording and publishing ===&lt;br /&gt;
&lt;br /&gt;
automatic recording helps&lt;br /&gt;
&lt;br /&gt;
=== What worked ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
=== What didn't work ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
== What would we try to do if we ran another event? ==&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124822</id>
		<title>FOSS4GUK 2020 Online - Lessons Learnt</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124822"/>
		<updated>2020-06-20T10:33:21Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''This is a draft at the moment!'''&lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
&lt;br /&gt;
[https://uk.osgeo.org/foss4gukonline2020/ FOSS4GUK 2020 Online] was hosted by the [https://uk.osgeo.org OSGeo:UK] committee on 17th June 2020 from 9.00am to 17.30pm UTC+1&lt;br /&gt;
&lt;br /&gt;
The event was free to attend with all of the costs (see below) funded from OSGeo:UK reserves. &lt;br /&gt;
=== Numbers ===&lt;br /&gt;
&lt;br /&gt;
==== Delegates ====&lt;br /&gt;
&lt;br /&gt;
* 1,000 people registered&lt;br /&gt;
* We estimate about 600 attended&lt;br /&gt;
* Maximum number online at any time was 460, minimum was 205&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
Finances and donations&lt;br /&gt;
Speakers&lt;br /&gt;
Geography&lt;br /&gt;
&lt;br /&gt;
== Tech and tools ==&lt;br /&gt;
&lt;br /&gt;
=== Choice of video conferencing platform ===&lt;br /&gt;
&lt;br /&gt;
What we looked at&lt;br /&gt;
&lt;br /&gt;
What we learnt&lt;br /&gt;
&lt;br /&gt;
Why we chose zoom&lt;br /&gt;
&lt;br /&gt;
Tiny number of complaints, no problem on the day&lt;br /&gt;
&lt;br /&gt;
Options for the future&lt;br /&gt;
&lt;br /&gt;
=== Eventbrite ===&lt;br /&gt;
&lt;br /&gt;
The pros and cons&lt;br /&gt;
&lt;br /&gt;
Free if you don't charge&lt;br /&gt;
&lt;br /&gt;
A bit pricey for low cost tickets&lt;br /&gt;
&lt;br /&gt;
OK email&lt;br /&gt;
&lt;br /&gt;
Easy to capture data like permission for further FOSS4G mailing, country&lt;br /&gt;
&lt;br /&gt;
Alternatives?&lt;br /&gt;
&lt;br /&gt;
=== WhatsAppp ===&lt;br /&gt;
&lt;br /&gt;
Team comms&lt;br /&gt;
&lt;br /&gt;
Volunteers Group, could have considered a speakers group&lt;br /&gt;
&lt;br /&gt;
Seems almost everyone uses&lt;br /&gt;
&lt;br /&gt;
=== Twitter ===&lt;br /&gt;
&lt;br /&gt;
not everyone is on twitter despite what we think&lt;br /&gt;
&lt;br /&gt;
== Event structure ==&lt;br /&gt;
&lt;br /&gt;
3 streams plus coffee bar, describe how it worked&lt;br /&gt;
&lt;br /&gt;
Link to programme&lt;br /&gt;
&lt;br /&gt;
=== Hosts and co-hosts ===&lt;br /&gt;
&lt;br /&gt;
Link to Guide&lt;br /&gt;
&lt;br /&gt;
=== Recording and publishing ===&lt;br /&gt;
&lt;br /&gt;
automatic recording helps&lt;br /&gt;
&lt;br /&gt;
=== What worked ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
=== What didn't work ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
== What would we try to do if we ran another event? ==&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124821</id>
		<title>FOSS4GUK 2020 Online - Lessons Learnt</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124821"/>
		<updated>2020-06-20T10:27:41Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''This is a draft at the moment!'''&lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
&lt;br /&gt;
[https://uk.osgeo.org/foss4gukonline2020/ FOSS4GUK 2020 Online] was hosted by the [https://uk.osgeo.org OSGeo:UK] committee on 17th June 2020 from 9.00am to 17.30pm UTC+1&lt;br /&gt;
&lt;br /&gt;
The event was free to attend with all of the costs (see below) funded from OSGeo:UK reserves. &lt;br /&gt;
=== Numbers ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Finances and donations&lt;br /&gt;
Speakers&lt;br /&gt;
Geography&lt;br /&gt;
&lt;br /&gt;
== Tech and tools ==&lt;br /&gt;
&lt;br /&gt;
=== Choice of video conferencing platform ===&lt;br /&gt;
&lt;br /&gt;
What we looked at&lt;br /&gt;
&lt;br /&gt;
What we learnt&lt;br /&gt;
&lt;br /&gt;
Why we chose zoom&lt;br /&gt;
&lt;br /&gt;
Tiny number of complaints, no problem on the day&lt;br /&gt;
&lt;br /&gt;
Options for the future&lt;br /&gt;
&lt;br /&gt;
=== Eventbrite ===&lt;br /&gt;
&lt;br /&gt;
The pros and cons&lt;br /&gt;
&lt;br /&gt;
Free if you don't charge&lt;br /&gt;
&lt;br /&gt;
A bit pricey for low cost tickets&lt;br /&gt;
&lt;br /&gt;
OK email&lt;br /&gt;
&lt;br /&gt;
Easy to capture data like permission for further FOSS4G mailing, country&lt;br /&gt;
&lt;br /&gt;
Alternatives?&lt;br /&gt;
&lt;br /&gt;
=== WhatsAppp ===&lt;br /&gt;
&lt;br /&gt;
Team comms&lt;br /&gt;
&lt;br /&gt;
Volunteers Group, could have considered a speakers group&lt;br /&gt;
&lt;br /&gt;
Seems almost everyone uses&lt;br /&gt;
&lt;br /&gt;
=== Twitter ===&lt;br /&gt;
&lt;br /&gt;
not everyone is on twitter despite what we think&lt;br /&gt;
&lt;br /&gt;
== Event structure ==&lt;br /&gt;
&lt;br /&gt;
3 streams plus coffee bar, describe how it worked&lt;br /&gt;
&lt;br /&gt;
Link to programme&lt;br /&gt;
&lt;br /&gt;
=== Hosts and co-hosts ===&lt;br /&gt;
&lt;br /&gt;
Link to Guide&lt;br /&gt;
&lt;br /&gt;
=== Recording and publishing ===&lt;br /&gt;
&lt;br /&gt;
automatic recording helps&lt;br /&gt;
&lt;br /&gt;
=== What worked ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
=== What didn't work ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
== What would we try to do if we ran another event? ==&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124814</id>
		<title>FOSS4GUK 2020 Online - Lessons Learnt</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124814"/>
		<updated>2020-06-18T20:36:43Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''This is a draft at the moment!'''&lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
&lt;br /&gt;
key facts about the event&lt;br /&gt;
&lt;br /&gt;
Link to website&lt;br /&gt;
&lt;br /&gt;
Numbers&lt;br /&gt;
Finances and donations&lt;br /&gt;
Speakers&lt;br /&gt;
Geography&lt;br /&gt;
&lt;br /&gt;
== Tech and tools ==&lt;br /&gt;
&lt;br /&gt;
=== Choice of video conferencing platform ===&lt;br /&gt;
&lt;br /&gt;
What we looked at&lt;br /&gt;
&lt;br /&gt;
What we learnt&lt;br /&gt;
&lt;br /&gt;
Why we chose zoom&lt;br /&gt;
&lt;br /&gt;
Tiny number of complaints, no problem on the day&lt;br /&gt;
&lt;br /&gt;
Options for the future&lt;br /&gt;
&lt;br /&gt;
=== Eventbrite ===&lt;br /&gt;
&lt;br /&gt;
The pros and cons&lt;br /&gt;
&lt;br /&gt;
Free if you don't charge&lt;br /&gt;
&lt;br /&gt;
A bit pricey for low cost tickets&lt;br /&gt;
&lt;br /&gt;
OK email&lt;br /&gt;
&lt;br /&gt;
Easy to capture data like permission for further FOSS4G mailing, country&lt;br /&gt;
&lt;br /&gt;
Alternatives?&lt;br /&gt;
&lt;br /&gt;
=== WhatsAppp ===&lt;br /&gt;
&lt;br /&gt;
Team comms&lt;br /&gt;
&lt;br /&gt;
Volunteers Group, could have considered a speakers group&lt;br /&gt;
&lt;br /&gt;
Seems almost everyone uses&lt;br /&gt;
&lt;br /&gt;
=== Twitter ===&lt;br /&gt;
&lt;br /&gt;
not everyone is on twitter despite what we think&lt;br /&gt;
&lt;br /&gt;
== Event structure ==&lt;br /&gt;
&lt;br /&gt;
3 streams plus coffee bar, describe how it worked&lt;br /&gt;
&lt;br /&gt;
Link to programme&lt;br /&gt;
&lt;br /&gt;
=== Hosts and co-hosts ===&lt;br /&gt;
&lt;br /&gt;
Link to Guide&lt;br /&gt;
&lt;br /&gt;
=== Recording and publishing ===&lt;br /&gt;
&lt;br /&gt;
automatic recording helps&lt;br /&gt;
&lt;br /&gt;
=== What worked ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
=== What didn't work ===&lt;br /&gt;
&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
== What would we try to do if we ran another event? ==&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124813</id>
		<title>FOSS4GUK 2020 Online - Lessons Learnt</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124813"/>
		<updated>2020-06-18T20:33:28Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''This is a draft at the moment!'''&lt;br /&gt;
&lt;br /&gt;
== Summary ==&lt;br /&gt;
&lt;br /&gt;
key facts about the event&lt;br /&gt;
&lt;br /&gt;
Link to website&lt;br /&gt;
&lt;br /&gt;
Numbers&lt;br /&gt;
Finances and donations&lt;br /&gt;
Speakers&lt;br /&gt;
Geography&lt;br /&gt;
&lt;br /&gt;
== Tech and tools ==&lt;br /&gt;
&lt;br /&gt;
=== Choice of video conferencing platform ===&lt;br /&gt;
&lt;br /&gt;
What we looked at&lt;br /&gt;
What we learnt&lt;br /&gt;
Why we chose zoom&lt;br /&gt;
Tiny number of complaints, no problem on the day&lt;br /&gt;
Options for the future&lt;br /&gt;
&lt;br /&gt;
=== Eventbrite ===&lt;br /&gt;
&lt;br /&gt;
The pros and cons&lt;br /&gt;
Free if you don't charge&lt;br /&gt;
A bit pricey for low cost tickets&lt;br /&gt;
OK email&lt;br /&gt;
Easy to capture data like permission for further FOSS4G mailing, country&lt;br /&gt;
&lt;br /&gt;
Alternatives?&lt;br /&gt;
&lt;br /&gt;
=== WhatsAppp ===&lt;br /&gt;
Team comms&lt;br /&gt;
Volunteers Group, could have considered a speakers group&lt;br /&gt;
Seems almost everyone uses&lt;br /&gt;
&lt;br /&gt;
=== Twitter ===&lt;br /&gt;
not everyone is on twitter despite what we think&lt;br /&gt;
&lt;br /&gt;
== Event structure ==&lt;br /&gt;
&lt;br /&gt;
3 streams plus coffee bar, describe how it worked&lt;br /&gt;
Link to programme&lt;br /&gt;
&lt;br /&gt;
=== Hosts and co-hosts ===&lt;br /&gt;
Link to Guide&lt;br /&gt;
&lt;br /&gt;
=== Recording and publishing ===&lt;br /&gt;
automatic recording helps&lt;br /&gt;
&lt;br /&gt;
=== What worked ===&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
=== What didn't work ===&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
== What would we try to do if we ran another event? ==&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124812</id>
		<title>FOSS4GUK 2020 Online - Lessons Learnt</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=FOSS4GUK_2020_Online_-_Lessons_Learnt&amp;diff=124812"/>
		<updated>2020-06-18T20:26:15Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: Stub page for lessons learnt from FOSS4GUK 2020 Online&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''This is a draft at the moment!'''&lt;br /&gt;
&lt;br /&gt;
# Summary&lt;br /&gt;
&lt;br /&gt;
key facts about the event&lt;br /&gt;
&lt;br /&gt;
Link to website&lt;br /&gt;
&lt;br /&gt;
Numbers&lt;br /&gt;
Finances and donations&lt;br /&gt;
Speakers&lt;br /&gt;
Geography&lt;br /&gt;
&lt;br /&gt;
# Tech and tools&lt;br /&gt;
&lt;br /&gt;
## Choice of video conferencing platform&lt;br /&gt;
&lt;br /&gt;
What we looked at&lt;br /&gt;
What we learnt&lt;br /&gt;
Why we chose zoom&lt;br /&gt;
Tiny number of complaints, no problem on the day&lt;br /&gt;
Options for the future&lt;br /&gt;
&lt;br /&gt;
## Eventbrite&lt;br /&gt;
&lt;br /&gt;
The pros and cons&lt;br /&gt;
Free if you don't charge&lt;br /&gt;
A bit pricey for low cost tickets&lt;br /&gt;
OK email&lt;br /&gt;
Easy to capture data like permission for further FOSS4G mailing, country&lt;br /&gt;
&lt;br /&gt;
Alternatives?&lt;br /&gt;
&lt;br /&gt;
## WhatsAppp&lt;br /&gt;
Team comms&lt;br /&gt;
Volunteers Group, could have considered a speakers group&lt;br /&gt;
Seems almost everyone uses&lt;br /&gt;
&lt;br /&gt;
## Twitter&lt;br /&gt;
not everyone is on twitter despite what we think&lt;br /&gt;
&lt;br /&gt;
# Event structure&lt;br /&gt;
&lt;br /&gt;
3 streams plus coffee bar, describe how it worked&lt;br /&gt;
Link to programme&lt;br /&gt;
&lt;br /&gt;
## Hosts and co-hosts&lt;br /&gt;
Link to Guide&lt;br /&gt;
&lt;br /&gt;
## Recording and publishing&lt;br /&gt;
&lt;br /&gt;
## What worked&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
## What didn't work&lt;br /&gt;
List our reflections&lt;br /&gt;
&lt;br /&gt;
# What would we try to do if we ran another event?&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=FOSS4G_Travel_Grant_Programme_Cookbook&amp;diff=123522</id>
		<title>FOSS4G Travel Grant Programme Cookbook</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=FOSS4G_Travel_Grant_Programme_Cookbook&amp;diff=123522"/>
		<updated>2020-02-23T13:31:38Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: /* Application criteria */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Setting up a FOSS4G TGP =&lt;br /&gt;
&lt;br /&gt;
This guidance is for those considering establishing a FOSS4G Travel Grant Program (TGP) for a regional event or becoming a member of a selection group for a FOSS4G TGP (global or regional). It is based on the experience and lessons learnt in running the 2017 &amp;amp; 2018 TGPs and the regional TGP in Oceania. Each FOSS4G TGP will develop its own approach and hopefully add to this advice.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Applications to the Conference Committee for OSGeo support =&lt;br /&gt;
&lt;br /&gt;
The OSGeo Foundation’s Conference Committee (CC) administers the FOSS4G Travel Grant Program on behalf of OSGeo. At the beginning of each calendar year the OSGeo board sets a budget for the TGP, the CC will aim to issue a call for applications for TGP support in early February and potentially will have a second call for applications in July (dependent on whether there is any unallocated budget).&lt;br /&gt;
&lt;br /&gt;
The global FOSS4G and regional LOCs should apply for TGP support by entering the details of their request in a wiki page that will be detailed when the call for applications is announced on the CC mailing list. It is anticipated that 50-60% of the TGP budget will be allocated to the global FOSS4G conference and that the balance will be available to support regional events. The CC may vary these percentages at their discretion.&lt;br /&gt;
&lt;br /&gt;
== Application criteria ==&lt;br /&gt;
The LOC should:&lt;br /&gt;
&lt;br /&gt;
# State the amount of TGP support requested in US dollars and confirm that the LOC will provide (at least) matching cash funding. The LOC should explain the source of their funding (e.g. a levy on ticket sales, a level on sponsor income, a specific sponsor, crowdfunding). &lt;br /&gt;
# Confirm that free full conference passes will be available to recipients of Travel Grants in addition to the cash funding provided by the LOC and OSGeo. &lt;br /&gt;
# Estimate the anticipated number of grants and their size. &lt;br /&gt;
# Set out the broad criteria that they will use to select applicants and indicate their priority groups (e.g. gender based, local/regional, specific deprived groups, some other criteria). &lt;br /&gt;
# Explain how your TGP will try to prioritise environmental sustainability in its selection process.&lt;br /&gt;
# Confirm that it has a team of volunteers available to administer the selection process and confirm whether it is seeking assistance from CC members in the selection process. &lt;br /&gt;
# Provide details of any accommodation available to TGP recipients e.g. a recommended hostel. Note that any recommended accommodation should be vetted as safe and secure for all event attendees. &lt;br /&gt;
# Outline the manner in which Travel Grants will be paid to recipients and by whom (e.g. cash, PayPal, bank transfer, etc).&lt;br /&gt;
&lt;br /&gt;
== Donations ==&lt;br /&gt;
OSGeo has a PayPal account which can be used to collect donations from individuals (and companies) - the “donate” link is on [https://www.osgeo.org/initiatives/foss4g-travel-grant-program this page].&lt;br /&gt;
&lt;br /&gt;
You should let the OSGeo Treasurer know if you are planning to direct donors to this link so that they can identify the donations and transfer them to your TGP.&lt;br /&gt;
&lt;br /&gt;
== Confirmation of TGP funding ==&lt;br /&gt;
The CC will confirm TGP funding to the LOC and clarify any additional conditions or terms as needed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Running a TGP =&lt;br /&gt;
&lt;br /&gt;
== Getting started ==&lt;br /&gt;
You need to appoint a chair of selectors who will 'run' the process and keep things on track.&lt;br /&gt;
&lt;br /&gt;
Set clear eligibility guidelines - this will help would-be applicants determine whether they can/should apply, and will save you time in the selections stage. As an example: ''You must be a resident of &amp;lt;your geographic region&amp;gt; to be eligible for this grant''. (This is only an example, you can set your own eligibility guidelines)&lt;br /&gt;
&lt;br /&gt;
You'll need to consider carefully whether you provide grants in advance, or only on arrival at the conference. By withholding funds until the grantee arrives at the conference, you probably reduce the risk of no-shows, but some people might find it difficult to come up with the funds up front. One way to manage this is to err on the side of offering to pay grants on arrival, but inviting grantees to get in direct contact if this is difficult for them.&lt;br /&gt;
&lt;br /&gt;
== Timing ==&lt;br /&gt;
Work out a timeline - you should set specific dates for key milestones, for example:&lt;br /&gt;
# Launch call for applications&lt;br /&gt;
## The LOC can/should publish the call for applications on [https://www.osgeo.org/initiatives/foss4g-travel-grant-program the OSGeo website]&lt;br /&gt;
# Application deadline: 14-28 days after launching call for applications (recommend a minimum of 2 weeks and ideally 3-4 weeks)&lt;br /&gt;
# Selection date: 14-28 days after closing call for applications (you will need at least 2 weeks to evaluate applications, possibly 3 or 4 for a global TGP with a lot of entries)&lt;br /&gt;
&lt;br /&gt;
You may wish to set a period to ask questions or seek clarifications from some applicants.&lt;br /&gt;
&lt;br /&gt;
In some regions, it may be important to leave enough time before the event for grantees to secure visas for travel.&lt;br /&gt;
&lt;br /&gt;
If possible, run the TGP early enough that successful applicants have time to submit presentations and workshops.&lt;br /&gt;
&lt;br /&gt;
Bear in mind, the total amount of TGP money (donations, grants from OSGeo etc.) should be known when announcing the number of possible grants.  If you publish early and subsequently identify additional funding, there is the possibility to announce more grants later in the process.&lt;br /&gt;
&lt;br /&gt;
== Call for applications ==&lt;br /&gt;
The TGP team will need to draft an application form that includes questions that help to evaluate the applications against the LOC criteria. This is [https://docs.google.com/forms/d/e/1FAIpQLSf53t3ToF6xHjGlKEmgWrihoaf5w9e1SGYZakZx-cd0hR9cNg/viewform a copy of a Google form] which was used in 2017, it fed into a spreadsheet. There is no need to use this form if you have an alternative tool that you prefer.&lt;br /&gt;
&lt;br /&gt;
This is your first chance to communicate with grant applicants - it's a good opportunity to provide important information so they know what to expect, and so they can write an application that clearly addresses the criteria. This can save you a lot of time later. Clearly articulate the objectives of the program, who it's trying to help, important dates (including deadline!), eligibility guidelines, and your selection criteria.&lt;br /&gt;
&lt;br /&gt;
You'll need to consider how you promote your program, to make sure you reach your audience. Use your committee's professional networks, make contacts with not-for-profits, agencies, and universities to spread the word. You can advertise your program on [https://www.osgeo.org/initiatives/foss4g-travel-grant-program the OSGeo website].&lt;br /&gt;
&lt;br /&gt;
You can also set up a Travel Grant page on the OSGeo website a bit like [https://www.osgeo.org/foundation-news/foss4g-2018-travel-grant-programme this] (this might be a duplicate or a link to a page on your event website)&lt;br /&gt;
&lt;br /&gt;
== Selection ==&lt;br /&gt;
# At the close of the application period the chair of selectors should collate all of the applications, anonymise them (so that selection is a &amp;quot;blind&amp;quot; process) and send to each selector.&lt;br /&gt;
# Each selector should devise their own personal marking scheme (i.e. you balance the different criteria in the way that you wish, giving more or less weight to income, gender, contribution etc). Each selector should to try to be consistent in the way that they evaluate each submission.&lt;br /&gt;
# Finally selectors will need to rank the submissions in descending order (based upon your marking). You will only be asked to rank slightly more than the likely number of grants that you will be making i.e. if there is a grant fund of $3,000 and you expect to make about 6 grants then each selector might be asked to rank your top 8 in descending order (8 for your top choice, then 7 etc).&lt;br /&gt;
# Be ready to handle large numbers of applications:&lt;br /&gt;
##FOSS4G 2017 had 86 applications, it took over 4 hours to review, mark and rank them&lt;br /&gt;
## FOSS4G 2018 had 156 applications&lt;br /&gt;
## the regional FOSS4G SotM Oceania 2018 had 45 applications&lt;br /&gt;
# Once the individual selections are completed, the chair will combine the rankings from each of the selectors to provide an overall ranking.&lt;br /&gt;
# You may then need to schedule a call to discuss any marginal choices.&lt;br /&gt;
# Once you have finalised your selections, you should:&lt;br /&gt;
## contact the applicants who have been successful&lt;br /&gt;
## notify the next few who just missed the cut that they are on a “standby” list&lt;br /&gt;
## contact those who have not been successful&lt;br /&gt;
# There is then a wait while people confirm their acceptance of the grant, provide evidence of eligibility criteria, travel plans, visas, etc.&lt;br /&gt;
&lt;br /&gt;
= Run up to the event =&lt;br /&gt;
There will be quite a lot of correspondence with grant recipients in the run up to the event. In many cases, grantees will be stepping outside their comfort zone, and we encourage you to stay in close contact and provide support while they make their travel plans. If practical, nominate a person to be the key point of contact with TGP grantees. Having a personal contact, rather than a generic ''tgp@your-event.org'' email, will build a sense of mutual trust and make it easier for grantees to get in touch if there are difficulties with travel plans, visas, etc.&lt;br /&gt;
&lt;br /&gt;
We recommend that you get confirmation that the grant recipients will be able to receive funds electronically as you really really really do not want to be trying to issue grants in cash at the conference. However, in many cases, TGP attendees will come from countries with different currencies and banking systems from that of the LOC. This may make direct electronic transfers difficult and you may have to resort to cash. Try to be as adaptable as possible to the needs of the grantees.&lt;br /&gt;
&lt;br /&gt;
= At the event =&lt;br /&gt;
Look for opportunities to be inclusive of TGP attendees, and make them feel welcome and involved, for example:&lt;br /&gt;
# A breakfast for TGP grantees to meet each other, with event organisers in attendance to welcome them.&lt;br /&gt;
# Birds of a Feather sessions.&lt;br /&gt;
# Try and organise a group photo.&lt;br /&gt;
# Ask the grantees to write a short blog post (2-300 words) with a couple of pics that you can publish after the event. It helps to explain the benefits of the TGP to the wider community and helps with fundraising for future events. This could be a requirement on the application form.&lt;br /&gt;
# If practical, nominate a person to welcome TGP attendees to the event and be the key on-site point of contact if they need any help.&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=OSGeo_Budget_2020&amp;diff=122850</id>
		<title>OSGeo Budget 2020</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=OSGeo_Budget_2020&amp;diff=122850"/>
		<updated>2019-12-30T10:42:48Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: /* OSGeo Initiatives */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''DRAFT'''&lt;br /&gt;
&lt;br /&gt;
Draft budget to be discussed in December board meeting, see [[OSGeo Budget 2019]] and [[Finance Committee#Documents]] for prior years.&lt;br /&gt;
&lt;br /&gt;
Total Approved Budget for 2019: $230,150 USD&lt;br /&gt;
&lt;br /&gt;
Total Approved Budget for 2020: $TBD USD&lt;br /&gt;
&lt;br /&gt;
== OSGeo Board ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! Board&lt;br /&gt;
! 2019&lt;br /&gt;
! 2019 Actual&lt;br /&gt;
! 2020&lt;br /&gt;
! Notes&lt;br /&gt;
|- &lt;br /&gt;
| Admin&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 3,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Operational expenses including liability insurance, tax filing fees, accountant, bank fees.&lt;br /&gt;
|-&lt;br /&gt;
| Travel&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 22,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Travel to main FOSS4G and F2F meeting (15k), and regional/representative events (7k)&lt;br /&gt;
|-&lt;br /&gt;
| Partners&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Relationship building, attending b2b functions, foss4g/foss4ge/foss4gna/foss4g-asia breakfast meetings&lt;br /&gt;
|-&lt;br /&gt;
| Sponsors&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Meetings with sponsors during events&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Total Board Budget for 2019: $29,000 USD&lt;br /&gt;
&lt;br /&gt;
Total Board Budget for 2020: $TBD USD&lt;br /&gt;
&lt;br /&gt;
== OSGeo Committees ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* Code of Conduct Committee&lt;br /&gt;
* Conference Committee&lt;br /&gt;
* GeoForAll - committee acting as advisory board for the GeoForAll Initiative &lt;br /&gt;
* Incubation Committee - committee providing hands-on support for project teams adopting open source principles and practice.&lt;br /&gt;
* Marketing Committee - outreach and advocacy support&lt;br /&gt;
* Open GeoScience Committee&lt;br /&gt;
* System Administration Committee - foundation infrastructure &lt;br /&gt;
* UN Committee - committee responsible for our participation in the UN Open GIS program&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! OSGeo Committees&lt;br /&gt;
! 2019&lt;br /&gt;
! 2019 Actual&lt;br /&gt;
! 2020&lt;br /&gt;
! Notes&lt;br /&gt;
|- &lt;br /&gt;
| SAC&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 23,750&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| Open GeoScience&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 6,100&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 1064 (EGU event) + X&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 7,562&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| Conference&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| Marketing&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 27,600&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 22,600&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 23,800&lt;br /&gt;
| See [[Marketing Committee Budget 2020]] for activities&lt;br /&gt;
|-&lt;br /&gt;
| GeoForAll&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 3,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 8,000&lt;br /&gt;
| There was no requests for G4A prizes in 2019. &lt;br /&gt;
For 2020, an activity similar to Hacktober/GCI/bug bounty is planned. This will be opened to everyone. The award for participating will be a t-shirt. $5,000 is requested for the printing and shipping of 250 t-shirts. The aim of the activity will be to encourage existing or new members to contribute to either the code or docs of OSGeo projects. This would be the higher priority activity for 2020. &amp;lt;br /&amp;gt; &lt;br /&gt;
Then we would like to request two awards of $1500 (total $3000) for a microgrant award. The idea with the grant is to encourage G4A labs to contribute and work together.  &lt;br /&gt;
|-&lt;br /&gt;
| UN Committee&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 11,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 1,051 euro + 6,000 $&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 9,000 &lt;br /&gt;
| Activities of the Committe available at https://wiki.osgeo.org/wiki/UnitedNations_Committee &lt;br /&gt;
Budget 2019: the expenses are less because a Field Mission in South Sudan was cancelled; &lt;br /&gt;
Budget 2020: 2 OSGeo Challenges (6,000) + 3,000 for the Partecipation at the &amp;quot;6th International Symposium on Partnership for Technology in Peacekeeping&amp;quot; 22-26 June 2020)&lt;br /&gt;
|-&lt;br /&gt;
| Incubation Committee&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 10,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 10,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 12,000&lt;br /&gt;
| No operational budget requested (board's community initiative takes care of that). Funds requested strictly to be used to support team/mentor activities towards completing osgeo incubation requirements.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Total Committees Budget for 2019: $76,450 USD&lt;br /&gt;
&lt;br /&gt;
Total Committees Budget for 2020: $TBD USD&lt;br /&gt;
&lt;br /&gt;
== OSGeo Initiatives ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
* FOSS4G - event series produced in collaboration with the conference committee and local chapters&lt;br /&gt;
* GeoForAll - education and research program produced in collaboration with our partners&lt;br /&gt;
* Incubation - mentor program for open source projects to be recognized as OSGeo project&lt;br /&gt;
* Local Chapters - board outreach initiative establishing regional OSGeo groups for direct grassroots advoacacy&lt;br /&gt;
* Meta CRS - interoperability initiative promoting data sharing with cross project spatial reference system compatibility&lt;br /&gt;
* Open GeoScience - outreach and advocacy geoscience community&lt;br /&gt;
* GSoC - coordinate participation in google-summer-of-code and code-in activities&lt;br /&gt;
* Travel Grant Program - provides assistance for attending OSGeo events&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! OSGeo Initiatives&lt;br /&gt;
! 2019&lt;br /&gt;
! 2019 Actual&lt;br /&gt;
! 2020&lt;br /&gt;
! Notes&lt;br /&gt;
|- &lt;br /&gt;
| FOSS4G&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Managed by Conference Committee. Seed money for 2020 will be allocated by the board when estimate numbers become available.&lt;br /&gt;
|-&lt;br /&gt;
| Local Chapters&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 5,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| 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)&lt;br /&gt;
|-&lt;br /&gt;
| Travel Grant Program &lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 25.000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; |15-18,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 25,000&lt;br /&gt;
| (Need to check actual spend in 2019)&lt;br /&gt;
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.&lt;br /&gt;
|-&lt;br /&gt;
| Events and Code Sprints&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 15,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| 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.)&lt;br /&gt;
|-&lt;br /&gt;
| Community Projects&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 15,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Managed by the board since community projects do not have an assigned officer to handle their budget. We have around 23-25 projects expected in 2020 (see list bellow). Budgeted 1000$ for each project.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Total Initiatives Budget for 2019: $60,000 USD&lt;br /&gt;
&lt;br /&gt;
Total Initiatives Budget for 2020: $TBD USD&lt;br /&gt;
&lt;br /&gt;
= Projects =&lt;br /&gt;
&lt;br /&gt;
==  OSGeo Projects ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Notes:&lt;br /&gt;
&lt;br /&gt;
* We have reached out (2019) to the projects mailing list with a default suggestion of 2000 for any project that responds&lt;br /&gt;
* Projects with a plan may of course ask for increased funding&lt;br /&gt;
* This is a budget, representing planned spending in 2020 - actual balance available to each PSC (from fundraising, donations and sponsorship) may be considered when planning.&lt;br /&gt;
* If a project did not respond (or runs into an unforeseen expense) please contact the board throughout the year as budgets can be amended&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! OSGeo Project&lt;br /&gt;
! 2019&lt;br /&gt;
! 2019 Actual&lt;br /&gt;
! 2020&lt;br /&gt;
! Notes&lt;br /&gt;
|- &lt;br /&gt;
| deegree&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GDAL/OGR&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 5,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GeoMOOSE&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GeoNetwork&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GeoNode&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GEOS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 1,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GeoServer&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 7,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 7,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 5,000&lt;br /&gt;
| [[GeoServer Budget 2020]]&lt;br /&gt;
|-&lt;br /&gt;
| GeoTools&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 5,000&lt;br /&gt;
| [https://github.com/geotools/geotools/wiki/GeoTools-Budget-Request-2020 GeoTools Budget Request 2020]&lt;br /&gt;
|-&lt;br /&gt;
| GRASS GIS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 9,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| [https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2020 GRASS GIS Budget 2020]&lt;br /&gt;
|-&lt;br /&gt;
| gvSIG&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 5,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| Details of the budget at [[GvSIG Budget 2020]]&lt;br /&gt;
|-&lt;br /&gt;
| Mapbender&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| MapServer&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
|  &lt;br /&gt;
|-&lt;br /&gt;
| Marble&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 1,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| OpenLayers&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 3,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| [[OpenLayers_Budget_2020]]&lt;br /&gt;
|-&lt;br /&gt;
| OTB&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| OSGeoLive&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| PostGIS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 3,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| PROJ&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | N/A&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | N/A&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| pycsw&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 3,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| [[Pycsw_budget_2020]]&lt;br /&gt;
|-&lt;br /&gt;
| PyWPS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 3,200&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| QGIS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 8,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Total Projects Budget for 2019: $64,700 USD&lt;br /&gt;
&lt;br /&gt;
Total Projects Budget for 2020: $TBD USD&lt;br /&gt;
&lt;br /&gt;
==  Community Projects ==&lt;br /&gt;
&lt;br /&gt;
Community projects act through the board as they do not have a project officer. Board approved $TBD for each project (see Community Projects Initiative above)&lt;br /&gt;
&lt;br /&gt;
* actinia&lt;br /&gt;
* FDO&lt;br /&gt;
* GC2/Vidi&lt;br /&gt;
* GeoExt&lt;br /&gt;
* GeoHealthCheck&lt;br /&gt;
* Geomajas&lt;br /&gt;
* GeoServer Client PHP&lt;br /&gt;
* GeoWebCache&lt;br /&gt;
* istSOS&lt;br /&gt;
* Loader&lt;br /&gt;
* MapGuide Open Source&lt;br /&gt;
* Mapfish&lt;br /&gt;
* Opticks&lt;br /&gt;
* OSGeo4W&lt;br /&gt;
* OSSIM&lt;br /&gt;
* OWSLib&lt;br /&gt;
* pgRouting&lt;br /&gt;
* PortableGIS&lt;br /&gt;
* Pronto Raster&lt;br /&gt;
* pygeoapi&lt;br /&gt;
* rasdaman&lt;br /&gt;
* TEAM Engine&lt;br /&gt;
* ZOO-Project&lt;br /&gt;
&lt;br /&gt;
Some incubation projects are not yet set up as part of OSGeo community:&lt;br /&gt;
&lt;br /&gt;
* Oskari&lt;br /&gt;
&lt;br /&gt;
Some guidance is offered by individual projects below:&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! Community Project&lt;br /&gt;
! 2019&lt;br /&gt;
! 2019 Actual&lt;br /&gt;
! 2020&lt;br /&gt;
! Notes&lt;br /&gt;
|- &lt;br /&gt;
| ZOO-Project&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot;| up to 4,000 (need specific requests to board and incubation committee)&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| pgRouting&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot;| up to 4,000 (need specific requests to board and incubation committee)&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| istSOS&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | up to 4,000 (need specific requests to board and incubation committee)&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Events =&lt;br /&gt;
&lt;br /&gt;
== Community Events ==&lt;br /&gt;
&lt;br /&gt;
We are considering setting aside a budget for community events in 2020:&lt;br /&gt;
&lt;br /&gt;
* Supporting community building events is distinct from the development focused code-sprints below&lt;br /&gt;
* We are inviting community members to contact us about events (rather than try and adjust their event to fit into our code sprint guidelines)&lt;br /&gt;
* 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.&lt;br /&gt;
* Previously we have had requests to fund a &amp;quot;community day&amp;quot; or &amp;quot;community sprints&amp;quot; as part a larger event as distinct from sponsorship, the have been funded to the best of our ability&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! Event Request&lt;br /&gt;
! 2019&lt;br /&gt;
! 2019 Actual&lt;br /&gt;
! 2020&lt;br /&gt;
! Notes&lt;br /&gt;
|-&lt;br /&gt;
| QGIS Developer Meeting and User Conference &lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 3,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
|-&lt;br /&gt;
| FOSS4G SotM Oceania Community Day &lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 1500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 1500&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 1500&lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Code Sprints ==&lt;br /&gt;
&lt;br /&gt;
We have asked project teams for guidance to help set our code sprint budget:&lt;br /&gt;
&lt;br /&gt;
* Please note our [[Code Sprint Guidelines]] ask for event details, budget and fundraising on your part.&lt;br /&gt;
* Out priority is to share the risk with organizers allowing access to funds early to book facilities as required&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot;   border=&amp;quot;2&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;6&amp;quot; rules=&amp;quot;all&amp;quot; style=&amp;quot;margin:1em 1em 1em 0; border:solid 1px #AAAAAAAA; border-collapse:collapse; font-size:95%; empty-cells:show;&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! Sprint Request&lt;br /&gt;
! 2019&lt;br /&gt;
! 2019 Actual&lt;br /&gt;
! 2020&lt;br /&gt;
! Notes&lt;br /&gt;
|-&lt;br /&gt;
| OSGeo Code Sprint&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | &lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| No financial request made yet, [[OSGeo Code Sprint 2020|event planning]] is well under way.&lt;br /&gt;
|-&lt;br /&gt;
| GeoServer Code Sprint&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 2,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| PostGIS Code Sprint &lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | -&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| GRASS GIS Community Sprint &lt;br /&gt;
|  style=&amp;quot;text-align:right;&amp;quot; | -&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|-&lt;br /&gt;
| Small Code Sprints&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 10,000&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| style=&amp;quot;text-align:right;&amp;quot; | 0&lt;br /&gt;
| &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Approval and Amendments =&lt;br /&gt;
&lt;br /&gt;
* Budget Meeting:  [[Board Meeting 2019-01-21]]&lt;br /&gt;
* Loomio Motion: [https://www.loomio.org/d/xmEyfoPn/osgeo-budget-2019]&lt;br /&gt;
* Amendments: TBD&lt;br /&gt;
&lt;br /&gt;
[[Category:Budget]]&lt;br /&gt;
[[Category:Finance]]&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Q%26A_Stage_2_Buenos_Aires&amp;diff=122448</id>
		<title>Q&amp;A Stage 2 Buenos Aires</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Q%26A_Stage_2_Buenos_Aires&amp;diff=122448"/>
		<updated>2019-11-25T15:36:10Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Questions to the BALOC from CC&lt;br /&gt;
&lt;br /&gt;
* name of the questioner&lt;br /&gt;
** question 1&lt;br /&gt;
** question 2&lt;br /&gt;
&lt;br /&gt;
-----&lt;br /&gt;
* '''Steven Feldman'''&lt;br /&gt;
&lt;br /&gt;
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)&lt;br /&gt;
&lt;br /&gt;
** 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?&lt;br /&gt;
** Are you also seeking any further guarantees or underwriting from OSGeo?&lt;br /&gt;
** 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?&lt;br /&gt;
** 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?&lt;br /&gt;
** 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 &amp;quot;in need&amp;quot; discount.&lt;br /&gt;
** I did not see any explicit mention of video recording or streaming. What are your plans and are they fully costed in your budget? &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Jonathan Moules&lt;br /&gt;
** '''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:'''&lt;br /&gt;
&lt;br /&gt;
''The BALOC is committed to set up a Sustainability and Social Responsibility Plan for our conference based on the resources available in our country. &lt;br /&gt;
On the following questions we will answer part of our currently planned strategy towards this.''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* '''Will you be sourcing your &amp;quot;conference swag&amp;quot; sustainably (i.e., not from sources that exploit Indiginous People?)'''&lt;br /&gt;
&lt;br /&gt;
''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. &lt;br /&gt;
About explotation, see next question.''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* '''Will you be sourcing your Tea/Coffee/Chocolate sustainably (i.e., not from sources that exploit Indiginous People &amp;amp; children?)'''&lt;br /&gt;
&lt;br /&gt;
''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.'' &lt;br /&gt;
&lt;br /&gt;
* '''Will your caterers source food locally by preference?'''&lt;br /&gt;
&lt;br /&gt;
''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.''&lt;br /&gt;
&lt;br /&gt;
* '''Does your travel grant prioritise sustainable travel over flying?'''&lt;br /&gt;
&lt;br /&gt;
''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.''&lt;br /&gt;
&lt;br /&gt;
* '''Will you be providing bottled water or some re-usable cups (FOSS4G UK did this for 2019 - worked well)?'''&lt;br /&gt;
&lt;br /&gt;
''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.&lt;br /&gt;
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.'' &lt;br /&gt;
&lt;br /&gt;
* '''Will the food lean away from carbon-intensive foodstuffs?'''&lt;br /&gt;
&lt;br /&gt;
''We will balance the diet (unless special needs are required) with fresh non-processed food.&lt;br /&gt;
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.''&lt;br /&gt;
&lt;br /&gt;
* '''How do you anticipate regional participants to travel there? (I'm guessing Local = public transit and International = flying)'''.&lt;br /&gt;
&lt;br /&gt;
''Extending the question regarding sustainability of the TGP transport:&lt;br /&gt;
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. &lt;br /&gt;
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.  ''&lt;br /&gt;
&lt;br /&gt;
* '''Will you default to opt-out for the t-shirt?'''&lt;br /&gt;
&lt;br /&gt;
''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.'' &lt;br /&gt;
&lt;br /&gt;
* '''Will you provide any sort of carbon-credit offset as part of the conference fee for those who choose to fly?'''&lt;br /&gt;
&lt;br /&gt;
''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. &lt;br /&gt;
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.'' &lt;br /&gt;
&lt;br /&gt;
* '''Will you cater to various dietary requirements?'''&lt;br /&gt;
&lt;br /&gt;
''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.&lt;br /&gt;
The menu will be healthy and varied, covering nutritional needs.''&lt;br /&gt;
&lt;br /&gt;
* '''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 )'''&lt;br /&gt;
&lt;br /&gt;
''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.&lt;br /&gt;
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). &lt;br /&gt;
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.''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* '''GeoChicas - I'm not sure what a &amp;quot;geochica&amp;quot; is, but what's the logic to arbitrarily splitting it by gender? This seems the exact opposite of the stated &amp;quot;inclusive&amp;quot;.'''&lt;br /&gt;
&lt;br /&gt;
''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.  &lt;br /&gt;
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.''&lt;br /&gt;
&lt;br /&gt;
'''* You state in regards to local sourcing: &amp;quot;Buenos Aires province is one of the largest meat and dairy producers in the country.&amp;quot; suggesting you plan to provision a fair amount of this. But then in response to carbon-intensive foodstuffs you say: ```&amp;quot;We will balance the diet (unless special needs are required) with fresh non-processed food.&amp;quot; ``` 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 &amp;quot;Food emissions&amp;quot; will find plenty of articles with suggestions for what's good/bad.)'''&lt;br /&gt;
&lt;br /&gt;
''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.''&lt;br /&gt;
&lt;br /&gt;
'''* 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?'''&lt;br /&gt;
&lt;br /&gt;
''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.''&lt;br /&gt;
&lt;br /&gt;
'''* Geochicas - you call this a &amp;quot;safe space&amp;quot;. 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?'''&lt;br /&gt;
&lt;br /&gt;
''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.''&lt;br /&gt;
&lt;br /&gt;
''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.''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Conference Committee]]&lt;br /&gt;
[[Category:FOSS4G]]&lt;br /&gt;
[[Category:FOSS4G2021]]&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Q%26A_Stage_2_Buenos_Aires&amp;diff=122447</id>
		<title>Q&amp;A Stage 2 Buenos Aires</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Q%26A_Stage_2_Buenos_Aires&amp;diff=122447"/>
		<updated>2019-11-25T14:41:06Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: Questions from Steven Feldman&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Questions to the BALOC from CC&lt;br /&gt;
&lt;br /&gt;
* name of the questioner&lt;br /&gt;
** question 1&lt;br /&gt;
** question 2&lt;br /&gt;
&lt;br /&gt;
-----&lt;br /&gt;
* '''Steven Feldman'''&lt;br /&gt;
&lt;br /&gt;
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)&lt;br /&gt;
&lt;br /&gt;
** 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?&lt;br /&gt;
** Are you also seeking any further guarantees or underwriting from OSGeo?&lt;br /&gt;
** 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?&lt;br /&gt;
** 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?&lt;br /&gt;
** 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 &amp;quot;in need&amp;quot; discount.&lt;br /&gt;
** I did not see any explicit mention of video recording or streaming. What are your plans and are they fully costed in your budget? &lt;br /&gt;
&lt;br /&gt;
* Jonathan Moules&lt;br /&gt;
** '''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:'''&lt;br /&gt;
&lt;br /&gt;
''The BALOC is committed to set up a Sustainability and Social Responsibility Plan for our conference based on the resources available in our country. &lt;br /&gt;
On the following questions we will answer part of our currently planned strategy towards this.''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* '''Will you be sourcing your &amp;quot;conference swag&amp;quot; sustainably (i.e., not from sources that exploit Indiginous People?)'''&lt;br /&gt;
&lt;br /&gt;
''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. &lt;br /&gt;
About explotation, see next question.''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* '''Will you be sourcing your Tea/Coffee/Chocolate sustainably (i.e., not from sources that exploit Indiginous People &amp;amp; children?)'''&lt;br /&gt;
&lt;br /&gt;
''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.'' &lt;br /&gt;
&lt;br /&gt;
* '''Will your caterers source food locally by preference?'''&lt;br /&gt;
&lt;br /&gt;
''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.''&lt;br /&gt;
&lt;br /&gt;
* '''Does your travel grant prioritise sustainable travel over flying?'''&lt;br /&gt;
&lt;br /&gt;
''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.''&lt;br /&gt;
&lt;br /&gt;
* '''Will you be providing bottled water or some re-usable cups (FOSS4G UK did this for 2019 - worked well)?'''&lt;br /&gt;
&lt;br /&gt;
''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.&lt;br /&gt;
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.'' &lt;br /&gt;
&lt;br /&gt;
* '''Will the food lean away from carbon-intensive foodstuffs?'''&lt;br /&gt;
&lt;br /&gt;
''We will balance the diet (unless special needs are required) with fresh non-processed food.&lt;br /&gt;
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.''&lt;br /&gt;
&lt;br /&gt;
* '''How do you anticipate regional participants to travel there? (I'm guessing Local = public transit and International = flying)'''.&lt;br /&gt;
&lt;br /&gt;
''Extending the question regarding sustainability of the TGP transport:&lt;br /&gt;
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. &lt;br /&gt;
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.  ''&lt;br /&gt;
&lt;br /&gt;
* '''Will you default to opt-out for the t-shirt?'''&lt;br /&gt;
&lt;br /&gt;
''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.'' &lt;br /&gt;
&lt;br /&gt;
* '''Will you provide any sort of carbon-credit offset as part of the conference fee for those who choose to fly?'''&lt;br /&gt;
&lt;br /&gt;
''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. &lt;br /&gt;
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.'' &lt;br /&gt;
&lt;br /&gt;
* '''Will you cater to various dietary requirements?'''&lt;br /&gt;
&lt;br /&gt;
''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.&lt;br /&gt;
The menu will be healthy and varied, covering nutritional needs.''&lt;br /&gt;
&lt;br /&gt;
* '''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 )'''&lt;br /&gt;
&lt;br /&gt;
''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.&lt;br /&gt;
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). &lt;br /&gt;
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.''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* '''GeoChicas - I'm not sure what a &amp;quot;geochica&amp;quot; is, but what's the logic to arbitrarily splitting it by gender? This seems the exact opposite of the stated &amp;quot;inclusive&amp;quot;.'''&lt;br /&gt;
&lt;br /&gt;
''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.  &lt;br /&gt;
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.''&lt;br /&gt;
&lt;br /&gt;
'''* You state in regards to local sourcing: &amp;quot;Buenos Aires province is one of the largest meat and dairy producers in the country.&amp;quot; suggesting you plan to provision a fair amount of this. But then in response to carbon-intensive foodstuffs you say: ```&amp;quot;We will balance the diet (unless special needs are required) with fresh non-processed food.&amp;quot; ``` 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 &amp;quot;Food emissions&amp;quot; will find plenty of articles with suggestions for what's good/bad.)'''&lt;br /&gt;
&lt;br /&gt;
''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.''&lt;br /&gt;
&lt;br /&gt;
'''* 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?'''&lt;br /&gt;
&lt;br /&gt;
''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.''&lt;br /&gt;
&lt;br /&gt;
'''* Geochicas - you call this a &amp;quot;safe space&amp;quot;. 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?'''&lt;br /&gt;
&lt;br /&gt;
''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.''&lt;br /&gt;
&lt;br /&gt;
''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.''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Conference Committee]]&lt;br /&gt;
[[Category:FOSS4G]]&lt;br /&gt;
[[Category:FOSS4G2021]]&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Q%26A_Stage_1_Buenos_Aires&amp;diff=121899</id>
		<title>Q&amp;A Stage 1 Buenos Aires</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Q%26A_Stage_1_Buenos_Aires&amp;diff=121899"/>
		<updated>2019-09-29T10:05:34Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Questions to LoI of the Buenos Aires Team:&lt;br /&gt;
&lt;br /&gt;
Point of info on dates from [[User:Stevenfeldman | Steven Feldman]] The Jewish High Holy Days run till 29 September 2021, this overlap may be unavoidable&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
	<entry>
		<id>https://wiki.osgeo.org/w/index.php?title=Q%26A_Stage_1_Buenos_Aires&amp;diff=121898</id>
		<title>Q&amp;A Stage 1 Buenos Aires</title>
		<link rel="alternate" type="text/html" href="https://wiki.osgeo.org/w/index.php?title=Q%26A_Stage_1_Buenos_Aires&amp;diff=121898"/>
		<updated>2019-09-29T10:04:09Z</updated>

		<summary type="html">&lt;p&gt;Stevenfeldman: Dates&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Questions to LoI of the Buenos Aires Team:&lt;br /&gt;
&lt;br /&gt;
Point of info on dates from [User:Stevenfeldman] The Jewish High Holy Days run till 29 September 2021, this overlap may be unavoidable&lt;/div&gt;</summary>
		<author><name>Stevenfeldman</name></author>
	</entry>
</feed>