WSC Open Action Items

1) Do not let your Action Items go past due. It creates overhead for me, 
which is time I could spend on the content of the group, instead of trying 
to figure out what I should do about overdue action items. 

2) Complete your Action Item by the Due Date. 

3) Make sure to send an email to publis-wsc-wg with the exact ID somewhere 
in the subject line (upper case, with the "-", for example, ACTION-3) for 
tracking purposes. While I sometimes realize and remember that an action 
was completed, I often do not without this. 

4) Do NOT close them yourself; I'll do that. That's how they get into the 
agenda, so I can give you props during the meeting. 

5) If a personal emergency arises so that at the last minute you cannot 
possibly complete the Action Item by the Due Date, reset the Due Date. It 
takes only 30 seconds. And decreases my nag overhead. 

6) And with these sky-flakes down in flurry on flurry. 


Thank you to all of you who do all this without regular personal 
reminders. 
[] : to - due 

[OPEN] ACTION-214: Bill Doyle to solicit commentary on Threat Trees from 
MITRE INFOSEC community - due 2007-08-04

[OPEN] ACTION-248: Johnathan Nightingale to Ensure that the robustness 
stuff (MozillaCurrentPractises) ends up in the recommendations - due 
2007-08-11

[OPEN] ACTION-256: Mike Beltzner to Summarize and bring back issues to 
working group - due 2007-08-08

[OPEN] ACTION-268: Phillip Hallam-Baker to Phrase conformance language for 
fully securing sites - due 2007-08-10

[OPEN] ACTION-274: Bill Doyle to experiment with lc-comments-tracker and 
report back - due 2007-08-15

[OPEN] ACTION-278: Audian Paxson to check on linux platform - due 
2007-08-22