[openstack-dev] [all][docs][tc] How to scale Documentation

Jay Pipes jaypipes at gmail.com
Sun Oct 5 03:00:46 UTC 2014


On 10/03/2014 09:18 PM, Zane Bitter wrote:
> The prospect of a much larger tent with many more projects in
> OpenStack-proper shines a spotlight on the scalability of the Docs team,
> and in particular how they decide which projects are "important" to work
> on directly.

I don't believe that a ticket to live under the OpenStack tent should 
come with the expectation that the Docs team is required to write 
documentation for the project.

IMHO, it should be up to the project itself to provide the resources to 
work *under the guidance* of the Docs team to write developer, end user 
and operator documentation. The Docs team members should be able to play 
an advisory role for new projects, helping them understand the automated 
doc processes, the way that common doc infrastructure works, and 
techniques for writing useful documentation consistent with other projects.

Best,
-jay



More information about the OpenStack-dev mailing list