[meeting] notes from 2004-09-28

Present: Bjoern, Nick, Ville, Olivier, (Jim)

* Action Items review and discussion

- The potential "SVG icons" are being reviewed. Bjoern notes that there 
are still issues with IE [1] with the png's generated from them, and 
suggests merging the SVG style with the one at [2], which uses the 
"proper" red and similar 3D button look.

[1] http://lists.w3.org/Archives/Member/w3c-archive/2004Sep/0107.html 
(member -only)
[2] http://lists.w3.org/Archives/Public/www-validator/2001Jul/0208.html

- The AI on adding one address into the the Error Document for (rare) 
cases of 500 server error was, after discussion, amended to: change the 
document to point to our documentation, bugzilla, etc.


* Understanding and planning 0.7.0

Our mid-term goal is to replace most of the check code with smaller, 
task-based modules (for which work has already started), but before we 
can actively do that, our short-term goal is the release of 0.7.0.

The progress for 0.7.0 is mainly tracked in a bugzilla meta-bug[3] 
depending on a flurry of bugs and RFEs. Discussion on which 
could/should be postponed is still going on (Nick is supposed to send 
his take on the issue ASAP now), while many of the bugs are getting 
closed.

[3] http://www.w3.org/Bugs/Public/show_bug.cgi?id=856

Discussion on this topic lead to three others...


* Usage of Bugzilla

Our usage of bugzilla is rather particular, in that we are using the 
qa-contact field as a way to broadcast information on the bugs being 
discussed, and using the "owner" as a default-owner-plus-qa-contact. 
This sometimes makes it difficult to know whether an ASSIGNED issue is 
being worked on or only acknowledged by the "owner". It is advised to 
at least drop a note to the owner before starting work on their issues.

Also a reminder that no issue is "obvious" enough to not be included in 
bugzilla.


* Testing HEAD

On top of the list of issues at #856 [3], our current HEAD code [4] 
needs more testing as there are certainly some post-merging bugs we 
haven't found out yet. "homework" for everyone is to try and use this 
instance instead of the production one for day-to-day validation, and 
input into bugzilla whatever issue is encountered.

[4] http://qa-dev.w3.org/wmvs/HEAD/


* Modified DTDs

Related to http://www.w3.org/Bugs/Public/show_bug.cgi?id=297 : we have 
been using "custom" DTDs (in particular for HTML2) as workarounds for 
OpenSP limitations. With the recent development of OpenSP it might be 
possible to get back to using standard DTDs. It was not, however, clear 
*which* SP issue we are going around with these hacks, as this is a 
very historical change.

Ville and Nick are in charge of sorting this out and reporting.


Next meeting Oct. 12th.
-- 
olivier