[OSGeo-Conf] Conference commitete meeting?

Dave McIlhagga dmcilhagga at mapsherpa.com
Mon Jan 11 11:48:42 PST 2016

Good points Cameron.

If I can suggest one more critical piece to number 3 … I think we should have a good discussion on whether we should have a consistent PCO year to year (regardless of the LocationTech issue). Every year we restart a lot of things simply because we have a new organization to ramp up every event. A lot of cost and headaches can be saved by having the same PCO to work with. Not to mention knowledge transfer year-to-year.

I think making this decision is the first and most important decision to make. Once that’s taken care of — then we can look at whether Location Tech might make sense as this PCO, or another 3rd party organization.


> On Jan 11, 2016, at 2:36 PM, Cameron Shorter <cameron.shorter at gmail.com> wrote:
> I'd attend a meeting. Also agree that starting conversation on email would be a good way to warm up.
> A way to focus the meeting might be to step through the current FOSS4G Handbook, collectively approving sections and removing the "Draft - awaiting review" comments.
> https://wiki.osgeo.org/wiki/FOSS4G_Handbook <https://wiki.osgeo.org/wiki/FOSS4G_Handbook>
> The big items which I think need addressing are:
> 1. What are the principles we should consider when selecting a FOSS4G conference? Lets write them down. Many of these principles would be derived from OSGeo principles. Others will be more logistical. Both the Handbook and RFP has some of this information. 
> https://svn.osgeo.org/osgeo/foss4g/rfp/2017/osgeo-conference-2017-request-for-proposal.pdf <https://svn.osgeo.org/osgeo/foss4g/rfp/2017/osgeo-conference-2017-request-for-proposal.pdf>
> 2. How do we transfer knowledge from one conference to the next. The cookbook FOSS4G Handbook is one method. There have been a number of suggestions to consistently use one Professional Conference Organisor, be that a paid person, or a company. Do we want to pursue this?
> 3. This leads to the sensitive question of "Do we want to consider Location Tech as that PCO?" Location Tech has teamed with unsuccessful FOSS4G bids in the past. I see this as evidence that our community is split on the answer to this question. This is a messy question to consider and make a decision on, but by not addressing it, we are wasting a lot of community energy and goodwill. As such, I see it as our most pressing question.
> On 11/01/2016 4:32 pm, Eli Adam wrote:
>> Hi all,
>> Are people interested in a conference committee meeting?  (or perhaps e-meeting conducted on email over the period of a few days).
>> We have a few loose ends that we could address.  If people are interested in a meeting, I'll start a wiki page.  I think that we should discuss and vote on a few motions.  Formalizing a few decisions, adjusting committee membership, discuss RFP revisions, discuss 2018 RFP schedule (according to this motion we should start soon,  <http://lists.osgeo.org/pipermail/conference_dev/2014-December/002794.html>http://lists.osgeo.org/pipermail/conference_dev/2014-December/002794.html <http://lists.osgeo.org/pipermail/conference_dev/2014-December/002794.html>).
>> Are committee members interested in a meeting?  Format or time preference?  Items for a meeting?
>> Be well, Eli
>> _______________________________________________
>> Conference_dev mailing list
>> Conference_dev at lists.osgeo.org <mailto:Conference_dev at lists.osgeo.org>
>> http://lists.osgeo.org/mailman/listinfo/conference_dev <http://lists.osgeo.org/mailman/listinfo/conference_dev>
> -- 
> Cameron Shorter,
> Software and Data Solutions Manager
> LISAsoft
> Suite 112, Jones Bay Wharf,
> 26 - 32 Pirrama Rd, Pyrmont NSW 2009
> P +61 2 9009 5000,  W www.lisasoft.com <http://www.lisasoft.com/>,  F +61 2 9009 5099
> _______________________________________________
> Conference_dev mailing list
> Conference_dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/conference_dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/conference_dev/attachments/20160111/0bc61345/attachment.html>

More information about the Conference_dev mailing list