Fedora VDI FAD

From FedoraProject

Jump to: navigation, search

This is the main page for the RHEV VDI FAD, which is a FAD focused on the inclusion of the Red Hat's Virtual Desktop Infrastructure components in Fedora.

Contents

Purpose

  1. Our purpose is to make available in Fedora as much components of Red Hat Virtual Desktop Infrastructure as possible complete with the following primary goals:
  2. In addition, we will attempt to complete the following secondary goals as time allows:
    • Strive to roll back the modified versions of suites included in the RH VDI stack, such as qpixman, qcairo, back onto the readily available pixman and cairo versions
    • Find the necessary motivation to open up the rest of the stack that builds the VDI product, or build a plan to build the VDI product architecture.

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: Utrecht, NL
  2. Date: ~March 2009
  3. Schedule Friday afternoon 'till whenever we're done
    • Participants arrive at THIS_TIME_AND_DATE
    • Welcome & Introduction, Meet & Greet
    • Discussing the tasks at hand and assigning the tasks
    • Execute
    • Participants leave at THIS_TIME_AND_DATE
  4. Important skills (one or more)
    • Coders in various stacks
    • Packagers (Packagers, Reviewers and possibly sponsors as well)
    • skill
  5. Personnel (people who might fit the bill)
    • Jeroen van Meeuwen (Utrecht, NL - organizer) Confirmed? (Y/N) Y
    • Name (location, role) Confirmed? (Y/N)
    • Name (location, role) Confirmed? (Y/N)
    • others?
  6. Other considerations
    • Jeroen van Meeuwen has the office workspace + infra for approx. 10 people available, as well as bar and fussball table.
    • 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