As I read it, partially correct. See comments below. At 13/08/2008 03:06 PM, Brendler, Beau wrote:
Colleagues...
I have some questions on this -- apologies I have not kept on top of it, due to recent personal circumstances. This document seems vague about the at-large travel budget itself. Here's what I get from these documents referenced in the below news alert:
1. The supporting organizations want and are going to get some additional ICANN funds for travel. So are nomcom appointed people.
Correct. In fact, even the ASO which according to the document does not WANT any will get it . Presumably, if they decline, the rest of us cannot spent their money.
2. Chairs and such get some more flexibility and discretion with how travel funding is spent.
I think the chair discretion disappeared from the current version, replaced by each group having to decide on what rules/procedures will be applied to them. Chairs are allowed to travel business class (presumably only if flight is over 5 hours), but the rules adopted by the organization may or may not fund the chair (for air and or per diem).
3. Because of the expense of the forthcoming at-large summit, the at-large will be considered after the summit to be "matured," and this means: -- limited to no travel funds for those outside the ALAC, i.e., people in ALSs, RALOs, etc. (?) -- limited to no travel funds for the 18-odd people on the ALAC itself (?)
As I read it, for the coming year, ALAC is fully funded (to the extent that we are now. There is no mention of any funding for RALO/ALS people (also no mention in summarizing the current state, so it will not be perceived as a cut by others). I presume we could voluntarily take less funding for the committee and spread it around to others. Post July 2009, if the same rules apply as for other orgs (as implied, although this document is less specific on the time-frame), we would get 50% of the needed money for the 10 RALO-selected Committee members. Just as the GNSO could use money for non-Councillors (ie working group members), we could do the same for RALO/ALS people. The status of Liaison to other groups is unclear. If they are a full-fledged ALAC member, they will be subject to the ALAC rules. If not, they *may* be eligible to funding based on the rules of the organization they are liaising to. Liaison to unfunded organizations (such as Hong for ID issues) are presumably not funded unless we take some of our money to support her. Ditto for liaison TO our committee. Or at least, that is how I read the document just distributed. If staff have a different interpretation, It would be nice to hear. It would specifically be nice to know very soon who is being funded for Cairo. Alan
Is this correct?
-----Original Message----- From: ICANN News Alert [mailto:communications@icann.org] Sent: Wed 8/13/2008 2:35 PM To: Brendler, Beau Subject: ICANN News Alert -- ICANN Posts Revised Community Travel Support Procedure for FY09
ICANN News Alert http://www.icann.org/en/announcements/announcement-13aug08-en.htm ________________________________
ICANN Posts Revised Community Travel Support Procedure for FY09 13 August 2008
The work to create a community travel support procedure began with a specific call for travel support in late 2007 by some in the community (though this issue has been discussed for some time). There has been extensive consultation on community travel support. It began as a workshop in Delhi, with comments received and an analysis posted. Further, a draft was posted in June, discussed in budget meetings in Paris, and again with fairly extensive comment in person, via email and on the web. These second round of comments were summarized and analyzed. This last summary is available at:
http://forum.icann.org/lists/travel-support-draft/msg00013.html
The revised Community Travel Support Procedure for FY09 http://www.icann.org/en/topics/travel-support/revised-procedure-11aug08.htm document strives to accommodate the community feedback. Of course, this is a subject about which complete agreement is not possible. However, there is strong agreement within the community that a procedure exist that is documented, transparent, consistent, adhered-to, and reviewed/revised for efficacy.
Comparing the final procedure with the draft discussed in Paris, some key changes include:
* Guarantees travel support for NomCom-nominated counselors * Stresses transparency in application and post-meeting reporting * Allows for some flexibility in the allocation mechanism within a SO without overburdening the Chair
The document strives to be complete without being overly-detailed. This will leave many specific questions unanswered. ICANN staff will develop and post a FAQ (frequently asked questions document) to capture questions, and provide consistent answers to the entire community. If you have questions, please send them to the ICANN staff member with whom you work most closely, or send them to travel-support@icann.org.
Staff will collect feedback on issues that arise in the first implementation of this procedure, now through the Cairo meeting, and Staff will make clarifications, as needed. Additionally, Staff will conduct a complete review of the Community Travel Support Procedure at year end with a public consultation at the June ICANN meeting, and this will be an opportunity for RSSAC to provide additional input if desired. ________________________________
Sign up for ICANN's Monthly Magazine http://www.icann.org/magazine/
This message was sent by: ICANN, 4676 Admiralty Way, Suite 330 , Marina del Rey, CA 90292-6601
Powered by iContact: http://freetrial.icontact.com
Manage your subscription: http://app.icontact.com/icp/mmail-mprofile.pl?r=10248929&l=6333&s=96FD&m=167...
*** Scanned
**************************************************************************** ******** SCANNED
**************************************************************************** ******** _______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org http://atlarge-lists.icann.org/mailman/listinfo/alac_atlarge-lists.icann.org
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: http://st.icann.org/alac