See also: IRC log
<trackbot> Date: 09 October 2014
<wycats____> I am on IRC only today
<scribe> Agenda:
Minutes & actions review from f2f
The never-ending URL discussion, is there anything further we can constructively do?
Any feedback / outreach plans for EW report card?
Technical topic for next call
Finalizing and sending EME feedback
Minutes from f2f: https://github.com/w3ctag/meetings/tree/gh-pages/2014/sept29-oct1
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?
Some actions recorded on the whiteboard from the f2f, here: https://github.com/w3ctag/meetings/blob/gh-pages/2014/sept29-oct1/whiteboard4.JPG
<twirl> twirl: Domenic made pull request with our F2F feedback, looks totally nice: https://github.com/w3ctag/eme/pull/9
<wycats> dka: ok :)
Is there any more constructive thing we can do in the URL debate?
(My sense is “no”, by the way.)
<wycats> I don't think we should support the HTML5 Editors changes
<wycats> the blog post inserted into the spec
Agreed but we shouldn’t become the html5 editors...
What technical topic should we tee up for next week’s teleconference?
<Yves> +1 the final word is in the html-wg and in the director's decision
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?)
<wycats> Yves: if that is the final word, the controversy will not end
<wycats> so let's not have it be the final work, mmkay?
Domenic, are you close to being able to join?
<wycats> dka: I'm kind of interested in talking about the EWM "staging problem"
<Yves> final word is not final work :)
<dherman> +1 re: staging
wycats can you elaborate on that?
<dherman> dka I can
<wycats> 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
<wycats> and how to ensure that things happen in the right order
<dherman> EWM is all about allowing user-customizable browser semantics
<wycats> I will let dherman say more :)
Ok do you want to put it into https://github.com/w3ctag/meetings/wiki
<dherman> but you need to run code to customize the semantics
<dherman> and then you need to run code that uses the customized semantics
<dherman> so one set of code has to be run earlier than another set of code is even processed
<dherman> this keeps coming up and being solved in different ad hoc ways
<dherman> html imports and custom elements: upgrade
(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)
<dherman> service worker: second-load
<dherman> module loaders: staging
<dherman> that's the gist of it
Any special guest we should invite to that discussion?
<dherman> dunno
OK sounds good!
Next step for EME?
Sergey: just to send it as a spec review.
ok - domenic should do that…. :)
Domenic: the feedback should be divided into bugs.
Dan: sounds fine, but seems like the bugs should link back to the full review...
Domenic: “we make them aware of
it first and we were thinking of filing bugs…”
... maybe use the issue tracker [in gh] as a backlog of
potential issues to discuss
Dan: sounds good.
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.
… being resolved, webrtc and promises … legacy prefixed APIs all use callbacks. but not shipping in any browsers…
… but it’s going down the right path.
Dan: Brings to mind that we were going to have a technical topic for a future call on webrtc I think.
Domenic: yes it would be good to get a status update.
Dan: I will take that action and maybe we can do that for 2 weeks from now, 23rd October.
This is scribe.perl Revision: 1.138 of Date: 2013-04-25 13:59:11 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) No ScribeNick specified. Guessing ScribeNick: dka Inferring Scribes: dka WARNING: No "Topic:" lines found. Default Present: plinss, +44.773.051.aaaa, dka, twirl, Yves, +1.408.355.aabb, Domenic Present: plinss +44.773.051.aaaa dka twirl Yves +1.408.355.aabb Domenic Regrets: Jeni WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 09 Oct 2014 Guessing minutes URL: http://www.w3.org/2014/10/09-tagmem-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: No "Topic: ..." lines found! Resulting HTML may have an empty (invalid) <ol>...</ol>. Explanation: "Topic: ..." lines are used to indicate the start of new discussion topics or agenda items, such as: <dbooth> Topic: Review of Amy's report[End of scribe.perl diagnostic output]
