<html>
<body>
Noting that this discussion was triggered by the RoP revision but is not
a part of it - any decisions on how individual members are handled (if
indeed we decide that this is an ALAC matter and not a RALO matter as is
currently the case) will come out of either the At-Large Review
Implementation r other follow-on activities.<br><br>
But to put add my own comments. Seun is right that it can be done in a
relatively uncumbersome way. But you lose the ability of telling a new
possible eager person that they are now a member (and not have to wait
for the periodic approval. And more to the point, if the ALAC will not
actually look at each prospective new member, case by case, what are we
getting for the new process?<br><br>
Alan<br><br>
At 10/10/2018 01:18 PM, Seun Ojedeji wrote:<br>
<blockquote type=cite class=cite cite="">Sent from my mobile<br>
Kindly excuse brevity and typos<br><br>
On Wed, 10 Oct 2018, 17:24 Olivier MJ Crépin-Leblond,
<<a href="mailto:ocl@gih.com">ocl@gih.com</a>> wrote:<br>
<dl>
<dd>Dear Seun,<br><br>
<dd>sorry just catching up with old emails.<br>
<dd>The procedure which you mention below, Seun, seems to be really heavy
handed. You are speaking of ALAC ratification for every individual
member? Do you realise that EURALO, for example, has in excess of 30
individual members handled by the EURALO individuals association. I could
not imagine getting the ALAC to vote on each and every individual
application.<br>
<dd>The way we have done it in EURALO is to delegate the task of handling
individual users to a purpose built structure and they have conducted the
process which you have listed below, by individual users, for individual
users. I realise that there are always pressures for centralisation, but
in this sort of process, I really think delegation and decentralisation
is the key to good growth whilst keeping the administrative workload of
the ALAC to a manageable level.<br><br>
</dl><br>
SO: Olivier, it depends on how much details ALAC is looking into;
ratification can simply mean approving the recommendation of that group
you said already does it and it can simply be to affirm if they have
followed the review process. Secondly ratification for individual members
can be done in bulk on periodic basis, that way it won't require voting
on each individual (but chance to exclude any controversial individual
may need to be included)<br><br>
Overall I don't think this process needs to be cumbersome, it all depends
on how much details ALAC will be required to look at before ratification.
On a lighter note, 30 isn't so much a big number to consider :-)<br><br>
Thanks<br><br>
<dl>
<dd>Kindest regards,<br><br>
<dd>Olivier<br><br>
<dd>On 05/10/2018 16:21, Seun Ojedeji wrote:<br>
<blockquote type=cite class=cite cite="">
<dd>While the uniform process still needs to be detailed, am in support
of such line of thought which I can summarize as follows: <br><br>
<dd>- EOI submission<br>
<dd>- Staff due diligence<br>
<dd>- Staff notification on RALO list, with the intent of confirming if
the applicant is not an ALS member<br>
<dd>- RALO approval for ALAC ratification<br>
<dd>- ALAC ratification<br><br>
<dd>Regards<br>
<dd>Sent from my mobile<br>
<dd>Kindly excuse brevity and typos<br><br>
<dd>On Fri, 5 Oct 2018, 14:44 Dev Anand Teelucksingh,
<<a href="mailto:devtee@gmail.com">devtee@gmail.com</a>>
wrote:<br>
<dl>
<dd>Something to file for the discussions then<br><br>
<dd>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 <br>
<dd>- a common online application form in the 6un languages on the at
large website<br>
<dd>- the ralos provide regional advice after staff due diligence is sent
to the ralos for their advice <br>
<dd>- the ALAC votes whether to accept the regional advice or
not<br><br>
<dd>Dev Anand<br><br>
<br><br>
<dd>On Fri, 5 Oct 2018 at 4:29 AM, Maureen Hilyard
<<a href="mailto:maureen.hilyard@gmail.com">
maureen.hilyard@gmail.com</a>> wrote:<br>
<dl>
<dd>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. <br><br>
<dd>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.<br><br>
<dd>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.<br><br>
<dd>Maureen<br><br>
<dd>On Wed, Oct 3, 2018 at 11:44 AM Alan Greenberg
<<a href="mailto:alan.greenberg@mcgill.ca">alan.greenberg@mcgill.ca</a>
> wrote:<br>
<dl>
<dd>Thanks Ricardo,<br><br>
<dd>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>
<dd>Alan<br><br>
<dd>At 03/10/2018 10:29 AM, Ricardo Holmquist wrote:<br><br>
<blockquote type=cite class=cite cite="">
<dd>Good day Alan,<br>
<dd>Thanks so much for the revision.<br><br>
<dd>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>
<dd>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>
<dd>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>
<dd>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>
<dd>Best<br><br>
<dd>Ricardo Holmquist<br><br>
<dd>El mar., 2 oct. 2018 a las 18:46, Alan Greenberg
(<<a href="mailto:alan.greenberg@mcgill.ca">
alan.greenberg@mcgill.ca</a>>) escribió:
<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>
<dd>To summarize, our overall rule set includes:<br>
<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>
<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>
<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>
<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>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>
<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>
<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>
<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>
<dd>Attached is the redline revision of the RoP as well as a Change Log
explaining each of the changes.<br>
<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>
<dd>Alan<br>
<dd>_______________________________________________
<dd>ALAC mailing list
<dd><a href="mailto:ALAC@atlarge-lists.icann.org">
ALAC@atlarge-lists.icann.org</a>
<dd>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" eudora="autourl">
https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br>
<dd>At-Large Online:
<a href="http://www.atlarge.icann.org">http://www.atlarge.icann.org</a>
<dd>ALAC Working Wiki:
<a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+%28ALAC%29">
https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a>
<br><br>
</dl>
<dd>Content-Type: image/jpeg; name="capture email guide
2.JPG"<br>
<dd>Content-Disposition: attachment; filename="capture email guide
2.JPG"<br>
<dd>Content-ID: <f_jmt2hr8w0><br>
<dd>X-Attachment-Id: f_jmt2hr8w0<br><br>
<dd>Content-Type: image/jpeg; name="capture email
guide.JPG"<br>
<dd>Content-Disposition: attachment; filename="capture email
guide.JPG"<br>
<dd>Content-ID: <f_jmt2hr9a1><br>
<dd>X-Attachment-Id: f_jmt2hr9a1<br><br>
<dd>_______________________________________________<br>
<dd>ALAC mailing list<br>
<dd><a href="mailto:ALAC@atlarge-lists.icann.org">
ALAC@atlarge-lists.icann.org</a><br>
<dd>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" eudora="autourl">
https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br><br>
<dd>At-Large Online:
<a href="http://www.atlarge.icann.org/">http://www.atlarge.icann.org</a>
<br>
<dd>ALAC Working Wiki:
<a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+%28ALAC">
https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC</a>
)</blockquote>
<dd>_______________________________________________<br>
<dd>ALAC mailing list<br>
<dd><a href="mailto:ALAC@atlarge-lists.icann.org">
ALAC@atlarge-lists.icann.org</a><br>
<dd>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" eudora="autourl">
https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br><br>
<dd>At-Large Online:
<a href="http://www.atlarge.icann.org">http://www.atlarge.icann.org</a>
<br>
<dd>ALAC Working Wiki:
<a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+%28ALAC%29">
https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a>
<br><br>
</dl>
<dd>_______________________________________________<br>
<dd>ALAC mailing list<br>
<dd><a href="mailto:ALAC@atlarge-lists.icann.org">
ALAC@atlarge-lists.icann.org</a><br>
<dd>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" eudora="autourl">
https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br><br>
<dd>At-Large Online:
<a href="http://www.atlarge.icann.org">http://www.atlarge.icann.org</a>
<br>
<dd>ALAC Working Wiki:
<a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+%28ALAC%29">
https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a>
<br><br>
</dl>
<dd>_______________________________________________<br>
<dd>ALAC mailing list<br>
<dd><a href="mailto:ALAC@atlarge-lists.icann.org">
ALAC@atlarge-lists.icann.org</a><br>
<dd>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" eudora="autourl">
https://atlarge-lists.icann.org/mailman/listinfo/alac</a><br><br>
<dd>At-Large Online:
<a href="http://www.atlarge.icann.org">http://www.atlarge.icann.org</a>
<br>
<dd>ALAC Working Wiki:
<a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+%28ALAC%29">
https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a>
<br><br>
</dl><br><br>
<br>
<dd><pre>_______________________________________________
<dd>ALAC mailing list
<dd><a href="mailto:ALAC@atlarge-lists.icann.org">
ALAC@atlarge-lists.icann.org</a>
<dd>
<a href="https://atlarge-lists.icann.org/mailman/listinfo/alac" eudora="autourl">
https://atlarge-lists.icann.org/mailman/listinfo/alac</a>
<dd>At-Large Online:
<a href="http://www.atlarge.icann.org">http://www.atlarge.icann.org</a>
<dd>ALAC Working Wiki:
<a href="https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)">
https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)</a>
</pre></blockquote><br><br>
<dd><pre>--
<dd>Olivier MJ Crépin-Leblond, PhD
<dd><a href="http://www.gih.com/ocl.html">http://www.gih.com/ocl.html</a>
</pre>
</dl></blockquote></body>
</html>