<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I take the point OCL is making (reflecting particularly Chris’ views) that there should be a way to be sure we seen as part of ICANN meetings and on ICANN meeting schedules. <div class=""><br class=""></div><div class="">In the first couple of online meetings, our sessions generally attracted a lot of members of the other communities in ways that hadn’t happened for in person meetings. WE were a very important component of ICANN meetings. </div><div class=""><br class=""></div><div class="">That said. Maureen makes very good points about better meeting the needs of ALAC members. When we attend ICANN meetings in person, we are physically in the same place/same timezone and can attend all of the sessions. But when meetings are online, we are physically scattered across the globe and still doing the activities/jobs for a normal day and then trying to fit ICANN meetings around normal days (for me, anyway, not necessarily in convenient timezones) - So meeting ALAC needs in those circumstances is also important.<div class=""><br class=""></div><div class="">Maybe as part of a review of the meeting, look at how we can be ALAC inclusive for its members - as well as part of ICANN meetings</div><div class=""><br class=""></div><div class="">Holly<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Oct 12, 2021, at 5:53 AM, Sebicann Bachollet via ALAC <<a href="mailto:alac@atlarge-lists.icann.org" class="">alac@atlarge-lists.icann.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hello<div class="">I would like to add that some of us suggested 3 Plenary sessions.</div><div class="">Two were decided and then one of them was postponed (and not replace).</div><div class="">Therefor the argument that our policy sessions are of interest for the whole community is normal as At-Large take the 3 topics suggested for the plenary sessions.</div><div class="">And yes we are inviting member from other constituencies to At-Large Policy sessions.</div><div class="">And we hope that a lot of them will be part both as speaker or participant.<br class=""><div class="">
<div dir="auto" style="caret-color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">All the best<div class="">SeB<br class=""><br class="">Sébastien Bachollet<br class="">+33 6 07 66 89 33<br class=""><div class=""><a href="mailto:sebicann@bachollet.fr" class="">sebicann@bachollet.fr</a></div><div class="">@SebBach</div><div class=""><br class=""></div><div class="">EURALO Chair</div><div class=""><br class=""></div></div></div><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">
</div>
<div class=""><br class=""><blockquote type="cite" class=""><div class="">Le 11 oct. 2021 à 19:49, Maureen Hilyard via ALAC <<a href="mailto:alac@atlarge-lists.icann.org" class="">alac@atlarge-lists.icann.org</a>> a écrit :</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hi Olivier and all<div class=""><br class=""></div><div class="">Well that sounds like that was an interesting meeting, and great to see that what At-Large is doing is being seen as impacting to some level of importance on other areas of ICANN. </div><div class=""><br class=""></div><div class=""><b class="">ICANN decided that the meeting was going to be over three weeks.</b> The ICANN community is now experiencing its sixth virtual meeting, and half of the community live outside of the European and the US time zones. Not surprisingly, ICANN statistics have shown that the attendance by the other half of the world has not been great. For At-Large, I wanted to look at how we could use the ICANN meeting time more effectively to get more attendance and participation among those members who have not or could not attend even our own sessions at ICANN meetings. Naturally, we would welcome participants from other communities to join into our sessions and hope that they do not feel disadvantaged by our making use of what is considered to still be within the ICANN meeting timeframe.</div><div class=""><br class=""></div><div class="">The week in between Prep Week and the ICANN meeting, despite whatever purpose ICANN originally intended, was created as the At-Large Week for the convenience of our community members whom we are encouraging to attend <u class="">our</u> sessions at least. It has given us an opportunity to experiment and do something different that considers our community of volunteers first, and to look at how it might impact their participation and attendance. Because they are real volunteers, many cannot sustain the timeframe of a full-on ICANN meeting even over four days. </div><div class=""><br class=""></div><div class="">Because of my lone timezone, I myself have found that trying to stay awake across a block of nearly 10 hours in the middle of the night to attend irregular sessions has been very difficult, and more so when I have also had to work during my daylight hours. It has taken me at least a couple of weeks to get back to some sort of normality after a meeting. </div><div class=""><br class=""></div><div class="">The At-Large week schedule is being held during what is our normal At-Large meeting times and at a more manageable load of two sessions a day. Our sessions do not conflict with other ICANN community sessions as they normally do when we participate in an ICANN meeting. At-Large involvement in the ICANN meeting this time is minimal and enables our members to attend other community sessions and to learn about what is of interest to the rest of the ICANN community. Our social media working group will be doing its best to ensure that other ICANNN communities are informed of our sessions as well as those of other communities that might be of interest to At-Large.</div><div class=""><br class=""></div><div class="">I find it interesting that at a time when ICANN itself is asking the wider community how they think future meetings will be held, that some ICANNers are persisting that other communities must fit their expectations. Fortunately, we have been given an opportunity to consider what best meets the needs of our community first. There were no objections made when it was first raised at the SOAC meeting nor during our own planning sessions. However, if we find at the end of the ICANN meeting that it had no real effect then so be it. Back to the drawing board. </div><div class=""><br class=""></div><div class="">I hope that helps.</div><div class="">Regards</div><div class="">Maureen</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Oct 12, 2021 at 4:16 AM Olivier MJ Crépin-Leblond <<a href="mailto:ocl@gih.com" class="">ocl@gih.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class="">
Dear Maureen,<br class="">
<br class="">
I am just off a call with UK ICANN Stakeholders, a sort of an ICANN
Read-Out with selected UK based ICANN participants, and I shared the
At-Large Activities, both during the ICANN week, but also in the
so-called "At-Large Week".<br class="">
Whilst there were congratulatory remarks all about for the At-Large
to convene such interesting sessions, two comments, from Susan Payne
and Chris Disspain questioned the organising of the "At-Large Week".
Susan, in particular, explained that the ICANN72 organising
committee debated at length how long the ICANN meetign should be,
whether it should be a short meeting or a longer one and the
consensus that was reached across SO/AC/SG was to have a shorter
ICANN week that was 4 days in length. <br class="">
I explained that for the At-Large Community, 4 days were impractical
as it had to conduct its own business whilst offering its community
the ability to attend plenaries, official meetings of the Board,
public forum etc. So the At-Large week was primarily organised for
At-Large participants but open to everyone, as in many At-Large
meetings. This did not quite satisfy Susan nor Chris: both said that
the topics and line-ups of these meetings were very interesting, yet
they were not on the public meeting schedule and it would be
interesting if they were, so as for many more participants to be
able to attend them. Chris in particular mentioned that if members
of the ICANN Board were attending these meetings, they should be
part of the overall ICANN Schedule. But of course, that cannot
happen since this is not technically part of the ICANN meeting.<br class="">
<br class="">
So I didn't know what to say. How are the At-Large Week meetings
going to be advertised? Are the At-Large happy to have anyone
attend? How do you respond to those who say that the At-Large has
effectively created, in its policy sessions, more potential plenary
ICANN sessions outside the ICANN plenary session schedule, as it has
invited guests from across SOs/ACs/SGs etc?<br class="">
<br class="">
Kindest regards,<br class="">
<br class="">
Olivier<br class="">
<br class="">
</div>
</blockquote></div>
_______________________________________________<br class="">ALAC mailing list<br class=""><a href="mailto:ALAC@atlarge-lists.icann.org" class="">ALAC@atlarge-lists.icann.org</a><br class=""><a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" class="">https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br class=""><br class="">At-Large Online: <a href="http://www.atlarge.icann.org" class="">http://www.atlarge.icann.org</a><br class="">ALAC Working Wiki: <a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" class="">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a><br class="">_______________________________________________<br class="">By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://www.icann.org/privacy/policy" class="">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" class="">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</div></blockquote></div><br class=""></div></div></div>_______________________________________________<br class="">ALAC mailing list<br class=""><a href="mailto:ALAC@atlarge-lists.icann.org" class="">ALAC@atlarge-lists.icann.org</a><br class="">https://atlarge-lists.icann.org/mailman/listinfo/alac<br class=""><br class="">At-Large Online: http://www.atlarge.icann.org<br class="">ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)<br class="">_______________________________________________<br class="">By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</div></blockquote></div><br class=""></div></div></body></html>