Open Stack

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 11/01/16 23:42, Sean Dague wrote:

<snip>

> 
> This conversation has gone on long enough I've completely lost the
> problem we're trying to solve and the constraints around it.

Thank you :)

> 
> I'd like to reset the conversation a little.
> 
> Goal: to not flood Docs team with vague bugs that are hard to decypher
> 
> Current Approach: machine enforce extra words after DocImpact (not
> reviewed by doc team)
> 
> Downsides with current approach:
> * it's a machine, not people, so clarity isn't guarunteed.
> * the reviewers of the commit message aren't the people that will have
> to deal with it,   leading to bad quality control on the reviews.
> * extra jobs which cause load and inhibit our ability to stop reseting
> jenkins votes on commit message changes
> 
> My Alternative Approach:
> 
> File doc bugs against project team instead of doc team. Make passing bug
> to Doc team a project team responsibility to ensure context is provided
> when it's needed.

I'm happy to try this, as long as the PTL's of the defcore projects agree.

> 
> This also means there is a feedback loop between the reviewers and the
> folks having to deal with the artifacts (on first pass).

- From docs perspective, it removes the triaging burden off us. If teams are happy to take that on, I certainly won't stand in their way.

Lana

- -- 
Lana Brindley
Technical Writer
Rackspace Cloud Builders Australia
http://lanabrindley.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCAAGBQJWlDWBAAoJELppzVb4+KUyhg4H/j2KKMKQDht9qjbIi80L9CgH
dzC59in/iUqRSjkAt44YG9ikwTQ5zPjIerR7Gj6Lmvm4cijWMoU+rhgO+7A07Nb4
sSADhjcshT8KPhJM/c9jf7BbZld7mGRZ7FrwH+FaxL8ESlcCbaEU9qVSxuwVciJy
ZALGroVDnILQmT5jzOLhOTNzuSW2FZlwamDhuV5TUp3LI8sLlnR0+W5K/6gC4Lmr
LEtIlvsEUk/7bNC3915jMiIrQuGwUBdxL0Z6xcPHRhkXHeiJUHvB31+4kxK8FqVc
GTQWJKNi9yAJ/GQ360vbXhY6HNnVTz0Fs22jlneAu48tlJqqtO6g0KHN8NZVHBc=
=T8bN
-----END PGP SIGNATURE-----