[Ssr2-review] [Ssr2-coordination] Public Comment Feedback spreadsheet fully populated

[Russ Housley]

The GAG comment came in.  These are the last comments that we are expecting.  Thanks to Heather for adding them to the table so quickly.

Sadly, we have 332 public comments to address.

To tackle this volume of work, we have formed sub-teams for each recommendation.  Some team member have still not signed up.  Gaps will be filled on Wednesday.  Please sign up now:

	https://docs.google.com/spreadsheets/d/1cOZ1lPXqHfuZNt68zvB5xRB63eBoL3gonDbhDuHEx7k/edit#gid=0

As mentioned on the call last week, many comments refer to the draft report overall, or to multiple SSR2 recommendations through a single public comment. Sub-teams are encouraged to scan the comments to make sure they have found everything related to their findings and recommendations.

Sub-teams can start addressing the comments here:

	https://docs.google.com/spreadsheets/d/1DQpPA0aLDsW5IHLKgQqHtW-5860CKGCuTYIOeMPEaaw/edit#gid=925648260 <https://docs.google.com/spreadsheets/d/1DQpPA0aLDsW5IHLKgQqHtW-5860CKGCuTYIOeMPEaaw/edit#gid=925648260>

Remember there are three things that need to be done:

1) A response for each public comment in the table.  The table contains a summary, not the full public comment.  The sub-team will probably have to read the whole public comment to get the full intent of the comment.

2) There are comments from team members in the draft report.  Handle those in addition to the public comments.

3) Modified finding and recommendation text.  In making changes, think about the new document outline to avoid the repetition that is in the draft report.

Flag items that are a big change from the draft report that require discussion (and consensus) from the whole team.

Russ

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/ssr2-review/attachments/20200405/36ebed2a/attachment.html>