<div dir="ltr">+1 @Sam.<div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2014-09-27 20:07 GMT+00:00 Sam Lanfranco <span dir="ltr"><<a href="mailto:lanfran@yorku.ca" target="_blank">lanfran@yorku.ca</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Rafik, <u></u><u></u><br>
<br>
Thanks for the useful questions and comments, and thanks to
Tapani for his comments and his expertise. Rather than making a long
response I
would like to extract the key points [numbered] for follow up. <u></u><u></u><br>
<br>
The objective is to manage these two processes while making
NCSG and its constituency groups, best practice users of the
Internet to. This
will reduce administrative demands on the various executives and
volunteers,
freeing up more time to deal with substantive and policy issues.<u></u><u></u><br>
<br>
One overarching issue has to do with how much ICANN support
and involvement does NCSG want. Is it is an issue of trust, of
efficiency, or
of optics that suggests that little be hosted on ICANN servers? This
needs to be
discussed, and decisions arrived at. There are pluses and minuses
whichever way
one goes here. <span> </span>At the moment
there are at least
three independent server sites support NCSG and constituency
services. <u></u><u></u><br>
<br>
<span><span>1.<span>
</span></span></span>We are in agreement with the
idea that there
should be one application form for NCSG that clearly states the
constituency (NCUC/NPOC/neither) membership options. <span> </span>The form can reside on NCSG, NCUC
and NPOC
websites and report back to admissions email boxes. <span> </span>With
regard to application improvements, there is no suggestion for over
engineering, and in fact the opposite. A clear and concise
application form will
expedite application by interested parties, and expedite the
admission processes
at both the NCSG and constituency levels. <u></u><u></u><br>
<u></u><u></u><br>
<span><span>2.<span>
</span></span></span>Glad to hear that application
improvement is
being discussed, including a review of appropriate fields for the
admission
process, and what fields may be needed by NCSG, NCUC and NPOC. The
key point is that
fields should serve both the admissions process and the ongoing work
of NCSG
and the constituencies. Proposals for changes here (record forms and
fields) should be shared with
NCSG members to gather member feedback and draw on member expertise.
<u></u><u></u><br>
<span></span><br>
<span><span>3.<span> </span></span></span>With regard to
maintaining
the membership database:<u></u><u></u> Best practices for maintaining
the membership
databases should put membership updating in the hands of members.
While NCSG
and the constituency groups may always have to chase laggards with
faulty
membership data, the process should have self-administered
membership profiles,
to facilitate ease of member access and to free up executive time
and talents
for more important work. <u></u><u></u><br>
<br>
<u></u><u></u><span><span>4.<span>
</span></span></span>The aution not adding fields
not directly
related to applications or aimed for specific purpose of course
makes sense.
Fields can be added when parts of the database are imported, for
local
(NCUC/NPOC) use. One way to facilitate that is for member profiles
to
contain fields for more information than just what is on the
membership
application. This doesn’t burden the application process,
facilitates profile
updates, and doesn’t take up NCSG executive time.<span> </span><u></u><u></u><br>
<br>
<u></u> <u></u><span><span>5.<span>
</span></span></span>The question of where to host
the membership database
and services is important and part of the overarching issue
referenced above. Hosting it, or not hosting it at ICANN, has
maintenance
implications, access implications, and possibly political (optics)
implications.<u></u><u></u><br>
<br>
<span><span>6.<span>
</span></span></span>The issue of database access
is not complicated.
Below the high level editing access, there can be only
edit/view/export access. NCUC and NPOC can export some/all of the
database and add whatever
they need. The NCSG Charter makes the NCSG EC and Chair responsible
for maintaining
and updating the membership database, but that does not mean that
they should use
valuable EC and Chair time to manually do what is an administrative
task. However that is done, membership
profiles would help. The current process of having members update
records by
contacting the NCSG chair is
needlessly burdensome and inefficient. <u></u><u></u><br>
<br>
<u></u> <u></u><span><span>7.<span>
</span></span></span><span> </span>With
regard to where profiles should reside, that doesn’t really matter.
The prior
issue to be resolved is what services should be mounted at ICANN, or
elsewhere,
and how profile access should be managed. The profile approach
respects the
KISS principle, gives more power to the stakeholder, and reduces
labor demands
on the executive and administration. <u></u><u></u><br>
<br>
The overall goal is to do these things efficiently and effective,
and free up executive and volunteer effort to deal with policy and
other matters of substance. <br>
<br>
Sam L. <br>
</div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Olévié Ayaovi Agbenyo KOUAMI<br>Responsable projet CERGI-Education (<a href="http://www.cergibs.com">http://www.cergibs.com</a>) <br>CEO de INTIC4DEV (<a href="http://www.intic4dev.org">http://www.intic4dev.org</a>)<br>SG de ESTETIC (<a href="http://www.estetic.tg">http://www.estetic.tg</a>)<br>Membre de ISoc (<a href="http://www.isoc.org">www.isoc.org</a> <<a href="http://www.isoc.org/">http://www.isoc.org/</a>>) & du FOSSFA (<br><a href="http://www.fossfa.net">www.fossfa.net</a>) <br>ICANN-NPOC Communications Committee Chair (<a href="http://www.icann.org/">http://www.icann.org/</a> et <a href="http://www.npoc.org/">http://www.npoc.org/</a>)<br>BP : 851 - Tél.: (228) 90 98 86 50 / (228) 98 43 27 72 <br>Skype : olevie1 FB : @olivier.kouami.3 Twitter : #oleviek Lomé – Togo<br><br>
</div>