Date: Tue, 20 Feb 2001 16:50:38 -0800
To: lwn@lwn.net
From: Lisa Mann <lisam@oreilly.com>
Subject: Call for papers

The O'Reilly Open Source Convention (July 23-27 in San Diego) is
looking for speakers on Linux and Open Source development.  Our
audience comprises sophisticated developers and administrators, so we
only want talks on solid technical subjects.  Sample topics:
 * embedded Linux
 * GNOME application development
 * Samba
 * securing open source systems
 * corporate needs for open source software
 * corporate experiences with the open source development model
 * using OpenSSL in other applications
 * the vast world of open source Java projects
 * tips on running Linux/FreeBSD/OpenBSD/NetBSD on laptops
 * migrating to FreeBSD 5.0
 * ...

There are two types of presentations: tutorials and talks.

Tutorials:
 * 3 or 6 hours 9 (half- or full-day)
 * take place in the first two days of the convention
 * are not "hands-on" (OScon tutorial attendees will not have
   computers in front of them unless they bring their own laptops)
 * earn $1500 per half-day, plus two days' hotel and food, travel,
   and free conference and tutorial registration.

Talks:
 * 90, 40 or 25 minutes in length (talks will be grouped into 90
   minute sessions)
 * take place in the remaining three days of the convention
 * earn free conference and tutorial registration, but *not* hotel,
   travel, etc.

Proposals should be emailed in plain text format (no attachments
and particularly no Word files) to:
  oscon2001-proposals@oreilly.com

You will have at least two months to prepare the full presentation materials.

All proposals should include:
 * type of presentation proposed (talk or tutorial)
 * title
 * preferred length (note that in some cases we may ask you to
   shorten your talk to accommodate limited time)
 * description of the talk (250 words or less)
 * speaker name, affiliation, email address
 * speaker biography for the website and brochure
 * complete speaker contact information.  If applicable, include
   administrative support (e.g., personal assistant) contact
   information.

In addition, tutorial proposals should include:
 * detailed (2 or more level) outline
 * target audience including any prerequisites (e.g., "a basic
   understanding of PHP is necessary")
 * what attendees will learn--the knowledge or skill take-away
   attendees will have at the completion of the tutorial 





Lisa Mann @ O'Reilly & Associates
101 Morris St., Sebastopol, CA 95472 
707-829-0515 ext. 230    lisam@oreilly.com
http://www.oreilly.com