[NPOC-EC] Fwd: COMMENT DRAFTING Tripti Sinha to Johan (Julf) Helsingius RE: NomCom Rebalancing

Tue Jun 27 07:29:20 UTC 2023

FYI foundational work done.

---------- Forwarded message ---------
From: Caleb Olumuyiwa Ogundele <muyiwacaleb at gmail.com>
Date: Mon, May 8, 2023, 4:44 PM
Subject: COMMENT DRAFTING Tripti Sinha to Johan (Julf) Helsingius RE:
NomCom Rebalancing
To: Johan Helsingius <julf at julf.com>
Cc: Digital <stephanie at digitaldiscretion.ca>, Juan Manuel Rojas <
jumaropi at yahoo.com>, <judith at jhellerstein.com>, Stephanie Perrin <
stephanie.perrin at mail.utoronto.ca>

@Stephanie Perrin <stephanie.perrin at mail.utoronto.ca> ,

Starting this thread so that we can respond when we can. I realize just a
few of us showed interest so I have kept the circle small so that we can
work closely and efficiently on this

I will await @Stephanie Perrin <stephanie.perrin at mail.utoronto.ca> who is
our primary pen holder to share the Google Doc we will use and moderate our
contributions.

Regards

Caleb

On Thu, Apr 27, 2023 at 11:58 AM Caleb Olumuyiwa Ogundele <
muyiwacaleb at gmail.com> wrote:

> @ Stephanie, I'd be interested to work with you on this. We can also
> schedule an hour meeting to discuss since we are in the same time zone. I
> also know a couple of people interested in joining the write-up and the
> approach we can adopt.
>
> But first, let me do some basic breakdown using the GNSO and ALAC as
> comparison vs the fact that the new bylaw continues to empower delegates as
> voting members means that if ALAC has 5 votes as a single
> constituency based on their RALOs, then, we are short playing ourselves if
> we don't get 3 slots for NCUC, NPOC, and NCSG. However, that is not
> realistic and will never be considered. what I think is realistic is to get
> the 2 slots distributed between NCUC and NPOC but decided by NCSG which is
> the mothership. The additional implication is that numbers-wise, we can be
> out-voted if our interest does not align.
>
> I also understand that when we send representatives there, they look at
> the overall perspective of ICANN as an ORG. However, there are human
> elements and biases when it comes to constituency reflection on the board
> and other roles.
>
> [image: image.png]
>
> Visually from the image above, it shows that BC  and RSG has two slots.
> What we can consider is approach through backchanneling for balancing from
> this perspective.
>
> On the other hand, as per the new bylaw change request, there is a blank
> cheque here by the strike-through in the document. What I rather perceive
> is that there is a big reset here that allows all seven GNSO folks to come
> together and reconfigure. What the strike-through means is that we give you
> guys 7 slots, go fix it amongst yourselves.
> Quoting Julf from a different exchange which I totally agree with ."GNSO
> to give NCSG 2
> slots and the CSG to have 3 slots and CPH to have 2 slots"
>
>
> [image: image.png]
>
> The strikethrough in the image below technically means the NCUC does not
> have the unique powers to only send someone to NomCom as decided by their
> EC alone.
> It empowers NCSG more this time. This then means NCSG will try to balance
> both NCUC/ NPOC internally.
> [image: image.png]
>
>
>
>
> On Thu, Apr 27, 2023 at 7:30 AM Johan Helsingius via NCSG-EC <
> ncsg-ec at lists.ncsg.is> wrote:
>
>> Indeed. We need to be purely fact-based, as we are facing a lot of "the
>> non-commercials just feel they are not important enough". We definitely
>> need to hear both from our nomcom reps as well as those involved in the
>> review specifically.
>>
>> It would be great if you could take the lead. Should we open the
>> discussion to our whole membership?
>>
>>         Julf
>>
>> On 27/04/2023 06:35, Digital wrote:
>> > I would say that this calls for a very thorough, fact-packed response,
>> not just a shrill shriek about fairness.   It needs a qualitative review of
>> past selections….who exactly have the ALAC reps been picking over the past
>> 20 Years ?  (I know I know, we cant get that data) .  How are end users
>> actually protected in this community, snd what role should nomcom nominees
>> play in that regard?
>> > May I just add that “at a point in time” is one of the most meaningless
>> cliches in the english language.  this exercise may well be equally
>> meaningless but we have to give it our best effort.  Happy to volunteer to
>> draft, but we need to contact everyone who worked on the nomcom review for
>> their input, I can think of Wolfgang and Brenden but doubtless there were
>> others.
>> > cheers Steph
>> >
>> > Sent from my iPhone
>> >
>> >> On Apr 27, 2023, at 00:37, Johan Helsingius <julf at julf.com> wrote:
>> >>
>> >> Wow!
>> >>
>> >>     Julf
>> >>
>> >>
>> >> -------- Forwarded Message --------
>> >> Subject:    [CORRESPONDENCE] Tripti Sinha to Johan (Julf) Helsingius
>> RE: NomCom Rebalancing
>> >> Date:    Wed, 26 Apr 2023 19:34:24 +0000
>> >> From:    Wendy Profit <wendy.profit at icann.org>
>> >> To:    julf at julf.com <julf at julf.com>
>> >> CC:    tripti.sinha at board.icann.org <tripti.sinha at board.icann.org>,
>> Correspondence <Correspondence at icann.org>
>> >>
>> >>
>> >>
>> >> Dear Johan (Julf) Helsingius,
>> >>
>> >> Please find the attached letter from Tripti Sinha, Chair, ICANN Board
>> of Directors regarding NomCom Rebalancing.
>> >>
>> >> Thank you and best regards,
>> >>
>> >> Wendy Profit
>> >>
>> >> Board Operations Senior Manager
>> >>
>> >> ICANN
>> >> <2023-04-26 Tripti Sinha to Julf Helsingius re NomCom Rebalancing.pdf>
>> >> _______________________________________________
>> >> NCSG-PC mailing list
>> >> NCSG-PC at lists.ncsg.is
>> >> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>> _______________________________________________
>> NCSG-EC mailing list
>> NCSG-EC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>>
>
>
> --
> *Caleb Ogundele*
> Email: muyiwacaleb at gmail.com
>

-- 
*Caleb Ogundele*
Email: muyiwacaleb at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/npoc-ec/attachments/20230627/4a9e5084/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 297704 bytes
Desc: not available
URL: <https://mm.icann.org/pipermail/npoc-ec/attachments/20230627/4a9e5084/image-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 84441 bytes
Desc: not available
URL: <https://mm.icann.org/pipermail/npoc-ec/attachments/20230627/4a9e5084/image-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 128367 bytes
Desc: not available
URL: <https://mm.icann.org/pipermail/npoc-ec/attachments/20230627/4a9e5084/image-0005.png>