User Tools

Site Tools


eg09:conference_nominations

Site Nomination Process for the Evergreen International Conference

Established by members of the 2010 Site Nomination Committee, updated by the 2012 committee, 2014 and 2016 committees

1. The Conference

The Evergreen International Conference takes place annually, usually during the month of April. Expected attendance is between 200 and 250 attendees, representing Evergreen users, advocates, vendors, and others interested in Evergreen or open source. A varied 3-track program is offered, attempting to cover many aspects of Evergreen and appeal to developers, system administrators, consortium leaders, managers, and front-end staff.

An attempt will be made to hold the conference in different regions of the United States to enable the wide-spread Evergreen community a chance to attend. Nominations from outside of the United States are encouraged but the location should appeal to a wide number of Evergreen users and supporters.

Past Conference Websites: EG 2009 EG 2010 EG 2011 EG 2013 EG 2014 EG 2015 EG 2016

Hosting a conference

Hosting a conference can be fun and very rewarding, but is also a lot of hard work. There are a number of crucial time-sensitive tasks, such as setting the conference dates and securing a venue, sponsorship recruitment, selecting speakers, and reviewing programs, and the final 90 days prior to the conference will be very busy for the site committee. A conference is also a fiscal commitment that involves building and staying within a very tight budget that allows registration costs to stay reasonable while providing an excellent conference experience for attendees, vendors, and other participants.

The call to host a conference usually goes out approximately 18 months in advance. The criteria and information (outlined below) are requested of all nominations and can be submitted in PDF, Open Office, or any other human-readable format, though we prefer open source formats.

2. The Site Committee

The Site Committee is comprised of volunteers from the Evergreen community who will hold one or two year terms. Two spots will be reserved for Evergreen vendors.

The Committee work begins by sending out requests for Conference hosting proposals. The call goes out on the evergreen-ils mailing lists, the primary communication mechanism of the Evergreen community. The Site Committee gathers the proposals and ranks them based on:

  • the criteria set out in this document;
  • the results of investigations to confirm the appeal and cost of potential conference centers;
  • and estimates of travel and accommodation costs.

Site committee members receive and review all submissions individually and then confer to make a final decision. The Committee then awards the conference to the most suitable proposal, usually within 3 weeks of the close date for nominations. Once the host has been determined, the Site Committee works with the local arrangement committee on a smooth hand-off of responsibilities. The local arrangement committee will work closely with the Software Freedom Conservancy on venue contract negotiations and fiscal responsibilities. The local arrangement committee is responsible for providing regular updates to the Evergreen Oversight Board.

3. The Proposal (NB: Please be as imaginative as you like in your proposal, the site selection committee is willing to consider variations on the following requirements as long as reasons for variations are made clear in your proposal)

Contact Information Required from all Potential Host Sites:

  • Name, organization, phone, and email of contact people
  • Name(s) of primary contact(s) for Site Committee. These are the people who will take the lead in organizing the conference.
  • Prior experience with hosting conferences

Requirements to be addressed in all Proposals

These should be outlined in as much detail as possible; including contact information for conference centers and hotels etc. to allow the Site Committee to investigate and confirm information provided. Proposals should include all likely sites.

  • A conference facility with an auditorium or similar space suitable for 200-250 persons
  • Four or more breakout rooms for 50-80, a registration area, and dedicated booth space for between 15 to 20 exhibitors
  • Include confirmed availability of all sites for the dates indicated
  • The facility must have either a catering company or be able to prepare meals onsite
  • Wireless network in the conference facility available to attendees free or sponsored by the conference
  • A host or hosts willing to manage local arrangements
  • A commitment to help keep attendee costs to a minimum (which may require a combination of cost-effective sites, and early, vigorous sponsorship recruitment)
  • Usual cost of a return air trip to your city from the following cities: Atlanta GA, Grand Rapids MI, Columbia SC, Indianapolis IN, Austin TX, Boston MA, Hartford CT, Seattle WA, Toronto ON, Winnipeg MB, Vancouver BC, Dublin Ireland, Amsterdam, Holland, Yerevan, Armenia

