<p dir="ltr">The Technology Task Force held several meetings and make recommendations it took over 3years for the ICANN to take up a decision.</p>
<p dir="ltr">When a security breach happened in San Juan during the meeting, Zoom was the next best alternative.</p>
<p dir="ltr">About the broken links - there is no company that has ever achieved 100% effectiveness, perfection and efficiency.</p>
<p dir="ltr">Thank you</p>
<div class="gmail_quote">On May 12, 2019 3:19 AM, "Ayden Férdeline" <<a href="mailto:icann@ferdeline.com">icann@ferdeline.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div>Hi Daniel,</div><div><br></div><div>Thanks for sharing this perspective and your experiences using Zoom. This is good to know, and would have been useful to feed back to ICANN through a formal consultation process. </div><div><br></div><div>As I have said before, I do not oppose migrating to new technologies or tools. What I oppose is the centralisation of decision making, where decisions are made in a top down manner by ICANN org without adequate community consultation. </div><div><br></div><div>You misunderstood my point about measuring volunteer contributions and the impact of transitioning to new technologies. This is not about a “data backup” or the like; it’s about monitoring cost in terms of volunteer hours that must be spent learning new tools versus engaging in other forms of ICANN volunteerism. And my point about records was that the existing Adobe Connect recordings could soon become inaccessible and that we need to make sure they are converted into a format that is preserved for the future. </div><div><br></div><div>You claim that ICANN staff are “on top of there game” when it comes to preserving data. Why, then, are there so many broken links on the ICANN website? I’m honestly surprised to hear so much praise of ICANN org. Sorry, but I don’t drink the Kool-Aid. I pay enough attention to know better. </div><div><br></div><div>Best wishes,</div><div><br></div><div>Ayden Férdeline </div><div><br></div><div id="m_-5019675140290438013protonmail_mobile_signature_block"><div>Sent from ProtonMail Mobile</div></div> <div><br></div><div><br></div>On Sun, May 12, 2019 at 01:57, DANIEL NANGHAKA <<a href="mailto:dndannang@GMAIL.COM" target="_blank">dndannang@GMAIL.COM</a>> wrote:<blockquote type="cite"> <p dir="ltr">Dear Ayden,</p>
<p dir="ltr">I will disagree with you on several matters also based on my experience and challenges encountered using Adobe connected.</p>
<p dir="ltr">The use of zoom came as a recommendation from the TTF (Technology Task Force) following tremendous issues with AC.</p>
<p dir="ltr">The use of zoom has simplified a lot of challenges for areas with limited connectivity where by I am a victim of connectivity. Personally am a rural boy coming from a place called Bududa which has one of the worst internet connections and now I can connect and chair a meeting on zoom with no request for dial out.</p>
<p dir="ltr">Zoom uses very low bandwidth and hence saves cost. When using Adobe, an a complete 1hour meeting would consume between 700Mb to 1Gb of data, a 2hr meeting would cost twice. But the use of Zoom is almost half the the bandwith which lowers cost. 1Gb of data costs approximately 4USD, and I have a minimum of 4 calls every week. You can do the math of cost comparison of the two.</p>
<p dir="ltr">The zoom connection is very stable and favors us from developing countries. </p>
<p dir="ltr">With the challenges of Adigo, the constant calls dropped, I bet you can understand the pain of chairing a meeting and the attendees. </p>
<p dir="ltr">You mention loss of data worth 1500hrs. ICANN has a strong data backup system and mitigation security for data loss. I believe ICANN support team is ontop of there game on this. </p>
<p dir="ltr">I would speak a lot as a member who has been following various issues and trend in ICANN.</p>
<p dir="ltr">Ayden, I suggest that please do your research well before criticizing important development and need for inclusiveness of the technologically marginalized areas with an example of where I come from.</p>
<p dir="ltr">Thank you<br>
Daniel K. Nanghaka</p>
<div class="gmail_quote">On May 12, 2019 1:38 AM, "dorothy g" <<a href="mailto:dgdorothydg@gmail.com" target="_blank">dgdorothydg@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-size:small">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...</div><div class="gmail_default" style="font-size:small">Dorothy</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, May 11, 2019 at 9:08 PM Ayden Férdeline <<a href="mailto:icann@ferdeline.com" target="_blank">icann@ferdeline.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>Hi Thato,<br></div><div><br></div><div>There was no formal consultation process. That's a fact.<br></div><div><br></div><div>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.<br></div><div><br></div><div>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.<br></div><div><br></div><div>Best wishes,<br></div><div><br></div><div><div><div>Ayden Férdeline <br></div></div><div><br></div></div><div><br></div><div>‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐<br></div><div> On Saturday, May 11, 2019 11:02 PM, Thato Mfikwe <<a href="mailto:thatomfikwe@gmail.com" target="_blank">thatomfikwe@gmail.com</a>> wrote:<br></div><div> <br></div><blockquote type="cite"><div dir="ltr"><div>Hi,<br></div><div><br></div><div>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?<br></div><div><br></div><div>Will go through your initial responses, thanks.<br></div><div><br></div><div><br></div><div>Thato Mfikwe. <br></div></div><div><br></div><div class="gmail_quote"><div dir="ltr">On Sat, May 11, 2019 at 10:19 PM Ayden Férdeline <<a href="mailto:icann@ferdeline.com" target="_blank">icann@ferdeline.com</a>> wrote:<br></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote"><div>Hi Thato,<br></div><div><br></div><div>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.<br></div><div><br></div><div>I think you are conflating the ICANN organization with the ICANN community in your remarks below. <br></div><div><br></div><div>Ayden Férdeline <br></div><div><div><br></div></div><div><br></div><div>‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐<br></div><div>On Saturday, May 11, 2019 10:00 PM, Thato Mfikwe <<a href="mailto:thatomfikwe@GMAIL.COM" target="_blank">thatomfikwe@GMAIL.COM</a>> wrote:<br></div><div><br></div><blockquote type="cite"><div dir="ltr"><div>Hi Ayend,<br></div><div><br></div><div>I also think that Zoom is a good platform, used it numerous times without a hassle. What limitations do you foresee with Zoom?<br></div><div><br></div><div>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.<br></div><div><br></div><div>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?<br></div><div><br></div><div>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.<br></div><div><br></div><div>Thato Mfikwe. <br></div></div><div><br></div><div class="gmail_quote"><div dir="ltr">On Sat, May 11, 2019 at 4:45 PM Ayden Férdeline <<a href="mailto:icann@ferdeline.com" target="_blank">icann@ferdeline.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>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".<br></div><div><br></div><div>Ayden<br></div><div><div><br></div></div><div><br></div><div>‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐<br></div><div>On Saturday, May 11, 2019 1:30 AM, Maryam Bakoshi <<a href="mailto:maryam.bakoshi@ICANN.ORG" target="_blank">maryam.bakoshi@ICANN.ORG</a>> wrote:<br></div><div><br></div><blockquote type="cite"><div>Dear All, <br></div><div><br></div><div><div>Please find <span style="font-family:Helvetica"><span style="font-size:12pt">ICANN's Move to Zoom: Follow-up Status Update and Response to Feedback: </span></span><a href="https://www.icann.org/news/blog/icann-s-move-to-zoom-follow-up-status-update-and-response-to-feedback" target="_blank">https://www.icann.or<wbr>g/news/blog/icann-s-move-to-zo<wbr>om-follow-up-status-update-and<wbr>-response-to-feedback</a><br></div><div><br></div><div><br></div><div dir="ltr"><div>—<br></div><div>Many thanks,<br></div><div><b></b><br></div><div><span style="background-color:rgba(255,255,255,0)"><b></b></span><br></div><div><span style="background-color:rgba(255,255,255,0)"><b>Maryam Bakoshi</b> | SO/AC Collaboration Services Sr. Coordinator </span><br></div><div><span style="background-color:rgba(255,255,255,0)"><b>ICANN</b> | Internet Corporation for Assigned Names and Numbers </span><br></div><div><span style="background-color:rgba(255,255,255,0)"><b>S</b>: Maryam.bakoshi.icann | <b>T</b>: +44 7846 471777</span><br></div></div><div dir="ltr"><br></div></div></blockquote><div><br></div></blockquote></div></blockquote><div><br></div></blockquote></div></blockquote><div><br></div></blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr"><div dir="ltr">Dorothy Gordon</div></div>
</blockquote></div>
</blockquote><div><br></div><div><br></div></blockquote></div>