<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none"><!--P{margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>Thanks Bill</p>
<p>Unfortunately, I cannot really add much (or correct): I was coughing so much that I only have confused memories of the meeting. But I trust the collective memory of the group!<br>
</p>
<p>Stefania<br>
</p>
<div id="Signature">
<div name="divtagdefaultwrapper" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:; margin:0">
<div>
<div>
<div>
<div class="BodyFragment"><font size="2"><font face="Calibri, Arial, Helvetica, sans-serif"></font></font></div>
</div>
</div>
</div>
</div>
</div>
<div style="word-wrap:break-word">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" face="Calibri, sans-serif" color="#000000"><b>Da:</b> ncuc-ec-bounces@lists.ncuc.org <ncuc-ec-bounces@lists.ncuc.org> per conto di William Drake <wjdrake@gmail.com><br>
<b>Inviato:</b> giovedì 25 settembre 2014 13.29<br>
<b>A:</b> Exec. Comm<br>
<b>Oggetto:</b> [NCUC-EC] Singapore EC meeting minutes</font>
<div> </div>
</div>
<div>Hi
<div><br>
</div>
<div>Talking with Stefi about posting the Instanbul minutes, we realized the Singapore minutes never got posted. I had thought that I circulated a text revising the notes that had been taken, but it seems I forgot and they have just been sitting on my computer
for a half year. Oops. If the two subsequent efforts to hold EC meetings hadn’t been busts I’d have looked this up then, but whatever, here they are now. If anyone wants to amend these or the Istanbul ones please suggest language, otherwise let’s please
approve and post them to the website.</div>
<div><br>
</div>
<div>Bill</div>
<div><br>
</div>
<div>————</div>
<div><br>
</div>
<div>Minutes of the 1st NCUC Executive Committee meeting of 2014<br>
Location: ICANN Singapore meeting<br>
Saturday 22 March 2014 <br>
<br>
Participants: <br>
<br>
William Drake (NCUC Chair)<br>
Carlos Affonso Pereira da Souza (Latin America/Caribbean representative)<br>
Roy Balleste (North America representative)<br>
Stefania Milan (Europe representative)<br>
Grace Githaiga (Africa representative) <br>
Pranesh Prakash (Asia/Australia/Pacific representative)<br>
<br>
Agenda:<br>
<br>
1. Introduction to the NCUC Work Cycle<br>
2. Internal Working Methods<br>
3. Teams<br>
4. Financial<br>
<br>
The meeting was held as part of a day-long “retreat” for the new EC that had the following schedule:<br>
<br>
————<br>
<br>
10:00-11:00<span class="Apple-tab-span" style="white-space:pre"> </span>Introductions, overview of NCUC <=> NCSG <=> GNSO <=> ICANN <br>
<span class="Apple-tab-span" style="white-space:pre"></span>Overview of the Week Ahead<br>
<br>
11:00-11:50<span class="Apple-tab-span" style="white-space:pre"> </span>Overview of GNSO/Council: Institutional & Procedural Aspects, with Rob Hoggarth (staff); <br>
<span class="Apple-tab-span" style="white-space:pre"></span>afterward move to GNSO Council, Sofia Room<br>
<br>
12:00-13:00 <span class="Apple-tab-span" style="white-space:pre"> </span>Council open and substantial strategic discussion<br>
<br>
13:00-14:00 <span class="Apple-tab-span" style="white-space:pre"> </span>Lunch<br>
<br>
14:00-15:00 <span class="Apple-tab-span" style="white-space:pre"> </span>NCUC Executive Committee Meeting & Annual Planning<br>
<span class="Apple-tab-span" style="white-space:pre"></span>afterward return to GNSO Council, Sofia Room<br>
<br>
15:15-16:00 <span class="Apple-tab-span" style="white-space:pre"> </span>Council Discussion with CEO Fadi Chehadé;<br>
<span class="Apple-tab-span" style="white-space:pre"></span>afterward return to Moor room<br>
<br>
16:15-17:00<span class="Apple-tab-span" style="white-space:pre"> </span>Overview of GNSO/Council: Substantive Issues, with Mary Wong (staff, former NCUC)<br>
<br>
17:00-17:30<span class="Apple-tab-span" style="white-space:pre"> </span>Next Steps, Wrap Up <br>
<br>
————<br>
<br>
The Chair opened the meeting, participants were introduced, and the agenda was created and approved.</div>
<div><br>
<br>
<b>1. Introduction to the NCUC Work Cycle</b><br>
<br>
Bill Drake provided background on NCUC’s quarter-by-quarter work cycle, and on GNSO council terms.<br>
<br>
<ul>
<li>Bylaws: The tortured history of efforts to revise these was reviewed. It was explained by ICANN staff that it takes a half year to get any changes approved by the Board. So in order to have a stable text that would be ready for a vote during the NCUC
regular election, revisions would have to happen in the first quarter or soon thereafter, when the EC is new and just getting up to speed. It might be difficult to do this in time for the 2014 election, but we could try, or let it wait until the 2015 election.
Carlos offered to lead a team that would take charge of the revision process.</li></ul>
<ul>
<li>Policy: Since the stakeholder group framework was implemented, NCUC has focused its GNSO-oriented work in the NCSG PC. The NCUC Policy Committee called for in the bylaws does not exist, and has not for some time. As such, NCUC really has no formalized
process for adopting policy statements, and has tended to settle for informal polling of member sentiment and identification of rough consensus on the members mail list. This is not an ideal approach, and in any bylaws revision it would be sensible to formalize
a method, recognizing that with the GNSO work being done at the SG level we may not have all that many occasions to use it.</li></ul>
<br>
<b>2. Internal Working Methods</b><br>
<br>
<ul class="MailOutline">
<li>We need to ensure more effective and responsive communications within the EC. The early signs on the mail list suggest a need for stronger engagement. Grace suggests it would be helpful to assemble volunteers to prepare a beginner's guide to the NCUC
EC.</li></ul>
<div><br>
</div>
<br>
<b>3. Teams</b><br>
<br>
Bill tried to establish these last year as means to bring together EC members with regular members to handle particular managerial tasks. EC members would serve as facilitators, and hopefully there’d evolve greater buy-in to the work. In the end, the record
in 2013 was rather mixed. <br>
<br>
<ul>
<li>The e-Platforms Team: This has been reasonably successful, volunteers have collaborated to maintain the data base, mail lists, and web site. It would be good to improve the website, e.g. by including member blog posts. </li></ul>
<ul>
<li>The Events Team: This was intended to formalize the ad hoc group that successfully organized the workshops at the Beijing meeting and the policy conferences in Toronto and San Francisco. For various reasons----especially the very compressed time frame
after ICANN budget approval and need for extensive interaction with staff and other community members---it proved more difficult to follow this model in organizing the Singapore Conference,
<i>ICANN & Global Internet Governance: The Road to São Paulo & Beyond</i> <a href="http://singapore49.icann.org/en/schedule/fri-ncuc-ig">http://singapore49.icann.org/en/schedule/fri-ncuc-ig</a>. As such, Bill Drake did most of the work, and hence the EC agreed
that this should be under conditions akin to the agreements NCUC had with Robin for previous conferences, to be agreed later online.</li></ul>
<ul>
<li>The Membership Team: This folded together two separate groupings that failed to launch (the Inreach Team and the Outreach Team). This one has fared no better, and nobody seems willing to lead it. Even if the person(s) leading this is not from the EC,
that would be fine. </li></ul>
<br>
<b>4. Financial</b><br>
<br>
<ul>
<li>Travel requests: The EC's travel funding situation was discussed. Several members are able to raise their own funds to attend ICANN meetings, which makes it easier to use the ICANN-provided slots for others, or for regular members who need to be at a
particular meeting.</li></ul>
<ul>
<li>CROPP Funding Program: This gives each constituency up to five travel grants within their region. It is on a rolling basis. Pranesh and Bill will coordinate this within the NCUC.</li></ul>
<ul>
<li>NCUC Resources: Milton Mueller is our treasurer, and operates the NCUC bank account with Solvay Bank in Syracuse. We have an outstanding pledge of USD $5,000 from ISOC, and Pranesh will follow up on this. </li></ul>
<ul>
<li>NCUC Expenditures: The EC approved an extra night’s stay at the Swissotel or similar in Singapore for: Avri Doria, Marilia Maciel, Joana Varon, Satish Babu, and David Cake so that they could participate in the NCUC conference. For Robin Gross, the EC approved reimbursements
of travel and lodging expenses, pending submission of reimburesement claims.</li></ul>
<ul>
<li>Travel Policy: The EC discussed the idea of making travel support funds available for application by members. Possible criteria for evaluating requests include whether the person is engaged in NCUC work, has a pressing need to be at a particular meeting,
and lacks alternative sources of funding.</li></ul>
<ul>
<li>ICANN Budget requests: The deadline for FY 15 budget proposals to ICANN for this year ended earlier in March. Bill put in a support proposal for the IGF in Istanbul. For FY 14 year he had requested and received budget allocations for the IGF in Bali,
the Singapore policy conference, the Singapore EC retreat, print materials. Next year we might want to do more.</li></ul>
<ul>
<li>Staff support: There’s an ongoing discussion about them providing us with part-time support. Priorities would seem to be database management, elections, compiling list of policy WGs, deadlines, etc. </li></ul>
<br>
<br>
</div>
</div>
</div>
<meta name="ProgId" content="Word.Document">
<meta name="Generator" content="Microsoft Word 14">
<meta name="Originator" content="Microsoft Word 14">
<link rel="File-List" href="eui%20footer_files/filelist.xml"><link rel="themeData" href="eui%20footer_files/themedata.thmx"><link rel="colorSchemeMapping" href="eui%20footer_files/colorschememapping.xml"><style> <!-- /* Font Definitions */ @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-520092929 1073786111 9 0 415 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} .MsoPapDefault {mso-style-type:export-only; margin-bottom:10.0pt; line-height:115%;} @page WordSection1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.WordSection1 {page:WordSection1;} --> </style><style> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin-top:0in; mso-para-margin-right:0in; mso-para-margin-bottom:10.0pt; mso-para-margin-left:0in; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} </style>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:8.0pt;color:#595959"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;color:#595959">The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination,
distribution, forwarding, or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited without the express permission of the sender. If you received this communication in
error, please contact the sender and delete the material from any computer. <o:p>
</o:p></span></p>
</div>
</body>
</html>