Open Stack

----- Original Message ----- 

> From: "Nermina Miller" <nerminamiller at gmail.com>
> To: "Steve Gordon" <sgordon at redhat.com>
> Cc: "openstack-docs" <openstack-docs at lists.openstack.org>
> Sent: Wednesday, November 20, 2013 11:32:08 AM
> Subject: Re: [Openstack-docs] Fwd: [openstack-dev] [Nova] Blueprint review
> process

> Steve, do you mean like a gap analysis between the projects and the
> documentation? And share that with each project? And prompt them to provide
> as much info as possible (with a tag for each undocumented item) as they
> submit each doc bug. And link the docs bugs to this gap analysis to ensure
> proper coverage? I'd be game for that :) Thank you for going deeper on this.
> I hope everyone jumps in on this conversation. - Nermina

Well, I think initially our gap analysis is the open bug queue (particularly those that have come in via DocImpact) and catching up on that - that's not to say a wider gap analysis wouldn't be beneficial if someone was willing to do it. I can certainly see how wider gaps relating to the bigger picture might gradually be introduced in spite of the DocImpact process.

What I'm pondering here though is how we can then work to ensure that there is more clarity around what documentation changes are nominally required - relevant to a given code change - earlier in the process (ideally when blueprints are actually being approved). To put it more generally "how can docs, or a voice representing docs, be more involved in bringing up blueprint quality".

-Steve