Open Stack

----- Original Message -----
> From: "Tom Fifield" <tom at openstack.org>
> To: "Summer Long" <slong at redhat.com>
> Cc: openstack-docs at lists.openstack.org
> Sent: Tuesday, April 1, 2014 6:18:04 PM
> Subject: Re: [Openstack-docs] How to deal with DocImpact patches
> 
> On 01/04/14 07:56, Summer Long wrote:
> > Was hoping someone would chime in with the further problem of not noting
> > doc bugs or review for docs in the dev space.
> > *  Could the automatic process for a DocImpact dev bug note somewhere that
> > the doc bug has been created?
> 
> Yes, it could post a message on the git review. This just needs a bit of
> coding. Effectively, get jeepyb, and look at welcome_message.py - this
> has the necessary code for posting messages on reviews. Grab that and
> put it in notify_impact.py. Just needs someone who knows python to do
> the work :)
> 
> > *  For patches without 'DocImpact', could we note somewhere that the dev
> > bug has been reviewed for doc impact?
> 
> I'm a little confused by this. Can you elaborate?
>
For blueprints or patches that don't have a doc impact. If 'no doc impact' has been assessed
by docs, would be good to put something on the blueprint's whiteboard so that it's not done over and over again.

Just for those cases where you see a blueprint, no dev has raised a 'DocImpact', and 
you think 'really?', so check it to make sure that something wasn't missed...