W3C

ARIA Editors

17 February 2021

Attendees

Present
JamesN, Jemma, Joanmarie_Diggs, Matt, MichaelC
Regrets
-
Chair
MichaelC
Scribe
MichaelC

Meeting minutes

ARIA 1.2 check in

Approved to transition to CR

plan to publish 23 Feb

ARIA 1.3 check in

1.3 FPWD pending

need to move stuff to stable branch now that 1.2 is clearing the queue

not planning 1.3 Practices

will go to ongoing maintenance of APG

just publish as updated Note (w/o version) as needed, until we have a non-TR version going

still need to track the ARIA features that need Practices guidance

<Jemma> I like the idea of having ARIA-APG to hold aria 1.3 till APG has new place.

need to figure out how to flag ARIA version to which Practices guidance applies

<Jemma> s/having repo/having ARIA-APG/

one of the early goals for the non-TR version

also want a filter for content that´s just draft

these questions will apply to ARIA if it goes to evergreen as well

getting browser testing of ARIA into wpt would allow generation of support tables in the spec

let´s move some of this discussion to requirements for evergreen ARIA and APG

Maintainer for Practices repo

MCK desire for role in APG that is not editor but has merge access

can do operational things to maintain the build process

might merge issues that don´t affect presentation etc.

easiest path is to add them to aria-practices team which has the needed permissions

document the role so the person focuses on it

give MCK and Jemma maintainer role in the aria-practices team

and give aria-practices team maintainer role in aria-practices repo

maybe later set up a team with admin access, if needed

<Jemma> https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#:~:text=Maintain:%20Recommended%20for%20project%20managers%20who%20need%20to,actions%20like%20managing%20security%20or%20deleting%20a%20repository

APG transition repo

May, or may not, need a repo to do scripts for migration

may be able to do stuff in branch

can create repo if needed

respec-w3c profile

Respec warning to migrate from Respec Common to Respec W3C

in URI of script that loads respec, just drop the ¨-common¨ from the URI

leaving ¨respec-w3c¨

GitHub discussions

https://docs.github.com/en/discussions

playing with it in Accname repo to see what we think

something to consider, if we like it

JamesN: ¨StackOverflow in GitHub¨

<joanie> https://github.com/w3c/accname/discussions

renamed branch in the ARIA repos except APG

should do this month

should be feasible

Main branch renaming

(prev 4 lines)

Host access to Zoom

have to get a MIT account, then be delegated as an alternate host

has to be done for each call

send MC email if you need the access

Next meeting

<MichaelC> Next meeting: 3 March 2021

Minutes manually created (not a transcript), formatted by scribe.perl version 127 (Wed Dec 30 17:39:58 2020 UTC).

Diagnostics

Succeeded: s/having repo/having ARIA-APG

Failed: s/having repo/having ARIA-APG/

Found 'Next meeting:' not followed by a URL: '3 March 2021'.