From Fedora Project Wiki

No edit summary
(added bullet points)
 
(One intermediate revision by the same user not shown)
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
#* Identify the purpose(s) of the feature process
#** What are we trying to improve? What is broken, what works well and should be retained?
#* Identify Fix-its: What are we trying to improve? What is broken, what works well and should be retained?
#* Redefine or further clarify definitions for [[Features/Policy/Definitions | Features and Enhancements]]
#* Draft and propose an improved feature process for approval by FESCo
#* Draft and propose an improved feature process for approval by FESCo
#* Redraw the feature process diagram
#* Create a plan to re-educate/spread the word about the New and Hopefully Improved Feature process


== Detailed Work Items & Final Attendees ==
== Detailed Work Items & Final Attendees ==
* [Changes_to_Feature_Process] is the starting point for what we are looking at.
* [[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]]



Latest revision as of 19:40, 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

  1. Our purpose is to... complete with the following primary goals:
    • Identify the purpose(s) of the feature process
    • Identify Fix-its: What are we trying to improve? What is broken, what works well and should be retained?
    • Redefine or further clarify definitions for Features and Enhancements
    • Draft and propose an improved feature process for approval by FESCo
    • Redraw the feature process diagram
    • Create a plan to re-educate/spread the word about the New and Hopefully Improved Feature process

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
  • Be Somewhat Structured
  • Arrange Lodging
  • Arrange Refreshments
  • Arrange a Social Event
  • Another action item
  • Another action item
  • Another action item

Plan

  1. Location:
  2. Date:
  3. Schedule
    • Participants arrive at THIS_TIME_AND_DATE
    • Schedule item
    • Schedule item
    • Schedule item
    • Participants leave at THIS_TIME_AND_DATE
  4. Important skills (one or more)
    • skill
    • skill
    • skill
  5. 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?
  6. 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
  1. Travel: $A for airfare, bus, train, etc. funding needed to get attendees to the FAD
  2. Housing: $B for hotel, etc. needed to have attendees sleep during the FAD
    • link to hotel room booking website, if applicable
  3. Space: $C for renting space to hack in, if applicable
    • address and travel details for the space
  4. Supplies: $D for anything else you may need
    • item
    • item
    • item

Total budget: $A+B+C+D