- From: Al Gilman <asgilman@iamdigex.net>
- Date: Thu, 16 Jan 2003 11:06:14 -0500
- To: "Jim Ley" <jim@jibbering.com>, <www-qa@w3.org>
- Cc: <public-evangelist@w3.org>
At 09:08 AM 2003-01-16, Jim Ley wrote: > >Le jeu 16/01/2003 à 12:17, Tom Gilder a écrit : > >> What about having working groups being required to issue a monthly > >> newsletter stating what they have done in plain English? Requesting > >> feedback on issues? > > > >Being a participant in a WG, I can assure you that the fact that WG have > >to publish a draft every 3 months (as required by W3C Process Document) > >is already a very heavy requirement compared to the resources available > >in WGs. I'm sure that most WG do their best to reply to any issue raised > >in the right forum, to document their issues resolution and to highlight > >their open issues in their draft, but requiring them to have more formal > >communications on all the front is unlikely to happen due to resources > >constraint. > >I agree formal communication with the public is not a reasonable >requirement, however I do feel a public issues list (perhaps with some >issues censored if necessary) published a number of weeks before a draft >moves phases, so the issuer has time to discover if their issue is being >discussed, or has been missed. There is little extra cost in this other >than any censorship required to make the issues list public, rather than >member only. What we need to formalize is the notion of the "opt-in panel" comprising those who took the trouble to contribute comments. There are multiple points, minor review phases, where the people who should have a voice are those who took the trouble to exercise the invitation to voice comments in a closely related earlier phase. This could be reflected in access rights, tracking notifications, etc. The notices or digests of activity should come automatically out of the Bugzilla installation [issue-tracking engine] and be controlled by individual preferences as to immediate notification on individual event vs. weekly or whatever periodic updates. The user can also profile what issues they wish to track. But they have to take the time to get on the reporting-administration site and edit the profile. Al >Jim.
Received on Thursday, 16 January 2003 11:06:23 UTC