- From: Dominique Hazael-Massieux <dom@w3.org>
- Date: Tue, 22 Nov 2016 18:07:55 +0100
- To: public-media-capture@w3.org
Hi, The mail below is a digest compiling activities in the Media Capture Task Force repositories over the past week - the chairs have suggested to see if these digests bring value in addition (and possible later instead) of live notifications of new issues and PRs - feedback on that and on the content of the digest is welcomed. Thanks, Dom On 22/11/2016 18:00, W3C Webmaster via GitHub API wrote: > > > Issues > ------ > * w3c/mediacapture-main (+1/-1/💬9) > 1 issues created: > - gUM algorithm shouldn't remove "denied" sources from finalSet (by > jan-ivar) > https://github.com/w3c/mediacapture-main/issues/418 > > 1 issues closed: > - gUM algorithm shouldn't remove "denied" sources from finalSet > https://github.com/w3c/mediacapture-main/issues/418 > > 2 issues received 9 new comments: > - #268 Iframe sandboxing options for gUM (8 by annevk, raymeskhoury, > alvestrand) > https://github.com/w3c/mediacapture-main/issues/268 > - #418 gUM algorithm shouldn't remove "denied" sources from finalSet > (1 by jan-ivar) > https://github.com/w3c/mediacapture-main/issues/418 > > * w3c/mediacapture-record (+3/-0/💬1) > 3 issues created: > - Bugs in isTypeSupported() example (by ddorwin) > https://github.com/w3c/mediacapture-record/issues/94 > - Reconsider isTypeSupported() API (by ddorwin) > https://github.com/w3c/mediacapture-record/issues/93 > - isTypeSupported() algorithm should be more specific (by ddorwin) > https://github.com/w3c/mediacapture-record/issues/92 > > 1 issues received 1 new comments: > - #92 isTypeSupported() algorithm should be more specific (1 by > ddorwin) > https://github.com/w3c/mediacapture-record/issues/92 > > * w3c/mediacapture-depth (+1/-0/💬7) > 1 issues created: > - Should we do depth-video synchronization in browser, in JS, in > both, what's v1 and what's v2? (by astojilj) > https://github.com/w3c/mediacapture-depth/issues/145 > > 5 issues received 7 new comments: > - #143 Change depth to MediaTrackConstraints (2 by huningxin) > https://github.com/w3c/mediacapture-depth/issues/143 > - #110 Accessing Camera Calibrations (2 by huningxin, astojilj) > https://github.com/w3c/mediacapture-depth/issues/110 > - #80 Need measureType for accurate reprojection (1 by huningxin) > https://github.com/w3c/mediacapture-depth/issues/80 > - #142 (16-bit) Grayscale conversion of (16-bit) depth map is wrong > (1 by huningxin) > https://github.com/w3c/mediacapture-depth/issues/142 > - #145 Should we do depth-video synchronization in browser, in JS, > in both, what's v1 and what's v2? (1 by astojilj) > https://github.com/w3c/mediacapture-depth/issues/145 > > > Pull requests > ------------- > * w3c/mediacapture-main (+1/-0/💬4) > 1 pull requests submitted: > - Make the devicechange consistent with enumerateDevices wrt > permissions. (by guidou) > https://github.com/w3c/mediacapture-main/pull/419 > > 1 pull requests received 4 new comments: > - #419 Make the devicechange consistent with enumerateDevices wrt > permissions. (4 by jan-ivar, guidou) > https://github.com/w3c/mediacapture-main/pull/419 > > * w3c/mediacapture-depth (+0/-0/💬1) > 1 pull requests received 1 new comments: > - #144 Fix #110, #135: Intrinsics and extrinsics (1 by astojilj) > https://github.com/w3c/mediacapture-depth/pull/144 > > > Repositories tracked by this digest: > ----------------------------------- > * https://github.com/w3c/mediacapture-main > * https://github.com/w3c/mediacapture-record > * https://github.com/w3c/mediacapture-image > * https://github.com/w3c/mediacapture-depth > * https://github.com/w3c/mediacapture-fromelement > * https://github.com/w3c/mediacapture-output > * https://github.com/w3c/mediacapture-screen-share >
Received on Tuesday, 22 November 2016 17:08:04 UTC