This is the main page for the 2010 Events FAD, which is a FAD focused on tools, infrastructure, and materials for Fedora events, with a focus on FUDCons (though much of the work will likely be reusable for FADs themselves).
Status
This page is a stub/draft; right now we are looking for ideas to put in the #Purpose section. Discussion and coordination are happening on the fudcon-planning list, but this wiki page is the canonical reference to the status of this event's planning.
Purpose
'We are now filling out this section - please add your ideas/thoughts here.
- Our purpose is to... complete with the following primary goals (Still brainstorming a list; we will select the final few primary goals after some options have been generated):
- A scaleable event registration and session scheduling solution
- A recording / remote participation solution
- A repository of FUDCon templates and materials (letters, posters, etc) with instructions for customization
- Define who is needed from RH and the community (who as in what groups, infrastructure, QA, FE, etc. ) to make a successful event
- Create a minimum standard for the type of facility needed to host the event. (ie. # and size of rooms, A/V, location in regards to food & transportation)
- Other ideas?
- In addition, we will attempt to complete the following secondary goals as time allows (Still brainstorming a list; we will select several secondary goals after some options have been generated and primary goals have been chosen):
- An accounting system that is less reliant on a RH person doing everything financially-related
- A FUDCon effectiveness feedback survey that can be used to chart our improvement over time
- A clearly defined sponsorship timeline, publication process, and selection process for assigning travel funding to community members who need it
- Other ideas?
Interested Attendees
Feel free to counterpropose additional locations/dates if you're willing to host and organize logistics for it!
Option 1: Raleigh, NC - Feb 5-7, 2010 (Fri-Sun), logistics-wrangler would be Mel Chua
Option 2: Raleigh, NC - Jan 29-31, 2010 (Fri-Sun), logistics-wrangler would be Mel Chua
| # | FAS Name & Full Name |
Hotel | Option 1 | Option 2 | Comment |
|---|---|---|---|---|---|
| 1 | Mel Chua | or couchsurf | in-person | in-person | coming (possibly driving, if there's carpool interest) from Boston MA |
| 2 | Steven Parrish | N/A | in-person | in-person | |
| 3 | Jon Stanley | yes, or something | in-person | remote, obviously :) | |
| N+1 | Your Name | need hotel? | in-person or remote? | in-person or remote? | other notes |
A note on remote participation
20:05:28 <@stickster> Oh wait -- didn't we talk about making this more of an
online event?
20:05:48 * stickster thinks that might have been Max's idea because it would
allow more participation... what's your take on that?
20:11:21 < mchua> stickster: the "how do we record events?" folks will have a
hard time testing if they're not in person
20:12:22 < mchua> stickster: I think having it as a joint physical/online - not
worrying about getting everyone over, but having a few people
in the same location so the recording team can test - would
work well
20:12:30 < mchua> stickster: echoing the FUDCon/FUDCon Live arrangement,
basically
20:12:33 <@stickster> WORKSFORME.
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
- Be Somewhat Structured
- Arrange Lodging
- Arrange Refreshments
- Arrange a Social Event
- Negotiate airline discount
- Verify network infrastructure exists and is up to the task
- 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