FAD Release Tools and Infrastructure 2015

This is the main page for FAD Release Tools and Infrastructure 2015. This hackathon is intended to take release tools and process to the next level in Fedora for F23 and beyond.

• Modularize the compose process
• Replace serial bash script with easier to hack and maintain Python tools
• Establish dependency management of compose deliverables
• Cut time to provide updates to users for critical security fixes

Purpose

Technical goals TBD
This should be completed by technical participants as we scope the FAD, to meet the general goals above.

1. Our purpose is to complete the following primary goals:
   • primary goal
   • primary goal
   • primary goal
2. In addition, we will attempt to complete the following secondary goals as time allows:
   • secondary goal
   • secondary goal
   • secondary goal

Potential Attendees

Contributor	Travel, Local, or Remote	Alternate dates (if proposed is no-go)

Detailed Work Items & Final Attendees

• TBD

Planning Prerequisites

See the How to organize a FAD list; you can keep your to-do list here.

• 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: TBA
   • F22 release scheduled Tue 2015-May-19 (but historically we haven't hit the date... FESCo keeping to time-driven, though)
   • Possibilities:
     • 2015-May-07 to 2015-May-11
     • 2015-May-14 to 2015-May-18
     • 2015-May-28 to 2015-Jun-01 (depends on budget?)
     • 2015-Jun-11 to 2015-Jun-15 (depends on budget?)
   • Considerations:
     • F22 release date is heavily time-driven, 2015-May-19, but our record is not good :-)
     • Red Hat Summit is 2015-Jun-26 to 2015-Jun-29
     • Don't want to wait too long for hackfest after new release tool architect arrival, strike while iron is hot
     • Don't want to drag PyCon attendees (Apr 6-16?) around the country too much at one time
3. Schedule
   • International participants arrive Wed before
   • Domestic participants arrive Thu before
   • Fri -- Work day
   • Sat -- Work day
   • Sun -- Work day
   • Participants leave Mon (or Sunday night if required)
4. Important skills
   • Python (vital!)
   • bash
   • understanding of release deliverables
   • knowledge of fedmsg and other backend technologies helpful
5. Personnel (people who might fit the bill)
   • New release tools person
   • Someone(s) from Fedora rel-eng
   • Someone(s) from Fedora app dev
   • Someone(s) from Fedora infra
   • Will Woods from Anaconda team
6. Other considerations
   • Raleigh was site of a previous FAD and is probably a good cost-based option.
     • Did the space last time work out OK?
   • Paul can drive to the event and possibly do some airport pickups.
   • International community members need as much as advance notice as possible

Logistics

Snacks/Beverages: Can be snarfed from RDU offices. (est. $0)

Breakfast:

• Likely at hotel (est $100 per day / $400 total)

Lunch:

• Days other than Fri/Sat/Sun to be covered by attendees.
• Fri: Use office facility, cost covered (est. $75)
• Sat: Order in, cost covered (est. $100)
• Sun: Order in, cost covered (est. $100)

Dinner:

• Days other than Thu/Fri/Sat/Sun to be covered by attendees
• Thu: ad-hoc
• Fri: Tir Na Nog or The Oxford (est. $300)
• Sat: Brewmasters (est. $300 - covered by Fedora Engineering)
• Sun: The Pit (est. $300)

Travel estimates

Contributor	Taxi/transport (to/from home)	Airfare	Taxi/transport (to/from site)	Parking	Other estimated costs
Name

1. Travel: $A for airfare, bus, train, etc. funding needed to get attendees to the FAD
2. Housing: $3045
   • based on 8 domestic + 2 international participants
   • Sheraton Raleigh: $145/night * 4 nights * 4 rooms (domestic); $145/night * 5 nights * 1 room (international)
   • (other possibilities)
3. Space:
   • $0 if Supplied by Red Hat
4. Supplies:
   • N/A

Total budget: $A+B+C+D