Conference Options 2014 - Revision history

Wiki-Bruce.bannerman: /* Votes/Comments */

2014-10-06T01:08:59Z

Votes/Comments

2014-10-06T01:07:43Z

Votes/Comments

2014-10-06T01:03:28Z

Votes/Comments

2014-10-06T00:59:25Z

Votes/Comments

2014-10-06T00:52:39Z

Votes/Comments

2014-10-04T11:38:29Z

fix wiki syntax; +category

2014-10-03T00:19:56Z

Votes/Comments

2014-10-03T00:17:25Z

Votes/Comments

2014-10-03T00:10:18Z

Votes/Comments

2014-10-03T00:07:57Z

Votes/Comments

@@ Line 80: / Line 80: @@
 * -1 Jive: If we want foss4g then this model does not scale, if we were more flexible we could end up with a different flavour each annual conference
 * -0 DanielKastl: Pretty much every year some local community has to reinvent the wheel, setup a new infrastructure for website, payment, etc.. IMO it's currently done not very efficient.
-* +1 BruceBannerman: Having served on the POC for FOSS4G 2009, this work is not overly onerous. Local knowledge in the Professional Organiser definitely helps. There is certainly room to improve how events are done: OSGeo could for example insist that the LOC contain members of past successful events; OSGeo could insist on common software, web infrastructure etc.
+* +1 BruceBannerman: Having served on the LOC for FOSS4G 2009, this work is not overly onerous. Local knowledge in the Professional Organiser definitely helps. There is certainly room to improve how events are done: OSGeo could for example insist that the LOC contain members of past successful events; OSGeo could insist on common software, web infrastructure etc.
 ==Engage a long term (for profit) PCO==

@@ Line 142: / Line 142: @@
 * +0 Jive: This is outreach - recommend joint events with a range of open source groups - expect LocationTech is an easy way to get started.
 * -0 DanielKastl: It sounds too nice to have a "win-win" collaboration, but I fear there is also some conflict of interest. It might be good to give this a try on a local conference (such as FOSS4G NA) first.
 = References =

@@ Line 120: / Line 120: @@
 * +0 Jive: Would hate to see us responsible for an employee, easier to exit out of a relationship with PCO. Still an employee could line up PCO in region hosting foss4g (as we advise LOC committee to do) while handling community / publicity angle.
 * +1 DanielKastl: I wouldn't call it "hire a staff", but pay people to spend a certain amount of time to lead organizing the conference. This doesn't need to be a single person (but could be shared within a small team of 2 or 3 people). The idea is, that there is a knowledge transfer from one year to the next, and that work gets done, that volunteers may not find so motivating (ie. overlook the conference management, acquiring sponsors, boring paper work, report to OSGeo,...). German FOSSGIS is doing this way for their local conference, and I think it works pretty well.
 == Partner with LocationTech==

@@ Line 97: / Line 97: @@
 * -0 Jive: Risk is a subject for contract negotiation
 * +0 DanielKastl: It's better than looking for a new PCO every year, so if there is a good candidate this might not require much work for OSGeo. I just doubt that it's easy to find a suitable PCO.
 == Hire a staff person to be the organiser ==

@@ Line 80: / Line 80: @@
 * -1 Jive: If we want foss4g then this model does not scale, if we were more flexible we could end up with a different flavour each annual conference
 * -0 DanielKastl: Pretty much every year some local community has to reinvent the wheel, setup a new infrastructure for website, payment, etc.. IMO it's currently done not very efficient.
 ==Engage a long term (for profit) PCO==

@@ Line 141: / Line 141: @@
 = References =
-* http://wiki.osgeo.org/wiki/FOSS4G
+* [[FOSS4G]]
-* http://wiki.osgeo.org/wiki/FOSS4G_Handbook
+* [[FOSS4G Handbook]]
-* http://wiki.osgeo.org/wiki/Official_OSGeo_Event_Policy
+* [[Official OSGeo Event Policy]]