ACTION-278: Suggest an alternative to debugging graduated response ('once identified a problem')

Suggest an alternative to debugging graduated response ('once identified a problem')

State:
pending review
Person:
Thomas Lowenthal
Due on:
October 10, 2012
Created on:
October 3, 2012
Associated Product:
Compliance Next
Related emails:
  1. action-409: gathering history on "graduated response" (from npdoty@w3.org on 2013-06-05)
  2. Re: ACTION-372 service providers and debugging (from jmayer@stanford.edu on 2013-03-22)
  3. Re: ACTION-372 service providers and debugging (from rigo@w3.org on 2013-03-22)
  4. Re: ACTION-372 service providers and debugging (from jmayer@stanford.edu on 2013-03-19)
  5. Re: ACTION-372 service providers and debugging (from fielding@gbiv.com on 2013-03-19)
  6. Re: ACTION-372 service providers and debugging (from jmayer@stanford.edu on 2013-03-18)

Related notes:

[npdoty]: "After identifying an error that impairs existing intended functionality, it is acceptable to collect additional data which may be needed to identify the cause of the error and resolve it, so long as the resolution of that error is as prompt as possible, and that the data is used only for that purpose and deleted immediately afterwards."

3 Oct 2012, 12:35:48

Display change log.


Matthias Schunter <matthias.schunter@intel.com>, Chair, Bert Bos <bert@w3.org>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.326 2018/10/13 17:29:51 vivien Exp $