- Gnso-review-wg - lists.icann.org

UPDATED FOR REVIEW: Draft Status Report to the GNSO Council
by Julie Hedlund March 2, 2018

March 2, 2018

Dear GNSO Review Working Group members, Please see the attached revised document (in Word and PDF) with redlined changes based on the discussion on our call today. Please let us know if you have further edits as soon as possible but not later than 1500 UTC tomorrow, Friday, 02 March. Kind regards, Julie From: Gnso-review-wg <gnso-review-wg-bounces(a)icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Wednesday, February 28, 2018 at 7:27 PM To: "gnso-review-wg(a)icann.org" <gnso-review-wg(a)icann.org> Subject: [Gnso-review-wg] FOR REVIEW: Draft Status Report to the GNSO Council Dear GNSO Review Working Group members, The GNSO Council has requested a brief written status report from the GNSO Review Working Group for ICANN61. At this point this is not an item on the GNSO Council’s agenda at its ICANN61 meeting on 14 March, but after receiving the written report the Council could decide to add an item to its agenda. In that case, the status report should be sent to the Council by the document and motion deadline, which is Sunday, 04 March. Please see the attached draft brief report for discussion on tomorrow’s call. The final draft report will be conveyed via email by staff on behalf of the GNSO Review Working Group Chair and Vice Chair in time for the deadline. Kind regards, Julie Julie Hedlund, Policy Director

1 1

Actions/Discussion Notes for GNSO Review WG Meeting on 01 March 2018
by Julie Hedlund March 2, 2018

March 2, 2018

