DRAFT: Process Document to contact the QA WG

Per long standing AI  A-2002-03-1-9, I had the ownership of 
developping a Process to help other WG to contact the QA WG and to 
define an appropriate mechanism from the QA WG.

Comments are welcome it's a small draft right now.

* WG Action:

A WG has a QA issue related to spec writing, process, TS, etc. The WG 
must assign an Action Item to the QA Contact for this particular WG. 
The QA Contact is the person who will be the liaison for any 
relationship with the QA WG.

The QA Contact send an email to the www-qa-wg@w3.org mailing list 
with a title starting with [XXX] where XXX is the name of the WG and 
an appropriate subject.

* Acknowledgement:

The next QA teleconf following the reception of this mail is the 
start of the issue tracking. The chair must put this issue as 
acknowledged and received at this teleconf. So the members of the QA 
WG will be aware of it, and the issue will be entered on the agenda.

* Resolution:

The Issue will be solved at this teleconf if it's possible. If the 
schedule is too tight and requires a longer discussion, we may 
schedule a new teleconference to solve it. It may occured that the 
issue needs more discussion to be solved or that the information 
given is not enough to find a solution. In this case, The QA WG 
assigned an action item on a QA WG member to discuss the issue with 
the Team contact and get more information.


* Answer:

When the issue is solved, the QA WG write a proposal, an answer which 
is sent to the QA Contact and to the QA WG mailing-list.



Caveats of this process:
	- It leaves no space for private request. A WG that will wish 
to not publicize a QA issue.
	- Buffer Overflow: when too many issues are arriving at the 
same time. Let say that 5 WGs raise issues at the same time.
	- W3C Team issue: When a charter is in development, when a 
W3C Team contact has a QA problems with its WG.


-- 
Karl Dubost / W3C - Conformance Manager
           http://www.w3.org/QA/

      --- Be Strict To Be Cool! ---

Received on Wednesday, 26 June 2002 16:29:30 UTC