Comments needing responses

Just a reminder for the people getting assigned to propose responses to comments today (Kerstin and Bruce, we drew your names out of the air today and assigned each of you one also, all others were taken by attendees to the call).

The list is here: https://www.w3.org/WAI/GL/wiki/Comments_Needing_Responses

What to do:

1)      Make sure that the comment is set to "open" and assigned to you.

2)      Review the comment, think about what the right approach to handling it is.  If you can work out a good resolution, great, if you feel stuck or have questions, ask the group via email!

3)      A good resolution should read as a direct comment addressed to the commenter. E.g. "Thank you for your comment.  We agree with your suggestion and will make the change as you suggest  with the exception of the suggestion that ...".

4)      In addition to the resolution proposal, you should add notes in the "WG notes" that will indicate EXACTLY what will need to be changed.  Sometimes this will say "add a 3rd example to H101, with the following code" or it might also say "The following sentence in the description section of F290 needs to change: The moon is made of @@green cheese" (the @@ is how we indicate that a change is happening close by).

5)      Once you're content that the proposed resolution is ready for group review, change the status to "proposal" and click submit (or just click "submit as proposal" - this button does this in one step.

6)      Let Josh and Andrew know that it is ready for survey.

As mentioned on the call, don't worry about breaking anything or accidentally sending a comment out publicly - unless you are seeing a lot of additional controls that I haven't mentioned, setting them all just so, and going through a 4 step process nothing will be sent out to the public.  Thanks for all of your work!

Thanks,
AWK

Andrew Kirkpatrick
Group Product Manager, Accessibility
Adobe Systems

akirkpat@adobe.com<mailto:akirkpatrick@adobe.com>
http://twitter.com/awkawk
http://blogs.adobe.com/accessibility

Received on Tuesday, 4 March 2014 20:32:12 UTC