Dear GNSO Review Working Group members, Please see below the action items and discussion notes captured by staff from the meeting on 01 March 2018. These high-level notes are designed to help WG members navigate through the content of the call and are not meant to be a substitute for the recording or transcript, which are posted on the wiki at: https://community.icann.org/display/GRWG/2018. Please note that the next meeting will occur on 29 March either at 1200 or 1300 UTC (time to be determined via separate message). Best regards, Julie Julie Hedlund, Policy Director Notes & Action Items GNSO Review Working Group Meeting on Thursday, 01 March 2018 at 13:00 UTC Action Items: Implementation Charter for Recommendation 22: Action Item 1: Staff will update the organization of training materials on the GNSO website. Staff will update the WG Determination that take into account that there are already trainings that are accessible and include real-time interaction. The WG Determination will note that staff will update the website and will link to the updated GNSO webpage when it is ready. Staff will put the changes out for a 3-week Consensus Call. Implementation Charter for Recommendations 1, 2, & 3: Action Item 2: Staff will add information about Council comment on CROP to the implementation charter once posted to public forum. Staff will also add text based on additional feedback that may be received on SG/C outreach. Action Item 3: Staff will adjust the text of the "note" on page 4 to be more neutral regarding dues collected. Staff will also add text clarifying how dues are used within the BC with respect to voting. Action Item 4: Staff will add text to the charter elaborating on the link between GSE activities and recruitment for PDP WGs. Implementation Charter for Recommendations 7 & 12: Action Item 5: Update implementation charter title to "Language Translation and Transcription." Action Item 6: Staff will add text about the translation of written material, including benefits, uses, and costs. Action Item 7: Staff will add some possible scenarios outlining the costs if GNSO WGs began using translation on their calls. Update to the GNSO Council: Action Item 8: Remove the target end date of June 2018 from the status update to the GNSO Council. Next Meeting: Action Item 9: Staff will send a note to the list asking whether the next meeting on 29 March should take place at 12:00 UTC or 13:00 UTC (due to US change to Daylight Saving Time on 11 March 2018). Notes: 1. Review agenda/SOIs: No updates. 2. Status of Consensus Call for revised implementation charter for recommendation 34: -- The consensus call ended on 8 February. No objections were raised to the text for this implementation charter. -- This recommendation is seen as implemented. The work is complete on this recommendation. 3. Discussion of the revised implementation charter for recommendation 22: -- This charter has been updated based on previous discussions. -- The change discussed on the call on the 8th was to make minor updates to the WG determination. -- Two additional sentences have been added to the end of this section "The Working Group recommends that training options should focus on accessibility of training, and in particular real-time interaction through remote platforms. The Working Group also recommends that all of the training and learning materials are linked from the GNSO website and described in the context of the competency-based framework." -- Earlier in the document, the trainings are organized into a framework. The recommendation states that information about the trainings should be organized following this framework on the GNSO website. -- Question: The WGs mandate is to finalize the implementation. Should we simply make a recommendation or should the WG take additional steps to implement the work itself in collaboration with staff? -- Response: Even if it says "recommend" this does not include a mandate, noting that many trainings have the recommended features. Staff can go ahead an updating the GNSO website as recommended by the WG. -- Question: someone reading this recommendation may wonder if the recommendation will be followed. It is possible that the recommendation will be implemented or can only be implemented under certain circumstances. -- The changes suggested in Action Item 1 will be circulated and go out for consensus call. The WG will aim to have the consensus call closed by the next WG meeting after ICANN61. 4. Discussion of the revised implementation charter for recommendations 1, 2, & 3: -- During the last meeting, staff was asked to make additional edits. -- Staff investigated the CROP program and updated text on this program based on status of the FY19 budget. The draft FY19 budget does not include funding for CROP. Chat excerpt: Marika Konings: Note that this is also input that the Council is considering in relation to the FY19 budget (focus on KPIs and metrics for outreach programs) -- Staff added content about Global Stakeholder Engagement. -- Staff investigated outreach conducted by SG/Cs and added text based on responses received. -- Additional text was included on suggested metrics based on feedback from the WG. -- Question: The note regarding BC and IPC dues may be confusing. The justification and rationales are not included. Could this text be worded in a more neutral manner. For example " There are Constituencies that collect dues . .." -- Question: How is GSE linked to recruiting more participants to GNSO PDP WGs? Some community members are not clear about the link. -- Response: Staff will add language about this link. -- Feedback: The community onboarding program may be useful to include in this implementation charter. -- Clarification: Membership dues allow members to reach decisions in the BC. While voting is not always used, when voting does take place, different members have a different number of votes based on the dues they pay. 5. Discussion of the implementation charter for recommendations 7 & 12: -- Staff had an action item to update text regarding current language services and costs. This text has been updated. Chat excerpt: Rafik Dammak: if I am not mistaking the budget for FY19 includes reduction on interpretation and translation service to be provided. captioning seems the more reasonable option for now -- The implementation charter includes possible approaches to using language services. -- Question: is this charter only covering interpretation services or also document translation services? -- Answer: because recommendation 7 is broad, the implementation charter should likely also include text about document translation. -- Question: If it is up to the WGs to determine the extent to which they use translation, what will be the impact on the budget? Could we check to see how many times GNSO WGs met last year and calculate the potential costs of using these services if X% chose to use translation services? Chat excerpt: Marika Konings: @Wolf-Ulrich - the costs of that would be substantial so it would be a question of priorities for the GNSO/Council. Rafik Dammak: we used interpretation to french and spanish at ccwg diveristy subgroup in the last calls, few people used it...and we got people asking for it Marika Konings: I recall that the CCWG-WS1 also 'demanded' interpretation for its calls, but a review of the numbers of users also showed that on many calls there were zero or just 1 or 2 people on one or more of the languages offered. Marika Konings: maybe some more awareness of the costs involved may ensure that it is a more conscious decision when interpretation is asked (and used) Rafik Dammak: interpretation for weinars make sense since the number of attendees is much higher Wolf-Ulrich Knoben: that's why we need a "solid" scenario, Marika Marika Konings: @Rafik - but my personal view is that it should be demand driven, even for webinars. Wolf-Ulrich Knoben: demand should be estimated by the WG Marika Konings: @Wolf-Ulrich, but it is probably for the Council to oversee if/how resources are used, as this would add a significant cost which would need to be funded from something else noting the budget situation we are in? 6. Discussion of the updated Work Plan: -- Anticipated for 29 March: Recommendations 22, 7, 12, 20, and 21 as well as revisiting recommendations 26-29 which have been on hold pending additional information about GDPR implementation. -- In April, the WG will revisit recommendations 6, 33, 35, and 36 which have been on hold pending work from the CCWG Accountability sub-group on diversity. Chat excerpt: Rafik Dammak: diveristy final recommendations passed the first reading yesterday Rafik Dammak: close to be approved -- The goal is for all recommendations to be implemented in June 2018. The WG will provide a Final Implementation Status Report to OEC and the GNSO Council. -- Additional time may be needed for implementation of some of the outstanding items. 7. Planning for Update to GNSO Council: -- Status report will be provided to the GNSO Council. This item is not currently on the GNSO Council agenda for ICANN61 but could be added under AOB. -- Suggestion: Do not include the internal June 2018 target date in the Council update. 8. Discussion of the implementation charter for recommendations 20 and 21 (time permitting): This item was not covered. 9. Next Meeting: 29 March 1300 UTC: Staff will send a note to the list asking whether the next meeting should take place at 12:00 UTC or 13:00 UTC.

