[APAC-Discuss] APAC-Discuss Digest, Vol 132, Issue 30

[Justine Chew]

Hi all,

Further to my earlier email, I just noticed that the APRALO Individual
Members application form mandates (approved) members to complete an
At-Large SOI (with a hyperlink to an At-Large SOI Workspace). Is this
workspace limited to the SOIs for individuals in leadership positions or
all individual members only? This At-Large SOI provides for the input on
the WGs or chartered teams which a member participates in.

This At-Large SOI is separate to the GNSO SOI then?

Thanks,

Justine Chew
-----

On 28 November 2017 at 08:37, Justine Chew <justine.chew at gmail.com> wrote:

> Hi all,
>
> Just thinking out loud.
>
> GNSO institutes and pays attention to a system of SOI - Statement of
> Interest for anyone who joins a GNSO PDP WG. Perhaps At-Large could some
> how leverage on this to extend SOI item no. 4 (ICANN Affiliation) to
> include "if you are a member of a RALO, which RALO and which ALS do you
> represent (if applicable)"? I say "leverage" because you may not want
> members to do up a duplicate At-Large SOI type profile, to avoid double
> keying-in and/or inconsistencies.
>
> ​Cheers,​
>
> Justine
> -----
>
>
>> ---------- Forwarded message ----------
>> From: Maureen Hilyard <maureen.hilyard at gmail.com>
>> To: Evin Erdogdu <evin.erdogdu at icann.org>
>> Cc: Satish Babu <sb at inapp.com>, Anupam Agrawal <
>> anupamagrawal.in at gmail.com>, APRALO <apac-discuss at atlarge-lists.icann.org
>> >
>> Bcc:
>> Date: Mon, 27 Nov 2017 07:31:41 -1000
>> Subject: Re: [APAC-Discuss] Additional Feedback on APRALO Applications
>> Hi Evin
>>
>> Actually, as people join a working group, etc they aren't necessarily
>> asked if they are a member of an ALS. They may not be a primary or
>> secondary contact.
>> We need to find some way to identify what ALSes are actually being
>> represented at our meetings. Otherwise we are not able to keep good stats
>> on participation.
>>
>> M
>>
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: Maureen Hilyard <maureen.hilyard at gmail.com>
>> To: Nadira Alaraj <nadira.araj at gmail.com>
>> Cc: Satish Babu <sb at inapp.com>, APRALO <apac-discuss at atlarge-lists.
>> icann.org>, Anupam Agrawal <anupamagrawal.in at gmail.com>
>> Bcc:
>> Date: Mon, 27 Nov 2017 08:06:43 -1000
>> Subject: Re: [APAC-Discuss] Additional Feedback on APRALO Applications
>> I have noted that some people already do that, but it would be a good
>> precedent for us to ask our members to make as a general practice. They
>> could indicate their first name and an abbreviation of their ALS if
>> possible - or some similar code that is not too long.  Thank you Nadira
>>
>> M
>>
>>
>> On Mon, Nov 27, 2017 at 7:43 AM, Nadira Alaraj <nadira.araj at gmail.com>
>> wrote:
>>
>>> Dear Maureen,
>>> Would be good practice if representatives of ALS to login to the Adobe
>>> meeting room with their first name and ALS name example: Ahmad-ALS
>>> Palestine.
>>> In this way, it will be easy to take note from the recordings of the
>>> meeting.
>>> I think there is an option in Adobe to edit the name after login. Then
>>> at the beginning of each meeting attendances ate asked to identity their
>>> affiliation to edit their name.
>>> Best,
>>> Nadira
>>>
>>>
>>> On Nov 27, 2017 19:32, "Maureen Hilyard" <maureen.hilyard at gmail.com>
>>> wrote:
>>>
>>> Hi Evin
>>>
>>> Actually, as people join a working group, etc they aren't necessarily
>>> asked if they are a member of an ALS. They may not be a primary or
>>> secondary contact.
>>> We need to find some way to identify what ALSes are actually being
>>> represented at our meetings. Otherwise we are not able to keep good stats
>>> on participation.
>>>
>>> M
>>>
>>>
>>>
>>>
>>
>> _______________________________________________
>> APAC-Discuss mailing list
>> APAC-Discuss at atlarge-lists.icann.org
>> https://atlarge-lists.icann.org/mailman/listinfo/apac-discuss
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://atlarge-lists.icann.org/pipermail/apac-discuss/attachments/20171128/868e776d/attachment-0001.html>