[NCSG-PC] Fwd: Re: [Epdp-dt] Working Methods
Stephanie Perrin
stephanie.perrin at mail.utoronto.ca
Thu Jun 28 21:12:21 EEST 2018
Ok I will rely on you to provide information to the List Rafik, my
apologies folks for the wrong date, I guess I was being optimistic. As
for concerns on the document....I had a lot. Far beyond scope.
cheers
Stephanie
On 2018-06-28 10:05, Rafik Dammak wrote:
> Hi,
>
> I want to add one point as we discussed several times about
> coordination and not discussing the substance. I drafted the initial
> text on resources/working methods and may have missed stuff for sure
> as there was no so much input. However, I discovered the changes and
> amendments like everyone in DT list. I guess I could have been
> informed for suggestions beforehand no?
>
> the DT call won't be in 2nd or 3rd June and will factor that for our
> Policy Call next week.
> With regard to input, I insist that we cover all areas of real
> concerns like the scope.
>
> Best,
>
> Rafik
>
> Le jeu. 28 juin 2018 à 23:55, Stephanie Perrin
> <stephanie.perrin at mail.utoronto.ca
> <mailto:stephanie.perrin at mail.utoronto.ca>> a écrit :
>
> Backing up Ayden here....we are trying to be as transparent as
> possible here, but we cannot keep up with the drafting and we are
> here on the ground. This is stacking up to be a highly political
> process, with set agendas from the parties and they are all
> preparing well. We will not have time to reach community
> decisions and remain effective. Transparency is about all we can
> manage.
>
> The next drafting team call is likely to be July 2-3, and we have
> to reach consensus. There are a lot of issues which are already
> unfavourable to us. So please keep your input coming, but time is
> against a robust consensus process at the NCSG level. You are
> going to have to trust your councillors.
>
> Stephanie Perrin
>
>
> On 2018-06-28 09:38, Ayden Férdeline wrote:
>> Hi Arsene,
>>
>> Given how rapidly the charter is being drafted - and let's be
>> clear, it is being drafted as we speak by the other stakeholder
>> groups - I thought it important to respond swiftly and to try to
>> get this language inserted into the document. I did not advocate
>> for anything that is inconsistent with the NCSG's values; call
>> transcription is essential to holding ICANN accountable. So no, I
>> do not think it was necessary for me to "share this with PC
>> before sending to council list." That said I did forward my email
>> to the PC ex post to keep those who are not on the drafting team
>> informed as to what is happening.
>>
>> As for cost, it is simply a cost of doing business for ICANN.
>>
>> Best wishes,
>>
>> Ayden
>>
>>
>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>> On 28 June 2018 7:29 AM, Arsène Tungali <arsenebaguma at gmail.com>
>> <mailto:arsenebaguma at gmail.com> wrote:
>>
>>> I wish you shared this with PC before sending to council list, a
>>> practice we have been encouraging here.
>>>
>>> I also agree that meeting transcription is useful especially
>>> when someone missed the call or need to cross check something or
>>> simply for archives. Sometimes transcription is better than
>>> listening to the recording for bandwidth reasons as well.
>>>
>>> Before i can back up this, i would like to know how much this
>>> would cost. Is it possible to get this estimate from staff?
>>>
>>> -----------------
>>> Arsène Tungali,
>>> about.me/ArseneTungali <http://about.me/ArseneTungali>
>>> +243 993810967
>>> GPG: 523644A0
>>> Goma, Democratic Republic of Congo
>>>
>>> Sent from my iPhone (excuse typos)
>>>
>>> On Jun 28, 2018, at 2:54 AM, Ayden Férdeline
>>> <icann at ferdeline.com <mailto:icann at ferdeline.com>> wrote:
>>>> Please send back up to the Council list
>>>>
>>>> Transcription is not expensive and to save money here is absurd
>>>>
>>>> Let’s save money elsewhere
>>>>
>>>> Ayden
>>>>
>>>> Sent from ProtonMail Mobile
>>>>
>>>>
>>>> On Wed, Jun 27, 2018 at 19:45, Martin Pablo Silva Valent
>>>> <mpsilvavalent at gmail.com <mailto:mpsilvavalent at gmail.com>> wrote:
>>>>> Ayden, there I gabe back up in transcript. Did you sent yours
>>>>> coments to the pc? Did we reach any conclusions on them?
>>>>>
>>>>> Cheers!
>>>>> Martín
>>>>>
>>>>> On Wed, Jun 27, 2018, 19:31 Ayden Férdeline
>>>>> <icann at ferdeline.com <mailto:icann at ferdeline.com>> wrote:
>>>>>
>>>>> I will need back up here from Councillors.
>>>>>
>>>>> This is important. We need transcription.
>>>>>
>>>>> Ayden
>>>>>
>>>>> Sent from ProtonMail Mobile
>>>>>> ---------- Forwarded message ----------
>>>>>> From: Michele Neylon - Blacknight<michele at blacknight.com
>>>>>> <mailto:michele at blacknight.com>>
>>>>>> Date: On Wed, Jun 27, 2018 at 19:28
>>>>>> Subject: Fwd: Re: [Epdp-dt] Working Methods
>>>>>> To: Ayden Férdeline <icann at ferdeline.com
>>>>>> <mailto:icann at ferdeline.com>>,epdp-dt at icann.org
>>>>>> <mailto:epdp-dt at icann.org> <epdp-dt at icann.org
>>>>>> <mailto:epdp-dt at icann.org>>
>>>>>> Cc:
>>>>>>
>>>>>> Ayden
>>>>>>
>>>>>>
>>>>>> I disagree with the transcription of all meetings. The
>>>>>> costs involved with that are disproportionately high and
>>>>>> ICANN funds would be better directed elsewhere
>>>>>>
>>>>>>
>>>>>> I agree with most of your other points.
>>>>>>
>>>>>>
>>>>>> Regards
>>>>>>
>>>>>>
>>>>>> Michele
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Mr Michele Neylon
>>>>>>
>>>>>> Blacknight Solutions
>>>>>>
>>>>>> Hosting, Colocation & Domains
>>>>>>
>>>>>> https://www.blacknight.com/
>>>>>>
>>>>>> http://blacknight.blog/
>>>>>>
>>>>>> Intl. +353 (0) 59 9183072
>>>>>>
>>>>>> Direct Dial: +353 (0)59 9183090
>>>>>>
>>>>>> Personal blog: https://michele.blog/
>>>>>>
>>>>>> Some thoughts: https://ceo.hosting/
>>>>>>
>>>>>> -------------------------------
>>>>>>
>>>>>> Blacknight Internet Solutions Ltd, Unit 12A,Barrowside
>>>>>> Business Park,Sleaty
>>>>>>
>>>>>> Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.:
>>>>>> 370845
>>>>>>
>>>>>>
>>>>>>
>>>>>> *From: *Epdp-dt <epdp-dt-bounces at icann.org
>>>>>> <mailto:epdp-dt-bounces at icann.org>> on behalf of Ayden
>>>>>> Férdeline <icann at ferdeline.com <mailto:icann at ferdeline.com>>
>>>>>> *Reply-To: *Ayden Férdeline <icann at ferdeline.com
>>>>>> <mailto:icann at ferdeline.com>>
>>>>>> *Date: *Wednesday 27 June 2018 at 17:34
>>>>>> *To: *"epdp-dt at icann.org <mailto:epdp-dt at icann.org>"
>>>>>> <epdp-dt at icann.org <mailto:epdp-dt at icann.org>>
>>>>>> *Subject: *[Epdp-dt] Working Methods
>>>>>>
>>>>>>
>>>>>> 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
>>>>>>
>>>>> _______________________________________________
>>>>> NCSG-PC mailing list
>>>>> NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>
>>>> _______________________________________________
>>>> NCSG-PC mailing list
>>>> NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>
>>
>> _______________________________________________
>> NCSG-PC mailing list
>> NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
> _______________________________________________
> NCSG-PC mailing list
> NCSG-PC at lists.ncsg.is <mailto:NCSG-PC at lists.ncsg.is>
> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20180628/dd6d4088/attachment.htm>
More information about the NCSG-PC
mailing list