For conferences, it's extremely important that attendees get top-quality content from industry experts. As a highly compelling format of educating others based on experience and research, conferences stand to be one the best sources of refined knowledge available. Still, it's important for a successful event to have a few guidelines to ensure quality content from the best and most appropriate speakers. Below is a set of guidelines for conference organizers that ensure quality content for attendees and the community.
-
Schedule: Conferences will let speakers know the time and duration of their talk at least two weeks before the event.
-
A/V & Power: Conferences will provide a quality projector with at least 1024x768 resolution, projected onto a screen that is appropriately sized and readily viewable by all attendees in the room. Conferences will also provide power outlets at the podium.
-
Water: Conferences will ensure speakers have water available either at the podium or somewhere easily accessible before the session begins.
- We will deliver a quality talk
- We will ensure that our talk does not go over the allotted time
- We will ensure that our slides are legible and well-designed
- We will consent to the distribution of video and audio recordings under a permissive Creative Commons license (such as CC-BY, CC-BY-NC, or CC-BY-SA; the exact license is at the discretion of the speaker)
- We will commit to spending time with attendees during the event
- We will commit to publicizing the fact that we'll be speaking at your event
- We will deliver talks that are current, correct, and of genuine interest to attendees; we promise not to make our talks a sales pitch
- We will refrain from language, images, or behavior during the conference that may reflect poorly on the conference, and will adhere to a conference's code of conduct if one is established.
- We will post our content and demos on the web within 48 hours after the conference
This is a forked, revised document from the original (https://gist.github.com/3098860) written by @rmurphey @nimbupani and @paulirish in June 2012. It is a living document and open for edits from the community.