openstack-doc-core team mailing list archive

[Alexandra Settle <alexandra.settle@xxxxxxxxxxxxx>]

Education seems to be the best way forward :)

Thanks everyone for putting forward your ideas and talking about this.


On 1/10/2015 4:12 pm, "Lana Brindley" <openstack@xxxxxxxxxxxxxxxx> wrote:

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>On 01/10/15 15:06, Kato, Tomoyuki wrote:
>>> On 01/10/15 06:37, Lana Brindley wrote:
>>>> -----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 par
>t o
>>>> f
>>>>> the big tent to a list of repos doesn't need one (a complete new ch
>apt
>>>> 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, whi
>le
>>>> still maintaining good quality control. That's a tricky balance to
>>>> manage, and I don't have any brilliant ideas outside of 'keep talkin
>g to
>>>> people about this'. Happy to hear your collective wisdom :)
>>>>
>>>
>>> +1 Completely agree. This is what I was trying to get at with the 'ca
>se
>>> study' as well.
>>>
>>> Instead of looking at the technical content, we went straight to gett
>ing
>>> hung up on whether a bug was triaged or not. That doesn't make sense
>to
>>> me :)
>
>It makes sense in the context of the message we've been sending out.
>Right now, we have a choice: We can have dozens of patches -2d at the
>last minute or (worse) backed out because they broke something, or we
>can have one or two patches with six -1s because they weren't triaged.
>At this point, option #2 seems like the lesser of two evils.
>
>It's certainly not ideal, but getting a more subtle message out there is
>going to take time and education. Which I'm happy to do, of course.
>
>L
>
>- --
>Lana Brindley
>Technical Writer
>Rackspace Cloud Builders Australia
>http://lanabrindley.com
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v2
>
>iQEcBAEBAgAGBQJWDM7CAAoJELppzVb4+KUyHO8H/2J5PcG28N0cbn9j+4bF0eki
>vwWfotVGZ+ZBYo0n7zpMZEKf6b4tkM6GpZakOVJxDS1zwXPeVSOEGdxjyISMHfc8
>258pzYrxi5xnsbPqvd19NG57qUGnZTlblILGaAYRLPTpdasBagcwlOSJ/A+Q6Pze
>sDZ0kZGi8zhbMzbAo0fm64wtH7b6xVq2ME3pUI52XY9vy95aTi1Xoj9XxQ1yPqTw
>ymQT5ailkDZ5NR/wG0thP7R0ioyqTioCRKqKuPfJL3yGXn089N87fJD7TOescDPM
>W1R7ay4IVc66flDMdifDJgMNPWffqbw8SQ5I9uABELatMunFpWfwfg+MNsM36NU=
>=3tQa
>-----END PGP SIGNATURE-----
>
>--
>Mailing list: https://launchpad.net/~openstack-doc-core
>Post to     : openstack-doc-core@xxxxxxxxxxxxxxxxxxx
>Unsubscribe : https://launchpad.net/~openstack-doc-core
>More help   : https://help.launchpad.net/ListHelp


________________________________
Rackspace Hosting Australia PTY LTD a company registered in the state of Victoria, Australia (company registered number ACN 153 275 524) whose registered office is at Level 1, 37 Pitt Street, Sydney, NSW 2000, Australia. Rackspace Hosting Australia PTY LTD privacy policy can be viewed at www.rackspace.com.au/company/legal-privacy-statement.php - This e-mail message may contain confidential or privileged information intended for the recipient. Any dissemination, distribution or copying of the enclosed material is prohibited. If you receive this transmission in error, please notify us immediately by e-mail at abuse@xxxxxxxxxxxxx and delete the original message. Your cooperation is appreciated.