W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2004

New Bug Tracking Procedure

From: Gregg Vanderheiden <gv@trace.wisc.edu>
Date: Wed, 7 Apr 2004 13:17:21 -0500
Message-Id: <200404071817.i37IHLML014925@jalopy.cae.wisc.edu>
To: <w3c-wai-gl@w3.org>
 

We are currently having trouble accurately tracking all of the bugs and
comments made to the list.  As we get closer to the end, it becomes ever
more important to capture and clear bugs.  

 

Currently, one of the chairs, editors or staff contact has gone through the
comments and tried to capture each bug in a succinct way to insert into
Bugzilla (our bug tracking system) which can be found at [insert bugzilla
URL here].

 

This takes a lot of work and the bugs or issues are not always captured.  

 

To facilitate the process we are asking that everyone who would like to have
their comments captured in Bugzilla please help out by doing the following. 

 

1.	If you have a new issue which you would like to have tracked and
resolved by the group, please start your email with a two to four sentence
summary of the issue with the title "New Bugzilla Issue".  

 

You may then continue to elaborate as much as you would like about the issue
in the rest of the email.  

 

2.	If you are making a comment that you would like to be registered
against an issue, then please put a succinct few sentence summary at the top
of your email with the label "Bugzilla Comment".  You do not have to make
reference to the specific issue that it is a comment to since we should be
able to determine that from the subject of the email.  If you re-label the
subject of the email, then please note the old subject. [also - if it is
already in bugzilla and you know its number - please continue to include
that in the subject line]

 

We will then be grabbing these issues along with a link back to the full
email and putting them into Bugzilla.  

An example of both a Bugzilla issue and comment are shown below.

 

We know that this is extra effort and may seem a cramp to one's freestyle
communication.  However, feel free to still use any form of presentation
that you would like to for the bulk of your message.  If you don't have the
time or ability to create a short synopsis of your issue, imagine how
difficult it is for us to try and do this for everyone's.  It just doesn't
happen. 

 

Thanks much,

 

Gregg

P.S.  This policy is only being used by people who are members of our group.
This does not apply to comments received on the public comment list where we
continue to review and create summaries ourselves.

 

EXAMPLES

Below is an example of how the issue about our epilepsy item might have been
raised and commented on.  These would be the top of two different postings.


 

--------------  

 

New Bugzilla Comment

Currently our guideline regarding epilepsy talks about avoiding any content
which flickers within a certain frequency.  This is a problem since a screen
which has four pixels blinking is not at all provocative and yet would be
forbidden.  Also, it doesn't say whether two flicks is too much flashing or
whether 10 seconds is needed or what.

 

------------ 

 

Bugzilla Comment  

Good points. Suggest that we do something based on English rules which are
much more precise and much more closely related to what is actually
provocative.  Trace is working on a new tool which is based on the English
rules.  We will be meeting with Dr. Harding soon who is probably the world's
leading expert on this.  We will post something back to the list soon.

 

 ------------  

 

Bugzilla Comment  [Issue 342]

We should also consider the pattern issues around epilepsy.

 

 

 
Received on Wednesday, 7 April 2004 14:18:58 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:29 GMT