From Fedora Project Wiki
(creating fixing features fad page) |
No edit summary |
||
| Line 3: | Line 3: | ||
== Purpose == | == Purpose == | ||
# Our purpose is to... complete with the following '''primary''' goals: | # Our purpose is to... complete with the following '''primary''' goals: | ||
#* | #* Identify the purpose of an improved Feature process | ||
#* | #** What are we trying to improve? What is broken, what works well and should be retained? | ||
#* Draft and propose an improved feature process for approval by FESCo | |||
#* | |||
== Detailed Work Items & Final Attendees == | == Detailed Work Items & Final Attendees == | ||
* [Changes_to_Feature_Process] is the starting point for what we are looking at. | |||
* See [[Fixing_Features_FAD_game_plan]] | * See [[Fixing_Features_FAD_game_plan]] | ||
Revision as of 16:53, 22 March 2011
This is the main page for the Fixing Features FAD (aka: F3), which is a FAD focused on fixing the Fedora feature process.
Purpose
- Our purpose is to... complete with the following primary goals:
- Identify the purpose of an improved Feature process
- What are we trying to improve? What is broken, what works well and should be retained?
- Draft and propose an improved feature process for approval by FESCo
- Identify the purpose of an improved Feature process
Detailed Work Items & Final Attendees
- [Changes_to_Feature_Process] is the starting point for what we are looking at.
- See Fixing_Features_FAD_game_plan
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
- 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