[LAC-Discuss] FW: [ALAC-Announce] Revised Community Travel SupportProcedure for FY09 Posted

Carlos Vera cveraq at gmail.com
Sat Aug 16 21:52:44 EDT 2008


May somebody can help to "translate" this.. I mean put it in plain 
english...?

Carlos Vera
Ecuador
----- Original Message ----- 
From: "Carlton Samuels" <carlton.samuels at uwimona.edu.jm>
To: "LAC Discuss" <lac-discuss at atlarge-lists.icann.org>
Sent: Thursday, August 14, 2008 11:03 AM
Subject: [LAC-Discuss] FW: [ALAC-Announce] Revised Community Travel 
SupportProcedure for FY09 Posted


> Dear Colleagues:
> See the new and long awaited travel support policy.  Quite frankly, this 
> is
> not the easiest documentation to get thru or understand.  And 
> unfortunately,
> it is not yet available in Spanish.  At any rate, the AT-Large staff will 
> be
> answering questions as best as they can.
>
>>From my reading, broad ALS/RALO travel support for attending ICANN 
>>meetings
> seems, by and large, to be relegated to fellowship assistance.  From a
> strategic perspective, this travel policy is merely the thin edge of a 
> sure
> wedge. Because the declaration that the ALAC is "mature" after the ALS
> Summit surely means that ICANN would have signalled less interest in the
> whole ALS/RALO enterprise input to policy; think of yourselves as unloved
> cousins visiting past your exit date.
>
> Carlton
>
>
>
> -----Original Message-----
> From: alac-announce-bounces at atlarge-lists.icann.org
> [mailto:alac-announce-bounces at atlarge-lists.icann.org] On Behalf Of 
> At-Large
> Staff
> Sent: Wednesday, August 13, 2008 12:46 PM
> To: alac-announce at atlarge-lists.icann.org
> Subject: [ALAC-Announce] Revised Community Travel Support Procedure for 
> FY09
> Posted
>
> ICANN Posts Revised Community Travel Support Procedure for FY09
>
> http://www.icann.org./en/announcements/announcement-13aug08-en.htm
>
> 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
>
> ) 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 at 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.
> -- 
> Regards,
>
> Nick Ashton-Hart, Matthias Langenegger, Frederic Teboul
> ICANN At-Large Staff
> email: staff at atlarge.icann.org
>
> _______________________________________________
> ALAC-Announce mailing list
> ALAC-Announce at atlarge-lists.icann.org
> http://atlarge-lists.icann.org/mailman/listinfo/alac-announce_atlarge-lists.
> icann.org
>
> At-Large Official Site: http://atlarge.icann.org
>
>
>
> _______________________________________________
> LAC-Discuss mailing list
> LAC-Discuss at atlarge-lists.icann.org
> http://atlarge-lists.icann.org/mailman/listinfo/lac-discuss_atlarge-lists.icann.org
>
> Homepage for the region: http://www.lacralo.org
>
> Posting guidelines to ensure machine translations of emails sent to the 
> list are more accurate: 
> http://www.funredes.org/mistica/english/emec/method_emec/presentation.html#anexo1 





More information about the lac-discuss-en mailing list