Difference between revisions of "Conference Options 2014"
Wiki-Geejee (talk | contribs) |
Wiki-Geejee (talk | contribs) |
||
| Line 30: | Line 30: | ||
==Engage an independent long term PCO== | ==Engage an independent long term PCO== | ||
| − | |||
| − | |||
| − | |||
| − | |||
===Advantages=== | ===Advantages=== | ||
| Line 39: | Line 35: | ||
* Institutional knowledge. The conference knowledge carries on in the organisation, and is hopefully not entirely imbued in one person. | * Institutional knowledge. The conference knowledge carries on in the organisation, and is hopefully not entirely imbued in one person. | ||
* Simplicity. | * Simplicity. | ||
| + | |||
| + | |||
| + | ===Disadvantages=== | ||
| + | |||
| + | * How would a OSGeo exit out of the arrangement with the PCO if the relationship sours? | ||
===Votes/Comments=== | ===Votes/Comments=== | ||
Revision as of 12:33, 19 September 2014
Future organisation of FOSS4G has been discussed at FOSS4G 2014 then followed onto OSGeo emails lists (Conference, Discuss and Board lists).
This wiki page aims to collate background information, options, options, and recommendations in order to facilitate making decisions about guiding the future management of FOSS4G events.
Editing this wiki
All with an opinion are encouraged to add it to this wiki. Options should be prefaced with your name:
[First Last] Comment ...
Background
The international FOSS4G conference has grown from 100-200 attendees when it started 10+ years ago, to ~ 800 attendees now in 2014. Some regional events are also attracting large numbers. Extra attendance leads to extra effort required to coordinate, leading the OSGeo Community to consider options on how to move forward.
Options
Following are options which have been identified.
Same as before
For a number of years, the large FOSS4G events have hired a new Professional Conference Organiser (PCO). This PCO is usually local and knows the city where the event is being held.
Advantages
- Minimal effort (for the board) to set up.
- A local PCO likely has local experience.
Disadvantages
- Loss of knowledge between events and associated risk of failure.
- Significant stress put on LOCs.
Votes/Comments
- -0 CameronShorter
- -1 Darrell: This model simply doesn't scale. The idea that local knowledge is required for the PCO position is, quite simply, false. (I find it amazing that we can operate a global organization on a small budget, but are unable to conceive that others are also able to.)
Engage an independent long term PCO
Advantages
- Institutional knowledge. The conference knowledge carries on in the organisation, and is hopefully not entirely imbued in one person.
- Simplicity.
Disadvantages
- How would a OSGeo exit out of the arrangement with the PCO if the relationship sours?
Votes/Comments
- 0 CameronShorter. I'm nervous about an exit strategy if things go sour. It is in the vested interests of a PCO not to share information with community, such that we become reliant upon the PCO.
- +1 Darrell. It's simple, the contract is renewable on an annual basis. If either party isn't happy with the arrangement, it can be ended. Put into the contract what knowledge is to be shared and how.
Hire a staff person to be the organiser
This is more risk, but also offers more potential.
Advantages:
- Having a staff person allows OSGeo to be more flexible in organising conferences. Is there a budding regional conference that needs some assistance? We can help with that. Would OSGeo like to foster growth in regions without a local FOSS4G event? OSGeo can do that.
Disadvantages
- You would only have one staff person, which means more risk of losing institutional knowledge if that person leaves.
- Potential for being seen as less of a a volunteer led organisation.
- Hiring is hard, and takes time, especially to find a good autonomous person to take on this role
Votes/Comments
- +0 CameronShorter
- +0 Darrell: I think this is a good idea, if and only if OSGeo has a clear vision of how they want the organization and the role to grow. Right now, I don't see that they do.
- Comments by Jeff McKenna: I proposed this option formally to the OSGeo Board in 2011. A full job description and rates are outlined on the wiki page: FOSS4G Advisor Role
Partner with LocationTech
Advantages
- LocationTech works in the same space, has contacts, and the Eclipse Foundation already runs conferences
- Retention of knowledge between regions
- Potential for future, deepened partnerships
Disadvantages
- LocationTech works in the same space, has contacts, and the Eclipse Foundation already runs conferences, so there’s a potential for conflicts of interest
- If it doesn’t work out for whatever reason, future partnership opportunities might be lost
- Potential OSGeo Brand dilution due to obvious prominence of LocationTech taking responsibility. Eg, publicity emails would come from a LocationTech email address.
- Reduction in OSGeo income.
Votes/Comments
- -0 CameronShorter. I think the OSGeo/LocationTech relationship discussions have further to go first. Also concerned about loss of OSGeo income and branding.