From Fedora Project Wiki

(→‎Purpose: Add the real purpose of the gathering.)
m (fix tables)
Line 18: Line 18:
 
=== Deliverables ===
 
=== Deliverables ===
  
{|
+
{| class="wikitable"
 
! Deliverables: ((TOPIC 1)) !! Task Owner !! Done  
 
! Deliverables: ((TOPIC 1)) !! Task Owner !! Done  
 
|-
 
|-
Line 30: Line 30:
 
=== Follow-up tickets ===
 
=== Follow-up tickets ===
  
{|
+
{| class="wikitable"
 
! Follow-up: !! Ticket  
 
! Follow-up: !! Ticket  
 
|-
 
|-
Line 37: Line 37:
  
 
=== Attendees and Travel Details ===
 
=== Attendees and Travel Details ===
{|
+
{| class="wikitable"
 
! Contributor !! Arrival !! Departure !! Roommate !! Notes
 
! Contributor !! Arrival !! Departure !! Roommate !! Notes
 
|-
 
|-
Line 82: Line 82:
 
== Travel estimates ==
 
== Travel estimates ==
  
{|
+
{| class="wikitable"
 
! Contributor !! Taxi/transport (to/from home) !! Airfare !! Taxi/transport (to/from site) !! Parking !! Other  
 
! Contributor !! Taxi/transport (to/from home) !! Airfare !! Taxi/transport (to/from site) !! Parking !! Other  
 
|-
 
|-

Revision as of 21:45, 4 January 2018

This is the main page for an infrastructure hackathon in spring 2018. This hackathon is intended to help the team leap ahead for several critical Fedora and CentOS initiatives.

Working Session Notes

Coming soon -- winter 2017/2018.

Output and outcomes

This section will record output blogs following the event.

Purpose

Our purpose is to complete the following primary goals:

  1. (TBD -- This outline will cover several topic areas, and specific work that will be completed during the event.)
  2. EPIC PUN BATTLE

Detailed Work Items & Final Attendees

Deliverables

Deliverables: ((TOPIC 1)) Task Owner Done
(Describe the exact thing to be delivered) (check here when done)
Deliverables: ((TOPIC 2)) Task Owner Done
(Describe the exact thing to be delivered) (check here when done)

Follow-up tickets

Follow-up: Ticket
(Describe item that still needs to be completed) (link to ticket)

Attendees and Travel Details

Contributor Arrival Departure Roommate Notes
Remote attendees
Lurkers

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 -- N/A

Plan

  1. Location: TBD
    • Candidate locations: Fredericksburg, VA; Raleigh, NC
    • Lodging: TBD
  2. Date: TBD -- Q1FY18 on Red Hat's fiscal calendar (March - May 2018)
    • (When should attendees arrive by?)
  3. Remote Attendees: (include dial-in)
  4. Schedule
    • Event starts (TIME) daily
    • Event ends by (TBD), to allow for travel outbound
    • ...

Logistics

Snacks/Beverages:

Travel estimates

Contributor Taxi/transport (to/from home) Airfare Taxi/transport (to/from site) Parking Other
  1. Travel: (TOTAL) (est)
  2. Housing: (TOTAL) (est)
  3. Space:
    • (COST) - Supplied by (LOCATION)
  4. Supplies:
    • N/A
  5. Food: (TOTAL) (est -- to be paid by Fedora Engineering budget)

Total budget: (TOTAL) estimated