Difference between revisions of "FOSS4G 2021 Lessons Learned"

From OSGeo
Jump to navigation Jump to search
Line 41: Line 41:
 
=== Code Sprint ===
 
=== Code Sprint ===
  
=== Other side events ===
+
 
  
  

Revision as of 06:36, 27 December 2021

Previous Years Lessons Learned

2019, 2018, 2017, 2017, 2016 , 2015, 2014, 2013, 2011, 2010, 2009, 2008, 2007

FOSS4G 2021 Lessons Learned

This is to document things that the local committee learned, for the benefit of future FOSS4Gs!!

There was a contest to get the logo, both in English and Spanish. This helps people get enthusiastic with the conference from the beginning and allows members of our community to contribute in their best.

It is recommended to have a designer ready to adapt the logo to the rest of the look and feel of the conference. Even if you ask for a theme, colors or topic on the contest, it is doubtful it will completely fit with the rest of the style.

Sponsorship

LOC Organization

Marketing

Discounts

Travel Grants, Discounts and Inclusivity

There was no travel grants per se in 2021, as it was an online conference. But we allowed a wide range of discounts and free tickets to allow people from all over the world to attend. We targeted both people with low income and people from underrepresented groups and identities.

There are several things to consider if you are going to target low income economies in an online event.

Not everyone has access to proper hardware and bandwidth for the conference. You can arrange with local communities crowd gatherings (health and law permitted) so they meet at some school, university, public library, or similar building to use a computer and watch the talks together. Still, that will not be enough in some communities, so it may be recommendable to save part of the budget to be able to send them some hardware or mobile phone card to be able to connect.

The same way, there will be lots of other issues for people that want to attend the conference but they can't even if you offer them free tickets. You can't foresee all of those issues. Contact as many chapters as possible and try to find common ground. There will be things you can fix and things you can't. Be open and save some budget in case you can.

Abstract Submissions

Paper selection

Workshops

Academic Track

Code Sprint