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

Planning Prerequisites

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. :) —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
   • Participants arrive at THIS_TIME_AND_DATE
   • Schedule item
   • Schedule item
   • Schedule item
   • Participants leave at THIS_TIME_AND_DATE
4. Important skills (one or more)
   • skill
   • skill
   • skill
5. Personnel (people who might fit the bill)
   • Name (location, role) Confirmed? (Y/N)
   • Name (location, role) Confirmed? (Y/N)
   • Name (location, role) Confirmed? (Y/N)
   • others?
6. Other considerations
   • Contributor V can offer a living room for evening social gatherings.
   • Contributor W has a car and is willing to do airport pick-ups.
   • Contributor X needs as much advance notice as possible.
   • Contributor Y has a schedule that is better on Fridays than on Tuesdays, and prefers weekend times after 4:28 AM.
   • 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!

Contributor	Dept	Arrv	Dept	Arrv	Cost
Name	Travel to FAD, departure	Travel to FAD, arrival	Travel from FAD, departure	Travel from FAD, arrival	Ticket cost
Name	Travel to FAD, departure	Travel to FAD, arrival	Travel from FAD, departure	Travel from FAD, arrival	Ticket cost
Name	Travel to FAD, departure	Travel to FAD, arrival	Travel from FAD, departure	Travel from FAD, arrival	Ticket cost

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
   • link to hotel room booking website, if applicable
3. Space: $C for renting space to hack in, if applicable
   • address and travel details for the space
4. Supplies: $D for anything else you may need
   • item
   • item
   • item

Total budget: $A+B+C+D