FINAL VERSION TO BE SUBMITTED IF RATIFIED
The final version to be submitted, if the draft is ratified, will be placed here by upon completion of the vote.
FINAL DRAFT VERSION TO BE VOTED UPON BY THE ALAC
The final draft version to be voted upon by the ALAC will be placed here before the vote is to begin.
Two statements will be presented, one on comments on the FY18 Plan and Budget, and a second one requesting additional ICANN meeting travel slots (last two paragraphs of first draft).
The At-Large Advisory Committee (ALAC) would like to thank the ICANN CFO and his team for the improvement made in the FY18 operating plan and budget in terms of clarity.
The ALAC notes with satisfaction the integration of the ALAC/RALO Development session and the CROPP Pilot Program into the ICANN core budget. We are also satisfied by the inclusion into the core Budget of the he Captioning project that will need in our opinion to be expanded as the activities expand.
The At-Large Advisory Committee supports the request made by the CCWG Accountability to extend the budget for the Work Stream 2 Subgroups support to FY18 to permit the completion of the CCWG Accountability mandate. However, the ALAC requests that the CCWG carefully monitor progress to ensure that no further extension is required.
We regret to notice that the Document Development Pilot Project (DDPP) is not in the FY18 budget anymore. The DDPP was a clear success for a large part of the ICANN community and deserves further funding in FY18. We even believe that it should be expanded to include training in the development of policy advice statements.
The ALAC notices that the Root Zone Maintainer Agreement (RZMA) cost increased by 33,33%. The increase relevant increase may be explained by FY18 being a full year instead of 9 months but not why the total for FY18 exceeds the $25k/month specified in the contract,
In the Planned capital projects for FY18 (Page 16), it is mentioned that $300,000 is allocated to the ICANN & At-Large website platforms enhancement. Upon investigation with ICANN staff, we now understand that this is a consolidation of other current expenses and is for a small support team to support the "Ruby on Rails" web development tool that is used for the main ICANN web site as well as for the part of the site used by At-Large. We suggest that such expenses not be labeled as if it were an expense requested by or for the benefit of a particular part of ICANN when it is just an internal IT decision to rationalize expenses.
Travel slot request to be posted shortly.
FIRST DRAFT SUBMITTED
The first draft submitted will be placed here before the call for comments begins.
FY18 Operating Plan and Budget
----------------------------------------------
ALAC Comment
------------------
The At-Large Advisory Committee (ALAC) would like to thank the ICANN CFO and his team for the improvement made in the FY18 operating plan and budget in terms of clarity.
The ALAC notes with satisfaction the integration of the ALAC/RALO Development session and the CROPP pilot Program into the ICANN core budget. We are also satisfied by the inclusion into the core Budget of the he Captioning project that will need in our opinion to be expanded as the activities expand.
The At-Large advisory Committee supports the request made by the CCWG Accountability to extend the budget for the Work Stream 2 Subgroups support to FY18 to permit the completion of most of those sub-groups work.
We regret to notice that the Document Development Pilot Project (DDPP) is not in the FY18 budget anymore. The DDPP was a clear success for a large part of the ICANN community and deserves further funding in FY18. We even believe that it should be expanded to include training in the development of policy advice statements.
The ALAC notices that the Root Zone Maintainer (RZM) agreement cost increased by 33,33%. Is it because the contract period for FY17 was only 9 months while for FY18, it is for the full year?
In the Planned capital projects for FY18 (Page 16), it is mentioned that $ 300,000 are allocated to the ICANN & At-Large website platforms enhancement. We strongly believe that this information should be further detailed to separate the cost of the At-Large website platform enhancement fro the ICANN’s one for more clarity and transparence.