From Fedora Project Wiki
(Initial Brand Book FAD page.) |
m (→Purpose: robyn can't type) |
||
Line 3: | Line 3: | ||
* A concise, centralized branding document with guidelines for usage of items such as logo, fonts, look and feel, etc. | * A concise, centralized branding document with guidelines for usage of items such as logo, fonts, look and feel, etc. | ||
* A more lengthy document (possibly printable as marketing collateral as well) which conveys the story and messages of Fedora in a timeless manner. | * A more lengthy document (possibly printable as marketing collateral as well) which conveys the story and messages of Fedora in a timeless manner. | ||
== Detailed Work Items & Final Attendees == | == Detailed Work Items & Final Attendees == |
Revision as of 17:12, 28 May 2010
Purpose
The purpose of the Brand Book FAD is to create the following (some of these items may be completed prior to actual FAD):
- A concise, centralized branding document with guidelines for usage of items such as logo, fonts, look and feel, etc.
- A more lengthy document (possibly printable as marketing collateral as well) which conveys the story and messages of Fedora in a timeless manner.
Detailed Work Items & Final Attendees
Planning Prerequisites
See the How to organize a FAD list; you can keep your to-do list here.
- Work out budget
- Decide on Dates and Location
- Arrange Facilities
- List Resources
- Be Somewhat Structured
- Arrange Lodging
- Arrange Refreshments
- Arrange a Social Event
- Another action item
- Another action item
- Another action item
Plan
- Location:
- Date:
- Schedule
- Participants arrive at THIS_TIME_AND_DATE
- Schedule item
- Schedule item
- Schedule item
- Participants leave at THIS_TIME_AND_DATE
- Important skills (one or more)
- skill
- skill
- skill
- 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?
- 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 |
- Travel: $A for airfare, bus, train, etc. funding needed to get attendees to the FAD
- Housing: $B for hotel, etc. needed to have attendees sleep during the FAD
- link to hotel room booking website, if applicable
- Space: $C for renting space to hack in, if applicable
- address and travel details for the space
- Supplies: $D for anything else you may need
- item
- item
- item
Total budget: $A+B+C+D