ICANN's Move to Zoom: Follow-up Status Update and Response to Feedback - ICANN

[dorothy g]

I have been using zoom for years - it works. Adobe had issues, I'm glad
it's gone. Lost time?...try connecting with Adobe when your country does
not have a dial in number. The point on consultation is well taken. Let us
flag it for the next change (which will surely happen)  and agree on a
protocol for this kind of adjustment.  Until the next change...we can zoom
on...
Dorothy

On Sat, May 11, 2019 at 9:08 PM Ayden Férdeline <icann at ferdeline.com> wrote:

> Hi Thato,
>
> There was no formal consultation process. That's a fact.
>
> I understand that meetings held in Zoom can be recorded, and that's great.
> My concern is about all of the past 20 years worth of meetings that are
> preserved and saved in the proprietary Adobe Connect format. We do not want
> to lose this institutional memory.
>
> And my point about using a new tool is not just downloading the file. Some
> people have computers provided by their employer with enterprise security
> settings, so will need to have IT install an application -- it isn't just
> downloading a file for everyone, it's a real inconvenience. Add on to that
> the 30 minutes of lost productivity per community member that is taken in
> them adjusting to this new tool, and we're talking conservatively about
> 1,500 lost hours of volunteer time. That is not inconsiderable, and I think
> ICANN org should be doing a better job at accounting for how it uses
> volunteer hours.
>
> Best wishes,
>
> Ayden Férdeline
>
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Saturday, May 11, 2019 11:02 PM, Thato Mfikwe <thatomfikwe at gmail.com>
> wrote:
>
> Hi,
>
> Maybe the issue is that there was insufficient time for public comment not
> that there was no consultation? Personally, I think Zoom will be OK because
> meeting recordings can be made, although not sure about transcripts and
> calling in perticipants to,eetings as metioned. But the inconvenience
> around the download of apps is not a determiner because to download Zoom
> just requires less than 10MB. When referring to dysfunctional, what are you
> referring to?
>
> Will go through your initial responses, thanks.
>
>
> Thato Mfikwe.
>
> On Sat, May 11, 2019 at 10:19 PM Ayden Férdeline <icann at ferdeline.com>
> wrote:
>
>> Hi Thato,
>>
>> I have outlined my concerns with Zoom on this list already, and they do
>> not stem from my personal experiences in using the program. My concerns are
>> around the centralization of decision making that impacts the ICANN
>> community being made without direct community input; the lack of
>> consideration for volunteer time in making the decision to migrate to a new
>> platform; and the lack of safeguards in place to ensure no records are lost
>> during this transition. I consider this in particular to be an extremely
>> important point.
>>
>> I think you are conflating the ICANN organization with the ICANN
>> community in your remarks below.
>>
>> Ayden Férdeline
>>
>>
>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>> On Saturday, May 11, 2019 10:00 PM, Thato Mfikwe <thatomfikwe at GMAIL.COM>
>> wrote:
>>
>> Hi Ayend,
>>
>> I also think that Zoom is a good platform, used it numerous times without
>> a hassle. What limitations do you foresee with Zoom?
>>
>> Not sure about transcripts and its other functionalities but I think it
>> could work, besides its inability to call in participants into meetings as
>> some regions do not have reliable connections to participate online.
>>
>> However, recording of previous meetings from Adobe connect should remain
>> accessible or archived.  I also think it is inappropriate and it is
>> uncalled for to call ICANN a dysfunctional organization because you are a
>> leader within NCSG subcommittees and also play a role within the GNSO, what
>> could possibly qualify ICANN being called dysfunctional, the preference of
>> Zoom over Adobe?
>>
>> Maybe I am mistaken, are you saying you have no knowledge of Zoom and how
>> it works? Your focus needs to be on NCSG finances and how they can enhance
>> and improve the participation of C's in ICANN processes and realising ICANN
>> objectives.
>>
>> Thato Mfikwe.
>>
>> On Sat, May 11, 2019 at 4:45 PM Ayden Férdeline <icann at ferdeline.com>
>> wrote:
>>
>>> This blog post gives the impression that little feedback has been
>>> received on the transition to Zoom, but what feedback has been received has
>>> been positive. What it does not mention is that there was no formal
>>> consultation process or even request for comments. I note many of my
>>> critical comments remain unaddressed -- which of course is possible when
>>> there was no formal request for community input. This transition went ahead
>>> with less than a month's notice to the community and we have never been
>>> provided with a platform to object to this change or to share our concerns
>>> formally. If ICANN terms it is a "success" to have transitioned to a new
>>> platform 1) without having considered how to preserve previous meeting
>>> recordings, 2) by inconveniencing the entire ICANN community by making us
>>> download new software and learn a new tool, and 3) by selecting a new tool
>>> with reduced functionality over the previous one, well it is just another
>>> instance of something that could only be seen as a success within and by
>>> this dysfunctional organization. I think the more apt term to describe this
>>> transition would be a "failure".
>>>
>>> Ayden
>>>
>>>
>>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>>> On Saturday, May 11, 2019 1:30 AM, Maryam Bakoshi <
>>> maryam.bakoshi at ICANN.ORG> wrote:
>>>
>>> Dear All,
>>>
>>> Please find ICANN's Move to Zoom: Follow-up Status Update and Response
>>> to Feedback:
>>> https://www.icann.org/news/blog/icann-s-move-to-zoom-follow-up-status-update-and-response-to-feedback
>>>
>>>
>>> —
>>> Many thanks,
>>>
>>>
>>> *Maryam Bakoshi* | SO/AC Collaboration Services Sr. Coordinator
>>> *ICANN* | Internet Corporation for Assigned Names and Numbers
>>> *S*: Maryam.bakoshi.icann | *T*: ‭+44 7846 471777‬
>>>
>>>
>>>
>>
>

-- 
Dorothy Gordon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-discuss/attachments/20190511/669a8d61/attachment.htm>