W3C home > Mailing lists > Public > public-media-capture@w3.org > February 2012

Re: Tracking issues for getUserMedia

From: Harald Alvestrand <harald@alvestrand.no>
Date: Thu, 09 Feb 2012 10:51:46 -0800
Message-ID: <4F3415C2.4040102@alvestrand.no>
To: Dominique Hazael-Massieux <dom@w3.org>
CC: Anant Narayanan <anant@mozilla.com>, public-media-capture@w3.org
Thanks for the outline of the possibilities.
Tracking in the document is obviously easiest when the editor has the 
issue, but might be impractical if others want to update it.

Are there any issues with DAP members accessing either the webrtc issue 
tracker or the webrtc Bugzilla component?

On 02/09/2012 09:21 AM, Dominique Hazael-Massieux wrote:
> Hi Anant,
> We discussed on the call how to collect the issues that you have
> identified for the getUserMedia API.
> I think you have 3 options available; I don't have a strong opinion
> toward which you should use — maybe the chairs do, though?
> 1. The simplest option is to document issues in the document itself; I
> think ReSpec.js recognizes class="issue" and highlights issues in a
> specific manner in the draft; that allows to document the issue close to
> the part of the document they relate to, but makes a bit harder to track
> discussion pertaining to a given issue
> 2. You can create issues in the WebRTC tracker tool, either via the Web
> interface: http://www.w3.org/2011/04/webrtc/track/issues/new
> or by typing "ISSUE: foo bar" on the #webrtc channel; then discussions
> on a given issue can be tracked in email by inserting the name of the
> issue (e.g. ISSUE-1) in any mail that relates to the said issue
> 3. or we could create a new component in Bugzilla, and make it so that
> any changes to a bug for that component be sent to this list
> Dom
Received on Thursday, 9 February 2012 18:52:16 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:26:08 UTC