16:59:50 RRSAgent has joined #tagmem 16:59:50 logging to http://www.w3.org/2014/10/09-tagmem-irc 16:59:52 RRSAgent, make logs public 16:59:54 Zakim, this will be TAG 16:59:54 ok, trackbot, I see TAG_Weekly()1:00PM already started 16:59:55 Meeting: Technical Architecture Group Teleconference 16:59:55 Date: 09 October 2014 17:00:17 zakim, who is here? 17:00:17 On the phone I see plinss, +44.773.051.aaaa 17:00:19 On IRC I see RRSAgent, dka, Zakim, twirl, wycats____, slightlyoff, Domenic, dherman, projector, plinss, Yves, trackbot 17:00:37 I am on IRC only today 17:00:48 zakim, aaaa is me 17:00:48 +dka; got it 17:01:11 +??P0 17:01:58 dka has changed the topic to: https://github.com/w3ctag/meetings/wiki 17:02:05 regrets: Jeni 17:03:05 Agenda: 17:03:07 Minutes & actions review from f2f 17:03:08 The never-ending URL discussion, is there anything further we can constructively do? 17:03:09 Any feedback / outreach plans for EW report card? 17:03:10 Technical topic for next call 17:03:11 Finalizing and sending EME feedback 17:03:25 Minutes from f2f: https://github.com/w3ctag/meetings/tree/gh-pages/2014/sept29-oct1 17:03:46 +Yves 17:04:06 For those on the IRC as well, please register any requests for changes to the minutes by next week and then we’ll call them published and agreed, ok? 17:05:19 Some actions recorded on the whiteboard from the f2f, here: https://github.com/w3ctag/meetings/blob/gh-pages/2014/sept29-oct1/whiteboard4.JPG 17:08:17 twirl: Domenic made pull request with our F2F feedback, looks totally nice: https://github.com/w3ctag/eme/pull/9 17:09:05 dka: ok :) 17:09:13 Is there any more constructive thing we can do in the URL debate? 17:09:31 (My sense is “no”, by the way.) 17:09:46 I don't think we should support the HTML5 Editors changes 17:09:53 the blog post inserted into the spec 17:11:28 Agreed but we shouldn’t become the html5 editors... 17:12:26 What technical topic should we tee up for next week’s teleconference? 17:12:34 +1 the final word is in the html-wg and in the director's decision 17:14:12 wycats, dherman - do you have a specific technical topic you’d like to suggest for next week’s call? (e.g. inviting a guest from a working group or editor of a specific spec?) 17:14:35 Yves: if that is the final word, the controversy will not end 17:14:42 so let's not have it be the final work, mmkay? 17:14:53 Domenic, are you close to being able to join? 17:15:14 dka: I'm kind of interested in talking about the EWM "staging problem" 17:15:34 final word is not final work :) 17:15:44 +1 re: staging 17:15:45 wycats can you elaborate on that? 17:15:50 dka I can 17:15:54 in particular, how to deal with the fact that user code changes the meaning of the platform, but still needs to use the platform to bootstrap 17:16:03 and how to ensure that things happen in the right order 17:16:06 EWM is all about allowing user-customizable browser semantics 17:16:07 I will let dherman say more :) 17:16:11 Ok do you want to put it into https://github.com/w3ctag/meetings/wiki 17:16:12 but you need to run code to customize the semantics 17:16:18 and then you need to run code that uses the customized semantics 17:16:34 so one set of code has to be run earlier than another set of code is even processed 17:16:45 this keeps coming up and being solved in different ad hoc ways 17:16:56 html imports and custom elements: upgrade 17:16:58 (Btw if people have a better suggestion of how to organize topics / agendas etc.. for these conference calls using github please speak up - I just used a wiki page since that’s what was there) 17:17:01 service worker: second-load 17:17:20 module loaders: staging 17:17:26 that's the gist of it 17:17:32 Any special guest we should invite to that discussion? 17:17:53 dunno 17:18:19 OK sounds good! 17:18:45 Next step for EME? 17:18:51 Sergey: just to send it as a spec review. 17:19:26 ok - domenic should do that…. :) 17:23:26 + +1.408.355.aabb 17:23:38 Zakim, aabb is me 17:23:38 +Domenic; got it 17:25:23 Domenic: the feedback should be divided into bugs. 17:25:49 Dan: sounds fine, but seems like the bugs should link back to the full review... 17:26:37 Domenic: “we make them aware of it first and we were thinking of filing bugs…” 17:29:02 Domenic: maybe use the issue tracker [in gh] as a backlog of potential issues to discuss 17:29:13 Dan: sounds good. 17:30:49 Domenic: a couple things have come up - web crypto has a big debate on extension specs. some say no, one says yes…interesting quesiton, we might want to have an opinion. 17:31:19 … being resolved, webrtc and promises … legacy prefixed APIs all use callbacks. but not shipping in any browsers… 17:31:35 … but it’s going down the right path. 17:31:58 Dan: Brings to mind that we were going to have a technical topic for a future call on webrtc I think. 17:32:11 Domenic: yes it would be good to get a status update. 17:32:43 Dan: I will take that action and maybe we can do that for 2 weeks from now, 23rd October. 17:33:48 -dka 17:33:51 -Domenic 17:33:54 -Yves 17:33:56 -plinss 17:33:57 -twirl 17:33:59 TAG_Weekly()1:00PM has ended 17:33:59 Attendees were plinss, +44.773.051.aaaa, dka, twirl, Yves, +1.408.355.aabb, Domenic 17:34:00 rrsagent, make minutes 17:34:00 I have made the request to generate http://www.w3.org/2014/10/09-tagmem-minutes.html dka 17:34:12 zakim, aaaa is me 17:34:12 sorry, dka, I do not recognize a party named 'aaaa' 17:34:32 rrsagent, make logs public 18:41:14 dka has joined #tagmem 19:27:14 dka has joined #tagmem 19:27:38 darobin has joined #tagmem 19:40:18 timbl has joined #tagmem 19:47:23 Zakim has left #tagmem