[NCUC-DISCUSS] [Important] Additional Budget Request/What do we need for next year?

[Ayden Férdeline]

There is a place for outreach, and I think the NCUC does a pretty good job at that already, but there is also a place for constituency inreach.

How about a more targeted use of travel funding — a two-day, NCUC-only pre-event that trains our members in how to write public comments, where we discuss the implications of our positions on ICANN’s overall vision, mission, and objectives, and on how to most strategically participate in working groups? We could bring in an external consultant on the first day to offer this capacity building training, and the second day could be the policy conference that Matt proposed last year.

In terms of support, I am thinking we would ask only for 2 nights hotel for a number of participants (say, 20?) who would already be coming to ICANN 60 or 61, venue hire, and full travel + fee for the external consultant, so it should be a reasonably frugal endeavour.



Ayden Férdeline
[linkedin.com/in/ferdeline](http://www.linkedin.com/in/ferdeline)



-------- Original Message --------
Subject: Re: [NCUC-DISCUSS] [Important] Additional Budget Request/What do we need for next year?
Local Time: 27 December 2016 1:55 AM
UTC Time: 27 December 2016 01:55
From: douglaskarel at gmail.com
To: Carlos Vera <cveraq at gmail.com>
NCUC-discuss <ncuc-discuss at lists.ncuc.org>


I agree we need to request travel support for outreach activities and meetings.

I might have missed it but I did not see any requests for travel support except that for the IGF.

regards

karel DOUGLAS



On 26 December 2016 at 19:16, Carlos Vera <cveraq at gmail.com> wrote:



As seen from document, high percentage of the budget is for travel support.

So:

1. We have to get more from people traveling using fellowships

2. We need more projects from inside constituencies to get more funds for projects

What kind of projects do we need now? As an old member of icann returning to activity I see there is a need for an easy way to get involved (induction, information, interaction) in what some time seems to me like a very close circle.

Carlos Vera
isoc Ecuador




On Dec 26, 2016, at 12:26 PM, farzaneh badii <farzaneh.badii at gmail.com> wrote:



Dear NCUC Members,

Each year we file additional budget requests at ICANN to get financial support for various activities. Last year we managed to get travel support for IGF (some of our other requests were rejected). This year we should aim for getting more of our budget requests approved.

Here is the link to the requests submitted last year and the decisions: https://community.icann.org/display/projfinadhocws/GNSO+-+FY17+Additional+Budget+Requests
I recommend that before making a suggestion, you go through the submitted requests by NCUC for last year and see the format of suggestions. You could also look at the suggestion format of other stakeholder groups.

You can also look at the decision of approval and rejection.But please do not get discouraged if you have similar ideas that were rejected last year.The link to decisions is available here:https://community.icann.org/display/projfinadhocws/FY17+Decisions


Please insert your recommendations here: https://docs.google.com/document/d/1aEZoUNsHBuzj3tyTmlDiGSeinNrKJUYcPrNTfJ-dLJ8/edit?usp=sharing


We have until 14 January to come up with the ideas. The EC will review your recommendations, add its own recommendations, and reformulate and submit to ICANN by 30th Jan.

The final version will be sent to NCUC members as well.






Farzaneh

<Adopted FY17 SO-AC Additional Budget Requests.pdf>

_______________________________________________
Ncuc-discuss mailing list
Ncuc-discuss at lists.ncuc.org
http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss

_______________________________________________
Ncuc-discuss mailing list
Ncuc-discuss at lists.ncuc.org
http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncuc.org/pipermail/ncuc-discuss/attachments/20161227/76b913ef/attachment-0002.html>