<LisaSeemanKest> scribe: Jennie

Lisa: maybe next year we will make a scribe list.

Review of actions https://www.w3.org/WAI/GL/task-forces/coga/wiki/PlanningPage#Actions

Lisa: Rachael has added to the actions the links to the items.
... if you are looking for them inline, they are in this new section. Is everyone ok with this?
... everyone agreed that this works well.
... EA's task?

Rachael: she did it.

Lisa: There is 1 other for John or David.
... David there was 1 more in the newly revised personas on Tom who had traumatic brain injury.
... John wrote a sentence on it, but it needs a bit more.

David: Are you doing an editor's call after this?

Lisa: Yes.

David: I was saving it for that.
... For the SC I was working on I the group was asking for research.
... Could we add this to the personas?
... I wrote a LinkedIn post about mental fatigue and its link to accidents around the world.
... it may sound hyperbolic, but it is true. Understanding this when designing is important.
... this pertains to many different disabilities.
... if we did 1 for PTSD, 1 for depression...we would be repeating ourselves for different disability types.

Lisa: Challenge 5 - Tim, touches on this.
... there are many things that affect multiple personas.
... It doesn't mean that they don't have these others. We should probably write a disclaimer that these are just examples.
... that challenges often occur in more than 1 persona.
... I think we can add it to challenge 5. You can imply it in challenge 4 as well.
... That is also in the mental health paper, which is next in the actions.
... Putting all that research into the mental health paper is fantastic, then it gets the right kind of review.
... Then we follow through from the Issue Paper - this is the starting point.

David: I think that makes sense.

Lisa: Great. Sorry, I jumped to David's.
... Rachael did you get to your tasks?

Rachael: I would like an extension to tomorrow.

Lisa: That's fine.

Rachael: What I would like to do with the Google docs, I would like to archive them, and make a copy of the current Git, then I can bring them back. Is everyone ok with that?
... we have personas in 3 places - the git, merge it into the master.
... the new and revised personas where we have been working,
... and EA emailed another version, which I think is the template for what is in the git now.
... I would like to retain everything else through links.

Lisa: I don't know anything about the copy EA sent us.

Rachael: I just want to link to it so we have the history, but not worry about it.

Lisa: We have the git, we make a new branch, we merge the new and revised, check that it is ok, then merge it back in.

Rachael: I have already incorporated the things from EA.

Lisa: I'm not ok with that since nobody has reviewed it.
... we have an editor's call after this, I suggest we table this to the editor's call.

Rachael: OK.

Lisa: Who is caller user 2?

John K: It is John Kirkwood.

Lisa: OK, so Rachael and I will coordinate these pieces.
... then there was one for Steve - checking if we captured all the user stories.
... we might want to send him a reminder.

John K: I am coordinating with Steve on that too.

Lisa: This is really important. I noticed that there are things being discussed and I wondered if we were missing any.
... Don't worry if we don't have a pattern.
... We can think about whether we know how to meet the need, or if we need to develop one.
... We just need all needs represented in the user stories.

David: I we interchanging user stories and personas?

Lisa: The personas are people like Tim.
... Then we had the user stories, which are at the top of the actions.

<LisaSeemanKest> https://docs.google.com/document/d/1xmmQkuZLEG014zDRVkgr3QLyINb7BNvWxqL7POn6Ei8/edit#

Lisa: making sure these vaguely map to the personas because this is how people understand it.

David: Personas have a name, and an identity.

Lisa: yes.
... The next thing: Rachael and I will add the missing aspects of the design patterns.
... others just need some editing.
... David you were going to work on the mental health issue paper. How is that going?

David: It is still going and will be done soon.

<LisaSeemanKest> https://docs.google.com/document/d/1G9SJSiAT-SYDVNxBfwOe7A6VPqsmX4Ua0QT7-NrfQTA/edit#heading=h.rpstiea4qz2r

Lisa: if you can add the references at the end of this document, that would be good.
... when you feel it is ready for others to review, please send to the list.
... then we will review the other documents to ensure all of it is addressed.
... That will be by December 31st.
... We have Justine working on the sections in Content Usable.
... She is not on the call.
... We should follow up on when she thinks she can get that done.
... We maybe need a call about what we want to see on the policy section.
... Justine is revising it. It seems to have slowed down. Maybe it is something we could all be thinking about.
... Guidance for Policy Makers.

