Differences between revisions 9 and 19 (spanning 10 versions)
Revision 9 as of 2006-09-12 13:05:29
Size: 3775
Comment: Move item into right section
Revision 19 as of 2009-05-18 20:53:49
Size: 5805
Editor: PaulBoddie
Comment: Fixed numbered list (which could use 1. for all items and be automatically numbered).
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Rough notes on how to run PyCon-style conventions. Rough checklist for running PyCon-style conventions.
Line 3: Line 3:
This table intends to list every single step required to plan and carry out a conference. *Do not remove items* from this list, because this isn't the to-do list for any particular year; the list of remaining tasks for a specific conference such as PyCon 2006 would be on other pages. Do feel free to *add* any tasks that you think of. This table intends to list every single step required to plan and carry out a conference. ''Do not remove items'' from this list, because this isn't the to-do list for any particular year; the list of remaining tasks for a specific conference such as PyCon 2006 would be on other pages. Do feel free to ''add'' any tasks that you think of.

The dates are given in terms of time before the conference. Larger conferences need lots of preparation time, and a smaller event can probably compress the timeline significantly.
Line 7: Line 9:
||- 18-24 months || Select conference city and venue ||
|| XXX || Select dates. Important: Check they don't conflict with holidays. ||
|| XXX || Book venue ||
|| XXX || Finances: determine costs ||
|| XXX
|| Finances: contact potential sponsors ||
|| XXX || Finances: Set registration price ||
|| XXX || Set up registration process and open registration ||
||-18-24 months || Select conference city and venue ||
||-18-24 months || Select dates. Important: Check they don't conflict with holidays. ||
||-12-18 months || Book venue ||
||-12-18 months || Finances: estimate costs and draw up a draft budget ||
|| -12-6 months
|| Finances: contact potential sponsors ||
|| XXX || Decide upon keynote speaker(s) ||
|| XXX || Call for proposals ||
|| XXX || E-mail speakers for invited talks ||
|| XXX || Review proposals ||
|| -6 months ||
Finances: Set registration price ||
|| XXX || Send proposal acceptances ||
|| XXX || Create sched
ule ||
|| XXX || Call for financial aid applications ||
|| XXX || Set u
p registration process and open early-bird registration ||
Line 15: Line 24:
|| XXX || Decide upon keynote speaker(s) ||
|| XXX || Determine giveaways (sponsors may help?) ||
|| XXX || Finalize design of T-shirt or other momento ||
|| XXX || Arrange manufacturing of T-shirt ||
|| XXX || Review/accept/reject financial aid applications ||
|| XXX || Arrange for wireless networking ||
Line 20: Line 27:
|| XXX || Arrange for wireless networking || || XXX || End early-bird registration ||
Line 24: Line 31:
|| XXX || Select program committee || || -9 months || Select program committee ||
Line 26: Line 33:
|| XXX || Post call for papers ||
|| XXX || Paper submission deadline ||
|| -9 months || Post call for papers ||
|| -2 months || Paper submission deadline ||
Line 33: Line 40:
|| XXX || Pick session leaders || || XXX || Pick session chairs ||
Line 37: Line 44:
|| XXX || Issue call for BoFs ||
|| XXX || Pick BoF topics ||
|| -2 months || Issue call for BoFs ||
|| -2 weeks || Pick BoF topics ||

=== Swag ===

