Meeting minutes
Improving coordination
RM: We discussed on email. We discussed
Dashboard
LS: A tool that we could use to communicate?
<LisaSeemanKest> https://
LS: it might be useful to mention that we couldn't wait and put a page together
… it does what we need, but it probably needs components
… instead of "team" you could say "people who need to review" and it could ping them.
… we haven't been great at it, so we created this table.
RM: if we did a wiki should it be one or one for each group?
LS: Let's try one so we have one place to look
CA: I would lean toward one
Wilco: ok
Chris: ok
Action: Michael, find a wiki page where we all facilitators have editor's right
<trackbot> Error finding 'Michael,'. You can review and register nicknames at <https://
RM: We would need edit rights
Action: shawn, set up a wiki page where we all have editors rights
<trackbot> Error finding 'shawn,'. You can review and register nicknames at <https://
SLH: W3C wiki will work. I will take that off Michael's plate
<Rachael> https://
RM: Is this the format we want, does it have the columns we need?
CL: The LVTF set up a GH project. We have review and approved column
<Zakim> jeanne, you wanted to say we need an originator column
RM: We need a column to link to the feedback
<Rachael> jeanne: we need an originator column
SLH: I have a hard time using a wiki table markup
JS: I find an HTML table markup is more universal
RM: We could do it in Github if we find that the wiki is harder to manage
SLH: The Github project feature is useful but difficult for some
RMB: Are there any comments
KP: What's it for?
RMB: We are using it to track inter-group comments and actions. It looks like a lot of people will use read it, but not a lot will edit.
LS: We can search by status
<Chuck> +1
<ChrisLoiselle> +1
RMB: Let's try until July
+1
We also need to give verbal requests in meetings
Resolution: Try the wiki out until July and then revisit.
<Wilco> +1
<Rachael> Jeanne: Need to still keep making verbal requests in meetings.
KP: An email with a consistent subject line
MC: I can put a timed reminder in my to do list.
CL: Add it to the agenda for this meeting as a regular item
Action: Rachael to add topic to agenda
<trackbot> Created ACTION-351 - Add topic to agenda [on Rachael Bradley Montgomery - due 2021-05-12].
RMB: I will make it a standing topic
Liaisons
RMB: We had a discussion on the list of how we support and train liaison
… both group facilitators agree on the person
… we had a list of characteristics we talked about
<Chuck> jeanne: Can we review the list of characteristics?
<Rachael> regularly attending meetings for both groups, being aware of topics that touch both groups, working with chairs/facilitators
+1
LS: They are good at passing on the information
… they are not the representative, they are passing on the information and passing it back as well.
… no guidance so far on how to use the liaison
… for example, I got a request for liaison, and got the people. Should the liaison maintain the table.
MC: The facilitators should reach out with "this is what we need", then the liaison reports on the meeting discussions
<Zakim> shawn, you wanted to explain that situation
MC: the facilitator would email and cc the liaison and the liaison will take it from there
SLH: It was the unnecessary extra work of going through the liaison to talk to other groups. Its unnecessary 3rd party involvement.
SLH: Don't require the liaison to take it over from the project manager. We copy the liaison.
MC: The liaison should take an elevated level of responsibility
<Zakim> Chuck, you wanted to suggest how we approach the liaison roll
SL: I ask the liaison to give more guidance to the meeting
CA: I think we should not be overly prescriptive so that groups can use the liaison the way that works for them
<shawn> +1 to Chuck for guidance, yet not overprescriptve
RMB: We also had discussion of how to document it.
… one person expressed a concern about the accessibility of google docs
KP: We need to know what the issues are with each of the accessibility of the different tools. Ikt's important to be aware.
… so we know over-arching issues and where things clash
<LisaSeemanKest> can we add to the agenda, working with workspaces and divercity groups
RMB: We need a place to document it all
JS: We need to coordinate by email and one person put it in one place
<LisaSeemanKest> janina hates googledocs
KP: Google spreadsheet
LS: Some people struggle with spreadsheets
<jeanne> s/ janina hates googledocs/ some people can't use googledocs
Action: Rachael, document issues with Google Docs, Github, Wiki, email, Google spreadsheets
<trackbot> Error finding 'Rachael,'. You can review and register nicknames at <https://
RMB: So I will ask about the following tools
Rachael: Anything else on liaison roles ?
Resources needed to Coordinate
Rachael: On improving coordination , what other resources do we need ?
Lisa: Is it worth coordinating with Diversity and Workplace ? It touches on accommodations and overall process.
Michael: Let us work through it in WAI and we can take it to them as a proposal.
Rachael: On facilitation , who would we want to take lead on that?
Lisa: I can and have someone work on it with me.
Michael: I will contribute in one way or another.
Kim: I can also help.
Lisa: Perhaps Jennie from COGA as well.
Action: Lisa, Michael, Jennie maybe and Kim to meet and discuss way forward on coordinating across groups
<trackbot> Error finding 'Lisa,'. You can review and register nicknames at <https://
Rachael: You can plan on meeting over next month and report back with what you've discussed.
<shawn> Here is start of page for WAI Group Coordination https://
Michael: I'll schedule a meeting on the administration side .
Shawn: Shares Coordination group page , https://
Shawn: Feel free to change columns, order , etc.
AG status update
Rachael: We had joint meeting with Silver. We are continuing joint meetings as well.
… Any questions from task forces?
Wilco: What are the plans on integrating Silver and AG?
Rachael: We will continue joint meetings and continue to explore. We want to continue to address 2.2 issues as well.
task force updates
Kim: How long are the joint meetings to go on ?
Rachael: Next two weeks are planned.
Chuck: Data exercise , fluid during and planning thereafter .
Lisa: Joint meetings discussion ? What do you mean?
Rachael: Silver work will merge at some point with AG , the discussion of how these groups work together is discussed in AGWG call.
Rachael: The support of groups and work to be done is the goal of meetings.
Lisa: Silver team will possibly inherit AGWG issues and vice versa. We could lose some things on both groups.
Rachael: The AG has the testing expertise needed , to bring out best of both groups.
Lisa: Task forces are strength within a bigger working group.
Chuck: We value Silver but also need to merge to combine strengths of both groups.
Wilco: I think the need to move bulk of work to AG gets more people involved. I think that is essential for consensus on WCAG 3.
Kim: What do we need to consider moving forward for task forces ?
Rachael: AG is to shift focus on WCAG 3. Potential sub group for WCAG 2.3 . If something in task force fits 2.3 , please volunteer in the AG subgroup for 2.3. Otherwise, coordinate for WCAG 3. and gap analysis etc.
Lisa: On COGA, we published ! Thank you !
… content usable is now a note. We are working on next round of research. We are starting to look at mental health.
Wilco: ACT we are reorganizing group. We are going through rules presented by community group and looking to which could be proposed rules.
… looking to phasing out community website and going through one website and consolidating content.
… Silver conversation , two three hour meetings , deep dive on WCAG 3 structure and where ACT can provide lessons learned
… second meeting what can we integrate into methods within Silver
<Rachael> Chris: We are doing well. Created github project...
<Rachael> consolidating what we need to do and where we are going. Drafted a participation email and Shawn has vetted. That is our next item to send that out.
<Rachael> ...other than that, reading the documents for review that our group will be working on.
<Zakim> shawn, you wanted to note WG and TF update
Shawn: Waiting on Michael to update task force page, so we can announce call for participation. Related: project to make updating WG and TF pages more easily by Chairs and Facilitators - will discuss in WAI CC today
<shawn> in-progress info abotu that: https://
Kim: Mobile task force. We have done a user needs and done a first step of taking WCAG 2.1 to Silver. Waiting on materials to be ready to shift things over. We are starting to shift over. Waiting for guidance.
<shawn> WCAG2ICT
WCAG to ICT discussion is in process.
new business and action review
Rachael: 11am time frame for a general chat on Thursday (date to be determined) ?
<Chuck> +1 ok
<Chuck> any movie fan has 50 movies in their top 10 list :-)
Kim: On topic for chat, technology pet peeve?
<Chuck> no objections on my end
Rachael: Any objection on extending invitation ?
<shawn> [ Sound of Metal - movie recommendation ]
no objections here.
Rachael: Cross groups would be informal and easy going.
<Zakim> ChrisLoiselle, you wanted to comment on date of this meeting?
<Rachael> May 27th 11 am