NOTES | UAC #8 | 20 December 2023 (13:00 UTC) 1. Welcome & roll call Meeting wiki: https://community.icann.org/x/OYAYEQ UAC main page: https://community.icann.org/x/UIfxDg Low attendance: meeting started 3 min. After the top of the hour Attendance: Mirjana, Abdalmonem, Regina, Jiankang, Sarmad, Vadim, Qing Cai, Sarmad, Bart, Joke. as taken from the zoom room. No apologies received to Bart and Kim’s knowledge Welcome by Abdalmonem Apologies for not being able to join the meeting last week, due to a family matter. Thank you for the constructive discussions. 2. Administrative matters a. SoI ccNSO guideline SOI/COI https://ccnso.icann.org/sites/default/files/field-attached/ccnso-internal-pr... SOI form https://forms.gle/79Jw4wSnNhn5W4Z46 Abdalmomen: reminder to please complete the SOI form Bart: voluntary, unique to ccNSO. If you have an update regarding your SOI, please share with the team. For transparency reasons. Any updates? None b. Action items: staff to circulate draft Roadmap to date Completed. See further discussion during item 4 on today’s agenda c. Self-nomination UAC Volunteer UA Day selection panel (volunteers) Completed No volunteers to date: Some UAC members are conflicted, including Abdalmonem and Qing Cai. Abdalmomen invites members to step forward. Sarmad confirmed that UA Day applicants cannot be a member of the selection committee. Bart: We discussed the time commitment last week. The group kicked off its work. First meeting will be held later today, they will discuss the evaluation criteria. They will review the proposals over the next weeks. 130 proposals received. Sarmad: first meeting is tomorrow is at 10:00 UTC. Regina: We haven't applied for an official proposal for the UA day, so I would be eligible. I would really like to let the spot for another volunteer from our group, but I do agree a rep from our group would be good. So in case nobody else steps up, I could do it. d. Letter to Invite IDN ccTLDs to participate Ongoing Abdalmomen: draft? Bart: no draft yet. Can circulate it by the 1st time we meet again in 2024. We need to ensure we have the best way forward. Following consultation with Sarmad, the proposal is for UAC leaders to invite IDN ccTLD managers to either participate in UAC work as a member of the committee, and/or to be subscribed to the community mailing list UAC will create (based on DASC model). ICANN staff (GSE) will also reach out to IDN ccTLD managers Action item #1 Staff to prepare a draft letter by the first UAC meeting in January. e. Scheduling of sessions: Doodle poll end January Ongoing Next UAC meeting on 17 Jan and 31 Jan. Note the changed start time on the 17th, 14:30 UTC, to avoid future overlap with the IGLC meeting at 13:00 UTC. Wednesday is a day when many WG/C meet. We tend to avoid Fridays and Mondays. By the end January, we have more insights regarding the ccPDP4 work. Proposal for this group to move from Wednesday to Tuesday, if the ccPDP4 Tuesday slot frees up. We will circulate a doodle poll. ccPDP4 aims to complete its work by mid-February at the latest. To be confirmed. Regina: Thursday might be an option too? Bart: yes, only potential conflict would be the MPC. Other groups have a standard slot on Thursday too. We will make some suggestions, and ensure we avoid overlap with other fixed slots 3. Charter UA ccTLD library: update text UAC repository/library terms of reference Doc https://docs.google.com/document/d/10hzfbJF4ud6x6k8HDELCjMhrCvgpzCJx/edit?usp=sharing&ouid=101111448672284939009&rtpof=true&sd=true<https://urldefense.com/v3/__https:/docs.google.com/document/d/10hzfbJF4ud6x6k8HDELCjMhrCvgpzCJx/edit?usp=sharing&ouid=101111448672284939009&rtpof=true&sd=true__;!!PtGJab4!4r4o6D8uvJKx7HdKb5gON2K4e8AdoSbgrMkdwhyaYSCLi_BwdAZozCoB2H2La1OM8akWBiS-yOXxs3Mjm_Zqcqc4QNSWAk8UQ40b$> Circulated originally by Kimberly with the request for UAC members to comment, with reminders by Joke and Bart. Repository with relevant information for ccTLDs, regarding UA-related matters. There will be a small team that reviews potential submissions to the library. The list is a vetted list, and materials are only published following consensus by the small team (also referred to as “editorial board”). The library will be on the UAC workspace. Accessible by all. You will see the links to the documents. The idea is to create a library. The library has various sub-categories. You will see those categories included in the ToR as well (Terms of Reference = Charter). It is important to agree on the charter before doing the actual work Sarmad: trying to think about a good set of docs to propose. Long list is not helpful. The UA readiness Report is published once a year. It has links to all other reports, and is a useful source of information. Bart: yes. Or a link to the readiness survey results. Qing Cai: question about the articles. Does it include news from our own ccTLDs? Bart: could fit under announcements? Qing Cai: for instance, invites to join our conference. Bart: events? Qing Cai: yes. Could not comment via the google account. Hence my comment here. Bart: important to have the categories correct. The Charter drives the library, and your role. The Charter is currently still in a draft version. The tracker which relates to the role of the editorial board is ready as well. Sarmad: have a category “cooperation with other SO/ACs”. Bart: there are other channels too: mailing list, or wiki. This is not the place to inform ccTLDs about the work by this ccNSO UA committee, but rather to inform the community about UA and UA readiness. Abdalmomen: agreed.
comments regarding “overview” section in ToR
Qing Cai: should we put materials here? e.g. UA readiness report See the materials from the UASG website. Bart: the charter defines the “rules” for populating the library/repository. Once the library goes live, anybody can make suggestions for inclusion in the library. The editorial board will review the proposed submissions, to ensure they meet expectations. The Terms of Reference we discuss now determine the how and the what: details about the repository, and the role of the editorial board, which vets proposed submissions for the library. Abdalmomen: information about UA and registering IDNs, for ASCII and IDN ccTLD managers alike Regina: maybe we can remove the IDN in brackets then? maybe IDN domain names and their management? as some ccTLDs may (not yet) have some under the management. May consider introducing Abdalmomen: “IDN domain names” might create confusion. Use “non-latin domain names” instead Sarmad: latin script can also have IDNs. we should not say non-latin. Abdalmomen: ok Qing Cai: typo. Repetitive word
comments regarding editorial board section in ToR
Bart: please use “editorial board”. Reflects your role. Any objections? Regina: agree. Be consistent. Bart: “library editorial board” instead of “content editorial board” Regina: agree Abdalmomen: might not be clear to the reader. Bart: ok. Will check for consistency by the next meeting
categories
Bart: Any comments or concerns? Vadim: question. See also in the google doc comments. Technical description? Instructions regarding e-mail configuration or use cases. Where would that fit? Articles? Or have a new category? Technical view? Bart: tools or technology category? Sarmad: technical training? Code repository? Regina: code repository as part of the tools? Sarmad: agree. Just overall heading “technical information” and have trainings, codes etc underneath that category. Regina: announcement and news. Time-sensitive. Have a separate time-sensitive category? Sarmad: technical materials Regina: where would the case studies fit? Success stories? Under Articles? Presentations are also one-off, connected to an event How will we differentiate between articles/commentaries or presentations and reports? Abdalmomen: UAC materials. Bart: case studies as a separate category might make sense Regina: important to have them, either separate or under another umbrella. Let’s think about it and discuss at the next meeting. Make sure we are consistent in labeling.
additional responsibilities by the Library Editorial Board
Comment by Abdalmomen. Bart: is this a role for the Library Editorial Board? Rather a role for the UAC Abdalmomen: agree. Action item #2: Staff to adjust the draft ToR, based on the discussions by UAC on 20 December. UAC members to review the proposed ToR and suggest comments or edits prior to UAC meeting #9 4. Review results Napkin exercises to date Draft UAC workplan (sections on napkin pitches) https://docs.google.com/document/d/1Td27YCcDrDZ3pa4JzyX6n6CAY6anIG_n2kizDMcJ... Circulated one week ago, with the request for UAC members to comment Action item #3: UAC members invited to review the proposed UAC workpan prior to UAC meeting #9. During that meeting, the impact-effort analysis will be an item on the agenda. We reached the top of the hour. 5. Time permitting: start impact/effort analysis Deferred to next meeting 6. Selection volunteer (zoom poll, if needed) Regina: I can volunteer. Would appreciate receiving the meeting invite for the 1st meeting tomorrow. Sarmad: will follow up with Regina. Bart: thanks for informing UAC about this opportunity 7. Next meetings 17 January 2024 – 14.30 UTC (avoid overlap with ccNSO IGLC meeting). Note new time, previously tentatively scheduled for 14:15 UTC. 31 January 2024 – 13.00 UTC Qing Cai: works. Pending potential UASG meeting Jiankang: I have another meeting at 15:00 UTC. Bart: ok. 8. AOB none 9. Adjourn This meeting has been adjourned. Warm regards for staff and members for joining today. See you at the next meeting. Joke Braeken joke.braeken@icann.org<mailto:joke.braeken@icann.org>