From Fedora Project Wiki

(Created page with "This is the main page for the systemd FAD 2013, which is a FAD focused on systemd in Fedora. == Purpose == # Our purpose is to... complete with the following '''primary''...")
 
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:
#* Discuss current systemd issues and priorities of systemd in Fedora
#* Discuss (and fix!) current issues and priorities of systemd in Fedora
#* Collect feedback for upstream development
#* Collect feedback for upstream development
#* Discuss possible additions to the RPM macros for systemd in Fedora
#* Discuss possible additions to the RPM macros for systemd in Fedora

Revision as of 17:40, 16 January 2013

This is the main page for the systemd FAD 2013, which is a FAD focused on systemd in Fedora.

Purpose

  1. Our purpose is to... complete with the following primary goals:
    • Discuss (and fix!) current issues and priorities of systemd in Fedora
    • Collect feedback for upstream development
    • Discuss possible additions to the RPM macros for systemd in Fedora
    • Discuss whether we should recommend Defaults for Restart= in Fedora for systemd services.

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