ISSUE-144: Chairs are asking for clarification for Wide Review

Wide Review

Chairs are asking for clarification for Wide Review

State:
OPEN
Product:
Process Document
Raised by:
Jeff Jaffe
Opened on:
2014-10-02
Description:
As Working Groups are getting experience with Wide Review they are asking for clarifications. Some ideas are: having a public mailing list for wide review; making it clear whose responsibility it is to figure out wide review (is it the chair, is it the WG)? We should iterate on this important point and get it done in Process 2015.
Related Actions Items:
Related emails:
  1. Summary of Resolutions re Process 2015 (from szilles@adobe.com on 2015-01-13)
  2. Re: Agenda Process Document Task Force 25 November 2014 (from jeff@w3.org on 2014-11-25)
  3. Agenda Process Document Task Force 25 November 2014 (from szilles@adobe.com on 2014-11-24)
  4. Update on the Process Document Task Force (from szilles@adobe.com on 2014-11-19)
  5. Re: Issue-144 Suggested updates to clarify Wide Review in Process2014 (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. Re: Process Task Force Telcon on 18 November, 2014 (from jeff@w3.org on 2014-11-17)
  9. RE: Process Task Force Telcon on 18 November, 2014 (from szilles@adobe.com on 2014-11-17)
  10. Re: Process Task Force Telcon on 18 November, 2014 (from chaals@yandex-team.ru on 2014-11-17)
  11. Re: Issue-144 Suggested updates to clarify Wide Review in Process2014 (from jeff@w3.org on 2014-11-17)
  12. RE: Issue-144 Suggested updates to clarify Wide Review in Process2014 (from szilles@adobe.com on 2014-11-17)
  13. Re: Issue-144 Suggested updates to clarify Wide Review in Process2014 (from jeff@w3.org on 2014-11-16)
  14. Issue-144 Suggested updates to clarify Wide Review in Process2014 (from szilles@adobe.com on 2014-11-15)
  15. Re: Agenda Process Task Force Telcon on 11 November, 2014 (from singer@apple.com on 2014-11-11)
  16. Re: Agenda Process Task Force Telcon on 21 October (from jay@kishigami.net on 2014-10-22)
  17. Re: Agenda Process Task Force Telcon on 21 October (from singer@apple.com on 2014-10-21)
  18. Re: Agenda Process Task Force Telcon on 21 October (from art.barstow@gmail.com on 2014-10-20)
  19. Re: Agenda Process Task Force Telcon on 14 October (from singer@apple.com on 2014-10-14)
  20. Re: Agenda Process Task Force Telcon on 14 October (from chaals@yandex-team.ru on 2014-10-14)
  21. Re: CfC: create a public list to announce new publications; deadline Oct 15 (from singer@apple.com on 2014-10-08)
  22. Re: CfC: create a public list to announce new publications; deadline Oct 15 (from chaals@yandex-team.ru on 2014-10-08)
  23. Re: CfC: create a public list to announce new publications; deadline Oct 15 (from jeff@w3.org on 2014-10-08)
  24. w3process-ISSUE-144 (Wide Review): Chairs are asking for clarification for Wide Review [Process Document] (from sysbot+tracker@w3.org on 2014-10-02)

Related notes:

[SteveZ]: Chairs are asking for clarification for Wide Review<http://www.w3.org/community/w3process/track/issues/144>

25 Nov 2014, 15:50:35

At its 11/18/2014 Telcon, The Process Document TF approved the following changes to the Process2014 text:
first the existing text:
===============
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 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.
=============

Then the adopted changes:

1. Change the following phrase in the first sentence of the paragraph, "and thereby an opportunity to comment on the specification" TO "and were able to actually perform reviews of and provide comments on the specification"

2. Change the final phrase of the second sentence of the paragraph, "and seek evidence of clear communication to the general public about appropriate times and which content to review" TO "and seek evidence of clear communication to the general public about appropriate times and which content to review and whether such reviews actually occurred"

4. Following the first sentence, ending with "opportunity to comment on the specification", add the following sentence, "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."

5. Modifying the first sentence phrase, "have had adequate notice of the progress of the Working Group and ..." TO "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 ..."

The item labeled 3. in the proposed resolution
http://lists.w3.org/Archives/Public/public-w3process/2014Nov/0130.html
was neither adopted nor excluded. It is still under discussion.

Steve Zilles, 10 Jan 2015, 21:06:12

After the above changes, 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, 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, 21:23:21

After the above changes, 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, 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, 21:23:33

Chaals asks "Hmm. I think we should consider how this plays out in practice - which is less than wonderful."

David Singer, 28 Mar 2017, 19:00:28

Moved back to Open for further consideration

David Singer, 28 Mar 2017, 19:17:49

Transferred to https://github.com/w3c/w3process/issues/7

David Singer, 21 Apr 2017, 18:28:41

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: index.php,v 1.326 2018/10/13 17:29:51 vivien Exp $