FAD Bodhi2 Taskotron 2014

From FedoraProject

Revision as of 16:44, 12 March 2014 by Lmacken (Talk | contribs)

Jump to: navigation, search

This is the main page for The Bodhi2/Taskotron FAD, which is a FAD focused on Bodhi2 and Taskotron.

Contents

Purpose

  1. Our purpose is to... complete with the following primary goals:
    • Bodhi/2.0:
      • Masher improvements and optimizations
      • fedmsg integration & automation
      • New update creation widgets
      • Improved testing feedback widgets
      • Modern Fedora chrome
      • New frontpage dashboard
      • koji-mash integration (if ready)
      • OpenID authenticating bodhi command-line client
      • Configurable update policy controls
      • Adapt to meet new requirements for Fedora.next
    • Taskotron:
      • bodhi2 integration
  2. In addition, we will attempt to complete the following secondary goals as time allows:
    • secondary goal
    • secondary goal
    • secondary goal

Potential Attendees

Let's use this table to track who is interested in attending, whether or not they need travel, and what times they are available or not.

Contributor Travel? or Local? Possible times?
Ralph would have to fly Anytime May or June works.
Kevin local Anytime after first week in may works.
Mathieu would have to fly Not available in May, early June could work.
Tim local-ish, ~70 miles Anytime in May or June Works
Mike local-ish, ~70 miles Anytime in May, After the 15th June
Luke local Anytime in May. Anytime in June except for 6-9th and the 21st.
You! fly, drive, local? Anytime except May 29th-June 2nd.

Detailed Work Items & Final Attendees

  • Will need folks from releng, qa, infrastructure and possibly packagers there.

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

Plan

  1. Location: Denver area
  2. Date: Late may/Early june.
  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)
    • packaging
    • updates testing
    • releng processes
    • python coders
  5. Personnel (people who might fit the bill)
    • Lmacken (local, bodhi2 author) Confirmed? (Y/N)
    • Tflink (local, taskotron author) Confirmed? (Y/N)
    • Name (location, role) Confirmed? (Y/N)
    • others?
  6. Other considerations
    • Kevin is local and can offer a living room for evening social gatherings.
    • Kevin has a car and is willing to do airport pick-ups.
    • Tim will be driving and thus will also have a car for some airport pick-ups

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 (old page) -- (new page) 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