mNo edit summary |
mNo edit summary |
||
Line 6: | Line 6: | ||
Northern California | Northern California | ||
* Stanford | * Stanford | ||
** We have this location for one day for sure; http://wikimapia.org/39261/Cordura-Hall-Stanford-University | |||
* Google Campus | * Google Campus | ||
* 20th and Mission co-working space in San Francisco | * 20th and Mission co-working space in San Francisco |
Revision as of 00:13, 8 August 2012
This is the main page for the Fedora Ambassador Day for North America, which is a FAD focused on planning future events, areas of concentration, and ambassador processes in North America.
Proposed Accomodations
Northern California
- Stanford
- We have this location for one day for sure; http://wikimapia.org/39261/Cordura-Hall-Stanford-University
- Google Campus
- 20th and Mission co-working space in San Francisco
- SFSU
Purpose
- Our purpose is to... complete with the following primary goals:
- Make Ambadassadors more awesome
- Make contributing easier.
- primary goal
- In addition, we will attempt to complete the following secondary goals as time allows:
- Identifying the best candidates to teach new skills to (in relation to folks from other Distros- as well as other types of geeks like gamers
- Creation of local Fedora groups
- secondary goal
Detailed Work Items & Final Attendees
Planning Prerequisites
See the How to organize a FAD list; you can keep your to-do list here.
Completed work item- Work out budget
- Decide on Dates and Location
- Arrange Facilities
- List Resources
- Local folks for driving/picking up folks, 3 nearby airports, numerous locations to choose from
- Be Somewhat Structured
- Arrange Lodging
- Arrange Refreshments
- Arrange a Social Event
- If we use 20th and Mission, an open bar event is most likely included
- Beefy Miracle cutout is needed.
- Another action item
- Another action item
Planning Prerequisite Brainstorming
- Proposed Purposes and Goals
- Help people polish some new presentations they might want to give on Fedora
- Solving logistical problems or discussing how to get new ambassadors or having more mentors
- Planning who is covering what for major events in the coming year or so
- Are there any swag/distribution issues or ideas for improving those processes
- Can ambassadors help promote Fedora things within the Fedora Project (like FADs for non-ambassadors)
- Evaluating the how-to-get involved processes/updating them then making how to videos about them :)
- Media/educational campaigns such as videos for local cable access, or even a weekly/monthly cable access show featuring open source, specifically fedora?
- Can ambassadors work more effectively with marketing or should ambassadors tackle some neglected tasks in that area
- Fix processes that are confusing or not well documented (handling funding requests, getting mentors and the whole concept of mentoring, effective use of trac instances)
- Location Ideas: When proposing a location, keep travel costs in mind. A good FAD location should be close to an airport, not have limited (and therefore usually expensive) transportation options, have free workshop/meeting facilities (with few distractions), is not co-located with another event, and preferrably is in the area where the organizer lives.
- Phoenix, AZ but it's 'hella hot'
- Orlando, FL
- Atlanta, GA
- FAD at a cabana
- Austin, TX
- Dallas-Fort Worth, TX
- Jacksonville, FL
- Stanford, CA aka San Francisco, CA
- Salt Lake City, Utah (It's beautiful here and plenty of nightlife, good transport, Delta hub, etc.)
- Proposed Dates: FADs are typically 2-3 days.
- Same time as FAD_EMEA_2012
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.
Local people
Logistics
Snacks/Beverages: Details go here.
Lunch: Details go here.
Dinner: Details go here.
Budget
If you want funding - you will need to talk to newly formed OSAS - talk to Ruth Suehle. 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