Re: [Audacity-quality] [Audacity-devel] Handling code issues and library/build policy discussions on bugzilla

[Vaughan J. <va...@au...>]

On 4/20/2011 8:38 PM, Gale Andrews wrote:
> [...]
>>>> On this bug, I thought only Leland's answer really resolved it. I obviously
>>>> don't know what Ed was driving at, and you don't either, 
>>[...]
>>
>>>> so that suggests
>>>> to me it may not be safe to resolve at that point. 
>>
>> In two consecutive sentences, you state Leland's answer resolved it, but
>> that it may not be safe to resolve.
> 
> Sorry if it was unclear, but the point at which I thought it was not
> safe to resolve meant the point at which James resolved it (on the 
> stated grounds there was no explanation of the problem). 

I read it as present tense, as it was "may not be" rather than "may not
have been".



>[...]
>  >From what Ed said about having been asked to not post to -devel or
>> -quality, or feedback@, he apparently thinks Bugzilla is where he should
>> have discussions about things he doesn't understand. James is totally
>> right that it is inappropriate.
> 
> Of course that would be inappropriate. Ed can speak for himself, but I
> believe he "thought" he knew what he was talking about initially. I
> don't think he was posting to bugzilla purely because he feels
> unwelcome on the mailing lists. 

At http://bugzilla.audacityteam.org/show_bug.cgi?id=374#c4, he wrote
"I've already been asked to refrain from posting on -quality and -dev;
when I report bugs to @feedback I am asked to put them here instead."


> 
> I have encouraged him to post to bugzilla rather than feedback@ if he
> is sure there is a describable problem, but I thought he understood 
> code and policy issues were better placed on -devel. If it had been 
> clearer that the best place to start reports about the code was -devel,
> I don't think he would have posted this to bugzilla. 
> 

Apparently not the case. He thinks he should never post to -devel. Will
discuss this with him off list.

- V