|| XXX || Determine other giveaways (sponsors may help?) ||
|| -90 days || Selecting the swag vendor ||
|| -80 days || Creating tshirt order based on size proportions of attendees prior year ||
|| -80 days || Calling for volunteer to accept delivery of tshirts and totes in advance of conference ||
|| -55 days || Bug graphic designer about images ||
|| -50 days || Get T-shirt images from graphic designer ||
|| Close of early registration || Chair commits to attendance figure. ||
|| -45 days || Get quote from swag vendor (T-shirts, tote bag) ||
|| -45 days || Get chair's approval for T-shirt, tote budget ||
|| -45 days || Have non-attending volunteers sign up on wiki to get shirts ||
|| -45 days || Get tote bag images from graphic designer ||
|| -44 days || Ordering tshirts, totes from swag vendor ||
|| -44 days || Emailing attendee tshirt images to vendor ||
|| -44 days || Emailing staff tshirt images to vendor ||
|| -44 days || Emailing tote images to vendor ||
|| -44 days || Submit reimbursement request to PSF treasurer ||
|| -37 days || Proofread T-shirts, totes at vendor ||
|| -30 days || Vendor ships to local volunteer ||
|| -30 days || Optionally make a second order if registration numbers suggest it. ||
|| -1 day || Stuff the bags ||
|| -1 day || Fold T-shirts ||
|| -1 day || Hand out some staff T-shirts ||
Line 59: Line 91:
  1. Formatting finalized program.
  2. Contracting for printing of individual programs for the delegates' totes, and the presentation boards to go outside each of the session rooms.
 1. Formatting finalized program.

2. Contracting for printing of individual programs for the delegates' totes, and the presentation boards to go outside each of the session rooms.
Line 62: Line 95:
  3. Purchasing and printing delegates' name labels.  3. Purchasing and printing delegates' name labels.
Line 64: Line 97:
  4. Preparation and printing of "Chairpersons' Notes", distributing to session chairmen/women.  4. Preparation and printing of "Session Chair Notes", for distribution to session chairs.
Line 66: Line 99:
  5. Preparation and printing of "Speakers' Notes", distributing to speakers.  5. Preparation and printing of "Speakers' Notes", for distribution to speakers.
Line 68: Line 101:
  6. Delivery of tote bag inserts and stuffing of inserts into totes (normally handled by on-site volunteers).  6. Delivery of tote bag inserts and stuffing of inserts into totes (normally handled by on-site volunteers).
Line 70: Line 103:
  7. Organization of registration process and briefing of day one volunteers.  7. Organization of registration process and briefing of day one volunteers.
Line 72: Line 105:
  8. Supervision of everything to make sure there won't be any unforeseen glitches. [This doesn't eliminate unforeseen glitches, it just minimizes them].  8. Supervision of everything to make sure there won't be any unforeseen glitches. [This doesn't eliminate unforeseen glitches, it just minimizes them].
Line 74: Line 107:
  9. [added after IRC communications]: encourage sprint leaders to prepare feedback and prepare to present it at the feedback session.  9. [added after IRC communications]: encourage sprint leaders to prepare feedback and prepare to present it at the feedback session.
Line 88: Line 121:

 * Prepare recorded audio.
Line 91: Line 126:
 * Determine profit/loss.
Line 92: Line 129:

