2023-01-23 Applicant Support GGP - Meeting #05

Notes/ Action Items

Action Items:

TASKS 3, 4, and 5:

1. Staff to send to the GGP WG list Section 9 of the GGP along with related text from the Bylaws. 
2. Rafik to provide text of his question for the GNSO Council for the WG to consider.
3. WG members to provide their comments in the Google sheet at https://docs.google.com/spreadsheets/d/13Q9QRDOBC0mdPBRDWxfMsUPtt4d-gVI9w8pBCkfugQc/edit?usp=sharing or via separate document by Thursday, 26 January for staff to integrate in the main sheet as necessary.
4. Staff to draft a sample survey (ongoing).Notes:

Notes:

1. Welcome & Updates to Statements of Interest (5 min.)

• No updates to SOIs.
• Paul McGrady and Mike Silber gave a brief update to the GNSO Council on the current status of the GGP WG’s work and work plan at the GNSO Council meeting on 19 January 2023.

2. Update from ICANN org staff on Applicant Support in the ODA (30 min.) – see attached slides.

a. Briefing from GDS staff (20 min.)

b. Q&A/discussion (10 min.)

• Question: About the depth of services provided pro bono and how this helped to encourage applicants. Were they paid for by ICANN? Answer: ICANN or didn’t fuudnd them and we don’t know how much they were used. It is also not clear how applicants were made aware that pro bono services were available.
• Good in future to track whether the applicants were able to use the pro bono services.  Need to track that usage.
• Comment: Clarification – understand that the ODA had to be released before the GGP makes recommendations.  Will the ODA be updated?  How will the GGP recommendations be taken into consideration.  Answer: The GGP’s recommendation report will go to the GNSO Council.  It will inform the IRT on Applicant Support.  The Liaison can take a question back to the Council.  The GGP is not a PDP; it is how the Council gives feedback to existing processes.  After the Board report there is a Board approval process.   Staff will send Section 9 of the GGP to the list and ask for comments with clarification from Rafik concerning his question.
• Question: according to the last point, there wouldn’t be "targeted regions" but "struggled applicants with financial needs"?  Answer: Moving away from regional designation of need.

ACTION ITEMS:

1. Staff to send to the GGP WG list Section 9 of the GGP along with related text from the Bylaws. 
2. Rafik to provide text of his question for the GNSO Council for the WG to consider.

3. Continue Discussion of Task 3 (30 min.) – see attached document and Google sheet at: https://docs.google.com/spreadsheets/d/13Q9QRDOBC0mdPBRDWxfMsUPtt4d-gVI9w8pBCkfugQc/edit?usp=sharing

a. Review Draft Discussion Framework (10 min.)

b.. Discussion (20 min.)

Awareness and Education:

Row 2: number of outreach events and follow up communications with potential applicants

• Maureen’s comments: What could we propose from the GGP and how to transfer that. 
• Identify existing events that non-profits attend.
• Rafik’s comments: Split into those organized by ICANN and by others.  We know with the first round that there was criticism that there was no outreach.  We need to leverage networking in the community, but want to see that ICANN is doing first.
• At-Large community keen that the wider community as to what ICANN is doing and why it’s doing it.  So there is greater awareness.
• CPWG document: Discussion around how we measure success?  There is the formal outreach but also community outreach.

Row 3: level of awareness about the New gTLD Program/Applicant Support Program

• Rafik’s comment: Not sure how to measure – what is the proxy here?  A survey?
• Roz’s comments:  Need to consider where the outreach is going in considering diversity. 

ACTION ITEM: WG members to provide their comments in the Google sheet at https://docs.google.com/spreadsheets/d/13Q9QRDOBC0mdPBRDWxfMsUPtt4d-gVI9w8pBCkfugQc/edit?usp=sharing or via separate document by Thursday, 26 January for staff to integrate in the main sheet as necessary.

4. AOB: Next meeting

• There are ICANN staff offsite meetings the week of 06 February, but staff will be able to support the regularly scheduled meeting on Monday the 6^th at the alternating time of 20:00 UTC.  Thus, the next meeting will be Monday, 06 February at 20:00 UTC.