[Epdp-dt] Working Methods

[Ayden Férdeline]

Thanks Marika, I suggested translation just out of an abundance of caution, as in the proposed FY19 budget it was noted that ICANN org will look to be more strategic in its use of language services moving forward. I think we do not need a rapid turnaround time for the final report, though for the initial report I would suggest that the executive summary and recommendations be translated into ICANN's core languages within 10 days of the public comment window opening, so non-English-fluent speakers may still be able to provide the EPDP with some inputs.

Best wishes, Ayden

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On 28 June 2018 5:54 AM, Marika Konings <marika.konings at icann.org> wrote:

> In relation to item 3, that is in line with the existing translation policy so as such there is no need to specifically call that out, although it will need to be factored in that there will be a delay in the translated versions being available, depending on the length of the executive summary / Final Report.
>
> Best regards,
>
> Marika
>
> On 27 Jun 2018, at 17:34, Ayden Férdeline <icann at ferdeline.com> wrote:
>
>> Hi all,
>>
>> I would like to request several revisions be made to the EPDP Working Methods please:
>>
>> 1) All meetings must be recorded and transcribed.
>>
>> Please revise this text from:
>>
>> In addition to the standard services provided to GNSO PDP Working Groups such as policy staff support, mailing lists and regular conference calls, including recording and transcription where needed (frequency and duration to be decided by EPDP team), the EPDP team will need appropriate support to:
>>
>> To:
>>
>> All calls of the EPDP must be recorded and transcribed, and said recordings and call transcriptions must be publicly accessible from the ICANN website. Standard support offered to GNSO PDP Working Groups, including but not limited to the provision of a wiki space, archived mailing lists, and conference call facilities, will be required. In addition, the EPDP will need appropriate support to:
>>
>> 2) Google Docs may only be used in conjunction with Google Vault.
>>
>> Please revise the text from:
>>
>> the EPDP Team should consider which tools provide the best flexibility to facilitate online collaboration, such as the wiki and Google docs.
>>
>> To:
>>
>> the EPDP Team should consider which tools provide the best flexibility to facilitate online collaboration, but it must do so in accordance with the principles of accountability and transparency that are so important to the GNSO. If Google Docs or other G Suite products are used, it must be used in conjunction with Google Vault, which logs data for archival purposes. Similarly, if other tools are used, they may be used only if they preserve information to a level that meets or exceeds eDiscovery standards in California, being the location of ICANN's headquarters.
>>
>> 3) Translation of executive summary and recommendations of the initial report for public comment, and of the entire final report, into ICANN's official languages.
>>
>> Suggested text:
>>
>> The substantive work of the EPDP must be translated into ICANN's official languages in order to provide non-English-fluent stakeholders with an equal level of access to review the work of the EPDP. For the initial report(s), this must consist of the executive summary and recommendations, and for the final report, this must be a translation of the entire report.
>>
>> Kind regards,
>> Ayden Férdeline
>
>> _______________________________________________
>> Epdp-dt mailing list
>> Epdp-dt at icann.org
>> https://mm.icann.org/mailman/listinfo/epdp-dt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/epdp-dt/attachments/20180628/efe2b4b3/attachment.html>