Re: Agenda for the Sept 11 call (V01)

It's ISSUE-206 against compliance-june, as noted on the Wiki page that you cited.

Thomas Roessler, W3C <tlr@w3.org> (@roessler)




On 2013-09-05, at 17:08 +0200, Vinay Goel <vigoel@adobe.com> wrote:

> Hi Matthias,
> 
> Both Roy and I have brought up numerous times that we have concerns over the current proposed definition of service provider.  Nick has documented ours (and others) comments about it: http://www.w3.org/wiki/Privacy/TPWG/Change_Proposal_Service_Provider.
> 
> Should that be listed as an open issue, or is that something the editors can address as part of the drafting?
> 
> -Vinay
> 
> From: "Matthias Schunter (Intel Corporation)" <mts-std@schunter.org>
> Date: Thursday, September 5, 2013 7:35 AM
> To: "public-tracking@w3.org (public-tracking@w3.org)" <public-tracking@w3.org>
> Subject: Agenda for the Sept 11 call (V01)
> Resent-From: <public-tracking@w3.org>
> Resent-Date: Thursday, September 5, 2013 7:51 AM
> 
> Hi Team,
> 
> 
> thanks a lot for the constructive call!
> 
> Enclosed is V01 of the agenda for next week's call. As indicated, during September, we need to ensure that we have a complete list of issues against the current editor's draft:
>  http://www.w3.org/2011/tracking-protection/drafts/tracking-compliance.html
> 
> The purpose of this call is to get every one of us started on this venture and ensure that we are all in sync.
> 
> 
> Feedback/comments are welcome.
> 
> Regards,
> matthias
> 
> ------------------------------
> Chair: Matthias Schunter
> ------------------------------
> 
> 1. Confirmation of scribe.  Volunteers welcome
> 
> 2. 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.
> 
> 3. Further feedback/clarification/questions on Poll and Plan (Matthias)
>     (formal deadline for comments has been shifted to Sept 13)
> 
> 4. Explanation of the poll (Matthias) and tutorial on how to provide input into the system (Nick)
> 
> 5. Survey of open issues at this point call for raising issues that are not on this list (Matthias)
>     + Tutorial on tooling for issue creation and text proposal submission (Nick)
> 
> 6. Publication of the current editor's draft as a working draft:
>     http://www.w3.org/2011/tracking-protection/drafts/tracking-compliance.html
>     I have asked our editors to 
>         - insert a disclaimer that this is only the current starting point of our 
>             discussion and that the text is not consensus of the group. 
>         - to list the issues currently open
>         - Indicating that more issues can be raised until October 02.
>    Discussion (you may email before the call, too): 
>    What are additional concrete changes to the text that are essential before we publish?
> 
> 7. Discussion how to best address ISSUE-214, i.e.
>     how to best re-insert valuable text from the very old draft (pre-June)
>     into our current working draft.
> 
> Remember: Timeline / Important dates
>     September 13: Deadline for feedback on the proposed plan
>     September 10: Poll opens
>      October 09: The poll closes; chairs and team assess responses.
>     October 02: Issue Freeze: Issues raised after October 02 will be deferred to be addressed after Last Call.
> 
> ================ 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