W3C home > Mailing lists > Public > public-ws-chor@w3.org > December 2003

Fwd: Issues Process

From: Steve Ross-Talbot <steve@enigmatec.net>
Date: Wed, 17 Dec 2003 10:38:36 +0000
To: public-ws-chor@w3.org
Message-Id: <2BB06D96-307D-11D8-9FA4-000393D13C9A@enigmatec.net>
The issues process to be used by WS-CHOR


Begin forwarded message:

> Resent-From: member-ws-chor@w3.org
> From: "Martin Chapman" <martin.chapman@oracle.com>
> Date: 15 July 2003 16:33:25 BST
> To: <member-ws-chor@w3.org>
> Subject: Issues Process
>
>
>
> As per my action point, here is a brief description of how I propose  
> to use
> bugzilla to manage issues within the WG.
>
> W3C's Bugzilla can be reached at http://www.w3.org/Bugs
>
> 1. As issues are raised they are recorded into bugzilla by either the  
> chairs
> or the issues editor.
> 2. The issue gets categorized, called a component in bugzilla. It is  
> up to
> the issues editor to ensure
>    each issue is placed into a category.  If one does not seem to be
> appropriate, the chairs will create a new component.
> 3. The issues editor performs an initial screen, completes those that  
> are
> not worth pursuing (see step 5) and seeks owners for
>    each remaining issue.
> 4. Owners will be actioned by the chairs to come up with proposals to
> resolve the issue.
> 5. The work group considers each proposal and agrees/disagrees. If  
> there is
> disagreement, the owner must work on a new resolution.
> 4. Upon an agreed completion of an Issue, the Owner marks the status as
> closed, and provides one of the following resolutions:
> 	FIXED: Issue accepted and resolution agreed/implemented.
> 	INVALID: Not a well formed issue or not appropriate
> 	DUPLICATE: Same as an existing issue.
>
> Bugzilla should not be used for discussing the issue. The normal email  
> lists
> should be used for that purpose, and when appropriate
> links to the mail archive should be made from the issue in bugzilla. In
> dealing with issues from external sources, for which the W3C
> has a defined process [1], the issue in bugzilla should reference all
> communication with the external party.
>
> I'm sure there are some holes in this, so I look forward to your  
> comments.
>
> Martin.
>
> [1]  
> http://www.w3.org/2003/06/Process-20030618/policies.html#formal- 
> address
>
>
>
> _________________________________________________________________
> Martin Chapman                                 500 Oracle Parkway
> Consulting Member of Technical Staff           Ms 4op990
> Oracle                                         Redwood Shores,
> P: +1 650 506 6941                             CA 94065
> e: martin.chapman@oracle.com                   USA
>
> This email is confidential and may be protected by legal privilege. If  
> you are not the intended recipient,  please do not copy or disclose  
> its content but  delete the email and contact the sender immediately.  
> Whilst we run antivirus software on all internet emails we are not  
> liable for any loss or damage. The recipient is advised to run their  
> own antivirus software.
>
Received on Wednesday, 17 December 2003 05:39:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 01:00:46 GMT