On 5/29/2014 6:34 AM, Colin Watson wrote:
> I have reopened this bug. Phillip, please could you refrain from
> triaging grub2 bugs in this way? It creates *more* work for me,
> not less, and does not help. It would in fact help me if there
> were as few further comments as possible until I have a chance to
> address this (which I plan to do for 14.04.1), so that I have less
> to wade through.
>
> The hardest bugs to deal with are the ones that have descended into
> an argument, and rejecting real problems out of hand (and this
> most certainly is a real problem, probably one of the most common
> issues reported to me) increases the probability of arguments.
Indeed, part of the problem is that everyone piled into the same bug
with several different issues rather than troubleshooting it on a case
by case basis.
> Yes, this is complex, and there are indeed some cases that are
> largely intractable; but I do have some ideas of how my code for
> dealing with this class of problems could be improved so that at
> least it affects many fewer people. However, the confrontational
> approach of "As a developer, I have said there is nothing we can do
> on our end to mitigate this", without even bothering to check with
> me whether that's an accurate reflection of the opinions of the
> person who does most of the work on the grub2 packaging, is not a
> good starting point for a conversation.
It wasn't a starting point for a conversation; I had tried dozens of
times for weeks to get more information, identify the cause(es), and
explain why it was a result of incorrect action on the user's part.
That statement was made in direct response to someone saying that as a
user they felt they needed to reopen it ( yet again ) without
understanding why I had closed it, or offering any real
counter-argument. By that point I was throwing my arms in the air.
It would be helpful if you would comment if you think there actually
is something that might be done. Since this had gone on for some time
without any comment from you, I assumed you were ignoring it as just
another kvetch fest. I certainly would be interested in any ideas you
might have.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 5/29/2014 6:34 AM, Colin Watson wrote:
> I have reopened this bug. Phillip, please could you refrain from
> triaging grub2 bugs in this way? It creates *more* work for me,
> not less, and does not help. It would in fact help me if there
> were as few further comments as possible until I have a chance to
> address this (which I plan to do for 14.04.1), so that I have less
> to wade through.
>
> The hardest bugs to deal with are the ones that have descended into
> an argument, and rejecting real problems out of hand (and this
> most certainly is a real problem, probably one of the most common
> issues reported to me) increases the probability of arguments.
Indeed, part of the problem is that everyone piled into the same bug
with several different issues rather than troubleshooting it on a case
by case basis.
> Yes, this is complex, and there are indeed some cases that are
> largely intractable; but I do have some ideas of how my code for
> dealing with this class of problems could be improved so that at
> least it affects many fewer people. However, the confrontational
> approach of "As a developer, I have said there is nothing we can do
> on our end to mitigate this", without even bothering to check with
> me whether that's an accurate reflection of the opinions of the
> person who does most of the work on the grub2 packaging, is not a
> good starting point for a conversation.
It wasn't a starting point for a conversation; I had tried dozens of
times for weeks to get more information, identify the cause(es), and
explain why it was a result of incorrect action on the user's part.
That statement was made in direct response to someone saying that as a
user they felt they needed to reopen it ( yet again ) without
understanding why I had closed it, or offering any real
counter-argument. By that point I was throwing my arms in the air.
It would be helpful if you would comment if you think there actually
is something that might be done. Since this had gone on for some time
without any comment from you, I assumed you were ignoring it as just
another kvetch fest. I certainly would be interested in any ideas you
might have.
-----BEGIN PGP SIGNATURE----- www.enigmail. net/
ThzjSAAoJEI5FoC IzSKrw7TEH/ 2TZLrcRVa0fjeM+ ToK1uyzC rp2caUkCtBfYX1+ 5ZEReMclkwn5RyX G7XKV08fgOtdWtd c9kd GKMGWIbxkT2DCyl 470cLiqhFvyAd3D bHBOunSCcY33EZ2 tnZN dbZk0lXUHjglqtH P0ckA0a10sVk4iu eOTgyrpu3yvZZHH g8Rowlsj3M Yp1nYhYpiSJTEVv G4G053gib/ e+uggyXMlTAqz1C FaTz8+ygN sKnJzvR+ 4N/2bITpV2Uv9OG vDtUXxnPb/ UGUTnsANQqCwii7 DIvM=
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://
iQEcBAEBAgAGBQJ
ol+vy6TSex4x9rK
RccyOMVcEaibbyh
SpLQqqor/
V+XUythsUbtPfTc
0s6nUGMy5n/
=qRUT
-----END PGP SIGNATURE-----