[ALAC] FW: Fwd: Cherine Chalaby to Alan Greenberg RE: GAC-ALAC Joint Statement of 2 Nov 2017

Alan Greenberg alan.greenberg at mcgill.ca
Sat Feb 17 20:53:52 UTC 2018 

I agree that it would have to be staff-led, but 
there would likely need to be volunteer 
involvement. If we could flesh this out a bit, we 
could include it as part of the At-Large improvements implementation.

I suspect monthly might be pushing thisg. We 
could also do it irregularly when there are 
sufficient updates or when particular input is 
required. The last thing we want to do is publish 
a newsletter that people quickly decide had no 
real content and thuse decide to ignore it in the future.

Alan

At 17/02/2018 11:48 AM, Maureen Hilyard wrote:

>A monthly ALAC newsletter would be a good idea, 
>based on the outcomes of our monthly call - that 
>not many non-ALAC or RALO leaders attend.  But 
>while RALO newsletters could focus on what is 
>happening in their regions, the ALAC newsletter 
>could focus on more high-level issues and 
>looking at what the ALAC thinking is at the 
>moment with regards to these issues. Only briefs 
>- we don't want to bore people to death, but giving them the hightlights.
>
>Of course this would have to be a staff 
>responsibility because I can't see anyone having 
>the time to add that to their ALAC and day jobs.
>
>M
>
>On Fri, Feb 16, 2018 at 6:35 AM, Vanda 
>Scartezini <<mailto:vanda at scartezini.org>vanda at scartezini.org> wrote:
>
>Our region also have one for all ICANN related 
>issues in the region not only LACRALO, but also 
>LACNIC, LACTLDs,  LACNOG , IGFS around and related..
>
>I guess an ALAC newsletter shall have links to 
>all othere regional newsletter in order to 
>promote our work that I continue to see as quite 
>ignored by ICANN”s community outside Ralos 

