[NCSG-FC] URGENT: Adoption of FC Operational Procedures

[Remmy Nweke]

Thanks for eventually making out time to look at the OP and points are well
noted.

I want to believe that after Kobe, every other comments will be harmonized.

Regards
Remmy

On Sat, 23 Feb 2019, 7:32 p.m. Stephanie Perrin <
stephanie.perrin at mail.utoronto.ca wrote:

> Although I did say I cannot review them over the weekend Thato, I have
> indeed looked at the operating procedures.  I think they need a lot of
> work.  They are not ready for the NCSG EC.  Here is a very short list of my
> feedback; as I said, I cannot really go into detail until after Kobe but I
> am putting half an hour on the agenda of the NCSG meeting for a discussion
> of our goals for the FC.
>
>    - There has not been an active FC since the Charter was developed.  We
>    should therefore revisit the Charter to see if if still matches reality,
>    after 9 years.  We agree, for instance, that the membership is too small.
>    - The Op procedures lack a logical structure.  They should refer to
>    the Charter, not quote it.  There is repetition of goals (for pages).  If
>    we need definitions, they need to be in the appendix.  Every one of them
>    needs to be checked.
>    - Sections currently have sub categories that do not fit within the
>    section title.
>    - We need crystal clarity about whose money we are monitoring....ICANN
>    is responsible for accountability re its travel funding (e.g. for
>    councillors, executives, etc).  Rafik has pointed this out recently on the
>    list, but it is an extremely important distinction.
>    - We need a discussion on fundraising and membership fees....prior to
>    drafting operating procedures.
>    - We need a discussion on creating an entity for NCSG before a
>    fundraising strategy is developed.
>    - there are details in there about amounts of funding that require
>    approval....but how will that approval be achieved?  how did you arrive at
>    those amounts?
>    - What are the policy considerations behind funding decisions, and how
>    will those decisions be made?  If, for instance, the GNSO council members
>    decided they needed to bring a subject matter expert to a given meeting to
>    speak on a topic, could the FC veto that decision?  the parameters of the
>    authority of the FC have been neither discussed in plenary, nor described
>    in this document, and this is important.
>
> I think this is enough for now.  Much work still needs to be done on this
> document in my view, and on the very nature of the FC and its
> responsibilities.  Fortunately, we have no money at the moment so there is
> no urgency to this.  We have the time to do this correctly, let us do so.
>
> Stephanie
>
> Hi Stephanie and all,
>
> Can you please kindly and urgently review the *2nd version of the FC
> Draft OP
> <https://docs.google.com/document/d/1MhJH2sxV1r9g6rCRHkPG50mgUrXeDxnweVB2xZWJLWA/edit>*,
> I would like to ask Stephanie to forward this draft, if agreed, to the NCSG
> EC for review and comment, on Monday or once adopted. The sooner we are
> able to get the EC input, the easier it will be to finalise and adopt this
> document.
>
> The objections and contention points that will emerge from this submission
> will form discussion points during the FC Kobe meeting.
>
> Please also note that this document tried to balance the inputs,
> suggestions and comments of the Finance committee with that of the
> community, should you deem necessary to make further comment, please do so
> ASAP. I wish that the adoption of the FC OP be finalised by end of April
> 2019 and obtain feedback from the EC by 4 March latest. I also understand
> your busy schedules and apologies for the needed pressure, thanks in
> advance.
>
> Thato Mfikwe.
>
> _______________________________________________
> NCSG-FC mailing list
> NCSG-FC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-fc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-fc/attachments/20190306/05d5f4d3/attachment.html>