14:54:25 RRSAgent has joined #maturity 14:54:29 logging to https://www.w3.org/2026/05/06-maturity-irc 14:54:29 RRSAgent, make logs Public 14:54:30 please title this meeting ("meeting: ..."), Fazio 14:55:07 meeting: Maturity Model Task Force 14:55:33 chair: David Fazio 14:55:43 Agenda+ New Business 14:55:43 Agenda+ Follow Up with Mark and Jeff on Github Issues #328 #331 14:55:43 Agenda+ Github Issue #335 Clarify impact on product deliver 14:55:43 Agenda+ Github Issue #323 Strengthen motivation for procurement language 14:55:50 present+ 14:59:26 JeffAdams-UN has joined #maturity 14:59:35 Mark_Miller has joined #Maturity 15:00:44 Sheri_B-H has joined #maturity 15:00:53 present+ 15:01:09 CharlesL has joined #maturity 15:01:14 present+ 15:01:18 present+ 15:01:57 Crispy has joined #maturity 15:02:06 present+ 15:02:23 present+ 15:03:25 jkline has joined #maturity 15:03:28 present+ 15:03:34 janina has joined #maturity 15:03:38 present+ 15:04:00 scribe+ 15:04:21 Zakim, next item 15:04:21 agendum 1 -- New Business -- taken up [from Fazio] 15:04:40 Sheri_B-H: New Book Published! 15:05:23 SusiPallero has joined #maturity 15:05:56 https://www.amazon.com/gp/product/1041018681/ref=ox_sc_act_title_1?smid=ATVPDKIKX0DER&psc=1 15:07:43 ... published with T&F, which is GCA certified by Benetech 15:10:17 zakim, next item 15:10:17 agendum 2 -- Follow Up with Mark and Jeff on Github Issues #328 #331 -- taken up [from Fazio] 15:10:38 Present+ 15:11:04 jkline has joined #maturity 15:11:12 https://github.com/w3c/maturity-model/issues/331 15:11:13 https://github.com/w3c/maturity-model/issues/331 -> Issue 331 "Proof points" language unclear (by iadawn) 15:11:19 https://github.com/w3c/maturity-model/issues/334 15:11:20 https://github.com/w3c/maturity-model/issues/334 -> Issue 334 Improve the About section (by iadawn) 15:11:47 JeffAdams-UN: maybe we don't need an about section. 15:12:07 ... we rewrote the abstract (Mark, Jeff and Claude AI) 15:12:59 ..., we removed the about section, and we rewrote How to use the model. 15:13:28 ..., I didn't not rewrite the customizing part as it looked in good order. 15:14:06 Mark_Miller: we did this illustratively. love the feedback, 15:14:19 Fazio: Where is this now? 15:14:27 Mark_Miller: emails back and forth. 15:14:34 JeffAdams-UN: we can put it in Google Docs. 15:14:51 Fazio: if you have it handy please share it with the group. 15:14:58 Mark_Miller: should we do a google Docs then? 15:15:08 Fazio: Yes, but there can be issues with Google Docs. 15:15:34 janina: I don't do Google Docs, I export it to Docs 15:15:52 ..., anything in MarkDown I am good 15:16:15 ..., change tracking is difficult. We should all re-read this. 15:16:45 ..., lets not nit-pic only substantive changes / issues. 15:17:32 Fazio: two versions maybe one we can comment on and one maybe to read. 15:17:53 JeffAdams-UN: I will be curious if Janina if this works for you 15:18:08 https://www.notion.so/jeffadams/About-Abstract-Current-Draft-358a25b4c196800f883cf1974e4b15e6?source=copy_link 15:18:39 ..., this is a Notion Doc that allows for suggestions / comments we will find out how accessible it is. 15:18:59 ..., I will follow up with a Google Doc afterwards 15:19:08 +1 15:20:34 got it 15:21:00 ..., Claude AI Desktop can connect with this and you tell what the AI can/cant do. 15:23:42 ..., When we put it into GitHub, that we are treating 328 and 334 together, but be clear in the wording. We don't want the About / Abstract separately. 15:24:16 Fazio: Yes we can specify that multiple issues are tagged with a PR. 15:24:38 JeffAdams-UN: #345 repetition, I worked on this too. 15:25:03 https://github.com/w3c/maturity-model/issues/345 15:25:04 https://github.com/w3c/maturity-model/issues/345 -> Issue 345 Repetition in 'how to evaluate...' (by iadawn) 15:25:37 ..., I can put it directly into Github if you ant. 15:25:53 ..., the how to evaluate sections. 15:26:39 Fazio: yes send that to the group as well. 15:26:42 JeffAdams-UN: when I create a google doc for 328 / 334, I can also provide this 345 work as well. 15:26:54 ..., it is a long revision. 15:27:09 ..., will put it in a doc and will send it along 15:27:42 no 15:30:11 Charles: Correction: it is not 331 the github issue is 328. 15:30:22 https://github.com/w3c/maturity-model/issues/328 15:30:23 https://github.com/w3c/maturity-model/issues/328 -> Issue 328 Clarify what model can do in abstract (by iadawn) 15:31:44 zakim, next item 15:31:44 agendum 3 -- Github Issue #335 Clarify impact on product deliver -- taken up [from Fazio] 15:31:54 https://github.com/w3c/maturity-model/issues/335 15:31:55 https://github.com/w3c/maturity-model/issues/335 -> Issue 335 Clarify impact on product deliver (by iadawn) 15:32:47 Fazio: Issue: The AMM covers the accessibility of the organisational environment but hints that it is important for delivery of accessible products - these are two different things but this is not clear. 15:33:51 Crispy has left #maturity 15:35:19 jeffK: The MM covers this some company uses products where others build products. I don't understand. 15:36:26 q+ 15:36:32 janina: If what he is asking for is unclear, or we need further information we can ask for clarification or suggestions. 15:38:15 Sheri_B-H: we went to lengths to avoid the word "inclusion" on purpose to avoid potential issues. i.e. support dimension. 15:38:27 janina: we are web focused. 15:39:04 Sheri_B-H: point to all the 2025 exec orders, we are trying to make this adoptable even from Gov. organizations. 15:39:52 Fazio: we are about everything going into the process not for creating the products which ISO addresses. 15:41:17 ..., I will point out the differences from our model with ISOs. 15:42:01 JeffAdams-UN: same with Culture. 15:42:08 ack Mark_Miller 15:42:34 Mark_Miller: if we go back to what Janina says, lets ask for examples from him directly. 15:43:32 ..., working on the organization and making that accessible. the inclusive of the org helps support creating a11y digital assets. 15:44:16 ..., just lets have him explain further. 15:44:26 janina: Yes, we can do that. 15:45:15 Fazio: don't we want these part of the same, there is no value to separate it. 15:46:14 Mark_Miller: I would just say, "We are trying to address this issue, we still don't understand your point." 15:46:23 Sheri_B-H: We also had the deliberate choice to inclusivity 15:48:22 s/inclusivity/not include inclusion 15:49:37 JeffK: "This maturity model takes a holistic approach" 15:50:15 Mark_Miller: KIS "We don't understand your issue" 15:53:24 s/KIS// 15:56:05 comment to issue #335 We have discussed this issue at length on 05/06/2026. We believe that an accessible environment and accessible product development are one and the same, and would like to better understand the distinction that you see in separating them. 15:57:10 rrsagent, make logs public 15:57:19 rrsagent, draft minutes 15:57:21 I have made the request to generate https://www.w3.org/2026/05/06-maturity-minutes.html CharlesL 15:57:41 zakim, end meeting 15:57:41 As of this point the attendees have been Fazio, Sheri_B-H, JeffAdams-UN, CharlesL, Crispy, Mark_Miller, jkline, janina, SusiPallero 15:57:43 RRSAgent, please draft minutes 15:57:45 I have made the request to generate https://www.w3.org/2026/05/06-maturity-minutes.html Zakim 15:57:50 I am happy to have been of service, CharlesL; please remember to excuse RRSAgent. Goodbye 15:57:51 Zakim has left #maturity 16:09:43 CharlesL has left #maturity 16:24:10 kirkwood has joined #maturity 16:24:10 alastairc has joined #maturity