[OSGeo-Conf] Poll: Change FOSS4G structure to have some continuity of organization and management

[Jonathan Neufeld]

I’m not sure I qualify as a voting member, but after our experience with 2020 in Calgary I support #2 – Changing the organizing structure.

Cheers,
Jon

From: Conference_dev <conference_dev-bounces at lists.osgeo.org> On Behalf Of María Arias de Reyna
Sent: Thursday, February 3, 2022 9:15 AM
To: Eli Adam <eadam at co.lincoln.or.us>
Cc: OSGeo-Conf <conference_dev at lists.osgeo.org>
Subject: Re: [OSGeo-Conf] Poll: Change FOSS4G structure to have some continuity of organization and management

2, clearly to me

El jue., 3 feb. 2022 15:04, Eli Adam <eadam at co.lincoln.or.us<mailto:eadam at co.lincoln.or.us>> escribió:
Hi all (particularly voting committee members),

The current FOSS4G structure has a new LOC every year starting more or less from scratch (some things like mailing lists and seed money are passed on).  Over the years, many people have commented on the load of work this creates for the LOC, the general inefficiency, the risk, and the burnout.

If you consider yourself a voting member of the committee (https://wiki.osgeo.org/wiki/Conference_Committee#Current_Members), please indicate your preference on this.

This is an informal poll to see if the conference committee wants to:
1. Keep it the way it is and not change anything
2. Change the FOSS4G organizing structure to something else (discussion of what we change it to can come later if people want to pursue this).

As I've expressed several times, I prefer option 2, changing the FOSS4G organizing structure.

Thanks for your time and participation.

Best regards, Eli





_______________________________________________
Conference_dev mailing list
Conference_dev at lists.osgeo.org<mailto:Conference_dev at lists.osgeo.org>
https://lists.osgeo.org/mailman/listinfo/conference_dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/conference_dev/attachments/20220203/f094f6d0/attachment.html>