23:59:22 RRSAgent has joined #tpac 23:59:22 logging to https://www.w3.org/2019/09/17-tpac-irc 23:59:45 meeting: TPAC 2019 Plenary 00:00:03 msw__ has joined #tpac 00:00:04 Zakim has joined #tpac 00:01:10 Ian has joined #tpac 00:01:48 shawn has joined #tpac 00:02:10 yofukami has joined #tpac 00:02:12 toshiakikoike has joined #tpac 00:02:20 RRSAGENT, set pointer 00:02:20 I'm logging. I don't understand 'set pointer', Ian. Try /msg RRSAgent help 00:02:24 RRSAGENT, pointer? 00:02:24 See https://www.w3.org/2019/09/17-tpac-irc#T00-02-24 00:02:30 Topic: Plenary 00:02:31 -> https://www.w3.org/2019/Talks/TPAC/ceo-tpac-update/ CEO Update slides 00:02:32 MO has joined #tpac 00:02:36 scribenick: Ian 00:02:43 Jeff: Welcome! Lots of attendance! 00:02:52 [Housekeeping] 00:02:53 dsinger has joined #tpac 00:02:55 Kangchan has joined #tpac 00:02:56 hfuji has joined #tpac 00:03:01 Yougnsun has joined #tpac 00:03:02 Sophie_ has joined #tpac 00:03:03 gildas has joined #tpac 00:03:04 dom has joined #tpac 00:03:06 florian has joined #tpac 00:03:09 Jeff: Please complete the survey to help us improve TPAC 00:03:12 dezell has joined #tpac 00:03:18 kimwooglae has joined #tpac 00:03:20 takio has joined #tpac 00:03:20 wonsuk has joined #tpac 00:03:20 hirata has joined #tpac 00:03:22 jkamata has joined #tpac 00:03:25 ...Naomi and the Keio Team were amazing at securing sponsors; most sponsors ever. 00:03:25 ajitomi has joined #tpac 00:03:33 iclelland has joined #tpac 00:03:34 suzuki has joined #tpac 00:03:37 joemedley has joined #tpac 00:03:38 [Slide displays all sponsor names] 00:03:45 fantasai has joined #tpac 00:03:45 yoshiaki has joined #tpac 00:03:53 prushforth has joined #tpac 00:04:03 CharlesL has joined #tpac 00:04:05 takashi has joined #tpac 00:04:07 Jeff: Many thanks in particular to the Platinum Sponsors: Rakuten Insitute of Technology, Coil, NTT 00:04:08 Masa has joined #tpac 00:04:15 s/Insitute/Institute 00:04:17 cwarnier has joined #tpac 00:04:21 present+ 00:04:27 Jeff: Thanks also to Gold sponsor Panasonic 00:04:35 Jeff: Let's thank all the sponsors! 00:04:37 present+ 00:04:44 I have made the request to generate https://www.w3.org/2019/09/17-tpac-minutes.html Ian 00:04:45 present+ 00:05:04 Jeff: Please recall that all W3C meetings are guided by our Code of Conduct 00:05:11 present+ 00:05:18 -> https://www.w3.org/Consortium/cepc/ Code of Ethics and Professional Conduct 00:05:19 yamada has joined #tpac 00:05:34 jorydotcom has joined #tpac 00:05:35 Jeff: There is a CG that is working on a substantial revision to the code of conduct. 00:06:05 Jeff: Schedule for today before breakouts includes two important topics: continuous spec developments and MDN 00:06:09 plh has joined #tpac 00:06:12 ...there is also a breakout session on Process 2020 later today 00:06:13 shimazu has joined #tpac 00:06:26 present+ 00:06:47 ....MDN did a developer survey to look at developer needs; W3C participated. We think it's important for the W3C community to hear the results, and there will be a breakout later today. 00:06:54 marie has joined #tpac 00:07:04 -> https://w3c.github.io/tpac-breakouts/sessions.html TPAC 2019 breakout schedule 00:07:10 jezza has joined #tpac 00:07:21 Jeff: We will finalize the breakout grid (this year mostly done before TPAC started) 00:07:30 Jeff: We canceled reporting this year in favor of more breakout time 00:07:41 Jeff: Tonight we have a reception on the first floor 00:08:02 Jeff: Some additional points for the community; we are proud of our commitment to diversity. 00:08:15 ..we created a diversity fund to raise money to pay expenses for people who might not be able to attend otherwise 00:08:33 ...In 2018 we enabled 2 people to attend. 00:09:09 ...In 2019, under Léonie Watson's leadership, we were able to support 7 scholarships. Many thanks to the 11 companies that enabled that. 00:09:18 ReinaldoFerraz has joined #tpac 00:09:37 ...we did hear that it requires time in companies to budget for these scholarships, so for next year we will start this effort sooner 00:09:46 [W3C Process] 00:10:10 Process CG mailing list https://lists.w3.org/Archives/Public/public-w3process/ 00:10:15 Jeff: Process changes managed through the Process CG; many important changes are coming. Please see the editors' draft for what's coming 00:10:25 present+ 00:10:25 Process CG GitHub https://github.com/w3c/w3process/issues 00:10:26 ...the small team that does this work is doing amazing work, but we'd like broader participation. 00:10:33 [TPAC 2020] 00:10:47 Jeff: next year's meeting 26-30 October in Vancouver, Canada 00:11:07 Topic: Continues Specification Development 00:11:15 [Fantasai and Philippe Le Hégaret] 00:11:25 JohnJansen has joined #TPAC 00:11:35 plh: Good morning and thanks for surviving TPAC so far! 00:11:59 -> https://www.w3.org/2019/Talks/TPAC/continuous-standards/# Continuous Spec Development Slides 00:11:59 nigel has joined #tpac 00:12:07 PLH: Come to the breakout session and don't hesitate to ask us questions. 00:12:36 rrsagent, pointer? 00:12:36 See https://www.w3.org/2019/09/17-tpac-irc#T00-12-36 00:12:43 [Ian does not plan to reproduce the slides by scribing PLH verbatim] 00:12:56 kaz has joined #tpac 00:12:59 -> https://www.w3.org/2019/Talks/TPAC/continuous-standards/#3 Where can the REC track be improved? 00:13:24 PLH: One note - patent policy commitments only solidify at REC, even though deployment happens sooner. 00:13:32 tk has joined #tpac 00:13:41 jc has joined #tpac 00:14:01 -> https://www.w3.org/2019/Talks/TPAC/continuous-standards/#4 Use cases 00:14:34 PLH: Use cases: Vocabularies (e.g., DCAT), mappings, registries, profiles, maintenance, enhancement, rapid development, tracking 00:14:45 -> https://www.w3.org/2019/Talks/TPAC/continuous-standards/#5 Interested groups 00:15:14 PLH: If you are a chair and you want us to stop by your meeting let us know. 00:15:19 -> https://www.w3.org/2019/Talks/TPAC/continuous-standards/#6 Goals 00:15:42 Kiyoshi has joined #tpac 00:16:06 PLH: Goals include preserving important goals like consensus, wide review 00:16:15 -> https://www.w3.org/2019/Talks/TPAC/continuous-standards/#7 Design intentions 00:16:25 Kiyoshi has joined #tpac 00:16:34 PLH: Goal is to include this evolution in Process 2020 00:17:01 ...the current preference is to fix the Rec track rather than create a parallel track, and to continue to incrementally improve the Rec track 00:17:25 fantasai: We propose a set of fixes (which can be taken together or separately) 00:17:29 -> https://www.w3.org/2019/Talks/TPAC/continuous-standards/#9 Process Improvements Package 00:17:48 -> https://www.w3.org/2019/Talks/TPAC/continuous-standards/#10 Secure licensees sooner 00:18:09 fantasai: Licenses are not guaranteed until Rec status. We'd like to get them sooner since specs are deployed sooner. 00:18:14 fantasai: each of these 6 proposals can be taken individually, but adopting them all give the most benefits 00:18:22 kaz_ has joined #tpac 00:18:28 ...the proposal is to adopt a contribution model (like WhatWG and Community Groups) 00:19:00 ...licenses by all participants would become active at the end of each exclusion period. 00:19:11 Fantasai: Key Questions: Can we change patent policy? Do we need to experiment? 00:19:22 -> https://www.w3.org/2002/09/wbs/33280/improved-pp-2019/ Survey for AC reps on this topic 00:19:29 christianliebel has joined #tpac 00:19:33 -> https://www.w3.org/2019/Talks/TPAC/continuous-standards/#11 Proposed Fix: Streamlining Routine CR Update Approvals 00:19:46 fantasai: Updating WDs is automatic given WG approval, but updating CR requires Director’s Approval. Most updates, however, are routine and don’t need much scrutiny. 00:20:02 ...so the proposal is to allow automatic Director’s Approval for straightforward cases 00:20:30 ...e.g., where there is a WG decision, no objections, changes documented, no new features, etc. 00:20:38 ...we'd like to make this easy case automatic 00:20:50 denis has joined #tpac 00:20:55 -> https://www.w3.org/2019/Talks/TPAC/continuous-standards/#12 Decoupling CR updates from CR review drafts 00:21:26 fantasai: We'd like to decouple CR into two types of publications: (1) Updates and (2) Review draft 00:21:43 ...the latter would trigger Call for Exclusions and other process checks 00:21:51 ...this would align with how many groups operate today 00:22:27 ...we'd like to make it easier to update CRs so that W3C points people to the same draft developers are looking at 00:22:34 -> https://www.w3.org/2019/Talks/TPAC/continuous-standards/#13 Modifying a Rec 00:22:38 jc has joined #tpac 00:22:40 xfq has joined #tpac 00:22:49 MURATA has joined #tpac 00:22:50 fantasai: We'd like to allow groups to inline errata. 00:23:07 ..allow in-place updates to a REC; no approval process needed to get feedback of modifications 00:23:16 ...let's implementers see changes are coming 00:23:35 ...and once there is review of these inline modifications, you can do a call for review to get a formally updated Recommendation 00:23:45 ...you can get review of some or all of the inline modifications 00:23:45 MURATA has left #tpac 00:23:47 MURATA has joined #tpac 00:23:57 MURATA has left #tpac 00:23:58 -> https://www.w3.org/2019/Talks/TPAC/continuous-standards/#14 Allow Adding Features to an Extensible REC 00:24:19 Fantasai: Some communities want stable feature set, others want continuous development 00:24:38 ...the proposal is to re-use REC maintenance process for incorporating proposed changes (above) to also allow incorporating proposed additions into specifications chartered to be extensible. 00:24:45 ..and make clear to each community what they are getting 00:24:58 -> https://www.w3.org/2019/Talks/TPAC/continuous-standards/#15 New process for registries 00:25:05 fantasai: Registries need lightweight update process, possible maintenance outside a WG 00:25:15 ...proposal is for a new type of technical report for W3C Registries 00:25:37 ...proposal allows for continuous updating of registry with low overhead 00:25:56 ...different registries may have different levels of process, so the check is "was the expected process followed" for that registry 00:26:04 ...updates to registry publication that conform to registry definition can be published instantly. 00:26:21 [PLH on impact] 00:26:28 -> https://www.w3.org/2019/Talks/TPAC/continuous-standards/#18 impact on WGs 00:26:32 I have made the request to generate https://www.w3.org/2019/09/17-tpac-minutes.html Ian 00:27:01 PLH: easier maintenance, lower overhead, earlier patent commitments 00:27:18 Judy has joined #tpac 00:27:25 -> https://www.w3.org/2019/Talks/TPAC/continuous-standards/#19 Impact on AC and Legal Teams 00:27:32 [We skip] 00:27:39 -> https://www.w3.org/2019/Talks/TPAC/continuous-standards/#20 Impact on horizontal review 00:28:02 PLH: Key is to improve tooling to help reduce cognitive load of context-switching due to ongoing changes 00:28:14 -> https://www.w3.org/2019/Talks/TPAC/continuous-standards/#21 Impact on implementers and users 00:28:44 PLH: RF commitments provide more confidence, official specs reflect latest thinking, easier maintenance, granular reviews of Proposed Recs 00:28:58 -> https://www.w3.org/2019/Talks/TPAC/continuous-standards/#23 Motivations for Alternative Track Proposal 00:29:17 kimwooglae has joined #tpac 00:29:18 PLH: Process CG originally tried developing an alternative track proposal but there were concerns 00:29:21 Bert has joined #tpac 00:29:48 PLH: AC more willing to change patent policy for an alternative track 00:29:56 PLH: WGs that want continuous development feel the proposal package is insufficient. 00:30:04 ...those are two motivations for an alternate track 00:30:27 jc has joined #tpac 00:30:40 -> https://www.w3.org/2019/Talks/TPAC/continuous-standards/#24 “Evergreen Recommendation” Track 00:30:52 ^the above are hypothetical, **if** they were true, we'd need the evergreen track 00:31:55 PLH: We have been asking WGs and Horizontal Review groups about value or challenges of alternate track 00:32:03 hober has joined #tpac 00:32:11 ...there's also a survey to the AC 00:32:14 https://www.w3.org/2019/Talks/TPAC/continuous-standards/#29 00:32:20 Arnaud has joined #tpac 00:32:27 xfq has joined #tpac 00:32:34 -> https://www.w3.org/2019/Talks/TPAC/continuous-standards/#29 Questions for the AC in the survey 00:32:42 mchampion has joined #tpac 00:32:47 lilin has joined #tpac 00:32:48 PLH: if you have questions, please come to our breakout session later today! 00:32:56 I have made the request to generate https://www.w3.org/2019/09/17-tpac-minutes.html Ian 00:33:24 MO has left #tpac 00:33:26 fantasai: We wanted to enable WGs to do continuous updates at the same time as we wanted to have checks in the process. 00:33:35 ...for REC status we wanted to ensure wide review and implementation experience 00:33:58 ...the REC status is formally recognized by other organizations, so we need to have the necessarily stability properties 00:34:17 ...we are trying to bring together these different requirements: ease of work, horizontal review, stability 00:34:44 ...and to enable both flexibility for groups as well as enough structure to enable new (or controversy-laden) groups to manage their work 00:34:52 yos has joined #tpac 00:35:00 marcosc: This is great, thanks for hearing editors! Let us know how we can help 00:35:02 horiuchi has joined #tpac 00:35:10 kzms2 has joined #tpac 00:35:15 fantasai: Please encourage AC reps to complete the survey, provide feedback and support 00:35:44 I have made the request to generate https://www.w3.org/2019/09/17-tpac-minutes.html Ian 00:36:28 Jeff: I want to emphasize the importance of AC feedback. Changing the patent policy or process involves a lot of work. I'd like to see a lot of enthusiasm and momentum from the membership. 00:36:31 jkamata__ has joined #tpac 00:36:35 ...please ask your AC rep to add to the support 00:36:52 Tpoic: MDN Web Developer Needs Assessment 00:36:57 Topic: MDN Web Developer Needs Assessment 00:37:09 horiuchi_ has joined #tpac 00:37:23 Dom: MDN is one of the most popular documentation portals for the Web. I am part of the effort. 00:37:28 -> https://www.w3.org/2019/Talks/TPAC/MDN-WEB-DNA.pdf slides: The MDN Web Developer Needs Assessment: The voice of developers and designers working on the web 00:37:33 ...Mozilla organized a survey that involved the W3C community 00:37:46 ...group chairs helped inform shape of survey 00:37:52 iclelland has joined #tpac 00:37:58 ...today we will go over what we learned. 00:38:10 Kadir Topal: I am the product lead for MDN Web Docs 00:38:17 ...I started my career in 1997 as a Web Developer 00:38:20 ...this is my first PAC 00:38:23 s/PAC/TPAC 00:38:31 ...you are amazing [at making sausage] 00:39:01 [slide on the case of CSS Grid] 00:39:43 Kadir: CSS Grid was a massive success because it addressed a real user need, was shipped by browsers around the same time, etc. 00:40:01 ...but CSS Grid was years in the making, and layout had been an issue since the days of using tables for layout. 00:40:13 jc_ has joined #tpac 00:40:16 ...so we had some questions: why did it take 5 years between spec and shipping interoperably? 00:40:30 ...what were the critical elements of moving this forward. 00:40:34 [Web Platform Lifecycle] 00:40:52 Kadir: We identified 3 distinct phases: Research, Standardization, Adoption 00:41:11 ...it is very simplified, of course, and looks like a pipe even though it is more like a loop of loops in reality 00:41:49 ...we really wanted to learn more in particular about the research phase (developer pain points etc.) 00:42:13 ...it's important to do more research to understand the developer pain points 00:42:26 ...here's what we heard about how things are prioritized.... 00:42:42 ...and what stood out in our project was clearly that we need to hear more the voice of developers 00:43:05 ...it's hard to get people to adopt something if a solution does not meet needs or does not do so in the right way 00:43:10 [Developer Needs Assessment] 00:43:18 - Prioritized list of web designer and developer needs 00:43:21 - Published on MDN 00:43:27 - Annually published, tracking changes over time 00:43:43 Kadir: This assessment is not owned by any particular browser vendor 00:43:50 s/Tpoic: MDN Web Developer Needs Assessment// 00:44:21 I have made the request to generate https://www.w3.org/2019/09/17-tpac-minutes.html Ian 00:44:43 Kadir: We think that if we do this well, the MDN DNA can be the voice of designers and developers working on the web 00:45:01 ....asking these question is not trivial since the audience is diverse and the problem space is enormouse 00:45:08 s/enormouse/enormous 00:46:06 Kadir: We formulated the survey based on interviews with developers and designers from the beginning 00:46:13 ..it was an outside-in process; that was really important 00:46:27 ...we followed a pinpoints analysis process to go from interviews to the survey 00:46:42 ...."Observations" -> "Insights" -> "Critical themes" 00:47:02 ...we transcribed 16 hours of interviews, bucketed them. 00:47:11 ...lots of moving post-its around 00:47:40 ...we worked with our MDN advisory board, revised the survey to remove ambiguities 00:48:01 ...in July 2019 we launched the final version of the survey 00:48:10 ...the survey was available in 8 languages 00:48:22 atai has joined #tpac 00:48:40 ...we heard from more than 76K developers and designers over 4 weeks. 00:48:58 ...more than 28K completes from 173 countries and almost 10K hours of developer time 00:49:33 ...we think this is the biggest dev/designer survey ever conducted. 00:49:46 wjmaclean has joined #tpac 00:49:46 ...we can slide the responses in different ways due to sample size 00:49:53 [Sample Questions] 00:50:29 - overall satisfaction with web 00:50:32 .... 00:50:34 [Sample Results] 00:50:58 Main question of the survey was top frustrations: 00:51:02 - having to support specific browsers 00:51:11 - outdated or inaccurate documentation for frameworks and libfrariers 00:51:27 - interop again: avoiding or removing a feature that doesn't work across browsers 00:51:33 - interop: testing across browsers 00:51:42 - interop: making a design look/work the same across browsers 00:52:06 [What are main barriers to adoption of a new feature?] 00:52:18 1) Interop across browsers 00:52:23 2) Documentation and training 00:52:31 3) Support for legacy browsers 00:52:42 [Biggest pain points for HTML dev] 00:52:52 - Biggest pain point cited was NONE 00:53:12 [Overall satisfaction] 00:53:21 - 76% are satisfied or very satisfied 00:53:28 [Applause from the room!] 00:53:33 [Next iteration] 00:53:52 Kadier: Report for first iteration in Nov 2019, second iteration starts March 2020 00:54:05 ...then publish next results in September 2020 in time for TPAC 2020! 00:54:10 [Prioritized list of needs] 00:54:29 jorydotcom has joined #tpac 00:54:31 Goal: Tool for prioritization.... 00:54:44 ....you are the target audience (in this room), how useful to you? What level of granularity? 00:54:58 CharlesL has joined #tpac 00:55:20 Kadir: Many thanks to everyone who contributed!! I'm excited by the results and look forward to more in this space. 00:55:24 I have made the request to generate https://www.w3.org/2019/09/17-tpac-minutes.html Ian 00:55:57 Glenn: You mentioned browser vendors many times, but there are other types of applications as well for Web technology. 00:56:22 ...you didn't mention volunteerism in WGs, which is a key factor in how priorities are worked out 00:56:28 s/Glenn/Glenn Adams 00:57:02 Rick Byers: one of our topi priorities at Blink is to help developers love the web more, so I want to say I am committed to changing priorities in our team based on what you learned 00:57:04 s/Glenn Adams/Glenn_Adams/ 00:57:08 s/topi/top 00:57:15 Phil_Archer: Thank you for MDN! 00:57:39 Charles_Lapierre: I was surprised that accessibility was not listed as a top frustration. 00:57:54 s/k B/k_B/ 00:58:14 Kadir: It is in the list of frustrations. It ended up fairly low on this list. Our interpretation is that it's more about lack of knowledge or practice 00:58:22 I have made the request to generate https://www.w3.org/2019/09/17-tpac-minutes.html Ian 00:58:26 tantek has joined #tpac 00:58:56 yy has joined #tpac 00:59:05 present+ 00:59:12 Topic: Finalizing the Breakout Session Grid 00:59:46 Dom: Reminder that the rest of the day is an unconference, where the discussion is driven by the participants 01:00:07 ...Coralie Mercier and I have worked with the meeting planners to make this a success 01:00:26 Dom: Many TPAC attendees find this day energizing and a great way to discover new topics 01:00:38 ....we have been collecting breakout session proposals 01:00:48 -> https://w3c.github.io/tpac-breakouts/sessions.html Session grid 01:00:54 jorydotcom has joined #tpac 01:00:57 ...participants decide which sessions they want to attend 01:01:07 -> https://www.w3.org/2019/Talks/TPAC/dhm-breakouts-intro/Overview.html slides: TPAC Unconference 01:01:54 ...please ask Coralie or me questions about the day. 01:02:13 Dom: We changed our format from previous years based on feedback. In particular, we heard: 01:02:24 - Please have more breakout session! 01:02:34 ...so we went from 4 slots to 5 this year 01:03:01 - We also did more work before the meeting on the grid to avoid the "mad scramble" which was considered non-inclusive 01:03:38 deiu has joined #tpac 01:03:39 - We also heard that having the schedule in a wiki was hard to read (especially on mobile) 01:04:14 - Also because people may be interested in more than one session, people may wish to follow some sessions by IRC. So we have IRC channels publicized in advance 01:04:21 MURATA has joined #tpac 01:04:34 Dom: We welcome your feedback on these improvements 01:05:06 Dom: We have 12 rooms and 5 slots, for 60 sessions (compared to 40-ish previously) 01:05:31 ...however, we gave up the reporting session. We will try to compensate for that by asking the session leads to create written reports 01:05:59 ...regarding gathering session proposals in advance - the response rate was really amazing! 01:06:13 ...that is also far more than we had received previously before a TPAC 01:06:39 ...my early analysis of the proposals is also that there is more diversity in who proposed sessions. I think we could still do better with enabling newcomers to submit proposals. 01:06:55 ...the agenda page is more mobile-friendly so that people can move among rooms more easily 01:07:26 Dom: We have some questions! 01:07:43 - Should we allow more opportunity for last-minute session proposals? 01:07:53 - Is 60 sessions too many? 01:08:24 Dom: Thanks to Marie-Claire Forgue for organizing 14 demos at the 3:30pm break. Demos from WGs and CGs 01:08:49 ...demos provide a great way to keep tabs on what's going on in other parts of W3C, and to understand why and how these technologies are being used. 01:08:59 ...you can also discuss them with the people who are behind the technologies. 01:09:05 ...the demos will be set up in the break room 01:09:25 Dom: Regarding final preparations: 01:09:28 -> https://www.w3.org/wiki/TPAC2019/Demos Demos later today 01:09:29 - Any last-minute adjustments 01:09:35 - Proposal for the last session room? 01:09:56 Dom: I invite proposers to come to the front of the room to enable you to adjust the grid with minimal conflict 01:10:08 I have made the request to generate https://www.w3.org/2019/09/17-tpac-minutes.html Ian 01:10:12 Arnaud has joined #tpac 01:10:19 -> https://w3c.github.io/tpac-breakouts/sessions.html#future agenda page 01:10:50 Dom: While we are doing the final preparations, I invite other people to check out the final agenda at 10:30 and plan to be at your first session at 11:00 01:11:18 ...please have a look at the sessions now as I anticipate few changes 01:12:00 Please also see: 01:12:05 -> https://www.w3.org/wiki/TPAC/2019/FAQ#What_is_good_practice_for_organizing_a_session.3F Good practice for running a session 01:12:23 Dom: Organizers, please allow 5 minutes at the end of the session when people have to travel to the next session 01:13:03 Dom: A breakout proposer includes (1) people who already proposed sessions (2) people who want to propose a sessoin 01:13:18 I have made the request to generate https://www.w3.org/2019/09/17-tpac-minutes.html Ian 01:13:38 nigel: since there is no reporting session, please make sure to take minutes 01:14:01 shimazu has joined #tpac 01:16:06 yoshiaki has joined #tpac 01:17:46 yoshiaki has joined #tpac 01:17:52 yajun_chen has joined #tpac 01:18:19 atai has joined #tpac 01:18:22 xfq has joined #tpac 01:18:32 yajun_chen has left #tpac 01:19:30 karl has joined #tpac 01:19:51 iclelland has joined #tpac 01:25:03 shimazu has joined #tpac 01:28:48 plh has joined #tpac 01:32:07 https://www.w3.org/wiki/TPAC/2019/SessionIdeas is now available for edits again 01:35:38 yoshiroy has joined #tpac 01:37:02 jorydotcom has joined #tpac 01:37:27 Judy has joined #tpac 01:37:50 jc has joined #tpac 01:37:55 nmooney has joined #tpac 01:39:23 karl has joined #tpac 01:40:23 xfq has joined #tpac 01:45:31 plh has joined #tpac 01:47:50 AdrianHB has joined #tpac 01:49:20 CharlesL has joined #tpac 01:49:25 CharlesL has left #tpac 01:51:02 kaz has joined #tpac 01:52:40 denis has joined #tpac 01:54:17 nmooney has joined #tpac 01:56:08 remember to /invite Zakim #yourchannelname 01:56:29 horiuchi has joined #tpac 01:57:22 dom has joined #tpac 01:57:43 cwarnier has joined #tpac 01:58:43 shimazu has joined #tpac 01:59:18 iclelland has joined #tpac 01:59:48 toshiakikoike has joined #tpac 01:59:54 jorydotcom has joined #tpac 02:00:49 AdrianHB has joined #tpac 02:02:00 yoshiaki has joined #tpac 02:02:07 atai has joined #tpac 02:02:08 jc has joined #tpac 02:02:45 anssik has joined #tpac 02:03:05 xfq has joined #tpac 02:03:14 xfq has left #tpac 02:03:39 msw_ has joined #tpac 02:05:41 dsinger has joined #tpac 02:05:50 jc has joined #tpac 02:06:07 karl has joined #tpac 02:07:06 nigel has joined #tpac 02:07:26 Judy has joined #tpac 02:08:21 mweksler has joined #tpac 02:08:27 public service announcement: Reload today's schedule early and often--the topics, rooms, etc, have all changed (and I suppose may again)! 02:08:59 yoshiroy has joined #tpac 02:10:17 Ian has left #tpac 02:15:23 jc has joined #tpac 02:16:16