what's left for the tempe packet?

[Ian Weller]

On Sun, Jan 09, 2011 at 08:49:24PM -0500, Paul Frields wrote:
> On Sun, Jan 9, 2011 at 3:31 AM, Ian Weller <ian at ianweller.org> wrote:
> > - I need a welcome letter (page 2).
> 
> Was Jared providing this?

Ryan wrote one today, we've been collaboratively editing it and it's on
the uploaded version of page 2 now. It's "from" all of the main event
owners (jsmith, rbergero and rrix).

> > - I need a write-up on how a BarCamp works (page 7).
> 
> Let me make a go of it, if you don't have already:

rrix wrote one of these too but is missing a lot of stuff from below so
ctyler and I are merging in EtherPad right now.

> In many conferences, attendees find some of the best information and
> exchange of ideas in the hallway, between sessions, as they engage
> with peers and colleagues. That effect's been referred to humorously
> as the "hallway track." The BarCamp conference attempts to take that
> experience and transform the proceedings into a way to deliver it.
> 
> In a BarCamp, attendees arrive ready to participate by holding a
> session that interests them, and that they think will interest their
> peers and colleagues. Sessions are pitched in the opening session, and
> a schedule for the remainder of the event is collaboratively created
> by the session owners and audience.
> 
> The Rule of Two Feet is also something attendees are encouraged to
> practice. You are not required to stay in a session that loses your
> interest. If you're unhappy, you have many alternatives. If you think
> you'd be happier in another session, go there! If you'd like a session
> leader to cover a different kind of material, ask them about it.
> (Nicely, of course -- we value courtesy along with flexibility.)
> 
> Sound confusing? In principle, you'd be right. In practice, though,
> this process results in a dynamic, engaging, and information-packed
> event. At FUDCon, we use a BarCamp style format for the technical
> sessions. The combination of collaboration, flexibility, and
> user-driven content makes it nearly impossible to leave the conference
> dissatisfied. Once you've experienced a BarCamp style event, you may
> start to enjoy it more than other formats!
> 
> > - I need more ideas for what to put on page 7, after the BarCamp stuff.
> 
> Hm. Just some lines for notes on upcoming hackfests or contacts?

Decided to say when and where the free food was, and explain the
lightning talks.

> > - Add artwork from the Tempe T-Shirt to blank spaces on page 3 and 9.
> 
> That sure would look nicer than blank lines IMHO!

Filled in space successfully on page 9 (see above) and decided to make
page 3 an area where we can stick labels with last minute information on
them. Basically, we'll print any last-minute changes and/or wireless
information on a bunch of labels and stick 'em on by hand when we're in
AZ.

> If there are ways to make this process easier for other FUDCons so
> they don't need a superhuman Ian at their disposal, let's plan to talk
> about them with the international attendees at Tempe -- those people
> who are going to participate in FUDCon planning and execution in other
> parts of the world.

The Makefile is there, with its hacky RGB->CMYK conversion and
everything. All that's necessary is knowledge of Inkscape and our brand.

Also, if you're saying I'm superhuman, why can't I make more caffeine
with my bare hands?

-- 
Ian Weller <ian at ianweller.org>
Where open source multiplies: http://opensource.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
Url : http://lists.fedoraproject.org/pipermail/fudcon-planning/attachments/20110109/e034e528/attachment.bin