Brand book FAD 2010

Purpose
The purpose of the Brand Book FAD is to create the following:
 * A concise, centralized branding document with guidelines for usage of items such as logo, fonts, look and feel, etc. (This will likely be completed pre-FAD - or at least be in a very solidified state.)
 * A more lengthy document / book / pdf / at least wiki page (likely printable for marketing collateral / Press Kit love) which conveys the story and messages of Fedora in a timeless manner.

Detailed Work Items & Final Attendees

 * See FAD_Fedora_Talk_2009_game_plan

Logistics

 * Work out budget - Ian to ask Max for go-ahead, funding guidelines.
 * Decide on Dates and Location. We have two possibilities in mind - trying to figure out what is easiest for travel and/or budget:
 * Arrange something pre- or post-Red Hat Summit in Boston. If appropriate / interested people are around, might be easier to adjust plane tickets than to buy a whole set of new ones.
 * Late July in RDU.
 * Arrange Facilities
 * List Resources
 * Be Somewhat Structured
 * Arrange Lodging
 * Arrange Refreshments
 * Arrange a Social Event

FAD Pre-Work

 * User:ianweller to complete actual Branding wiki page prior to FAD. Will contain information such as (ian, fixthis if i'm off base here):
 * Logo / trademark guidelines
 * Color Palette
 * Fonts / usage
 * ... all in ONE place.
 * Yes, yes, and yes. :) &mdash;Ian Weller 18:59, 31 May 2010 (UTC)
 * Make a brand book / story book wiki page. (More storybook oriented; basically a place to brainstorm ideas pre-FAD.)
 * Determine if we are going to lay out content just in wiki format during FAD, and format into .pdf / book format post-FAD.
 * If so: how will we structure the content for each page on the wiki?
 * Suggested: Notate for each page - (a) background content (color or photo) (b) text (c) font used, sizing, location --Rbergero 17:28, 28 May 2010 (UTC)
 * People should read the Red Hat story for ideas / brainstorming (need to find link for this). Would be useful to also have other content to preview.

Plan

 * 1) Location:
 * 2) Date:
 * 3) Schedule
 * 4) * Participants arrive at THIS_TIME_AND_DATE
 * 5) * Schedule item
 * 6) * Schedule item
 * 7) * Schedule item
 * 8) * Participants leave at THIS_TIME_AND_DATE
 * 9) Important skills (one or more)
 * 10) * skill
 * 11) * skill
 * 12) * skill
 * 13) Personnel (people who might fit the bill)
 * 14) * Name (location, role) Confirmed? (Y/N)
 * 15) * Name (location, role) Confirmed? (Y/N)
 * 16) * Name (location, role) Confirmed? (Y/N)
 * 17) * others?
 * 18) Other considerations
 * 19) * Contributor V can offer a living room for evening social gatherings.
 * 20) * Contributor W has a car and is willing to do airport pick-ups.
 * 21) * Contributor X needs as much advance notice as possible.
 * 22) * Contributor Y has a schedule that is better on Fridays than on Tuesdays, and prefers weekend times after 4:28 AM.
 * 23) * Contributor Z is allergic to peanuts.

Logistics
Snacks/Beverages: Details go here.

Lunch: Details go here.

Dinner: Details go here.

Budget
'''If you want funding from Red Hat, ask the Community Architecture team. If you can find other ways to fund your FAD, that's great too!'''


 * 1) Travel:  $A for airfare, bus, train, etc. funding needed to get attendees to the FAD
 * 2) Housing:  $B for hotel, etc. needed to have attendees sleep during the FAD
 * 3) * link to hotel room booking website, if applicable
 * 4) Space: $C for renting space to hack in, if applicable
 * 5) * address and travel details for the space
 * 6) Supplies: $D for anything else you may need
 * 7) * item
 * 8) * item
 * 9) * item

''Total budget: $A+B+C+D