<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Peter,<div class=""><br class=""></div><div class="">Great, so that’s everyone then. Will have Maryam post and then announce.</div><div class=""><br class=""></div><div class="">Thanks, but I believe the deadline issue is really there already. For regular ICANN meetings, it says "Interested members have two weeks (until midnight UTC) from the announcement date to submit proposals.” That’s pretty clear, no? For non-ICANN meetings, it says "At least two weeks before the relevant meeting, an interested member should submit a proposal that explains the importance of the event to NCUC and…” Again, I would think a reader would understand that if it’s not submitted at least two weeks prior, we don’t consider it. And in the case of adding a night of hotel as has sometimes happened, e.g. when we organized pre-conferences, we say "The Executive Committee will assess such requests for assistance on a case-by-case basis,” meaning we leave ourselves max flex as to how we treat these. If someone asks four days before the meeting for an extra night, we shouldn’t have to have a big bureaucratic mechanism to say yes or no to a couple hundred dollars. This would be very occasional anyway.</div><div class=""><br class=""></div><div class="">Optically, the revised rules are already tighter and more limiting than before, I’d not like to overemphasize what’s already there or it might be viewed as a deterrent. And as to how strictly we enforce deadlines, that’s up to our discretion. One can imagine circumstances in which someone submits a day late due to factors beyond their control, like uncertainty about visas or whatever, so we should use our judgement in such cases. But the default is that yes, the deadlines above are firm, so if they just don’t act fast enough, well then sorry.</div><div class=""><br class=""></div><div class="">Thanks</div><div class=""><br class=""></div><div class="">Bill</div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Apr 10, 2015, at 5:33 AM, PeterGreen <<a href="mailto:seekcommunications@hotmail.com" class="">seekcommunications@hotmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" style="font-family: Verdana; font-size: 16px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">Hi Bill, Hi Folks,<br class=""> <br class="">Agree with all of the edits made by @Bill.<br class=""> <br class="">I would like to discuss with you guys, shall we add a line stating whether we have a strict enforcement regarding timing of submitting applications, since there are members who may submit their applications after the application deadline?<br class=""> <br class="">Shall we enfore that strictly?<br class=""> <br class="">Listen to your response.<br class=""> <br class="">Thanks<br class=""> <br class="">Best<span class="Apple-converted-space"> </span><br class="">Peter<br class=""><br class=""> <br class=""><div class=""><hr id="stopSpelling" class="">From:<span class="Apple-converted-space"> </span><a href="mailto:rballeste@stu.edu" class="">rballeste@stu.edu</a><br class="">To:<span class="Apple-converted-space"> </span><a href="mailto:Stefania.Milan@EUI.eu" class="">Stefania.Milan@EUI.eu</a>;<span class="Apple-converted-space"> </span><a href="mailto:william.drake@uzh.ch" class="">william.drake@uzh.ch</a>;<span class="Apple-converted-space"> </span><a href="mailto:ncuc-ec@lists.ncuc.org" class="">ncuc-ec@lists.ncuc.org</a><br class="">CC:<span class="Apple-converted-space"> </span><a href="mailto:ggithaiga@hotmail.com" class="">ggithaiga@hotmail.com</a>;<span class="Apple-converted-space"> </span><a href="mailto:caribe@entropia.blog.br" class="">caribe@entropia.blog.br</a>;<span class="Apple-converted-space"> </span><a href="mailto:seekcommunications@hotmail.com" class="">seekcommunications@hotmail.com</a><br class="">Subject: RE: Please respond: travel support policy for policy work<br class="">Date: Thu, 9 Apr 2015 16:25:05 +0000<br class=""><br class=""><div class="">+1 Roy</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><div style="color: rgb(87, 87, 87); font-size: 8px;" class="">Sent from my T-Mobile 4G LTE Device</div></div><br class=""><br class=""><div class="">-------- Original message --------</div><div class="">From: "Milan, Stefania"<span class="Apple-converted-space"> </span></div><div class="">Date:04/09/2015 11:58 AM (GMT-05:00)<span class="Apple-converted-space"> </span></div><div class="">To: William Drake ,"Exec. Comm"<span class="Apple-converted-space"> </span></div><div class="">Cc: "Balleste, Roy" ,Grace Githaiga ,João Carlos Rebello Caribé ,Peter Green</div><div class="">Subject: Re: Please respond: travel support policy for policy work<span class="Apple-converted-space"> </span></div><div class=""><br class=""></div><div class=""><div id="ecxdivtagdefaultwrapper" style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; background-color: rgb(255, 255, 255);" class="">Hi Bill<br class=""><br class="">apologies for the silence. I have been rather busy, and I am terribly behind on email and EC-related tasks. It happens, unfortunately. <br class=""><br class=""><br class=""><br class="">I approve the revised travel policy. <br class=""><br class="">More in the coming days!<br class=""><br class="">Stefania<br class=""><br class=""><div id="ecxSignature" class=""><div style="font-family: Calibri, Arial, Helvetica, sans-serif;" class=""><div class=""><div class=""><div class=""><div class="ecxBodyFragment"><font size="2" class=""><div class="PlainText"><font face="Helvetica, sans-serif" class=""><br class=""></font></div><div class="PlainText" style="font-family: Calibri, Arial, Helvetica, sans-serif;"><br class=""></div></font></div></div></div></div></div></div><div style="color: rgb(33, 33, 33);" class=""><hr tabindex="-1" style="width: 1234.796875px; display: inline-block;" class=""><div id="ecxdivRplyFwdMsg" dir="ltr" class=""><font face="Calibri, sans-serif" style="font-size: 11pt;" class=""><b class="">Da:</b><span class="Apple-converted-space"> </span>William Drake <<a href="mailto:william.drake@uzh.ch" class="">william.drake@uzh.ch</a>><br class=""><b class="">Inviato:</b><span class="Apple-converted-space"> </span>giovedì 9 aprile 2015 10.43<br class=""><b class="">A:</b><span class="Apple-converted-space"> </span>Exec. Comm<br class=""><b class="">Cc:</b><span class="Apple-converted-space"> </span>Roy Balleste; Grace Githaiga; João Carlos Rebello Caribé; Milan, Stefania; Peter Green<br class=""><b class="">Oggetto:</b><span class="Apple-converted-space"> </span>Please respond: travel support policy for policy work</font><div class=""> </div></div><div class="">Hi<div class=""><br class=""></div><div class="">So three days later, no comments, I assume this means everything is fine. So ok, please let’s vote and get this off my desk and onto the website so I can announce the BA call for proposals and Milton can process reimbursement requests accordingly when they come in.</div><div class=""><br class=""></div><div class="">Approve revised travel policy, please tick:</div><div class=""><br class=""></div><div class="">[ ] Yes</div><div class="">[ ] No</div><div class=""><br class=""></div><div class="">Thanks</div><div class=""><br class=""></div><div class="">Bill</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""><div class=""><blockquote class=""><div class="">On Apr 6, 2015, at 3:50 PM, William Drake <<a href="mailto:william.drake@uzh.ch" class="">william.drake@uzh.ch</a>> wrote:</div><br class="ecxApple-interchange-newline"><div class=""><div class="">Hello<div class=""><br class=""></div><div class="">Thanks again Peter and Stefania for taking a crack at this. Attached please find my suggested revision.</div><div class=""><br class=""></div><div class="">I made a number of changes, in general to be clearer and more conservative for book keeping/resource conserving purposes, e.g.</div><div class=""><br class=""></div><div class="">1. Stating the overall annual thresholds we can spend up to for the two main elements. One would expect that our actual outlays would be less than the amounts for each. And below the thresholds we have flexibility, e.g. for non-ICANN meetings if five members each spend less than $1,000 there’s still something left in the kitty if we get another request for some small change, like just hotel at a working group meeting. </div><div class=""><br class=""></div><div class="">2. Stating explicitly that we cover xyz documented costs rather than giving out a flat amount irrespective of actual costs incurred. Our prior ‘up to’ formulation wasn’t precise enough without this, and we can’t just send people money for undocumented expenses. If ever we had to explain what we are doing to donors or (god forbid) the tax authorities, that wouldn’t be good.</div><div class=""><br class=""></div><div class="">3. Relatedly, per Stefania’s suggestion, making it clear that we can’t do per diem.</div><div class=""><br class=""></div><div class="">4. Deleting the "In exceptional circumstances (i.e. involving otherwise unmanageable financial hardship) it may be possible to provide the transfer in advance upon submission of a paid airline ticket receipt and confirmed hotel booking.” I recognize this may preclude someone from applying, but upon reflection there’s really no choice, we cannot just pay out a money ex ante to people who for whatever reason might not actually get to the meeting in question. It doesn’t take a vivid imagination to see how that could go wrong.</div><div class=""><br class=""></div><div class="">5. Adding mention of hotel extensions, which we have in the past done on an ad hoc basis.</div><div class=""><br class=""></div><div class="">6. Clarifying where the money’s from, in case someone asks (lots of suspicious folks in the ICANNsphere).</div><div class=""><br class=""></div><div class="">7. Adding Peter’s suggestion that the blog post be submitted before reimbursement begins. Otherwise people may be slow to do this small task, or turn it into a big thing in their heads (it only need be a couple paragraphs) and not do it at all. Make sense?</div><div class=""><br class=""></div><div class="">8. As this is a standing policy I don’t think we need to say when it was started or revised within the text. And of course a future EC can revise it if necessary, so we needn’t note that either.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">We need to move this along quickly and get the new policy in place before we start to process requests we have approved (Ed and Stephanie) or expect (James) when they come in. Moreover, it’s getting near time to issue the call for proposals for the BA meeting. </div><div class=""><br class=""></div><div class="">Please see the attached. If you want to suggest edits, please do so by Wednesday, whether in an email or by using the Track Changes function in Word and sending the doc back. If there are no suggestions by then, I will call a vote to be completed by next Saturday so we can get this posted.</div><div class=""><br class=""></div><div class="">Again, once we have received the above mentioned reimbursement requests (the first two of which we’ve already approved), maybe I will aggregate these decisions and anything else we’ve done of late (have to check email records) or will need to do soon into a single pro forma yes/no poll and send that out as an ersatz “EC Meeting” so when we’re done there’s a single record that can be posted to the web. We’ve only had one EC meeting this year, and the Bylaws call for four. Not that we should meet just to meet, but what decisions we do make should be posted in a manner that doesn’t require people to read through the archive of this list.</div><div class=""><br class=""></div><div class="">Thanks</div><div class=""><br class=""></div><div class="">Bill</div><div class=""><br class=""></div><div class=""><br class=""><div class=""><blockquote class=""><div class="">On Apr 2, 2015, at 2:46 PM, PeterGreen <<a href="mailto:seekcommunications@hotmail.com" class="">seekcommunications@hotmail.com</a>> wrote:</div><br class="ecxApple-interchange-newline"><div class=""><div dir="ltr" style="text-transform: none; text-indent: 0px; letter-spacing: normal; word-spacing: 0px; white-space: normal;" class="">Hi Bill, Hi Folks,<br class=""> <br class="">Sorry for being a bit late in posting. Please find attached the revised and integrated<span class="ecxApple-converted-space"> </span><strong class="">NCUC Travel Support Policy</strong>.<br class=""> <br class="">What I think is worthy to be highlighted is that the current version is built upon what Stefania has done previously. And thanks for tips from Bill.<br class=""> <br class="">What I have done is integrating and reframing. In addition, you would see I have added<span class="ecxApple-converted-space"> </span><strong class="">different titles for corresponding sections and themes<span class="ecxApple-converted-space"> </span></strong>in order to make the policy more well organized in its overall structure.<br class=""> <br class="">Sorry @Stefania, I am considering not adding the<span class="ecxApple-converted-space"> </span><strong class="">"No per diems will be reimbursed via this scheme [the scheme for ICANN-related meetings]".</strong><span class="ecxApple-converted-space"> </span>We would discuss on that.<br class=""> <br class="">Saying so, I want to draw your attention to the points @Stefania has made previously. <span class="ecxApple-converted-space"> </span><br class="">Let's now have a follow-up on those points made by @Stefania and the current version reframed by myself.<br class="">For convenience, those points are copied below:<br class=""> <br class=""><font color="#ac193d" class="">{</font><br class=""><font color="#006fc9" class=""></font> <br class=""><font color="#006fc9" class="">Two further points:<br class=""><br class=""></font><ul class=""><li class="">I suggest no per diems are paid through this policy. This is not designed to punish our volunteer members who sacrifice for a working group, but it is intended to maximum the number of people we can fund per year. We are eroding NCUC budget after all, and we should avoid being too lush at the beginning, only to have to cancel the funding scheme right after...</li><li class="">If we wish, we could also suggest this funding scheme is a try-out for a year. This is somehow a special year, with the IANA transition, the GNSO review, the WHOIS review, ect. -- so we can take it as a pilot here, try this out for 12 months and then see how much money is left, and whether we can afford to continue the program. (The same could apply to the travel support policy for ICANN meetings)<br class=""></li><li class="">I wanted to add something about rotation of grantees but not sure it makes sense: policy work in working group is in one's own personal capacity, so people cannot be 'easily replaced'. Therefore I suggest we don't include this 'rule' but strive to create or encourage diversity<span class="ecxApple-converted-space"> </span></li><li class="">What about postponing reimbursement only after the receipt of the blog post? Too though on people who already volunteer much of their time and energies?</li></ul> <br class=""><font color="#ac193d" class="">}</font><br class=""> <br class="">If there are any points that need to be covered, please point out.<br class="">Listen to your suggestions.<br class=""> <br class="">Best<span class="ecxApple-converted-space"> </span><br class="">Peter<br class=""> <br class=""> <br class=""></div></div></blockquote></div></div></div><span id="ecxcid:1C66839F-E7F9-4C9E-B352-77411F4B0A09@home" class=""><NCUC Travel Support Policy [BD revision 04.2015].docx></span><div class=""><div class=""></div></div>_______________________________________________<br class="">NCUC-EC mailing list<br class=""><a href="mailto:NCUC-EC@lists.ncuc.org" class="">NCUC-EC@lists.ncuc.org</a><br class=""><a href="http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec" class="">http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec</a><br class=""></div></blockquote></div><br class=""><div class=""><div style="text-transform: none; text-indent: 0px; letter-spacing: normal; word-spacing: 0px; white-space: normal;" class="">*********************************************************<br class="">William J. Drake<br class="">International Fellow & Lecturer<br class=""> Media Change & Innovation Division, IPMZ<br class=""> University of Zurich, Switzerland<br class="">Chair, Noncommercial Users Constituency, <br class=""> ICANN,<span class="Apple-converted-space"> </span><a href="http://www.ncuc.org/" target="_blank" class="">www.ncuc.org</a><br class=""><a href="mailto:william.drake@uzh.ch" class="">william.drake@uzh.ch</a> (direct), <a href="mailto:wjdrake@gmail.com" class="">wjdrake@gmail.com</a> (lists),<br class=""> <span class="Apple-converted-space"> </span><a href="http://www.williamdrake.org/" target="_blank" class="">www.williamdrake.org</a><br class=""><i class="">Internet Governance: The NETmundial Roadmap </i><a href="http://goo.gl/sRR01q" target="_blank" class="">http://goo.gl/sRR01q</a><br class="">*********************************************************</div></div><br class=""></div></div></div></div><div class="ecxWordSection1"><p class="ecxMsoNormal" style="margin: 0px; padding: 0px;"><span style="color: rgb(89, 89, 89); font-size: 8pt;" class=""> </span></p><div style="margin: 0px; padding: 0px;" class=""><span style="color: rgb(89, 89, 89); font-size: 8pt;" class="">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.<span class="Apple-converted-space"> </span></span></div></div></div></div></div><span style="font-family: Verdana; font-size: 16px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">_______________________________________________</span><br style="font-family: Verdana; font-size: 16px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="font-family: Verdana; font-size: 16px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">NCUC-EC mailing list</span><br style="font-family: Verdana; font-size: 16px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><a href="mailto:NCUC-EC@lists.ncuc.org" style="font-family: Verdana; font-size: 16px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">NCUC-EC@lists.ncuc.org</a><br style="font-family: Verdana; font-size: 16px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><a href="http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec" style="font-family: Verdana; font-size: 16px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec</a></div></blockquote></div><br class=""><div apple-content-edited="true" class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">*********************************************************<br class="">William J. Drake<br class="">International Fellow & Lecturer<br class=""> Media Change & Innovation Division, IPMZ<br class=""> University of Zurich, Switzerland<br class="">Chair, Noncommercial Users Constituency, <br class=""> ICANN, <a href="http://www.ncuc.org" class="">www.ncuc.org</a><br class=""><a href="mailto:william.drake@uzh.ch" class="">william.drake@uzh.ch</a> (direct), <a href="mailto:wjdrake@gmail.com" class="">wjdrake@gmail.com</a> (lists),<br class=""> <a href="http://www.williamdrake.org" class="">www.williamdrake.org</a><br class=""><i class="">Internet Governance: The NETmundial Roadmap </i><a href="http://goo.gl/sRR01q" class="">http://goo.gl/sRR01q</a><br class="">*********************************************************</div>
</div>
<br class=""></div></body></html>