W3C

– DRAFT –
Maturity Model

09 Nov 2022

Attendees

Present
CharlesL, Fazio, Fazio_, Fazio__, JakeAbma, janina, jlkline, kline, Lionel_Wolberger, Lionel_Wolberger_, maryjom, nadine, present, sheri_b-h
Regrets
-
Chair
Fazio
Scribe
nadine

Meeting minutes

group github issues

issue 146: Each sheet shoudl track each dept answered

<Fazio> Maturity Git: https://github.com/w3c/maturity-model

janina: organizations want to do that by department, do we need a field for organization unit?

jlkline: date it was done, who did it

janina: new issue for tracking mechanisms we need (legal entity departments or sub units) if user want to break it down to departments

jlkline: I will open a new issue

janina: we close this issue

bpoday_: there is so much variance in organizations and departments and business units, they can overlap

jlkline: the model is intended to measure the entire organization. For each dimension there should be one answer for each organization, because they are so different

jlkline: organizations should do it on their own

janina: we should help them to build a tree and to track, who is responsible

janina: we should give them the flexibility

bpoday_: each business unit could have an other maturity for the dimensions

jlkline: keep it simple, maybe just have a text in the beginning

bpoday_: maybe best practices for very big organizations?

Fazio: thats why we want organizations to test it

janina: we try to show where there are gaps with the maturity model, but if there is no responsible person for accessibility, than you need the maturity model

Fazio: if we can implement something for tracking that would be good

jlkline: adding some fields for tracking would be good

janina: we close this issue and Jeff will open a new issue for it and refer to it

<Fazio> Issue 146 closed with comment: We will open a new issue about capturing meta data that encompasses this issue. Thank you

<trackbot> Sorry, but no Tracker is associated with this channel.

Issue 147 Name of the Administrator of the Model

janina: more input for meta data tracking

Fazio: same as issue 146

Fazio: open new issue and close this one

<Fazio> Issue closed with comment: Similar to issue 146 about meta data. We will open a new issue to address 146, and 147

<trackbot> Sorry, but no Tracker is associated with this channel.

issue 145 Linking would make it easier to use

Issue 143 communities of practice. Question, communities we serve

Fazio: what is the context of the issue?

Fazio: revisit it for more context

<Fazio> Iss 143 editorial We need more context. Will revisit when Charles is present to elaborate

Issue 145 Linking would make it easier to use

nadine: Charles just copied our minutes

Fazio: we need more context

janina: we should continue with issues not from Charles and handle his issues, when he is here

<Fazio> New Rule issues from group members that file issues will be addressed only when those members are present

jake: should we first comment on github or talk about it directly?

janina: first on github is better and than we can go through it faster

Fazio: I look at the issues which ones are fast

Fazio: and send a short agenda

janina: Jake can we organize your issues before the meeting?

jake: can we label issues?

Fazio: yes, I can do it

Minutes manually created (not a transcript), formatted by scribe.perl version 196 (Thu Oct 27 17:06:44 2022 UTC).

Diagnostics

Maybe present: bpoday_, jake

All speakers: bpoday_, Fazio, jake, janina, jlkline, nadine

Active on IRC: Fazio, janina, jlkline, nadine