From Fedora Project Wiki
m (→Process) |
|||
Line 53: | Line 53: | ||
# If it definitely solves a problem, it's a "must do." | # If it definitely solves a problem, it's a "must do." | ||
# If it might solve a problem, consider it as an experiment, and mark any regional concerns. | # If it might solve a problem, consider it as an experiment, and mark any regional concerns. | ||
=== Potential things to work on Saturday === | |||
# General calendar for FUDcons | |||
# 2010 instance of said calendar | |||
# Bid process | |||
# "things we should keep" list | |||
# Bug list | |||
# "howto run a fudcon" doc | |||
# make FUDCon 4 days | |||
# Welcome packet at hotel | |||
# Conference software (conman) | |||
# Improved FUDCon Live | |||
# Make event "family friendly" | |||
# Have a clear process for attendee sponsorship |
Revision as of 21:16, 29 January 2010
This is a page where we can work through the "FUDCon 2.0" track of the Events FAD 2010.
Current resources
- FUDCon page and things it links to
- FUDCon#FUDCon_calendar
- FUDCon/Organization - our current howto plan a FUDCon doc
Constraints
- 1 FUDCon per quarter
- $20k of budget from Red Hat per quarter, for FUDcons and FADs
- Hard minimum of at least 4 months advance planning for a FUDCon - 6 months recommended
- Time investment for planners: 3 months ahead at 10-15 hours per week, 1 month ahead at 25 hours per week.
Open questions
- Not Europe for EMEA FUDcon?
- India on its own (split out from APAC)
- Rest of APAC
Issues
- Keep budget spread out.
- Do all FUDCons cost the same?
- Fill in the gaps with FADs
- Climate
- Vacation time (contributors who have to take it)
- Proximity to other major events
- Fix spacing over time
Data from the FUDCon survey
See Marketing_research#FUDCon_Toronto_2009_Survey for data.
Discussion notes below:
Paul:
- May very well need four days for next FUDCon. Need two days for technical sessions alone, fewer rooms at once.
- Welcome packet *at hotel*
- Conference software - ConMan
Mel:
- Accessibility for remote attendees - workable FUDCon Live directions
- Find people who know what it means to make the event "family friendly"
Figuring out action items
Process
- Look at the problems brainstorm at the start of the day, and...
- For each action item/deliverable, see what problems it potentially solves.
- If it definitely solves a problem, it's a "must do."
- If it might solve a problem, consider it as an experiment, and mark any regional concerns.
Potential things to work on Saturday
- General calendar for FUDcons
- 2010 instance of said calendar
- Bid process
- "things we should keep" list
- Bug list
- "howto run a fudcon" doc
- make FUDCon 4 days
- Welcome packet at hotel
- Conference software (conman)
- Improved FUDCon Live
- Make event "family friendly"
- Have a clear process for attendee sponsorship