Meeting minutes
aria-in-html and using-aria WDs aria#2694
Daniel: this has been lurking around for a while.
… we're redirecting this according to the original ask.
… but we want to change that.
… to match where the work is happening now.
… but this was before my time so I'm not sure why it's the way it is.
scotto: IIRC the original github was set up this way. Then Steve forked it to a separate thing. But somehow both were continued.
… so it stayed messy
Daniel: Right. So let's fix it.
… the old aria-in-html seems unmaintained.
… and the other one might be picked up.
jamesn: who will pick it up?
Daniel: It's not in our charter right now.
jamesn: do we want it?
Daniel: I suppose that's the question.
jamesn: if we take it on, then having this content in this document seems incongruent to other things.
Daniel: a requirement analysis might be useful. A lot of it might belong in Practices
jamesn: I agree. A lot of duplication.
Daniel: right. I'll check with Matt how he feels about some things moving to practices
jamesn: I'm not sure the strong opinions in there always fit well with ARIA. We know too much about nuances and exceptions.
Daniel: ok. I think I could do a bit of the moving.
… and follow up.
using resolutions more often
spectranaut_: this was a suggestion from Chris.
jamesn: could we use a label instead? It seems less efficient.
spectranaut_: I pointed out that many times issues need research. So a lot of resolutions can only happen later.
… but I find myself wondering what the status of particular issues is. Reading minutes etc. is time consuming.
… so I'm wondering if it's worth noting even just that we need more research.
jamesn: right. I'm not against it. I'm just not sure where it fits and where it doesn't.
Daniel: I also had this from others.
… it helps with transparency
… we'd need to decide which steps of our process would need resolutions.
spectranaut_: resolutions could be scraped from minutes, right?
Daniel: I think that would require some more work but we can look into it.
scotto: example from openUI openui/
… uses the CSS meeting bot.
spectranaut_: right. we talked about that bot.
… it would be nice
… would require linking the issues correctly.
scotto: right. This way, it's automatic and easy to find them again in the issues.
Daniel: the problem with the CSS bot is that they don't work with zakim, esp. agenda.
jamesn: right, I had filed an issue. Maybe we should just fix it.
scotto: I think open UI uses agendas and CSS Bot.
Daniel: they might use topics and not zakim?
scott: right. I'm not sure.
… but it is very nice and simplifies things.
jamesn: we should be able to find it from their full minutes
… they use github bot to move through things.
<spectranaut_> https://
spectranaut_: they use zakim, too. Just for queue though.
jamesn: I do like zakim's agenda features though.
spectranaut_: we'd have to set the topic, then github-bot takes it up?
jamesn: seems like you have to tell it.
… but you can do that anytime
spectranaut_: triage is a difficult though.
jamesn: but we shouldn't talk to much there anyway?
… perhaps we should try to do this except for triage issues
spectranaut_: we could do it manually.
jamesn: but it might create too much spam, e.g. when the relevant person isn't in the meeting
… I think it's worth trying though.
… or fix the agenda problem with CSS Bot.