Petr Kovar wrote: > Hi all, > > With the core docs suite moving from openstack-manuals to individual > project repos as per > http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html, > it's also time to update the docs team mission statement from > https://governance.openstack.org/tc/reference/projects/documentation.html. > > What are everybody's thoughts on what should the new mission statement > say now that most OpenStack docs maintenance is in the hands of project > teams? > > One idea is for the docs team to act as a focused group of editors and > maintain a common set of guidelines, recommended practices (style > guidelines come to mind, for instance), and requirements (such as a common > docs and publishing structure shared across projects).
I would say something like: The docs team provides guidance, assistance, tooling, and style guides enabling OpenStack project teams to produce consistent, accurate, and high-quality documentation. -- Thierry Carrez (ttx) __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
