<scribe> scribe: Chuck

jn: Is this meeting time the best time?

judy: We can discuss and review.

Scribe, rrsagent, agenda, confirming next meeting

judy: Next meeting is week after US Thanksgiving. Dec 2.

<Judy> NEXT MEETING IS DECEMBER 2

judy: let us know if there are conflicts.
... Any additional agenda items?

Input on TPAC intersection with your groups' workflow?

judy: This item is specific to discussions that followed TPAC. Sense from some w3c management, concern that not all groups cancelled their wg meeting.
... I pointed out that there are demanding workflows, and can't suspend work for multiple weeks.
... There's a move to make it a clearer expectation or requirement to encourage participation.
... If that happens people need to hear months in advance, and work schedules could be forgiven.
... This is an opportunity on intersection of a prolonged TPAC virtual meeting.

janina: Most of meetings that APA scheduled were in first week, with less overlap, but still some.
... That was a challenge, due to various competing responsibilities.
... There were excellent breakouts. I did stomp on some APA scheduled meetings.
... I think a lot of TPAC, it's largest value is the cross group opportunities.

judy: Any comment from James?

james: TPAC didn't get in the way of TPAC, it was very early in the morning and didn't conflict.

judy: It extended your day earlier, but you didn't need to cancel?

james: We didn't need to cancel. There is one meeting we cancelled, due to other conflicts.

judy: ...it was thought by some that it would be better to send a message out to team to cancel team internal meetings.
... Maybe send an "absence" (metaphorically) note.

james: We can deal with our own management.

Josh: Nothing to add. Mostly fine. Core part of my job.

Chuck: Our team had large workload, and I need to think about future options. Happy to hear that workload might be allowed to slip.

Judy: TPAC serves many purposes in many different ways. There was a wg meeting week, posting for others to sit in, even though not explicitly joint meetings.
... I got to attend some, and appreciated my opportunities.

Announcements: https://www.w3.org/WAI/cc/wiki/WAI_Announcement_Drafts

judy: I sent a link to announcements draft. James you have ARIA 1.2... When's your annoucement?

james: When everything is done. We have some horizontal review that needs to happen.

judy: 2 week deadline.

james: Just 2 weeks?

judy: Yes. Michael may need a reminder.
... Once the horizontal review request has been filed.

james: I did internationalization and security, I filed in github and sent email. Michael did accessibility one.

judy: Is accessibility pending?

janina: Shouldn't be.

james: Michael sent out this week. Got sent less than a week ago.

judy: Can you help out James?

janina: We passed on it several weeks ago. Are we logging in the right place? We are moving to new dashboard.

judy: I think you are in good shape.
... I'll follow up with Michael.
... Discussion on timing for WCAG 3.0 fpwd release.
... I gave some feedback, and then with Shawn had different feedback.
... Chairs and staff need a break, don't want suprises, might be good to wait until after holidays.

josh: We are now, in RQTF, decided to publish RTC accessibility requirements as working group note. Doc is good to go.
... I need to draft announcement. Shawn is out this week. I'll put together something. Will take cycles with Janina and Shawn.

janina: Reported out of RQTF asking APA to publish. Means CFC in APA.
... CFC nov 30th...

<joconnor> Here is the publication branch

janina: You have that long...

<joconnor> https://raw.githack.com/w3c/apa/2020-nov-raur-publication/raur/index.html

janina: COULD publish in December.

Reminder to reread CEPC

judy: Reminder to reread CEPC. I'll mention quarterly. Take a glance, mention to our groups in next month or so.
... 2 trainings, one was pilot, one during TPAC. We will try to have a recorded. Stay tuned for another live session.

Your groups' priorities for 2021? Other round-table items?

judy: What are your groups priorities for 2021? I can bring up next time we meet. Might be helpful for other groups to hear about.

james: We need to get back on timelines. 1.2 is late, 1.3 aims to be out of the door at beginning of year. We have content ready to go.
... We don't want to delay 1.3 a year after release of 1.2.

judy: a followup: Could you let myself and colleagues know what's in it?

james: Annotations and braille.

judy: Anything you want to share, or rather share with more colleagues?

josh: Priorities... last year myself that funds my role in W3C. What are the priority areas for me? Brought up certain things.
... mini-apps we could look at in new year.
... I'll be producing one more user requirements doc.

Judy: Let's have conversation on priorities team-side.
... I've a few ideas with a role for you to play.

janina: Josh, leave some time for seeking funding.
... We desire prolonged "josh".
... From APA perspective, we've got some late specs (on due dates). Too narrow a scope in personalization.
... Looking for a way to find out if one of the youngsters in APA want to take a greater role.
... And getting at least one spec out would be good. Pronunciation would be good to get out.
... Going to be engaged in planning for voice interaction workshop that peers are planning for us.
... APA is rechartering, would like to get done in timely fashion. Need to get done soon.
... There's some exciting pieces coming out of RQTF.
... We discussed in joint meeting during TPAC to come up with strongly researched evidence on Synchronization.

judy: And you are recruiting.

janina: Yes.

judy: Is that the gist of it for 2021.

janina: Pretty much. Confident that some we didn't get done, and some we did do. We did good job pre-TPAC to find our work.

judy: Thank you very much. Very satisfied with results.

<joconnor> CA: Lets postpone it until we have a wider group

<joconnor> JB: Comments on support and responses

josh: One thing for janina. Talking with Roy on paper on personalization in XR. How we can shoe them in with dom overlay api.
... Interesting work. It would be great to have POC for this. Mathew would be great person to talk to.

janina: Discussed on Monday, he would be perfect, and he might have personal interest.

judy: Was talking with Peter on Monday, he had discussed that I join 15 minutes of sub-group on conformance.
... I'm tentative.

janina: Eager to discuss, open to alternatives.

judy: Happy to discuss and try and get some help on better framing.

janina: We are open, already thinking of options.

judy: If I can't join tomorrow, he believes challenges doc is completed note, it's not.

janina: I think he is satisfied with how it lays out the concerns.
... Not that the note is complete.

judy: Anything from AGWG needs to come through the group.

janina: I will try to catch up with you (janina) on that.

This is scribe.perl Revision of Date 
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/not all groups/concern that not all groups/
Succeeded: s/absence/"absence" (metaphorically)/
Succeeded: s/roll/role/
Succeeded: s/janina/judy/
Succeeded: s/janina/judy/
Present: Chuck Judy joconnor janina
Found Scribe: Chuck
Inferring ScribeNick: Chuck

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 18 Nov 2020
People with action items: 

WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)