<div dir="ltr"><div>Dear Rosemary,</div><div>Yes ,I know, </div><div>Like you , I am involved in many area inside and outside ICANN.</div><div>But everybody recognizes the volume and pressure, urgency of so many issues that are being assigned to you and the legal Team</div><div>These efforts, in particular, your good temperament and like reaction on these moments that you are working almosr round the clock is higly appreciated by EVEERYONE </div><div>Regards</div><div>Kavouss </div></div><div class="gmail_extra"><br><div class="gmail_quote">2016-04-16 9:07 GMT+02:00 Bruce Tonkin <span dir="ltr"><<a href="mailto:Bruce.Tonkin@melbourneit.com.au" target="_blank">Bruce.Tonkin@melbourneit.com.au</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">In terms of discussions in the Empowered Community (EC) Council I don't think we need to specify that the ICANN Secretary must post all material. I think more general language that notes that meetings and communications etc should be open and transparent should be sufficient. Most groups at ICANN have their own websites and ICANN staff support to ensure that material is posted to those pages including archives of mailing list.<br>
<br>
For example - see: <a href="http://gnso.icann.org/en/" target="_blank" rel="noreferrer">http://gnso.icann.org/en/</a> - where everything is achived for the GNSO. I would imagine something similar could be set up for the EC.<br>
<br>
I would have thought a variation this existing text in the bylaws should cover it:<br>
<br>
"ARTICLE III: TRANSPARENCY<br>
<br>
Section 1. PURPOSE<br>
ICANN and its constituent bodies shall operate to the maximum extent feasible in an open and transparent manner and consistent with procedures designed to ensure fairness.<br>
<br>
Section 2. WEBSITE<br>
ICANN shall maintain a publicly-accessible Internet World Wide Web site (the "Website"), which may include, among other things,<br>
<br>
(i) a calendar of scheduled meetings of the Board, Supporting Organizations, and Advisory Committees;<br>
<br>
(ii) a docket of all pending policy development matters, including their schedule and current status;<br>
<br>
(iii) specific meeting notices and agendas as described below;<br>
<br>
(iv) information on ICANN's budget, annual audit, financial contributors and the amount of their contributions, and related matters;<br>
<br>
(v) information about the availability of accountability mechanisms, including reconsideration, independent review, and Ombudsman activities, as well as information about the outcome of specific requests and complaints invoking these mechanisms;<br>
<br>
(vi) announcements about ICANN activities of interest to significant segments of the ICANN community;<br>
<br>
(vii) comments received from the community on policies being developed and other matters;<br>
<br>
(viii) information about ICANN's physical meetings and public forums; and<br>
<br>
(ix) other information of interest to the ICANN community."<br>
<br>
Regards,<br>
Bruce Tonkin<br>
<div class="HOEnZb"><div class="h5"><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" target="_blank" rel="noreferrer">https://mm.icann.org/mailman/listinfo/bylaws-coord</a><br>
</div></div></blockquote></div><br></div>