Meeting minutes
scribe pkra
scribe, pkra
[new] aria-common #109 remove/replace aria-wg-active.md and
bryan: accname seems ready to go
daniel: yes, one odd plural language problem left.
<spectranaut_> w3c/
valerie: spawned by aria PR from new contributor.
… was this problem overlooked?
pkra: they're still used?
valerie: yes.
… in aria draft.
… let me look.
… yes, looks like it.
pkra: ok, so question is can we pull it from W3C data?
… contributions are via github
… but membership seems like it should come from W3C.
valerie: the list is so out of date though.
pkra: last commit to https://
… 5 years ago.
… daniel, is there automation for this?
<spectranaut_> this out of date list is in CR: https://
daniel: I don't think there's a way to do that.
valerie: we should update it then!
pkra: +1
Daniel: there are pages generated with participants lists.
… should be an API to grab that.
pkra: would be great to build that into spec production
valerie: this should be updated all the time, no?
pkra: +1
daniel: this should be doable.
pkra: assign to daniel.
[new] refs to HTML terms aria #1876
pkra: this is about https://
… a comment from jcraig.
… about HTML references not resolving.
… my question is: why aren't they resolving and how do we do automatically do it?
<spectranaut_> https://
pkra: I don't remember how to resolve it.
valerie: this link should be the official way?
… this is used in the spec, too.
… so it should work.
pkra: thanks!
… I'll comment
[continue] automation and synonyms (via aria #2073)
pkra: this really needs the aria.js rewrite.
[continue] modernizing aria.js (aria-common #104 & PR #106)
valerie: I haven't had time yet.
pkra: I'm happy with the code. roleInfo makes me unhappy. I feel it's not correct but I didn't feel comfortable changing it.
… roleInfo with 1.3 seems off. I tried to make sure that the PR doesn't change it.
… also some bugs from the jquery days.
valerie: I hope to have time soon.
pkra: maybe sit down together.
valerie: where is roleInfo used?
pkra: children specs, dpub aria, graphics aria, I think
valerie: do they run the same code?
pkra: no, that's separate and much the same but I haven't got to that.
valerie: I'll find time.
[continue] PR/Merge process - next steps after deep dive? (aria #2055)
pkra: news from deep dive?
valerie: jcraig is coming around to the idea of implementation before merge
… then there's a the link issue
… jcraig said he sees more benefit
… question is: do we agree this will help us out?
… jcraig still wants issues in different repos
… I feel like it will end up in aria repo
… even though repos are helpful for us editors
pkra: I feel like it could work. CSSWG has much more surface but single repo
valerie: what would the work be?
pkra: automation for EDs. Their github URLs come to mind
… but seems doable
valerie: how does it relate to evergreen? Do we need everything in evergreen?
pkra: also control.
… which ones we can control.
valerie: those outside our control need to stay in their own repos
… timeline
… maybe a F2F just working on this.
pkra: could be virtual, too.
valerie: I think a dedicated work effort would be good.
valerie: TPAC maybe
… in any case, let's make an issue to track a "work effort"