<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Data loss is one thing and understandable, but I am afraid major design flaws in how the email system no longer works are not as understandable. <div><br></div><div>I hope these are also being addressed. ISOC should ask itself why Chapters, such as ours, use MailChimp and Eventbrite for Chapter management. </div><div><br></div><div>To be clear I am sure you are working to address the issues being raised by everyone. </div><div><br></div><div>Yours,</div><div><br></div><div>John<br><br><div id="AppleMailSignature" dir="ltr">John More </div><div dir="ltr"><br>On Feb 13, 2019, at 8:48 PM, Veni Markovski <<a href="mailto:veni@veni.com">veni@veni.com</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<font face="Helvetica, Arial, sans-serif">Thanks, Andrew. <br>
I was just about to write to John and Eduardo, that you and
colleagues at ISOC are staying on top of things - as visible from
your two messages.<br>
<br>
Shift (in data) happens. I've gone in some of these during my
tenure as an ISP owner in Bulgaria, so I know how you folks feel
and what efforts you put to resolve issues. Best of luck!<br>
<br>
v/<br>
</font><br>
<div class="moz-cite-prefix">On 02/13/19 19:50, Andrew Sullivan
wrote:<br>
</div>
<blockquote type="cite" cite="mid:20190214005045.vtmxdd4s4cmiwre2@outlook.office365.com">
<pre class="moz-quote-pre" wrap="">Dear colleagues,
There has been a lot of additional discussion about the new AMS today.
I want to follow up with all of you about the status.
We continue to validate the data. We are unsure when we will complete
that. If we completely resolve every issue, we will send a notice
right away. If the issues are not completely resolved before 17:00
UTC (12:00 EST, which is where most of the staff working this problem
are) tomorrowe, we will send another status update then. If the
problem is not resolved by 22:00 UTC (17:00 EST) tomorrow, we will
send another status, with a new schedule for updates.
We are confirming whether there has in fact been any data loss during
migration. If there has, you will hear about it as soon as we have
confirmed it. The old system remains set aside and mothballed in
order to ensure that no data loss is possible there, so this data is
not lost as such. But there have been transactions in the new system
since the AMS opened after the migration, so we are proceeding as
though our post-transition validation was accurate until we have clear
evidence of loss of data.
It should be noted that, in keeping with communications prior to the
change over, some discrepancies in numbers were expected. So the fact
of differences as such does not necessarily indicate a problem. Some
of the numbers reported are somewhat surprising to us, however, which
is why we are undertaking this comprehensive review before concluding
nothing is wrong.
At the same time, I want to note that we believe we have prevented the
recurrence of the "empty mail" problem that people saw over the past
24 hours.
I apologise for the disruption this has caused, I understand your
frustration at the difficulty we are having, and I apologise that I am
unable to answer all your questions right now. We are working to
correct any problem, and will keep you updated as we make progress.
Best regards,
Andrew
On Wed, Feb 13, 2019 at 10:19:08AM +0000, Andrew Sullivan wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Dear colleagues,
I want you to know that we are aware of some of the concerns regarding
the new AMS and the difficulties people are having with it. I've
asked the team responsible for a more comprehensive response than
this, but I wanted to let you know in the meantime that we're
listening and taking these concerns seriously. All of the issues are
important, but as an one-time data person I'm particularly concerned
about the reports of missing members that seem to be unrelated to the
GDPR-related changes in rolls that happened last year. Please stand
by while we figure out what is going on.
Independent of that, we're aware of an email that might have looked
suspicious that was sent to a number of people in the past 24 hours.
We're also working out what happened there, but it does appear to have
been generated by the system and is not a phishing attempt as near as
we can tell. Again, you'll hear more from the relevant staff soon.
I thank you for your forebearance as we attempt to make ensure that we
have the right tools to enable the whole Internet Society, community
and staff, function well together.
Best regards,
A
--
Andrew Sullivan
President & CEO, Internet Society
<a class="moz-txt-link-abbreviated" href="mailto:sullivan@isoc.org">sullivan@isoc.org</a>
+1 517 885 3587
_______________________________________________
As an Internet Society Chapter Officer you are automatically subscribed
to this list, which is regularly synchronized with the Internet Society Chapter Portal (AMS):
<a class="moz-txt-link-freetext" href="https://admin.internetsociety.org/622619/User/Login">https://admin.internetsociety.org/622619/User/Login</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap=""></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Best regards,
Veni
<a class="moz-txt-link-freetext" href="http://www.veni.com">http://www.veni.com</a>
pgp:5BA1366E <a class="moz-txt-link-abbreviated" href="mailto:veni@veni.com">veni@veni.com</a>
The opinions expressed above are those of the
author, not of any organizations, associated
with or related to him in any given way. </pre>
</div></blockquote><blockquote type="cite"><div dir="ltr"><span>_______________________________________________</span><br><span>As an Internet Society Chapter Officer you are automatically subscribed</span><br><span>to this list, which is regularly synchronized with the Internet Society Chapter Portal (AMS):</span><br><span><a href="https://admin.internetsociety.org/622619/User/Login">https://admin.internetsociety.org/622619/User/Login</a></span><br></div></blockquote></div></body></html>