17:00:38 RRSAgent has joined #eo 17:00:38 logging to http://www.w3.org/2017/08/09-eo-irc 17:00:40 RRSAgent, make logs world 17:00:40 Zakim has joined #eo 17:00:42 Zakim, this will be 3694 17:00:42 ok, trackbot 17:00:43 Meeting: Education and Outreach Working Group Teleconference 17:00:43 Date: 09 August 2017 17:00:50 present: Shawn, Laura, Eric 17:01:58 present+ Brent 17:02:17 present+ 17:02:23 zakim, who is on the phone? 17:02:23 Present: Shawn, Laura, Eric, Brent, shawn-brb 17:02:34 present- shawn-brb 17:02:37 zakim, who is on the phone? 17:02:37 Present: Shawn, Laura, Eric, Brent 17:02:46 chair: James 17:02:51 scribe: Brent 17:06:11 present+ James, Charlotte 17:06:57 James calls meeting to order. 17:07:28 Topic: Information Architecture Feedback 17:08:04 James: Charlotte and I can do another round of updates based on feedback provided by Shawn. 17:08:12 ... Is that okay with everyone? 17:08:20 Shawn: Yes 17:08:25 No other comments. 17:08:49 Topic: Development work 17:09:38 Eric: Caleb and I are working on the structure of the site. Working on some components and the front page. When I have something more to show, I will send it our for comment. 17:10:09 James: Good, Thanks Eric. 17:10:29 Topic: Reviewing open issues 17:10:55 Issue #72: Spacing and Proximity 17:11:06 Shawn: Spacing looks much better. 17:11:29 James: Adding comment that it looks good to task force. 17:11:34 Shawn: What about the bullet? 17:11:48 Eric: Worked on that. I think I have it working in any combination. 17:11:57 Shawn: Looks great. Thank you Eric. 17:12:24 Issue #71: nav - current page indicator 17:12:54 #71: nav - current page indicator 17:13:28 James: Alicia worked on the visual of the page indicators. 17:14:01 SLH: maybe make the separator lines quieter 17:14:08 zakim, who is on the phone 17:14:08 zakim, who is on the phone? 17:14:08 I don't understand 'who is on the phone', yatil 17:14:09 Present: Shawn, Laura, Eric, Brent, James, Charlotte 17:14:09 Brent: triagnles are enough indication 17:15:16 Eric: I think the indicator triangle is okay. We should try it for a while and can adjust later if needed. 17:15:58 Shawn: Lines quieter means making them a little darker, less pronounced. 17:16:45 James: #71, adding task force is okay with triangles for now and closing issue. 17:17:37 #70: suggest slightly darker lines, and remove the last line (see comment). 17:18:32 Action - yatil add Alicia to the EO group in GitHub so assignments can be given to her. 17:18:32 Error finding '-'. You can review and register nicknames at . 17:18:55 ACTION yatil add Alicia to the EO group in GitHub so assignments can be given to her. 17:18:56 Created ACTION-381 - Add alicia to the eo group in github so assignments can be given to her. [on Eric Eggert - due 2017-08-16]. 17:19:52 #69 - Home Page Content 17:20:45 James: Shawn's concern is that we decide what the home page content is. What is included. 17:21:03 Shawn: Yes, some of that content will need to be created. 17:22:24 ... There are areas that we have visual design for, we need to make decisions on what we are going to include, and if it is included then we need to start working on it. 17:23:11 yatil: We do have some of the content and iconography that would/could be used. 17:23:45 James: Should we create another "resource" for Home Page Content that we assign people to and have people work on? 17:24:32 Shawn: Featured resource, tip of the day, featured video are easier to do. 17:25:17 ... The middle [showcase] boxes that are there need some decision of what we will put there and what content needs to be created or linked to. 17:26:04 James: These four slots could be our high quality, or high priority resources that we want to lead people to. 17:26:57 Homepage link: https://visa.invisionapp.com/share/YPAVCUZA9#/screens/234693428 17:28:07 Brent: label them, not showcase, mabe "Leader boxes" 17:28:54 +1 for section headingg 17:29:08 Yatil: Some examples - BAD, Policies, Tutorials, Etc... 17:29:48 Shawn: make clear if those are going to change 17:30:42 Brent: let's say on leads to BAD, and they don't see it in the nav. they use that leader box to lead them to BAD. then we change it, and then they feel frustrated 17:31:03 ... do think they should change. And think some title to make clear they'll change 17:31:23 eric: featured resource 17:31:34 james: already have at top. do we related these? 17:31:49 Shawn: If they are not going to be static, need some indication so that people will know that these "feader boxes" will change. 17:32:11 Eric: link to all featured resource 17:32:17 +1 to link to all !!! 17:32:35 James: Idea - integrate it with "Featured Resources" at the top and cycle them down. 17:32:47 +1 for link to all for all rotating content, including tip of the Week 17:34:14 [ Eric: We could have an additional link to all tips. ] 17:34:27 James: Propose that we make this Home Page Content another "resource" to work out a plan and content proposal and do the work and bring to the Task Force for approval of the home page content. 17:35:07 Shawn: This is not formal EOWG deliverable -- good to get input, but not need formal WG approval 17:35:16 ... shawn and Brent, do you want to come up with the strategy/plan and recommendations? 17:35:34 Shawn: Yes, but may not be next week. 17:36:22 Brent: tip of the week... concern with that. 17:36:52 ... know what we're getting into. we';; burn thorugh that content in 1/2 year 17:37:08 s/we';; burn thorugh/we'll burn through 17:37:15 q+ 17:37:25 ... when fit end, either start over, or have people to write it 17:37:49 .... We do that in our group, and it is a big challenge to come up with good quality, vetted content. spend about 3 hours / week 17:38:19 close action 381 17:38:43 q+ 17:39:28 q+ to say denis; can start over; can add some 17:40:15 ack e 17:40:18 ack y 17:40:51 Yatil: I was thinking they would be direct links to the quick tips content. 17:41:22 q+ to say quick tip / week/ day 17:41:24 ack me 17:41:24 shawn, you wanted to say denis; can start over; can add some and to say quick tip / week/ day 17:41:25 ... Not too concerned about the amount and starting over. 17:42:11 Shawn: Agree we could start over and rotate them. We can add some. Denis said he wanted to create many of these and have them somewhere. 17:42:38 q+ to say make the random one sticky for 24 hours using javascript 17:42:44 ... Another idea could be that we drop "week" and just have tips that are shown. 17:43:13 James: Could say "design tip", etc. and have a bunch of them that could randomly load. 17:44:05 Shawn: Need to do more thinking about this. Some of them we want to get them to the details of the tip content. 17:44:27 ack me 17:44:27 yatil, you wanted to say make the random one sticky for 24 hours using javascript 17:44:45 Yatil: Would be good to show a random one but let it stick for a while before moving to the next random one. 17:45:42 James: Shawn and Brent will take up this "tip of the week" issue as well as part of the Home Page Content plan. Bring back to Task Force when ready. 17:46:09 #68 - Homepage Sponsors and Funders 17:46:34 James: Alicia has already added that to the page footer. 17:46:46 Shawn: One issue is the two columns. 17:47:08 Yatil: I will be able to take care of that. 17:47:18 James: closing issue #68. 17:47:48 #66 - no "learn more" links 17:48:04 Shawn: This is complete, close issue. 17:48:13 #65 - Above the fold 17:48:48 Yatil: I am okay with having "About WAI" where it is. Don't need to have it higher on the page. 17:49:38 Shawn: I am fine with this. I still wish the static content was a little visually different than dynamic content, but I am okay with this. 17:49:48 #64 - Big Footer Nav 17:49:59 Shawn: still think would be better to have static content look differently than chaning content, but don't feel super strongly about it 17:50:05 James: This one needs to stay as is until we finish edits to the IA. 17:51:19 #50 - Design Mockups: Ideas for fly-out menu on sub pages? 17:51:48 Shawn: Need to keep this open as it is a big issue. From a usability / accessibility standpoint. 17:52:33 #41 - Design Mockups: In-page links 17:53:02 Yatil: This was a long time ago. I think there have been changes and we are good with this issue now. 17:53:23 James: Closing #41 17:54:02 #32 - Translations 17:54:31 Shawn: Need a little more focus on what the translation interface will be, what it will look like, how it will work. 17:54:42 James: Okay, adding that to issue. 17:55:13 Topic: Next Meeting 17:55:26 James: Do we need to meet next week? 17:55:38 Topic: User Testing 17:56:03 Charlotte: Going to treat everyone like I treat others who come through the lab. 17:56:36 ... Have a information sheet that I would like Shawn, Sharron, and Brent to fill out. Would like this by next week. 17:57:05 ... There are other items on a timeline to prep for the user studies. I will send out the timeline. 17:58:14 ... In order for this to all happen in mid September we need to be sure that we have a solid IA in place for testing (not a lot of changes taking place to the site). Need by the 11th, no later. 17:58:44 ... Anything we want tested needs to be in final state by September 11. 18:00:24 ... Pushing the user testing out to October will be an issue with completing the site by TPAC. 18:01:32 Shawn: There are comments that I had made for the IA (some questions, some things missing). Have not received any comments back on this feedback. 18:02:01 Yatil: What about putting those into GitHub and going through them one by one next week so that we can decide on each? 18:04:26 James: Let's get the IA done. Charlotte and I can go through Shawn's comments and work through the issues. 18:04:57 Shawn: Would like for the three of us to do this together. It will save a lot of going back and forth. 18:09:02 James: Better yet, Shawn take your comments and make the changes and we will impliment. 18:10:22 s/impliment/implement 18:15:38 James: Next week we will work at final discussion of IA and have a complete IA in place. We will also have completed survey forms to Charlotte (from Shawn, Brent, Sharron) so we can move deeper into prep planning for user studies. 18:15:49 James: Anything else for this week? 18:15:55 ... Meeting adjourned. 18:27:34 [ Eric added Alicia to the EO Team on Github. ] 18:28:08 rrsagent, draft minutes 18:28:08 I have made the request to generate http://www.w3.org/2017/08/09-eo-minutes.html yatil 18:28:22 rrsagent, make logs world 18:29:41 i/Topic: User Testing/[Tentatively: IA questions meeting lead by Shawn] 18:30:08 rrsagent, draft minutes 18:30:08 I have made the request to generate http://www.w3.org/2017/08/09-eo-minutes.html yatil 18:30:44 scribeOptions: -final -noEmbedDiagnostics 18:30:45 rrsagent, draft minutes 18:30:45 I have made the request to generate http://www.w3.org/2017/08/09-eo-minutes.html yatil 18:31:08 trackbot, end meeting 18:31:08 Zakim, list attendees 18:31:08 As of this point the attendees have been Shawn, Laura, Eric, Brent, shawn-brb, James, Charlotte 18:31:16 RRSAgent, please draft minutes 18:31:16 I have made the request to generate http://www.w3.org/2017/08/09-eo-minutes.html trackbot 18:31:17 RRSAgent, bye 18:31:17 I see no action items