[Gnso-sc-budget] [EXTERNAL] Re: [v.0.9.2] Please review urgently - draft Council comment on the Budget

[Ayden Férdeline]

Thanks Donna and Jimson for flagging this. In light of the scheduled comment period on this issue, might I suggest we instead revise this bullet point from:

"The GNSO Council understands that Reserve Fund replenishment is a current area of focus for the ICANN organization. We would like to see a plan developed over the course of the next two which reviews all options for replenishing the fund in a sustainable way."

So to read:

"The GNSO Council understands that Reserve Fund replenishment is a current area of focus for the ICANN organization. We would like to see a plan developed as a matter of priority over the course of the next twowhich reviews all options for replenishing the fund in a sustainable way."

Best wishes,

Ayden

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On 6 March 2018 6:13 PM, Austin, Donna <Donna.Austin at team.neustar> wrote:

> Jimson, I think the missing word is ‘years’ if I recall correctly the comment from Erika.
>
> From: Gnso-sc-budget [mailto:gnso-sc-budget-bounces at icann.org] On Behalf Of Jimson Olufuye
> Sent: Tuesday, March 06, 2018 8:21 AM
> To: Ayden Férdeline <icann at ferdeline.com>; gnso-sc-budget at icann.org
> Subject: [EXTERNAL] Re: [Gnso-sc-budget] [v.0.9.2] Please review urgently - draft Council comment on the Budget
>
> Hi Ayden et al,
>
> Something is missing in this sentence after "...next two...":
>
> - The GNSO Council understands that Reserve Fund replenishment is a current area of focus for the ICANN organization. We would like to see a plan developed over the course of the next two  (months or ???) which reviews all options for replenishing the fund in a sustainable way.
>
> Could it be "next two months" that is anticipated or what?
>
> Cheers,
>
> JO
>
>> --------- Original Message ---------
>>
>> Subject: [Gnso-sc-budget] [v.0.9.2] Please review urgently - draft Council comment on the Budget
>> From: "Ayden Férdeline" <icann at ferdeline.com>
>> Date: 3/6/18 5:47 pm
>> To: "gnso-sc-budget at icann.org" <gnso-sc-budget at icann.org>
>>
>> Dear all,
>>
>> Just a friendly reminder that we need to send our comment on the FY19 Budget through to the Council mailing list today for evaluation and review.
>>
>> Unless I hear any objections, I plan to send through the attached file (with track changes marked to 'accepted') in 3 hours time at 17:30 UTC.
>>
>> I did a quick fact check and couldn't find where the $8.1 million figure originated from re: increase in personnel costs. Document #2, page 9 says $7.3 million, so I've adjusted this now - but I would appreciate it if someone could please double check this.
>>
>> The other changes I made were largely grammatical, replacing "implantation" on page 3 with "implementation", and reverting one sentence regarding GSE to a previous draft of our comment ([please see my email here](https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_pipermail_gnso-2Dsc-2Dbudget_2018-2DMarch_000261.html&d=DwMFaQ&c=MOptNlVtIETeDALC_lULrw&r=CwipU91YB6EkpFXK9ynnT_QUef4yC5p7jpsDm8cU97g&m=p2w3lXJYhYNaGniQpI3fXrKhPNJUeZUizP6E0QQQWWs&s=grAslBpRoqr0x8KHlNyOCnVk9WJiA8BDZJqzi5oL5Lo&e=)).
>>
>> I have also flagged one edit on page 2, second bullet point of our specific comments. "SAs/Cs" was changed to "SGs/Cs". However "SGs/Cs" was the original language, and I believe the change to "SOs/Cs" originated from Marilyn. Marilyn could you please review this and kindly advise if this change to "SOs/Cs" was intentional? Thank you.
>>
>> All - as a matter of priority could you please review the attached comment one last time and indicate if you have any concerns? Thank you very much.
>>
>> Best wishes,
>>
>> Ayden Férdeline
>>
>> _______________________________________________ Gnso-sc-budget mailing list Gnso-sc-budget at icann.org https://mm.icann.org/mailman/listinfo/gnso-sc-budget
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-sc-budget/attachments/20180306/16d09352/attachment-0001.html>