ISSUE-148: Consider Liaison when deciding who should review a REC Track document

Consider Liaisons

Consider Liaison when deciding who should review a REC Track document

State:
CLOSED
Product:
Process Document
Raised by:
Steve Zilles
Opened on:
2014-11-17
Description:
It was noted[1] that W3C keeps a list of Liaisons[2] with organizations requesting liaisons with W3C groups and/or activities.
[1] https://www.w3.org/wiki/TPAC2014/SessionIdeas#What_is_Wide_Review_and_How_do_we_achieve_it
[2] http://www.w3.org/2001/11/StdLiaison.html

The text of the first paragraph of Section 7.2.3.1 Wide Review currently reads:

"The requirements for wide review are not precisely defined by the W3C Process. The objective is to ensure that the entire set of stakeholders of the Web community, including the general public, have had adequate notice of the progress of the Working Group and thereby an opportunity to comment on the specification. Before approving transitions, the Director will consider who has been explicitly offered a reasonable opportunity to review the document, who has provided comments, the record of requests to and responses from reviewers, especially groups identified as dependencies in the charter, and seek evidence of clear communication to the general public about appropriate times and which content to review."

To include Liaisons in the final sentence, it is suggested that the phrase, "especially groups identified as dependencies in the charter," be changed to, "especially groups identified as dependencies in the charter or identified as <a href="http://www.w3.org/2001/11/StdLiaison.html">liaisons</a>,"

The "href" refers to the Liaison page that tracks liaison requests made to the W3C.
Related Actions Items:
Related emails:
  1. Summary of Resolutions re Process 2015 (from szilles@adobe.com on 2015-01-13)
  2. Re: w3process-ISSUE-148 (Consider Liaisons): Consider Liaison when deciding who should review a REC Track document [Process Document] (from singer@mac.com on 2014-11-20)
  3. Update on the Process Document Task Force (from szilles@adobe.com on 2014-11-19)
  4. RE: w3process-ISSUE-148 (Consider Liaisons): Consider Liaison when deciding who should review a REC Track document [Process Document] (from szilles@adobe.com on 2014-11-19)
  5. Re: w3process-ISSUE-148 (Consider Liaisons): Consider Liaison when deciding who should review a REC Track document [Process Document] (from singer@mac.com on 2014-11-18)
  6. Re: Process Task Force Telcon on 18 November, 2014 (from jeff@w3.org on 2014-11-18)
  7. Re: Agenda Process Task Force Telcon on 18 November, 2014 (from singer@apple.com on 2014-11-17)
  8. w3process-ISSUE-148 (Consider Liaisons): Consider Liaison when deciding who should review a REC Track document [Process Document] (from sysbot+tracker@w3.org on 2014-11-17)

Related notes:

At it 11/18/2014 Telcon, the Process Document TF resolve to accept the suggested change above.

After the change and the changes made for Issue-144, the paragraph in question would read:

7.2.3.1 Wide Review
The requirements for wide review are not precisely defined by the W3C Process. The objective is to ensure that the entire set of stakeholders of the Web community, including the general public, have had adequate notice of the progress of the Working Group (for example, using public-review-announce@w3.org <mailto:public-review-announce@w3.org>) and were able to actually perform reviews of and provide comments on the specification. A second objective is to encourage groups to request reviews early enough that comments and suggested changes may still be reasonably incorporated in response to the review. Before approving transitions, the Director will consider who has been explicitly offered a reasonable opportunity to review the document, who has provided comments, the record of requests to and responses from reviewers, especially groups identified as dependencies in the charter or identified as <a href="http://www.w3.org/2001/11/StdLiaison.html">liaisons</a>, and seek evidence of clear communication to the general public about appropriate times and which content to review and whether such reviews actually occurred.

Steve Zilles, 10 Jan 2015, 23:23:43

Display change log ATOM feed


David Singer <singer@apple.com>, Chair, Dominique Hazaƫl-Massieux <dom@w3.org>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 148.html,v 1.1 2020/03/09 13:49:30 carcone Exp $