W3C home > Mailing lists > Public > public-w3process@w3.org > February 2014

Re: Agenda for Chapter 7 Task Force Telcon, 8AM Pacific, 11AM Eastern, 3 February

From: Charles McCathie Nevile <chaals@yandex-team.ru>
Date: Mon, 03 Feb 2014 15:00:52 +0400
To: "'public-w3process@w3.org'" <public-w3process@w3.org>, "Stephen Zilles" <szilles@adobe.com>, "Charles McCathie Nevile" <chaals@yandex-team.ru>
Cc: "Michael Champion (Michael.Champion@microsoft.com)" <Michael.Champion@microsoft.com>
Message-ID: <op.xapcvqjby3oazb@5.255.232.42-red.dhcp.yndx.net>
On Mon, 03 Feb 2014 12:23:35 +0400, Charles McCathie Nevile  
<chaals@yandex-team.ru> wrote:

> On Mon, 03 Feb 2014 01:47:21 +0400, Stephen Zilles <szilles@adobe.com>  
> wrote:
>
>> Chapter 7 Task Force Telcon, 8AM Pacific, 11AM Eastern, 3 February
>>
>> Zakim, 24277
>>
>> IRC Channel: #w3process
>>
>>
>>
>> Current version of Chapter 7 dated 22 Jan 2014 is at:
>>
>>   https://dvcs.w3.org/hg/AB/raw-file/fbff0fa7f073/tr.html
>
> New version posted with updates for most resolutions already taken...

Err, except a note covering the fact that groups may have additional  
working processes, e.g. defined by their charter. (Issue 83). I'll put  
that in now for the next Editor's draft.

cheers

> https://dvcs.w3.org/hg/AB/raw-file/default/tr.html
>
> cheers
>
>> Agenda:
>>
>> 1.       Complete closure of issues 56-58, 67, 70, 72, 81
>>
>> http://www.w3.org/community/w3process/track/issues/raised
>>
>> https://www.w3.org/community/w3process/track/issues/closed
>>
>> 2.       Discuss Issues 6, 69, 79, 80, 83 and 84
>> https://www.w3.org/community/w3process/track/issues/6
>>   Suggested Resolution: POSTPONE as out of scope for this version.
>> https://www.w3.org/community/w3process/track/issues/69
>>   Suggested Resolution: CLOSE: Independent SDOs do not review their  
>> proposed Process changes with other SDOs and the Chapter 7 changes do  
>> not reduce Review opportunities.
>> https://www.w3.org/community/w3process/track/issues/79
>>   Suggested Resolution: PENDINGREVIEW: specifically allow status  
>> updates that describe reasons for not re-publishing a document
>>
>> https://www.w3.org/community/w3process/track/issues/80
>>   Suggested Resolution: Clarify that the W3C Team has the ultimate  
>> responsibility for declaring Rec Track work unfinished and publishing a  
>> W3C Note with what had been done.
>> https://www.w3.org/community/w3process/track/issues/83
>>
>> The issue here is not whether we want to do this, but the change would  
>> be to a different section of the Process document than Chapter 7. It  
>> was suggested that we put a note into Chapter 7 describing the intent.
>> https://www.w3.org/community/w3process/track/issues/84
>>   Suggested Resolution: CLOSED: accepted with PR having a much smaller  
>> role that previously.
>>
>> http://www.w3.org/community/w3process/track/issues/raised
>>
>> https://www.w3.org/community/w3process/track/issues/open
>>
>> 3.       Review the Process within CR.
>>
>> http://www.w3.org/community/w3process/track/issues/59
>>
>> https://www.w3.org/community/w3process/track/issues/77
>>
>> Steve Zilles
>
>


-- 
Charles McCathie Nevile - Consultant (web standards) CTO Office, Yandex
       chaals@yandex-team.ru         Find more at http://yandex.com
Received on Monday, 3 February 2014 11:01:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:51:17 UTC