[NCSG-PC] [NCSG-EC] Fwd: Initiating the Community Dialogue on "How We Meet": Initial Ideas & Meeting Request

Thu Jul 25 01:47:57 EEST 2024

Hi Jean,

NCSG should be able to respond to follow-up comments.

Warmly,
Tomslin

On Thu, 25 Jul 2024 at 04:30, Jean F. Quéralt via NCSG-EC <
ncsg-ec at lists.ncsg.is> wrote:

> Should anyone want to follow up on some of their recommendations/comments,
> would NCSG respond directly or add them to its own comment document?
>
> Best,
> Jean F. Queralt
> Founder & CEO - The IO Foundation <https://TheIOFoundation.org>
> Book a meeting <https://TIOF.Click/BookJFQ> (30 minutes)
>
>
> On Wed, 24 Jul 2024 at 23:16, Johan Helsingius via NCSG-EC <
> ncsg-ec at lists.ncsg.is> wrote:
>
>> Interesting comments from ISPC.
>>
>>         Julf
>>
>>
>>
>> -------- Forwarded Message --------
>> Subject:        [GNSO-SG-C-Leadership] Re: [soac-chairs] Initiating the
>> Community Dialogue on "How We Meet": Initial Ideas & Meeting Request
>> Date:   Wed, 24 Jul 2024 15:09:51 +0000
>> From:   philippe.fouquart--- via GNSO-SG-C-Leadership
>> <gnso-sg-c-leadership at icann.org>
>> Reply-To:       philippe.fouquart at orange.com
>> To:     DiBiase, Gregory <dibiase at amazon.com>
>> CC:     gnso-chairs at icann.org <gnso-chairs at icann.org>, Novoa, Osvaldo
>> via
>> ISPCP-Leadership <ispcp-leadership at icann.org>,
>> gnso-sg-c-leadership at icann.org <gnso-sg-c-leadership at icann.org>
>>
>>
>>
>> Hi Greg,
>>
>> Thanks for this opportunity of providing comments on the proposed
>> approach to the Community Dialogue.
>>
>> You will find attached the ISPCP Constituency’s initial ideas.
>>
>> Happy to discuss.
>>
>> Regards,
>>
>> Philippe, on behalf of the ISPs and Connectivity Providers Constituency
>>
>> *From:* DiBiase, Gregory via council <council at icann.org>
>> *Sent:* Monday, July 22, 2024 4:44 PM
>> *To:* GNSO Council List <council at gnso.icann.org>;
>> gnso-sg-c-leadership at icann.org
>> *Cc:* gnso-chairs at icann.org
>> *Subject:* [council] Re: [soac-chairs] Initiating the Community Dialogue
>> on "How We Meet": Initial Ideas & Meeting Request
>>
>> *CAUTION*: This email originated outside the company. Do not click on
>> any links or open attachments unless you are expecting them from the
>> sender.
>>
>> *ATTENTION*: Cet e-mail provient de l'extérieur de l'entreprise. Ne
>> cliquez pas sur les liens ou n'ouvrez pas les pièces jointes à moins de
>> connaitre l'expéditeur.
>>
>> Hi All- resending this email as a reminder.  Council Leadership is
>> requesting feedback by 24 July.
>>
>> Thanks,
>>
>> Greg
>>
>> *From:*DiBiase, Gregory
>> *Sent:* Tuesday, July 9, 2024 11:02 AM
>> *To:* GNSO Council List <council at gnso.icann.org
>> <mailto:council at gnso.icann.org>>; 'gnso-sg-c-leadership at icann.org'
>> <gnso-sg-c-leadership at icann.org <mailto:gnso-sg-c-leadership at icann.org>>
>> *Cc:* gnso-chairs at icann.org <mailto:gnso-chairs at icann.org>
>> *Subject:* FW: [EXTERNAL] [soac-chairs] Initiating the Community
>> Dialogue on "How We Meet": Initial Ideas & Meeting Request
>>
>> Dear Councilors and SG/C Leadership,
>>
>> We are forwarding the below message re: “How We Meet” from ICANN staff.
>> Please solicit input from your respective groups on the ideas
>> articulated in the attached Community Discussion Paper. For the purposes
>> of gathering feedback, GNSO Leadership is happy to collect and collate
>> inputs from the SG/Cs in order to share it with the other SO/AC Chairs.
>> Looking at ICANN’s proposed timeline below, please send any feedback to
>> gnso-chairs at icann.org <mailto:gnso-chairs at icann.org> by 24 July. Let us
>> know if you have concerns with this approach.
>>
>> Thanks,
>>
>> Greg on behalf of GNSO Leadership
>>
>> *From:*Mary Wong via soac-chairs <soac-chairs at icann.org
>> <mailto:soac-chairs at icann.org>>
>> *Sent:* Sunday, July 7, 2024 11:58 PM
>> *To:* soac-chairs at icann.org <mailto:soac-chairs at icann.org>
>> *Cc:* team-leaders at icann.org <mailto:team-leaders at icann.org>
>> *Subject:* [EXTERNAL] [soac-chairs] Initiating the Community Dialogue on
>> "How We Meet": Initial Ideas & Meeting Request
>>
>> *CAUTION*: This email originated from outside of the organization. Do
>> not click links or open attachments unless you can confirm the sender
>> and know the content is safe.
>>
>> Dear SOAC leaders,
>>
>> An action item from your informal meeting with Sally in Kigali was for
>> the Policy team to facilitate a dialogue with you about “How We Meet”,
>> viz., how our in-person and hybrid meetings can be optimized to ensure
>> that resources (including financial, staff and community time) continue
>> to be allocated appropriately to ensure the community can do its work
>> effectively and efficiently, while staying within budgetary constraints.
>> As a starting point for this dialogue, we have drafted the attached
>> discussion paper with some initial ideas for your community’s
>> consideration and to invite your suggestions for further discussion.
>>
>> To capitalize on the momentum of recent conversations and to facilitate
>> a constructive and substantive dialogue, we’d like to suggest the
>> following cadence of meetings, structured around a few foundational
>> questions:
>>
>>    * Late/end-July: first call with SOAC Chairs and Vice-Chairs to share
>>      feedback on agreed strategic questions
>>    * Mid/late August (following collation of ideas and input): second
>>      call to discuss and agree on concrete ideas for implementation or
>>      further exploration
>>    * End-August/early September (if agreed is needed): third call to
>>      review agreed way forward, including any next steps for additional
>>      (longer term) ideas to be discussed further
>> The sort of strategic, foundational questions we were thinking might be
>> helpful for focusing the dialogue include:
>>
>>        o If you or your group could change one thing about how we meet
>>          that will facilitate efficiency in how we deliver ICANN’s
>>          mission while remaining sustainable into the future, what would
>>          that be?
>>        o What other key changes do we need to make to continue to ensure
>>          we can meet these goals?
>>
>> Thank you for your support and willingness to collaborate with us in
>> seeking to improve and optimize how we meet. Assuming you are
>> comfortable with the proposed approach, I’ll make sure to come back to
>> you with some suggested dates for the calls. Please let me know if your
>> group have any questions or would like any additional information that
>> can assist with your internal discussions about this topic. Thank you!
>>
>> Cheers
>>
>> Mary
>>
>>
>> ____________________________________________________________________________________________________________
>> Ce message et ses pieces jointes peuvent contenir des informations
>> confidentielles ou privilegiees et ne doivent donc
>> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez
>> recu ce message par erreur, veuillez le signaler
>> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
>> electroniques etant susceptibles d'alteration,
>> Orange decline toute responsabilite si ce message a ete altere, deforme
>> ou falsifie. Merci.
>>
>> This message and its attachments may contain confidential or privileged
>> information that may be protected by law;
>> they should not be distributed, used or copied without authorisation.
>> If you have received this email in error, please notify the sender and
>> delete this message and its attachments.
>> As emails may be altered, Orange is not liable for messages that have
>> been modified, changed or falsified.
>> Thank you.
>> _______________________________________________
>> NCSG-EC mailing list
>> NCSG-EC at lists.ncsg.is
>> https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>>
>
> *DISCLAIMER*
> *The content of this message, which may contain personal or sensitive
> data, is confidential. If you have received it by mistake, please inform
> the sender by replying to the email and then permanently delete the
> message, including any attachments. It is forbidden to copy, forward or in
> any way reveal the content of this message to anyone. The integrity and
> security of this email cannot be guaranteed over the Internet and,
> therefore, the sender will not be held liable for any damage caused by the
> message.*
> _______________________________________________
> NCSG-EC mailing list
> NCSG-EC at lists.ncsg.is
> https://lists.ncsg.is/mailman/listinfo/ncsg-ec
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20240725/d16ed656/attachment-0001.htm>