[NCSG-FC] [Ext] ICANN64 FC meeting preparations

[Stephanie Perrin]

I think you must have meant this for Bruna, Thato.  I am not the head of the NCUC, nor of NPOC.  the heads of those constituencies are in charge of managing the selection of their members of the Finance Cttee, not me.  ccing Bruna so she can respond.  Other responses in line.

Stephanie

On 2019-02-20 15:53, thatomfikwe wrote:
Hi,


When things are happening in parallel, with announcements for FC members replacement, makes the entire planning process for the Kobe meeting a mission.

It would have been better if such announcements were made after ICANN64, they put the FC in a difficult position and the Kobe meeting is planned to revive the FC not create uncertainty and uncomfortable situations with members who will be leading deliberations. Not sure if such actions were well thought of or well planned.
see Bruna and Joan


I am not exactly sure how we are going to proceed despite serveral attempts to hold a meeting with members before Kobe in order to discuss the planned agenda in detail and emerging issues.

Do you have any idea how busy council is, and the epdp, and the WHOIS review cttee, and the comments process in general?  We are running ragged.  WE need more members to staff the working groups.

ICANN staff is just an email away, the Charter requires the FC to work with ICANN finance so if the committee is to be effective then it needs to establish or revive critical connections that will ensure that NCSG and its constituencies are fairly supported.
First we determine our own policy positions.  Do we want paid memberships?  Do we want to establish an entity, if so what?  These are not issues to discuss with staff, they would not be authorized to express an opinion, nor should they.

Regarding the strong position of the community, what issues are they arguing? Do you think they are valid and what were the reposnes of members during that time?
not sure what this question is addressing

If you carefully review comments, they.were centered around
- the bank account and incorporation of NCSG. This is currently being dealt with and in progress, to also be further discussed and decided upon
- the role of the FC, many disagree with a lot of what is stipulated on the Charter, whereas the Charter uses simple language
Indeed, I cannot figure out for the life of me what the drafters of the Charter had in mind.  Establishing an entity has serious financial repercussions.  I have no idea where the money for that would come from.  Fund raising is difficult at the best of times, to support us at ICANN....likely to be quite a chore.

When we review we need to be objective, even though it might seem like the vocal in the mailing list are the majority. If the FC is designed to have no autonomy then its efforts to correct mistakes of the past will always go unnoticed and unrecognised.

what specific mistakes are you talking about?



Thato Mfikwe.

Sent from my Samsung Galaxy smartphone.
-------- Original message --------
From: Stephanie Perrin <stephanie.perrin at mail.utoronto.ca><mailto:stephanie.perrin at mail.utoronto.ca>
Date: 20/02/2019 21:59 (GMT+02:00)
To: Thato Mfikwe <thatomfikwe at gmail.com><mailto:thatomfikwe at gmail.com>
Cc: Maryam Bakoshi <maryam.bakoshi at icann.org><mailto:maryam.bakoshi at icann.org>
Subject: Re: [Ext] ICANN64 FC meeting preparations


The event where the FC Chair, without informing his colleagues on Council or the PC, invited senior ICANN staff to one of the first FC meetings.  Nobody was prepared.  Most of us were unable to attend the last minute meeting.  Surprises are rarely appreciated, and noone knew the conditions under which staff had been invited.   If you check back in the email archives you will be able to see the grumbling that ensued after that meeting.  Senior people are exceptionally busy at ICANN meetings....we don't invite them unless we have consensus that we are ready to meet them.

We are by nature a consultative group.  The FC should always be consulted, so there is an open record for members to consult.  Many members have strongly held views on the FC and its mandate, and check the email archives. If there is nothing there, it is insufficiently transparent, at least in my view.  I believe that is a commonly held view.

Stephanie


On 2019-02-20 13:51, Thato Mfikwe wrote:
Hi Sephanie,

What was an embarrasment?

Thato Mfikwe.

On Wed, Feb 20, 2019 at 8:40 PM Stephanie Perrin <stephanie.perrin at mail.utoronto.ca<mailto:stephanie.perrin at mail.utoronto.ca>> wrote:

Personally, I do not think we are ready to meet with ICANN Finance staff. However, it appears the request has gone.  We have already gone through this when Ed was chairing the Finance Committee, and it was an embarrassment in my opinion.


Cheers Stephanie

On 2019-02-20 03:27, Maryam Bakoshi wrote:
Hi Thato,

Good morning I hope this email meets you well. I have forwarded this request to Mary Wong, ICANN Staff.

I am also cc’ing Stephanie, so she is in the loop.

—
Many thanks,


Maryam Bakoshi | SO/AC Collaboration Services Sr. Coordinator
ICANN | Internet Corporation for Assigned Names and Numbers
S: Maryam.bakoshi.icann | T: ‭+44 7846 471777‬

On 20 Feb 2019, at 00:25, Thato Mfikwe <thatomfikwe at gmail.com<mailto:thatomfikwe at gmail.com>> wrote:

Hi Maryam,

Is it possible that we request the presence of one of ICANN Finance staff and ICANN legal in the FC meeting in Kobe which will be taking place on Wednesday, 15h15 - 16h45.

Main support needed from ICANN staff:
- Elaboration on legal implications on incorporation of NCSG and what it will mean for ICANN.
- Advice on alternative sources of fundraising and opening a bank account in the name of NCSG.
- Recommendation on how to best set up the Operational Procedures and ways of working with ICANN finance to support NCSG and constituency initiatives and activities.
- Provision of clarity on how community comments are reflected in current and future ICANN operational and financial plans.

We only have 2 weeks before the meeting. I hope this message, finds you well, thanks.

Thato Mfikwe.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-fc/attachments/20190220/d2bc9927/attachment-0001.html>