<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<div dir="auto">Very much in agreement with what is expressed here, in journalism they teach us the importance of a good title and subtitle. A good title with keywords, may attract attention and many participate in our meetings.
<div dir="auto"><br>
<div dir="auto"> It is also very important that the Newcomers, Next Gen Fellows and general participants of the ICANN meetings are linked to the meetings of At Large and know what we do and that are linked to this important work within the gear of the ICANN
is also important within of the commitment and involvement process that the Newcomers Next Gen and fellow especially, know and adhere to the different working groups of At Large. The goal is for our community to grow and strengthen.
<div dir="auto">
<div dir="auto"><br>
</div>
<div dir="auto">Regards,</div>
<div dir="auto"><br>
</div>
<div dir="auto">Lilian Ivette De Luque Bruges</div>
<div dir="auto">LACRALO Member</div>
<div dir="auto"><br>
</div>
</div>
</div>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">El 21 nov. 2018 2:54 p. m., Judith Hellerstein <judith@jhellerstein.com> escribió:<br type="attribution">
<blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<p>HI Dev,</p>
<p>I agree with you and have been suggesting changes to this for a while. Staff puts these in as placeholders until the schedule is finalized. I also would like to see them changed and list the topics that are being discussed at the meeting. The At Large response
has been to tell people not to look at that schedule but the At Large schedule and that is not necessarily a correct answer. It is fine to leave it generic at the beginning but then we should fill it out with the topics covered so people who do not know to
look at the at large schedule see what we will be talking about and then come or not come as is their preference. However, at least when we go for more descriptive they can make a more informed decision</p>
<p>Best,</p>
<p>Judith<br>
</p>
<pre>_________________________________________________________________________
Judith Hellerstein, Founder & CEO
Hellerstein & Associates
3001 Veazey Terrace NW, Washington DC 20008
Phone: (202) 362-5139 Skype ID: judithhellerstein
Mobile/Whats app: +1202-333-6517
E-mail: <a href="mailto:Judith@jhellerstein.com">Judith@jhellerstein.com</a> Website: <a href="http://www.jhellerstein.com">www.jhellerstein.com</a>
Linked In: <a href="http://www.linkedin.com/in/jhellerstein/">www.linkedin.com/in/jhellerstein/</a>
Opening Telecom & Technology Opportunities Worldwide
</pre>
<div>On 11/20/2018 12:27 PM, Dev Anand Teelucksingh wrote:<br>
</div>
<blockquote>
<div dir="ltr">
<div>One suggestion for the O&E to fix is the issue of how our At-Large/ALAC meetings are listed in the schedule at ICANN F2F meetings.
<br>
</div>
<div dir="ltr"><br>
Consider ICANN61. There is a session at <a href="https://61.schedule.icann.org/meetings/647710">
https://61.schedule.icann.org/meetings/647710</a> titled "ALAC and Regional Leaders Working Session Part 1"<br>
This is the descriptive text that newcomers, fellows will see <br>
"The Members of the ALAC and the Regional Leadership will discuss policy and process issues of importance to them. These sessions will also include presentations by senior staff."<br>
<br>
Why should any newcomers, ICANN fellows, nextgen care to attend this ? <br>
</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">The description says nothing what the ALAC is, only says the ALAC will discuss stuff important to them, implying its like a closed meeting and we're not talking anything of importance to newcomers to attend.
<br>
</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">So we should work to change this descriptive text. <br>
</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">Also, the title of our sessions "ALAC and Regional Leaders Working Session Part 1", Part 2, Part 3, Part 4, etc etc.<br>
</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">I know its hard to finalize agendas in a timely manner, but can we come up with better descriptive text for these names? We tend (or should) group these Working Sessions under a particular theme or subject - Security, new gTLD policy, Finance
for example and we should therefore have the subject or theme in the title of the sessions.<br>
<br>
Also, instead of "ALAC and Regional Leaders" which again gives a "if you're not a ALAC or Regional Leader, you are NOT welcome" vibe, so lets make it more inviting...perhaps "At-Large Community (ALAC)"
<br>
<br>
</div>
<div>This may seem tedious, but I think it would have huge benefit to At-Large. Once created however, we can use the improved description and titles going forward for future ICANN F2F meetings.</div>
<div><br>
</div>
<div>Dev Anand Teelucksingh<br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
<br>
<fieldset></fieldset> <br>
<pre>_______________________________________________
Alac-sc-outreach mailing list
<a href="mailto:Alac-sc-outreach@atlarge-lists.icann.org">Alac-sc-outreach@atlarge-lists.icann.org</a>
<a href="https://mm.icann.org/mailman/listinfo/alac-sc-outreach">https://mm.icann.org/mailman/listinfo/alac-sc-outreach</a>
</pre>
</blockquote>
<br>
</div>
</blockquote>
</div>
<br>
</div>
</body>
</html>