<LisaSeemanKest> https://w3c.github.io/coga/content-usable/#guidance_for_policy_makers

Lisa: Could everyone review the headings, or think if there are other headings we would like.

Jennie: I can reach out to Justine and see if I can help out.

Lisa: This is a big one - we have a whole bunch of design patterns that we identified and we didn't have all the patterns we needed.
... David you picked 1 - did you manage to do that?

<LisaSeemanKest> David Fazio: I can get to the feature I need using the minimum number of easy steps

<LisaSeemanKest> https://docs.google.com/document/d/1k0QpMa2XKB4UIEJKjL98y7Dw7vcbtC41skRmrexGs6M/edit#heading=h.qqgz8tvr0tyj

Lisa: We were thinking of maybe doing one together later and that will help everyone fill in their pieces.

David: They don't take me much time once I get time to do it.

Lisa: John K there was one you were going to do with Steve.
... anyone else able to take 1 or 2?

Jennie: I can take one
... please assign me one

<LisaSeemanKest> https://www.w3.org/WAI/GL/task-forces/coga/wiki/PlanningPage#Actions

Jennie: I will take I need explanations of implied content, like body gestures and facial expressions seen in images and animations.

Lisa: Do we need to go over anything from 2.2?

Rachael: My SC I feel comfortable with
... others?

Jennie: at the last meeting, we troubleshooted and figured out some possible language updates. I'm drafting those now.

David: I don't need any support right now.

What needs to be done for next iteration of content usable https://w3c.github.io/coga/content-usable

John K: Mine is going well.

<LisaSeemanKest> https://w3c.github.io/coga/content-usable

Lisa: Are there other sections in Content Usable that people have time over the holiday to rewrite?
... I'm tempted to say if you have time, do an extra pattern. Just take one if you have time.
... Let's focus on patterns and get those done.

Missing patterns - maybe doing doing one together

Lisa: Send me an email if you decide you want to do part of Content Usable.
... With the Design Patterns that are missing, let's do 1 together.

<LisaSeemanKest> https://docs.google.com/document/d/1k0QpMa2XKB4UIEJKjL98y7Dw7vcbtC41skRmrexGs6M/edit#heading=h.qqgz8tvr0tyj

Lisa: We did the User Needs, we tried to map them to the patterns, and we found we were missing some patterns.
... the process is thorough, which is good.
... I will send the Making Content Usable an example pattern of 1 we have before

<LisaSeemanKest> https://w3c.github.io/coga/content-usable/#pattern-make-the-purpose-of-your-page-clear

Lisa: it is the first one in the document.
... Starts with a sentence telling people what to do.
... Then we have "How to help"
... Then we have details, then examples which illustrate what to do.
... That's the basic template.
... Should we do one together, or each try and do one?

David: Works for me.

Lisa: Let's do Controls do not move unexpectedly when I am using them.

<LisaSeemanKest> https://docs.google.com/document/d/1k0QpMa2XKB4UIEJKjL98y7Dw7vcbtC41skRmrexGs6M/edit#heading=h.yypo6txw1ow8

Lisa: I will fill in the pattern name.
... 1st I'm giving it a title, using active voice.
... (editing done in document and will not be added into minutes).
... After the name is the pattern description.
... I will add the instructions from the template.

(group shared examples from YouTube, Windows File Explorer, recent calls on a smartphone)

Lisa: 1st we need the instruction in active voice.
... and we should put the instructions for how it helps.
... include a sentence such as "Fore example, a user with..."

<johnkirkwood> +1 to difference on content and controls moving

Lisa: getting started you do not need to add.
... in the details we should indicate where it is not a problem.
... Can others stay on the line to work on their own one now?

Rachael: I can keep the line open.

<johnkirkwood> sorry had to drop

<Rachael> Have a good holiday. Next meeting is January 9th

<Rachael> trackbot end meeting

This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Default Present: JohnRochford, Rachael, johnkirkwood, Roy, Jennie, LisaSeemanKest, Fazio, stevelee_, MichaelC
Present: JohnRochford Rachael johnkirkwood Roy Jennie LisaSeemanKest Fazio stevelee_ MichaelC
Found Scribe: Jennie
Inferring ScribeNick: Jennie

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

Found Date: 19 Dec 2019
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.)