15:11:40 <RRSAgent> RRSAgent has joined #coga
15:11:45 <RRSAgent> logging to https://www.w3.org/2026/01/26-coga-irc
15:11:52 <Zakim> RRSAgent, make logs Public
15:11:53 <Zakim> Meeting: Cognitive and Learning Disabilities Accessibility Task Force Teleconference
15:11:53 <Lisa> q?
15:12:25 <Lisa> scribe+ Eric
15:43:37 <Lisa> Lisa has joined #coga
15:43:46 <Lisa> agenda?
15:43:57 <Lisa> zakim, start meeting
15:43:57 <Zakim> RRSAgent, make logs Public
15:43:59 <Zakim> Meeting: Cognitive and Learning Disabilities Accessibility Task Force Teleconference
15:44:08 <Lisa> scribe+ Eric
15:44:33 <Lisa> Regrets+ Jan, Jennie D, Abigail, Gareth
15:44:57 <Lisa> RRSAgent, publish minutes
15:44:58 <RRSAgent> I have made the request to generate https://www.w3.org/2026/01/26-coga-minutes.html Lisa
15:46:20 <Lisa> licenses: AGA uses  https://www.w3.org/copyright/document-license-2023/     and APA uses  https://www.w3.org/copyright/software-license-2023/
15:46:36 <Lisa> Q?
15:53:25 <Lisa> Q?
15:58:26 <Lisa> Q?
15:58:45 <Eric_hind> Eric_hind has joined #coga
15:58:51 <Eric_hind> present+
15:59:34 <Lisa> hello
15:59:51 <Lisa> scribe+ Eric_hind
16:00:36 <Jennifer> Jennifer has joined #coga
16:01:28 <julierawe> julierawe has joined #coga
16:01:31 <julierawe> present+
16:01:52 <Jennifer> present+
16:02:31 <Lisa> present+
16:02:46 <Lisa> next item
16:02:46 <LenB> LenB has joined #coga
16:02:51 <LenB> present+
16:03:41 <Lisa> Licences. See https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2026Jan/0017.html
16:03:59 <Lisa> licenses: AGA uses  https://www.w3.org/copyright/document-license-2023/     and APA uses  https://www.w3.org/copyright/software-license-2023/
16:04:06 <janina> janina has joined #coga
16:04:41 <Becca_Monteleone> Becca_Monteleone has joined #coga
16:04:48 <Becca_Monteleone> present+
16:05:09 <Eric_hind> Lisa: Review of what the difference in licenses, both are under w3c.  AG uses w3c for documents, APA uses w3c for software and documents.
16:05:16 <Lisa> Licences. See https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2026Jan/0017.html
16:05:54 <julierawe> q+
16:06:02 <janina> q+
16:06:19 <Eric_hind> Lisa: Want to have a review and get consensus today.
16:07:04 <Eric_hind> Julierawe: Does picking one over the other change anything else for COGA?
16:08:58 <tiffanyburtin> tiffanyburtin has joined #coga
16:09:07 <tiffanyburtin> Present+
16:09:37 <Lisa> proposal is in See https://lists.w3.org/Archives/Public/public-cognitive-a11y-tf/2026Jan/0017.html
16:10:00 <Lisa> ack next
16:10:03 <Eric_hind> Lisa: Either group may pick up our work as a supplement, guidance, etc.   Guideance under AG, but main publishing under APA
16:10:08 <Lisa> ack next
16:11:33 <Lisa> janina: 2008 to 2010, there was a lot of review and migration to softwear and documents
16:11:40 <Lisa> ag may migrate as well
16:11:58 <Eric_hind> Janina: Historically, around 10-15 years ago, there was more discussion around licensing (near HTML5).   AG has stayed with the existing documentation licence but may update to the same one APA is using.
16:12:18 <Lisa> q+
16:13:05 <Eric_hind> Janina: As of now, COGA does have to pick one over the over.  But there is potential for AG to update to the same licence as APA
16:14:30 <Eric_hind> Eric_Hind: Correction, the research publication is published under APA, not Guidance (from Lisa comment)
16:14:44 <Lisa> but we can publish Guideance under AG, but reserch (this work) under APA
16:16:15 <Eric_hind> Janina: If we publish under APA, thats fine, if we want to publish also under AG, we have to work through the same processes.
16:19:45 <Eric_hind> Lisa: Should we then go forward with APA?
16:19:48 <Lisa> ack next
16:19:48 <Eric_hind> q+
16:19:55 <Lisa> ack next
16:20:01 <LenB> scribe+
16:20:02 <julierawe> q+
16:21:24 <Eric_hind> Eric_hind: Will AG going to the same license as APA be seamless?
16:21:51 <LenB> janina this will likely need to be a new item in the AG charter process. Once the AG group agrees on charter, then management reviews / approves, then it goes it W3C members - and this process will usually bring up some edits. We're talking 2 to 3 months before it is final
16:22:17 <Lisa> ack next
16:22:23 <LenB> janina we're talking 4 to 5 months before we can use it to publish.
16:22:24 <Eric_hind> Janina: Estimated 4-5 months in total
16:23:04 <Eric_hind> Julierawe: Charter discussion for AG will potentially take even longer than that (from working group discussions)
16:23:11 <Lisa> Proposal  we can publish Guideance under AG, but reserch (this work) under APA. (we will ask kevin and shawn if that is ok). assuming there is still an issue for guidence
16:23:51 <kirkwood> present+
16:24:00 <janina> present+
16:24:56 <julierawe> +1
16:25:00 <Eric_hind> +1
16:25:01 <Becca_Monteleone> +1
16:25:02 <LenB> +1
16:25:04 <Jennifer> +1
16:25:07 <kirkwood> +1
16:25:11 <Lisa> +1 agree, -1 disagee. , 0 not a big deal
16:25:21 <tiffanyburtin> +1
16:25:47 <Lisa> +1
16:25:50 <Eric_hind> Lisa: We have consensus.
16:26:21 <Eric_hind> Lisa: Next steps, write to Kevin and Shawn about going forward with what we want to do.
16:26:58 <Lisa> next item
16:27:21 <Lisa> agenda?
16:29:19 <Lisa> https://docs.google.com/document/d/15HtPkkYx1CIl6bAwP2nsSZKhqTVbqcuMDRz5RmtmvXg/edit?tab=t.p64c5smxfdrc
16:29:23 <Eric_hind> Lisa: review, Thursday weekly calls for Editors or research (9AM EST), then Guidance group (11AM EST)
16:31:20 <Eric_hind> Lisa: We don't currently do reminders/updates on an email basis for these meetings (join info is posted on COGA site).  Are there people who would like to come to these meeting?  Would they like an email reminder?
16:32:23 <julierawe> q+
16:32:33 <Lisa> ack next
16:33:50 <Eric_hind> Lisa: Research call is often done as topic reviews are needed, etc.
16:34:10 <julierawe> julierawe: For the COGA Guidance Subgroup meetings, I do try to send email reminders with agendas, pre-reads, etc.
16:34:15 <tiffanyburtin> I don't mind the emails or calendar invites. It allows me to plan and attempt to attend things I can.
16:34:47 <Eric_hind> Lisa: Are the notifications (W3C Calendar) bothersome if you don't usually attend?
16:34:48 <Jennifer> I can't attend the research group because of my time zone, but it's fine to keep it on my calendar
16:35:36 <julierawe> q+
16:35:43 <Lisa> ack next
16:36:17 <Eric_hind> Lisa: Based on comments, having the Calendar seems OK with all.
16:36:59 <Eric_hind> julierawe: Guidance group encourages asynch communications, maybe this is an alternative for the Research group.
16:38:20 <Eric_hind> Lisa: Would folks like to be alerted when there's potential asynch work for Research group? (Emails)
16:39:19 <Lisa> agenda?
16:39:28 <Eric_hind> Lisa: Folks don't seem to be bothered if we update them on potential asynch work.
16:39:31 <Lisa> next item
16:40:14 <Eric_hind> Lisa: For now, we'll keep doing what we're doing - if people want reminders we can do more.
16:41:47 <Eric_hind> Lisa:  We are about to publish the research modules and getting feedback (we have some already).  Most issues will come via github issues (and most like from w3c members).
16:43:01 <Eric_hind> Lisa: We want to consolidate this into one place like into the COGA repository - research group would generally prefer to avoid rework when going back and forth from docs to github.
16:43:37 <Lisa> next item
16:43:57 <Eric_hind> Lisa: Question, will keeping things in research feedback in github, make things difficult for others to participate
16:45:48 <Eric_hind> kirkwood: google docs makes response and findability somewhat easier.. but no real opinion towards github or not.
16:46:23 <Eric_hind> tiffanyburtin: Docs let us rough draft/discuss, but github is more public and not as much a safe space.
16:46:25 <julierawe> q+
16:46:43 <LenB> q+
16:47:00 <Eric_hind> Jennifer: Agree that docs are easier, more friendly, less public as a pro towards docs
16:47:06 <Lisa> ack next
16:48:22 <Eric_hind> Julierawe: Maybe internal comments for our group belong in docs for internal tracking.
16:50:55 <Eric_hind> Lisa: What we're discussing will require interacting with github - some will be editorial, some discussion.  This will be mostly with research group.  In the past, we have transcribed github to a google doc, but we then have to keep two streams of discussion going (github and doc).  With the potential to miss one stream or the other.
16:52:23 <Eric_hind> q+
16:52:28 <Lisa> ack next
16:53:24 <janina> q+
16:53:43 <Lisa> ack next
16:54:10 <kirkwood> +1 eric do that ;)
16:54:15 <LenB> Eric_hind if there is someway to automatically pull in comments from GitHub into google. I'd volunteer for that.
16:54:24 <Lisa> ack next
16:54:40 <LenB> Eric_hind it has to be one person to do it.
16:55:59 <Lisa> GitHub REST API documentation: https://docs.github.com/en/rest?apiVersion=2022-11-28
16:56:16 <Eric_hind> Janina: There's groups available that we could chat with about doing some kind of github to docs automation.
16:56:51 <Lisa> google doc / spread sheet ?
16:57:01 <tiffanyburtin> tiffanyburtin has joined #coga
16:57:04 <Lisa> +1
16:57:07 <kirkwood> +1
16:57:08 <Eric_hind> +1
16:57:12 <Jennifer> +1
16:57:12 <LenB> +1
16:57:13 <Becca_Monteleone> +1
16:57:20 <Lisa> inplace of github
16:57:24 <tiffanyburtin> +1
16:57:55 <Eric_hind> Lisa: No objections to google docs/sheet for research subgroup
16:58:09 <kirkwood> present+
16:58:32 <Lisa> RRSAgent, publish minutes
16:58:33 <RRSAgent> I have made the request to generate https://www.w3.org/2026/01/26-coga-minutes.html Lisa
17:00:11 <janina> Yes`! Are you briefly free now?
17:00:22 <janina> OK!
17:01:01 <janina> I have to head out for around 90 minutes at some point this afternoon, otherwise free
17:04:33 <LenB> LenB has left #coga