Re: Use Bugzilla to Track Changes

On 06/20/2012 08:49 PM, Li Li wrote:
>
> 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].
>

There have been a few suggestions along those lines.
The current split (which is a draft procedure) is described here:

http://www.w3.org/2011/04/webrtc/wiki/Tracker_usage_guidelines


Note that this is NOT the one you suggest; in particular, experience in 
certain other groups has led to the realization that sometimes it is not 
good to have just anyone raise bugs - it can quickly lead to both an 
overload of bugs and reopening of old issues (whether intended or not).

> 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
>