2 1

Response Requested re: Timing of meeting on 29 March
by Julie Hedlund March 1, 2018

March 1, 2018

Dear GNSO Review Working Group members, Please see the following action item from today’s meeting: Action Item 9: Staff will send a note to the list asking whether the next meeting on 29 March should take place at 12:00 UTC or 13:00 UTC (due to US change to Daylight Saving Time on 11 March 2018). Note that upon the change to Daylight Saving Time (DT) in the US, the usual time of 13:00 UTC will change from 05:00 to 06:00 PDT/08:00 to 09:00 EDT. Please indicate whether you prefer that the time should stay at 13:00 UTC, or revert to 12:00 UTC (thus maintaining the time at 05:00 PDT/08:00 EDT). Thank you very much for your assistance. Kind regards, Julie Julie Hedlund, Policy Director

1 0

Recordings, Attendance & AC Chat from GNSO Review WG call on Thursday, 1 March 2018 at 13:00 UTC
by Nathalie Peregrine March 1, 2018

March 1, 2018

Dear all, Please find the mp3, AC Recording, attendance and AC Chat below for the GNSO Review Working Group held on Thursday, 1 March 2018 at 13:00 UTC. Mp3: https://audio.icann.org/gnso/gnso-review-01mar18-en.mp3 AC Recording: https://participate.icann.org/p7wztb89z3w/<https://participate.icann.org/p7wztb89z3w/?OWASP_CSRFTOKEN=390c3f629a9e8e92…> The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: http://gnso.icann.org/en/group-activities/calendar<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_group…> Mailing list archives: http://mm.icann.org/pipermail/gnso-review-wg/ Wiki agenda page: https://community.icann.org/x/3xW8B Attendance Members: Sara Bockey (RrSG Alternate) Wolf-Ulrich Knoben (ISPCP Primary) Lori Schulman (IPC Primary) Jen Wolfe (RySG Primary) Rafik Dammak (NCSG Primary) Participants: Pascal Bekono (NCUC) On Audio Only: Lawrence Owalale-Roberts (BC Primary) Apologies: none ICANN staff: Julie Hedlund Emily Barabas Marika Konings Berry Cobb Nathalie Peregrine ** Please let me know if your name has been left off the list ** Thank you. Kind regards, Nathalie ------------------------------- Adobe Connect chat transcript for 1 March 2018 Unavailable for this call. Please see Notes and Action items circulated by staff and posted on the wiki page: https://community.icann.org/x/3xW8B

1 0

Agenda and Materials for 01 March Meeting 13:00 UTC
by Julie Hedlund March 1, 2018

March 1, 2018

