From Fedora Project Wiki

Line 10: Line 10:
 
# Our purpose is to complete the following '''primary''' goals:
 
# Our purpose is to complete the following '''primary''' goals:
 
#* Create repositories and workflow for code collaboration including patch review
 
#* Create repositories and workflow for code collaboration including patch review
 +
#** Where will the code be stored? Where will patches and commit messages go?
 +
#** Who can approve patches? How does one get commit access? (Note: This should be ''as many responsible/trusted committers as possible'', in accordance with good community practice)
 
#* Complete any remaining architecture/design details for new release tools
 
#* Complete any remaining architecture/design details for new release tools
 +
#** As much of this should be worked out on mailing list and IRC ''before'' the FAD as possible
 +
#** If additional VMs are needed, complete RFRs for infrastructure
 
#* Hack (possibly fedmsg-based) framework for product compose
 
#* Hack (possibly fedmsg-based) framework for product compose
 
#* (stand up VMs and/or ansible playbooks for required systems?)
 
#* (stand up VMs and/or ansible playbooks for required systems?)
 
#* ...
 
#* ...
 
# In addition, we will attempt to complete the following '''secondary''' goals as time allows:
 
# In addition, we will attempt to complete the following '''secondary''' goals as time allows:
#* Early sessions on Fedora Hubs design/user stories - Thursday, [[Fedora Engineering]] team members
+
#* Early sessions on Fedora Hubs design/user stories - Thursday, [[Fedora Engineering]] team members + [[User:Decause | Remy]]
 
#* ...
 
#* ...
  

Revision as of 13:24, 5 May 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/F24 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

Important.png
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:
    • Create repositories and workflow for code collaboration including patch review
      • Where will the code be stored? Where will patches and commit messages go?
      • Who can approve patches? How does one get commit access? (Note: This should be as many responsible/trusted committers as possible, in accordance with good community practice)
    • Complete any remaining architecture/design details for new release tools
      • As much of this should be worked out on mailing list and IRC before the FAD as possible
      • If additional VMs are needed, complete RFRs for infrastructure
    • Hack (possibly fedmsg-based) framework for product compose
    • (stand up VMs and/or ansible playbooks for required systems?)
    • ...
  2. In addition, we will attempt to complete the following secondary goals as time allows:

Detailed Work Items & Final Attendees

Contributor Arrival Departure Roommate
Dennis Gilmore Peter Robinson
Peter Robinson Dennis Gilmore
Ralph Bean n/a
Remy DeCausemaker TBD
Luke Macken Adam Miller
Mike McLean Mike Bonnet
Adam Miller Luke Macken
Will Woods Ian McLeod
Colin Walters n/a n/a n/a
Ian McLeod Will Woods
Jon Disnard TBD
Remote attendees
Dan Horak (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

Plan

  1. Location: Red Hat, Westford, MA USA
  2. Date: Jun-04 to Jun-08
    • Considerations:
  3. Schedule
    • Fedora Engineering team domestic participants arrive Wed before (for Thu Hubs session)
    • Non-Fedora Engineering team 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
    • knowledge of Koji processes and internals helpful
    • Will Woods from Anaconda team

Logistics

Snacks/Beverages: Can be snarfed from Westford office

Breakfast:

  • Covered at hotel

Lunch:

  • Days other than Thu/Fri/Sat/Sun to be covered by attendees.
  • Thu: Order in, cost covered (est. $125)
  • Fri: Order in, cost covered (est. $125)
  • Sat: Order in, cost covered (est. $125)
  • Sun: Order in, cost covered (est. $125)

Dinner:

  • Days other than Thu/Fri/Sat/Sun to be covered by attendees
  • Thu: ad-hoc
  • Fri: Team @ local venue (est. $300)
  • Sat: Team @ local venue (est. $300)
  • Sun: Team @ local venue (est. $300)

Total food: est. $1400

Travel estimates

Contributor Taxi/transport (to/from home) Airfare Taxi/transport (to/from site) Parking Other
Dennis Gilmore - - - - covered by RCM
Peter Robinson - - - - covered by RCM
Ralph Bean $100 (gas) $ 50 (parking from F-Eng budget)
Daniel Mach - - - - covered by RCM
Luke Macken $390 $ 50 (parking from F-Eng budget)
Mike McLean - - - - covered by RCM
Adam Miller $225 $ 50 (parking from F-Eng budget)
Will Woods $210 $ 50 (parking from Anaconda or F-Eng budget)
Ian McLeod $250 $ 50
Jon Disnard - - - - covered by RCM
  1. Travel: $500 rental minivan + $1175 above = $1675
  2. Housing: $1185
    • Hampton Inn Westford/Chelmsford, <http://ur1.ca/ka20d> -- $117/night
      • for FAD budget: 1 room 4 nights, 1 room 5 nights = 9 nights + tax = ~$1185
    • Ralph Bean: $65 * 5 nights = $325
  3. Space:
    • $0 if Supplied by Red Hat
  4. Supplies:
    • N/A
  5. Food: $1400 (from above)

Total budget: $4,585