<div dir="ltr"><div class="gmail_default" style="font-size:small;color:#20124d">I believe the concept of Individual membership spans across almost all RALOs. If we have one form where members sign up and select the region, then automatically the name sent to the respective RALOs. <br></div><div class="gmail_default" style="font-size:small;color:#20124d">I think the process should be simplified. <br></div><div class="gmail_default" style="font-size:small;color:#20124d">Definitely Satish, it could be an idea that is worth implementing when it comes to cleaning up the lists and making the lists organised. <br></div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, 5 Oct 2018 at 17:11, Satish Babu <<a href="mailto:sb@inapp.com">sb@inapp.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>A few related points:</div><ul><li>Given the possibility that numbers could be non-trivial compared to ALS applications, and also given that different RALOs could have criteria specific to them, should the individual member admissions be left to each RALO?</li><li>Should we have an ALAC-level roster of all individual members so that we can detect overlaps?</li><li>Although not directly related to membership, should we also clean up RALO-level community mailing lists and convert existing mailing list members who are neither individual members nor RALO representatives, to consider becoming individual members?</li></ul><div><br></div><div><br></div><div><br></div><div><br></div><div>satish<br></div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Oct 5, 2018 at 7:14 PM Dev Anand Teelucksingh <<a href="mailto:devtee@gmail.com" target="_blank">devtee@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div dir="auto">Something to file for the discussions then</div><div dir="auto"><br></div><div dir="auto">To me, the individual membership should be done in a equivalent manner for Organisations applying to be Accredited as a member of the at large community </div></div><div dir="auto">- a common online application form in the 6un languages on the at large website</div><div dir="auto">- the ralos provide regional advice after staff due diligence is sent to the ralos for their advice </div><div dir="auto">- the ALAC votes whether to accept the regional advice or not</div><div dir="auto"><br></div><div dir="auto">Dev Anand</div><div dir="auto"><br></div><div dir="auto"><br></div><div><br><div class="gmail_quote"><div dir="ltr">On Fri, 5 Oct 2018 at 4:29 AM, Maureen Hilyard <<a href="mailto:maureen.hilyard@gmail.com" target="_blank">maureen.hilyard@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I agree that individual membership as well as ALS registration details still need to be discussed further and this was certainly going to be on my "to do" list.<div><br></div><div>But I do not think that any real changes to the ROPs can be made at this time without full consultation with everyone, especially when some RALOs are still discussing it within their own membership lists.</div><div><br></div><div>The issue of defining / redefining different types of membership (affiliated and unaffiliated individual members as well as of ALSes) should be incorporated into the implementation plan, under Item #2 which looks at individual participation.</div></div><div dir="ltr"><div><br></div><div>Maureen<br></div></div><br><div class="gmail_quote"><div dir="ltr">On Wed, Oct 3, 2018 at 11:44 AM Alan Greenberg <<a href="mailto:alan.greenberg@mcgill.ca" target="_blank">alan.greenberg@mcgill.ca</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
Thanks Ricardo,<br><br>
You may be right that 1.1 needs more than a few words inserted to have it
make full sense. I will look at it.<br><br>
Alan<br><br>
At 03/10/2018 10:29 AM, Ricardo Holmquist wrote:<br><br>
<blockquote type="cite" class="m_1574084647712335928m_641006652980102851m_-7939173438500427609m_239064551904787459cite">Good day Alan,<br>
Thanks so much for the revision.<br><br>
I have one comment for the Introduction, where a phrase concerning the
approval of the Individual members seems to be missing (Being it an RALO
approval, an ALAC Approval, a Committee Approval or what the RALO
establishes in its own RoP).<br><br>
About the Email guide, attached is a screen capture of the At Large email
list (capture email guide), there is a missing "a" on the
"may de-subscribe" line. It then its repeated in the rest of
the lists from there on.<br>
Also on the Email Guide, almost at the end, in one of the corrections
(capture email guide 2) it should say ALAC-Internal, and not just
ALAC.<br>
In the same guide, about all the RALO lists (and also the At Large list),
there is no direct inclusion of the Individual members. I understand that
for EURALO (Not sure how the other RALO works, and LACRALO is still
deciding how), it works like an ALS, where a representative is named to
vote on EURALO instances, but I will also understand that in any RALO if
an individual is asking to be a member, is not because he wants a
"virtual" ALS, but because he wants to interact directly. Yes,
I am aware anyone can auto subscribe, but it is just another step in the
recognition of the individual users to include him in the list once
approved.<br><br>
Best<br><br>
Ricardo Holmquist<br><br>
El mar., 2 oct. 2018 a las 18:46, Alan Greenberg
(<<a href="mailto:alan.greenberg@mcgill.ca" target="_blank">
alan.greenberg@mcgill.ca</a>>) escribió:<br>
<dl>
<dd>As I am about to relinquish the honor of being the Chair of the ALAC,
I would like to leave things in reasonable order. There are a number of
overdue changes needed to the Rules of Procedure (RoP) and associated
documents.<br><br>
</dd><dd>To summarize, our overall rule set includes:<br><br>
</dd><dd>Rules of Procedure: We have a backlog of correction,
clarifications and changes to address issues that have arisen or to bring
the RoP in line with current practices.<br><br>
</dd><dd>Adjunct Document 01: "Position Description for ALAC Members,
Liaisons and Appointees" I expect to be considered by the ARIWG
in relation to Issue 16 (Metrics)<br><br>
</dd><dd>Adjunct Document 02: "Metrics and Remedial Actions for ALAC
Members and Appointees" was never written but to the extent it
is needed, it should also be considered in relation to Issue 16.<br><br>
</dd><dd>Adjunct Document 03: "At-Large Board Member Selection
Implementation" should not need any immediate attention. The
Selection process was referenced in the Review (Issue 6) but our proposal
that was accepted by the Board disagreed with the Review Team and said
that we will not address it in the Review Implementation. We may of
course re-open that discussion at any point in the future if changes is
needed.<br><br>
</dd><dd>Adjunct Document 04: "At-Large Structure Framework"
will no doubt be reviewed and likely changed as part of addressing Review
Issue 2 (ALS and Individual Membership).<br><br>
</dd><dd>ALAC E-mail Guide: There are a number of corrections and changes
needed to being the document in line with current ALAC practice (and
reduce routine work).<br><br>
<br><br>
</dd><dd>Accordingly I am proposing a set of changes to the ALAC Rules of
Procedure and the ALAC E-mail Guide. The RoP call for at least 21
calendar days notice and and this message will allow us to vote on the
amendments at the Wrap-Up Session in Barcelona. There will also be time
allocated for discussion in Barcelona, but hopefully any need for change
can be brought up and resolved via e-mail prior to travel. <br><br>
</dd><dd>I will do a very brief overview of the changes on the ALAC call later
today, and we can have a dedicated call if people wish.<br><br>
</dd><dd>Attached is the redline revision of the RoP as well as a Change Log
explaining each of the changes.<br><br>
</dd><dd>Also attached is the redline E-mail Guide. All of the changes are
either clear corrections or changes to reflect current practice (such as
including the any ALT Advisor in the ALT or ALAC lists, and including key
working group chairs in the ALAC list).<br><br>
</dd><dd>Alan<br><br>
</dd><dd>_______________________________________________<br>
</dd><dd>ALAC mailing list<br>
</dd><dd><a href="mailto:ALAC@atlarge-lists.icann.org" target="_blank">
ALAC@atlarge-lists.icann.org</a><br>
</dd><dd>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" target="_blank">
https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br><br>
</dd><dd>At-Large Online:
<a href="http://www.atlarge.icann.org" target="_blank">http://www.atlarge.icann.org</a>
<br>
</dd><dd>ALAC Working Wiki:
<a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" target="_blank">
https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a>
<br><br>
</dd></dl>Content-Type: image/jpeg; name="capture email guide
2.JPG"<br>
Content-Disposition: attachment; filename="capture email guide
2.JPG"<br>
Content-ID: <f_jmt2hr8w0><br>
X-Attachment-Id: f_jmt2hr8w0<br><br>
Content-Type: image/jpeg; name="capture email guide.JPG"<br>
Content-Disposition: attachment; filename="capture email
guide.JPG"<br>
Content-ID: <f_jmt2hr9a1><br>
X-Attachment-Id: f_jmt2hr9a1<br><br>
_______________________________________________<br>
ALAC mailing list<br>
<a href="mailto:ALAC@atlarge-lists.icann.org" target="_blank">ALAC@atlarge-lists.icann.org</a><br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" target="_blank">
https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br><br>
At-Large Online:
<a href="http://www.atlarge.icann.org/" target="_blank">
http://www.atlarge.icann.org</a><br>
ALAC Working Wiki:
<a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC" target="_blank">
https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC</a>
)</blockquote></div>
_______________________________________________<br>
ALAC mailing list<br>
<a href="mailto:ALAC@atlarge-lists.icann.org" target="_blank">ALAC@atlarge-lists.icann.org</a><br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" rel="noreferrer" target="_blank">https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br>
<br>
At-Large Online: <a href="http://www.atlarge.icann.org" rel="noreferrer" target="_blank">http://www.atlarge.icann.org</a><br>
ALAC Working Wiki: <a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" rel="noreferrer" target="_blank">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a></blockquote></div>
_______________________________________________<br>
ALAC mailing list<br>
<a href="mailto:ALAC@atlarge-lists.icann.org" target="_blank">ALAC@atlarge-lists.icann.org</a><br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" rel="noreferrer" target="_blank">https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br>
<br>
At-Large Online: <a href="http://www.atlarge.icann.org" rel="noreferrer" target="_blank">http://www.atlarge.icann.org</a><br>
ALAC Working Wiki: <a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" rel="noreferrer" target="_blank">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a></blockquote></div></div>
_______________________________________________<br>
ALAC mailing list<br>
<a href="mailto:ALAC@atlarge-lists.icann.org" target="_blank">ALAC@atlarge-lists.icann.org</a><br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" rel="noreferrer" target="_blank">https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br>
<br>
At-Large Online: <a href="http://www.atlarge.icann.org" rel="noreferrer" target="_blank">http://www.atlarge.icann.org</a><br>
ALAC Working Wiki: <a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" rel="noreferrer" target="_blank">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a></blockquote></div>
_______________________________________________<br>
ALAC mailing list<br>
<a href="mailto:ALAC@atlarge-lists.icann.org" target="_blank">ALAC@atlarge-lists.icann.org</a><br>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" rel="noreferrer" target="_blank">https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br>
<br>
At-Large Online: <a href="http://www.atlarge.icann.org" rel="noreferrer" target="_blank">http://www.atlarge.icann.org</a><br>
ALAC Working Wiki: <a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)" rel="noreferrer" target="_blank">https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a></blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>Nanghaka Daniel K.<br><span style="font-size:small">Executive Director - ILICIT Africa/ Chair - Outreach and Engagement WG (ICANN At-Large)</span><span style="font-size:small;letter-spacing:0.2px">/ former Chair - FOSSFA</span><span style="font-size:small;letter-spacing:0.2px"> </span><span style="font-size:small;letter-spacing:0.2px"> / Geo4Africa Lead / Organising Team - FOSS4G2018</span></div><div>Mobile +256 772 898298 (Uganda)<br></div><div>Skype: daniel.nanghaka<br></div><div><br></div><div>----------------------------------------- <i><span>"Working for Africa" </span></i>-----------------------------------------<br> <br><br></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>