[Gnso-bylaws-dt] PLEASE READ: URGENT NEXT STEPS to finalising our work

Sun Oct 6 20:51:24 UTC 2019

Hi all,

I also went through 3.1 - 3.3 with one substantive comment only 
regarding (3.2) the distinction between the two council voting cases. I 
think a quick bylaws compliance check from ICANN Legal could put us (at 
least myself) on the safe side.

Thanks and best regards

Wolf-Ulrich

Am 06.10.2019 um 19:00 schrieb McAuley, David via Gnso-bylaws-dt:
>
> Thanks Heather,
>
> I have completed the First assignment regarding 3.1, 3.2, and 3.3 – 
> made some few minor editorial (non-substantive) comments.
>
> Best wishes,
>
> David
>
> David McAuley
>
> Sr International Policy & Business Development Manager
>
> Verisign Inc.
>
> 703-948-4154
>
> *From:* Gnso-bylaws-dt <gnso-bylaws-dt-bounces at icann.org> *On Behalf 
> Of *Heather Forrest
> *Sent:* Thursday, October 03, 2019 8:19 PM
> *To:* gnso-bylaws-dt at icann.org
> *Subject:* [EXTERNAL] [Gnso-bylaws-dt] PLEASE READ: URGENT NEXT STEPS 
> to finalising our work
>
> Dear DT colleagues,
>
> We have reached the end of our work plan! There are 2 things 
> immediately left to do (we'll circle back to clean up the last item, 
> the Joint Consultation Guidelines with ccNSO, once our looming 
> deadline to Council is met). To meet Council's document deadline, both 
> tasks must be done before Monday, 14 October:
>
> *FIRST: FINALIZE 3.1, 3.2 and 3.3 - TO COMPLETE BY THIS SUNDAY, 6 
> OCTOBER*in your time zone: Ariel has worked diligently to clean up 
> these documents following our call, and I have reviewed her edits and 
> tinkered a bit further. Please can all DT members review these, with 
> particular attention to:
>
> ·3.2 - the revisions to 4.2.3 (*SO/AC Director Removal Petition Review 
> and Certification of Completeness*): Ariel has tidied up, and you will 
> see I have also further added the words 'Certification of 
> Completeness' in the heading of this section and some plain-English 
> introductory words in the introduction at the bottom of page 1 to more 
> clearly distinguish between Certification of Completeness by Council 
> leadership;  Acceptance of the Petition by Vote of Relevant House; and 
> Approval of Petition by entire Council. The same language has been 
> ported to 2.2/2.3, 3.1, and 3.3 as well.
>
> ·3.3 - the revisions to  4.2.4 (*GNSO Community Feedback on Certified 
> Board Recall Petition) *to address David's comment to specify the help 
> from staff to compile, and if time permits, summarise, any comments 
> received through Community Feedback. The same language has been ported 
> to other relevant sections in 1.3/1.4, 2.2/2.3, 3.1, 3.2, and 3.3 (as 
> noted in Ariel’s response to David).
>
> *SECOND: REVIEW OF FULL PACKAGE - TO COMPLETE BY NEXT FRIDAY, 11 
> OCTOBER* in your time zone: Ariel has added a table at the top of our 
> work plan to set out each Guideline/Template we have developed. 
> WORKPLAN found here 
> (https://docs.google.com/document/d/1yeydtqli8UWOrrvChIf9EMprGxo0pOr5lcadM-n0PnY/edit?usp=sharing). 
> I have randomly nominated an active DT member to each Guideline. If 
> you are completely dissatisfied with your allocated document, please 
> convince another DT member to swap with you (bear with me please, as 
> we don't have too much time to rock-paper-scissors over who gets 
> what). I'm happy to take on 2 reviews to complete the list unless a DT 
> member who was not allocated a doc wants to take on a review. Starting 
> from next Monday morning, 7 October (please wait until Monday morning 
> so Julie, Ariel and I can ensure that 3.1, 3.2 and 3.3 are ready and 
> port any relevant changes across to the other docs) please review your 
> allocated document next week. When your review is complete, indicate 
> so in the workplan table by typing 'yes' or 'complete' into the 
> relevant box in the chart. Ariel has diligently ported backwards to 
> earlier documents our learnings and decisions from the more recent 
> documents, but we're all more experienced now, and this final review 
> may catch further things we didn't think about earlier in the year. If 
> you find any issues of concern in your review, please raise them ASAP 
> on the DT list, making very clear which document you're referring to 
> and what the problem is.
>
> Very best wishes to all,
>
> Heather
>
>
> _______________________________________________
> Gnso-bylaws-dt mailing list
> Gnso-bylaws-dt at icann.org
> https://mm.icann.org/mailman/listinfo/gnso-bylaws-dt
> _______________________________________________
> By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-bylaws-dt/attachments/20191006/bff49762/attachment-0001.html>