<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div apple-content-edited="true" class="">Hi Arun</div><div apple-content-edited="true" class=""><br class=""></div><div apple-content-edited="true" class="">Thanks for the reboot and your willingness to step forward and coordinate. Your proposed schedule is ambitious but I’d think doable. Some parts obviously are going to take longer than others. </div><div apple-content-edited="true" class=""><br class=""></div><div apple-content-edited="true" class="">For the calls, why don’t we Doodle dates and then when we have them I’ll ask Maryam to set up Adobe Connect so we can look on screen together.</div><div apple-content-edited="true" class=""><br class=""></div><div apple-content-edited="true" class="">On the third point, we need to consider also the comments and changes suggested in 2012. I’d be loath to just set these aside as people spent time on them. I guess what we could do as we walk through section by section is have two screens open comparing the suggestions then and the current bylaws for reference and then have a third new one we are doing where we move over and adapt newly agreed stuff?</div><div apple-content-edited="true" class=""><br class=""></div><div apple-content-edited="true" class="">As I said on discuss, I also think it’d be </div><div apple-content-edited="true" class=""><br class=""></div><div apple-content-edited="true" class=""><blockquote type="cite" class=""><blockquote type="cite" class=""><span class="" style="display: inline !important;">It might be useful to begin by making a list of things that should be changed in order to conform with actual practice and the NCSG charter. And a list of things that might be “nice to add” or delete. Build consensus in the team around these, develop a revision with line by line comment</span></blockquote></blockquote><div class=""><blockquote type="cite" class=""><span class="" style="display: inline !important;"><br class=""></span></blockquote></div></div><div apple-content-edited="true" class="">
</div>
<div class=""><br class=""></div><div class="">We could keep these in mind as proceeded through the sections…</div><div class=""><br class=""></div><div class="">Greetings from yet another ICANN meeting in Amsterdam</div><div class=""><br class=""></div><div class="">Bill</div><br class=""><div><blockquote type="cite" class=""><div class="">On Aug 14, 2015, at 1:17 PM, Arun Mohan Sukumar <<a href="mailto:arunmohan.s@gmail.com" class="">arunmohan.s@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hello bylawyers!<div class=""><br class=""></div><div class="">For the revision, since we've two months to attempt this before Constituency Day in Dublin, may I suggest one working method? Comments, suggestions most welcome</div><div class=""><br class=""></div><div class="">1. There are 10 sections in the NCUC charter - perhaps we could go through this section-by-section, and compare them with the NCSG charter to ensure they are in line. Here's a proposed timeline:</div><div class=""><br class=""></div><div class="">August 15 - 22 - Sections I, and II - Mission, Organisation and Structure</div><div class="">August 23 - 30 - Section III - Membership</div><div class="">August 31 - September 7 - Section IV - Executive Committee</div><div class="">September 8 - 15 - Sections V and VI - Policy Committee and Voting</div><div class="">September 16 - 23 - Sections VII, VIII - Leaving office and Changes to the Charter</div><div class=""><div class="">September 24 - October 1 - IX and X - Communications and Transparency</div><div class=""><br class=""></div><div class="">We leave ourselves with a week's buffer in this timeline to address any unscheduled delay. I'm not sure if we will be able to work during the second week of October leading up to ICANN 54 since most folks will be busy preparing for travel.</div><div class=""><br class=""></div><div class="">2. Meetings - I propose a call once at the end of this month and one at the end of September to take stock. These online meetings aside, I feel most of our work could be done through mailing list discussion and shared editing.</div><div class=""><br class=""></div><div class="">3. All members in the NCUC and Bylaws list will be notified of the proposed timeline, so that the open google document can be reviewed anytime. As with any negotiating text on which there is no consensus, we leave it in square brackets to discuss during Constituency Day. Consensus text in green. </div><div class=""><br class=""></div><div class="">How do all these sound?</div><div class=""><br class="">Arun</div><div class=""><br class=""></div>-- <br class=""><div class="gmail_signature"><div dir="ltr" class=""><div class=""><div dir="ltr" class="">Head, Cyber Initiative<div class="">Observer Research Foundation, New Delhi</div><div class=""><a href="http://amsukumar.tumblr.com/" target="_blank" class="">http://amsukumar.tumblr.com</a></div><div class="">+91-9871943272</div></div></div></div></div>
</div></div>
_______________________________________________<br class="">Bylaws mailing list<br class=""><a href="mailto:Bylaws@lists.ncuc.org" class="">Bylaws@lists.ncuc.org</a><br class="">http://lists.ncuc.org/cgi-bin/mailman/listinfo/bylaws<br class=""></div></blockquote></div><br class=""></body></html>