Hey Gareth,
While I understand this whole mail was meant to enforce good practices
(and that's good!), I think it went out quite wrong and agressive, and
that's quite unnecessary.
Don't forget we have people from different languages and cultures in
this project, and sometimes misunderstandings ca
Le 28/03/2014 04:38, Fabrice Desré a écrit :
> On 03/26/2014 06:09 AM, Gareth Aye wrote:
>> When we answer these
>> questions for ourselves, we are /being open/ when we mirror our answers
>> to bugzilla.
>>
>> - Is this a good idea?
>> - What problem does it solve (and for whom)?
>> - Is it high p
On 03/26/2014 06:09 AM, Gareth Aye wrote:
> When we answer these
> questions for ourselves, we are /being open/ when we mirror our answers
> to bugzilla.
>
> - Is this a good idea?
> - What problem does it solve (and for whom)?
> - Is it high priority?
I strongly disagree on this one. Any issue,
Evidently we disagree. IMHO the communication and openness we achieved in
that bug leaves a lot to be desired.
> One thing made me totally didn't understand is that according to your
> own comments, you *did* repeatedly complain one error
> that caused the patch broken, even after the patch got up
I don't think what we discussed are totally about what you mentioned.
Although I definitely agree what you want mentioned about
communication and questions you've listed.
One thing made me totally didn't understand is that according to your
own comments, you *did* repeatedly complain one error
tha
Thanks Gareth, for bringing this up -- in a sort of "recursive" form it
seems that you communicated very well the bug about the bug process,
with a good use case too. After reading your "questions template", at
the end, it reminded me on how Bugzilla teach beginners with a basic
text templates. A s
Thanks Gareth, I will take this to the team tomorrow.
On Wed, Mar 26, 2014 at 9:09 PM, Gareth Aye
wrote:
> Hi Gaia,
>
> tl;dr Please make a habit of explaining what the high-level goals of a bug
> are when you file one. If you do one thing well as a software developer,
> please make it communicat
Hi Gaia,
tl;dr Please make a habit of explaining what the high-level goals of a bug
are when you file one. If you do one thing well as a software developer,
please make it communication.
/* The longer version */
Sometimes our software doesn't work like we would like for it to. When this
happens
