From Fedora Project Wiki

This is the main page for the Fedora/RHEL/CentOS docs FAD, which is a FAD focused on collaboration on docs with other projects in the Fedora ecosystem.

Dial-in information
Blue Jeans conference code: 97839 21014 -- see for toll free call-in; or via your web browser, use to join.
Report out information
Day 1 -- Blue Jeans recording; Day 2 - Decause Recording


  • Identify key documents that need to be produced each release cycle
    • Identify segments of users to serve and what their docs need are
    • Discuss how these documents can be assembled from reusable topics
  • Outline user stories/requirements for experience for
    • active or frequent Docs team contributors
    • newcomer/drive-by contributors
    • end users/readers
    • remixers/consumers of docs downstream
  • Agree on a strategy for tools that
    1. provide for maximum contribution (both to those tools and content), and
    2. are 100% open and transparent to provide the forkability required in Fedora
  • Produce a roadmap for tool production and deployment, as needed, that includes contribution from all stakeholders (note: this may be minimal if existing tools are available)
  • Set up an informal group to work on follow-ups
    • can reuse existing Docs team meeting time, or a more convenient time if needed
    • assign some regularly periodic progress report, as simple as article on comm-blog or elsewhere
  • If possible, use some meeting time for some form of hackfesting -- if not originating code, at least testing integration and determining bugs/issues or other change requests and setting up to track them over time


The completion of these goals will create the following positive change within the project:

  • The Fedora docs team will have better strategic direction for its docs, rather than writing whatever somebody happens to decide to write.
  • Fedora documentation will have more contributors from downstream projects by making reuse easier.

These outcomes connect with the following Fedora Community Objectives by creating documentation that can be reused for modular Fedora. Fedora's modularization efforts are in line with the direction of its downstream projects, and easing reuse for downstreams also makes Fedora's docs more reusable internally.

There are two notable international travelers for the FAD: Silas Hensley and Ryan Lerch. Both are critical to success at our goals and impact. Silas oversees tools and related process in Red Hat platform docs, so he can bring required experience to help guide us on where we need to align tools with internal groups; and Ryan as a designer with related experience in content/docs can ensure we are designing a workflow that meets requirements for the people who will use the tools and processes, before we get too deep into picking tools.

Detailed Work Items & Final Attendees

  • TBD

Diversity Statement

We are aware that the State of North Carolina has passed recent laws which are not consistent with the Fedora Project's views on equality and diversity, and may make some attendees of the FAD uncomfortable. Both Red Hat and the Fedora Project are committed to providing a discrimination-free experience for attendees. Red Hat, the host of this FAD, will provide facilities appropriately regardless of gender, sexuality, religion or race.

Regardless, if North Carolina's laws make you feel uncomfortable or unable to attend the FAD for any reason, or require changes to your travel arrangements, please contact either Josh Berkus or the Fedora Project diversity advisor, Maria Leandro with your concerns. All such contacts will be confidential.

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 (tentatively set)
  • Arrange Facilities
  • List Resources
  • Be Somewhat Structured
  • Arrange Lodging
  • Arrange Refreshments
  • Arrange a Social Event


  1. Location: Red Hat Tower, Raleigh, NC
  2. Date: May 6-8, 2016
  3. Schedule
    • Participants arrive by the evening of May 5.
    • May 6: all day meeting
    • May 7: all day meeting
    • May 8: all day meeting, possibly early adjourn for travel
    • Participants leave on the evening of May 8 or morning of May 9
  4. Personnel (people who might fit the bill)
    • Name (location, role) Confirmed? (Y/N)
    • Pete Travis (location?, Fedora docs team lead) Confirmed? (Y)
    • Zach Oglesby (Baltimore MD, Fedora docs team member) Confirmed? Y
    • Jared Smith (Fredericksburg, VA, Capital One) Confirmed? N -- NOTE CHANGE
    • Shaun McCance (Cincinnati, Red Hat community docs) Confirmed? Y
    • Stephen Gilson (Westford, Red Hat product docs) Confirmed? (Y)
    • Paul Frields (Fredericksburg VA, Red Hat Fedora eng) Confirmed? Y
    • Ryan Lerch (Brisbane QLD Australia, Red Hat Fedora eng) Confirmed? Y
    • Silas Hensley (Brno, Red Hat product docs) Confirmed? Y
    • Remy DeCausemaker (Raleigh, Red Hat OSAS/Fedora community lead) Confirmed? Y
    • Jim Perrin (Houston Tx, CentOS Project) Confirmed? (Y)
    • Glen Rundblom (Champaign, IL, Fedora docs team member) - Cannot Travel in May but would like to contribute / be apart in some manner
    • Stephen Wadeley (Brno, Red Hat by day, Fedora docs team member by night) - Unfortunately I will be traveling that weekend, holiday already booked.
    • Karsten Wade (Santa Cruz, CA; former Fedora Docs Lead) - Interested in helping remotely, at least in a history-of session, & in discussions around CentOS & workflow.
    • others?
  5. Other considerations
    • Paul would drive to RDU and could give Jared a lift, and/or pick up someone at the airport. Paul must leave the afternoon of Saturday, May 7.
    • Remy lives locally and can do airport
    • 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.


Snacks/Beverages: Details go here.

Lunch: Details go here.

Dinner: Details go here.


If you want funding from Red Hat, ask the OSAS team. If you can find other ways to fund your FAD, that's great too!

Contributor Dept Arrv Dept Arrv Cost
Shaun McCance Wed May 4 morning Wed May 4 noonish Mon May 9 afternoon Mon May 9 afternoon (funded directly by Red Hat)
Paul Frields by car, ~6am Fri May 6 ~10am Fri May 6 by car, ~4pm Sat May 7 ~8pm Sat May 7 F-Eng budget will handle transportation, 1 night lodging
Jared Smith (ditto w/ pfrields) (ditto) (ditto) (ditto) 1 night lodging, can share with pfrields
Pete Travis (by air, 5MAY PM) (by air, 5MAY PM) (by air, 9MAY PM) Travel from FAD, arrival ~$425, need lodging
Ryan Lerch 1000, Wed May 4 BNE (QF15) 1818, Wed May 4 RDU QF3317 (AA) 1855, Sun May 8 -- RDU (AA173) 0905 Tue May 10 BNE $1882AUD (~$1440USD) airfare; Still need lodging for 4 nights.
Zach Oglesby TBD - Jury Duty (Driving) TBD May 7 PM 6ish hours after I leave 3 nights lodging, can share with Pete
Silas Hensley Wed May 4 -- TBA Wed May 4 Mon May 9 -- TBA Mon May 9 $1400 airfare; 5 nights lodging
Stephen Gilson BOS-RDU DL3761 4-may 06:44 Arrive RDU: 08:45 RDU-BOS 8-may DL3890 14:25 Arrive BOS 16:23 Covered by RH
Name Travel to FAD, departure Travel to FAD, arrival Travel from FAD, departure Travel from FAD, arrival Ticket cost
  1. Travel: $3225 for airfare, bus, train, etc. funding needed to get attendees to the FAD
    • Taxi fare for any attendees?
  2. Housing: ~$1500 for hotel, etc. needed to have attendees sleep during the FAD
    • Sheraton or Marriott -- Red Hat rates ($149 to $169/night usually)
    • (pfrields) This estimate seems low, more detail needed
  3. Space: $0

Total budget: $4725