15:51:43 RRSAgent has joined #maturity 15:51:48 logging to https://www.w3.org/2024/01/31-maturity-irc 15:51:48 RRSAgent, make logs Public 15:51:49 please title this meeting ("meeting: ..."), Fazio_ 15:52:10 meeting: Maturity Model Task Force 15:53:05 Agenda+ New Business 15:53:22 Agenda+ Github Issues 43 and 85 (Doc Usability work: Stacey, Jeff, Mark, Susi) 15:53:38 Agenda+ Maturity Model Scoring 15:54:00 Agenda+ Github Issue #78 3.3.2 Ratings for Evaluation - Support section: why is knowledge and skills mentioned 15:54:00 /issues/78 -> #78 15:54:26 Agenda+ Github Issue #104 Proof points = Written or tangible evidence, according to definition, not an 'or' / 'other' part / sub-section 15:54:26 /issues/104 -> #104 15:54:51 Agenda+ Github Issue #103 Where are the "Outcomes" in the Maturity Model Structure? 15:54:51 /issues/103 -> #103 15:58:16 Chair: Fazio 15:58:32 present+ 16:00:08 Mark_Miller has joined #Maturity 16:01:42 CharlesL1 has joined #maturity 16:02:33 present+ 16:02:39 stacey has joined #maturity 16:02:44 nadine has joined #maturity 16:03:03 Nichole_ has joined #maturity 16:03:09 present+ 16:03:13 present+ 16:03:32 janina has joined #maturity 16:03:35 present+ 16:03:37 present+ 16:03:47 kline has joined #maturity 16:03:51 present+ 16:03:59 nehaj has joined #maturity 16:03:59 present+ 16:03:59 scribe+ 16:04:03 scribe+ 16:04:04 present+ 16:04:34 zakim next item 16:04:36 SusiPallero has joined #maturity 16:04:53 zakim, next item 16:04:53 agendum 1 -- New Business -- taken up [from Fazio_] 16:06:38 Fazio_: Had a meeting with Intel head of accessibility. Intel is using the maturity model. Having some difficulties as they are so big. Will be reaching out to Brian for participation. 16:06:52 Zakim, next item 16:06:52 agendum 2 -- Github Issues 43 and 85 (Doc Usability work: Stacey, Jeff, Mark, Susi) -- taken up [from Fazio_] 16:07:53 stacey: link to google doc for potential solves for issues 43, 85, and 89. https://docs.google.com/document/d/1Wrhomdc2gJWIkDPOveiH3_ig1bddTMonEhIDZIzohrc/edit?usp=sharing 16:10:56 stacey: Issues 43, 85 and 89: usability of understanding how to rate and evaluate proof point How to rate and evaluate the dimensions of each section 16:11:28 stacey: Review of google doc 16:14:29 present+ 16:14:48 +1 to Mark's comment on "measurable" term 16:15:08 Fazio_: Should Optimize say they have proof? 16:15:36 stacey: Document is editable and welcome suggestions 16:16:08 q+ 16:16:29 stacey: This removes the table 16:17:09 CharlesL1: Moves it above the proof points 16:17:16 q? 16:18:00 ack SusiPallero 16:18:26 SusiPallero: The document is a little redundant and may need review. 16:19:20 stacey: One or two people to read through the whole document then assign editors 16:21:11 Fazio_: Does it work the same if we say you have proof points that demonstrate… 16:22:10 jeff 16:22:26 kline: Put heigh up: achieved maturity level proof point should be supported by documentation. 16:23:35 stacey: May need to review for clarity. Use different methods to review – read, listen etc. 16:24:05 stacey: Each one is customized for the section. Take a look and add comments. 16:25:07 stacey: Read the comment Jeff and Susi added 16:25:35 Fazio_: Reading proof points 43, 85 and 89 16:27:04 Fazio_: Resolving issues. Will update later comment then. 16:27:42 CharlesL1: I would only close issues when in the editor’s draft. 16:29:30 janina: Create and editor’s draft and make changes there. Close the issue once it is in the editor’s draft. 16:32:42 Usability google doc addresses Issues 43 and 85. Will close once Editors drsft is updated 16:33:46 q? 16:33:58 kline has joined #maturity 16:34:05 present+ 16:34:15 kline: MJ is looking for consistent language across all dimensions. I think Stacey started that. We could come up with global language… Stacey has done that. Addresses 85 16:34:48 stacey: Will it address 89? 16:35:08 Fazio_: Reading 89 16:35:51 stacey: Looking at it aligning with clarity and consistency 16:36:49 zakim, next item 16:36:49 agendum 3 -- Maturity Model Scoring -- taken up [from Fazio_] 16:39:24 kline: The way the scoring is set up is confusing and not that meaningful. Need to focus on a new scoring method going forward. Trying to set up different level of scores at different stages is confusing and not meaningful Need a way to tally these things. Ie. we have 5 pp in integrate and 5 in optimize and 5 launch. 16:39:58 Fazio_: Scoring can be ambiguous. Same issue in WCAG. 16:40:28 q+ 16:40:57 kline: Can’t solve it now. Volunteer to take up a subgroup to come up with a better method for showing progress. 16:43:00 q? 16:43:07 ack CharlesL1 16:43:15 Mark_Miller: I’d like to be part of subgroup 16:43:57 CharlesL1: I’d like to be part of the subgroup. View for each dimension: what is the majority of proof points and get a sense. 16:45:09 q? 16:45:44 kline: Should someone build a set of requirements for web interface? 16:46:04 ack kline 16:46:10 CharlesL1: Export feature in jSon 16:46:42 Fazio_: Don’t want to house at W3C 16:46:55 Zakim, next item 16:46:55 I see a speaker queue remaining and respectfully decline to close this agendum, Mark_Miller 16:47:01 ack me 16:47:12 q? 16:47:18 zakim, next item 16:47:18 agendum 4 -- Github Issue #78 3.3.2 Ratings for Evaluation - Support section: why is knowledge and skills mentioned -- taken up [from Fazio_] 16:47:18 /issues/78 -> #78 16:48:33 Fazio_: Tried to address last time group was small so doing again. 16:49:17 Fazio has joined #maturity 16:49:21 https://github.com/w3c/maturity-model/issues/78 16:49:22 https://github.com/w3c/maturity-model/issues/78 -> Issue 78 3.3.2 Ratings for Evaluation - Support section: why is knowledge and skills mentioned? (by maryjom) 16:49:47 Fazio: Reading 78 16:51:04 kline: In support: training is in place with staff to support dimension 16:52:08 kline: Modify to say there is no training programs in place for support staff. 16:52:51 CharlesL1: It is inconsistent but in tables that are going to be rewritten. Need to be consistent. 16:53:32 kline: K&S section is over all org plan. Dimensions need some kind of training. 16:54:07 Fazio: Two solutions: label them out or say in each dimension that they’re provided. 16:54:33 q+ 16:54:59 Fazio: We need to update the document for each proof point. 16:55:06 Fazio: Who wants to update the document? 16:55:13 CharlesL1: Will do 16:55:40 CharlesL1: With the outcome, will I have to wait for the table? 16:55:52 ack stacey 16:55:54 ack stacey 16:56:01 stacey: Need to align documents 16:56:36 Fazio: Are we ready to update documents? 16:57:10 stacey: Need to do updates but can do Charles’ updates first 16:57:39 Fazio: You can do and Charles plug in or we can do it along the way. 16:57:57 stacey: I can add to the updates 16:58:16 CharlesL1: Need to nail down language 16:58:58 charles and stacey will present updated language next week 16:59:06 Fazio: Stacy and Charles will present updated language 16:59:16 Zakim, end meeting 16:59:17 As of this point the attendees have been Fazio_, CharlesL, Nichole_, stacey, Mark_Miller, janina, nadine, kline, nehaj, SusiPallero 16:59:19 RRSAgent, please draft minutes 16:59:20 I have made the request to generate https://www.w3.org/2024/01/31-maturity-minutes.html Zakim 16:59:28 I am happy to have been of service, Mark_Miller; please remember to excuse RRSAgent. Goodbye 16:59:28 Zakim has left #maturity