17:04:18 RRSAgent has joined #aria-editors 17:04:23 logging to https://www.w3.org/2023/12/11-aria-editors-irc 17:04:24 RRSAgent, make logs Public 17:04:25 Meeting: ARIA Editors 17:04:58 scribe: pkra 17:05:38 agenda+ [continue] automation and synonyms (via aria#2073) 17:05:38 agenda+ [continue] modernizing aria.js (aria-common#104) 17:05:38 agenda+ [continue] PR/Merge process - next steps after deep dive? 17:05:38 agenda+ [continue] roll out prettier setup - tracked via aria-common#99 17:05:39 agenda+ [continue] retiring contributors.md across specs - tracked via aria-common#103) 17:05:39 agenda+ [on Hold] spec markup for advice for AT (jnurthen) 17:05:55 zakim, next item 17:05:55 agendum 1 -- [continue] automation and synonyms (via aria#2073) -- taken up [from jamesn] 17:06:27 agenda+ what do we need to complete for 1.3 FPWD 17:10:32 pkra: this is mostly to talk about my aria.js refactoring. 17:11:20 ... which is progressing but very messy 17:13:22 ... lots of knowledge gained. 17:13:28 ... but still lots left to do 17:14:25 ... we could review changes so far and merge or do something else. 17:17:07 ... in other words: I could use some help 17:17:10 valerie: I could find time. 17:19:43 jamesn: me too 17:19:58 pkra: thanks. I'll work out when I want it. It's a bit of a mess to do. 17:22:43 pkra: and I won't forget about the actual item I mentioned - where we need new markup. 17:23:31 jnurthen: bikeshe would support markdown 17:23:46 daniel: respec supports it too 17:23:56 ... but probably not a good time. 17:24:19 zakim, next item 17:24:19 agendum 2 -- [continue] modernizing aria.js (aria-common#104) -- taken up [from jamesn] 17:24:30 zakim, close item 17:24:30 I don't understand 'close item', pkra 17:24:40 zakim, close this item 17:24:40 agendum 2 closed 17:24:41 I see 5 items remaining on the agenda; the next one is 17:24:41 3. [continue] PR/Merge process - next steps after deep dive? [from jamesn] 17:24:44 zakim, next item 17:24:44 agendum 3 -- [continue] PR/Merge process - next steps after deep dive? -- taken up [from jamesn] 17:25:01 pkra: did we follow up on that? 17:25:09 ... e.g., with jcraig 17:26:39 ... can somebody follow up on this? 17:28:46 jamesn: maybe he can read the emails :) 17:29:24 val: I will follow up. maybe summarize things on the issue. 17:29:30 zakim, next item 17:29:30 agendum 4 -- [continue] roll out prettier setup - tracked via aria-common#99 -- taken up [from jamesn] 17:29:39 zakim, close this item 17:29:39 agendum 4 closed 17:29:40 I see 3 items remaining on the agenda; the next one is 17:29:40 5. [continue] retiring contributors.md across specs - tracked via aria-common#103) [from jamesn] 17:29:48 zakim, next item 17:29:48 agendum 5 -- [continue] retiring contributors.md across specs - tracked via aria-common#103) -- taken up [from jamesn] 17:32:46 jamesn: we should leave it to specs to decide 17:32:58 ... there's a limit with github's API which might cause problems. 17:34:07 pkra: maybe I should go back and remove the old list from specs. Feels a fair call for ARIA WG to make 17:34:15 jamesn: for funders, should we keep this? 17:34:18 daniel: yes, for now it should. 17:34:25 ... maybe next year. 17:34:27 ... will check. 17:34:37 zakim, next item 17:34:37 agendum 6 -- [on Hold] spec markup for advice for AT (jnurthen) -- taken up [from jamesn] 17:34:44 zakim, close item 17:34:44 I don't understand 'close item', pkra 17:34:46 zakim, close this item 17:34:46 agendum 6 closed 17:34:47 I see 1 item remaining on the agenda: 17:34:47 7. what do we need to complete for 1.3 FPWD [from jamesn] 17:34:53 zakim, next item 17:34:53 agendum 7 -- what do we need to complete for 1.3 FPWD -- taken up [from jamesn] 17:35:03 jamesn: what do we need to do? 17:35:09 ... remove association list code. 17:35:17 ... as per WG decision 17:35:21 ... changelog 17:35:39 ... probably go for automated + manual editing afterwards 17:36:07 daniel: we'll find out more things when we push it through the publication process 17:36:20 jamesn: right. 17:36:52 pkra: other specs, too? accname? 17:37:01 jamesn: right, we'll need to do this for all specs. 17:37:16 bryan: the main accname thing would be inline/block label stuff. 17:37:22 ... that's holding up other work. 17:37:34 ... it's waiting for review. 17:37:39 jamesn: does it have to be for CR? 17:37:55 ... because once we are in CR, we're evergreen and we can make the changes quickly 17:38:02 bryan: that sounds good. 17:38:10 jamesn: we had a CfC already, I think. 17:38:17 bryan: not sure but think so 17:39:18 jamesn: we've had a CfC for core-aam and accname in Oct 2022 17:41:13 pkra: looking at core-aam, should it say somewhere that it's evergreen? 17:41:34 daniel: we don't use that term but it's in our charter 17:41:45 pkra: so it's always called "draft"? 17:41:49 jamesn: we can do snapshots. 17:42:15 jamesn: if we can publishing something for accname today that's better than right now, we should do it. 17:42:26 ... @daniel should we do another CfC? Is it too old? 17:42:40 daniel: yes. 17:42:49 jamesn: do we then need a wide review? 17:43:00 daniel: could list changes 17:43:22 jamesn: right. it's short. but wide review always finds issue. internationalization will likely find something. 17:43:31 ... so we need to do a new wide review? 17:43:35 daniel: yes 17:43:44 jamesn: can we clean things up fo that? 17:44:01 bryan: will talk to Melanie. Is it basically reviewing things and making sure nothing outstanding? 17:44:10 jamesn: just "better than last version" seems fine. 17:44:22 bryan: ok. 17:45:38 jamesn: I'll try to get the process running by January. 17:45:41 daniel: sounds good. 17:49:25 zakim, end meeting 17:49:25 As of this point the attendees have been (no one) 17:49:26 RRSAgent, please draft minutes v2 17:49:27 I have made the request to generate https://www.w3.org/2023/12/11-aria-editors-minutes.html Zakim 17:49:34 I am happy to have been of service, pkra; please remember to excuse RRSAgent. Goodbye 17:49:35 Zakim has left #aria-editors