>
>Kisses
>
>From: ALAC 
><<mailto:alac-bounces at atlarge-lists.icann.org>alac-bounces at atlarge-lists.icann.org> 
>on behalf of Judith Hellerstein 
><<mailto:judith at jhellerstein.com>judith at jhellerstein.com>
>Date: Tuesday, February 13, 2018 at 20:35
>To: Vanda Scartezini <<mailto:vanda at scartezini.org>vanda at scartezini.org>
>Cc: 'ALAC List' 
><<mailto:alac at atlarge-lists.icann.org>alac at atlarge-lists.icann.org>
>Subject: Re: [ALAC] FW: Fwd: Cherine Chalaby to 
>Alan Greenberg RE: GAC-ALAC Joint Statement of 2 Nov 2017
>
>
>
>Hi all
>
>Naralo has a newsletter and this is good info for our newsletter
>
>
>
>Best
>
>Judith
>
>Sent from my iPhone
>
><mailto:Judith at jhellerstein.com>Judith at jhellerstein.com
>
>Skype ID:Judithhellerstein
>
>
>On Feb 13, 2018, at 2:47 PM, Vanda Scartezini 
><<mailto:vanda at scartezini.org>vanda at scartezini.org> wrote:
>
>Sorry I have responded just to Holly.
>
>Kisses to all.
>
>
>
>Vanda Scartezini
>
>Polo Consultores Associados
>
><https://maps.google.com/?q=Av.+Paulista+1159&entry=gmail&source=g>Av. 
>Paulista 1159, cj 1004
>
>01311-200- Sao Paulo, SP, Brazil
>
>Land Line: <tel:+55%2011%203266-6253>+55 11 3266.6253
>
>Mobile: <tel:+55%2011%2098181-1464>+ 55 11 98181.1464
>
>Sorry for any typos.
>
>
>
>From: Vanda Scartezini <<mailto:vanda at scartezini.org>vanda at scartezini.org>
>Date: Tuesday, February 13, 2018 at 17:45
>To: Holly Raiche <<mailto:h.raiche at internode.on.net>h.raiche at internode.on.net>
>Subject: Re: [ALAC] Fwd: Cherine Chalaby to Alan 
>Greenberg RE: GAC-ALAC Joint Statement of 2 Nov 2017
>
>
>
>You right Holy, as I am reading from your 
>comments looks like we still not promoting well 
>our work. May be helpful to create newsletter 
>and send once at each 2-3 months resuming all 
>the work was done in all Ralos and ALAC itself 
>to the Board, Göran and directory and all AC/SOs “baord”members.
>
>Kisses
>
>Vanda Scartezini
>
>Polo Consultores Associados
>
><https://maps.google.com/?q=Av.+Paulista+1159&entry=gmail&source=g>Av. 
>Paulista 1159, cj 1004
>
>01311-200- Sao Paulo, SP, Brazil
>
>Land Line: <tel:+55%2011%203266-6253>+55 11 3266.6253
>
>Mobile: <tel:+55%2011%2098181-1464>+ 55 11 98181.1464
>
>Sorry for any typos.
>
>
>
>
>
>
>
>
>
>
>
>From: ALAC 
><<mailto:alac-bounces at atlarge-lists.icann.org>alac-bounces at atlarge-lists.icann.org> 
>on behalf of Holly Raiche 
><<mailto:h.raiche at internode.on.net>h.raiche at internode.on.net>
>Date: Monday, February 12, 2018 at 20:04
>To: Javier Rua <<mailto:javrua at gmail.com>javrua at gmail.com>
>Cc: 'ALAC List' 
><<mailto:alac at atlarge-lists.icann.org>alac at atlarge-lists.icann.org>, 
>Alan Greenberg <<mailto:alan.greenberg at mcgill.ca>alan.greenberg at mcgill.ca>
>Subject: Re: [ALAC] Fwd: Cherine Chalaby to Alan 
>Greenberg RE: GAC-ALAC Joint Statement of 2 Nov 2017
>
>
>
>Folks
>
>
>
>Yes, we will ned some staff support.  But one 
>thing we can easily do is that, when we respond 
>to PDPs, in the response, include in an 
>introductory paragraph what we are saying - not 
>that difficult.  And maybe point out to Cherine 
>that we already have a policy page (thanks to 
>Ariel) where what we have said is organised by 
>various topics - a start at least.
>
>
>
>Holly
>
>
>
>
>
>On 13 Feb 2018, at 2:50 am, Javier Rua 
><<mailto:javrua at gmail.com>javrua at gmail.com> wrote:
>
>
>
>
>“The Board also looks forward to discussing 
>this issue further with the ALAC and GAC at the 
>ICANN61 meeting in San Juan, Puerto Rico.”
>
>
>
>One, some or all the “issues” touched upon in the Joint Statement?
>
>
>
>
>
>
>
>Javier Rúa-Jovet
>
>
>
><tel:+1%20787-396-6511>+1-787-396-6511
>
>twitter: @javrua
>
>skype: javier.rua1
>
><https://www.linkedin.com/in/javrua>https://www.linkedin.com/in/javrua
>
>
>
>
>On Feb 12, 2018, at 11:40 AM, Evan Leibovitch 
><<mailto:evan at telly.org>evan at telly.org> wrote:
>
>"The Board also encourages the ALAC to continue 
>to lead by example in producing materials that 
>ensure effective and equal participation by all 
>stakeholders, and would encourage the ALAC to 
>include executive summaries on statements, 
>advisories, and other materials issued by the ALAC."
>
>
>
>How noble. Will the Board sufficiently resource 
>the ALAC to produce such materials and additional content?
>
>
>
>What the Board wants -- anywhere in ICANN, 
>they're able to get if it's sufficiently resourced.
>
>
>
>- Evan
>
>
>
>_______________________________________________
>ALAC mailing list
><mailto:ALAC at atlarge-lists.icann.org>ALAC at atlarge-lists.icann.org
>https://atlarge-lists.icann.org/mailman/listinfo/alac
>
>At-Large Online: <http://www.atlarge.icann.org/>http://www.atlarge.icann.org
>ALAC Working Wiki: 
><https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)>https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)
>
>_______________________________________________
>ALAC mailing list
><mailto:ALAC at atlarge-lists.icann.org>ALAC at atlarge-lists.icann.org
>https://atlarge-lists.icann.org/mailman/listinfo/alac
>
>At-Large Online: <http://www.atlarge.icann.org>http://www.atlarge.icann.org
>ALAC Working Wiki: 
><https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)>https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)
>
>
>
>_______________________________________________
>ALAC mailing list
><mailto:ALAC at atlarge-lists.icann.org>ALAC at atlarge-lists.icann.org
>https://atlarge-lists.icann.org/mailman/listinfo/alac
>
>At-Large Online: <http://www.atlarge.icann.org>http://www.atlarge.icann.org
>ALAC Working Wiki: 
><https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)>https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)
>
>_______________________________________________ 
>ALAC mailing list 
><mailto:ALAC at atlarge-lists.icann.org>ALAC at atlarge-lists.icann.org 
>https://atlarge-lists.icann.org/mailman/listinfo/alac 
>At-Large Online: 
><http://www.atlarge.icann.org>http://www.atlarge.icann.org 
>ALAC Working Wiki: 
><https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)>https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)
>
>
>Content-Type: text/plain; charset="us-ascii"
>Content-Transfer-Encoding: 7bit
>Content-Disposition: inline
>X-Microsoft-Exchange-Diagnostics:
> 
>1;YQXPR0101MB1589;27:eqDqhO9I/luauwvh0LPMdSn1/xm2vsPjQKEk0lgQ3v9M7E3BgXOTgzwGJluhS9r1D5P1UI+WNdPMF/7nowAKqWM3MxRJAGUd5iqhMDN8TZ8WYWAG3RcmrmcuQ6gLqsXp
>X-Microsoft-Antispam-Message-Info:
> 
>Cghv+DH0ORPSET06Rl0xVuVy2ShXzSQcwfUbBkWuDcs8wIp5S/l7ZLTBJXO8kygXVTZWlg2xia1dIpdIIxdUTjpKrlt4ufTIj8Yyf7vzjlQsw3XNvtgaNg/xegp/IrXRWUHGo/O1rHogCuJAZ0cGBsr7XEzFSeqUkVaN0ctr7lc=
>
>_______________________________________________
>ALAC mailing list
>ALAC at atlarge-lists.icann.org
>https://atlarge-lists.icann.org/mailman/listinfo/alac
>
>At-Large Online: http://www.atlarge.icann.org
>ALAC Working Wiki: 
>https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://atlarge-lists.icann.org/pipermail/alac/attachments/20180217/c0767c29/attachment.html>

More information about the ALAC mailing list