<div dir="ltr"><div class="gmail_extra">Hi Andrew, Gigi,</div><div class="gmail_extra"><br></div><div class="gmail_extra">Thanks for those comments.</div><div class="gmail_extra">I want to add here some clarifications about the kind of information we have to deal with and how we get them, before giving labels.</div><div class="gmail_extra"><br></div><div class="gmail_extra">What I am getting regularly (other NCSG officer may get them directly for some cases) , trying to summarise roughly here:</div><div class="gmail_extra">- from GNSO ICANN staff : the GNSO council call agenda; call for participation to join working groups; request to appoint NCSG representatives to working group , cross-community working groups , drafting teams etc; reminder about public comments. On more ad-hoc basis, direct request or questionnaire from working groups to get NCSG input about drafts or position etc. same for GNSO council itself sending requests to NCSG.</div><div class="gmail_extra"><br></div><div class="gmail_extra">- I also receive the announcement about the regular webinar like the ICANN policy update usually held before an ICANN meeting, any other webinars (like about IANA stewardship transition), the newcomers webinars to explain about participation in GNSO working group. informations related to the ICANN meetings prior and during the meetings. Also now, the summary updates made by ICANN paid consultant to highlight the work on cross-community working groups on IANA stewardship transition and ICANN accountability. The latter can be helpful for those not participating to grasp quickly what is happening there.</div><div class="gmail_extra">- I also receive sometimes emails about ICANN blog posts or special announcement (probably those more close to PR thing) .</div><div class="gmail_extra"><br></div><div class="gmail_extra">and this list is still non-exhaustive!</div><div class="gmail_extra"><br></div><div class="gmail_extra">for the 2 first kind of announcements, we usually share them with the NCSG list and our Policy Committee for those we need to make decision like appointment. for the latter, it depends about the relevance to NCSG concerns.</div><div class="gmail_extra"><br></div><div class="gmail_extra">One of the question I have for a while is what kind a format we may need to not overload members with many announcement and how we can ensure that we are acting for those relevant and critical for us. Maybe giving some context and background in addition to the existing message? maybe trying to make a digest more easy to read? maybe using our wiki space more (<a href="http://ncsg.is" target="_blank">ncsg.is</a>) for info sharing ? it is a lot of brainstorm here and it really depends of people preferences on information management. In addition to that, the overload and information and process management was also a topic for discussion with other leaders of different supporting organisation and advisory committee within ICANN.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Many of those announcements led to discussion with the list, so separating into another list may impact that. I guess we should act on ad-hoc basis and case by case. </div><div class="gmail_extra">On other hand, members can share other ICANN public info they see relevant and worthy to discuss. </div><div class="gmail_extra">More work ahead :)</div><div class="gmail_extra"><br></div><div class="gmail_extra">Best Regards,</div><div class="gmail_extra"><br></div><div class="gmail_extra">Rafik Dammak</div><div class="gmail_extra"><br></div><div class="gmail_extra">NCSG chair</div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div><div class="gmail_extra">
<br><div class="gmail_quote">2015-05-20 8:46 GMT+09:00 Andrew A. Adams <span dir="ltr"><<a href="mailto:aaa@meiji.ac.jp" target="_blank">aaa@meiji.ac.jp</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Perhaps we could set up an NCSG-ICANN-Announce mailing list to which NCSG<br>
members are entitled (but not required) to subscribe (we could start by<br>
subscribing all members of NCSG-Discuss and automatically adding new members<br>
to both lists, but allow self-unsubscription from the announce list). We<br>
could then allow posting to that list by ICANN staff (whether Maryam and/or<br>
others) of information that ICANN staff would like to send to NCSG members<br>
(who wish to receive such communications). This would keep our internal<br>
discussion list for our business but allow a formal and clearly separate<br>
channel for ICANN to send communications to our members.<br>
<br>
I've used a similar arrangement for other groups such as ACM SIGCAS where<br>
there is a commitee announcement list with limited posting privileges, but<br>
also a member-member discussion list to which all members can subscribe and<br>
post.<br>
<span><font color="#888888"><br>
<br>
--<br>
Professor Andrew A Adams <a href="mailto:aaa@meiji.ac.jp" target="_blank">aaa@meiji.ac.jp</a><br>
Professor at Graduate School of Business Administration, and<br>
Deputy Director of the Centre for Business Information Ethics<br>
Meiji University, Tokyo, Japan <a href="http://www.a-cubed.info/" target="_blank">http://www.a- .info/</a><br>
</font></span></blockquote></div><br></div></div>