← Back to team overview

openstack-doc-core team mailing list archive

Re: Bug triaging issue

 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 30/09/15 16:41, Andreas Jaeger wrote:
> Let me open a side discussion:
> 
> I also see far too many bug reports getting asked for.
> 
> We have been liberal about "obvious" bugs. So, a typo does not need a
> bug report. A one-line addition of an OpenStack project that is part o
f
> the big tent to a list of repos doesn't need one (a complete new chapt
er
> needs IMHO something) etc.
> 
> 
> Some people just create those but let's not complicate contribution an
d
> if a patch is obvious, include it.
> 
> There's no sense to create a bug report "like X is missing in list Y"
> and then confirm it, and fix it.
> 

I absolutely agree with you here, and it's more or less what I was
trying to get to by saying we needed to trust everyone's judgement. If
you notice a typo, you don't need a bug, and if you have a bug, you
don't need it triaged before you fix it.

We need to allow people to have control over what they're doing, while
still maintaining good quality control. That's a tricky balance to
manage, and I don't have any brilliant ideas outside of 'keep talking to
people about this'. Happy to hear your collective wisdom :)

L


- -- 
Lana Brindley
Technical Writer
Rackspace Cloud Builders Australia
http://lanabrindley.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBAgAGBQJWDGQgAAoJELppzVb4+KUyY/0H/j0MQ9ZbRBvIUQnTC4PKBOaG
vVgiKnwqwqV1jd/w1FSREgVBh0tcv4QwBcGWj/HU3lKPQT9+EqRFNhknhBO/4iAB
w1jQaprE/CEHorIf4zWktS+tzi2q/KADavpoyC2sYmeMWzG+ddiEbAzGCAlpv6pn
VrZSoswIky84Lra728iJCmrxZE/g3elktUyQCSy/IrDeyjEhon31yPX3z9BeEegk
SQcILNBOYMvsUBDmN1F9xw/fiE39DDYCGlBPod8edCXgb77ETGJtdRITxTaGnNV8
9HhFIW0mmIkHayJEC0CAPwtrdNhZAr4Op4VMqwMVsmgJoi3v615J1ScR5YYT6eo=
=L4/L
-----END PGP SIGNATURE-----


Follow ups

References