[ALAC] IMPORTANT: PAPER ON OFFICE OF DIVERSITY PUBLIC COMMENTS
Carlton Samuels
carlton.samuels at gmail.com
Thu Feb 15 00:55:44 UTC 2018
Well said, Maureen. Big +1.
Deeds!
-Carlton
==============================
*Carlton A Samuels*
*Mobile: 876-818-1799Strategy, Planning, Governance, Assessment &
Turnaround*
=============================
On Tue, Feb 13, 2018 at 7:42 PM, Maureen Hilyard <maureen.hilyard at gmail.com>
wrote:
> Hi Alan
>
> I will repeat a message I sent to an internal group as my only comment on
> the matter.
>
> I am not in favour of a formal office for diversity.
>
> In the multi-stakeholder bottom-up organisation that ICANN is supposed to
> be, diversity should be one of the underpinning features of its corporate
> culture. It shouldn't have to be defined and detailed. It should be
> characterised by the inclusive nature of its policies and practices. I
> agree with you in that we don't need more bureaucracy, we just need ICANN
> org to actively and constructively work with the rich diversity of the
> membership groups of ICANN so that we can together successfully achieve our
> mission. Dealing with any diversity issues can be given to the Ombudsman
> and his/her team.
>
> Maureen
>
>
>
>
> On Tue, Feb 13, 2018 at 2:18 PM, Alan Greenberg <alan.greenberg at mcgill.ca>
> wrote:
>
>> I would like to call your attention to this paper that was just
>> circulated by the CCWG-Accountability WS2 on Diversity.
>>
>> The ALAC was silent on the question of an Office of Diversity (OOD) that
>> was mentioned in the draft recommendations (see
>> https://community.icann.org/x/Z5tEB)
>>
>> As important as diversity is, I find it troublesome that ICANN might be
>> dedicating more bureaucracy to it. As I noted in my recent comments on the
>> Specific Reviews Operating Standards ( https://mm.icann.org/pipermail
>> /comments-reviews-standards-17oct17/2018q1/000008.html ), I find that
>> for the best of reasons, ICANN is building more and more complex process,
>> rules and bureaucracy. At a time when it is clear we are going to have
>> increasing budget constraint, this must be controlled. If we consider
>> issues such as this as sacred , then we will see more and more other more
>> discretionary budgets cut (and I am predicting that if we don't change our
>> philosophy, budget issues will get MUCH worse).
>>
>> According to the original recommendations document (
>> https://www.icann.org/en/system/files/files/ccwg-acct-ws2-
>> draft-recs-diversity-26oct17-en.pdf ): The role of this office would be
>> to independently support, record and keep track of issues including
>> complaints from the community on diversity issues within the organization.
>>
>> I presume that by "organization" the document means all of ICANN (ICANN
>> Organization as the staff are now known, the volunteer community and the
>> Board). For ICANN Organization, I see this as falling directly under Human
>> Resources and the Complaints Officer. For the volunteer part of ICANN, and
>> the Board, I think it quite reasonable to keep records but that does not
>> warrant a staffed office. Selection of volunteers is not done centrally,
>> and complaints presumably should go to the Ombudsman.
>>
>> Should the ALAC issue a further statement on this? And if so, what are
>> your views?
>>
>> Alan
>>
>>
>> From: Bernard Turcotte <turcotte.bernard at gmail.com>
>> Date: Mon, 12 Feb 2018 14:28:23 -0500
>> To: ws2-diversity <ws2-diversity at icann.org>
>> Subject: [Ws2-diversity] CCWG-Accountability-WS2-Diversity - PAPER ON
>> OFFICE OF DIVERSITY PUBLIC COMMENTS
>>
>> All,
>>
>> As promised at the last meeting of the diversity sub-group please find
>> below and attached the document prepared by Fiona and Rafik on this topic.
>>
>> Bernard Turcotte
>> ICANN Staff Support to the CCWG-Accountability-WS2
>>
>> For Fiona and Rafik.
>>
>>
>> *DIVERISTY SUB-GROUP *
>>
>>
>>
>>
>>
>> *PAPER ON OFFICE OF DIVERSITY PUBLIC COMMENTS *
>>
>>
>>
>>
>> *Preamble: *
>>
>>
>> The Diversity sub-group presented a report for public comments that
>> presented diversity at ICANN identified by a number of elements by which
>> diversity may be characterized, measured and reported. The report was
>> informed by feedback from ICANN Supporting Organization(SO)/Advisory
>> Committee (AC)/groups through a Diversity Questionnaire. In the report the
>> Sub-group proposes a number of recommendations by which ICANN may define,
>> measure, report, support and promote diversity. It also indicated that
>> there was a lack of consensus on the establishment on an office of
>> diversity and sought to receive public comments on the position of the
>> office of diversity.
>>
>>
>>
>>
>> *Summary of Responses from Public Comments: *
>>
>>
>> - Total of 15 comments
>>
>>
>>
>>
>> - 6 had no comments on an office of diversity
>> - 3 supported an office of diversity or a panel
>> - 3 supported an office of diversity
>> - 3 rejected the notion of an office of diversity.
>>
>>
>>
>>
>> - Breakdown by major categories
>>
>>
>>
>>
>> - 7 SO/ACs/Board (those which will have to approve the WS2 final
>> report):
>>
>>
>>
>>
>> - 4 had no comments
>> - 3 Rejected the notion of an office of diversity
>>
>>
>>
>>
>> - 2 Governments:
>>
>>
>>
>>
>> - 1 had no comments on an office of diversity
>> - 1 supported an office of diversity
>>
>>
>>
>>
>> - 6 Individuals/Associations:
>>
>>
>>
>>
>> - 1 had no comments on an office of diversity
>> - 3 supported an office of diversity or a panel
>> - 2 supported an office of diversity
>>
>>
>>
>>
>>
>>
>>
>> *Summary of Positions relating to the OOD from Public Comments: *
>>
>>
>> 1. Establishment of an office of diversity or a panel similar to
>> what is proposed in the Ombuds recommendations.
>>
>> 2. Establishment of an office of diversity
>>
>> 3. Rejection of an office of diversity in favour of staff performing
>> this work.
>>
>>
>>
>>
>> *Required Actions: *
>> The Sub-group on diversity does not have one solid position from the
>> public comments but has instead received a number of options that need to
>> be discussed further and weighed in order to determine how oversight of
>> diversity can be pursued.
>>
>>
>>
>> Content-Type: application/pdf; name="Office Of Diversity OptionsV1.2.pdf"
>> Content-Disposition: attachment;
>> filename="Office Of Diversity OptionsV1.2.pdf"
>> X-Attachment-Id: f_jdkm12g20
>> X-Microsoft-Exchange-Diagnostics:
>> 1;YQXPR0101MB1589;27:5Mxd449bwS/HOp/iuqOwk4pTsHsOLwp4Urd2lAQ
>> C+LxH4sZOpA5H5EWy2W2rBs7gToTighaGdY2nGhYw4nbnkMhHj+A5OHljcCM
>> G4yzy5c5s6+66WnCi//rOuNRtAQcG
>> X-Microsoft-Antispam-Message-Info:
>> ApKEtrCYhRKl3UPpOM0fLBOZkaTcY6QwBeeGtAqZw+OgOzfrvYEk+AotEDu2
>> +rNWAMq6958Jvp+c+glyW7W4EQn8cXBw9UBrowrCZ+P5ytgQVR8nbfFnqRaj
>> G4VJuLLwZc6022IzI09Frtk3p2uxpg==
>>
>> Content-Type: text/plain; charset="us-ascii"
>> Content-Transfer-Encoding: 7bit
>> Content-Disposition: inline
>> X-Microsoft-Exchange-Diagnostics:
>> 1;YQXPR0101MB1589;27:5Mxd449bwS/HOp/iuqOwk4pTsHsOLwp4Urd2lAQ
>> C+LxH4sZOpA5H5EWy2W2rBs7gToTighaGdY2nGhYw4nbnkMhHj+A5OHljcCM
>> G4yzy5c5s6+66WnCi//rOuNRtAQcG
>> X-Microsoft-Antispam-Message-Info:
>> ApKEtrCYhRKl3UPpOM0fLBOZkaTcY6QwBeeGtAqZw+OgOzfrvYEk+AotEDu2
>> +rNWAMq6958Jvp+c+glyW7W4EQn8cXBw9UBrowrCZ+P5ytgQVR8nbfFnqRaj
>> G4VJuLLwZc6022IzI09Frtk3p2uxpg==
>>
>> _______________________________________________
>> Ws2-diversity mailing list
>> Ws2-diversity at icann.org
>> https://mm.icann.org/mailman/listinfo/ws2-diversity
>>
>>
>> _______________________________________________
>> ALAC mailing list
>> ALAC at atlarge-lists.icann.org
>> https://atlarge-lists.icann.org/mailman/listinfo/alac
>>
>> At-Large Online: http://www.atlarge.icann.org
>> ALAC Working Wiki: https://community.icann.org/di
>> splay/atlarge/At-Large+Advisory+Committee+(ALAC)
>>
>
>
> _______________________________________________
> ALAC mailing list
> ALAC at atlarge-lists.icann.org
> https://atlarge-lists.icann.org/mailman/listinfo/alac
>
> At-Large Online: http://www.atlarge.icann.org
> ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+
> Advisory+Committee+(ALAC)
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://atlarge-lists.icann.org/pipermail/alac/attachments/20180214/a58b9723/attachment.html>
More information about the ALAC
mailing list