[PC-NCSG] [council] FW: [CCWG-ACCT] CCWG-Acct Hyderabad Meeting and Travel Funding Process for Members

Fri Aug 5 21:32:18 EEST 2016

Already pinged Robin on this, and when I last looked at the google doc, Avri seems to have submitted her application.

The deadline for this is today.

Thanks.

Amr

> On Aug 5, 2016, at 7:05 PM, Stephanie Perrin <stephanie.perrin at mail.utoronto.ca> wrote:
> 
> I trust our members have got their support requests in by this deadline of today?
> 
> stephanie
> 
> 
> 
> -------- Forwarded Message --------
> Subject:	[council] FW: [CCWG-ACCT] CCWG-Acct Hyderabad Meeting and Travel Funding Process for Members
> Date:	Fri, 5 Aug 2016 02:36:37 +0000
> From:	Phil Corwin <psc at vlaw-dc.com> <mailto:psc at vlaw-dc.com>
> To:	council at gnso.icann.org <mailto:council at gnso.icann.org> <council at gnso.icann.org> <mailto:council at gnso.icann.org>
> 
> Fellow Councilors:
>  
> I just wanted to make sure that you were all aware that a full day meeting of the CCWG on WS2 Accountability issues has been scheduled for November 2nd , the day prior to the official start of ICANN 57. My understanding is that the CCWG?s time frame required a full day F2F meeting and that this could only be accomplished on that date.
>  
> Best to all, Philip
>  
>  
>  
> Philip S. Corwin, Founding Principal
> Virtualaw LLC
> 1155 F Street, NW
> Suite 1050
> Washington, DC 20004
> 202-559-8597/Direct
> 202-559-8750/Fax
> 202-255-6172/Cell
>  
> Twitter: @VlawDC
>  
> "Luck is the residue of design" -- Branch Rickey
>  
> From: accountability-cross-community-bounces at icann.org <mailto:accountability-cross-community-bounces at icann.org> [mailto:accountability-cross-community-bounces at icann.org <mailto:accountability-cross-community-bounces at icann.org>] On Behalf Of Karen Mulberry
> Sent: Tuesday, August 02, 2016 12:58 PM
> To: CCWG accountability
> Cc: ACCT-Staff
> Subject: [CCWG-ACCT] CCWG-Acct Hyderabad Meeting and Travel Funding Process for Members
>  
> Dear CCWG-Acct ,
>  
> I wanted to let you know that the November 2nd Face-to-Face meeting in Hyderabad the day before ICANN 57 has been confirmed. 
>  
> A process had been prepared for CCWG appointed members to apply for travel funding to attend the meeting that aligns with the CCWG-Acct budget for WS2. 
>  
> The current budgeted amount to support the work of CCWG WS2 members allocates support (travel, hotel and per diem) for an amount equivalent to 20 appointed members to attend a CCWG-Acct. face-to-face meeting in association with an ICANN meeting with support for 7 days.  The Co-Chairs have the authority to re-allocate this amount ? this could include supporting requests for partial funding to allow them to maximize the number of members attending (e.g. if someone only needs a few additional days of hotel this could be acceptable).
>  
> You are eligible for travel support from the CCWG if you are an officially appointed member of WS2 from a Chartering SO or AC.
>  
> Travel support arrangements will follow Constituency Travel Guidelines located at:
> https://community.icann.org/display/trvlconstit/Constituency+Travel+Home <https://community.icann.org/display/trvlconstit/Constituency+Travel+Home>
>  
> The CCWG travel support slots will be allocated as follows:
>  
> CCWG Co-Chairs ? 3 slots (or equivalent amount)
> CCWG Appointed Members ? 17 slots (or equivalent amount)
>  
> CCWG appointed Members requesting consideration by the Co-Chairs for travel support to attend a face-to-face meeting must complete the travel request form three (3) months in advance of the date of the CCWG face-to-face meeting in order to be considered for funding. 
>  
> NOTE:  In evaluating the applications for travel funding the Co-Chairs will consider applicant's attendance to CCWG meetings and their contributions to the ongoing work.
>  
> CCWG Staff support will send out an announcement regarding the application for travel support and deadline for application submissions as soon as a face-to-face meeting has been approved.  The application to request travel support is located at:  https://community.icann.org/x/qQubAw <https://community.icann.org/x/qQubAw>  
>  
> The deadline for applications for travel funding for the Hyderabad face-to-face meeting is August 5th 23:59 UTC.
>  
> CCWG approved members seeking travel support must submit their applications by the August 5th in order to be considered for travel support 
>  
> Completed forms can be sent to Acct-Staff at icann.org <mailto:Acct-Staff at icann.org> for submission to the Co-Chairs for review and approval.
>  
> All applicants for CCWG WS2 travel support will be posted on the CCWG WS2 wiki under Travel Support at https://community.icann.org/x/qQubAw <https://community.icann.org/x/qQubAw>.  Names will be listed under Requested and then once approved will be list under approved for travel support including the type of support that is approved
>  
> The Co-Chairs will review the applications received, including the requests for partial support, and determine the list of approved CCWG members who will receive travel funding. 
>  
> The CCWG approved travel support list will be submitted to ICANN Constituency Travel for processing according to community travel guidelines.
>  
> The approved list of funded CCWG members will be posted on the WS2 wiki athttps://community.icann.org/display/WEIA/Travel+Support <https://community.icann.org/display/WEIA/Travel+Support>
>  
>  
> Karen Mulberry
> Multistakeholder Strategy and Strategic Initiatives
> ICANN
>  
>  
> No virus found in this message.
> Checked by AVG - www.avg.com <http://www.avg.com/>
> Version: 2016.0.7690 / Virus Database: 4627/12704 - Release Date: 07/29/16
> <smime.p7s><ATT00001.c>_______________________________________________
> PC-NCSG mailing list
> PC-NCSG at ipjustice.org <mailto:PC-NCSG at ipjustice.org>
> http://mailman.ipjustice.org/listinfo/pc-ncsg <http://mailman.ipjustice.org/listinfo/pc-ncsg>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.ipjustice.org/pipermail/pc-ncsg/attachments/20160805/803c3ae0/attachment-0001.html>