[ALAC] IMPORTANT: PAPER ON OFFICE OF DIVERSITY PUBLIC COMMENTS
Maureen Hilyard
maureen.hilyard at gmail.com
Sat Feb 17 03:20:44 UTC 2018
+1 Evan
On Fri, Feb 16, 2018 at 10:48 AM, Evan Leibovitch <evan at telly.org> wrote:
> Thanks for the info, Dev.
>
> If that's the case, IMO we should appreciate but not applaud the decision.
>
> Diversity is still a worthwhile goal, but it is best spread by culture and
> leadership rather than bureaucracy. ALAC is and has been one of the most
> diverse communities within ICANN (consider, for instance, our pioneering
> use of language interpretation long before most other volunteer communities
> -- including, suprisingly, the GAC) and yet we are still striving for
> better. Perhaps we have something to offer (so long as the result of this
> offer is not compelled volunteer labour :-P )
>
> IMO there is nothing wrong in taking this opportunity to remind of the
> value (and values) we bring to ICANN. Heaven knows there are plenty who
> would take any opportunity to put us down....
>
> Cheers,
> - Evan
>
>
> On 16 February 2018 at 13:45, Dev Anand Teelucksingh <devtee at gmail.com>
> wrote:
>
>> As a FYI, the ICANN Board responded during the public comment period last
>> month
>> http://mm.icann.org/pipermail/comments-accountability-divers
>> ity-26oct17/attachments/20180116/539b3dfe/ICANNBoardComments
>> -WS2Diversity-0001.pdf
>>
>> saying that the office will not be established given lack of consensus
>> and budget constraints.
>>
>> Dev Anand
>>
>> On Thu, Feb 15, 2018 at 3:07 AM, Bastiaan Goslings
>> <bastiaan.goslings at ams-ix.net> wrote:
>> > I am with Holy and Alan on this one, i.e. when it comes to additional
>> ‘bureaucracy’ and ‘budget’ that would have to be reserved for an OOD. So I
>> too think setting up such an office is not a good idea.
>> >
>> > As a fyi, with regard to ‘diversity’ as a theme within ICANN, I can
>> only reiterate myself. When a couple of us worked on a draft statement re
>> the CCWG WS2 ‘Enhancing Accountability - Recommendations for Diversity’
>> report last December, I a.o. stated:
>> >
>> > 'I too am convinced ‘diversity’ is a good and important thing to strive
>> for. But it is not a goal in itself as far as I am concerned - I could not
>> care less whether someone is black or blue or what her/his sexual
>> orientation might be. Without going into detail, (the first half of) this
>> draft is the most political correct piece of windowdressing material I have
>> come across in a long time. Simply put, IMO, its reads as a plea for
>> ‘diversity for the sake of diversity and let’s focus on that in stead of
>> what ICANN’s missions tells us to’. Emphasised by a large amount of
>> supposedly ‘factual’ statements without basis/underlying sources.’
>> >
>> > (Obviously that was a personal point of view. I then left it to others
>> to suggest comments and I stayed ’neutral’)
>> >
>> >
>> >> On 14 Feb 2018, at 19:36, Javier Rua <javrua at gmail.com> wrote:
>> >>
>> >> I do not disfavor measures like “affirmative action” to attain better
>> balanced workplaces, leadership positions and governmental contexts (In
>> fact, I think representative democracy, in order to truly be representative
>> must sometimes force such representativity with measures that force gender
>> balance. There is good evidence that “affirmative action” measures can
>> balance out many structural and societal obstacles that tend to
>> predetermine male-dominated scenarios, even there are highly qualified
>> women around and available.
>> >> http://ajou.ac.kr/~seoyong/paper/2014-
>> >>
>> >> However, in this particular context I agree with the line of thinking
>> in this thread, particularly as espoused by Holly and Alan, since it is in
>> no way a critique of diversity itself as a positive end, it’s an objection
>> to the way ICANN is structuring the means to that end, which seems to be
>> impracticable and perhaps counterproductive. Why not put scarce ICANN
>> dollars in more outreach geared at female stakeholders, or perhaps
>> supporting spouses of male stakeholders (in return for active Community
>> participation) instead of more bureaucratic/organizational layers?
>> >> 2 Cents.
>> >>
>> >> Javier
>> >>
>> >>
>> >>
>> >>
>> >> Javier Rúa-Jovet
>> >>
>> >> +1-787-396-6511
>> >> twitter: @javrua
>> >> skype: javier.rua1
>> >> https://www.linkedin.com/in/javrua
>> >>
>> >>
>> >> On Feb 14, 2018, at 2:04 PM, Andrei Kolesnikov <andrei at rol.ru> wrote:
>> >>
>> >>> OMG!
>> >>> Holly, Alan, +1. Please keep me out from keyboard for a while...
>> >>>
>> >>> --andrei
>> >>>
>> >>> 2018-02-14 20:46 GMT+03:00 Kan Kaili <kankaili at gmail.com>:
>> >>> Hi,
>> >>>
>> >>> I fully agree with the comments initiated by Alan and the points by
>> Maureen, Holly and others.
>> >>>
>> >>> That is, ALAC should issue a statement against establishing this
>> office. I believe comments of Holly, Maureen and others would suffice as
>> the main body of the statement.
>> >>>
>> >>> Kaili
>> >>>
>> >>>
>> >>>
>> >>> ----- Original Message -----
>> >>> From: Maureen Hilyard
>> >>> To: Holly Raiche
>> >>> Cc: ALAC ; Alan Greenberg
>> >>> Sent: Wednesday, February 14, 2018 9:19 AM
>> >>> Subject: Re: [ALAC] IMPORTANT: PAPER ON OFFICE OF DIVERSITY PUBLIC
>> COMMENTS
>> >>>
>> >>> +1 Holly
>> >>>
>> >>> On Tue, Feb 13, 2018 at 3:07 PM, Holly Raiche <
>> h.raiche at internode.on.net> wrote:
>> >>> Folks
>> >>>
>> >>> Part of me absolutely supports any moves that support diversity. At
>> one point in my life, I headed up the Equal Opportunity Unit in the Aust.
>> Broadcasting Corporation so diversity was my job.
>> >>> Putting that aside, I have serious doubts about the concept in this
>> context.
>> >>>
>> >>> If they talking about just ICANN staff, there is already an ICANN HR
>> function that would (or should) be charged with addressing the issue.
>> >>>
>> >>> If they talking about the various organisations that attend the
>> SOs/ACs? I have even more concern. Just for starters, it is up to each
>> SO/AC - and then individual members within each SO/AC as to who
>> participates. Is ICANN seriously going to tell GAC members that some of
>> them must send more women representatives/more Asian members/more members
>> from non-English speaking backgrounds? And who is going to tell each
>> registry/registrar whom they can send to represent them!
>> >>>
>> >>> If the idea is to have diversity in the make-up of ICANN committees,
>> I would hope the first basis for selection is qualifications for the task.
>> >>>
>> >>> In short, I support Alan’s comments. If the concept is diversity
>> WITHIN ICANN staff, it is covered by HR. Otherwise, I have real doubts
>> about the concept, other than - at best -it could be just a score card.
>> >>>
>> >>> Holly
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> On 14 Feb 2018, at 11:18 am, 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:5Mxd449bw
>> S/HOp/iuqOwk4pTsHsOLwp4Urd2lAQC+LxH4sZOpA5H5EWy2W2rBs7gToTig
>> haGdY2nGhYw4nbnkMhHj+A5OHljcCMG4yzy5c5s6+66WnCi//rOuNRtAQcG
>> >>>>> X-Microsoft-Antispam-Message-Info:
>> >>>>> ApKEtrCYhRKl3UPpOM0fLBOZkaTcY6
>> QwBeeGtAqZw+OgOzfrvYEk+AotEDu2+rNWAMq6958Jvp+c+glyW7W4EQn8cX
>> Bw9UBrowrCZ+P5ytgQVR8nbfFnqRajG4VJuLLwZc6022IzI09Frtk3p2uxpg==
>> >>>>>
>> >>>>> Content-Type: text/plain; charset="us-ascii"
>> >>>>> Content-Transfer-Encoding: 7bit
>> >>>>> Content-Disposition: inline
>> >>>>> X-Microsoft-Exchange-Diagnostics:
>> >>>>> 1;YQXPR0101MB1589;27:5Mxd449bw
>> S/HOp/iuqOwk4pTsHsOLwp4Urd2lAQC+LxH4sZOpA5H5EWy2W2rBs7gToTig
>> haGdY2nGhYw4nbnkMhHj+A5OHljcCMG4yzy5c5s6+66WnCi//rOuNRtAQcG
>> >>>>> X-Microsoft-Antispam-Message-Info:
>> >>>>> ApKEtrCYhRKl3UPpOM0fLBOZkaTcY6
>> QwBeeGtAqZw+OgOzfrvYEk+AotEDu2+rNWAMq6958Jvp+c+glyW7W4EQn8cX
>> Bw9UBrowrCZ+P5ytgQVR8nbfFnqRajG4VJuLLwZc6022IzI09Frtk3p2uxpg==
>> >>>>>
>> >>>>> _______________________________________________
>> >>>>> Ws2-diversity mailing list
>> >>>>> Ws2-diversity at icann.org
>> >>>>> https://mm.icann.org/mailman/listinfo/ws2-diversity
>> >>>> <Office Of Diversity OptionsV1.2.pdf>______________
>> _________________________________
>> >>>> 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/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/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/di
>> splay/atlarge/At-Large+Advisory+Committee+(ALAC)
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> Andrey Kolesnikov
>> >>> RIPN.NET
>> >>>
>> >>> _______________________________________________
>> >>> 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/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/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/di
>> splay/atlarge/At-Large+Advisory+Committee+(ALAC)
>>
>
>
>
> --
> Evan Leibovitch
> Toronto, Canada
>
> Em: evan at telly dot org
> Sk: evanleibovitch
> Tw: el56
>
>
> _______________________________________________
> 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/20180216/ec1912aa/attachment.html>
More information about the ALAC
mailing list