W3C home > Mailing lists > Public > public-webrtc@w3.org > June 2012

Use Bugzilla to Track Changes

From: Li Li <Li.NJ.Li@huawei.com>
Date: Wed, 20 Jun 2012 18:49:34 +0000
To: "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <B60F8F444AAC9C49A9EF0D12D05E0942216A150B@szxeml535-mbx.china.huawei.com>
Since we have a FPWD [1],  I hope we can treat any changes to it, either feature improvements or editorial fixes, as a process of fixing bugs through the Bugzilla database [2].

The process looks like this:
Request: any member who wants to make a change to [1] (or an editor's version)  first fires a bug with or without a proposal in [2].
Action: the bug will be discussed by the WG to reach an action, such as "Accept" or  "Close With No Action".
Resolution: the proposals to an accepted bug can be discussed in the public mailing list. When a consensus is reached, the bug is resolved and closed, with a link to the proposal.
Revision: the accepted resolution can be incorporated into the next editor's edition whose "summary of changes" section links back to the bugs.

Currently, the Bugzilla database is underused as there are only 5 bugs in it. These bugs do not cover all the current discussion topics in the public mailing list.
I hope this process improves our ability to track problems and control the scope of discussions.

I understand it might a bit late to change our process. I wonder if this approach has been considered before and if there were any reasons against it.

Thanks.

Li

[1] http://www.w3.org/TR/webrtc/
[2] https://www.w3.org/Bugs/Public/describecomponents.cgi?product=WebRTC%20Working%20Group
Received on Wednesday, 20 June 2012 18:55:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 20 June 2012 18:55:52 GMT