Dear GNSO Review Working Group members, Please see below the draft agenda for the meeting on Thursday, 01 March at 13:00 UTC. Please also see the attached materials and the action items below with updates from the previous meeting. Draft agenda: Review agenda/SOIs Status of Consensus Call for revised implementation charter for recommendation 34 Discussion of the revised implementation charter for recommendation 22 Discussion of the revised implementation charter for recommendations 1, 2, & 3 Discussion of the implementation charter for recommendations 7 & 12 Discussion of the updated Work Plan Planning for Update to GNSO Council Discussion of the implementation charter for recommendations 20 and 21 (time permitting) Next Meeting: 29 March 1300 UTC AOB Action Items and Updates: GNSO Review Working Group Meeting on Thursday, 08 February 2018 at 13:00 UTC Action Item 1 (revised implementation charter for recommendation 22): Staff will accept changes in the document and add text to the GNSO Review Working Group determination recommending accessibility of training, and in particular real-time interaction through remote platforms. Staff will also add language recommending that all of the trainings and learning materials are linked from the GNSO website and described in the context of the competency-based framework. Staff will send these proposed changes on the mailing list and invite feedback on proposed edits and for discussion on the 15 February call. [SEE UPDATED ATTACHED CHARTER.] Action Item 2 (revised implementation charter for recommendations 1, 2, & 3): 1) Collect additional information about the potential budget reduction for the CROPP Program and reasons for this. Move CROPP to #1. [SEE UPDATED ATTACHED CHARTER.] Action Item 3 (revised implementation charter for recommendations 1, 2, & 3): Staff will connect with ICANN staff to understand links between regional outreach, stakeholder journey, and some of the other initiatives described in the implementation charter. In revised text, focus on the manifestation of the outreach in the regions rather than describing the program. [SEE UPDATED ATTACHED CHARTER.] Action Item 4 (revised implementation charter for recommendations 1, 2, & 3): Staff will get in touch with Secretariats of SG/Cs to get more information about how they do outreach and whether any metrics are available on these efforts. [SEE UPDATED ATTACHED CHARTER/ONGOING] Action Item 5 (revised implementation charter for recommendations 1, 2, & 3): Add to metrics section, a metric that looks at engagement/level of activity/sustainability. [SEE UPDATED ATTACHED CHARTER.] Best regards, Julie Julie Hedlund, Policy Director

3 3

FOR REVIEW: Draft Status Report to the GNSO Council
by Julie Hedlund March 1, 2018

March 1, 2018

Dear GNSO Review Working Group members, The GNSO Council has requested a brief written status report from the GNSO Review Working Group for ICANN61. At this point this is not an item on the GNSO Council’s agenda at its ICANN61 meeting on 14 March, but after receiving the written report the Council could decide to add an item to its agenda. In that case, the status report should be sent to the Council by the document and motion deadline, which is Sunday, 04 March. Please see the attached draft brief report for discussion on tomorrow’s call. The final draft report will be conveyed via email by staff on behalf of the GNSO Review Working Group Chair and Vice Chair in time for the deadline. Kind regards, Julie Julie Hedlund, Policy Director

3 3

Re: [Gnso-review-wg] FOR REVIEW: Draft Status Report to the GNSOCouncil
by Kris Seeburn March 1, 2018

March 1, 2018

A ok for me too Kris > On Mar 1, 2018, at 15:40, Wolf-Ulrich.Knoben <wolf-ulrich.knoben(a)t-online.de> wrote: > > <https://www.boxbe.com/overview> This message is eligible for Automatic Cleanup! (wolf-ulrich.knoben(a)t-online.de) Add cleanup rule <https://www.boxbe.com/popup?url=https%3A%2F%2Fwww.boxbe.com%2Fcleanup%3Fkey…> | More info <http://blog.boxbe.com/general/boxbe-automatic-cleanup?tc_serial=37126024602…> > Thanks Julie, > > I'm fine with this. Just a hint to the WG status report given at ICANN60 as well as to the related OEC response would complete it. > > Best regards > > Wolf-Ulrich > > Am 01.03.2018 um 01:21 schrieb Julie Hedlund: >> Dear GNSO Review Working Group members, >> >> Â >> >> The GNSO Council has requested a brief written status report from the GNSO Review Working Group for ICANN61.Â At this point this is not an item on the GNSO Councilâs agenda at its ICANN61 meeting on 14 March, but after receiving the written report the Council could decide to add an item to its agenda.Â In that case, the status report should be sent to the Council by the document and motion deadline, which is Sunday, 04 March.Â Please see the attached draft brief report for discussion on tomorrowâs call.Â The final draft report will be conveyed via email by staff on behalf of the GNSO Review Working Group Chair and Vice Chair in time for the deadline. >> >> Â >> >> Kind regards, >> >> Julie >> >> Julie Hedlund, Policy Director >> >> >> >> _______________________________________________ >> Gnso-review-wg mailing list >> Gnso-review-wg(a)icann.org <mailto:Gnso-review-wg@icann.org> >> https://mm.icann.org/mailman/listinfo/gnso-review-wg <https://mm.icann.org/mailman/listinfo/gnso-review-wg> > _______________________________________________ > Gnso-review-wg mailing list > Gnso-review-wg(a)icann.org > https://mm.icann.org/mailman/listinfo/gnso-review-wg Kris Seeburn seeburn.k(a)gmail.com www.linkedin.com/in/kseeburn/ <http://www.linkedin.com/in/kseeburn/> "Life is a Beach, it all depends at how you look at it"

