[NCUC-EC] Fwd: Conduct at ICANN Meetings

[farzaneh badii]

Hi Rafik

for option one, it be subject to public comment? I agree with not over
engineering it .

On 19 April 2016 at 05:28, Rafik Dammak <rafik.dammak at gmail.com> wrote:

> hi everyone,
>
> with the regard to our statement about anti-harassment, there is ongoing
> discussion on how the community should work on that, the different options
> to give input to board. On other hand, GNSO council itself is drafting a
> letter to send to the interim CEO and making some suggestions about key
> points to be covered (
> http://gnso.icann.org/mailing-lists/archives/council/msg18468.html and
> http://mailman.ipjustice.org/pipermail/pc-ncsg/2016-April/003591.html)
>
> reading some reactions, not all part of communities are keen to get
> involved on working on such process and would prefer to  experts to handle
> it. On other side, I know that some of our members are eager to work on the
> issue.
>
> so the question here, it is how NCUC should do for this issue and what is
> the preferred option.
> personally, I don't have a preference and guess some mix of volunteers and
> experts to draft a policy would work, avoiding over-engineering the process
> and able to deliver quickly.
>
> Best Regards,
>
> Rafik
>
> ---------- Forwarded message ----------
>
>
>
> Dear Community Leaders:
>
>
>
> I would  like to follow up on our discussion on 12 April regarding the
> community’s involvement in developing anti-harassment language, policies
> and procedures appropriate for our global diverse community that attend
> ICANN’s meetings. ICANN staff had initially recommended that a
> community-based consultation group could be formed with the aim to gather
> information about other policies elsewhere, particularly in the Internet
> and technology conference space, that can inform further Board and
> community discussions on the topic.
>
>
>
> Several participants on the 12 April call noted, however, that in order to
> develop an appropriate policy and process, expert advice will be key. As
> such, they felt that confining these discussions to a community group which
> may lack the requisite expertise might not be the best approach.
>
>
>
> The call participants all agreed that this is nevertheless a topic that
> clearly warrants further discussion. Certainly, the ICANN Board remains
> eager to work with the community to move forward with clarifying and
> enhancing our current Expected Standards of Behavior. Staff would therefore
> like to offer the following suggestions for you and your respective
> community’s consideration as to whether any of them might be a useful way
> to continue to involve the community in this work:
>
>
> •  Convene a community-based group to provide a list suggestions of other
> event and organizational policies that the ICANN Board should look at in
> considering improved or new policies, on the understanding that appropriate
> subject matter experts will be consulted in drafting a final policy;
>
> •  Convene a community-based group to provide input to the ICANN Board
> with respect to any potential changes or additions that the Board may wish
> to recommend to the community as a result of further Board discussions and
> expert consultations on the topic; and
>
> •  Do not convene a formal group, but leave it to each community
> (SO/AC/SG/Constituency/RALO) and individual participants to provide
> suggestions to, and comment on possible recommendations from, the Board as
> a result of further Board discussions and expert consultations on the
> topic.
>
>
> Thank you all for your input and for helping us ensure that the ICANN
> community remains involved in work on this important topic.
>
>
>
> Best regards,
>
>
> David
>
>
>
> _______________________________________________
> NCUC-EC mailing list
> NCUC-EC at lists.ncuc.org
> http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-ec
>
>


-- 
Farzaneh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncuc.org/pipermail/ncuc-ec/attachments/20160419/95223d1c/attachment.html>