Re: Agenda for January 29, 2014

Apologies to all, I have a conflict tomorrow and won't be able to attend
the weekly call.

Cheers,
Sid

On 01/28/2014 11:33 AM, Ninja Marnau wrote:
> This week, the co-chairs will talk about the advancement of the TPE spec
> to Last Call and the steps the group needs to take.
> We have narrowed down the remaining ISSUES and will probably proceed to
> Call for Objections within the next two weeks. Therefore, the co-chairs
> will start to take up ISSUES from the Compliance spec in February.
> 
> Regards,
> Ninja
> 
> ----------------------------------
> 
> 1. Confirmation of scribe. Volunteers welcome!
> 
> 2. Offline-caller-identification (see end for instructions)
> 
> ----------------------------------
> --- Issues for this Call ---
> 
> Note: See more info at the end for details.
> 
> ISSUE-217 and ISSUE-228: Definition of network interaction
> https://www.w3.org/2002/09/wbs/49311/tpwg-interact-217/results
> January 29: M7 (announcement): Results are announced
> 
> Announcement: Getting closer to Last Call
> http://www.w3.org/2005/10/Process-20051014/tr.html#last-call
> 
> ISSUE-240: Do we need to define context?
> https://www.w3.org/2011/tracking-protection/track/issues/240
> http://www.w3.org/wiki/Privacy/TPWG/Proposals_on_the_definition_of_context
> January 29: M2 (discussion): List of change proposals is frozen;
> Discussion whether clear consensus emerges for one change proposal
> February 5: M3 (announcement): Call for objections to validate /
> determine consensus
> 
> ISSUE-241: Distinguish elements for site-internal use and elements that
> can be re-used by others (1/3)
> https://www.w3.org/2011/tracking-protection/track/issues/241
> https://www.w3.org/wiki/Privacy/TPWG/Proposals_on_elements_for_1and3_party_use
> 
> January 29: M1 (discussion): Initial change proposals have been
> submitted; Discussion on change proposals; Call for final list of change
> proposals
> February 5: M2 (discussion): List of change proposals is frozen;
> Discussion whether clear consensus emerges for one change proposal
> 
> AoB
> 
> Reminder for open Call for Objection:
> 
> ISSUE-153: Limitations for add-ons
> https://www.w3.org/2002/09/wbs/49311/tpwg-addons-153/
> Deadline - January 29
> 
> ================ Summary Documentation on Resolving ISSUES
> =================
> 
> PHASES to resolve issues:
> M0 (announcement): Initial call for change proposals; All change
> proposals should be drafted
> M1 (discussion): Initial change proposals have been submitted;
> Discussion on change proposals; Call for final list of change proposals
> M2 (discussion): List of change proposals is frozen; Discussion whether
> clear consensus emerges for one change proposal
> M3 (announcement): Call for objections to validate / determine consensus
> M5 (deadline): Deadline for inputs to call for objections (2 weeks after
> M3); Analysis starts
> M7 (announcement): Results are announced
> 
> STATUS of the ISSUES:
> - OPEN During phases M0, M1, M2
> - PENDING REVIEW: During phases M3, M5
> - CLOSED after M7
> All other issues are RAISED.
> -----
> ================ Infrastructure =================
> 
> Zakim teleconference bridge:
> VoIP: sip:zakim@voip.w3.org
> Phone +1.617.761.6200 passcode TRACK (87225)
> IRC Chat: irc.w3.org<http://irc.w3.org/>, port 6665, #dnt
> 
> OFFLINE caller identification:
> If you intend to join the phone call, you must either associate your
> phone number with your IRC username once you've joined the call
> (command: "Zakim, [ID] is [name]" e.g., "Zakim, ??P19 is schunter" in my
> case), or let Nick know your phone number ahead of time. If you are not
> comfortable with the Zakim IRC syntax for associating your phone number,
> please email your name and phone number to
> npdoty@w3.org<mailto:npdoty@w3.org>. We want to reduce (in fact,
> eliminate) the time spent on the call identifying phone numbers. Note
> that if your number is not identified and you do not respond to
> off-the-phone reminders via IRC, you will be dropped from the call.
> 
>

Received on Tuesday, 28 January 2014 22:23:59 UTC