1 0

ICANN61: GNSO Sessions How to Get Organized and Remote Participation Details
by Nathalie Peregrine Feb. 27, 2018

Feb. 27, 2018

Dear all, The one-stop wiki page for all your Remote Participation queries is now available. This wiki page covers remote participation details for all GNSO open and public meetings. In addition to this, ICANN meetings’ team has put together a new ICANN meeting website which allows you to download all GNSO-related meetings to your inbox calendar in one go. 2 LINKS TO BOOKMARK NOW: ICANN61 Meeting Schedule[61.schedule.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__61.schedule.icann.org_…> GNSO Remote Participation wiki page[community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> Step 1 – Create a profile and your personalized ICANN61 schedule Go to the Meeting Schedule webpage and create a profile and login. Every session on the schedule can be selected and added to your individual schedule by clicking the Add box to the bottom right of each meeting, this adds it to your individual schedule which you can then email to yourself or add to your calendar. See next step. Step 2 - There are two ways to import your schedule into Outlook: once you’ve added all your chosen meetings to “My Schedule” go to Export. 1. Importing creates a one-time snapshot of your schedule and copies it into Outlook. If you subsequently make changes to your Pathable calendar, they will not be reflected in Outlook. 2. Subscribing creates a live feed of your schedule in Outlook. Outlook checks for changes every few hours and updates your calendar appropriately. * For Outlook calendars: http://support.pathable.com/knowledgebase/articles/81449-moving-your-schedu…<https://urldefense.proofpoint.com/v2/url?u=http-3A__support.pathable.com_kn…> * For Google calendars: http://support.pathable.com/knowledgebase/articles/1313-moving-your-schedul…<https://urldefense.proofpoint.com/v2/url?u=http-3A__support.pathable.com_kn…> Step 3 All Adobe Connect rooms (which can be found on the session information on the Meeting Schedule<https://urldefense.proofpoint.com/v2/url?u=https-3A__61.schedule.icann.org_…> and on the GNSO Remote Participation wiki page<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…>) will provide audio streaming only Adobe Connect room microphones will not be enabled. If you cannot join an Adobe Connect room for a session, and will need to dial in with your phone, please refer to the GNSO Remote Participation wiki page<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_…> for the audio pass codes and dial in numbers. Please also follow the previous steps if you wish to take part in the session over the phone. Step 4 Please download the mobile app by searching for “ICANN61” in your app stores. Nathalie Peregrine and Julie Bisland will be onsite in San Juan to assist you directly. For all GNSO meeting related queries (RP or others), please email us at: gnso-secs(a)icann.org<applewebdata://FB60497E-61D8-4FE9-BF9C-EB238191E416/gnso-secs@icann.org> and we will be more than happy to assist! Kind regards, GNSO SO/AC Support team Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Email: nathalie.peregrine(a)icann.org <nathalie.peregrine(a)icann.org%20> Skype: nathalie.peregrine.icann Find out more about the GNSO by taking our interactive courses<applewebdata://EB3A6F47-9760-400D-A39B-A7EFFC56B467/learn.icann.org/courses…> and visiting the GNSO Newcomer pages<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gn…>

1 0

Agenda and Materials for 15 February Meeting 13:00 UTC
by Julie Hedlund Feb. 15, 2018

Feb. 15, 2018

Dear GNSO Review Working Group members, Please see below the draft agenda for the meeting on Thursday, 15 February at 13:00 UTC. Please also see the attached materials and the action items below with updates from the previous meeting. Draft agenda: Review agenda/SOIs Status of Consensus Call for revised implementation charter for recommendation 34 Discussion of the revised implementation charter for recommendation 22 Discussion of the revised implementation charter for recommendations 1, 2, & 3 Discussion of the updated Work Plan Planning for Update to GNSO Council at ICANN61 on 14 March 2018. Next Meeting: 01 March 1300 UTC AOB Action Items and Updates: GNSO Review Working Group Meeting on Thursday, 08 February 2018 at 13:00 UTC Action Item 1 (revised implementation charter for recommendation 22): Staff will accept changes in the document and add text to the GNSO Review Working Group determination recommending accessibility of training, and in particular real-time interaction through remote platforms. Staff will also add language recommending that all of the trainings and learning materials are linked from the GNSO website and described in the context of the competency-based framework. Staff will send these proposed changes on the mailing list and invite feedback on proposed edits and for discussion on the 15 February call. [SEE UPDATED ATTACHED CHARTER.] Action Item 2 (revised implementation charter for recommendations 1, 2, & 3): 1) Collect additional information about the potential budget reduction for the CROPP Program and reasons for this. Move CROPP to #1. [SEE UPDATED ATTACHED CHARTER.] Action Item 3 (revised implementation charter for recommendations 1, 2, & 3): Staff will connect with ICANN staff to understand links between regional outreach, stakeholder journey, and some of the other initiatives described in the implementation charter. In revised text, focus on the manifestation of the outreach in the regions rather than describing the program. [SEE UPDATED ATTACHED CHARTER.] Action Item 4 (revised implementation charter for recommendations 1, 2, & 3): Staff will get in touch with Secretariats of SG/Cs to get more information about how they do outreach and whether any metrics are available on these efforts. [ONGOING] Action Item 5 (revised implementation charter for recommendations 1, 2, & 3): Add to metrics section, a metric that looks at engagement/level of activity/sustainability. [SEE UPDATED ATTACHED CHARTER.] Best regards, Julie Julie Hedlund, Policy Director

2 1

FOR REVIEW: Revised Charter for Recommendation 22
by Julie Hedlund Feb. 14, 2018

Feb. 14, 2018

Dear GNSO Review Working Group members, Per Action Item 1 below, please see for your review the attached revised charter for Recommendation 22. In particular, please see the revised text in redline in the Working Group Determination section of the document, and as follows (new text in red and brackets): “The Working Group has reviewed the existing ICANN-provided training options in the context of a competency-based framework and has determined that these address the recommendation that there should be a competency-based framework to identify development needs and opportunities. [The Working Group recommends that training options should focus on accessibility of training, and in particular real-time interaction through remote platforms. The Working Group also recommends that all of the training and learning materials are linked from the GNSO website and described in the context of the competency-based framework.]” Best regards, Julie Julie Hedlund, Policy Director Notes & Action Items GNSO Review Working Group Meeting on Thursday, 08 February 2018 at 13:00 UTC Action Items: Action Item 1 (revised implementation charter for recommendation 22): Staff will accept changes in the document and add text to the GNSO Review Working Group determination recommending accessibility of training, and in particular real-time interaction through remote platforms. Staff will also add language recommending that all of the trainings and learning materials are linked from the GNSO website and described in the context of the competency-based framework. Staff will send these proposed changes on the mailing list and invite feedback on proposed edits and for discussion on the 15 February call. Action Item 2 (revised implementation charter for recommendations 1, 2, & 3): 1) Collect additional information about the potential budget reduction for the CROPP Program and reasons for this. Move CROPP to #1. Action Item 3 (revised implementation charter for recommendations 1, 2, & 3): Staff will connect with ICANN staff to understand links between regional outreach, stakeholder journey, and some of the other initiatives described in the implementation charter. In revised text, focus on the manifestation of the outreach in the regions rather than describing the program. Action Item 4 (revised implementation charter for recommendations 1, 2, & 3): Staff will get in touch with Secretariats of SG/Cs to get more information about how they do outreach and whether any metrics are available on these efforts. Action Item 5 (revised implementation charter for recommendations 1, 2, & 3): Add to metrics section, a metric that looks at engagement/level of activity/sustainability. Notes: 1. Review agenda/SOIs: No SOI Updates. 2. Status of Consensus Call for revised implementation charter for recommendation 34: -- A call for consensus was opened 3 weeks ago. This was a longer consensus call due to meetings over the last few weeks. The consensus call will close later today. Staff will send an update once the deadline has passed. If there are no comments or objections, the implementation charter will be deemed to be approved by full consensus. >From the chat: Kris Seeburn: Please put down a kind of attendance or metrics to see whether it is working -- Staff clarified that individual working groups do informal assessments regarding attendance to ensure that rotation is serving the intended purpose. Kris Seeburn: ok that sounds great...... Sara Bockey: Yes, and I've seen this happen :) 3. Discussion of the revised implementation charter for recommendation 22: -- During the last meeting, staff was asked to more clearly link the programs available to a competency-based framework. -- Text describing the framework has been added. Throughout text about individual programs, specific references linking program elements to the framework have also been added. -- The text now includes additional references to existing programs and detailed explanations of these programs. -- Question: The list of opportunities is a mix of online and face-to-face programs. Is this sufficiently clear in the text? Answer: Some of these programs are exclusively online, whereas others are a combination of online and face-to-face. Of the online materials, some are static and others are more interactive. -- There is a difference between online and face-to-face programs. Face-to-face programs will reach fewer people. Is it clear that the ones that require in-person attendance require the participants to physically be present? The only program that requires physical attendance is the ICANN Academy training. The majority of the training does not require attendance in-person. >From the chat: Marika Konings: but there is the ability to track 'attendance' for GNSO Learn, no? So could it be made a requirement to take certain courses? Marika Konings: not in person I mean, but that it has been taken Kris Seeburn: maybe we could do face to face training plannings - perhaps that will help the new members Kris Seeburn: i understand ...but if you see the list of elected sometimes you find that many did not go through them.... Lori Schulman: If there is a requirement to take courses then are they all online? Lori Schulman: The Face2Face Leadership program was very good. I was sorry that more couldn't take it. There were no phone leadership courses and I think that is a great idea. -- There are newcomer and fellowship programs where community members are funded to travel to ICANN meetings. These will also include some training. These appear to have a somewhat different focus (newcomers vs. Council members and WG members). -- The opportunity to get training should be as wide as possible to reach as many stakeholders as possible. Ideally, as many courses as possible should be available online. This could be a recommendation from the group. Tracking is also important to gather information about who has completed the courses and whether the materials have been helpful to participants. Is it possible to put text about these items in the determination? -- Additional support for making materials available online. At the same time, materials that are passively consumed are less helpful. Adobe Connect sessions with live interaction are more interactive. The most well-rounded trainings have a little bit of everything: face-to-face, online static content, dynamic online interaction (such as through Adobe Connect). >From the chat: Kris Seeburn: when comes to leadership it is a real challenge and also the understanding of consensus Kris Seeburn: but i am in support with wolf ulrich Marika Konings: Maybe providing information on all the training available in an integrated manner may already help? Kris Seeburn: ALAC is doing that already -- People may currently have trouble finding appropriate learning opportunities. It may be helpful to have a one-stop-shop with information about all of the different opportunities, who is eligible, who can apply/participate, and how participation takes place (online, in-person, etc). This may be able to help people to identify what is missing. -- See Action 1 reflecting next steps regarding Recommendation 22. 4. Discussion of the revised implementation charter for recommendations 1, 2, & 3: -- On the last call, staff was asked to look at GNSO outreach efforts within SG/Cs and the GNSO generally, add text regarding recommendations on the use of metrics, and add text about reducing cost barriers to participation. Staff added text on these items. -- There is ongoing evaluation of the fellows program and ongoing oversight within the GNSO Council and SG/Cs. There is currently discussion underway regarding the fellowship program in the context of the FY19 Budget. -- With respect to metrics, staff added text recommending ways to use metrics to evaluate effectiveness (see 3: Suggested Metrics on page 3 of the implementation charter). -- Question: CROPP appears to be missing from 1, but appears in 3. Should it be included in 1 because it is not only GNSO-related? Answer: Yes, this should be moved. -- Question: How does the Regional Outreach Program fit into the other elements related to outreach? Answer: Additional information needs to be gathered on this front. There are local events, connections to institutions of higher learning, and other activities. -- Under Stakeholder Group and Constituency outreach, is it possible to provide additional information about the activities. Each SG/C has the information about outreach in different places. It can be difficult to find this on the different websites. Is there a way to improve this? -- We should learn from the experience of SG/Cs regarding outreach. -- Question from staff: regarding metrics, would it be helpful to get SG/C input? -- Suggestion: contact the secretariats of the SG/Cs about both metrics and outreach measures? -- Suggestion: include not only in metrics on the number of new members but also try to track engagement of members. The real success would be having more active members, not just new members. >From the chat: Kris Seeburn: i would take constituencies and break into region as well 5. Status of the Work Plan: Update will be included in the call next week. 6. Next Meeting: 15 February 1300 UTC (moved from 22 February due to conflict with GNSO Council meeting). 7. AOB: None.

2 2