- From: Travis Leithead <travis.leithead@microsoft.com>
- Date: Tue, 22 Nov 2011 17:55:35 +0000
- To: Robin Berjon <robin@berjon.com>, DAP <public-device-apis@w3.org>
We looked it over and have no objections. Ready to get started! -Travis >-----Original Message----- >From: Robin Berjon [mailto:robin@berjon.com] >Sent: Tuesday, November 22, 2011 4:19 AM >To: DAP >Subject: Fwd: [DRAFT] Media Capture Task Force Charter > >Any feedback on this before it becomes solid and we get started? > >Begin forwarded message: >> Resent-From: public-device-apis@w3.org >> From: Robin Berjon <robin@berjon.com> >> Date: November 16, 2011 15:42:59 GMT+01:00 >> To: "public-device-apis@w3.org public-device-apis@w3.org" <public-device- >apis@w3.org>, public-webrtc@w3.org >> Subject: [DRAFT] Media Capture Task Force Charter >> archived-at: <http://www.w3.org/mid/22C84B78-685C-4B6F-85E4- >A12BC073D075@berjon.com> >> >> Dear WebRTC and Device APIs Working Groups, >> >> As discussed during our joint and respective meetings, here is a draft >proposal for a TF charter on media capture. As indicated, it is only a >draft and is very much open to feedback, concerns, etc. >> >> As per process, a TF charter is a rather informal document that only >needs to document the TF's existence. It can just live in an email that is >linked to from our groups' pages - so we don't need to do anything >complicated and only need to write down what we think is important to >capture (i.e. no boilerplate required). >> >> """ >> The Media Capture Task Force is a joint task force of the Web Real-Time >Communications and Device APIs WGs that aims to produce APIs to capture >media from cameras and microphones in a manner that is both simple for >local-only use cases and amenable to real-time streaming. This work will be >produced by iterating over the existing "getUserMedia()" API. >> >> The mailing list on which the TF's discussions take is public-media- >capture@w3.org. The chairs are Stefan Håkansson and Harald Alvestrand. >Since any participant in either group can join the TF, decisions are made >by consensus inside of the task force and do not require separate >ratification by the wider groups. >> >> Operational modalities such as whether or not to have phone and/or face >to face meetings, as well as where to store the draft document are left to >the TF to decide by consensus. >> >> Given that this deliverable is covered by both groups' charters, the >resulting specification will be covered by the union of RF commitments for >both groups. >> """ >> >> Ideally, we should be able to garner sufficient feedback inside of a week >to tweak this charter and just get to work, which my understanding is what >everyone wants to do! >> >> -- >> Robin Berjon - http://berjon.com/ - @robinberjon >> >> > >-- >Robin Berjon - http://berjon.com/ - @robinberjon > >
Received on Tuesday, 22 November 2011 17:56:22 UTC