More explanation on upcoming deadlines and the required actions/input

Hi Team


The latest "Important Dates" are listed in our cheat sheet at
http://www.w3.org/wiki/Privacy/TPWG#Tracking_Protection_Working_Group

Enclosed I try to add some explanation of the input we expect at each 
deadline..

An important note is that by October 16, all _issues_ must be raised, be 
documented, and have at least one change proposal. To solicit the 
complete list of _change proposals_, we will later ask for a final list 
of change proposals again once a given issue is discussed during Phase 2.

disclaimer: The plan is the normative document. If you discover 
inconsistencies between this mail and the plan, please tell me and I 
will ensure to clarify.

Feedback/questions are welcome!


Regards,
matthias


------
*by October 2nd *
    **All ISSUEs to be considered have been raised; Phase 2 will start
    for ISSUES-25, -24, -5, -10, and -170 that are sufficiently documented. 

This means that the issue tracker shows all issues people deem important 
to raise and initial documentation for each issue has been submitted.

"Raising" an issue means entering
** a name and
** a short description,
by 2 October, for every issue to be considered. This "raising" will enable
  us to get an idea of how much additional work -- as well as the severity of that work -- so
that we can modify, if necessary, our schedules. "

On October 02, the Phase 2 of ISSUES-25, -24, -5, -10, and -170 will 
start since these issues are already in a sufficient quality (i.e., 
while we required that they are properly documented by October 02, there 
is nothing anyone need to do). The goal of keeping the Oct02 deadline 
for these issues is that we can start with Phase 2 on Oct 02.

*by October 9th *
    **Respond to the poll on how to best to continue at:
    https://www.w3.org/2002/09/wbs/49311/tpwg-poll/

*by October 16 *
    **All ISSUEs are properly documented; Phase 2 starts for all issues. 

This means that all ISSUEs are in the database (as already required by 
October 02) and that each issue has proper documentation.
Proper documentation requires ** a change proposal and ** a rationale 
explaining that change, as defined in our plan as Action 3 of Phase 1 (see
http://www.w3.org/2011/tracking-protection/1309-plan.html).

By this point in time, at least one concrete change proposal and rationale must be present for each issue intended to be addressed
further.

*December 03 *

    **Publication of our next working draft (will be frozen for review
    on Nov 22)