== Programming conferences ==

 * [[http://live.gnome.org/GuadecPlanningHowTo|GUADEC Planning HowTo]]
Line 95: Line 136:
 * [http://caption.org/1998/prog-howto.html Running cons the CAPTION way]
 * [http://www.smof.com/conrunner/index2.htm Conrunner] -- a 1995/6 'zine
 * [http://www.smof.com/smofiles.htm Secret Masters of Fandom]
 * [[http://caption.org/1998/prog-howto.html|Running cons the CAPTION way]]
 * [[http://www.smof.com/conrunner/index2.htm|Conrunner]] -- a 1995/6 'zine
 * [[http://www.smof.com/smofiles.htm|Secret Masters of Fandom]]

Rough checklist for running PyCon-style conventions.

This table intends to list every single step required to plan and carry out a conference. Do not remove items from this list, because this isn't the to-do list for any particular year; the list of remaining tasks for a specific conference such as PyCon 2006 would be on other pages. Do feel free to add any tasks that you think of.

The dates are given in terms of time before the conference. Larger conferences need lots of preparation time, and a smaller event can probably compress the timeline significantly.

Timeline

-18-24 months

Select conference city and venue

-18-24 months

Select dates. Important: Check they don't conflict with holidays.

-12-18 months

Book venue

-12-18 months

Finances: estimate costs and draw up a draft budget

-12-6 months

Finances: contact potential sponsors

XXX

Decide upon keynote speaker(s)

XXX

Call for proposals

XXX

E-mail speakers for invited talks

XXX

Review proposals

-6 months

Finances: Set registration price

XXX

Send proposal acceptances

XXX

Create schedule

XXX

Call for financial aid applications

XXX

Set up registration process and open early-bird registration

XXX

Post call for volunteers

XXX

Review/accept/reject financial aid applications

XXX

Arrange for wireless networking

XXX

Plan refreshments

XXX

End early-bird registration

Refereed papers

-9 months

Select program committee

XXX

Set up conference management software

-9 months

Post call for papers

-2 months

Paper submission deadline

XXX

Deadline for paper accept/decline decisions

XXX

Write page giving presentation advice

XXX

Notify paper authors of acceptance

XXX

Determine conference schedule

XXX

Arrange iCal/RSS publication of schedule

XXX

Pick session chairs

BoFs

-2 months

Issue call for BoFs

-2 weeks

Pick BoF topics

Swag

XXX

Determine other giveaways (sponsors may help?)

-90 days

Selecting the swag vendor

-80 days

Creating tshirt order based on size proportions of attendees prior year

-80 days

Calling for volunteer to accept delivery of tshirts and totes in advance of conference

-55 days

Bug graphic designer about images

-50 days

Get T-shirt images from graphic designer

Close of early registration

Chair commits to attendance figure.

-45 days

Get quote from swag vendor (T-shirts, tote bag)

-45 days

Get chair's approval for T-shirt, tote budget

-45 days

Have non-attending volunteers sign up on wiki to get shirts

-45 days

Get tote bag images from graphic designer

-44 days

Ordering tshirts, totes from swag vendor

-44 days

Emailing attendee tshirt images to vendor

-44 days

Emailing staff tshirt images to vendor

-44 days

Emailing tote images to vendor

-44 days

Submit reimbursement request to PSF treasurer

-37 days

Proofread T-shirts, totes at vendor

-30 days

Vendor ships to local volunteer

-30 days

Optionally make a second order if registration numbers suggest it.

-1 day

Stuff the bags

-1 day

Fold T-shirts

-1 day

Hand out some staff T-shirts

Demos

XXX

Post call for demos for demo room

PSF Meeting

-3 months

Request nominees for new PSF members

-3 months

Request nominees for board of directors

-2 months

Send out agendas and proxy forms

Next year's con

-4 months

Write requirements for con sites (like http://www.yapc.org/venue-reqs.txt)

-4 months

Post call for site proposals

-1 month

Check over site proposals

At con

Run a panel / voting session to choose a proposal

Days before conference

  1. Formatting finalized program.
  2. Contracting for printing of individual programs for the delegates' totes, and the presentation boards to go outside each of the session rooms.
  3. Purchasing and printing delegates' name labels.
  4. Preparation and printing of "Session Chair Notes", for distribution to session chairs.
  5. Preparation and printing of "Speakers' Notes", for distribution to speakers.
  6. Delivery of tote bag inserts and stuffing of inserts into totes (normally handled by on-site volunteers).
  7. Organization of registration process and briefing of day one volunteers.
  8. Supervision of everything to make sure there won't be any unforeseen glitches. [This doesn't eliminate unforeseen glitches, it just minimizes them].
  9. [added after IRC communications]: encourage sprint leaders to prepare feedback and prepare to present it at the feedback session.
  10. Preparation and printing of public notices (e.g. signage for registration desk, sponsors' logo sheet).

During the conference

  • Supervise sprints.
  • Run the registration desk.

After the conference

  • Prepare web-based proceedings.
  • Prepare recorded audio.
  • Evaluate participant feedback and prepare report.
  • Determine profit/loss.

Related links

Programming conferences

SF fandom


CategoryPyConPlanning

ConventionHowto (last edited 2009-05-18 20:53:49 by PaulBoddie)

Unable to edit the page? See the FrontPage for instructions.