Differences between revisions 8 and 12 (spanning 4 versions)
Revision 8 as of 2008-03-24 17:54:44
Size: 2991
Editor: px5o
Comment:
Revision 12 as of 2008-04-08 14:19:59
Size: 2077
Editor: 03-144
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
#format rst
Line 4: Line 6:

Mailing Lists
-------------

pyohio mailing list, for announcements only: http://mail.python.org/mailman/listinfo/pyohio

pyohio-organizers, for all sorts of planning discussion: http://mail.python.org/mailman/listinfo/pyohio-organizers
Line 10: Line 19:
Location
--------
Planning Resources
------------------
Line 13: Line 22:
Requirements:  * Organizers__
Line 15: Line 24:
 * Ideally, space for 2 talks of ~ 50 attendees each, plus 2 Open Space groups of ~ 20 each   __ PyOhio/Organizers
Line 17: Line 26:
 * Wireless! Absolutely crucial if we have sprints, very desirable otherwise  * Venue__
Line 19: Line 28:
Places to check with:   __ PyOhio/Venue
Line 21: Line 30:
 * Ohio Supercomputing Center  * Staff__
Line 23: Line 32:
    They did, after all, put this on: http://www.osc.edu/press/releases/2007/python.shtml   __ PyOhio/Staff
Line 25: Line 34:
 * Universities  * Supplies__
Line 27: Line 36:
 * High schools

 * Library

    The Columbus Public Library has a very generous policy on letting groups meet: http://evanced.columbuslibrary.org/evanced/lib/roomrequest.asp The only problem is the funny capacity: a 200-seating auditorium (OK but overkill) and two conference rooms (seating 15 and 10). That would suit a single talk track and two open spaces OK, but things would get funny in the afternoon when it's all open spaces.

 * Private company

    Anyplace with substantial Python-using population might be willing

 * Training companies

    The Cincinnati and Dayton branches of New Horizons have been friendly to user groups; is that true of Columbus?

 * [http://www.oclc.org/conferencecenter/default.htm OCLC]

    It looks like a nice facility, and it's said they have some Python users. My only worry is that they'll want $, but it can't hurt to ask.
  __ PyOhio/Supplies
Line 54: Line 47:

Gear needed
-----------

 * Projectors: At least one per scheduled talk track; ideally, Open Space rooms should have projectors, too

    CatherineDevlin can borrow one from work. Can anybody else?

    Don't sweat it too much until we know the locale, since it may provide them.

 * Microphones, amplifiers, etc.

 * Big board for Open Space scheduling
Line 88: Line 68:
 * a Kinko's (or whatnot) card for our program guides / handouts
Line 89: Line 71:

Publicizing
-----------

Announcements should go to:

 * comp.lang.python.announce

 * COLUG

 * Dayton Microcomputer Association

 * Everybody's blogs, of course

 * Columbus Ruby Brigade

PyOhio is a daylong regional miniconference being planned for the summer of 2008 in Columbus, OH.

We are very much still in the planning stages, and this page is being used to gather notes.

Mailing Lists

pyohio mailing list, for announcements only: http://mail.python.org/mailman/listinfo/pyohio

pyohio-organizers, for all sorts of planning discussion: http://mail.python.org/mailman/listinfo/pyohio-organizers

Budget

Let's try to avoid having one! If we can get a location for free and turn attendees loose for lunch, we can avoid this headache.

Planning Resources

Schedule

I suggest one or two tracks of pre-scheduled talks in the morning, with Open Space available outside. The afternoon can be an unconference, devoted entirely to Open Space.

Anyone who would like to schedule a sprint in conjunction with PyOhio should definitely do so!

And let's have Lightning Talks!

Brochure

Attendees should get a handout describing:

  • what Open Spaces are & how to participate
  • scheduled talks with their abstracts

Sponsors

Shouldn't be necessary, since we're trying to go without a budget. However, if any sponsors do appear, there are some things they could do for us:

  • Buying lunch or snacks
  • Swag or door prizes
  • Paying for a locale (if all else fails)
  • a Kinko's (or whatnot) card for our program guides / handouts
  • Paying for an after-party

Publicizing

Announcements should go to:

  • comp.lang.python.announce
  • COLUG
  • Dayton Microcomputer Association
  • Everybody's blogs, of course
  • Columbus Ruby Brigade

After-party

Don't look at me, I'm a nerd. But it is a possibility...

More planning resources at [http://wiki.python.org/moin/Advocacy/UsergroupSupport User Group Support]

PyOhio08 (last edited 2009-04-05 01:13:51 by pool-68-238-9-184)

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