17:02:20 RRSAgent has joined #eo 17:02:20 logging to http://www.w3.org/2016/07/20-eo-irc 17:02:22 RRSAgent, make logs world 17:02:22 Zakim has joined #eo 17:02:24 Zakim, this will be 3694 17:02:24 ok, trackbot 17:02:25 Meeting: Education and Outreach Working Group Teleconference 17:02:25 Date: 20 July 2016 17:04:25 Scribe: Brent 17:04:37 https://www.w3.org/WAI/EO/wiki/WAI_site_TF/Technicalities 17:04:49 Eric: Need to look at time again to see if this is the best time for James to meet. 17:05:27 Eric: Technicalities page is where Eric is adding ideas and research on technologies. 17:06:10 ... Most of the information will work its way into the backlog. 17:06:22 Eric: First up is the CMS 17:06:52 ... Eric talking through the pros and cons of the CMS. 17:07:46 ... Pros - Easy to use, Consistent navigation, Allow for quick updates and little team involvement 17:09:33 ... Cons - Probably not flow well back and forth with GitHub, Would need to be maintained and updated, Our content is diverse so this could be restricted a little by the CMS with the document structures types available. 17:10:16 Eric: Other idea would be to build some type of custom CMS that could flow back and forth with GitHub. Also have comparison features. 17:11:06 ... Could build a preview functionality as well that could be beneficial to the work on the project. 17:11:32 Anna Belle: Eric are you aware of any CMS in the W3C that could be used? 17:11:55 Eric: The WordPress is the only one that I am aware of that we have. 17:12:48 Anna Belle: FYI - I know WordPress quite well so I am happy to talk with you about that. 17:13:38 Eric: Connection to GitHub is the biggest concern that would need to be overcome. WordPress has its advantages and drawbacks. 17:14:24 Eric: Next topic is Central navigation 17:15:32 ... Need to wait on the IA portion to see what direction we need to go with navigation. 17:16:02 ... Two ways to do it. start with light navigation and you have to dig deeper and deeper as you go. 17:16:36 ... Or start with most important stuff at top and as the user digs deeper they find the variety of resources. 17:17:06 Sharron has joined #eo 17:17:43 Anna Belle: What I have used most recently is have a master template that was used for each page, then used includes for header, navigation, footer. 17:18:00 q+ to say that is the way that we were planning to go 17:18:02 ... was with a big site but allowed us to customize. 17:18:07 q- 17:18:46 Eric: If we provide a preview on GitHub, there is conciderations as it will not allow includes as easily. 17:19:17 ... Could be problematic for resources with sub-pages as a lot of that may need to be handled manually. 17:19:44 ... How much do we want to be automatic vs. manually. This will make a difference with iteration. 17:20:40 Eric: CMS - we could split it up. One CMS for press releases, etc. Then on the other side a CMS for resources that are not needing to be updated. 17:20:57 ... For more static-ish resources 17:22:21 Eric: When we are creating new or updating resources that are on GitHub, we would fork the base repository, this would allow quick set up for new resources and preview. 17:22:42 ... Then we can have sub-repositories. 17:23:47 Eric: If we go with Custom CMS, when reviewing the page, can add ? to URL to review the page which would add some simplification to reviewing. 17:24:00 Eric: Any questions? 17:24:58 ... no questions. That is all. 17:25:18 http://www.webpagetest.org/result/160713_NC_d691cf9644daf968336a109052ff6eab/ 17:25:22 Eric: Last thing is the Performance Budget 17:25:44 ... This is about testing pages for performance. 17:26:11 ... This will help in informing our decisions for design. 17:26:55 ... One of our priorities is that our pages load fast. Interesting to watch the performance results. 17:27:33 ... Want to manage and keep the kilobytes very low so pages load fast. 17:28:03 ... I will be learning and researching more about how it works and will report back to the group to help keep us on track for performance. 17:28:19 Anna Belle: Any questions? 17:29:05 Anna Belle: I have been planning to use that exact same tool for testing performance. Thinking we should keep some results on the wiki site for tracking performance. 17:29:39 Topic: Backlog 17:29:48 q+ 17:29:52 q. 17:29:54 q- 17:29:57 s/q./ 17:30:01 https://3.basecamp.com/3119737/buckets/936310/messages/173370065 17:30:02 Anna Belle: Set up on Basecamp a temporary file for backlog 17:30:29 Eric: When we decide for a name for the repository, I can post the new information. 17:30:34 https://github.com/w3c/wai-website-design 17:31:14 Anna Belle: James and I talked about the next steps for jumping into high gear on the work. 17:31:37 ... Thought we would start by focusing on the information architecture and the design. 17:31:52 ... Start working the the adjectives and the goals. 17:32:32 ... Appears that Charlotte (?) UT would have some time in August to work with the group on Information Architecture. 17:32:45 ... So where should the task force start? 17:32:48 q+ 17:33:23 q- y 17:34:00 Eric: For more background information... it is like a pool of information. When things don't work you put it into the backlog and then start to prioritize that work during a sprint meeting. 17:34:15 ... What do we actually want to do, and who does what. 17:34:37 ... Some others may work on some smaller side projects. 17:35:11 ... So keep in mind that we may not need everyone doing all one task all the time unless it is needed. 17:36:01 Eric: Start with IA. Information gathering, what are the smaller components. I think it is a good place to start. Collect what we have on the page. 17:37:04 Anna Belle: What do you think about simultaniously starting with style tiles? What I was discussing with James, August 1 we would get in touch with those interested in visual design work and get them started pulling together fonts, colors, etc. 17:37:56 ... We could all be working on visual design simultaniously. Then at the end of the month it could be submitted and the TF could make selections and move forward. 17:38:48 ... Could have this anonatized where people could submit annonmously the designs they work on. 17:39:31 Eric: This makes sense. Help stay away from templating, etc. I think this is good and can work in parallel with the rest of the work. 17:41:01 Sharron: I agree with starting IA and working simultaniously on other design is a great idea. 17:41:56 Anna Belle: Have asked James if he would be willing to model using the backlog. 17:42:29 ... Eric, do you know how to do this. Agile, so that you could model backlogging? 17:42:54 Eric: Yes I have a while ago. Need a good PjtMgr to do that. 17:43:59 ... Basically, what you put in is formulate what a user would want to do on the page, like "expand/collapse". Then you dump that application/functionality into the backlog. 17:44:28 Then after everything is in you go about prioritizing what shoule be worked on and when. 17:45:16 Eric: Another way is to use it more like an issue tracker. Put in issues and then formulate them as tasks. 17:46:12 ... Then you have the standup work meetings. Everyone participates and talks about their tasks. Work through the Sprint planning. 17:46:34 ... Using Spring Points to assign what tasks can be completed in the current Sprint. 17:46:56 s/Spring/Sprint/ 17:47:30 ... As Sprints move on, the team starts to understand how long various tasks take and can make adjustments as needed. 17:48:05 Eric: Stand up meetings where everyone is just checking in, talking about what they have done, assigning tasks, etc. 17:48:37 Anna Belle: Shawn, your thought on running IA and visual design side by side? 17:48:52 Shawn: I am all for concurrent work. Good idea. 17:49:11 Shawn: I am wondering about the Search. 17:49:51 ... It's important to get going on the IA and the visual design. They depend on each other and are required for the coding. 17:50:26 ... What I learned from the analytics is the amount of people clicking on the Search. Not sure what is involved in implementing a smart search. 17:50:28 q+ to say “define smart search” :-D 17:50:55 Judy has joined #eo 17:51:10 ... If we had that smart search, we wouldn't have to wait for that to be deployed. Could be a different person working on that? Could we actually work on all three at the same time? 17:51:20 q- y 17:51:52 Eric: Need to define what we mean by smart search. What meta information do we need? What functionality? 17:52:21 ... Would it be like the Quickref? Would be heavy on the data side. Fun, Interesting. 17:52:47 ... We sould at least define and find good examples of what we thing the smart search will have. 17:52:57 Search in part of Information Architecture 17:53:16 ... Could stage it out. Stage out the work. But we need to define the finish line. 17:53:42 s/Search in/Search is/ 17:53:58 Anna Belle: As part of this, maybe Brent could do a brainstorming session on the smart search. 17:54:25 Brent: Yes, I could do that if the Task Force decides that is appropriate. 17:54:53 Anna Belle: Thank you all so much. That is it for now. 17:55:08 q+ 17:55:09 ... James will most likely be leading the call next week. 17:55:32 q- y 17:55:57 Eric: Is there anything we should do now? Action items? To report back to the larger Task Force group. 17:56:41 Anna Belle: I can send out an email to the redesign task force about starting backlog. 17:57:08 ... This is temporary in basecamp now and James can transfer into GitHub 17:57:43 Eric: We can use the current GitHub repository for the backlog. 17:58:11 Anna Belle: James has indicated that he wants to set up the backlog. Eric can you work with him on that. 17:58:31 ... Then we can encourage Task Force members to start adding to the backlog. 17:58:49 Anna Belle: Anything else for today? 17:59:03 Shawn: Just excited about getting going on the work. 17:59:09 Sharron: agreed 17:59:13 Brent: agreed 17:59:48 present+ Sharron 17:59:52 rssagent, draft minutes 18:00:04 rrsagent, draft minutes 18:00:04 I have made the request to generate http://www.w3.org/2016/07/20-eo-minutes.html yatil 18:00:20 rrsagent, draft minutes 18:00:20 I have made the request to generate http://www.w3.org/2016/07/20-eo-minutes.html yatil 18:00:28 trackbot, make logs world 18:00:28 Sorry, yatil, I don't understand 'trackbot, make logs world'. Please refer to for help. 18:00:41 rrsagent, make logs world 18:00:44 rrsagent, draft minutes 18:00:44 I have made the request to generate http://www.w3.org/2016/07/20-eo-minutes.html yatil 18:00:54 Chair: Anna Belle 18:01:35 presen+ Brent, Shawn, Anna Belle, EricE, NotJames 18:01:50 s/NotJames/ 18:02:05 s/presen+ Brent, Shawn, Anna Belle, EricE, NotJames/present+ Brent, Shawn, Anna Belle, EricE 18:02:12 rrsagent, draft minutes 18:02:12 I have made the request to generate http://www.w3.org/2016/07/20-eo-minutes.html yatil 18:02:49 s/presen+ Brent, Shawn, Anna Belle, EricE,/present+ Brent, Shawn, Anna Belle, EricE 18:02:50 rrsagent, draft minutes 18:02:50 I have made the request to generate http://www.w3.org/2016/07/20-eo-minutes.html yatil 18:03:01 rrsagent, draft minutes 18:03:01 I have made the request to generate http://www.w3.org/2016/07/20-eo-minutes.html yatil 18:03:20 s|s/present+ Brent, Shawn, Anna Belle, EricE NotJames/present+ Brent, Shawn, Anna Belle, EricE| 18:03:20 rrsagent, draft minutes 18:03:20 I have made the request to generate http://www.w3.org/2016/07/20-eo-minutes.html yatil 18:03:46 s/presen+ Brent, Shawn, Anna Belle, EricE,/present+ Brent, Shawn, Anna Belle, EricE 18:03:48 rrsagent, draft minutes 18:03:48 I have made the request to generate http://www.w3.org/2016/07/20-eo-minutes.html yatil 18:04:05 s/rssagent, draft minutes/ 18:04:20 s/trackbot, make logs world/ 18:04:30 s|Sorry, yatil, I don't understand 'trackbot, make logs world'. Please refer to for help.| 18:04:33 rrsagent, draft minutes 18:04:33 I have made the request to generate http://www.w3.org/2016/07/20-eo-minutes.html yatil 18:06:20 i|https://www.w3.org/WAI/EO/wiki/WAI_site_TF/Technicalities|Topic: Technicalities 18:06:48 i/First up is the CMS/Topic: Tech – CMS 18:07:18 i/Central navigation/Topic: Tech – Navigation 18:08:03 i/For more static-ish resources/Topic: Tech – Static Resources/ 18:08:34 i|http://www.webpagetest.org|Topic: Tech – Performance Budget 18:08:40 rrsagent, draft minutes 18:08:40 I have made the request to generate http://www.w3.org/2016/07/20-eo-minutes.html yatil 18:09:39 s/Anna Belle:/AnnaBelle:/g 18:09:41 rrsagent, draft minutes 18:09:41 I have made the request to generate http://www.w3.org/2016/07/20-eo-minutes.html yatil 18:10:39 s|http://www.w3.org/2005/06/tracker/irc|g 18:10:41 rrsagent, draft minutes 18:10:41 I have made the request to generate http://www.w3.org/2016/07/20-eo-minutes.html yatil 18:11:04 s/s|Sorry, yatil, I don't understand 'trackbot, make logs world'. Please refer to for help.|/ 18:11:06 rrsagent, draft minutes 18:11:06 I have made the request to generate http://www.w3.org/2016/07/20-eo-minutes.html yatil 18:11:24 s|Sorry, yatil, I don't understand ''. Please refer to for help.| 18:11:26 rrsagent, draft minutes 18:11:26 I have made the request to generate http://www.w3.org/2016/07/20-eo-minutes.html yatil 18:11:48 s/trackbot, make logs world/ 18:11:49 rrsagent, draft minutes 18:11:49 I have made the request to generate http://www.w3.org/2016/07/20-eo-minutes.html yatil 18:12:28 ScribeOptions: --final --noEmbedDiagnostics 18:12:29 rrsagent, draft minutes 18:12:29 I have made the request to generate http://www.w3.org/2016/07/20-eo-minutes.html yatil 18:13:06 s/--final --noEmbedDiagnostics/-final -noEmbedDiagnostics/ 18:13:07 rrsagent, draft minutes 18:13:07 I have made the request to generate http://www.w3.org/2016/07/20-eo-minutes.html yatil 18:16:29 trackbot, end meeting 18:16:29 Zakim, list attendees 18:16:29 As of this point the attendees have been Sharron 18:16:37 RRSAgent, please draft minutes 18:16:37 I have made the request to generate http://www.w3.org/2016/07/20-eo-minutes.html trackbot 18:16:38 RRSAgent, bye 18:16:38 I see no action items