[technology taskforce] [Ext] LACRALO mailing list issues May 2018

[Corinna Ace]

Hi Dev,

Thanks for your patience on this. Our development teams were recently reorganized, so it took some time to identify the new plan for transbot support. We now have a request in queue with our sustaining engineering team to investigate the reported issues, including instances of emails not being sent or being received by only one list, as well as removal of error checking.

While we’ve identified the right resources, we don’t have confirmation on when the team will be able to address the work. We are still focused on high-priority GDPR compliance-related efforts, and on top of that are prioritizing a queue for about 60 systems this team supports. I’ll let you know when we get a sense of timing and another update when we start actively investigating the issues.

Please let me know if you’d like to have a call to discuss any questions or concerns.

Thank you,
Corinna

On 6/11/18, 6:11 PM, "Dev Anand Teelucksingh" <devtee at gmail.com> wrote:

    cc the TTF mailing list
    
    Hello Corinna, Mark
    
    Trust you are well and hope to get some feedback on this issue since
    first raised on June 1 2018.
    
    Just to followup on some observed discrepancies on the LACRALO mailing
    list translations. Several emails from the LACRALO-es list are not
    being translated to the lac-discuss-en list.
    One example : https://urldefense.proofpoint.com/v2/url?u=https-3A__atlarge-2Dlists.icann.org_pipermail_lac-2Ddiscuss-2Des_2018-2DMay_034043.html&d=DwIBaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=jWxEUqvxwaWlpHy4N1qJRCrU0t-i0B2kqTh7sTZSYbY&m=WFHf7CiCOxa1PAjiUcsqhjxcC9gcTF78N_0kZRmnZlc&s=fe6gb_bWiJXa4dIBFMju9Ui0lytSQtzjT_8F5LUokG4&e=
    
    The LACRALO-es list in May 2018
    (https://urldefense.proofpoint.com/v2/url?u=https-3A__atlarge-2Dlists.icann.org_pipermail_lac-2Ddiscuss-2Des_2018-2DMay_thread.html&d=DwIBaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=jWxEUqvxwaWlpHy4N1qJRCrU0t-i0B2kqTh7sTZSYbY&m=WFHf7CiCOxa1PAjiUcsqhjxcC9gcTF78N_0kZRmnZlc&s=GB2g7pAf6HT_anP7x64OtW8UQiNjVZzosSEe40MHCz4&e=)
    had 229 emails while the LACRALO-en list in May 2018 had 179 emails
    (https://urldefense.proofpoint.com/v2/url?u=https-3A__atlarge-2Dlists.icann.org_pipermail_lac-2Ddiscuss-2Den_2018-2DMay_thread.html&d=DwIBaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=jWxEUqvxwaWlpHy4N1qJRCrU0t-i0B2kqTh7sTZSYbY&m=WFHf7CiCOxa1PAjiUcsqhjxcC9gcTF78N_0kZRmnZlc&s=tJeRpulXzNfGiv5c1d7PABN7oONQ_cO0mrkk-mF2fPA&e=)
    which sounds like a LOT of emails are not being translated.
    
    Given you have access to the error logs of the translation tool, can
    you investigate why this is happening?
    
    Also, I've received many private complaints/concerns regarding the
    "Sentence punctuation must be followed by a space" error message
    emails they get.
    
    As I've noted before on TTF calls, I think this error check needs to
    be reconsidered as it is very hard to find where in an email the
    sentence punctuation error occurs. The error email doesn't include any
    indication of where the error was detected. I suspect many (if not
    all) persons don't bother trying to find the problem and therefore
    nothing changes, behaviour wise.
    
    I'm thinking the tool needs to be updated to treat with punctuation
    points without the space immediately after and thereby removing the
    error check. Or failing that, the error email points to where the
    sentence punctuation error occurs.
    
    Kind Regards,
    
    Dev Anand Teelucksingh
    former TTF chair