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.
Purpose
- Objectives:
- Identify key strategic deliverables. For example, Installation Guide, Admin Guide, etc. The Fedora docs team can (and almost certainly will) deliver other docs, but these will be the focus of cross-project collaboration.
- Outline how each key deliverable can be assembled from smaller topics. Smaller topics ease reuse and collaboration between teams.
- Discuss the hornet's nest that is tooling. Common tooling can reduce cross-project friction, but it's not strictly necessary. Fedora needs tools that serve its community's needs first.
Impact
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.
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(tentatively set)- Arrange Facilities
- List Resources
- Be Somewhat Structured
- Arrange Lodging
- Arrange Refreshments
- Arrange a Social Event
Plan
- Location: Red Hat Tower, Raleigh, NC
- Date: May 6-8, 2016
- 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
- Personnel (people who might fit the bill)
- Pete Travis (location?, Fedora docs team lead) Confirmed? (Y/N)
- Zach Oglesby (location?, Fedora docs team member) Confirmed? (Y/N)
- Jared Smith (Stafford VA, Fedora docs team member) Confirmed? (Y/N)
- Shaun McCance (Cincinnati, Red Hat community docs) Confirmed? Y
- Stephen Gilson (Westford, Red Hat product docs) Confirmed? (Y/N)
- Paul Frields (Fredericksburg VA, Red Hat Fedora eng) Confirmed? (Y/N)
- Ryan Lerch (Brisbane QLD Australia, Red Hat Fedora eng) Confirmed? (Y/N)
- Name (location, role) Confirmed? (Y/N)
- Name (location, role) Confirmed? (Y/N)
- Name (location, role) Confirmed? (Y/N)
- others?
- Other considerations
- 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.
Logistics
Snacks/Beverages: Details go here.
Lunch: Details go here.
Dinner: Details go here.
Budget
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 | Travel to FAD, departure | Travel to FAD, arrival | Travel from FAD, departure | Travel from FAD, arrival | (funded directly by Red Hat) |
| 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 |
- Travel: $A for airfare, bus, train, etc. funding needed to get attendees to the FAD
- Housing: $B for hotel, etc. needed to have attendees sleep during the FAD
- link to hotel room booking website, if applicable
- Space: $C for renting space to hack in, if applicable
- address and travel details for the space
- Supplies: $D for anything else you may need
- item
- item
- item
Total budget: $A+B+C+D