Additional Desirable Qualities for Conference Sites

  • Reasonably easy to get to, both cost- and travel-wise
  • Some distance away from the last conference site
  • Attractive, interesting surroundings
  • Restaurants within easy access of the host facility (walking distance, shuttles, etc.)
  • Attractive to potential site sponsors (keeping in mind issues such as shipping costs for exhibitor materials, travel costs, etc.)
  • Prior experience hosting multi-date user conferences
  • Note any other strengths of the local site and site committee

Responsibilities of the Hosting Site

Proposals will include comments on the proposed site's ability to do the following:

  • Preliminary site visits to the proposed site and hotels
  • Managing the program and events planning process
  • Arranging and providing information about evening networking opportunities (e.g., interesting and/or good restaurants and bars and/or events)
  • Participating in the effort to sign on conference sponsors
  • Arrange for 1 local arrangements committee member to attend the conference prior to the one you are hosting to participate in a handover meeting.
  • Arrange for 1 local arrangements committee member to act as a consultant (by phone and email) for the next conference host planning committee.
  • Provide Wi-Fi for up to 250 very active Internet users

Please submit proposals to eg-sites@list.evergreen-ils.org by January 31, 2017 at 5:00 p.m. ET to qualify.

Typical/Example Conference Schedule

Past conferences have stuck to a similar schedule of events:

  • Wednesday (full day) - Developer Hackfest/Pre-conference/Un-conference and committee meetings
  • Thursday (full day) - Conference Day 1: Opening Keynote session, Multi-track presentation sessions.
  • Friday (full day) - Conference Day 2: Multi-track presentation sessions.
  • Saturday (half-day) - Conference Day 3: Multi-track presentation sessions, Closing.
  • Sessions are usually one hour blocks (45 or 50 minutes), but some conferences have done 2 hour blocks for more in-depth topics.
  • One or both of the afternoons may include "Lightning Talk" sessions (5 minute limit - sign up happens just before the session)
  • Some conferences have included catered lunches for at least one day, but most have extended the lunch break to accommodate lunch outings.

Social Activities have included the following:

  • Dine-Arounds - typically the evening of Day 1
  • Pub Crawl - typically the evening of Day 2
  • Coordinated tours of local libraries or other sites of interest
  • Gaming spaces and informal hacking time for developers/admins

Expectations of the Local Arrangements Committee

The local arrangement committee is responsible for managing the program and events planning process. Local planners from the host site will work in conjunction with the conference planning committee, which is made up of community volunteers available to advise the host site and assist with planning details.

The local arrangements committee should have a minimum of three people who are willing to be responsible for leading such subcommittees as programming, sponsorships, venue and entertainment, and registration. The local committee shall appoint one representative to be the lead and that person shall be responsible for proactive and timely communication with both the EOB, SFC, and the Evergreen community.

A representative from the local arrangements committee is expected to provide regular conference updates at the monthly meetings of the Evergreen Oversight Board, currently scheduled for 2 p.m. Eastern on the third Thursday of the month.

The local arrangements committee should strive to stick to the following timeline. This timeline is based on an April conference date and should be adjusted accordingly if the conference is scheduled for a different month.

  • May - First draft of conference budget submitted to the Evergreen Oversight Board. The hosting site should also seek approval from the EOB for any budget changes that increase an expense by at least 10% and decrease income by at least 10%.
  • June - Venue agreement forwarded to the Software Freedom Conservancy for review/final negotiations.
  • August - Sponsorship package submitted to the Software Freedom Conservancy for review.
  • August - If Pre-Conference sessions will be available on Wednesday at an additional cost, the sessions and presenters need to be set prior to registration
  • September - Early Bird Registration available
  • September - Issue Call for Program Proposals
  • September - Web site up for conference (including program proposals, sponsor recognition, and general information about the site/costs/travel)
  • October - First contact with potential Sponsors/Exhibitors
  • October - Keynote speaker selected and notified
  • December - Program Proposal Selection finalized and presenters notified
  • January - Program Schedule Posted
eg09/conference_nominations.txt · Last modified: 2017/01/06 13:20 by terlaga

© 2008-2017 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a member of Software Freedom Conservancy.