Meeting minutes
the recent prettier mess, w3c/aria#2568
daniel: I've tried to get to the bottom of this. It seems there's a difference between the new prettier setup and the old.
… running it on main shows a lot of difference. I'll dive deeper.
spectranaut_: so that's why all PRs are getting messed up?
Daniel: yes.
… I didn't understand the issue on scott's PR.
… the prettier seems ok.
spectranaut_: it's more that it now has 100 commits.
… I had something similar on a private repository
… closing and making a fresh PR helped there.
pkra: so it might be a github issue.
spectranaut_: right.
… so should we try a fresh PR for scott's?
Daniel: I tried to fix it.
pkra: it looked better.
spectranaut_: I'll take a look
Daniel: it's w3c/
spectranaut_: looks good at first sigh
Daniel: I merged main into it. didn't work for giacomo's.
pkra: did my comment on that other PR make sense?
… that the commit is separate from other changes, so PRs which didn't touch the area affected would not be affected.
spectranaut_: makes sense. But that leaves the first problem, right?
pkra: right.
spectranaut_: where does change come from?
pkra: I think 2 sources: running on main and new, custom action with pinned prettier version.
spectranaut_: ok, so we can remove running prettier on PRs, just have it on main.
daniel: I've made https://
pkra: but not add the local changes?
daniel: yes. Let's see how it runs afterwards.
spectranaut_: then we can remove the prettier commits from PRs.
pkra: should I merge?
… [all] yes!
… prettier run is clean.
daniel: makes sense.
pkra: I've updated w3c/
… does this look good?
jamesn: +1
spectranaut_: +1
pkra: looks like prettier does not have commits.
… which seems correct.
Daniel: I'll look at giacomo's.
spectranaut_: what were the steps you did?
pkra: I rebased on main and then removed the prettier commit.
… by git reset but revert should work as well in more complex settings.
continuing aria.js w3c/aria#2501
pkra: I actually wante to talk about pkra/
… it was a mess to get going.
… the script uses a light dom. It's hacky because of current aria.js . If we move to just having this path, then we could make it sane (import and run a function)
… the action works now. Could probably learn from the prettier action regarding commits.
… the diff is difficult because of different serializations.
jamesn: maybe do it by hand first?
pkra: ok.
… so I'll move this forward?
spectranaut_: +1
jamesn: +1
gaps in Taxonomy of WAI-ARIA States and Properties w3c/aria#1823
pkra: coming back to this, I found myself disagreeing with James. But also the taxonomy seems weird and outdated
jamesn: don't mind if you want to do something but it seems not important.
… but we should probably remove drag-and-drop
spectranaut_: I had never noticed this section either.
pkra: so maybe remove it.
replace practicesURLs with respec APG references w3c/aria#2552
pkra: just wanted to check if that'd be ok for the other editors.
Daniel: since APG is not respec'ed we'd have to use hardcoded links.
pkra: right. But it's just 15 so it feels like the right thing.
jamesn: makes sense.
daniel: sounds good.
align conformance sections across specs, w3c/aria#2554
pkra: daniel did you want to take this?
Daniel: yes. Just not sure when I'll get to it.
zakime, close this item
different time for meeting
different time for meeting
jamesn: I could do something else on Wednesday.
daniel: I'm flexible on wednesday
pkra: me too.
jamesn: maybe do a survey
pkra: which survey system should we use?
daniel: w3c wbs is good.
… but we're not a task force anymore.
… then maybe just google forms.
… ah, correction. We could use wbs.
pkra: can I do this?
daniel: yes.
<Daniel> WBS
status of biblio.js & html-aam/biblio.js w3c/aria#2547
zkaim, end meeting