<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">This raises critical questions and serious concerns, which I've put inline. The use of the passive voice in this is quite astounding -- in a number of critical spots, you can't tell who is supposed to be doing what. That makes it quite impossible to understand the process. The timing (or lack of time for any meaningful work or response by anyone but Staff and Board) is deeply troubling.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Is this just the Board's review of the comments? Is the community being written out of the process from this point forward? If so, just say so, so that we can react accordingly. Answers that fail to address these issues, failures to respond, and answers that obscure the role of the parties in this process are harmful, not helpful.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">I have been a defender of this process and this timeline in a variety of contexts, but I am losing faith. </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">I would strongly suggest that a review of the comments and a decision on amendments by the Bylaws Coordination Group should be a step in this process. If that requires another week (or more), so be it.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">The irony that the community may have no way to hold this process accountable to the community is overwhelming.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">I'm extremely concerned with where we are in this process -- which was supposed to represent the community's voice in proposing revisions to the Bylaws.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Greg</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><span style="font-family:arial,sans-serif">On Mon, May 23, 2016 at 8:43 AM, Bruce Tonkin </span><span dir="ltr" style="font-family:arial,sans-serif"><<a href="mailto:Bruce.Tonkin@melbourneit.com.au" target="_blank">Bruce.Tonkin@melbourneit.com.au</a>></span><span style="font-family:arial,sans-serif"> wrote:</span><br></div><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">Hello All,<br>
<br>
Here is my current understanding of the process steps towards the Board meeting on 27 May to consider the new bylaws:<br>
<br>
25 May - Staff sends out a summary of all comments and any proposed changes <div class="gmail_default" style="font-family:verdana,sans-serif;display:inline">[GSS: PROPOSED BY WHOM? WILL THIS INCLUDE EVERY CHANGE PROPOSED IN ALL THE COMMENTS, OR JUST COMMENTS CHOSEN BY SOME BODY? IF ONLY CHOSEN COMMENTS, WHO'S DOING THE CHOOSING? HOW WILL THIS WORK PLAN DEAL WITH COMMENTS THAT DID NOT PROPOSE SPECIFIC LANGUAGE TO IMPLEMENT CONCERNS/CHANGES FROM THOSE COMMENTS?] </div>to the draft Bylaws to the community and ICANN Board, 48 hours before the Board's vote.<br></blockquote><div><br></div><div><div class="gmail_default" style="font-family:verdana,sans-serif;display:inline">[WHAT IS THE COMMUNITY SUPPOSED TO DO WITH THIS SUMMARY IN 48 HOURS? WILL THE BYLAWS COORDINATION GROUP OR ANY OTHER SPECIFIC COMMUNITY</div> <div class="gmail_default" style="font-family:verdana,sans-serif;display:inline">GROUP HAVE A ROLE IN RESPONDING TO AND/OR APPROVING PROPOSED CHANGES?]</div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
<br>
Sidley and Adler law firms have already suggested proposed changes to the draft bylaws based on the CCWG on Accountability public comments. ICANN staff are now compiling a summary of all the public comments, and then that can be reviewed <div class="gmail_default" style="font-family:verdana,sans-serif;display:inline">[BY WHOM?] </div>with respect to possible amendments<div class="gmail_default" style="font-family:verdana,sans-serif;display:inline"> [WHO WILL DECIDE WHICH COMMENTS GET TURNED INTO POSSIBLE AMENDMENTS? WHO WILL TURN COMMENTS INTO POSSIBLE AMENDMENTS?]</div> to the draft bylaws.<br>
<br>
<br>
26 May at 21:00 UTC - Board will hold an information call to review comments received since the Board's meeting in Amsterdam, and consider any suggested <div class="gmail_default" style="font-family:verdana,sans-serif;display:inline">[SUGGESTED BY WHOM?] </div>changes to the draft bylaws<br>
<br>
<br>
27 May at 13:00 UTC - Board will hold a formal meeting to vote on the Bylaws.<br>
<br>
<br>
If there are any outstanding issues identified<div class="gmail_default" style="font-family:verdana,sans-serif;display:inline"> [BY WHOM?]</div> from the summary of comments and proposed changes to the draft bylaws provided on 25 May, then the Bylaws Coordination Group will be convened <div class="gmail_default" style="font-family:verdana,sans-serif;display:inline">[BY WHOM?] </div>to get guidance.<br>
<br>
I will separately send this to the CCWG on Accountability mailing list.<br>
<br>
<br>
Regards,<br>
Bruce Tonkin<br>
<br>
_______________________________________________<br>
bylaws-coord mailing list<br>
<a href="mailto:bylaws-coord@icann.org">bylaws-coord@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/bylaws-coord" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/bylaws-coord</a><br>
</blockquote></div><br></div></div>