This is a static archive of the Python wiki, which was retired in February 2026 due to lack of usage and the resources necessary to serve it — predominately to bots, crawlers, and LLM companies.
Pages are preserved as they were at the time of archival. For current information, please visit python.org.
If a change to this archive is absolutely needed, requests can be made via the infrastructure@python.org mailing list.

DC-Area Python BarCamp

Goals

Space requirements

We'll bring in easels w/ whiteboards or paper pads, or those static-clinging sheets for the wall.

Talk ideas

Talks on the first day should be a mix of offered and invited, going from more introductory talks early on to more advanced and specialized talks later. Possible ideas:

Possible venues

DC:

Arlington:

Baltimore:

Current tasks

E-mail possible CS department contacts

Research hotel prices in the fall: Baltimore vs. DC; is one city much cheaper?

What to do about wireless, which is critical? Bring it in? Rely on the venue's wireless? What if it fails, which would cripple us?

Budget notes

Assuming 50 attendees, and assuming we get food (which is looking unlikely):

 1500? Venue
  500? Projector rental
 1500  Food for 50 attendees ($15 x 50 attendees x 2 days)
  250  Contingency 
  250  Equipment (power strips, etc.)
  250  Printing (signage, local map, etc.)
---------------------------
 4250  Total

Charging $10 admission to 50 people only brings in $500; we'd need to charge at least $80 to break even. Maybe we should just forget about charging admission and look for sponsorship instead.

The Chicago BarCamp cut costs by borrowing projectors and other equipment from techies and businesses who wanted a mention; it cut out the food cost by borrowing microwaves and finding a venue near restaurants. Do it on the cheap!


2026-02-14 16:12