See also: IRC log
<trackbot> Date: 27 February 2014
<scribe> ScribeNick: fjh
fjh: add agenda item regarding meeting scheduling and frequency
Approve minutes from 20 February 2014
http://lists.w3.org/Archives/Public/public-device-apis/2014Feb/att-0047/minutes-2014-02-20.html
RESOLUTION: Minutes from 20 February 2014 are approved
fjh: CfC to shelve extended one week, to 4 March, see http://lists.w3.org/Archives/Public/public-device-apis/2014Feb/0055.html
fjh: Pull request status summary : http://lists.w3.org/Archives/Public/public-device-apis/2014Feb/0049.html
... All four pull requests have a critic comment that says "waiting for review from Simon Pieters, Masataka Yakura, xiaoqian, Anne van Kesteren, James Graham"
... I'm not quite sure what we should do with these reviewers
... or how they became the default critics
anssik: what about Tobie
<anssik> "This is an external review system which you may optionally use for the code review of your pull request."
fjh: Tobie has raised an issue I noted in my message, so he has been reviewing, I don't think we need to ask him again
... not quite sure how to incorporate these changes, from the change log
<scribe> ACTION: fjh to follow up on how to approve pull requests and to identify correct reviewers, remove inappropriate critics etc [recorded in http://www.w3.org/2014/02/27-dap-minutes.html#action01]
<trackbot> Created ACTION-682 - Follow up on how to approve pull requests and to identify correct reviewers, remove inappropriate critics etc [on Frederick Hirsch - due 2014-03-06].
<anssik> Zhiqiang Zhang
fjh: we also need to determine if pull request closes Tobie's issue, I'll ask Tobie about this issue as well as the pull requests in general
... Lisa you wanted to mention helping with implementation
LisaDeLuca_IBM: Dom sent message to cordova list
... I said I am in both groups, suggested we open Jira issues, Dom opened 10 of them
... also part of open standards group at IBM, working with management to see how much time I can spend, resources we can involve
... others have their own agendas, so I might be able to help align efforts
... next steps will be to break out Jira issues to various platforms, iOS, Android, etc
... then need to get those familiar with those platforms to help with changes
... this will take some work but is progressing
<LisaDeLuca_IBM> https://issues.apache.org/jira/browse/CB-6065 battery https://issues.apache.org/jira/browse/CB-6066 html media capture https://issues.apache.org/jira/browse/CB-6068 contacts https://issues.apache.org/jira/browse/CB-6069 motion https://issues.apache.org/jira/browse/CB-6070 orientation https://issues.apache.org/jira/browse/CB-6071 notifications https://issues.apache.org/jira/browse/CB-6072 File transfer https://issues.apache.org/jira/brows[CUT]
<LisaDeLuca_IBM> https://issues.apache.org/jira/browse/CB-6074 Media https://issues.apache.org/jira/browse/CB-6075 Vibration which was marked as a dup of https://issues.apache.org/jira/browse/CB-5459
fjh: thanks for the information and the help
... do you have any idea regarding time frames for various milestones etc?
LisaDeLuca_IBM: I also have more links regarding plugins
<LisaDeLuca_IBM> http://cordova.apache.org/docs/en/3.4.0/cordova_plugins_pluginapis.md.html#Plugin%20APIs
<LisaDeLuca_IBM> 17 core plugins for Cordova
LisaDeLuca_IBM: expect more resources to help with Cordova so having clearly defined issues in Jira should help
anssik: have looked at material Lisa has provided
LisaDeLuca_IBM: we need to prioritize
<anssik> I propose Cordova prioritizes features for which there are other implementations and/or that are more mature
LisaDeLuca_IBM: will share these links on the list and get the conversation started
fjh: that sounds great
<anssik> for example, Vibration, Battery Status API, and HTML Media Capture already have implementations, and the specs are maturing
WD published, see http://lists.w3.org/Archives/Public/public-device-apis/2014Feb/0048.html
fjh: now the publication is consistent with our current state which is good
WD: http://www.w3.org/TR/2014/WD-discovery-api-20140220/
fjh: I have entered a few new issues that came up during the publication process
ISSUE-157?
<trackbot> ISSUE-157 -- Style element appears in body before bibliography, should be in head (validation issue) -- open
<trackbot> http://www.w3.org/2009/dap/track/issues/157
ISSUE-158?
<trackbot> ISSUE-158 -- Whatwg promises related links are broken and should be removed, new promises reference needed -- open
<trackbot> http://www.w3.org/2009/dap/track/issues/158
ISSUE-159?
<trackbot> ISSUE-159 -- Diff link in WD broken, update in source -- open
<trackbot> http://www.w3.org/2009/dap/track/issues/159
fjh: I also followed up on my action and shared information about the publication and its revisions, including CORS and promises , to both Mozilla and Chromium, on their bug lists which I joined
ACTION-681?
<trackbot> ACTION-681 -- Frederick Hirsch to Follow up on letting chromium & mozilla teams know about cors addition to network service discovery -- due 2014-02-20 -- PENDINGREVIEW
<trackbot> http://www.w3.org/2009/dap/track/actions/681
fjh: Chromium: https://groups.google.com/a/chromium.org/forum/#!searchin/blink-dev/network$20service$20discovery/blink-dev/HT0KZKuTLxM/S3w-SdvjZfUJ
... Mozilla: https://bugzilla.mozilla.org/show_bug.cgi?id=914579
... there was some concern about promise usage but Rich discussed that and I believe it was a misunderstanding
... concern from Jonas about security model with suggestion to avoid Network Service Discovery and build directly on sockets etc
... those interested in NSD for TV seem to go along with that approach
... suggest we have call with Jonas to discuss
... will set up, but would like Dom on call so may be in two weeks
... will follow up privately then if interest share on list
... also suggest we might need to change the call time so we can have Rich on the call (and make it easier for Cathy to join)
... Cathy do you have anything more to add
cathy_chan: not more to add
close ACTION-681
<trackbot> Closed ACTION-681.
fjh: testing and implementation remain primary actions
ACTION-523?
<trackbot> ACTION-523 -- Anssi Kostiainen to Work on test cases for battery, vibration, and HTML Media Capture -- due 2012-08-31 -- OPEN
<trackbot> http://www.w3.org/2009/dap/track/actions/523
fjh: we may wish to reschedule meeting time so participants in Network Service Discovery can attend
... also prefer earlier in week
... Tue, Wed might be best
... suggest we might want calls every other week so people can make better use of their time and plan
... we don't seem to have need for weekly calls right now, and I wish to respect your time
LisaDeLuca_IBM: +1
anssik: +1
<Clarke> +1
fjh: I will propose an every other week schedule immediately, taking into account holidays etc
... using the current slot - we can then think about changing the slot separately
none