W3C

WAI Coordination

24 Apr 2023

Agenda

Attendees

Present
MichaelC, janina, kevin, jeanne, GeorgeK, Rachael, Lionel_Wolberger, Matt_King, shawn, jamesn, maryjom, matatk, Lionel_Wolberger_, Daniel, spectranaut_, Lionel
Regrets
matatk, tzviya, kim
Chair
MichaelC
Scribe
MichaelC

Contents


<agendabot> clear agenda

<janina> scribe+

<scribe> agenda: https://lists.w3.org/Archives/Public/public-wai-cc/2023Apr/0009.html

<agendabot> clear agenda

Infoshare and coordination checks

<janina> GeorgeK: Notes AB nominations are underway. Dpub has nominated Avneesh

Member link: https://lists.w3.org/Archives/Member/w3c-ac-members/2023AprJun/0000.html

Automatic transcripts update https://github.com/w3c/Guide/issues/170

<janina> MichaelC: Desire coalescing to liberize policies on use of transcripts; requires a PR to update policies

<janina> MichaelC: Anyone interested in creating the PR?

<janina> James: Currently we can't even copy and paste from them

Zoom language translation

<janina> MichaelC: We've begin migrating from MIT Zoom to our new Zoom account(s)

<janina> james: Is live?

<janina> michael: believe so

<janina> MichaelC: Suggests at least investigating W3C Zoom

Coordination project prioritization

<janina> MichaelC: Returning to traditional concerns of the CC calls ...

<janina> MichaelC: How to best cooperate across WAI groups

<janina> MichaelC: e.g. Community Group monitoring

scribe+

janina: CG tracking of interest

in work with the a11yedge CG, have been discovering activity in other CGs that we didn´t know about

the previous APA strategy to track was not surfacing that

there may be a CG subculture in existence

<janina> janina: Notes we've found subcultures of accessibility conversations in CG groups because of A11yEdge CG we were otherwise unaware of

<janina> MichaelC: So how to connect?

<janina> george: Know that ChemML is publishing; also several publishing TFs; but unclear how to track CGs

janina: unclear how output from a CG proceeds

<janina> janina; asks about elevating CG work into standard W3C pub mechanisms

<janina> MichaelC: Does the CC wish to discuss CG tracking?

<janina> Lionel: When CG interfaces with any of W3C at all is an open q with m; TPAC?

<janina> Lionel: Just in general, is anyone in W3C minding the CG store?

<janina> MichaelC: There's been a rather deliberate policy to allow CG to just be

<janina> MichaelC: Other thoughts?

straw poll: -1 = don´t do, 0 = can do, +1 = must do

<janina> +1

Cross-WAI review procedures

<janina> +1 we should know what to expect of each other

scribe-

<jeanne> +1

+1

<jamesn> +1

<Lionel> +1

<maryjom> +1

Community Group monitoring

<jamesn> 0

0

<Lionel> 0

<spectranaut_> 0

<jeanne> 0

<janina> +1 but also a bit more in available elevation

<shawn> +1

<maryjom> 0

<george> +1

<kevin> +1

Glossary harmonization

<jamesn> -1

0

<jeanne> +1

<janina> +1 -- we need to be consistent for brand value

<Lionel> 0

<kevin> 0

Tool accessibility

<jamesn> +1

+1

<maryjom> +1

<shawn> +1

<kevin> 0

<janina> +1 but mostly OK

<spectranaut_> +1

<jeanne> 0

<george> +1

Project incubation and coordination

<shawn> ?

<jeanne> 0

<janina> +0 time is limited -- when it's brought to CC needs to be clear

0

<jamesn> 0

<kevin> 0

<maryjom> 0

In-depth project updates

<Lionel> +1

<janina> +0 useful, but with only 30 minutes?

<jamesn> 0

<jeanne> 0

+1

<shawn> -1 for indepth; +1 for more than infoshare

<kevin> 0

Industry knowledge tracking

<maryjom> 0

<shawn> +1

<janina> +1 but perhaps mostly because this matters to APA

0

<jamesn> 0

<kevin> +1

<jeanne> 0

Skill training

<jeanne> 0

<janina> +1 we need to get good at it -- train the trainer

<maryjom> +1

<Lionel> 0

+1

<kevin> 0

<jamesn> 0

<janina> george: would be useful to have a place to go for help with tooling -- e.g. github

Participation support, e.g., tech support

<janina> +1

<kevin> +1

<jeanne> +1

<maryjom> +1

0

<Rachael> +1

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.200 (CVS log)
$Date: 2023/04/24 16:00:07 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision VERSION of 2020-12-31
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Found embedded ScribeOptions:  -final

*** RESTARTING DUE TO EMBEDDED OPTIONS ***

Default Present: MichaelC, janina, kevin, jeanne, GeorgeK, Rachael, Lionel_Wolberger, Matt_King, shawn, jamesn, maryjom, matatk, Lionel_Wolberger_, Daniel, spectranaut_, Lionel
Present: MichaelC, janina, kevin, jeanne, GeorgeK, Rachael, Lionel_Wolberger, Matt_King, shawn, jamesn, maryjom, matatk, Lionel_Wolberger_, Daniel, spectranaut_, Lionel
Regrets: matatk, tzviya, kim
No ScribeNick specified.  Guessing ScribeNick: MichaelC
Inferring Scribes: MichaelC
Agenda: https://lists.w3.org/Archives/Public/public-wai-cc/2023Apr/0006.html

WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)


[End of scribe.perl diagnostic output]