Hi Andrew, Gigi,

Thanks for those comments.
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.

What I am getting regularly (other NCSG officer may get them directly for
some cases) , trying to summarise roughly here:
- 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.

- 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.
- I also receive sometimes emails about ICANN blog posts or special
announcement (probably those more close to PR thing) .

and this list is still non-exhaustive!

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.

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 (ncsg.is)
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.

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.
On other hand, members can share other ICANN public info they see relevant
and worthy to discuss.
More work ahead :)

Best Regards,

Rafik Dammak

NCSG chair






2015-05-20 8:46 GMT+09:00 Andrew A. Adams <[log in to unmask]>:

> Perhaps we could set up an NCSG-ICANN-Announce mailing list to which NCSG
> members are entitled (but not required) to subscribe (we could start by
> subscribing all members of NCSG-Discuss and automatically adding new
> members
> to both lists, but allow self-unsubscription from the announce list). We
> could then allow posting to that list by ICANN staff (whether Maryam and/or
> others) of information that ICANN staff would like to send to NCSG members
> (who wish to receive such communications). This would keep our internal
> discussion list for our business but allow a formal and clearly separate
> channel for ICANN to send communications to our members.
>
> I've used a similar arrangement for other groups such as ACM SIGCAS where
> there is a commitee announcement list with limited posting privileges, but
> also a member-member discussion list to which all members can subscribe and
> post.
>
>
> --
> Professor Andrew A Adams                      [log in to unmask]
> Professor at Graduate School of Business Administration,  and
> Deputy Director of the Centre for Business Information Ethics
> Meiji University, Tokyo, Japan       http://www.a- .info/
> <http://www.a-cubed.info/>
>