Hello from the land of sleep deprivation.
Here's what's left for the Tempe booklets. Deadline for when Ian burns a CD with the PDFs is Sunday night, CST.
Some info I'm not totally sure about or can't write because I am bad at writing. Here's what I need:
- I need a welcome letter (page 2). - I need a write-up on how a BarCamp works (page 7). - I need more ideas for what to put on page 7, after the BarCamp stuff. - I need someone to tell me what rooms we're using for the different talks on Saturday and Sunday in BYAC, or to tell me to leave the headings blank so people can write in room numbers themselves (pages 8 and 9). - I need someone to double-check the schedule on pages 8 and 9. - I need a few more copy editing eyes.
Things I'm going to spend time on tomorrow:
- Double check that all URLs actually point to what they should point to. - Double check information for local vendors. Add mileages for anything that's more than a 15-minute walk. - Add artwork from the Tempe T-Shirt to blank spaces on page 3 and 9. - Double checking a few thousand times that the PDFs are completely CMYK, and hoping they open up fine at the print shop (I don't see why not, seeing as how GhostScript is standards compliant. Oh, you never know...).
Thanks to everyone who has slaved getting me information and other stuff to make this thing happen. It's worth it, I think :)
Production schedule for the booklet: - Monday: Order placed, CD given to publishers, see if they can accept a credit card number over the phone from Max for payment - Tuesday: approve proofs (mainly a color check) - Wednesday-Friday: printers gonna print
On Sun, Jan 9, 2011 at 12:31 AM, Ian Weller ian@ianweller.org wrote:
Some info I'm not totally sure about or can't write because I am bad at writing.
Liar. :-)
- I need a few more copy editing eyes.
Since I do this for a living, I'll lend you one of mine (OK, both). Let me know what I can read for you.
Larry Cafiero
On Sun, Jan 09, 2011 at 08:34:14AM -0800, Larry Cafiero wrote:
On Sun, Jan 9, 2011 at 12:31 AM, Ian Weller ian@ianweller.org wrote:
- I need a few more copy editing eyes.
Since I do this for a living, I'll lend you one of mine (OK, both). Let me know what I can read for you.
http://ianweller.fedorapeople.org/fudcon-tempe-booklet/view_all.html (click the image to get the PNG, and if you need a PDF, just s/png/pdf/ in the URL)
On Sun, Jan 9, 2011 at 1:31 AM, Ian Weller ian@ianweller.org wrote:
Hello from the land of sleep deprivation.
Here's what's left for the Tempe booklets. Deadline for when Ian burns a CD with the PDFs is Sunday night, CST.
Some info I'm not totally sure about or can't write because I am bad at writing. Here's what I need:
- I need a welcome letter (page 2).
- I need a write-up on how a BarCamp works (page 7).
- I need more ideas for what to put on page 7, after the BarCamp stuff.
- I need someone to tell me what rooms we're using for the different
talks on Saturday and Sunday in BYAC, or to tell me to leave the headings blank so people can write in room numbers themselves (pages 8 and 9).
Saturday and Sunday: BYAC 110, 150, 190, 240, 260, 270.
Also, ART 220 (the large space we have for the morning barcamp setups).
And as an FYI, in the MemU on Monday:
MU226 - Graham MU236 - Mohave MU238 - Apache MU240 - Navajo MU242 - La Paz MU246 - Coconino
- I need someone to double-check the schedule on pages 8 and 9.
- I need a few more copy editing eyes.
Things I'm going to spend time on tomorrow:
- Double check that all URLs actually point to what they should point
to.
- Double check information for local vendors. Add mileages for anything
that's more than a 15-minute walk.
- Add artwork from the Tempe T-Shirt to blank spaces on page 3 and 9.
- Double checking a few thousand times that the PDFs are completely
CMYK, and hoping they open up fine at the print shop (I don't see why not, seeing as how GhostScript is standards compliant. Oh, you never know...).
Thanks to everyone who has slaved getting me information and other stuff to make this thing happen. It's worth it, I think :)
Production schedule for the booklet:
- Monday: Order placed, CD given to publishers, see if they can accept a
credit card number over the phone from Max for payment
- Tuesday: approve proofs (mainly a color check)
- Wednesday-Friday: printers gonna print
-- Ian Weller ian@ianweller.org Where open source multiplies: http://opensource.com
fudcon-planning mailing list fudcon-planning@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/fudcon-planning
On Sun, Jan 09, 2011 at 01:30:34PM -0700, Robyn Bergeron wrote:
Saturday and Sunday: BYAC 110, 150, 190, 240, 260, 270.
I know which rooms we have, I don't know which four rooms we are using for talks. That's the problem (see also "BYAC Some Room" on the schedule pages). :)
On Sun, Jan 9, 2011 at 1:33 PM, Ian Weller ian@ianweller.org wrote:
On Sun, Jan 09, 2011 at 01:30:34PM -0700, Robyn Bergeron wrote:
Saturday and Sunday: BYAC 110, 150, 190, 240, 260, 270.
I know which rooms we have, I don't know which four rooms we are using for talks. That's the problem (see also "BYAC Some Room" on the schedule pages). :)
Oh. I knew that.
:D
-- Ian Weller ian@ianweller.org Where open source multiplies: http://opensource.com
fudcon-planning mailing list fudcon-planning@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/fudcon-planning
On Sun, Jan 9, 2011 at 3:31 AM, Ian Weller ian@ianweller.org wrote:
Hello from the land of sleep deprivation.
Here's what's left for the Tempe booklets. Deadline for when Ian burns a CD with the PDFs is Sunday night, CST.
Some info I'm not totally sure about or can't write because I am bad at writing. Here's what I need:
- I need a welcome letter (page 2).
Was Jared providing this?
- 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:
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?
- I need someone to tell me what rooms we're using for the different
talks on Saturday and Sunday in BYAC, or to tell me to leave the headings blank so people can write in room numbers themselves (pages 8 and 9).
Looks like you got this elsewhere.
- I need someone to double-check the schedule on pages 8 and 9.
- I need a few more copy editing eyes.
Things I'm going to spend time on tomorrow:
- Double check that all URLs actually point to what they should point
to.
- Double check information for local vendors. Add mileages for anything
that's more than a 15-minute walk.
- Add artwork from the Tempe T-Shirt to blank spaces on page 3 and 9.
That sure would look nicer than blank lines IMHO!
- Double checking a few thousand times that the PDFs are completely
CMYK, and hoping they open up fine at the print shop (I don't see why not, seeing as how GhostScript is standards compliant. Oh, you never know...).
Thanks to everyone who has slaved getting me information and other stuff to make this thing happen. It's worth it, I think :)
YOU DID A FANTASTIC JOB, IAN. Cannot say that loudly or often enough. I know paid professional organizations that would kill or maim for such a nice conference guide!
Production schedule for the booklet:
- Monday: Order placed, CD given to publishers, see if they can accept a
credit card number over the phone from Max for payment
- Tuesday: approve proofs (mainly a color check)
- Wednesday-Friday: printers gonna print
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.
Again, GREAT JOB.
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@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?
fudcon-planning@lists.fedoraproject.org
-
Ian Weller -
Larry Cafiero -
Paul W. Frields -
Robyn Bergeron