This is the schedule for the Kilo Design Summit, where OpenStack contributors discuss the future of OpenStack development. Click here for the main OpenStack Summit conference schedule.
To borrow from the mailing list thread at http://lists.openstack.org/pipermail/openstack-dev/2014-October/047801.html "The current system is something of a hybrid model - for some subset of official projects considered "important", the Docs team is directly responsible; for the others, the project team has to write the documentation. The docs team is available to provide support and tools for other official projects." Some questions for discussion:
Project liasons, what should they do? The OpenStack Documentation is centralized on docs.openstack.org but often there's a need for specialty information when reviewing patches or triaging doc bugs. A doc liaison should be available to triage doc bugs when the docs team members don't know enough to triage accurately, and be added to doc reviews that affect your project. You'd be notified through email when you're added either to a doc bug or a doc review. We also would appreciate attendance at the weekly doc team meeting, We meet weekly in #openstack-meeting every Wednesday at alternating times.
Do project teams want a Documentation team as advisory? What expectations do you have from the Docs team?
How should the Docs team engage projects that are not already writing user/operator/API docs? How to get integrating teams better docs faster?
How should we write, review, and publish integrated documentation?
