- From: Patrick Curran <Patrick.Curran@Sun.COM>
- Date: Mon, 03 May 2004 07:32:49 -0700
- To: QAWG <www-qa-wg@w3.org>
QA Working Group Teleconference Wednesday, 26-April-2004 -- Scribe: Patrick Curran Attendees: (PC) Patrick Curran (Sun Microsystems) (DD) Dimitris Dimitriadis (Ontologicon) (KD) Karl Dubost (W3C, WG co-chair) (DH) Dominique Hazaël-Massieux (W3C) (LH) Lofton Henderson (CGMO - WG co-chair) (MS) Mark Skall (NIST) (AT) Andrew Thackrah (Open Group) Guest: (DM) David Marston (IBM) Regrets: (MC) Martin Chamberlain (Microsoft) (LR) Lynne Rosenthal (NIST - IG co-chair) (VV) Vanitha Venkatraman (Sun Microsystems) Agenda: http://lists.w3.org/Archives/Public/www-qa-wg/2004Apr/0072.html Previous Telcon Minutes: hhttp://lists.w3.org/Archives/Public/www-qa-wg/2004Apr/0079.html 1.) roll call 11am EDT, membership 2.) routine business - Future telecons [0] (3-may?) QAH and SpecGL Logistics for June f2f - Patrick to circulate logistics CR issues 1-26 circulated for past few weeks now considered closed (no comments received) 3.) QAF 4/29 publication - Titles? - SpecLite update (LR) - TestLite update (PC) - QAH update (LH) - glossary update (MS/KD) - QAH publication permission (AI to ?) - BH comments on "you" We aren't going to be able to publish next week. Spec is partial, Test is only in outline form. Should we publish even if we are at different levels of completion? Patrick: how about publishing handbook only, and not the others? Lofton: or, publish all, even if incomplete? Goal is to show people what we will publish when we're complete - we need to show we're making progress Dom: an outline with links showing overall structure would be OK Lofton: is it OK not to be fully synchronized? Dom: It's OK, so long as we don't go to last call unsynchronized Patrick: We could give ourselves a few more weeks until things are in better shape Dom: We could publish after the moratorium - May 25 Lofton: plan for publication on 1st day after moratorium, and go for aggressive feedback Try to stick to original deadline: relatively complete introduction and outline this week? Mark: no progress on glossary this week Lofton: AI to ask Karl to request publication permission 4.) TestLite draft review -- Ref: [2] 5.) QAH draft review - third editors draft [3] - flagged embedded issues [3] Title: just "QA Handbook" Resolution on "fuzzy phrases" outlined in pink - take this to email Intro/Roadmap: Five stories - should they be left here, or distributed throughout the document? Dom/David: would prefer to distribute if possible, but do we have too many here? Lofton: would link from here to the relevant sections in the document Consensus: leave them here, seek feedback Day to day operations: name the actual team in the story or keep it anonymous? Mark: as a matter of policy should we do so? This could cause issues? Patrick: beware putting words into peoples' mouths Agreed: keep this anonymous QA Process Document: should we point to examples as an alternative to the QAPD? Consensus: no - template should be the union of good practice Sections 3.2 and 3.3: most of this stuff belongs in Test Guidelines - simply point to it Agreed: don't duplicate test Licensing & Branding: should we point to a separate "hints and tips" document? No - just try to summarize the issues here. Agreed: keep references to JR discussion, not that this is still ongoing. Acquiring test materials: needs work. Not yet really a "story". Lofton will flesh this out TM Quality Assessment Checklist/Template: take this discussion to email Transfer checklist discussion: should we keep this? Consensus: yes - such checklists are very useful Appendix: has been rewritten; suggestion - point to these sections from the introduction 6.) Adjourn 7.) Overflow (12-12:30): available.
Received on Monday, 3 May 2004 10:32:35 UTC