[EURO-Discuss] ACTION needed: FY17 Special Community Requests - looking for proposals

[Christopher Wilkinson]

Dear Olivier, Dear All:

It is quite important for At Large members and ALS, to participate activly in this exercise.
I detect from CCWG Accountability, a determined move to narrow down and definitively codify ICANN's mandate and consequently the budget, 
in order to severely limit the scope for funding activities outside ICANN's 'core mission'.

I believe from what I have heard that some participants are targeting anything that looks like NetMundial in the future. (Which pour memoire was co-funded by ICANN:)

However, such a restricted CCWG approach could have a negative impact on measures to improve diversity, geographical balance and development.
Which, if I am not mistaken would, in due course, also knock on to the scope for the specific requests from the community, that you have called for here.

Regards, and best wishes for 2016 to you all,

CW


On 06 Jan 2016, at 00:09, Olivier MJ Crepin-Leblond <ocl at gih.com> wrote:

> Dear All,
> 
> The FY17 Special Community Requests process has started.  This process pertains to a dedicated part of the overall ICANN annual budget that is set aside to fund specific requests from the community for activities that are not already included in the recurring ICANN budget. FY17 Special Community Requests cover the period 1 July 2016 through 30 June 2017.
> 
> The relevant information is available on the At-Large FY17 Budget Development Workspace<https://community.icann.org/display/atlarge/At-Large+FY17+Budget+Development+Workspace>, including the key deadlines, details of the process, principles and the request template.
> 
> IMPORTANT: The members of the ALAC Finance and Budget Sub-Committee (FBSC) have agreed to the following criteria for At-Large proposals:
> 
> 
>  *   Outreach should not be a major focus. Activities to improve engagement with existing members are encouraged.
>  *   If any request is made on outreach, it should probably go through the CROPP program and not this special request process.
> 
>  *   Proposals should include ways which will make the ALAC/At-Large community more effective or which will help develop the At-Large community.
>  *   RALO requests must go through a bottom up process within their RALO prior to being submitted for consideration by the FBSC.
>  *   RALOs should consider the General Assembly/Summit timeline
>  *   Proposals must be explicitly supported by the EURALO representative on the FBSC.
>  *   Staff are currently expecting that basic resources for community communications/printing will be supported through the core ICANN budget, but that community proposals for printing , etc. will be accepted as a back-up in case expectations change.  Specific proposals for communications resources beyond simple printing and editing functions should be prepared and submitted.
> 
> IMPORTANT:  Between 4 January and 22 January the RALOs are asked to review any ALS request or complete a template on behalf of the RALO and send requests to At-Large Staff<mailto:staff at atlarge.icann.org>.
> 
> Kind regards,
> 
> 
> Olivier MJ Crépin-Leblond
> EURALO Chair
> 
> _______________________________________________
> EURO-Discuss mailing list
> EURO-Discuss at atlarge-lists.icann.org
> https://atlarge-lists.icann.org/mailman/listinfo/euro-discuss
> 
> Homepage for the region: http://www.euralo.org