Re: Tracking comments and issues (Was: Web Audio API is now ready for publication)

James, that would be great, thank you for volunteering.

I am sure the group will be able to help you identify issues raised. And 
don't hesitate to send me mail if you have questions about the tracking 
tool.

http://www.w3.org/2011/audio/track/issues/?sort=status


Would you like to give it a first go with the issue on numberOfOutputs 
in the RealtimeAnalyserNode ?
http://lists.w3.org/Archives/Public/public-audio/2012JanMar/thread.html#msg450

Thanks,
Olivier



On 22/03/2012 08:18, Wei, James wrote:
> I am willing to do it for Web Audio API if some guide provided at the beginning. you can point out that something need to be documented in the tracking system and then I can do the remaining stuffs.
>
> Best Regards
>
> James
>
>
>
> -----Original Message-----
> From: olivier Thereaux [mailto:olivier.thereaux@bbc.co.uk]
> Sent: Thursday, March 22, 2012 3:41 PM
> To: Audio Working Group
> Cc: Thierry MICHEL; Raymond Toy
> Subject: Tracking comments and issues (Was: Web Audio API is now ready for publication)
>
>
> On 21 Mar 2012, at 18:14, Raymond Toy wrote:
>
>> On Wed, Mar 21, 2012 at 10:32 AM, Thierry MICHEL<tmichel@w3.org>  wrote:
>>
>>> How do we track all the comments sent about our specification.
>>> Is it the editor who tracks those ?
>>> Any other mean ?
>> Maybe they can be tracked as audio issues using the audio issue tracker?
>
> Thierry, Ray, thanks for bringing this up.
>
> I don't think we (chairs) should decide and impose this, but I can give a few elements of answer:
>
> Where: We should use our issues tracker. (I don't think we need to use bugzilla as e.g the HTML5 group does)
> http://www.w3.org/2011/audio/track/issues/?sort=status
>
> What: What needs to happen is relatively simple: whenever a new comment is sent to the list, the group records a new issue if the issue raised is new, or adds the message to the record of an existing issue if appropriate. The group acknowledges the comment (very important!) and the conversation continues on the list, "tagged" with the issue. When the issue reaches resolution, people who are known to have participated to the issue are informed of the resolution.
>
> Who: it is up to us to decide who is in charge. In some groups the editor(s) of the specification take care of that. In the case of the web audio API, we have only one editor and I think it would be a mistake to give Chris too much work by adding the tracking of issues to his burden.
>
> So we have two choices: either the group as a whole does it, or one person becomes the warden of issues (in effect, a co-editor of the specification). Any volunteer?
>
> Olivier
>

-- 
Olivier Thereaux
BBC Internet Research & Future Services