<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">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.<div class=""><br class=""><div><div class=""><div class=""><div name="messageBodySection" class=""><div dir="auto" class="">
<div dir="auto" class=""></div></div></div></div></div><div class=""><div class=""><div name="messageBodySection" class=""><div dir="auto" class=""><div dir="auto" class="">Sadly, we have 332 public comments to address.</div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">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:</div><div dir="auto" class=""><br class=""></div><div dir="auto" class=""><span class="Apple-tab-span" style="white-space:pre"> </span><a href="https://docs.google.com/spreadsheets/d/1cOZ1lPXqHfuZNt68zvB5xRB63eBoL3gonDbhDuHEx7k/edit#gid=0" class="">https://docs.google.com/spreadsheets/d/1cOZ1lPXqHfuZNt68zvB5xRB63eBoL3gonDbhDuHEx7k/edit#gid=0</a></div><div dir="auto" class=""><br class=""></div></div></div></div></div><div class=""><div class=""><div name="messageBodySection" class=""><div dir="auto" class="">
<div dir="auto" class="">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.</div><div dir="auto" class=""><br class=""></div></div></div></div></div><div class=""><div class=""><div name="messageBodySection" class=""><div dir="auto" class=""><div dir="auto" class="">Sub-teams can start addressing the comments here:</div><div dir="auto" class=""><br class=""></div><div dir="auto" class=""><span class="Apple-tab-span" style="white-space:pre"> </span><a href="https://docs.google.com/spreadsheets/d/1DQpPA0aLDsW5IHLKgQqHtW-5860CKGCuTYIOeMPEaaw/edit#gid=925648260" class="">https://docs.google.com/spreadsheets/d/1DQpPA0aLDsW5IHLKgQqHtW-5860CKGCuTYIOeMPEaaw/edit#gid=925648260</a></div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">Remember there are three things that need to be done:</div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">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.</div><div dir="auto" class=""><br class=""></div><div dir="auto" class=""><div dir="auto" class="">2) There are comments from team members in the draft report. Handle those in addition to the public comments.</div><div class=""><br class=""></div></div><div dir="auto" class="">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.</div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">Flag items that are a big change from the draft report that require discussion (and consensus) from the whole team.</div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">Russ</div></div></div></div></div><div class=""><div class=""><div name="messageBodySection" class=""><div dir="auto" class="">
</div>
</div>
</div></div></div><br class=""></div></body></html>