"WeekinQA" is a monthly (started bi-weekly, hence the name) summary of the main topics discussed on www-qa@w3.org, the public mailing-list of W3C QA Interest Group and www-qa-wg@w3.org, the public mailing-list of W3C's QA Working Group.
The regular editor for "WeekinQA" is Lynne Rosenthal, NIST, co-chair of the QA Interest Group.
See also the initial calendar and initial requirements for this resource.
Topics discussed at the F2F included: Outreach, the resolution of
Specification Guideline (SpecGL) issues, Test Guideline (TestGL), a proposed
testing task group, and demonstrations of test suites for several W3C
technologies. Many thanks to the KEIO team and Olivier for the meeting
arrangements. Outreach efforts in order to attract new members to the WG as
well as informing members and the public about the WG's Guideline documents
was discussed. For the TestGL, a few key issues regarding the focus,
objectives, and audience of the guideline were addressed. The document will
be restructured to present a strategic view of how to develop good test
suites. The minutes of the meeting is at: http://www.w3.org/QA/2002/10/f2f-minutes
The WG's Issues list has been updated - over 31 SpecGL issues were resolved at the F2F. Much of October's email discussions contributed to the resolutions. The Issues List is at: http://www.w3.org/QA/WG/qawg-issues-html.html
Dimitris Dimitriadis presented a proposal to form a testing task force to help people use the Framework Guidelines (i.e., OpsGL, SpecGL and TestGL). The group would develop tools and provide assistance to W3C WGs and the web community to facilitate the implementation of the Guidelines. A draft charter is being developed. It is hoped that this new task force would attract new participants.
See Thread :
http://lists.w3.org/Archives/Public/www-qa-wg/2002Oct/0019.html
The WG has changed its telecon to a weekly, 1 hour meeting on Mondays, at 11AM (eastern US). Meetings will start on time and a scribe will be named prior to the telcon.
An interesting discussion on the IG list explored the idea of defining pieces of technology as "public interfaces". These public interfaces would be, like in Java, definitions that a WG would commit to maintain in future versions of the specs. If a specification had to supply a list of definitions which will be maintained over versions or slowly deprecated, other specs would know what they can safely refer to and rely on for the latest version. Taking the idea further, W3C might want to keep a registry where spec dependencies are defined. This would allow easy use by various specs and help with backward compatibility.
See Thread:
http://lists.w3.org/Archives/Public/www-qa/2002Oct/0023.html
All meeting minutes are available at: http://www.w3.org/QA/Agenda/