Agenda Process Document Task Force 16 December 2014; Last Telcon of 2014; correcting the date

Correcting the date to 16 December.

The call is on Tuesday, 16 December, 2014 at  14:00-15:00 UTC<http://www.timeanddate.com/worldclock/fixedtime.html?month=08&day=26&year=2014&hour=14&min=00&sec=0&p1=0> (10:00am-11:00am Boston local)
Zakim Bridge +1.617.761.6200<tel:+1.617.761.6200>, conference code 7762 ("PROC")
IRC Channel: #w3process

Last telcon of 2014; Telcons will resume on Tuesday, 6 January 2015

For residents of other (typical) time zones the start times were:
Pacific:  7:00
Eastern US: 10:00
Central Europe: 16:00
Japan: 24:00/0:00 +1
Australia: 1:00 + 1

The purpose of these meetings has been to agree on the resolution of open issues, close them where possible or assign actions to move toward closure.


Agenda:

1.      Review Open Action Items
https://www.w3.org/community/w3process/track/actions/open

2.      Issue-140: The description of the Team in Section 2.2 of the process document is out of date<http://www.w3.org/community/w3process/track/issues/140>
See thread beginning with:
http://lists.w3.org/Archives/Public/public-w3process/2014Nov/0116.html
which has the discussion of the text Chaals proposed for Section 2.2

The open topic is doing the updates to other sections that are implied by the removal of text from section 2.2.
And, the issue of delegation of the CEO's responsibilities, those previously given to the COO and Chair.

3.      Issue-145: Clean up mentions of W3C Chair, COO etc<http://www.w3.org/community/w3process/track/issues/145>
See http://lists.w3.org/Archives/Public/public-w3process/2014Dec/0001.html

4.      Issue-100 Should it be possible to publish a pr before a call for exclusion ends<http://www.w3.org/community/w3process/track/issues/100>
See thread beginning: http://lists.w3.org/Archives/Public/public-w3process/2014Nov/0195.html

5.      Issue-141: Improve Errata management in W3C<http://www.w3.org/community/w3process/track/issues/141>

See thread on Patent Policy FAQ 37 beginning at
https://lists.w3.org/Archives/Member/member-psig/2014OctDec/0154.html

And, there was a private e-mail exchange that seems to have reached the conclusion that since section 7.7.2 Revising a Recommendation says that for errata to become normative they must pass a CR which provides an exclusion opportunity, there is no significant problem if new features accidentally creep into an proposed Edited Recommendation. If they trigger an exclusion, then that can be handled prior to it becoming an Edited Recommendation.

6.      Issue-129 Remove Coordination Groups<http://www.w3.org/community/w3process/track/issues/129>
Discussion with Judy Brewer
Should the Process Document include a discussion of "coordination" (and an escalation path when it does not occur)?

7.      Issue-93: What should the requirements be for specifications produced by more than one WG?<http://www.w3.org/community/w3process/track/issues/93>

Steve Zilles
Chair, Process Document Task Force