- From: Ninja Marnau <ninja@w3.org>
- Date: Tue, 11 Feb 2014 21:47:24 +0100
- To: John Simpson <john@consumerwatchdog.org>
- CC: "public-tracking@w3.org (public-tracking@w3.org)" <public-tracking@w3.org>
John, sorry, if my email was ambiguous. We will have the usual Working Group call tomorrow. Starting from _next week_, we will have the break. Ninja Am 11.02.14 21:15, schrieb John Simpson: > Hi Ninja, > > Sorry, not following this. Does this mean no call tomorrow or that the break is after tomorrow's call? > > Thanks, > John > > > On Feb 11, 2014, at 12:08 PM, Ninja Marnau <ninja@w3.org> wrote: > >> ---------------------------------- >> >> 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-151: UA requirement to handle exceptions >> https://www.w3.org/2002/09/wbs/49311/tpwg-exception-151/results >> February 12: M7 (announcement): Results are announced >> >> ISSUE-153: Limitations for add-ons >> https://www.w3.org/2002/09/wbs/49311/tpwg-addons-153/results >> February 12: M7 (announcement): Results are announced >> >> 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 >> February 12: M3 (announcement): Call for objections to validate / determine consensus >> February 26: M5 (deadline): Deadline for inputs to call for objections (2 weeks after M3); Analysis starts >> >> 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 >> February 12: M3 (announcement): Call for objections to validate / determine consensus >> February 26: M5 (deadline): Deadline for inputs to call for objections (2 weeks after M3); Analysis starts >> >> Announcement: >> We will take a break from the weekly calls (but not from our work) until March 12 to finalize and review the TPE draft for Last Call. >> After the break, we plan to take up the work on Tracking Compliance and Scope again. >> >> AoB >> >> ================ 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 >> >> ================ 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, 11 February 2014 20:47:52 UTC